Method and device for interaction between controller and human-computer interaction equipment, equipment and medium

Abstract

The invention provides a method and device for interaction between a controller and human-computer interaction equipment, equipment and a medium, the method is suitable for a many-to-many network framework, and comprises the following steps: when a binding request sent by one of the human-computer interaction equipment is received, performing permission verification based on a target equipment identifier; if the permission verification is passed, detecting whether the current controller is bound with a man-machine interaction device or not; if the current controller is not bound with one of the man-machine interaction devices, binding the current controller with one of the man-machine interaction devices; carrying out heartbeat detection; if the heartbeat detection is successful, judging whether an operation instruction sent by one man-machine interaction device is received within a preset duration after the heartbeat detection is successful; and if the heartbeat detection fails or an operation instruction sent by one of the man-machine interaction equipment is not received within a preset time period after the heartbeat detection succeeds, releasing the binding between the one of the man-machine interaction equipment and the current controller. According to the invention, flexible connection between any man-machine interaction device and any controller can be realized, and multi-task parallel operation is supported.

Description

Technical Field

[0001] The present invention relates to the field of semiconductor manufacturing technology, and in particular to a method, device, equipment and medium for interaction between a controller and a human-computer interaction device. Background Art

[0002] In the field of semiconductor equipment control, semiconductor equipment is generally controlled through a human-machine interaction system consisting of a human-machine interface device (HMI) and a controller (such as a programmable logic controller (PLC). For example, wafer cleaning equipment typically includes multiple independent process modules, each of which is controlled by a dedicated controller, and each controller is connected to a corresponding human-machine interaction device. Traditional human-machine interaction systems mainly have the following two architectures: The first architecture is a one-to-one configuration where one HMI device corresponds to one controller. Under this architecture, operators must operate the corresponding controller on the HMI device at a specific workstation. This lacks flexibility and cannot support dynamic collaboration. When cross-station scheduling is required, operators must frequently move to different HMI devices.

[0003] The second architecture is a one-to-many architecture where one HMI device corresponds to multiple controllers. For scenarios where multiple devices need to operate in coordination, this architecture does not support a single HMI device operating multiple controllers simultaneously. Summary of the Invention

[0004] In order to solve the problem in the prior art that the interaction flexibility between the controller and the human-computer interaction device is insufficient and cannot meet the dynamic collaborative operation of multiple controllers, the present invention provides a method, device, equipment and medium for interaction between the controller and the human-computer interaction device.

[0005] In order to achieve the above object, the present invention adopts the following technical solutions: In a first aspect, the present invention provides a method for interacting between a controller and a human-computer interaction device, wherein a plurality of the controllers and a plurality of the human-computer interaction devices are interconnected via a switch, the method being applicable to the controllers and comprising: When receiving a binding request sent by one of the human-computer interaction devices, and the binding request includes a target device identifier of the one of the human-computer interaction devices, performing an authority check based on the target device identifier; If the permission check is passed, then check whether the current controller has been bound to a human-computer interaction device; If not bound, binding the current controller with one of the human-computer interaction devices so that the current controller and one of the human-computer interaction devices can perform data interaction; Performing heartbeat detection to detect whether the controller and one of the human-computer interaction devices are currently in a normal communication connection state; If the heartbeat detection is successful, determining whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the success; If the heartbeat detection fails, or if no operation instruction is received from one of the human-computer interaction devices within a predetermined time period after the heartbeat detection succeeds, the binding between one of the human-computer interaction devices and the current controller is released.

[0006] Furthermore, the method further includes: when an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the heartbeat detection is successful, executing the operation instruction and returning to the step of performing the heartbeat detection.

[0007] Furthermore, after the permission check is passed, the method further includes: Identifying a target permission level corresponding to the target device identifier; When an operation instruction is received from one of the human-computer interaction devices within a predetermined time period after the heartbeat detection is successful, determining whether the operation instruction matches the target permission level; if so, executing the operation instruction; if not, refusing to execute the operation instruction; Return to the step of performing heartbeat detection.

[0008] Furthermore, after binding with one of the human-computer interaction devices, the method further includes: if an operation instruction sent by the other human-computer interaction device is received, refusing to execute the operation instruction.

[0009] Furthermore, the performing of permission verification based on the target device identification includes: The target device identification is matched with the pre-stored device identification. If the match is successful, the permission check is passed.

[0010] Furthermore, the method further comprises: The binding request currently received by the controller, the bound human-computer interaction device, and the received operation instruction are recorded in the operation log.

[0011] Furthermore, the method further includes: encrypting data during the data interaction between the controller and one of the human-computer interaction devices.

[0012] In a second aspect, the present invention provides an apparatus for interacting between a controller and a human-computer interaction device, wherein a plurality of the controllers and a plurality of the human-computer interaction devices are interconnected via a switch, the apparatus being applicable to the controller and comprising: an authority verification module, configured to, upon receiving a binding request sent by one of the human-computer interaction devices, and the binding request including a target device identifier of the one of the human-computer interaction devices, perform authority verification based on the target device identifier; a binding module, configured to detect whether the current controller has been bound to a human-computer interaction device when the permission check passes, and if not, bind the current controller to one of the human-computer interaction devices so that the current controller and one of the human-computer interaction devices can perform data interaction; A heartbeat detection module, configured to perform heartbeat detection to detect whether the controller and one of the human-computer interaction devices are currently in a normal communication connection state; A timeout detection module is used to determine whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the heartbeat detection is successful; The binding release module is used to release the binding between one of the human-computer interaction devices and the current controller when the heartbeat detection fails or no operation instruction sent by the one of the human-computer interaction devices is received within a predetermined time after the heartbeat detection succeeds.

[0013] In a third aspect, the present invention provides a semiconductor device, comprising multiple process modules, multiple controllers and multiple human-computer interaction devices, wherein the multiple process modules and the multiple controllers are connected one-to-one, wherein the multiple controllers and the multiple human-computer interaction devices are interconnected through a switch, and the controller is used to implement the method of interaction between the controller and the human-computer interaction device as described above.

[0014] In a fourth aspect, the present invention provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for interaction between the controller and the human-computer interaction device as described above is implemented.

[0015] In a fifth aspect, the present invention provides a computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the method for interaction between the controller and the human-computer interaction device as described above is implemented.

[0016] By adopting the above technical solution, the present invention has the following beneficial effects: This invention transcends the limitations of traditional one-to-one or one-to-many architectures. By interconnecting multiple controllers and multiple human-computer interaction devices through switches, it constructs a many-to-many parallel interactive network system. Furthermore, by providing corresponding intelligent interaction methods, it enables real-time data interaction between any human-computer interaction device and any controller within the same network system, supporting multiple groups of interactive operations simultaneously, significantly improving the operational parallelism and management efficiency of the network system. Furthermore, the present invention allows human-computer interaction devices to flexibly switch to interacting with any idle controller (i.e., not bound to other human-computer interaction devices) at any time as needed. When a controller is idle, the human-computer interaction device can quickly bind to it and interact with data based on user instructions, eliminating the need for complex manual configuration or restart operations. Furthermore, to ensure control stability and security, the present invention incorporates an exclusive interaction mode. This mode allows a controller to bind to the currently requesting human-computer interaction device only when it is idle. Once bound, the controller automatically cuts off the interaction privileges of other human-computer interaction devices, achieving secure interaction isolation and eliminating the risk of control chaos. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 This is a diagram of the network system architecture consisting of multiple controllers and multiple human-computer interaction devices in the present invention; Figure 2 This is a flow chart of a method for interaction between a controller and a human-computer interaction device in Example 1 of the present invention; Figure 3 This is a structural block diagram of a system for interaction between a controller and a human-computer interaction device in Example 3 of the present invention; Figure 4 This is a hardware architecture diagram of the electronic device in Example 4 of the present invention. DETAILED DESCRIPTION In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention is further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0018] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "the," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

