Remote control pairing method, device, and storage medium

Abstract

The application discloses a pairing method and device of a remote controller and a storage medium, relates to the technical field of wireless remote control, and the method comprises the following steps: in response to a selected operation of a user on a controlled device, determining a target controlled device for this time pairing from the accessed controlled device; generating a pairing authorization instruction associated with the target controlled device based on the identity information and the wireless receiving parameters of the target controlled device; and sending the pairing authorization instruction to the target controlled device to trigger the target controlled device to switch to a pairable state. The application determines the target controlled device in response to the selected operation of the user on the controlled device, generates the corresponding pairing authorization instruction, and issues the trigger to switch to the pairable state, thereby solving the problem of poor running safety of the controlled device, improving the pairing accuracy, and realizing the effect of remote directional and convenient pairing.

Description

Technical Field

[0001] This application relates to the field of wireless remote control technology, and more particularly to a pairing method, device and storage medium for a remote control. Background Technology

[0002] In scenarios with dense deployment of multiple devices, such as industrial workshops, automated production lines, and large warehouses, the accurate and secure pairing of remote controllers with controlled devices directly affects the reliability of device control, the stability of production line operation, and the safety of on-site management. Anti-interference pairing triggering mechanisms, full-process pairing status management, and controllable pairing time window management are the core foundations for achieving secure and reliable pairing of remote controllers in multi-device scenarios.

[0003] In related technologies, pairing mode is usually entered by pressing and holding a button on the receiving device. The pairing operation between the remote control and the device is completed through an open process without unified control, which can easily cause nearby devices to accidentally trigger pairing, resulting in poor operational security of the controlled device.

[0004] The above content is only used to help understand the technical solution of this application and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this application is to provide a pairing method, device, and storage medium for a remote control, aiming to solve the technical problem of poor operational security of the controlled device.

[0006] To achieve the above objectives, this application proposes a pairing method for a remote control, the method comprising: In response to the user's selection of a controlled device, the range of controlled devices that the user can operate is filtered based on the user's permission level. Then, combined with the user's current physical space and usage scenario, the range of operable devices is further filtered to obtain a pool of selectable devices. Based on the pool of available devices, the device information corresponding to the selected operation is matched to determine the target controlled device for this pairing. Based on the identification information and wireless reception parameters of the target controlled device, a pairing authorization command associated with the target controlled device is generated; The pairing authorization command is sent to the target controlled device to trigger the target controlled device to switch to a pairable state.

[0007] In one embodiment, a pairing verification key adapted to the wireless communication specifications of the target controlled device is obtained based on the wireless reception parameters of the target controlled device. The identity information of the target controlled device, the pairing verification key, and the pairing operation parameters are encrypted and integrated to obtain the initial authorization data; Add an anti-tampering verification code and a host computer identity signature to the initial authorization data to generate a paired authorization instruction associated with the target controlled device.

[0008] In one embodiment, the pairing result information returned by the target controlled device and the remote controller after pairing is completed is received, and the pairing result information is associated with this pairing and archived. The pairing results are compared and analyzed according to the pairing process optimization rules to determine the parameter adjustment space in the pairing process; Based on the parameter adjustment space, combined with the deployment environment and operating status of the controlled device, and the parameter information of the remote controller, a pairing optimization parameter set adapted to the controlled device and the remote controller is generated; The pairing optimization parameter set is sent to the corresponding controlled device and the remote controller to complete the parameter update of the controlled device and the remote controller.

[0009] In one embodiment, in response to a pairing authorization command issued by the host computer, the pairing timer window of the target controlled device is started, and the target controlled device is switched to a pairable state; Within the effective duration of the pairing time window, the parsed data of the remote control identity identifier, pairing verification key, device type matching identifier, and group affiliation identifier contained in the candidate signal are extracted, and the authorization control rules in the current pairing authorization instruction are retrieved. The candidate signal is the signal sent by the target controlled device in the pairable state. The parsed data of the candidate signals are matched with the authorization control rules for this pairing in all dimensions to filter out signals that meet the authorization requirements for this pairing and determine them as the pairing request signals for this pairing. The remote control corresponding to the pairing request signal is bidirectionally linked to the target controlled device.

[0010] In one embodiment, after receiving the pairing authorization command sent by the host computer, the identity information of the pairing authorization command is parsed to obtain the identity information of the pairing authorization command; After confirming that the identity information matches the identity of the target controlled device, a pairing mode trigger signal is generated according to the pairing authorization instruction; Based on the pairing mode trigger signal, a pairing timer window of fixed duration is started, and the wireless receiving module of the target controlled device is switched to the pairable state. Based on the pairable state, the control unit switches its own status indicator to a pairing process prompt state and sends the status information of the pairing window back to the host computer.

[0011] In one embodiment, based on the pairable state, a wireless communication channel is locked and external noise interference is shielded to construct a pairing signal detection environment; During the effective time period of the pairing timing window, the wireless radio frequency signal of the pairing signal detection environment is collected at a fixed timing period; The wireless radio frequency signal is screened step by step according to the encoding rules to filter out invalid interference signals and obtain the candidate signal. By verifying the identity information carried in the candidate signal, the pairing request signal is determined and received by the wireless receiving module within the pairing timing window.

[0012] In one embodiment, if the target controlled device does not receive a verified pairing request signal before the pairing time window is zeroed, a pairing failure trigger signal is generated. Based on the pairing failure trigger signal, the pairing identification channel of its own wireless receiving module is turned off, and a pairing failure result analysis command is generated; Based on the failure result analysis instructions, organize the pairing records and failure reasons for this pairing operation to obtain the failure traceability record; After associating the failure tracing record with the current pairing, the failure tracing record is uploaded to the host computer.

[0013] In one embodiment, upon receiving the pairing request signal, a pairing confirmation signal with the target controlled device is triggered; The pairing confirmation signal is sent to the remote controller to establish a pairing and binding channel between the target controlled device and the remote controller; Based on the pairing and binding channel, a two-way interactive binding is performed with the remote controller to complete the pairing process between the remote controller and the target controlled device.

[0014] In addition, to achieve the above objectives, this application also proposes a pairing device for a remote control, the pairing device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the pairing method for the remote control as described above.

[0015] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the remote control pairing method described above.

[0016] This application provides a remote control pairing method, which includes determining the target controlled device for pairing from the connected controlled devices in response to a user's selection operation for the controlled device, generating a pairing authorization command associated with the target controlled device based on the identification information and wireless receiving parameters of the target controlled device, and finally sending the pairing authorization command to the target controlled device to trigger it to switch to a pairable state. This method solves the technical problems in existing controlled device pairing processes, such as the need for users to manually operate the device to enter pairing mode, low pairing target accuracy in multi-device access scenarios, easy mispairing with non-target devices, and cumbersome and inefficient pairing triggering process. It improves the directional accuracy and overall execution efficiency of controlled device pairing, simplifies the user's pairing operation steps, realizes remote directional triggering of the target controlled device's pairable state, effectively avoids the risk of mispairing in multi-device scenarios, and greatly optimizes the operation experience and process controllability of device pairing.

[0017] In summary, this application determines the target controlled device by responding to the user's selection operation of the controlled device, generates a corresponding pairing authorization command and issues it to trigger the switching of its pairable state, thus solving the technical problem of low overall process efficiency, improving pairing accuracy, and achieving the effect of remote, targeted, and convenient pairing. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0020] Figure 1 This is a flowchart illustrating the first embodiment of the pairing method for the remote control of this application; Figure 2 This is a flowchart of the matching process for this application; Figure 3 This is a flowchart illustrating the fourth embodiment of the pairing method for the remote control of this application; Figure 4 This is a diagram illustrating the interaction framework of this application; Figure 5 This is a flowchart illustrating the seventh embodiment of the pairing method for the remote control of this application; Figure 6 This is a schematic diagram of the pairing device for the remote control of this application.

[0021] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0022] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0023] In related technologies, pairing mode is usually entered by pressing and holding a button on the receiving device. The pairing operation between the remote control and the device is completed through an open process without unified control, which can easily cause nearby devices to accidentally trigger pairing, resulting in poor operational security of the controlled device.

[0024] This application provides a solution: First, in response to a user's selection operation for a controlled device, the range of controlled devices that the user can operate is filtered based on the user's permission level. Then, combined with the user's current physical space and usage scenario, the range of operable devices is further targeted to obtain a pool of optional devices. Next, based on the pool of optional devices, the device information corresponding to the selection operation is matched to determine the target controlled device for this pairing. Then, based on the identity information and wireless reception parameters of the target controlled device, a pairing authorization instruction associated with the target controlled device is generated. Finally, the pairing authorization instruction is sent to the target controlled device to trigger the target controlled device to switch to a pairable state.

[0025] It should be noted that the executing entity in this embodiment can be a computing service device with data processing, network communication, and program execution functions, such as a tablet computer, personal computer, or mobile phone, or an electronic device capable of performing the above functions, a pairing device for a remote control, etc. The following description uses a pairing device for a remote control as an example to illustrate this embodiment and the subsequent embodiments.

[0026] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0027] This application provides a method for pairing a remote control, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the pairing method for the remote control of this application.

[0028] In this embodiment, the pairing method for the remote control includes steps S10 to S40: Step S10: In response to the user's selection operation for the controlled device, the range of controlled devices that the user can operate is filtered based on the user's permission level. Then, the range of operable devices is further filtered by combining the user's current physical space and usage scenario to obtain a pool of selectable devices.

[0029] Step S20: Based on the optional device pool, match the device information corresponding to the selected operation to determine the target controlled device for this pairing.

[0030] The user's selection of a controlled device is an interactive control action initiated by the user to specify the target device for pairing. It is the core control command that triggers the target device determination process. The connected controlled device is a variety of intelligent terminal devices with pairing capabilities that are connected to the main control system via a wireless communication link. These are the basic objects for target device selection. Examples include smart home devices, industrial IoT terminals, commercial office equipment, Bluetooth peripherals, network cameras, and smart access control devices. The target controlled device is the object selected by the user for this pairing process and is the sole target for generating and sending subsequent pairing authorization commands.

[0031] The scope of controlled devices includes all controlled devices that have established a stable communication connection with the host computer via a USB wired link and completed identity registration and ledger entry. This serves as the basic data source for device screening. Examples include all USB camera devices connected to the production line, all registered controlled devices in the same factory area, the entire set of controlled devices connected to a designated production line, and all online controlled devices in the same zone.

[0032] Physical space information, obtained through positioning modules, factory access control systems, and workstation binding information, represents the user's current physical location and spatial range. This data forms the core spatial dimension for secondary targeted filtering. Examples include the user's production line partition number, the physical address of their workstation, the factory area identifier, the physical spatial range of equipment deployment, and the real-time location coordinates collected by the positioning module.

[0033] Secondary targeted filtering, building upon primary permission filtering, involves a second, more refined filtering operation based on spatial and business scenario dimensions to assess the range of operable devices. This eliminates invalid devices that are permission-compliant but do not match the spatial or scenario requirements, narrowing the pool of selectable devices and reducing the risk of incorrect selection. Examples include physical space matching-based filtering, business scenario adaptability-based filtering, device online status-based filtering, and pairing status-based filtering.

[0034] The optional device pool is a list of controlled devices that the user can currently operate on, generated after primary permission filtering and secondary space and scenario-based targeting. It is the only selectable range of devices for the user to subsequently initiate pairing authorization and execute pairing control operations. Examples include a list of online devices in the same partition with compliant permissions, a list of devices to be maintained that match the scenario, a list of dedicated controlled devices bound to a workstation, and a list of debugging devices with temporary authorization.

[0035] In this embodiment, the user's selection operation for the controlled device can be triggered in six ways. First, device list click selection trigger: the user clicks on the target controlled device's entry in the access device list of the device management interface. After receiving the click, the system triggers the selection operation for that controlled device, used in typical single-device pairing scenarios. Second, device QR code recognition trigger: the user scans the controlled device's QR code or NFC tag. After the system recognizes the device's identity information, it automatically triggers the selection operation for the scanned device, used in scenarios of rapid on-site device pairing. Third, voice command selection trigger: the user inputs a pairing voice command containing the controlled device's name / number through a voice assistant. After the system recognizes the device information in the voice command, it automatically triggers the selection operation for the corresponding controlled device, used in touchless intelligent pairing scenarios. Fourth, automatic device discovery trigger: when a new controlled device connects to the system, the system automatically pops up a device access prompt. After the user clicks the pairing option in the prompt, the system triggers the selection operation for the newly connected device, used in scenarios of initial pairing of a new device. Fifth, scene linkage selection trigger: When the user selects a preset intelligent scene linkage scheme, the system automatically triggers the selection operation for the controlled devices bound to that scene, used for batch scene-based device pairing. Sixth, device failure reconnection trigger: When the system detects that a paired controlled device is offline, a reconnection prompt automatically pops up. After the user clicks the reconnection option, the selection operation for the offline device is triggered, used for re-pairing scenarios after device disconnection.

[0036] After completing user identity verification and permission level retrieval, the first-level permission screening process is initiated. Based on the device operation range rules corresponding to the user's permission level, all online controlled devices that have established communication connections with the host computer are traversed. The matching of the control zone, permission control level, and user permissions of each controlled device is verified one by one, eliminating controlled devices for which the user has no operation permissions, and filtering out the range of controlled devices for which the user has full operation permissions. Next, the second-level targeted screening process is initiated. Through the factory area positioning system, workstation binding ledger, and operation business type tags, the physical space information and current business usage scenario information of the user are collected. Based on preset space matching rules and scenario adaptation rules, a second filtering is performed on the range of operable devices after the first-level screening, eliminating controlled devices with mismatched spatial locations or unsuitable business scenarios. Finally, all remaining controlled devices after the second screening are integrated to generate a standardized device list, forming a pool of optional devices that perfectly matches user permissions, on-site environment, and business needs. This three-level progressive screening based on permissions, space, and scenario significantly narrows down the range of optional devices, fundamentally eliminating the risks of unauthorized user operations, misselection of devices across regions, and mispairing of devices that are not compatible with the scenario, thereby improving the accuracy and security of subsequent pairing and authorization operations.

[0037] Once the pairing control device receives the user's selection operation for the controlled device, it begins the process of filtering the connected controlled devices and determining the target controlled device.

[0038] For example, there are two methods for determining the target controlled device. The first is a device unique fingerprint full-dimensional matching locking method. After the selected operation is triggered, all the identity information of all connected controlled devices is read, including the device's unique hardware fingerprint, device name, device type, and access network information. Then, the device identification information corresponding to the user's selected operation is matched precisely with the identity information of all connected devices in a full-dimensional manner to lock the uniquely matching device, which is then determined as the target controlled device for this pairing. This method uses a full-dimensional device fingerprint matching locking logic. Through hardware-level unique identifier matching, it completely avoids the problem of misselecting devices with the same name, achieving extremely high matching accuracy and adapting to complex office and industrial scenarios where multiple devices of the same type are connected.

[0039] The second method is a scenario-based permission-based targeted filtering method. After a selected operation is triggered, the current user's device operation permission level is first read. Based on the permission level, the range of controllable devices that the user can operate is filtered out. Then, combined with the user's current physical space and usage scenario, the range of operable devices is further targeted to obtain a pool of optional devices. Finally, the pool of optional devices is matched with the device information corresponding to the user's selected operation to determine the target controllable device for this pairing. This method uses a two-dimensional targeted filtering logic of permissions and scenarios. It first narrows down the device range through permissions and scenarios, and then performs target matching, which greatly reduces the amount of invalid matching calculations, while ensuring the security of device operation permissions. It is suitable for commercial scenarios such as smart homes and multi-user hierarchical management.

[0040] After obtaining the device identifier corresponding to the user's selected operation and the full information of the connected controlled device, the device that matches it can be selected as the target controlled device based on the following methods.