[0019] The present invention provides a method, apparatus, equipment and medium for interaction between a controller and a human-computer interaction device, so as to achieve a breakthrough in the dynamic interaction capability between any human-computer interaction device and any controller in the same equipment cluster, and can meet the high-precision control requirements of multi-station collaborative monitoring and multi-process parallel operation in semiconductor equipment.

[0020] Example 1 This embodiment provides a method for interacting with a human-computer interaction device. Figure 1 The distributed system architecture shown in Figure 1 includes multiple controllers and multiple human-machine interaction devices connected via a switch (e.g., an Ethernet switch). These devices establish a communication link based on the Modbus TCP protocol. Each controller and each human-machine interaction device is assigned a unique static ID as its identifier. These IDs can be the same or different for each controller and each human-machine interaction device.

[0021] In this embodiment, the controller includes but is not limited to a PLC controller, and the human-computer interaction device includes but is not limited to a touch screen. Communication parameters are configured in the configuration software of the human-computer interaction device, and the interface of the human-computer interaction device displays the identifier of the controller currently bound to it.

[0022] The above-mentioned distributed system architecture can be applied to control semiconductor equipment, such as wafer cleaning equipment, wherein each controller is connected to each process module of the semiconductor equipment in a one-to-one correspondence to monitor and operate the corresponding process module.

[0023] When a user requires a human-computer interaction device to interact with a designated controller, an interaction instruction is input to the corresponding human-computer interaction device. The interaction instruction carries the identifier of the corresponding controller to instruct the human-computer interaction device to interact with the corresponding controller.

[0024] When the human-computer interaction device receives an interaction command from the user, it first checks whether it has been bound to another controller (except the specified controller). If it has been bound, it first unbinds itself from the other controller and then sends a binding request to the corresponding controller. If it has not been bound, it directly sends a binding request to the corresponding controller. The binding request includes the target device identifier corresponding to the requesting human-computer interaction device.

[0025] When the human-computer interaction device sends a binding request, the subsequent steps will be executed by the corresponding controller. The method of interaction between the controller and the human-computer interaction device provided in this embodiment is applicable to any controller, such as Figure 2 As shown, the method specifically includes the following steps: Step S1: When a binding request is received from one of the human-computer interaction devices, and the binding request includes the target device identifier corresponding to one of the human-computer interaction devices, a permission check is performed based on the target device identifier. If the permission check passes, step S2 is executed. Otherwise, the binding is rejected, and information indicating that the permission check failed is fed back to one of the human-computer interaction devices.

[0026] In one implementable method, the specific process of performing permission verification in this step is as follows: matching the target device identifier with multiple pre-stored device identifiers. If it matches one of the pre-stored device identifiers successfully, the permission verification passes; if it does not match any of the pre-stored device identifiers, the permission verification fails.

[0027] Step S2, detect whether the current controller has been bound to a human-computer interaction device. If it has been bound, in order to ensure the stability and security of the control, no subsequent operations will be performed to ensure that the bound human-computer interaction device can exclusively interact with the current controller; if it has not been bound, it means that the current controller is in an idle state, and then execute step S3.

[0028] Step S3: Bind the current controller to one of the human-computer interaction devices so that the current controller and the one of the human-computer interaction devices can perform data interaction.

[0029] Step S4, starting the heartbeat detection to detect whether the current controller and one of the human-computer interaction devices are in a normal communication connection state. If the heartbeat detection is successful, step S5 is executed; otherwise, step S6 is executed.

[0030] In one practicable manner, the following steps are used to perform heartbeat detection: a heartbeat request packet is sent to one of the human-computer interaction devices at a predetermined period (e.g., 100ms); if a response packet is received from one of the human-computer interaction devices in response to the heartbeat request packet, the heartbeat detection is successful; otherwise, the heartbeat detection fails.

[0031] Step S5, determining whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time (eg, 30 seconds) after the heartbeat detection is successful. If not, executing step S6; otherwise, executing step S7.

[0032] Step S6: unbinding one of the human-computer interaction devices from the current controller.

[0033] This step actively unbinds the controller so that the controller resources can be released in time for interaction with other human-computer interaction devices.

[0034] S7, executing the operation instruction sent by one of the human-computer interaction devices, and returning to step S4 to perform heartbeat detection.

[0035] Thus, real-time control of the current controller by one of the human-computer interaction devices is achieved.

[0036] In addition, after step S3, if the current controller receives an operation instruction sent by other human-computer interaction devices except the one of the human-computer interaction devices, it refuses to execute the operation instruction.

[0037] Through the above steps, the present invention breaks through the limitations of traditional one-to-one architecture or one-to-many architecture. By connecting multiple controllers and multiple human-computer interaction devices through switches, a many-to-many parallel interactive network system is constructed. At the same time, by providing corresponding intelligent interaction methods, real-time data interaction between any human-computer interaction device and any controller in the same network system is realized, and multiple groups of interactive operations are supported to be carried out simultaneously, which greatly improves the operational parallelism and management efficiency of the network system.