[0041] In one alternative approach, the system first retrieves a pre-set list of controlled devices, extracts the unique identifier and basic information of each device in the list, and then compares the device identifier corresponding to the user's selected operation with the device identifiers in the list one by one to filter out the uniquely matching controlled device, which is then determined as the target controlled device for this pairing. This method relies on matching a pre-set device list with fixed identifiers to achieve selection, and its logic is intuitive, computationally intensive, and fast, making it suitable for typical home pairing scenarios with a small number of devices.

[0042] In another alternative approach, the user's selected operation is first analyzed from multiple dimensions to extract core features such as the selected device name, device type, physical location, and access time. Simultaneously, all connected controlled devices are analyzed hierarchically to extract their identity, permission level, online status, and core operational indicators related to the scenario. Based on the characteristics of the user's selected operation, suitable device filtering rules are generated. These rules are then used to filter all connected devices from multiple dimensions, generating a set of candidate devices that meet the requirements. A feasibility check is then performed on the candidate device set, verifying whether the device is online, whether the user has the necessary permissions, and whether the device supports the pairing process. All infeasible devices are eliminated, and the single compliant device remaining is the target controlled device for this pairing. This method can flexibly generate personalized filtering rules tailored to the user's current operation, offering richer filtering dimensions and higher matching accuracy. It fully ensures the security and accuracy of device operations and is suitable for complex intelligent scenarios involving multiple devices and multiple users.

[0043] In an exemplary scheme for identifying target controlled devices, a pre-set set of controlled access devices is first loaded. This set includes three basic types of devices: online devices, offline reconnectable devices, and newly connected devices awaiting pairing. Each device is pre-configured with a unique identifier, a permission matching matrix, and a scene affiliation tag. Then, a preliminary screening of basic permissions is performed, comparing the current user's operation permission level with the device's permission requirements and comparing the device's online status with a pre-set online threshold requirement, filtering out candidate devices that simultaneously meet both permission and online status requirements. Next, for online devices that pass the preliminary screening, the stability of the device's wireless access link and the proper activation of the device's pairing function are verified. For offline reconnectable devices that pass the preliminary screening, the offline duration is verified to be within the pre-set reconnection validity period, and the historical pairing records of the device are verified to match the current user. Next, a device identifier matching verification is performed. The device identifier corresponding to the user-selected operation is accurately matched with the unique identifier of the candidate device. Devices with mismatched identifiers are eliminated. Then, redundant devices are excluded. If there are multiple devices of the same type with partially matched identifiers, the one with the highest matching degree with the selected operation feature is retained, and the remaining redundant devices are eliminated. Finally, all devices that pass all the above verifications are determined as the target controlled devices for this pairing and are used for the generation of subsequent pairing authorization instructions.

[0044] It should be noted that in some special cases, if there is only one candidate device that matches the user's selected operation, the candidate device screening and verification process will be skipped, and it will be directly used as the target controlled device for this pairing.

[0045] Step S30: Based on the identity information and wireless reception parameters of the target controlled device, generate a pairing authorization command associated with the target controlled device.

[0046] Identity information is a set of hardware-level and system-level identifiers used to uniquely represent the identity of the target controlled device, and is the core basis for the targeted binding of pairing authorization commands. Examples include the device's MAC address, hardware serial number, unique identification code, manufacturer's serial number, Bluetooth chip address, and LAN IP address. Wireless reception parameters are the communication configuration parameters used by the target controlled device to receive wireless commands, and are the core foundation for ensuring that pairing authorization commands can be accurately received by the target device. Examples include the device's wireless communication frequency band, receiving port number, broadcast address, unicast communication address, communication protocol version, and data encryption public key. The pairing authorization command is an encrypted control command carrying the target device's identity verification information, pairing permission information, and state switching instructions; it is the core control carrier that triggers the target controlled device to switch to a pairable state. Examples include the device identity verification frame, pairing permission token, state switching control code, command validity parameters, and encrypted verification fields.

[0047] In this example, when generating pairing authorization instructions based on the identity information and wireless reception parameters of the target controlled device, the full parameter synchronization processing method provided in the first embodiment can be referred to. Alternatively, a streaming incremental dynamic generation method can be used, where the real-time status parameters of the target controlled device are read while the permission configuration and validity parameters of the instruction are updated synchronously to dynamically generate pairing authorization instructions adapted to the current status of the device, thereby completing the real-time generation of pairing authorization instructions.

[0048] After identifying the target controlled device, the pairing authorization command generation process is initiated. First, the identification information and wireless reception parameters of the target controlled device are extracted. Based on the extracted parameters, the command is targetedly bound and encrypted, generating a pairing authorization command uniquely associated with the target controlled device. By targeting the device parameters, the pairing authorization command can only be recognized and executed by the target device, avoiding accidental triggering by non-target devices and improving the targeting accuracy of pairing.

[0049] For example, there are two methods for generating pairing authorization commands. The first is a static encryption-based generation method with hardware identifier binding. After the command generation process officially starts, the unique hardware identity of the target controlled device is extracted, including the device MAC address, hardware serial number, and chip unique ID. The hardware identifier is used as the core verification field of the command. Then, based on the device's wireless receiving parameters, the communication protocol format and encryption method of the command are determined. The command content is asymmetrically encrypted using the device's public key. At the same time, a fixed pairing permission token and state switching control code are embedded in the command to generate a pairing authorization command uniquely bound to the hardware identifier of the target controlled device. This method uses a static encryption generation logic with hardware-level identifier binding. The command can only be decrypted and recognized by the device with the corresponding hardware identifier, avoiding the risk of accidental triggering and malicious cracking by non-target devices. The command generation logic is stable and reliable, with extremely high security, and is suitable for pairing scenarios with high security levels in industrial equipment and commercial applications.

[0050] The second method is a dynamic token generation method with time-limited permissions. After the command generation process officially starts, the identity information and wireless reception parameters of the target controlled device are extracted first. Then, based on the current system time, user permission level, and device pairing history, a one-time dynamic time-limited pairing token is generated. The validity period of this dynamic time-limited pairing token can be flexibly configured according to the scenario. At the same time, the device's real-time online status and wireless link quality parameters are embedded in the command, and the retransmission mechanism and control logic of the command are dynamically adjusted. Finally, a dynamic session key is used to encrypt the command, generating a pairing authorization command associated with the target controlled device with a single-use validity period. This method uses dynamic generation logic of dynamic time-limited tokens and session keys, does not rely on fixed encryption methods and permission tokens, and each generated command is valid only once, which can effectively prevent command replay attacks. At the same time, the command parameters can be dynamically adjusted according to the real-time status of the device, making it more adaptable and suitable for daily high-frequency pairing scenarios such as smart homes and mobile terminals.

[0051] After extracting the parameters of the target controlled device, a pairing authorization instruction can be generated based on the following method.

[0052] In one alternative approach, a pre-set set of fixed instruction templates is retrieved. This set stores standardized pairing authorization instruction templates adapted to different device types and communication protocols. Based on the device type and communication protocol version of the target controlled device, the corresponding pre-set instruction template is directly retrieved. The target device's identification information is filled into the template's verification field. The instruction format is encapsulated based on wireless reception parameters, and a pairing authorization instruction is directly generated for subsequent instruction transmission. This method is logically simple and stable, with unified and controllable instruction templates, enabling rapid generation of pairing authorization instructions, and is suitable for typical home pairing scenarios with high response speed requirements.

[0053] In another alternative approach, the identification information, wireless reception parameters, and real-time operating status of the target controlled device are first extracted. Simultaneously, the current user's operating permissions and pairing scenario type are extracted. Then, instruction generation rules optimized based on historical pairing tasks are retrieved from the rule base. Based on the target device's parameters and the user's permission scenario, an instruction structure, encryption method, and permission configuration adapted to this pairing task are dynamically generated. The compliance of the generated pairing authorization instruction is verified, confirming that the instruction format conforms to the device's communication protocol requirements and that the encryption method can be normally decrypted by the device. After verification, this is used as the pairing authorization instruction for this pairing. This method can flexibly generate customized pairing authorization instructions tailored to the current pairing task and device status, without relying on fixed preset templates. It offers higher adaptation accuracy, fully adapts to the communication requirements of different devices, improves instruction reception success rate and security, and adapts to pairing scenarios with multiple device types and complex network environments.

[0054] In an exemplary scheme for determining pairing authorization instructions, a pre-set set of instruction generation rules is first loaded. This set includes two basic templates: static encrypted instruction templates and dynamic token instruction templates. Each template is pre-configured with corresponding encryption rules, field configurations, and protocol adaptation parameters. Next, device parameter parsing is performed, standardizing the identification information, wireless receiving parameters, device type, and security level of the target controlled device to eliminate differences in parameter formats between different devices. Then, based on the security level of the target controlled device, a corresponding instruction generation template is selected. If the device is a high-security industrial / commercial device, a static encrypted instruction template is selected; if the device is a home smart device, a dynamic token instruction template is selected. Following this, instruction content is filled in, inserting the target device's identification information into the instruction's verification field, configuring the instruction's communication format and receiving address based on the wireless receiving parameters, and embedding the pairing status switching control code and authorization token. After content filling is complete, instruction encryption is performed, encrypting and encapsulating the instruction content based on the encryption rules corresponding to the selected template, and adding verification fields. Next, a command validity check is performed. This check verifies whether the command format conforms to the device's communication protocol requirements, whether the encryption method can be decrypted by the device, and whether the command's permission configuration is compliant. Abnormal command results are eliminated, redundant content is removed, and invalid fields in the command are simplified to ensure command transmission efficiency. Finally, the commands that pass the verification are determined as the final pairing authorization commands, which are used for subsequent command sending and device status triggering.

[0055] Step S40: Send the pairing authorization command to the target controlled device to trigger the target controlled device to switch to a pairable state.

[0056] The pairable state is the operational state in which the target controlled device is enabled, can be searched, discovered, and paired by the master control device, and is the target execution result triggered by the pairing authorization command. Examples include Bluetooth discoverable state, LAN pairing detection state, Wi-Fi hotspot pairing state, Zigbee networking pairing state, and NFC near-field pairing state. Sending the pairing authorization command is the process of transmitting the encrypted pairing authorization command to the target controlled device through a matched wireless communication link; it is the core step in triggering device state switching. Examples include wireless unicast transmission, directional broadcast transmission, near-field communication transmission, LAN multicast transmission, and Bluetooth Low Energy broadcast transmission.

[0057] In this embodiment, the pairing authorization command sending process can be triggered in six ways. First, automatic triggering after command generation: Once the pairing authorization command is generated and verified, the system automatically triggers the command sending process without additional user intervention, suitable for routine automated pairing scenarios. Second, user confirmation triggering: After the pairing authorization command is generated, the system displays a confirmation pop-up window; clicking the confirmation button triggers the command sending process, suitable for high-security device pairing scenarios. Third, device link detection triggering: When the system detects a stable wireless communication link with the target controlled device, it automatically triggers the command sending process, ensuring a high success rate for command transmission, suitable for pairing scenarios in complex network environments. Fourth, scheduled task triggering: The system automatically triggers the command sending process at specified times according to a preset scheduled pairing task, suitable for scheduled device maintenance pairing scenarios. Fifth, scenario linkage triggering: When the system executes a preset intelligent scenario startup task, it automatically triggers the corresponding device's pairing authorization command sending process, suitable for scenario-based batch device pairing scenarios. Sixth, device wake-up triggering: when the system wakes up the target controlled device through the low-power link, it automatically triggers the instruction sending process, which is used for pairing scenarios of low-power sleep devices.

[0058] After the pairing control device generates the pairing authorization command, it begins the command sending process. Through the wireless communication link matched with the target controlled device, the pairing authorization command is sent to the target controlled device. After receiving the command, the device completes identity verification and command decryption. After successful verification, it automatically switches to the pairable state, thereby realizing the remote directional triggering of the target device's pairing state.

[0059] For example, there are two ways to implement the sending and status triggering of pairing authorization commands. The first is the reliable transmission triggering method using a directional unicast link. After the sending process officially starts, a point-to-point reliable unicast communication link is established with the target device based on the wireless reception parameters of the target controlled device. The device's reception status is confirmed through a link handshake. Then, the pairing authorization command is reliably transmitted in packets through this unicast link. Each packet transmission awaits the device's confirmation response. After the full command transmission is completed, the device awaits the command verification response. After receiving the full command, the target controlled device first decrypts and verifies the command. After confirming that the command matches its own identity, it executes the status switching process, closes the default unpairable state, opens the pairable detection mode, and simultaneously returns a status switching success response to the master control device. This method uses the triggering logic of point-to-point reliable unicast transmission. Through a reliable transmission mechanism of handshake confirmation, packet transmission, and response verification, it ensures the success rate and directionality of command transmission. Only the target device can receive the complete command, avoiding the leakage risk and false triggering problem of broadcast transmission. It is suitable for pairing scenarios of industrial and commercial equipment with high security levels.

[0060] The second method is the encrypted broadcast frame-based targeted wake-up triggering method. After the transmission process officially starts, the core control content in the pairing authorization command is first bound and encapsulated with the target device's identity identifier to generate an encrypted broadcast frame that only the target device can recognize. Then, based on the target controlled device's wireless reception parameters, the encrypted broadcast frame is transmitted in the corresponding wireless frequency band, while simultaneously enabling a multi-cycle repetitive transmission mechanism to ensure that devices in a dormant state can be woken up and receive commands. When the target controlled device receives the broadcast frame in low-power detection mode, it first extracts the identity identifier information from the frame and matches it with its own identity identifier. Only when the identifiers match completely is the broadcast frame decrypted and the command parsed. After successful verification, it automatically wakes up from the dormant state and switches to a pairable state, while simultaneously returning a wake-up and state switch response to the master control device. This method uses an identity-bound encrypted broadcast frame-based targeted wake-up triggering logic, which can directly wake up low-power dormant devices and trigger state switching, exhibiting strong adaptability. Furthermore, through identity identifier pre-matching, non-target devices will not parse the command content, ensuring both the accuracy of targeted triggering and enabling rapid wake-up and pairing of low-power devices. It is suitable for battery-powered low-power smart devices and IoT terminal pairing scenarios.

[0061] Once the pairing authorization command is encapsulated, command sending and status triggering can be performed in the following manner.

[0062] In one alternative approach, a pre-set set of fixed communication link configurations is retrieved from the system. Based on the wireless reception parameters of the target controlled device, the corresponding communication link configuration is directly matched and retrieved. A communication link is established based on this configuration, and the pairing authorization command is sent directly to the target controlled device through this link, triggering the device to switch to a pairable state. This method features simple and stable logic, unified and controllable link configuration, fast transmission speed, and is suitable for common device pairing scenarios.

[0063] In another alternative approach, the wireless reception parameters, real-time online status, and link quality parameters of the target controlled device are first extracted, along with the current network environment and interference conditions. Then, link scheduling rules optimized based on historical transmission tasks are retrieved from the rule base to dynamically select the optimal communication link, transmission cycle, and retransmission mechanism. This generates a command transmission strategy adapted to the current environment. After verifying the feasibility of the strategy, pairing authorization commands are sent to the target controlled device according to this strategy, triggering the device to switch to a pairable state. This method can flexibly generate customized transmission strategies tailored to the current network environment and device status, achieving higher adaptation accuracy and ensuring a high success rate for command transmission in complex environments. It is suitable for IoT scenarios with complex network environments and multi-device interference.