[0038] Moreover, the present invention can enable the human-computer interaction device to flexibly switch to interact with any idle controller (i.e., not bound to other human-computer interaction devices) at any time as needed. When a controller is idle, the human-computer interaction device can quickly bind to the controller and interact with data according to user instructions, without the need for complicated manual configuration or restart operations.

[0039] In addition, in order to ensure the stability and security of control, the present invention has designed an exclusive interaction mode. It can only bind to the currently requested human-computer interaction device when the controller is idle. After binding, the interaction permissions of other human-computer interaction devices will be automatically cut off, realizing interactive security isolation and eliminating the risk of control chaos.

[0040] Preferably, this embodiment can also effectively avoid the risk of command conflicts and operational errors caused by the simultaneous control of multiple human-computer interaction devices through data encryption transmission and operation log auditing mechanisms.

[0041] Specifically, the method of this embodiment may further include: encrypting data during the process of data interaction between the current controller and one of the human-computer interaction devices.

[0042] The method of this embodiment may further include: recording the binding request received by the current controller, the bound human-computer interaction device, and the received operation instruction in an operation log to support audit tracking.

[0043] Example 2 This embodiment adds the following permission identification step based on the method of embodiment 1: after the permission verification is passed, the target permission level corresponding to the target device identifier is identified.

[0044] In one implementation, the permission levels can be divided into three levels: monitoring level, operation level, and management level. The monitoring level only allows read operations, the operation level allows read and write operations, and the management level allows execution of specific instructions in addition to the operation level.

[0045] In this embodiment, the controller pre-stores permission levels corresponding to different device identifiers, and can determine a target permission level corresponding to a target device identifier by performing matching.

[0046] Due to the addition of the above-mentioned permission identification step, this embodiment adjusts step S7 of Example 1 to (the other steps are the same as Example 1): determine whether the operation instruction sent by one of the human-computer interaction devices matches the target permission level; if so, execute the operation instruction; if not, refuse to execute the operation instruction; then, return to step S4 to perform heartbeat detection.

[0047] This embodiment further improves the security of the network system by introducing device identification-based permission hierarchical control based on the many-to-many flexible interaction and exclusive control mechanism of embodiment 1.

[0048] Example 3 This embodiment provides a device for interacting with a controller and a human-computer interaction device, wherein Figure 3 As shown, multiple controllers and multiple human-computer interaction devices are interconnected through switches, forming a many-to-many distributed network architecture.

[0049] The device of this embodiment is applicable to any controller, and Figure 3 As shown, the device specifically includes the following modules: The permission verification module 11 is configured to perform permission verification based on the target device identifier when receiving a binding request sent by one of the human-computer interaction devices, and the binding request includes the target device identifier of the one of the human-computer interaction devices; A binding module 12 is used to detect whether the current controller has been bound to a human-computer interaction device when the permission check is passed. If not, the current controller is bound to one of the human-computer interaction devices so that the current controller and the one of the human-computer interaction devices can perform data interaction; A heartbeat detection module 13 is used to perform heartbeat detection to detect whether the current controller and one of the human-computer interaction devices are in a normal communication connection state; A timeout detection module 14 is configured to determine, when the heartbeat detection succeeds, whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the success; The binding release module 15 is configured to release the binding between one of the human-computer interaction devices and the current controller when the heartbeat detection fails or no operation instruction is received from the one of the human-computer interaction devices within a predetermined time period after the heartbeat detection succeeds.

[0050] In one practicable manner, the apparatus of this embodiment further includes an operation execution module for executing the operation instruction and re-calling the heartbeat detection module 13 when receiving an operation instruction sent by one of the human-computer interaction devices within a predetermined time period after the heartbeat detection is successful.

[0051] In one practicable embodiment, the apparatus of this embodiment further includes a level identification module and an operation execution module. The level identification module is configured to identify the target permission level corresponding to the target device identifier; the operation execution module is configured to, upon receiving an operation instruction sent by one of the human-computer interaction devices within a predetermined time period after a successful heartbeat detection, determine whether the operation instruction matches the target permission level; if so, execute the operation instruction and re-invoke the heartbeat detection module 13; if not, refuse to execute the operation instruction and re-invoke the heartbeat detection module 13.

[0052] In one practicable manner, after the current controller is bound to one of the human-computer interaction devices, if an operation instruction sent by another human-computer interaction device is received, the operation execution module refuses to execute the operation instruction.

[0053] In one practicable manner, the permission verification module 11 is specifically configured to match the target device identification with a pre-stored device identification. If the match is successful, the permission verification is passed.

[0054] In an practicable manner, the apparatus of this embodiment further includes: a log recording module, configured to record in an operation log the binding requests received by the current controller, bound human-computer interaction devices, and received operation instructions.

[0055] In an practicable manner, the apparatus of this embodiment further includes: an encryption module, configured to encrypt data during data interaction between the current controller and one of the human-computer interaction devices.

[0056] This embodiment breaks through the limitations of traditional one-to-one or one-to-many architectures. By connecting multiple controllers and multiple human-computer interaction devices through switches, a many-to-many parallel interactive network system is constructed. At the same time, by providing corresponding interaction methods, real-time data interaction between any human-computer interaction device and any controller in the same network is achieved, supporting multiple groups of human-computer operations to be carried out simultaneously, greatly improving the system's operational parallelism and management efficiency.

[0057] Moreover, this embodiment can enable the human-computer interaction device to flexibly switch to interact with any idle controller (i.e., not bound to other human-computer interaction devices) at any time as needed. When a controller is idle, the human-computer interaction device can quickly bind to and interact with the controller according to user instructions without the need for complicated manual configuration or restart operations.

[0058] In addition, in order to ensure the stability and security of control, this embodiment has designed an exclusive interaction mode. It can only be bound to one of the human-computer interaction devices when the controller is idle. After binding, the interaction permissions of other human-computer interaction devices will be automatically cut off, realizing interactive security isolation and eliminating the risk of control confusion.

[0059] Embodiment 4 This embodiment provides a semiconductor device, comprising multiple process modules, multiple controllers, and multiple human-computer interaction devices. The multiple process modules are connected to the multiple controllers in a one-to-one correspondence, the multiple controllers are interconnected with the multiple human-computer interaction devices via a switch, and the controllers are configured to implement the method for interaction between the controllers and the human-computer interaction devices provided in Embodiment 1.

[0060] In this embodiment, the semiconductor device is, for example, a wafer cleaning device, the human-computer interaction device is preferably a touch screen, and the controller is preferably a PLC.

[0061] Example 5 This embodiment provides an electronic device, which can be expressed in the form of a computing device (for example, a server device), including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps of the method for interaction between the controller and the human-computer interaction device provided in Example 1 can be implemented.

[0062] Figure 4 The hardware structure diagram of this embodiment is shown in FIG. Figure 4 As shown, the electronic device 30 specifically includes: At least one processor 31, at least one memory 32, and a bus 33 for connecting different system components (including the processor 31 and the memory 32), wherein: The bus 33 includes a data bus, an address bus, and a control bus.

[0063] The memory 32 includes a volatile memory, such as a random access memory (RAM) 321 and / or a cache memory 322 , and may further include a read-only memory (ROM) 323 .

[0064] The memory 32 also includes a program / utility 325 having a set (at least one) of program modules 324, such program modules 324 including but not limited to: an operating system, one or more application programs, other program modules and program data, each of which or some combination may include an implementation of a network environment.

[0065] The processor 31 executes various functional applications and data processing by running the computer program stored in the memory 32, such as the steps of the method for interaction between the controller and the human-computer interaction device provided in Example 1 of the present invention.

[0066] The electronic device 30 can further communicate with one or more external devices 34 (e.g., a keyboard, pointing device, etc.). This communication can occur via an input / output (I / O) interface 35. Furthermore, the electronic device 30 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 36. The network adapter 36 communicates with other modules of the electronic device 30 via a bus 33. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with the electronic device 30, including but not limited to microcode, device drivers, redundant processors, external disk drive arrays, RAID (RAID) systems, tape drives, and data backup storage systems.

[0067] It should be noted that although several units / modules or sub-units / modules of the electronic device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, depending on the embodiment of the present application, the features and functions of two or more units / modules described above can be embodied in one unit / module. Conversely, the features and functions of one unit / module described above can be further divided and embodied by multiple units / modules.

[0068] Example 6 This embodiment provides a computer-readable storage medium having a computer program stored thereon. When the program is executed by a processor, the steps of the method for interaction between a controller and a human-computer interaction device provided in Example 1 are implemented.