[0064] In an exemplary scheme for executing command transmission and status triggering, a pre-set set of communication link configurations is first loaded. This set includes three basic links: unicast reliable transmission links, broadcast wake-up transmission links, and near-field communication transmission links. Each link is pre-configured with corresponding transmission parameters, retransmission mechanisms, and verification rules. Then, link adaptation is determined. Based on the target controlled device's wireless reception parameters, device type, power consumption mode, and current link quality, an appropriate communication link is selected. If the device is a high-security online device, a unicast reliable transmission link is selected; if the device is a low-power sleep device, a broadcast wake-up transmission link is selected; and if the device is a near-field contact device, a near-field communication transmission link is selected. Next, link establishment is performed. For the selected unicast link, a handshake interaction with the target device is completed to establish a point-to-point reliable communication link. For the selected broadcast link, the corresponding broadcast frequency band, transmission period, and repetition count are configured. For the selected near-field link, near-field communication detection is initiated, awaiting near-field sensing from the device. Next, the command is sent, encapsulating the pairing authorization command according to the transmission format of the selected link and sending it to the target controlled device through the established communication link. Simultaneously, a timeout retransmission mechanism is initiated; if no response is received from the device within a preset time, the command is retransmitted according to the retransmission mechanism. Then, device status verification is performed. Upon receiving a response from the target device, it is verified whether the device has successfully switched to a pairable state. If the device status switch fails, the pairing authorization command is regenerated and retransmitted; if the device status switch is successful, the transmission process is complete. Finally, the sent pairing authorization command completes the targeted triggering of the target controlled device's pairable state, providing the foundation for subsequent device pairing connections.

[0065] It should be noted that in some special cases, if the target controlled device fails to verify or fails to switch states after receiving the pairing authorization command, it will return a failure response to the master control device. After receiving the response, the master control device will automatically regenerate the pairing authorization command and send it a second time. If the sending fails three times in a row, the process will be terminated and a prompt will be sent to the user.

[0066] For example, please refer to Figure 2 , Figure 2This is the pairing flowchart for this application. In the remote control pairing scenario of a multi-camera production line environment, the process begins with step S101: the production line initiates the pairing process. Then, in step S102: the host computer sends a pairing authorization command to the designated USB camera. After the command is sent, two parallel process branches are executed simultaneously. The first branch proceeds through step S103: the receiving MCU receives the authorization command. Then, in step S104: the MCU outputs a control level to the 2.4G receiving chip. Next, in step S105: the receiving end enters a 10-second pairing window state. The second branch proceeds through step S106: the operator presses and holds the left and right buttons on the remote control for 3 seconds. In step S107: the remote control enters pairing mode, and the indicator light flashes. After completing the two parallel branches, step S108: it checks whether both parties are simultaneously in a pairing state. If the detection result is negative, it reverts to step S102 and re-initiates the pairing authorization process. If the detection result is positive, it proceeds sequentially through steps S109: performing ID exchange and binding, step S110: storing pairing information, and step S111: the indicator light stops flashing, finally ending the pairing process.

[0067] By responding to the user's selection of the controlled device, the target controlled device is identified, a corresponding pairing authorization command is generated and sent to trigger the switching of its pairable status. This solves the technical problem of low overall process efficiency, improves pairing accuracy, and achieves the effect of remote, targeted, and convenient pairing.

[0068] Second Embodiment This embodiment provides an exemplary scheme for securely generating device-specific pairing authorization commands. In this example, firstly, a unique pairing verification key adapted to the wireless communication specifications of the target controlled device is generated by matching the wireless receiving parameters reported by the target controlled device. Then, the identity information of the target controlled device, the pairing verification key, and the pairing operation parameters are encrypted and integrated to obtain initial authorization data. Finally, an anti-tampering verification code and a host computer identity signature are added to the initial authorization data to generate a pairing authorization command that is uniquely associated with the target controlled device and cannot be tampered with. Step S30 includes steps A11 to A13: Step A11: Based on the wireless receiving parameters of the target controlled device, a pairing verification key adapted to the wireless communication specifications of the target controlled device is obtained.

[0069] Step A12: Encrypt and integrate the identity information, pairing verification key, and pairing operation parameters of the target controlled device to obtain initial authorization data.

[0070] Step A13: Add an anti-tamper verification code and a host computer identity signature to the initial authorization data to generate a pairing authorization instruction associated with the target controlled device.

[0071] The pairing verification key is a unique key that is compatible with the wireless communication specifications of the target controlled device. It is used for bidirectional encryption and decryption of pairing signals and for verifying their legitimacy. It is the core security carrier that ensures the security of the pairing process and prevents unauthorized devices from parsing the response. Examples include symmetric encryption keys, asymmetric encryption public key strings, pairing signal verification encryption strings, device-specific identity verification keys, and dynamically valid encryption keys.

[0072] Pairing operation parameters are preset control parameters used to constrain the pairing process rules of the target controlled equipment. They are the core control basis for limiting the effective scope and timeliness of pairing permissions. Examples include pairing timing window duration parameters, pairing signal filtering thresholds, effective time limits for pairing permissions, pairing operation traceability codes, and hierarchical control rules for the pairing process.

[0073] A tamper-proof checksum is a verification identifier generated from the full content of the initial authorization data using an irreversible algorithm. It is used to verify data integrity and ensures that paired authorization instructions are not tampered with or forged during transmission. Examples include cyclic redundancy checksums, hash check values, irreversible full data check strings, tamper-proof digital digests, and integrity check identifiers.

[0074] A host computer identity signature is a digital signature generated by the host computer based on its administrator privileges and unique identity information. It is used to identify the legitimate source of authorized instructions, and only instructions with a legitimate signature can be recognized and responded to by the controlled device. Examples include administrator privilege digital signatures, host computer device unique identity signatures, authorized operation legitimate source identifiers, operation traceability signature strings, and approval process compliance signatures.

[0075] In this example, when generating a pairing verification key based on the wireless receiving parameters of the target controlled device, the method of retrieving pre-stored parameters provided in the first embodiment can be referred to. Alternatively, a parameter acquisition command can be sent to the communication link between the host computer and the target controlled device in real time to obtain the current operating parameters, hardware specifications, and real-time channel status of the target controlled device's wireless receiving module. Based on the real-time acquired parameters, an appropriate pairing verification key can be dynamically matched and generated, thereby completing the accurate matching and generation of the pairing verification key.

[0076] After the pairing verification key is adapted and generated, the initial authorization data encryption and integration process is initiated. This involves retrieving the unique identification information of the target controlled device, the pairing verification key, and the preset pairing operation parameters. A device-specific encryption algorithm is then used to fuse and encrypt these three types of data, resulting in initial authorization data with a unified format. Next, an anti-tamper verification code is generated based on the full content of the initial authorization data, and a legitimate signature from the host computer is added. Finally, a pairing authorization command uniquely associated with the target controlled device is generated. This layered encryption, end-to-end anti-tampering, and unique device binding generation logic enhances the security and uniqueness of the pairing authorization command, avoiding pairing security risks caused by unauthorized devices responding incorrectly or commands being tampered with or forged.

[0077] For example, there are two ways to generate pairing authorization instructions associated with a target controlled device through layered encryption. The first is single-device-specific static full-link encryption generation. For a single target controlled device selected by the user, the device's pre-stored and verified wireless receiving parameters and unique identification information are retrieved. Based on the device's supported wireless encryption algorithm types and encoding formats, a static pairing verification key uniquely compatible with the device's hardware specifications is generated. Then, the device's unique identification information, exclusive pairing verification key, and preset fixed pairing operation parameters are fully fused and encrypted using the device's exclusive symmetric encryption algorithm to generate initial authorization data uniquely bound to the device. Based on the full content of the initial authorization data, an anti-tampering verification code is generated using an irreversible hash algorithm. At the same time, the host computer administrator's identity signature and operation traceability code corresponding to this operation are added, finally generating an exclusive pairing authorization instruction that can only be parsed and responded to by the target controlled device, and is tamper-proof and untamperable. This method employs a generation logic of one-to-one exclusive encryption for each device and static binding across the entire link. Through key matching and multi-layer encryption that are deeply adapted to the device hardware specifications, it eliminates the risk of pairing authorization commands being parsed, stolen, or tampered with by other devices. The authorization accuracy and security level are extremely high, making it suitable for high-security pairing scenarios after the replacement of remote controls for a single device in an industrial production line or after fault repair.

[0078] The second method involves batch grouping and dynamic hierarchical encryption generation. For multiple target controlled devices within the same partition of a user-selected production line, the devices are first divided into multiple independent pairing groups based on deployment partitions, production line workstations, and wireless interference levels. Each group is configured with independent hierarchical control rules and timing parameters. Then, for all controlled devices within each group, wireless reception parameters, identification information, and real-time channel status are simultaneously collected. Based on the group control rules and the hardware specifications of each device, a unique dynamic pairing verification key with timing control is generated for each device within the group. Next, the device's identification information, corresponding dynamic pairing verification key, and group hierarchical pairing operation parameters are batch-fused and encrypted by group, generating initial authorization data specific to each device. Then, for each device's initial authorization data, a unified anti-tampering verification code and a device-specific sub-verification identifier are generated for the group. Simultaneously, a batch operation identity signature from the host computer, a group authorization identifier, and an operation traceability code are added. Finally, a batch pairing authorization instruction with group control attributes and uniquely associated with each device is generated. This method adopts a generation logic of dynamic hierarchical grouping and batch adaptation encryption. Through pre-grouping control and dynamic key matching, it not only ensures the uniqueness of authorization for a single device, but also realizes the batch authorization generation and distribution of multiple devices on the production line. At the same time, hierarchical timing control avoids signal interference and authorization conflicts when pairing multiple devices, improving the operational efficiency and control security of batch pairing on the production line. It is suitable for large-scale pairing scenarios such as new production line commissioning and batch operation and maintenance of the entire line of equipment.

[0079] Third Embodiment This embodiment provides an exemplary scheme for closed-loop management and adaptive parameter optimization of pairing results. In this example, the pairing result information returned by the target controlled device and remote controller after pairing is completed is received first, and the pairing result information is associated and archived with the current pairing operation. Then, the pairing result information is compared and analyzed from multiple dimensions according to the pairing process optimization rules to accurately locate the parameter adjustment space in the pairing process. Next, based on the parameter adjustment space, combined with the deployment environment and operating status of the controlled device and the parameter information of the remote controller, a pairing optimization parameter set that is precisely adapted to the corresponding controlled device and remote controller is generated. Finally, the pairing optimization parameter set is sent to the corresponding controlled device and remote controller, completing the iterative update of the device pairing operation parameters and realizing continuous self-optimization and scene adaptive adaptation of the pairing mechanism. After step S40, steps B11~B14 are also included: Step B11: Receive the pairing result information returned by the target controlled device and the remote controller after pairing is completed, and archive the pairing result information with this pairing.

[0080] Step B12: Compare and analyze the pairing result information according to the pairing process optimization rules to determine the parameter adjustment space in the pairing process.

[0081] Step B13: Based on the parameter adjustment space, combined with the deployment environment and operating status of the controlled device, and the parameter information of the remote controller, generate a pairing optimization parameter set adapted to the controlled device and the remote controller.

[0082] Step B14: Send the pairing optimization parameter set to the corresponding controlled device and the remote controller to complete the parameter update of the controlled device and the remote controller.

[0083] Pairing result information is a set of bidirectional aggregated pairing process data generated after the target controlled device and the remote control have completed pairing and binding. It is the core foundational data source for evaluating pairing effectiveness and optimizing parameters. Examples include the actual runtime of the pairing window, wireless signal communication quality, total identity verification time, pairing success identifier, abnormal interference records, device interaction latency, wireless module operating load data, and a unique traceability code for the pairing operation.

[0084] The pairing process optimization rules are standardized analysis and judgment criteria pre-configured by the host computer and trained on massive historical pairing samples. They are used to quantitatively evaluate the rationality, operational adaptability, and optimization potential of the parameters throughout the pairing process. Examples include pairing window duration adaptation rules, wireless signal transmission power adjustment rules, identity verification delay control rules, signal filtering threshold matching rules, multi-device interference avoidance rules, and hardware load security management rules.

[0085] The parameter adjustment space is determined through multi-dimensional comparative analysis, identifying optimizable parameter dimensions and safe, reasonable adjustment ranges. It covers optimizable operational indicators across the entire pairing process. Examples include adjustment space for pairing timing window duration, wireless transmission power, signal filtering threshold, identity verification encryption level, pairing request broadcast cycle speed, and pairing timeout countdown correction.

[0086] The deployment environment refers to the external environmental characteristics corresponding to the on-site installation and deployment of the target controlled equipment. It is a core environmental factor that constrains the optimization boundary of pairing parameters and affects the quality of wireless communication. For example, the density of equipment deployment, the interference intensity of 2.4G wireless channels, the electromagnetic radiation level of the workstation, the physical obstruction conditions in space, the partitioned network topology, the real-time occupancy of on-site channels, and the environmental fluctuation patterns during production line operation.

[0087] Operational status refers to real-time hardware load and module health data of the target controlled device. It is used to limit the hardware capacity limit for parameter optimization and ensure the safe and stable operation of the optimized parameters. For example, it includes data such as the real-time load rate of the wireless receiving module, the operating frequency of the microcontroller unit, the timing accuracy of the hardware timer, the module temperature rise status, the real-time occupancy rate of the communication interface, the degree of aging of the device after long-term operation, and the stability of the power supply.

[0088] The remote control's parameter information is a collection of its inherent hardware configuration and user-defined operating parameters, determining the remote control's pairing capabilities and optimization limits. Examples include the rated power range of the wireless transmitter module, the sensitivity of combination button triggers, the flashing frequency rules of indicator lights, the pairing signal encoding format, the adjustable range of the broadcast transmission cycle, the accuracy of the built-in timing module, and the hardware version and performance level.

[0089] The pairing optimization parameter set is a customized set of combined configurations containing multiple adjustable operating parameters, generated bidirectionally for both the controlled device and the remote controller. This set is used to achieve collaborative optimization and scenario adaptation of the pairing operation mechanism at both ends. Examples include: controlled device pairing window optimization duration, dynamic signal filtering threshold, identity verification encryption level, remote controller wireless transmission adaptive power, pairing request broadcast interval, timeout countdown correction parameters, and automatic interference channel avoidance rules.

[0090] In this example, when receiving pairing result information and completing the associated archiving of this pairing, the method of single-device dedicated data reporting can be followed. Alternatively, a batch group summary reporting method can be used, with the target controlled device acting as a data relay node. After pairing is completed, it actively retrieves the pairing operation data from the remote control side, integrates its own device's entire pairing process record, generates unified pairing result information, and then encrypts and uploads it to the host computer. Upon receiving the information, the host computer extracts the globally unique operation code for this pairing, completes the bidirectional data association matching and archiving storage, thereby completing the full collection and standardized management of pairing result information.

[0091] After the pairing results are associated and archived, the comparison and analysis process of the pairing process is initiated. Pre-set pairing optimization rules are retrieved, and multi-dimensional core operational indicators from the archived pairing results are broken down and compared with standard parameter thresholds, historical best data for the same scenario, and historical operational data for a single device. Parameters with operational redundancy, insufficient adaptability, and weak anti-interference capabilities are identified, and a safe adjustment range for each optimizable parameter is defined, summarizing to form the parameter adjustment space for this pairing. Next, based on the parameter adjustment space, real-time deployment environment detection data and hardware operation status data of the target controlled device are retrieved simultaneously, along with the hardware parameter information and performance boundaries of the bound remote controller. This completes the fusion and matching of multi-dimensional constraints, generating a pairing optimization parameter set that precisely adapts to the hardware capabilities, on-site environment, and operational status of both devices. Finally, through a dedicated communication link established with the controlled device and remote controller, the pairing optimization parameter set is distributed to the corresponding devices, completing the secure update and iteration of the pairing operation parameters for both devices. This closed-loop management of the pairing results enables continuous self-optimization of the pairing mechanism, constantly improving the scenario adaptability, anti-interference capability, and operational stability of the pairing solution.