[0069] The readable storage medium may include, but is not limited to, a portable disk, a hard disk, a random access memory, a read-only memory, an erasable programmable read-only memory, an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0070] Although specific embodiments of the present invention have been described above, those skilled in the art will appreciate that these are merely illustrative and that the scope of the present invention is defined by the appended claims. Those skilled in the art may make various changes or modifications to these embodiments without departing from the principles and essence of the present invention, and such changes and modifications are intended to fall within the scope of the present invention.

Claims

1. A method for interaction between a controller and a human-computer interaction device, characterized in that: A plurality of the controllers and a plurality of the human-computer interaction devices are connected to each other via a switch, and the method is applicable to the controllers and includes: When receiving a binding request sent by one of the human-computer interaction devices, and the binding request includes a target device identifier of the one of the human-computer interaction devices, performing an authority check based on the target device identifier; If the permission check is passed, then check whether the current controller has been bound to a human-computer interaction device; If not bound, binding the current controller with one of the human-computer interaction devices so that the current controller and one of the human-computer interaction devices can perform data interaction; Performing heartbeat detection to detect whether the controller and one of the human-computer interaction devices are currently in a normal communication connection state; If the heartbeat detection is successful, determining whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the success; If the heartbeat detection fails, or if no operation instruction is received from one of the human-computer interaction devices within a predetermined time period after the heartbeat detection succeeds, the binding between one of the human-computer interaction devices and the current controller is released.

2. The method according to claim 1, wherein The method further includes: when an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the heartbeat detection is successful, executing the operation instruction and returning to the step of performing the heartbeat detection.

3. The method according to claim 1, wherein After the permission check is passed, the method further includes: Identifying a target permission level corresponding to the target device identifier; When an operation instruction is received from one of the human-computer interaction devices within a predetermined time period after the heartbeat detection is successful, determining whether the operation instruction matches the target permission level; if so, executing the operation instruction; if not, refusing to execute the operation instruction; Return to the step of performing heartbeat detection.

4. The method according to claim 1, wherein The performing permission verification based on the target device identification includes: matching the target device identification with a pre-stored device identification; if the match is successful, the permission verification is passed.

5. The method according to any one of claims 1 to 4, wherein The method further comprises: The binding request currently received by the controller, the bound human-computer interaction device, and the received operation instruction are recorded in the operation log.

6. The method according to any one of claims 1 to 4, wherein The method further includes: encrypting data during the current data interaction between the controller and one of the human-computer interaction devices.

7. The method according to any one of claims 1 to 4, wherein The method further includes: after being bound to one of the human-computer interaction devices, if an operation instruction sent by another of the human-computer interaction devices is received, refusing to execute the operation instruction.

8. A device for interaction between a controller and a human-computer interaction device, characterized in that: The plurality of controllers and the plurality of human-computer interaction devices are interconnected via a switch, and the apparatus is applicable to the controllers and includes: an authority verification module, configured to, upon receiving a binding request sent by one of the human-computer interaction devices, and the binding request including a target device identifier of the one of the human-computer interaction devices, perform authority verification based on the target device identifier; a binding module, configured to detect whether the current controller has been bound to a human-computer interaction device when the permission check passes, and if not, bind the current controller to one of the human-computer interaction devices so that the current controller and one of the human-computer interaction devices can perform data interaction; A heartbeat detection module, configured to perform heartbeat detection to detect whether the controller and one of the human-computer interaction devices are currently in a normal communication connection state; A timeout detection module is used to determine whether an operation instruction sent by one of the human-computer interaction devices is received within a predetermined time period after the heartbeat detection is successful; The binding release module is used to release the binding between one of the human-computer interaction devices and the current controller when the heartbeat detection fails or no operation instruction sent by the one of the human-computer interaction devices is received within a predetermined time after the heartbeat detection succeeds.

9. A semiconductor device comprising a plurality of process modules, a plurality of controllers and a plurality of human-computer interaction devices, wherein the plurality of process modules and the plurality of controllers are connected in a one-to-one correspondence, characterized in that: The plurality of controllers and the plurality of human-computer interaction devices are connected to each other via a switch, and the controller is used to implement the method for interaction between the controller and the human-computer interaction device according to any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that: When the processor executes the computer program, the method for interaction between the controller and the human-computer interaction device according to any one of claims 1 to 7 is implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for interaction between a controller and a human-computer interaction device according to any one of claims 1 to 7 is implemented.

Images