[0092] For example, there are two ways to achieve adaptive optimization of device parameters through closed-loop management of pairing results. The first is a time-locked, full-process closed-loop precise optimization for a single device. After the pairing process is completed, the host computer receives the pairing result information transmitted bidirectionally from the target controlled device and the remote controller. Using the globally unique traceability code of this pairing operation as the core index, the association matching and standardized archiving of the data at both ends are completed. Subsequently, according to the pairing process optimization rules, the entire pairing process is divided into five independent time-series stages: authorization issuance, window opening, signal detection, identity interaction, and binding solidification. The corresponding operating parameters are broken down for each stage and compared with the device's preset standard optimal parameter thresholds and historical optimal pairing data time-series. The parameter shortcomings and optimization potential of each stage are identified, and the safe adjustment space for each parameter is defined. Then, combined with the device's dedicated deployment environment, real-time hardware operating status, and remote controller hardware performance boundaries, the optimal adaptation value is calculated for each optimizable parameter, forming a single-device-specific pairing optimization parameter set. Finally, optimized parameter sets are sent to the controlled device and remote controller via a USB wired link and a wireless point-to-point channel, respectively. After receiving the parameters, the device performs validity verification and hot updates, completing parameter iteration without interrupting the device's regular operations. This method employs a time-locked, phased decomposition, step-by-step benchmarking, and device-specific customized optimization logic to fully restore the operational details of the entire pairing process. The parameter optimization is highly accurate and adaptable, enabling targeted optimization of operational shortcomings of individual devices and meeting the precise optimization needs of special workstation equipment in industrial production lines and equipment after fault repair.

[0093] The second approach involves batch parallel clustering and hierarchical optimization of devices within partitioned groups. For devices that have completed batch pairing within the same deployment partition and wireless environment on the production line, the host computer receives pairing result information from all controlled devices and remote controllers within the partition. It then categorizes and archives the batch data according to device deployment partitions and workstation groups. Following pairing process optimization rules, the batch pairing result data undergoes multi-dimensional feature decomposition, extracting core features such as device deployment environment, hardware level, pairing operation efficiency, and anti-interference capability. Clustering is then performed on the pairing operation data of all devices, dividing them into device clusters with different performance levels. For each device cluster, horizontal benchmarking analysis and vertical review analysis are conducted simultaneously to identify common parameter shortcomings and optimization opportunities. Combining the unified environmental characteristics of the partition and the cluster hardware performance level, a hierarchical pairing optimization parameter set is generated, combining general cluster optimization parameters with individual device-specific adaptation parameters. Finally, according to production line operation and maintenance rules, general optimization parameters are distributed in batches via multicast during low-load periods, and individual device-specific adaptation parameters are distributed via point-to-point links, completing the parameter updates and iterations for all devices within the partition in batches. This method employs a logic of partitioned grouping and clustering, batch parallel analysis, and hierarchical adaptation optimization, which can simultaneously complete the pairing optimization of dozens or even hundreds of devices on the production line, significantly reducing the workload of large-scale operation and maintenance of the production line. At the same time, by combining cluster common optimization with individual device differentiated adaptation, it balances optimization efficiency and individual device adaptation accuracy, perfectly adapting to large-scale industrial scenarios such as new production line commissioning and batch operation and maintenance of the entire line of equipment.

[0094] Fourth embodiment This application provides a method for pairing a remote control, referring to... Figure 3 , Figure 3 This is a flowchart illustrating the fourth embodiment of the pairing method for the remote control of this application.

[0095] In this embodiment, the pairing method for the remote control includes steps C11 to C14: Step C11: In response to the pairing authorization command issued by the host computer, start the pairing timer window of the target controlled device and switch the target controlled device to the pairable state.

[0096] In this embodiment, the activation of the pairing timing window and the switching of the pairable state can be triggered in six ways. First, immediate authorization verification triggering: After receiving the pairing authorization command from the host computer, the target controlled device immediately completes the verification of the command's legality and identity consistency. Upon successful verification, the pairing timing window is immediately activated, and the device state is switched synchronously. This is used for remote control pairing scenarios involving a single device. Second, batch grouping time-sequential triggering: After receiving the group pairing authorization command from the host computer, the target controlled device activates the pairing timing window and switches states at specified time nodes according to the preset time intervals within the command. This is used for batch pairing scenarios involving multiple devices on a production line, avoiding signal interference caused by simultaneous pairing of multiple devices. Third, automatic fault reset triggering: When the target controlled device detects a loss of remote control binding or a wireless module fault reset, it automatically initiates a pairing authorization request to the host computer. Upon receiving the pairing authorization command from the host computer, it automatically activates the pairing timing window and switches states. This is used for automatic re-pairing scenarios after device fault repair. Fourth, scheduled maintenance cycle triggering: Following preset production line maintenance cycle rules, the system automatically sends pairing authorization commands to the target controlled equipment during designated maintenance periods via the host computer. Upon receiving the command, the equipment automatically starts the pairing timer window and switches its state. This is used for maintenance scenarios involving regular inspections of production line equipment and batch replacement of remote controls. Fifth, manual on-site triggering: Operators initiate pairing requests via the local maintenance trigger button on the target controlled equipment. Upon receiving the request, the host computer issues a pairing authorization command. Upon receiving the command, the equipment starts the pairing timer window and switches its state. This is used for on-site emergency pairing scenarios where operators lack remote operation permissions from the host computer. Sixth, remote maintenance backend triggering: Maintenance personnel initiate pairing commands to the host computer via the remote maintenance platform. After verifying the maintenance personnel's permissions, the host computer issues a pairing authorization command to the designated target controlled equipment. Upon receiving the command, the equipment starts the pairing timer window and switches its state. This is used for remote maintenance pairing scenarios involving production line equipment across different factory areas and distances.

[0097] Once the target controlled device receives the pairing authorization command, it begins to perform the verification of the legality of the pairing authorization command and the preparatory work for the pairing process.

[0098] For example, the verification and pre-pairing preparation of the pairing authorization command can be implemented in two ways. The first is a full-scale hardware verification instant trigger mode. After receiving the pairing authorization command, the target controlled device performs a full verification of the command through a hardware security chip, sequentially verifying the host computer's identity signature, anti-tampering verification code, device identity identifier matching, and authorization validity. After all verification items pass, the pairing function permission is unlocked, the hardware timer is initialized, and the pairing signal filtering rules of the wireless receiving module are configured, completing all pre-pairing preparations. This method uses hardware-level full-dimensional verification, the verification logic is tamper-proof, and the security level is extremely high, completely eliminating the risk of illegal commands triggering pairing. It is suitable for pairing scenarios of core equipment in industrial production lines with stringent security requirements. The second is a hierarchical soft verification step-by-step ready mode. After receiving the pairing authorization command, the target controlled device first performs a first-level basic format verification, verifying whether the command's frame format and cyclic redundancy check code are compliant. After the format verification passes, it enters the pre-ready state and sends a command reception receipt to the host computer. The second level of identity and permission verification is then performed, validating the device's identity identifier and the host computer's authorization signature. Upon successful verification, the device enters a standby state and configures the basic operating parameters of the wireless receiver module. After receiving the final startup confirmation command from the host computer, the hardware timer is initialized to initiate the pairing timing window, completing the final switch to the pairable state. This method employs a hierarchical, step-by-step verification and readiness mechanism, which can filter invalid and illegal commands in advance, reducing device operating costs. It also supports precise control of the pairing startup timing by the host computer, adapting to time-sequential management scenarios for batch pairing of multiple devices.

[0099] After completing the verification and preparatory work for the pairing authorization command, the pairing timer window can be started and switched to the pairing-ready state in the following ways.

[0100] In one alternative approach, the system first retrieves pre-set standardized pairing operation parameters, extracting the fixed pairing window duration, wireless signal filtering rules, and status indication control rules. Then, based on these pre-set parameters, a hardware timer is initialized, starting the fixed-duration pairing timing window. Simultaneously, the operating mode of the wireless receiving module is configured according to pre-set rules, the regular control command response channel is closed, and the dedicated identification channel for pairing request signals is opened, switching the device to a standardized pairable state. This method relies on pre-set fixed parameters to achieve state switching, offering intuitive logic, stable operation, and fast execution speed, making it suitable for conventional standardized device pairing scenarios.

[0101] In another alternative approach, the received pairing authorization command is first parsed to extract the pairing window duration, hierarchical control rules, channel configuration parameters, and interference avoidance rules carried within the command. Simultaneously, the current hardware operating status of the device and real-time wireless channel interference data are collected. Based on the parsed command parameters and the real-time device status data, the pairing timing window duration, the signal filtering threshold of the wireless receiving module, and the channel detection rules are dynamically adjusted. A hardware timer is initialized to start a pairing timing window adapted to the current scenario, and the dynamic configuration of the wireless receiving module is completed, switching the device to a scenario-adaptive pairable state. This method can flexibly generate personalized pairing configurations that fit the current command requirements, device status, and field environment, offering higher adaptation accuracy, stronger anti-interference capabilities, and fully adapting to the differentiated pairing needs in complex industrial environments.

[0102] In an exemplary scheme for determining the start and state switching of the pairing timing window, a pre-set set of pairing authorization command verification rules for the target controlled device is first loaded. This set includes four categories of basic rules: basic format verification rules, device identity matching rules, host computer signature verification rules, and authorization validity verification rules. Each rule is pre-configured with a corresponding verification threshold and anomaly handling mechanism. Then, a full verification of the commands is performed. First, the basic frame format and cyclic redundancy check code of the pairing authorization command are verified, filtering out invalid commands with abnormal formats. Next, the device identity identifier carried in the command is verified to ensure it completely matches the unique identity identifier stored locally on the device, filtering out cross-device commands from non-designated devices. Then, the host computer identity signature and anti-tampering check code in the command are verified to confirm that the command has not been tampered with and its source is legitimate. Finally, the authorization validity of the command is verified to ensure it is within the valid range, eliminating expired or invalid authorization commands. After completing the full verification, pairing pre-preparation is performed, initializing the hardware timer, configuring the pairing signal filtering rules of the wireless receiving module, locking the dedicated pairing communication channel, and setting the pairing prompt rules for the status indicator component. Subsequently, the pairing timer window is started and the status is switched. The pairing timer window is started based on the preset or command-specified duration parameters. At the same time, the wireless receiving module is switched to the pairing request dedicated response mode, the parsing and response channel of the regular control command is closed, the control status indicator is switched to the pairing process prompt status, and at the same time, feedback information is sent to the host computer that the pairing window has been opened and the device has entered the pairing state.

[0103] It should be noted that in some special cases, if the target controlled device detects strong interference in the wireless channel or an abnormal situation where the device hardware load exceeds the threshold before the pairing timing window is started, it will automatically send an abnormal alarm message to the host computer, delay the start of the pairing timing window, and perform the state switch after the abnormal situation is eliminated.

[0104] Step C12: Within the effective duration of the pairing time window, extract the parsed data of the remote control identity identifier, pairing verification key, device type matching identifier, and group affiliation identifier contained in the candidate signal, and retrieve the authorization control rules in the current pairing authorization instruction. The candidate signal is the signal sent by the target controlled device in the pairable state.

[0105] Step C13: Perform a full-dimensional match between the parsed data of the candidate signals and the authorization control rules for this pairing, filter out the signals that meet the authorization requirements for this pairing, and determine them as the pairing request signals for this pairing.

[0106] The remote control identification identifier is a unique encrypted code embedded in the candidate signal, used to uniquely identify the hardware identity of the remote control initiating the signal. It is the core foundation for verifying the legitimacy of the remote control. Examples include the remote control's unique hardware serial number encrypted string, the remote control's factory-installed MAC address identifier, the remote control's globally unique device ID, and the identification code within the remote control's hardware security chip. The pairing verification key is encrypted verification data carried in the candidate signal that uniquely matches the pairing authorization command of the target controlled device. It is the core security carrier for verifying the legitimacy of the pairing request authorization. Examples include the symmetric encryption key agreed upon in the pairing authorization command, the verification key pre-shared between the remote control and the controlled device, the dynamic session key specific to this pairing, and the one-time verification key with time-limited control. The device type matching identifier is an identifier carried in the candidate signal, used to identify the type and model specifications of the controlled device to which the remote control is compatible. It is used to filter remote control signals from incompatible models and avoid mis-pairing across models. Examples include a USB camera-specific adaptation identifier, an industrial equipment remote control model matching code, a device category-specific pairing identifier, and a universal pairing identifier for devices of the same model.

[0107] Group affiliation identifiers are the affiliation codes carried within candidate signals, used to identify the production line partition, business group, and workstation cluster to which the remote control belongs. This is used to implement pairing permission control for partitioned groups, avoiding cross-partition crosstalk pairing. Examples include production line physical partition affiliation codes, business function group identifiers, workstation cluster binding codes, and maintenance-specific group matching identifiers. Parsed data is a structured dataset extracted after the target controlled device fully decrypts and parses the candidate signal, containing remote control identity identifiers, pairing verification keys, device type matching identifiers, and group affiliation identifiers. This is the core comparison object for matching and verifying with authorization control rules. Examples include a candidate signal full-field parsing structured dataset, a remote control pairing core information decryption dataset, a multi-dimensional matching verification basic dataset, and an authorization compliance comparison core parameter set. Authorization control rules are a set of full-dimensional control rules embedded in the pairing authorization instruction, used to define the legal scope of this pairing. This is the sole criterion for verifying the legality of candidate signals and filtering pairing request signals. Examples include remote control identity whitelist rules, device type adaptation rules, group affiliation matching rules, pairing verification key verification rules, and pairing timeliness control rules.

[0108] In this embodiment, the detection and reception of pairing request signals can be initiated in six ways. First, fixed-slot cyclic detection: After the target controlled device enters the pairable state, the effective duration of the pairing timing window is divided into multiple equal-length fixed detection slots. Full-power signal reception is enabled within each slot, and a low-power standby state is entered between slots. This cycle repeats until the pairing timing window reaches zero, suitable for pairing scenarios of low-power controlled devices powered by batteries. Second, continuous detection throughout the entire time frame: After the target controlled device enters the pairable state, the full-channel scanning and signal reception function of the wireless receiving module is continuously enabled throughout the entire effective duration of the pairing timing window, collecting all radio frequency signals within the wireless channel in real time. This is suitable for pairing scenarios of industrial production line equipment with high pairing response speed requirements. Third, interference-adaptive frequency hopping detection: After the target controlled device enters the pairable state, interference scanning is first performed on the entire frequency band wireless channel, marking strong interference channels. Within the effective duration of the pairing timing window, detection is only performed cyclically within clean channels with no or low interference, receiving pairing request signals in real time. This is suitable for pairing scenarios of industrial production lines with complex wireless environments and severe interference. Fourth, dedicated group channel detection: After the target controlled device enters the pairing-ready state, it locks onto the dedicated pairing channel based on its own production line group identifier. Within the effective duration of the pairing time window, it only detects the wireless signal within this dedicated channel, filtering out all signals from other channels. This is used in batch pairing scenarios with densely deployed multiple devices on production lines to avoid cross-group signal interference. Fifth, signal strength threshold triggered detection: After the target controlled device enters the pairing-ready state, within the effective duration of the pairing time window, it first continuously detects the signal strength of the wireless channel in low-power mode. Only when the detected signal strength reaches the preset near-distance pairing threshold will it activate full-power signal reception and parsing. This is used to avoid mis-pairing scenarios of distant, nearby devices. Sixth, host computer command controlled detection: After the target controlled device enters the pairing-ready state, within the effective duration of the pairing time window, it only activates the wireless signal reception function when it receives a detection start command from the host computer. When it receives a detection stop command from the host computer, it pauses signal reception. This is used in scenarios where the host computer can accurately control the entire pairing process.

[0109] Once the target controlled device enters the pairable state, the wireless channel scanning and pairing request signal acquisition and screening process is initiated.

[0110] For example, there are two ways to acquire and filter the pairing request signal. The first is a step-by-step filtering precision acquisition mode. Within the effective duration of the pairing timing window, the target controlled device continuously acquires all radio frequency signals in the wireless channel. First, it performs the first-level physical layer filtering to filter out excessively strong / weak signals whose signal strength exceeds a preset reasonable range. Then, it performs the second-level format layer filtering to filter out invalid interference signals whose frame format and encoding rules do not conform to the pairing signal specifications. Finally, it performs the third-level data layer filtering to filter out non-pairing service signals that do not carry a valid pairing identifier. Finally, it retains candidate signals that fully conform to the filtering rules and parses them to obtain the pairing request signal broadcast by the remote control. This method adopts a three-level step-by-step filtering logic of physical layer, format layer, and data layer, narrowing the signal range layer by layer. It has high filtering accuracy, can eliminate various invalid interference signals, reduces the parsing overhead of invalid signals, and is suitable for complex industrial scenarios with severe wireless interference. The second method is a multi-dimensional feature clustering intelligent recognition mode. Within the effective duration of the pairing timing window, the target controlled device collects all radio frequency signals within the wireless channel. Each collected signal undergoes multi-dimensional feature decomposition, extracting its encoding format features, timing features, frequency features, identification features, and signal strength fluctuation features to generate a multi-dimensional feature dataset for each signal. Then, based on a pre-trained pairing signal recognition model, clustering analysis is performed on the feature datasets of all signals to automatically distinguish between legitimate pairing request signals, industrial interference signals, and other device service signals, accurately identifying and extracting the pairing request signal broadcast by the remote control. This method employs AI feature clustering intelligent recognition logic, which can autonomously learn the characteristics of interference signals in different scenarios and adaptively optimize recognition rules. Even in complex environments with strong interference and overlapping signals, it can accurately capture legitimate pairing request signals, adapting to high-end industrial production line scenarios with ultra-dense deployment of multiple devices and complex electromagnetic environments.

[0111] Once the radio frequency signals within the wireless channel are acquired and preliminary screening is completed, a legitimate pairing request signal can be identified and received based on the following methods.

[0112] In one alternative approach, the system first retrieves preset fixed pairing signal verification rules, extracting signal format verification thresholds, identity matching rules, and verification key verification rules. Then, the initially filtered candidate signals are compared item by item with the preset verification rules to filter out all signals that meet the rules, identifying them as legitimate pairing request signals, thus completing signal reception and parsing. This method relies on preset fixed verification rules for signal filtering, featuring simple and stable logic, fast execution speed, and adaptability to conventional and standardized pairing scenarios.

[0113] In another alternative approach, the candidate signals after initial screening are first fully parsed to extract the remote control identifier, pairing verification key, device type matching identifier, and group affiliation identifier. Simultaneously, the authorization control rules within the current pairing authorization command, including the authorization scope, group control rules, and device matching requirements, are retrieved. Then, the parsed data of the candidate signals is matched against the authorization control rules for this pairing across all dimensions. Signals that fully meet the authorization requirements are selected and identified as legitimate pairing request signals, thus completing signal reception and parsing. This method can combine the specific authorization rules for this pairing for dynamic matching and filtering, accepting only pairing request signals that conform to the authorization scope, eliminating the risk of mispairing or unauthorized pairing by other remote controls, and is suitable for high-security, dedicated pairing scenarios.

[0114] In an exemplary scheme for determining the reception of a pairing request signal, a pre-set set of pairing signal detection and verification rules for the target controlled device is first loaded. This set includes five basic rule categories: channel detection rules, signal strength filtering rules, format verification rules, identity matching rules, and authorization verification rules. Each rule is pre-configured with corresponding thresholds and filtering logic. Then, channel detection configuration is executed. Based on the authorization requirements of this pairing and the on-site wireless environment, a dedicated pairing detection channel is locked, the detection mode and signal reception parameters of the wireless receiving module are configured, and continuous signal acquisition within the effective duration of the pairing time window is initiated. Next, signal filtering is performed step-by-step. First, signal strength filtering is performed on all acquired radio frequency signals, eliminating invalid signals with signal strengths below the near-range pairing threshold or above the strong interference threshold. Then, format compliance verification is performed on the remaining signals, verifying the preamble, data frame format, and cyclic redundancy check code, filtering out interference signals with mismatched formats. Finally, pairing identifier verification is performed on the remaining signals, selecting candidate signals carrying valid pairing identifiers. Next, signal legitimacy verification is performed. The remote control identifier, pairing verification key, and group affiliation information within the candidate signal are parsed and compared item by item with the authorization scope and device matching requirements in the current pairing authorization command to confirm the legitimacy and authorization matching of the signal. Finally, the verified signal is determined as a legitimate pairing request signal, and full signal parsing and caching are completed. At the same time, unnecessary channel scanning and signal filtering processes are paused, focusing on pairing interaction with the corresponding remote control until the pairing process is completed or the pairing timer window reaches zero.

[0115] It should be noted that in some special cases, if the target controlled device receives multiple pairing request signals that meet the verification rules within the effective duration of the pairing time window, it will immediately send a multi-signal conflict alarm to the host computer, and at the same time suspend the pairing process, filter all pairing request signals, until the pairing time window returns to zero, so as to avoid one-to-many misbinding.

[0116] Step C14: The remote control corresponding to the pairing request signal is bidirectionally linked to the target controlled device.

[0117] In this embodiment, bidirectional interactive binding between the target controlled device and the remote controller can be achieved in six ways. First, symmetric encryption bidirectional verification binding: the target controlled device and the remote controller use a pre-agreed symmetric encryption key to encrypt and transmit their own identity information. After receiving the encrypted information, both parties use the same key to decrypt and verify. Once verification is successful, pairing and binding are completed. This is used for rapid pairing scenarios of conventional standardized devices. Second, asymmetric encryption identity signature binding: the target controlled device and the remote controller each generate their own public-private key pairs, exchange public keys, and complete identity signature verification. Based on the digital signatures of both parties, mutual identity recognition is achieved before pairing and binding are performed. This is used for pairing scenarios of core devices with extremely high security requirements. Third, dynamic key real-time negotiation binding: during the pairing interaction process, the target controlled device and the remote controller negotiate and generate a dynamic session key specific to this pairing in real time based on a random number algorithm. Bidirectional encrypted transmission and verification of identity information are completed based on the dynamic key. Once verification is successful, pairing and binding are completed. This eliminates the risk of pairing signals being intercepted and cracked, and is used for pairing in high-security industrial scenarios. Fourth, hard binding of unique device identifiers: The target controlled device exchanges its unique hardware serial number bidirectionally with the remote controller's unique hardware serial number, writing the remote controller's hardware serial number into the one-time programmable storage area of ​​the hardware security chip, completing an immutable hardware-level hard binding. This is used for scenarios where the device and remote controller are permanently paired. Fifth, hierarchical binding of group permissions: Based on the production line's group control rules, the target controlled device and remote controller complete bidirectional group permission verification. After confirming that the remote controller's group operation permissions match the device's group affiliation, the corresponding permission level pairing and binding are completed. This is used for hierarchical control scenarios with multiple zones and multiple permission levels on the production line. Sixth, end-to-end binding of operation and maintenance traceability: While completing bidirectional identity verification, the target controlled device and remote controller simultaneously exchange the operation traceability code, operation and maintenance personnel information, and pairing timestamp for this pairing. The end-to-end traceability information and pairing binding relationship are stored bidirectionally and synchronously. This is used for operation and maintenance control scenarios where the entire process of an industrial production line is traceable.

[0118] Once the target controlled device receives a pairing request signal that has passed verification, it initiates the entire two-way interactive binding process with the corresponding remote controller.

[0119] For example, there are two ways to implement the two-way interactive binding between the target controlled device and the remote controller. The first is a full-link encrypted two-way identity verification binding mode. The target controlled device parses the verified pairing request signal, extracts the remote controller's unique identifier and public key information, generates a pairing confirmation signal carrying its own unique identifier, pairing authorization information, and public key information, encrypts the pairing confirmation signal using the remote controller's public key, and sends it point-to-point to the corresponding remote controller. After receiving the encrypted pairing confirmation signal, the remote controller decrypts it using its own private key, completes the identity verification of the target controlled device, and then generates a response signal carrying its own identity signature and pairing confirmation receipt, encrypts it using the target controlled device's public key, and sends it back. After receiving the response signal, the target controlled device decrypts and verifies it, confirming that the remote controller's identity signature is legal and valid, completing the two-way identity verification. Subsequently, both parties write each other's unique identifier, pairing key, and permission information to local non-volatile storage to solidify them, establishing a one-to-one exclusive control relationship and completing the two-way interactive binding. This method employs asymmetric encryption for end-to-end encrypted transmission and two-way identity signature verification. All interactive data during the pairing process is encrypted and cannot be intercepted or cracked. Simultaneously, the two-way identity signature ensures the legitimacy of both parties' identities, eliminating security risks such as unauthorized device access, man-in-the-middle attacks, and misbinding. It boasts an extremely high security level and is suitable for high-security pairing scenarios involving core industrial equipment. The second method is a full lifecycle management and binding mode with fixed permissions. The target controlled device parses and verifies the pairing request signal, extracts the remote controller's unique identifier, permission level information, and device compatibility information. It first verifies the compatibility and permission matching between the remote controller and itself. After confirming that the remote controller has the corresponding device's operating permissions, it generates a pairing confirmation signal carrying its unique identifier, control permission scope, pairing time limit rules, and maintenance traceability rules, and sends it to the corresponding remote controller. Upon receiving the pairing confirmation signal, the remote controller verifies the device's identifier and permission rules, generates a pairing confirmation receipt, and sends it back to the target controlled device. After both parties complete mutual confirmation, they not only permanently store each other's identity identifiers and pairing information, but also simultaneously configure the control permission scope, operation timeliness rules, anomaly locking rules, and operation and maintenance traceability rules. At the same time, the entire pairing process is reported to the host computer for operation and maintenance archiving, establishing a pairing and binding relationship for full lifecycle management. This method not only completes basic identity pairing and binding, but also simultaneously achieves bidirectional management of remote control permissions, operation rules, and operation and maintenance traceability throughout the entire lifecycle. It enables refined management of remote control permissions and full traceability of pairing operations, adapting to the large-scale, hierarchical, and traceable operation and maintenance management needs of industrial production lines.

[0120] After completing two-way identity verification and permission confirmation, the final pairing and binding can be completed in the following ways.

[0121] In one optional solution, the remote control and the target controlled device first exchange and verify each other's identity information. After successful verification, both parties write each other's unique identifier and pairing verification key into a local temporary storage area, establishing a temporary pairing and binding relationship. The binding relationship automatically expires after the device restarts. This method is suitable for temporary pairing scenarios such as temporary device debugging and emergency maintenance. The binding process is simple and fast, enabling temporary pairing and automatic expiration without manual unbinding, making it suitable for temporary maintenance scenarios.

[0122] In another optional solution, the identity information of the remote controller and the target controlled device are first mutually verified, and the control permissions are mutually confirmed. After successful verification, both parties write each other's unique identifier, pairing verification key, and permission configuration information to a local non-volatile secure storage area, completing a permanent binding. Unless an unbinding authorization command is received from the host computer, the binding relationship is permanently valid, and device restarts or power outages will not affect the binding relationship. This method can establish a stable and permanent exclusive pairing binding relationship. After binding, only this remote controller can control the corresponding target controlled device, eliminating the risk of accidental control and unauthorized control, and is suitable for the conventional fixed pairing scenarios of industrial production line equipment.

[0123] In an exemplary scheme for completing two-way interactive binding, a pre-set set of pairing and binding rules for the target controlled device is first loaded. This set of rules includes five basic categories: identity verification rules, permission matching rules, data encryption rules, information solidification rules, and status feedback rules. Each rule is pre-configured with corresponding execution standards and security thresholds. Next, a pairing confirmation signal is generated and sent. The verified pairing request signal is parsed, and the remote controller's unique identifier, pairing verification key, and device type information are extracted. Based on the pairing and binding rules, a pairing confirmation signal carrying its own unique identifier, pairing authorization information, encryption public key, and status feedback rules is generated. After encryption using the remote controller's pairing verification key, it is sent point-to-point to the corresponding remote controller via a dedicated pairing channel. Then, two-way identity verification is performed. The pairing confirmation receipt signal returned by the remote controller is received, decrypted, and the remote controller's identity signature and permission confirmation information are extracted. This completes the secondary verification of the remote controller's identity and permission matching verification, confirming the remote controller's legitimacy and compatibility. Subsequently, bidirectional pairing information is solidified, writing the remote controller's unique identifier, pairing verification key, and permission configuration information to the local non-volatile secure storage area. Simultaneously, a pairing information solidification confirmation command is sent to the remote controller, triggering it to synchronously write the target controlled device's identifier and permission information to its local storage, completing the solidification process. Next, a pairing status update is performed, terminating the running pairing timer window, closing the pairing request detection channel of the wireless receiver module, restoring the normal control command response mode, and simultaneously stopping the pairing process indicator, switching to a stable, successfully paired state. Finally, the successful pairing result information, including the identifiers of both paired devices, pairing time, permission configuration, and operation traceability code, is transmitted back to the host computer, completing the closed-loop management of this pairing process.

[0124] It should be noted that in some special cases, if the target controlled device and the remote controller fail to verify identity, interrupt signal transmission, or have abnormal verification data during two-way interaction, the pairing and binding process will be terminated immediately, all temporary pairing data will be cleared, the pairing detection state will be restored until the pairing timer window reaches zero, and a pairing abnormality alarm message will be sent to the host computer.

[0125] Further, please refer to Figure 4 , Figure 4This is a diagram illustrating the interaction framework of this application. The remote control-oriented secure pairing method in a multi-USB camera production line environment comprises a PC acting as the host computer, at least three USB cameras establishing dedicated wired communication links with the PC via multiple USB ports through USB cables, a remote control with a built-in wireless transmission module, a combination button unit, and status indicator lights. The PC establishes a stable full-duplex data transmission channel with the corresponding USB camera through each independent USB cable. In response to the operator's device selection operation, the PC only sends a pairing authorization command point-to-point to the selected target USB camera via its dedicated USB cable. Other unselected USB cameras do not receive, parse, or respond to this authorization command. After receiving the pairing authorization command and completing the legality verification, the target USB camera immediately starts a pairing window of fixed duration, simultaneously controlling its own status indicator light to enter a bright flashing pairing progress indication state. Other unauthorized USB cameras maintain normal operation, and their indicator lights do not show pairing indications. The operator simultaneously presses and holds the left and right combination buttons on the remote control to trigger the pairing mode. The remote control's status indicator light simultaneously illuminates, and it continuously broadcasts a pairing request signal via the 2.4G wireless channel. Only target USB cameras within the pairing window can recognize, parse, and respond to this pairing request signal; other unauthorized USB cameras directly filter the wireless signal. After the target USB camera and remote control complete two-way identity information exchange, pairing binding, and two-way storage of pairing information, their status indicator lights simultaneously stop displaying the pairing prompt, ultimately completing a one-to-one exclusive pairing between the remote control and the target USB camera. This implementation method, through targeted exclusive authorization via a USB wired link, fundamentally solves the problems of mispairing of remote controls and signal crosstalk in environments with densely deployed multi-camera setups. Simultaneously, the two-way visual feedback via dual indicator lights on both paired devices allows the operator to intuitively grasp the entire pairing process. The physically isolated design of the wired authorization link and the wireless pairing link ensures secure and interference-free transmission of authorization commands and avoids cross-device crosstalk during wireless pairing, improving the security, accuracy, and controllability of the pairing process. It is perfectly suited for pairing and maintenance scenarios involving the mass deployment of multiple USB cameras in industrial production lines.

[0126] Fifth Embodiment This embodiment provides an exemplary scheme for secure triggering and closed-loop status management of controlled device pairing mode. In this example, the target controlled device first parses the pairing authorization command issued by the host computer, extracts the identity information carried in the command, and then completes the consistency verification between its own device identity and the command identity information. After the verification is successful, a pairing mode trigger signal is generated. Then, based on the pairing mode trigger signal, a pairing timer window of fixed duration is started, and the wireless receiving module of the target controlled device is switched to the pairable state simultaneously. Finally, based on the pairable state, the device controls its own status indicator to switch to the pairing process prompt state, and feeds back the status information of the pairing window to the host computer in real time, realizing full-process identity verification, precise timing management, and closed-loop status feedback for pairing mode initiation. Step C11 includes steps D11~D14: Step D11: After receiving the pairing authorization command sent by the host computer, parse the identity information of the pairing authorization command.

[0127] Step D12: After confirming that the identity information matches the identity of the target controlled device, generate a pairing mode trigger signal according to the pairing authorization instruction.

[0128] Step D13: Based on the pairing mode trigger signal, start the pairing timer window of a fixed duration, and switch the wireless receiving module of the target controlled device to the pairable state.

[0129] Step D14: Based on the pairable state, control its own status indicator to switch to the pairing process prompt state, and feed back the status information of the pairing window to the host computer.

[0130] The pairing mode trigger signal is an internal control signal generated by the internal microcontroller unit after the target controlled device completes identity verification. It triggers the entire pairing process and is the sole trigger source for starting the pairing timer window, switching the wireless module status, and controlling indicator components. Examples include hardware timer start trigger signals, wireless module status switching trigger signals, indicator light control trigger signals, and status feedback trigger signals.

[0131] Status indicator components are hardware units built into the target controlled equipment to visually indicate the current operating status of the equipment. Specifically, they refer to LED status indicator lights, which can correspond to different operating states of the equipment through different on / off and flashing modes, providing operators with intuitive feedback on the pairing process. Examples include a rapidly flashing pairing progress indicator, a constantly lit equipment running indicator, a stable constantly lit indicator for successful pairing, a slowly flashing alarm indicator for pairing failure, and a rapidly flashing equipment fault indicator.

[0132] The pairing process indication status is a dedicated display mode for the status indicator component after the device enters the pairing-ready state. Specifically, it refers to a fixed-frequency rapid flashing mode of the LED indicator light, used to visually indicate to the operator that the device has entered the pairing-ready state and can initiate remote control pairing operations. Examples include a 500ms period rapid flashing state, an alternating red and green flashing state, a breathing light gradual flashing state, and a pairing-specific high-brightness flashing state.

[0133] The pairing window status information is real-time structured data fed back from the target controlled device to the host computer, representing the operating status of the pairing window. It is the core basis for the host computer to realize centralized management, timing scheduling, and anomaly alarms for the entire pairing process. For example, pairing window opening success information, pairing window countdown remaining time, pairing window timeout closing information, device pairing status change information, pairing process anomaly alarm information, and wireless channel interference status information.

[0134] In this example, when receiving the pairing authorization command and parsing the identity information, the process can be performed using a one-time data packet parsing method. Alternatively, a streaming segmented parsing method can be used, where the pairing authorization command data packets sent by the host computer are received while format validation and core field extraction are performed segment by segment. After all data packets have been received, the complete identity information is extracted, thus completing the reception of the pairing authorization command and the accurate parsing of the identity information.

[0135] After parsing and extracting the identity information, the system initiates an identity consistency verification process. This process compares the parsed identity information with the device identity information embedded in the device's local security chip, ensuring a complete match and legitimate command attribution. Based on parameters such as the pairing window duration and control rules carried in the pairing authorization command, a pairing mode trigger signal is generated. Subsequently, based on this trigger signal, the internal hardware timer is initialized, a preset fixed-duration pairing timer window is started, and the signal filtering rules for the wireless receiver module are configured. The regular control command response channel is closed, and the wireless receiver module is switched to a pairable state that only responds to legitimate pairing request signals. Then, based on the entered pairable state, the system controls its status indicator to switch to a fast-flashing prompt state corresponding to the pairing process. Simultaneously, through a dedicated USB communication link with the host computer, real-time status information indicating that the pairing window has been successfully opened and the device has entered a pairable state is provided. This end-to-end identity verification, status control, and closed-loop feedback ensure that only legitimately authorized commands can trigger the device to enter the pairing state, eliminating the security risks of unauthorized or accidental pairing and allowing the host computer and operators to monitor the device's pairing status in real time.

[0136] For example, there are two ways to implement pairing mode triggering and status control through pairing authorization command verification. The first is a hardware-level full-link encrypted verification instant triggering mode. After the target controlled device receives the pairing authorization command sent by the host computer via USB cable, it immediately transmits the command to the internal hardware security chip. The security chip performs full-link hardware verification: first, it verifies the frame format of the command, the cyclic redundancy check code, and the host computer's digital signature to confirm that the command source is legitimate and has not been tampered with; then, it decrypts and extracts the identity information in the command, and accurately compares it with the unique device identity information stored in the one-time programmable storage area in the security chip to complete the identity consistency verification. After all verification items pass, the security chip outputs a pairing mode trigger signal to the microcontroller unit. After receiving the trigger signal, the microcontroller unit immediately initializes the hardware timer to start a fixed 10-second pairing timing window, and simultaneously outputs a control level to the wireless receiver chip through the general-purpose input / output port (GPIO) to switch the wireless receiver module to the pairable state. At the same time, it configures hardware signal filtering rules to only allow pairing request signals that conform to the preset format. Subsequently, the microcontroller unit controls the LED status indicator to enter a rapid flashing state, on for 100ms and off for 100ms, to indicate the pairing process. Simultaneously, it sends real-time status information to the host computer via USB communication link, indicating successful pairing window opening and the device entering a pairable state. A periodic reporting mechanism for the pairing window countdown is also initiated concurrently. This method employs end-to-end hardware verification with a hardware security chip, tamper-proof fixed identity comparison, and hardware-level signal-triggered control logic, eliminating security risks such as software tampering, illegal command forgery, and unauthorized pairing triggers. It boasts extremely high security and anti-tampering capabilities, making it suitable for pairing core equipment in industrial production lines with stringent security control requirements.

[0137] The second method is a partitioned, grouped, hierarchical, time-sequenced control delayed trigger mode. After receiving the group pairing authorization command from the host computer, the target controlled device first performs the first-level basic format verification and group affiliation verification. Once it confirms that the group identifier in the command matches its own production line partition group, it enters a pre-ready state and sends a command reception receipt to the host computer, but does not initiate the pairing process. Subsequently, based on the deployment locations of multiple devices on the production line and the wireless channel interference situation, the host computer allocates independent pairing timing windows for all controlled devices within the same group and sends timing start commands to each device. After receiving the start command corresponding to its own timing, the target controlled device then performs the second-level identity consistency verification, comparing the identity identifier information in the command with its own device identity. If the verification is successful, a pairing mode trigger signal is generated. Based on the trigger signal, a fixed-duration pairing timing window matching its own timing window is initiated, and the wireless receiving module is switched to the pairable state of the group's dedicated channel, only detecting pairing request signals within the group's dedicated channel. Subsequently, the control status indicator component enters the pairing process prompt state of the corresponding group, and simultaneously feeds back the timing synchronization information of the pairing window opening to the host computer. After its own timing window ends, it automatically closes the pairing state. This method adopts a management logic of partitioned group hierarchical verification, timing peak-shifting delay triggering, and dedicated channel isolation. Through peak-shifting timing allocation and channel isolation, it completely solves the problems of wireless signal interference, crosstalk, and mispairing caused by multiple devices being paired simultaneously in the scenario of dense deployment of multiple devices on the production line. At the same time, it supports the host computer to accurately control the timing of the batch device pairing process, improves the success rate and management efficiency of batch pairing on the production line, and is suitable for large-scale pairing scenarios such as new production line commissioning and batch operation and maintenance of the entire line of equipment.

[0138] Sixth Embodiment This embodiment provides an exemplary scheme for accurate identification and reception of pairing request signals with anti-interference capabilities. In this example, the target controlled device first locks onto a dedicated wireless communication channel based on its entered pairable state and shields against external clutter interference, constructing a high signal-to-noise ratio pairing signal detection environment. Then, within the effective time period of the pairing timing window, wireless radio frequency signals within the pairing signal detection environment are continuously collected at a fixed time interval. Next, the collected wireless radio frequency signals are screened step-by-step according to preset encoding rules, filtering out various invalid interference signals to obtain candidate signals. Finally, by verifying the identity information carried in the candidate signals, a legitimate pairing request signal is accurately determined and received by the wireless receiving module within the effective duration of the pairing timing window. This achieves high-precision identification, strong anti-interference reception, and anti-accidental touch filtering of pairing request signals in complex industrial environments. After step C11, steps E11~E14 are also included: Step E11: Based on the pairable state, lock the wireless communication channel and shield external noise interference to construct a pairing signal detection environment.

[0139] Step E12: During the effective time period of the pairing timing window, collect the wireless radio frequency signal of the pairing signal detection environment at a fixed timing period.

[0140] Step E13: The wireless radio frequency signal is screened step by step according to the encoding rules to filter out invalid interference signals and obtain the candidate signal.

[0141] Step E14: By verifying the identity information carried in the candidate signal, determine and receive the pairing request signal within the pairing timing window via the wireless receiving module.

[0142] External noise interference refers to all invalid electromagnetic signals within a wireless communication channel, excluding legitimate pairing request signals. It is the core source of interference affecting the accuracy of pairing signal identification. Examples include interference from Wi-Fi signals in the same frequency band, electromagnetic radiation noise from nearby industrial equipment, wireless communication signals from other controlled equipment, electromagnetic interference from production line motors, and radio frequency noise from the surrounding environment.

[0143] The pairing signal detection environment is a high signal-to-noise ratio wireless signal receiving environment built by the target controlled device after configuring channel locking, clutter shielding, and filtering rules. It is dedicated to the detection, acquisition, and identification of pairing request signals and is the foundation for ensuring the quality of pairing signal acquisition. Examples include single-channel locking dedicated detection environments, detection environments with hardware clutter suppression, frequency hopping synchronous scanning detection environments, and partitioned group isolation detection environments.

[0144] Encoding rules are pre-configured, pairing signal-specific encoding specifications agreed upon between the target controlled device and the remote controller. They are the core criteria for distinguishing legitimate pairing signals from invalid interference signals, and only signals that fully comply with the encoding rules can proceed to subsequent verification stages. Examples include pairing signal preamble encoding rules, data frame format encoding rules, cyclic redundancy check encoding rules, industrial-grade encryption encoding rules, and device type identification encoding rules.

[0145] In this example, when locking the wireless communication channel based on the pairable state and shielding external clutter interference to construct the pairing signal detection environment, the single-channel fixed locking method can be used as a reference. Alternatively, a full-band interference scan can be performed. First, an interference intensity scan is performed on the entire 2.4 GHz band to mark all strong interference frequencies. The clean frequency with the highest signal-to-noise ratio is selected as the dedicated wireless communication channel for this pairing. Then, hardware filters are used to shield the clutter interference of the remaining frequencies, constructing a high signal-to-noise ratio pairing signal detection environment. This completes the anti-interference optimization construction of the pairing signal receiving environment.

[0146] After constructing the pairing signal detection environment, the periodic acquisition process of wireless radio frequency signals is initiated. Within the effective time period of the pairing timing window, the signal acquisition function of the wireless receiving module is cyclically activated according to a preset fixed time sequence, continuously acquiring all wireless radio frequency signals within the pairing signal detection environment to complete the full acquisition of raw signals. Subsequently, according to the preset pairing signal-specific encoding rules, all acquired wireless radio frequency signals undergo a step-by-step screening at the physical layer, link layer, and application layer, filtering out invalid interference signals with abnormal signal strength, mismatched formats, and inconsistent encoding rules, retaining all candidate signals that conform to the encoding rules. Next, for each candidate signal, the remote control identification information it carries is decrypted and extracted, and compared item by item with the legal remote control identification rules agreed in this pairing authorization instruction. Within the effective time period of the pairing timing window, signals whose identification information completely matches are selected and identified as legitimate pairing request signals. The wireless receiving module completes the reception and buffering of the signals. In this way, through a layered filtering and double legality verification mechanism, the accuracy of pairing request signal identification is improved, thoroughly filtering out various interference signals in the industrial environment and eliminating the misidentification and misresponse of invalid signals.

[0147] For example, there are two ways to achieve accurate identification and reception of pairing request signals through step-by-step screening and identity verification. The first is a three-level step-by-step filtering serial accurate identification mode with time locking. After the target controlled device completes the construction of the pairing signal detection environment, the effective time period of the pairing timing window is divided into equal-length acquisition time slots corresponding to a fixed acquisition cycle. A complete signal acquisition, screening, and verification process is completed within each time slot. Within each acquisition time slot, all wireless radio frequency signals in the current pairing signal detection environment are first acquired at full power. The first-level physical layer screening is performed to filter out invalid clutter signals with signal strength below the preset near-distance pairing threshold and above the strong interference threshold, retaining only radio frequency signals with signal strength within a reasonable range. Then, the second-level link layer screening is performed on the remaining signals to verify the preamble, data frame format, and cyclic redundancy check code, filtering out invalid service signals with mismatched frame formats and incorrect check codes, retaining only radio frequency signals that conform to the pairing signal encoding format. Then, the third-level application layer screening is performed on the remaining signals to verify the pairing-specific identifier and device type code within the signal, filtering out non-pairing signals without a valid pairing identifier to obtain candidate signals. Subsequently, the candidate signals undergo identity verification. The unique remote control identifier and pairing verification key within the signal are decrypted and extracted, and compared item by item with the legal identity rules in the current pairing authorization command. Once verification is successful, the signal is identified as a legitimate pairing request signal, completing signal reception and buffering. Simultaneously, the invalid acquisition and screening process in subsequent time slots is paused, focusing on subsequent pairing interactions. This method employs a control logic of time slot timing locking, three-level hierarchical filtering, and serial packet-by-packet verification. Through layer-by-layer filtering from the physical layer to the application layer, it eliminates the vast majority of invalid interference signals at the source, retaining only a very small number of candidate signals for final identity verification. This reduces the computational overhead of the device, while achieving extremely high signal recognition accuracy, preventing misidentification of interference signals in industrial environments, and adapting to pairing scenarios in most conventional industrial production lines.

[0148] The second method is a multi-dimensional feature clustering-based intelligent anti-interference parallel recognition mode. After the target controlled device completes the construction of the pairing signal detection environment, it continuously collects all wireless radio frequency signals at a fixed time period within the effective time window of the pairing timing window. Simultaneously, a dual-process parallel processing mode is initiated. The first process is the signal feature extraction process, which decomposes each collected wireless radio frequency signal into five core dimensions: encoding format features, time period features, frequency stability features, identification features, and signal strength fluctuation features, generating a feature dataset for each signal. The second process is the intelligent clustering recognition process. Based on a pre-trained industrial scenario pairing signal recognition model, it performs cluster analysis on the feature datasets of all signals, automatically dividing the signals into three categories: legitimate pairing signal clusters, industrial interference signal clusters, and other equipment service signal clusters. All invalid signals within the interference signal clusters and service signal clusters are filtered out, retaining only signals within the legitimate pairing signal clusters as candidate signals. Subsequently, for candidate signals, a batch of full-dimensional identity verification is performed. The remote control identity, pairing verification key, and group affiliation information within each candidate signal are extracted and fully matched against the authorization scope of the current pairing authorization command. Signals with unique and compliant identities are then selected as the legitimate pairing request signals, completing signal reception and parsing. This method employs innovative logic including multi-dimensional feature extraction, AI intelligent clustering recognition, and dual-process parallel processing. It can autonomously learn the characteristics of interference signals in different industrial scenarios and adaptively optimize recognition rules. Even in extremely complex industrial environments with dense deployment of multiple devices, strong electromagnetic interference, and overlapping signals, it can accurately isolate interference signals and lock onto legitimate pairing request signals. This completely solves the pain point of traditional fixed filtering rules being unable to adapt to dynamically changing interference environments. It is suitable for complex industrial scenarios such as high-end intelligent manufacturing production lines and dense deployment of multiple devices, demonstrating strong scenario adaptability and creativity.

[0149] Seventh Embodiment This embodiment provides an exemplary scheme for closed-loop management and full-process traceability of remote control pairing failure. In this example, the target controlled device first monitors the running status of the pairing timer window in real time. If no verified pairing request signal is received before the pairing timer window resets to zero, a pairing failure trigger signal is generated. Then, based on the pairing failure trigger signal, the pairing identification channel of its own wireless receiving module is shut down, and a pairing failure result analysis command is generated. Next, based on the failure result analysis command, the entire pairing record of this pairing operation is compiled, the root cause of the failure is located, and a standardized failure traceability record is obtained. Finally, the failure traceability record is uniquely associated with this pairing operation and uploaded to the host computer, realizing a secure closed-loop, anomaly traceability, and centralized operation and maintenance management of the pairing failure process. Please refer to... Figure 5 , Figure 5This is a flowchart illustrating the seventh embodiment of the pairing method for the remote control of this application. Following step C11, steps F11 to F14 are also included: Step F11: If the target controlled device does not receive a verified pairing request signal before the pairing timer window is zeroed, a pairing failure trigger signal is generated.

[0150] Step F12: Based on the pairing failure trigger signal, shut down the pairing identification channel of its own wireless receiving module and generate a pairing failure result analysis command.

[0151] Step F13: Based on the failure result analysis instruction, organize the pairing records and failure reasons for this pairing operation to obtain the failure traceability record.

[0152] Step F14: After associating the failure tracing record with the current pairing, upload the failure tracing record to the host computer.

[0153] The pairing failure trigger signal is an internal control signal generated by the internal microcontroller unit when the target controlled device does not receive a valid pairing request signal before the pairing timer window returns to zero. It is used to trigger the termination of the pairing process and manage failures. It is the sole trigger source for closing the pairing channel and initiating the failure analysis process. Examples include pairing timeout failure trigger signals, pairing window zeroing trigger signals, termination signal due to no valid pairing request, abnormal termination trigger signal of the pairing process, and authorization expiration failure signal.

[0154] The pairing identification channel is a pre-configured signal processing channel within the target controlled device's wireless receiving module, dedicated to identifying and parsing remote control pairing request signals. This channel is only activated during the valid pairing time window and remains closed at other times, effectively avoiding interference from invalid signals and the risk of false triggering outside of pairing periods. Examples include a dedicated pairing request signal parsing channel, a 2.4G wireless pairing signal receiving channel, a pairing signal identification channel with filtering rules, a pairing signal processing channel that is activated for a limited time, and a dedicated encrypted pairing signal parsing channel.

[0155] The pairing failure result analysis command is an internal command generated by the target controlled device based on the pairing failure trigger signal. It is used to initiate a full-process backtracking and root cause analysis of this pairing failure and is the core trigger signal for triggering pairing record organization and failure cause location. Examples include pairing failure root cause analysis command, pairing process backtracking command, failure record organization command, pairing anomaly tracing command, and operation and maintenance data generation command.

[0156] The pairing record is a real-time record of all operational data and information from the target controlled device throughout the entire pairing process. It is the core foundational data for locating the cause of pairing failure. Examples include the time the pairing authorization command was received, the time the pairing window opened and closed, the pairing window duration parameter, wireless channel interference data, records of received invalid signals, device hardware operating status data, host computer authorization information, and operation traceability codes.

[0157] The failure reason is the core cause of the pairing process failure, identified by the target controlled device based on the entire pairing process record and through preset root cause analysis rules. This is the core content of the failure tracing record. For example, the pairing timer window expires without a valid pairing request, strong wireless channel interference causes the signal to be unrecognizable, the remote control does not enter a valid pairing mode, crosstalk from nearby devices, abnormal pairing authorization command, or abnormal operation of the device hardware module.

[0158] Failure traceability records are standardized traceability documents generated by integrating the entire pairing process record, failure root cause, device identity information, and authorization information of the target controlled device. They serve as the core basis for the host computer to achieve centralized management, anomaly analysis, and operation and maintenance optimization of the pairing process. Examples include: a full-process pairing failure traceability record; a pairing anomaly record with a unique operation code; a pairing failure report with root cause location; a standardized operation and maintenance traceability record; and an anomaly analysis report with optimization suggestions.

[0159] In this example, when generating a pairing failure trigger signal by detecting the pairing timer window status, a fixed-duration pairing window timing control method can be used. Alternatively, a hierarchical multi-segment pairing window status detection method can be used to monitor the operating status and signal reception of each pairing window in real time. If no verified pairing request signal is received before the final pairing window is zeroed out, a pairing failure trigger signal is generated, thereby achieving accurate determination and reliable triggering of pairing failure.

[0160] After generating the pairing failure trigger signal, the pairing process is terminated and a failure analysis procedure is initiated. Based on the pairing failure trigger signal, the pairing identification channel of its own wireless receiver module is shut down, the normal control command response mode of the wireless receiver module is restored, the pairing process is terminated, and a pairing failure result analysis command is generated. Subsequently, based on this failure result analysis command, the pairing records of the entire pairing process are retrieved, including host computer authorization information, pairing window operation data, wireless channel signal data, invalid signal reception records, etc. Through preset root cause analysis rules, the core reason for this pairing failure is located, and the pairing records and failure reasons are integrated to generate a standardized failure tracing record. Next, an operation traceability code, a unique device identifier, and an operation timestamp are added to the failure traceability record to uniquely bind it to this pairing. This completes the unique association between the failure traceability record and this pairing. Finally, the failure traceability record is uploaded to the host computer via a USB communication link to complete archiving and operation and maintenance analysis. In this way, through the closed-loop management of the pairing failure process, the traceability, analysis, and optimization of pairing anomalies are achieved, providing data support for the iterative optimization of the production line pairing process. At the same time, it ensures that the controlled equipment can quickly return to normal operation after pairing failure, eliminating the security risks of unauthorized pairing.

[0161] For example, there are two ways to generate failure tracing records through pairing record organization and root cause analysis. The first is a time-locked full-process serial backtracking root cause analysis. After the target controlled device generates a pairing failure result analysis instruction, based on the execution sequence of this pairing process, starting from the starting node of receiving the pairing authorization instruction, all operational data of the entire pairing process are backtracked node by node in chronological order. First, the receiving and verification nodes of the pairing authorization instruction are backtracked to confirm the legality, completeness, and execution status of the authorization instruction. Then, the starting and running nodes of the pairing timing window are backtracked to confirm the execution status of the window duration parameters and state switching actions. Next, the signal receiving nodes of the wireless channel are backtracked to statistically analyze all wireless signals received within the pairing window, verification results, and environmental interference. Finally, the hardware operation status nodes of the device itself are backtracked to confirm the operation status of the wireless receiving module and microcontroller unit. Upon completion of the backtracking of each time-series node, the node's operational data and anomalies are recorded synchronously. After the backtracking of all time-series nodes is completed, based on the anomalies of all nodes, the core cause of the pairing failure is located using preset root cause determination rules. The entire time-series pairing record and the failure cause are integrated to generate a standardized failure traceability record. This method employs a time-locked, node-by-node serial backtracking and step-by-step verification analysis logic to completely reconstruct the execution of the entire pairing process without omitting any execution node. It boasts high root cause location accuracy and can clearly reconstruct the complete cause of pairing failure. It is suitable for traceability analysis scenarios of conventional single-device pairing failures, providing maintenance personnel with clear avenues for anomaly troubleshooting.

[0162] The second method is multi-dimensional parallel clustering for root cause analysis. After the target controlled device generates a pairing failure result analysis command, all data from the entire pairing process is first dimensionally split into five independent analysis dimensions: authorization and control, time-series operation, wireless channel, device hardware, and operational behavior. Pairing record data for each dimension is extracted simultaneously to generate feature datasets for each of the five dimensions. Then, parallel verification analysis is initiated simultaneously for these feature datasets. Within each dimension, the feature data from this pairing is compared with preset standard normal operation thresholds and historical normal pairing datasets to locate abnormal features and mark their impact level. After the parallel verification analysis of all dimensions is completed, the abnormal features from all dimensions are summarized. Using preset clustering analysis rules, root cause clustering is performed on all abnormal items to identify the core primary and secondary causes of the pairing failure. Corresponding operation and maintenance optimization suggestions are also matched to each abnormal item. Finally, the full-dimensional pairing records, root cause clustering results, and operation and maintenance optimization suggestions are integrated to generate a full-dimensional failure tracing record. This method employs an analytical logic of multi-dimensional splitting, full-dimensional parallel verification, and anomaly clustering root cause localization. It can not only accurately locate the core reasons for pairing failures, but also comprehensively uncover potential anomalies in the pairing process. At the same time, it provides actionable optimization suggestions, offering comprehensive data support for optimizing the pairing process of large-scale controlled equipment on production lines and for centralized operation and maintenance management. It is suitable for industrial production line operation and maintenance scenarios with dense deployment of multiple devices and large-scale batch pairing.

[0163] Eighth embodiment This embodiment provides an exemplary scheme for constructing a pairing confirmation and secure binding channel between a remote control and a controlled device. In this example, after the target controlled device receives a verified pairing request signal, a pairing confirmation signal uniquely bound to the pairing request signal is generated. This pairing confirmation signal is then sent point-to-point to the remote control that initiated the pairing request, thus constructing an encrypted dedicated pairing binding channel between the target controlled device and the remote control. Finally, based on this dedicated pairing binding channel, two-way identity verification and pairing information exchange are completed, thus achieving secure pairing binding between the remote control and the target controlled device. Step C14 includes steps G11~G13: Step G11: After receiving the pairing request signal, trigger the pairing confirmation signal with the target controlled device.

[0164] Step G12: Send the pairing confirmation signal to the remote controller to establish a pairing and binding channel between the target controlled device and the remote controller.

[0165] Step G13: Send the pairing confirmation signal to the remote controller to establish a pairing and binding channel between the target controlled device and the remote controller.

[0166] The pairing confirmation signal is a dedicated encrypted response signal generated by the target controlled device based on a legitimate pairing request signal. It is used to confirm the validity of the pairing and initiate a two-way binding interaction. The signal carries the target controlled device's unique identifier, pairing verification key, session negotiation information, and authorization configuration data, and is the core interactive carrier for building the pairing and binding channel. Examples include an encrypted pairing response signal with the device's unique identifier, a pairing authorization confirmation signal, an identity verification interaction trigger signal, a session key negotiation signal, and a binding information synchronization command.

[0167] A dedicated pairing and binding channel is a point-to-point, fully encrypted, and exclusively used wireless communication channel established between the target controlled device and the remote controller based on a pairing confirmation signal. This channel is used only for the two-way identity verification and binding information exchange during this pairing process. All other non-pairing data cannot be transmitted through this channel, making it the core security carrier for ensuring secure pairing interactions and preventing signal interception and crosstalk. Examples include point-to-point encrypted wireless communication channels, single-device dedicated pairing session channels, encrypted binding channels with frequency hopping rules, one-time pairing dedicated communication channels, and hardware-level encrypted interaction channels.

[0168] Two-way identity verification is a full-process mutual verification operation in which the target controlled device and the remote control transmit and verify each other's identity identifiers, pairing verification keys, and authorization information through a dedicated pairing and binding channel. It is a core security step to confirm the legitimacy of both parties and prevent unauthorized binding. Examples include two-way verification of device identity identifiers, two-way negotiation and verification of pairing keys, two-way matching and verification of authorization permissions, two-way mutual verification of digital signatures, and two-way comparison of hardware identity information.

[0169] Pairing information interaction is the bidirectional synchronous transmission of pairing control rules, permission configurations, operating parameters, and traceability information between the target controlled device and the remote controller through a dedicated pairing and binding channel. It is the core link in establishing a stable control relationship between the two parties. For example, it includes bidirectional synchronization of control command response rules, bidirectional confirmation of permission level configurations, bidirectional storage of pairing traceability information, bidirectional adaptation of operating parameters, and bidirectional synchronization of anomaly locking rules.

[0170] In this example, when receiving a pairing request signal and generating a pairing confirmation signal uniquely bound to it, the method for generating a fixed-format signal can be followed. Alternatively, a dynamic association binding method can be used. This involves extracting the remote control's unique identifier, random serial number, and pairing verification key from the received pairing request signal. Based on this information, a random session key uniquely associated with this pairing request is generated. The device's own identifier, session key, pairing authorization information, and channel frequency hopping rules are then encrypted and integrated to generate a pairing confirmation signal uniquely bound to this pairing request signal. This completes the secure generation and unique association binding of the pairing confirmation signal.

[0171] After generating the pairing confirmation signal, the pairing and binding channel construction process is initiated. The pairing confirmation signal is sent point-to-point to the remote control that initiated the pairing request via a dedicated wireless channel corresponding to the pairing request signal. Upon receiving the remote control's receipt, based on the encryption rules, frequency hopping timing, and communication protocol agreed upon in the pairing confirmation signal, the exclusive communication frequency and encryption rules for both parties are locked, establishing a dedicated pairing and binding channel between the target controlled device and the remote control. Next, based on this dedicated pairing and binding channel, bidirectional transmission and cross-verification of the identity identifiers, pairing keys, and authorization information of both parties are completed. Simultaneously, bidirectional interaction of pairing control rules, permission configurations, and maintenance traceability information is completed. After both parties have passed verification and the information is synchronized, the pairing information is written bidirectionally to the local secure storage area for solidification. Finally, the secure pairing and binding between the remote control and the target controlled device is completed. This end-to-end isolation interaction through the dedicated encrypted channel eliminates the security risks of interception, tampering, and man-in-the-middle attacks on the pairing signal, ensuring the uniqueness and security of the pairing and binding.

[0172] For example, there are two ways to achieve secure pairing and binding through pairing confirmation signal interaction. The first is a hardware-level one-time key binding mode. After receiving the verified pairing request signal, the target controlled device transmits the signal to its internal hardware security chip. The security chip extracts the remote control's unique hardware serial number, public key information, and random number from the pairing request signal. Based on a true random number generator, it generates a one-time symmetric encryption key specific to this pairing. At the same time, it encrypts and integrates its own unique hardware serial number, public key information, pairing authorization rules, and one-time key to generate a pairing confirmation signal uniquely bound to this pairing request. This pairing confirmation signal can only be decrypted by the hardware security chip of the corresponding remote control. Subsequently, the security chip sends the pairing confirmation signal point-to-point to the corresponding remote control through a wireless receiving module. After receiving the hardware-level reception receipt from the remote control, it constructs a hardware-level encrypted exclusive pairing and binding channel based on the one-time key and the agreed fixed frequency. All data transmissions in this channel are encrypted and decrypted by the hardware security chips of both parties. The main controller can only transmit but cannot read the key content. Next, the hardware identity information of both parties is cross-verified through this channel. After confirming the legality and validity of the hardware identities of both parties, the unique hardware serial number and one-time pairing key of the other party are written into the one-time programmable storage area within the security chip, completing the tamper-proof hardware-level solidification. At the same time, control rules and permission configurations are synchronized, ultimately completing the lifelong unique binding between the remote control and the target controlled device. This method adopts innovative logic of end-to-end encryption and decryption of hardware security chips, tamper-proof solidification of one-time keys, and hardware-level channel isolation, eliminating the security risks of software cracking, key leakage, and unauthorized tampering with the binding relationship. The security level and anti-cracking capability of the pairing binding reach the highest industrial-grade standard, making it suitable for pairing application scenarios with extremely high security requirements, such as military, high-end manufacturing, and classified scenarios. It has strong creativity and irreplaceability.

[0173] The second method is a full lifecycle management and binding mode based on dynamic session key negotiation. After receiving a verified pairing request signal, the target controlled device first extracts the remote controller's identity, device type, permission level, and grouping information from the pairing request signal. This information is then matched and confirmed against the management rules of the pairing authorization command. Subsequently, a temporary public-private key pair is generated based on the elliptic curve cryptography algorithm. The device's own public key, device identity, pairing authorization rules, and frequency hopping channel sequence are packaged to generate a pairing confirmation signal. This pairing confirmation signal is then sent point-to-point to the corresponding remote controller. Upon receiving the remote controller's public key and pairing confirmation receipt, a dynamic session key specific to this pairing is generated based on the public keys of both parties. Simultaneously, the timing switching rules of the frequency hopping channel are synchronized to construct a dedicated pairing and binding channel that dynamically hops over time and is fully encrypted throughout the session. This dedicated pairing and binding channel will switch communication frequencies and encryption keys in real time according to preset rules to avoid the risks of signal interception and crosstalk. Next, through this dynamic encrypted channel, two-way verification of identity information, two-way matching of control permissions, two-way synchronization of operation rules, and two-way interaction of operation and maintenance traceability information are completed. Simultaneously, the effective time of the binding relationship, anomaly locking rules, unbinding authorization procedures, and parameter update mechanisms are agreed upon. After all information from both parties is synchronized and verified, the pairing binding information, session key, and control rules are written bidirectionally to the local non-volatile storage area, completing the pairing binding with full lifecycle control rules. At the same time, the full-link traceability information and permission configuration data of this pairing are sent back to the host computer. This method employs innovative logic of dynamic public key negotiation, real-time frequency-hopping encrypted channels, and full lifecycle control rule synchronization. It not only ensures communication security and anti-crosstalk capabilities during the pairing process but also achieves full-process controllability, traceability, and configurability of the pairing binding relationship. It is suitable for large-scale application scenarios involving dense deployment of multiple devices in industrial production lines, hierarchical permission control, and batch operation and maintenance management. It solves the pain point that traditional fixed binding modes cannot adapt to the dynamic operation and maintenance needs of production lines, demonstrating strong scenario adaptability and creativity.

[0174] Ninth Embodiment This embodiment provides an exemplary solution for a secure pairing system. In this example, the secure pairing system includes a host computer and target controlled devices. First, the host computer groups and partitions all connected controlled devices according to their physical deployment area and business function type, and manages them in a ledger manner. In response to the user's target partition selection operation, it generates a batch pairing authorization command uniquely bound to the partition. Then, through the dedicated communication link established between the host computer and the controlled devices in the target partition, the authorization command is sent to each target controlled device according to the time-sequence control rules, triggering each device to enter the pairable state in a time-sequence manner to complete the secure binding with the remote controller. Finally, the host computer summarizes the pairing results of all partitions to complete batch archiving and closed-loop control, thereby realizing the partitioned and hierarchical, anti-crosstalk, and highly efficient batch secure pairing control of large-scale controlled devices in industrial production lines.

[0175] In this example, when grouping and partitioning controlled equipment to generate a partition control ledger, the method of binding a single device identity can be used as a reference. Alternatively, by using a production line digital twin mapping method, the physical deployment location, business function affiliation, and workstation association of the controlled equipment in the production line's 3D model can be read to automatically complete the grouping and partitioning of the equipment, and simultaneously generate a partition control ledger and a unique encrypted partition identifier for each partition, thereby completing the intelligent partitioning and ledger-based management of the controlled equipment.

[0176] After establishing the partition control ledger, the process of generating and issuing batch pairing authorization instructions is initiated. The host computer responds to the user's selection of a target partition in the partition control interface, retrieves the control ledger, partition identifier, and device list for the target partition, and generates a batch pairing authorization instruction uniquely bound to the target partition. This instruction carries the partition's unique identifier, time-sequence control rules, pairing window parameters, and authorization validity period. Subsequently, the host computer establishes a dedicated point-to-point communication link with each target controlled device based on its USB access address within the partition. Following the preset time-sequence control rules, it sequentially issues batch pairing authorization instructions to each controlled device within the partition, triggering each controlled device to activate its pairing timer window and enter a pairable state in a staggered sequence, avoiding wireless channel interference caused by multiple devices simultaneously activating pairing. Then, each target controlled device within the partition completes the identification, verification, and two-way pairing binding of its corresponding remote control pairing request signal within its own pairing window. Upon completion of pairing binding for each device, it immediately sends the partition pairing result information back to the host computer. After receiving the pairing results of all partitioned devices, the host computer performs batch verification, classification and archiving of the pairing results, and anomaly alarms based on the partitioned control ledger. At the same time, it binds and stores the pairing results with the partitioned device ledger, completing the closed-loop control of the entire process of this partitioned batch pairing. In this way, through the partitioned hierarchical and time-sequence isolated control mechanism, the industry pain points of signal crosstalk, mispairing, and low control efficiency during the batch pairing of large-scale controlled devices in industrial production lines are solved. At the same time, the pairing process is made fully traceable and controllable.

[0177] For example, there are two ways to achieve batch secure pairing through regional and functional control. The first is a fixed physical partition static time-sequence batch pairing control mode. The host computer pre-divides all controlled devices into multiple independent fixed physical partitions according to the physical workstations and installation areas of the production line. Each partition is assigned a unique partition identifier, a dedicated wireless pairing channel, and fixed time-sequence control rules, generating a partition control ledger and permanently fixing it. When a user initiates a batch pairing operation, the target physical partition is selected first. Based on the fixed control rules of that partition, the host computer generates a batch pairing authorization command uniquely bound to the partition. The command carries the partition's dedicated pairing channel parameters and fixed staggered timing rules. Subsequently, the host computer sends pairing authorization commands to each controlled device in the partition sequentially through the partition's dedicated USB communication link, according to a fixed staggered timing of 10 seconds. After the pairing window of the previous device ends, the authorization command is sent to the next device, ensuring that only one controlled device in the partition is in a pairable state at any given time, and only the partition's dedicated pairing channel is detected. After receiving the authorization command, each controlled device initiates a pairing window of fixed duration, switches to a pairable state, completes pairing and binding with the corresponding remote controller, and then sends the pairing result back to the host computer. Once the pairing process for all devices within the partition is complete, the host computer performs batch archiving and status updates of all pairing results based on the partition management ledger. This method employs a management logic of fixed physical partitions, static timing staggered peaks, and single-device exclusive pairing windows. Through the dual mechanisms of physical partitioning and timing isolation, it fundamentally eliminates wireless signal crosstalk and mispairing issues during multi-device pairing. The management logic is simple, stable, secure, and reliable, adaptable to standardized industrial production line scenarios with fixed equipment layouts and regular batch pairing requirements, demonstrating strong practicality.

[0178] The second type is the dynamic functional partition adaptive parallel pairing control mode. The host computer dynamically partitions all connected controlled devices based on the service function type of the controlled equipment, the production line's cycle time, and the real-time wireless channel interference status. Devices performing the same service function, operating at the same production cycle time, and exhibiting consistent wireless channel interference characteristics are grouped into the same dynamic functional partition. Each dynamic partition is assigned an independent frequency-hopping pairing channel group, parallel control rules, and adaptive timing adjustment strategy, and the partition control ledger is updated in real time. When a user initiates a batch pairing operation, the target dynamic functional partition is first selected. The host computer then performs a real-time interference scan of the full-band wireless channels corresponding to the partition, selecting multiple interference-free clean frequencies as the partition's parallel pairing channel group. An adaptive batch pairing authorization command bound to the dynamic partition is generated, carrying the frequency-hopping channel group, parallel pairing control rules, and interference adaptive adjustment strategy. Subsequently, the host computer, through the parallel communication mechanism of the USB bus, simultaneously sends batch pairing authorization commands to all controlled devices within the partition. Upon receiving the command, each controlled device, according to the frequency hopping rules within the command, locks onto different independent clean frequencies within the channel group and synchronously starts the pairing timer window to enter the pairable state. At the same time, multiple devices within the partition execute the pairing process in parallel on different independent channels without interfering with each other. After each controlled device completes pairing and binding with its corresponding remote controller on its own independent channel, it transmits the pairing result information back to the host computer in real time, and the host computer synchronously updates the dynamic partition management ledger. After all devices within the partition have been paired, the host computer completes batch archiving and releases channel resources, and simultaneously optimizes the dynamic partitioning rules and channel selection strategies based on the pairing results. This method adopts an innovative management logic of service function-driven dynamic partitioning, multi-channel parallel isolation, and interference adaptive adjustment, breaking through the efficiency bottleneck of traditional fixed partitioning and serial pairing. While eliminating signal crosstalk and mispairing, it achieves parallel batch pairing of a large number of devices.

[0179] This application provides a pairing device for a remote control, the pairing device for a remote control including: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the pairing method for the remote control in the first embodiment described above.

[0180] The following is for reference. Figure 6The diagram illustrates a structural schematic of a pairing device suitable for implementing the remote control embodiments of this application. The pairing device for the remote control in these embodiments may include, but is not limited to, mobile terminals such as mobile phones, laptops, display terminal devices, personal digital assistants (PDAs), portable media players (PMPs), smart home devices, etc., as well as fixed terminals such as smart lighting devices, game consoles, etc. Figure 6 The pairing device for the remote control shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0181] like Figure 6 As shown, the pairing device for the remote control may include a processing unit 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the pairing device for the remote control. The processing unit 1001, the read-only memory 1002, and the RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the pairing device of the remote control to communicate wirelessly or wiredly with other devices to exchange data. Although pairing devices for remote controls with various systems are shown in the figures, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems can be implemented alternatively.

[0182] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from read-only memory 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0183] The remote control pairing device provided in this application, employing the remote control pairing method described in the above embodiments, can solve the technical problem of poor operational security of the controlled device. Compared with the prior art, the beneficial effects of the remote control pairing device provided in this application are the same as those of the remote control pairing method provided in the above embodiments, and other technical features of the remote control pairing device are the same as those disclosed in the previous embodiment method, and will not be repeated here.

[0184] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

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

[0186] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, the computer-readable program instructions being used to execute the remote control pairing method in the above embodiments.

[0187] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, radio frequency (RF), etc., or any suitable combination thereof.

[0188] The aforementioned computer-readable storage medium may be included in the pairing device of the remote control; or it may exist independently and not assembled into the pairing device of the remote control.

[0189] The aforementioned computer-readable storage medium carries one or more programs that, when executed by the pairing device of the remote control, cause the pairing device of the remote control to: in response to a user's selection operation for a controlled device, determine the target controlled device for this pairing from the connected controlled devices; generate a pairing authorization instruction associated with the target controlled device based on the identification information and wireless receiving parameters of the target controlled device; and send the pairing authorization instruction to the target controlled device to trigger the target controlled device to switch to a pairable state.

[0190] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0191] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation that may be implemented in systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0192] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0193] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the pairing method of the remote control described above, which can solve the technical problem of poor operational security of the controlled device. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as the beneficial effects of the pairing method of the remote control provided in the above embodiments, and will not be repeated here.

[0194] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A pairing method for a remote control, characterized in that, Applied to a host computer, the method includes: In response to the user's selection of a controlled device, the range of controlled devices that the user can operate is filtered based on the user's permission level. Then, combined with the user's current physical space and usage scenario, the range of operable devices is further filtered to obtain a pool of selectable devices. Based on the pool of available devices, the device information corresponding to the selected operation is matched to determine the target controlled device for this pairing. Based on the identification information and wireless reception parameters of the target controlled device, a pairing authorization command associated with the target controlled device is generated; The pairing authorization command is sent to the target controlled device to trigger the target controlled device to switch to a pairable state.

2. The pairing method for the remote control as described in claim 1, characterized in that, The step of generating a pairing authorization command associated with the target controlled device based on the identification information and wireless reception parameters of the target controlled device includes: Based on the wireless receiving parameters of the target controlled device, a pairing verification key adapted to the wireless communication specifications of the target controlled device is obtained; The identity information of the target controlled device, the pairing verification key, and the pairing operation parameters are encrypted and integrated to obtain the initial authorization data; Add an anti-tampering verification code and a host computer identity signature to the initial authorization data to generate a paired authorization instruction associated with the target controlled device.

3. The pairing method for the remote control as described in claim 1, characterized in that, After the step of sending the pairing authorization command to the target controlled device to trigger the target controlled device to switch to a pairable state, the pairing method of the remote control further includes: Receive the pairing result information returned by the target controlled device and the remote controller after pairing is completed, and archive the pairing result information with this pairing; The pairing results are compared and analyzed according to the pairing process optimization rules to determine the parameter adjustment space in the pairing process; Based on the parameter adjustment space, combined with the deployment environment and operating status of the controlled device, and the parameter information of the remote controller, a pairing optimization parameter set adapted to the controlled device and the remote controller is generated; The pairing optimization parameter set is sent to the corresponding controlled device and the remote controller to complete the parameter update of the controlled device and the remote controller.

4. A pairing method for a remote control, characterized in that, Applied to a target controlled device, the method includes: In response to the pairing authorization command issued by the host computer, the pairing timer window of the target controlled device is started, and the target controlled device is switched to a pairable state; Within the effective duration of the pairing time window, the parsed data of the remote control identity identifier, pairing verification key, device type matching identifier, and group affiliation identifier contained in the candidate signal are extracted, and the authorization control rules in the current pairing authorization instruction are retrieved. The candidate signal is the signal sent by the target controlled device in the pairable state. The parsed data of the candidate signals are matched with the authorization control rules for this pairing in all dimensions to filter out signals that meet the authorization requirements for this pairing and determine them as the pairing request signals for this pairing. The remote control corresponding to the pairing request signal is bidirectionally linked to the target controlled device.

5. The pairing method for the remote control as described in claim 4, characterized in that, The steps of responding to the pairing authorization command issued by the host computer, starting the pairing timer window of the target controlled device, and switching the target controlled device to a pairable state include: Upon receiving the pairing authorization command sent by the host computer, the identity information of the pairing authorization command is parsed to obtain the identity information of the pairing authorization command; After confirming that the identity information matches the identity of the target controlled device, a pairing mode trigger signal is generated according to the pairing authorization instruction; Based on the pairing mode trigger signal, a pairing timer window of fixed duration is started, and the wireless receiving module of the target controlled device is switched to the pairable state. Based on the pairable state, the control unit switches its own status indicator to a pairing process prompt state and sends the status information of the pairing window back to the host computer.

6. The pairing method for the remote control as described in claim 4, characterized in that, After the steps of responding to the pairing authorization command issued by the host computer, starting the pairing timer window of the target controlled device, and switching the target controlled device to a pairable state, the pairing method of the remote control further includes: Based on the pairable state, the wireless communication channel is locked and external noise interference is shielded to construct a pairing signal detection environment; During the effective time period of the pairing timing window, the wireless radio frequency signal of the pairing signal detection environment is collected at a fixed timing period; The wireless radio frequency signal is screened step by step according to the encoding rules to filter out invalid interference signals and obtain the candidate signal. By verifying the identity information carried in the candidate signal, the pairing request signal is determined and received by the wireless receiving module within the pairing timing window.

7. The pairing method for the remote control as described in claim 4, characterized in that, After the steps of responding to the pairing authorization command issued by the host computer, starting the pairing timer window of the target controlled device, and switching the target controlled device to a pairable state, the pairing method of the remote control further includes: If the target controlled device does not receive a verified pairing request signal before the pairing time window is zeroed, a pairing failure trigger signal is generated. Based on the pairing failure trigger signal, the pairing identification channel of its own wireless receiving module is turned off, and a pairing failure result analysis command is generated; Based on the failure result analysis instructions, organize the pairing records and failure reasons for this pairing operation to obtain the failure traceability record; After associating the failure tracing record with the current pairing, the failure tracing record is uploaded to the host computer.

8. The pairing method for the remote control as described in claim 4, characterized in that, The step of bidirectionally binding the remote control corresponding to the pairing request signal with the target controlled device includes: Upon receiving the pairing request signal, a pairing confirmation signal with the target controlled device is triggered; The pairing confirmation signal is sent to the remote controller to establish a pairing and binding channel between the target controlled device and the remote controller; Based on the pairing and binding channel, a two-way interactive binding is performed with the remote controller to complete the pairing process between the remote controller and the target controlled device.

9. A pairing device for a remote control, characterized in that, The pairing device for the remote control includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the pairing method for the remote control as described in any one of claims 1 to 8.

10. A storage medium, characterized in that, The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, it implements the steps of the pairing method for the remote control as described in any one of claims 1 to 8.

Images