Unbinding method, device and equipment, computer readable storage medium and program product

Abstract

The invention provides an unbinding method, apparatus and device, a computer readable storage medium and a program product. The method comprises the steps of receiving an unbinding request sent by a peripheral component; acquiring a first equipment identifier of the peripheral component according to the unbinding request; determining a second device identifier associated with the first device identifier; and releasing the association relationship between the second equipment identifier and the first equipment identifier so as to unbind the peripheral component and the operation entity corresponding to the second equipment identifier. According to the method and the device, the external component and the operation entity are unbound remotely through the unbinding device, a user does not need to unbind the external component through cold-drawing plugging or hot-drawing plugging, the unbinding process of the external component is simplified, and the unbinding convenience of the external component is improved.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to an unbinding method, apparatus, device, computer-readable storage medium, and program product. Background Art

[0002] Peripheral components refer to the components in a terminal device responsible for interacting with the user. Peripheral components are, for example, a keyboard, a mouse, a joystick, a camera, a display, a microphone, a speaker, a scanner, and a printer, etc.

[0003] Peripheral components are usually bound to a computing entity one-to-one. When a peripheral component needs to be unbound, it needs to be removed by means of cold plugging or hot plugging, and the unbinding process of the peripheral component is relatively cumbersome. Summary of the Invention

[0004] The present invention provides an unbinding method, apparatus, device, computer-readable storage medium, and program product to solve the problem that the unbinding process of peripheral components is relatively cumbersome.

[0005] On the one hand, the present invention provides an unbinding method applied to an unbinding device. The unbinding device is communicatively connected to a peripheral component and a computing entity. The unbinding method includes:

[0006] Receiving an unbinding request sent by the peripheral component;

[0007] Obtaining a first device identifier of the peripheral component according to the unbinding request;

[0008] Determining a second device identifier associated with the first device identifier;

[0009] Releasing the association relationship between the second device identifier and the first device identifier to unbind the peripheral component from the computing entity corresponding to the second device identifier.

[0010] Optionally, the step of determining the second device identifier associated with the first device identifier includes:

[0011] Obtaining a target computing entity for which the peripheral component requests unbinding according to the unbinding request;

[0012] Determining the device identifier corresponding to the target computing entity as the second device identifier associated with the first device identifier.

[0013] Optionally, the step of determining the second device identifier associated with the first device identifier includes:

[0014] Determining each third device identifier associated with the first device identifier, where the third device identifier is used to indicate the device identifier of the computing entity to which the peripheral component is bound;

[0015] Obtaining the priority corresponding to each computing entity bound to the peripheral component;

[0016] The third device identifier corresponding to the computing entity corresponding to the highest priority is used to determine the second device identifier associated with the first device identifier.

[0017] Optionally, before the step of disassociating the second device identifier from the first device identifier, the step further includes:

[0018] Receiving a binding request sent by the peripheral component;

[0019] Acquire, according to the binding request, a first device identifier of the peripheral component and a second device identifier of a computing entity to which the peripheral component requests to be bound;

[0020] Configure and store an association relationship between the first device identifier and the second device identifier.

[0021] Optionally, the step of configuring and storing an association relationship between the first device identifier and the second device identifier includes:

[0022] Obtaining a registration request sent by the peripheral component;

[0023] Acquire a fourth device identification of the peripheral component based on the registration request, and store the fourth device identification;

[0024] When the first device identifier matches the fourth device identifier, it is determined that the peripheral component has been registered, and an association relationship between the first device identifier and the second device identifier is configured and stored.

[0025] Optionally, the step of configuring and storing an association relationship between the first device identifier and the second device identifier includes:

[0026] Sending a registration request to a computing entity corresponding to the second device identifier;

[0027] When receiving the registration success information fed back by the computing entity corresponding to the second device identifier, the second device identifier is stored, and an association relationship between the first device identifier and the second device identifier is configured and stored.

[0028] On the other hand, the present invention also provides an unbinding device, comprising:

[0029] A receiving module, used for receiving an unbinding request sent by a peripheral component;

[0030] An acquisition module, configured to acquire a first device identifier of the peripheral component according to the unbinding request;

[0031] A determination module, configured to determine a second device identifier associated with the first device identifier;

[0032] A disassociation module, configured to disassociate the second device identifier from the first device identifier, so as to disassociate the peripheral component from the computing entity corresponding to the second device identifier.

[0033] On the other hand, the present invention further provides an unbinding device, including: a memory and a processor;

[0034] The memory stores computer-executable instructions;

[0035] The processor executes the computer-executable instructions stored in the memory, so that the processor executes the unbinding method as described above.

[0036] On the other hand, the present invention further provides a computer-readable storage medium, in which computer-executable instructions are stored, and when the computer-executable instructions are executed by a processor, they are used to implement the unbinding method as described above.

[0037] On the other hand, the present invention further provides a computer program product, including a computer program, and when the computer program is executed by a processor, it is used to implement the unbinding method as described above.

[0038] The unbinding method, device, equipment, computer-readable storage medium and program product provided by the present invention receive an unbinding request sent by a peripheral component, obtain the first device identifier of the peripheral component according to the unbinding request, determine the second device identifier associated with the first device identifier, and disassociate the second device identifier from the first device identifier to disassociate the peripheral component from the computing entity corresponding to the second device identifier. In the present invention, the peripheral component and the computing entity are remotely unbound through the unbinding device, and there is no need for the user to unbind the peripheral component by cold plugging or hot plugging, which simplifies the unbinding process of the peripheral component and improves the unbinding convenience of the peripheral component. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure.

[0040] Figure 1 It is a schematic diagram of the scenario involved in the unbinding method of the present invention;

[0041] Figure 2 It is a schematic flowchart of the first embodiment of the unbinding method of the present invention;

[0042] Figure 3 It is a schematic flowchart of the second embodiment of the unbinding method of the present invention;

[0043] Figure 4 Schematic flowchart of the third embodiment of the unbinding method of the present invention;

[0044] Figure 5 Schematic flowchart of the fourth embodiment of the unbinding method of the present invention;

[0045] Figure 6 Schematic diagram of the modules of the unbinding device of the present invention;

[0046] Figure 7 Schematic diagram of the hardware structure of the unbinding device of the present invention.

[0047] Through the above-mentioned drawings, the specific embodiments of the present disclosure have been shown, and more detailed descriptions will be given later. These drawings and written descriptions are not intended to limit the scope of the concept of the present disclosure in any way, but to illustrate the concept of the present disclosure to those skilled in the art by referring to specific embodiments. Detailed Description of the Embodiments

[0048] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0049] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards, and corresponding operation entrances are provided for users to choose to authorize or refuse.

[0050] Peripheral components refer to the components in a terminal device responsible for interacting with the user. Peripheral components are, for example, keyboards, mice, gamepads, cameras, displays, microphones, speakers, scanners, and printers.

[0051] The inventors of this patent found that peripheral components are usually bound to computing entities one by one. When a peripheral component needs to be unbound, it needs to be removed by cold plugging or hot plugging, and the unbinding process of peripheral components is relatively cumbersome.

[0052] Therefore, the inventors of this patent thought of remotely unbinding the peripheral component from the computing entity through an unbinding device, eliminating the need for the user to unbind the peripheral component by cold plugging or hot plugging, simplifying the unbinding process of the peripheral component, and improving the convenience of unbinding the peripheral component.

[0053] Reference Figure 1 , Figure 1 is a schematic diagram of the scenario involved in the unbinding method of the present invention. Refer to Figure 1 , the unbinding device 100 is communicatively connected to the peripheral component 200 and the computing entity 300. The unbinding device 100 can be communicatively connected to multiple peripheral components 200, and can also be communicatively connected to multiple computing entities 300. The peripheral component 200 can be bound to the computing entity 300 one-to-one, and the peripheral component 200 can also be bound to multiple computing entities 300. In addition, multiple peripheral components 200 can also be bound to one computing entity 300. If the peripheral component 200 is bound to the computing entity 300, the device identifier of the peripheral component 200 and the device identifier of the computing entity 300 have an association relationship in the unbinding device 100. When the peripheral component 200 requests the unbinding device 100 to unbind, the unbinding device 100 unbinds the association relationship corresponding to the peripheral component 200 and the computing entity 300 that requests unbinding, thereby completing the binding between the peripheral component 200 and the computing entity 300.

[0054] The following uses specific embodiments to elaborate in detail on the technical solutions of the present invention and how the technical solutions of the present application solve the above technical problems. These several specific embodiments below can be combined with each other, and for the same or similar concepts or processes, they may not be repeated in some embodiments. The following will describe the embodiments of the present invention with reference to the accompanying drawings.

[0055] Reference Figure 2 , Figure 2 is a flowchart of the first embodiment of the unbinding method of the present invention. The unbinding method includes the following steps:

[0056] Step S201, receiving an unbinding request sent by the peripheral component.

[0057] In this embodiment, the execution subject is the unbinding device. For ease of description, the unbinding device is hereinafter referred to as the device. The device can be any terminal device with communication functions.

[0058] The computer system includes peripheral components and computing entities. The peripheral components include keyboards, mice, gamepads, cameras, monitors, microphones, speakers, scanners, printers, etc. The computing entity is a component in the computer system responsible for data storage, data calculation, etc. The computing entity can be a local device, a remote device, or a virtual device. Examples of virtual devices are virtual machines, containers, etc. The computing entity includes computer main bodies, game console main bodies, set-top boxes, cloud computing, cloud storage, etc.

[0059] The peripheral component is communicatively connected to the computing entity through the device, that is, the communication between the peripheral component and the computing entity is transmitted through the device.

[0060] The apparatus may bind the peripheral component to the computing entity. Exemplarily, an association relationship may be set between the device identification of the peripheral component and the device identification of the computing entity, and the association relationship is used to indicate that the peripheral component is bound to the computing entity.

[0061] A peripheral component can be bound to multiple computing entities, and multiple peripheral components can also be bound to one computing entity. Of course, a peripheral component can also be bound to a computing entity one-to-one.

[0062] The peripheral component may initiate an unbinding request to the device. In one example, the peripheral component may be provided with an unbinding button, and after the user clicks the unbinding button, the peripheral component sends an unbinding request to the device, that is, the device receives the unbinding request sent by the peripheral component.

[0063] In another example, the peripheral component can perform input, for example, the peripheral component is a keyboard, and an unbinding request can be initiated to the device through the input of the keyboard.

[0064] In another example, the peripheral component may collect the user's voice, and if the voice involves unbinding, the peripheral component sends an unbinding request to the device.

[0065] Step S202: Acquire the first device identifier of the peripheral component according to the unbinding request.

[0066] The unbinding request carries a device identifier of the peripheral component, which is defined as a first device identifier. The device parses the unbinding request to obtain the first device identifier of the peripheral component.

[0067] Step S203: Determine a second device identifier associated with the first device identifier.

[0068] The peripheral component is bound to the computing entity, so the device stores the association relationship between the peripheral component and the computing entity. The device obtains the association relationship corresponding to the first device identifier, and then obtains the second device identifier associated with the first device identifier based on the association relationship. The second device identifier is the device identifier of the computing entity bound to the peripheral component.

[0069] Step S204: cancel the association between the second device identifier and the first device identifier, so as to unbind the peripheral component from the computing entity corresponding to the second device identifier.

[0070] After obtaining the second device identifier, the device removes the association between the first device identifier and the second device identifier, thereby unbinding the peripheral component from the computing entity corresponding to the second device identifier. By sending an unbinding request to the device, the computing entity and the peripheral component can be remotely unbound.

[0071] In this embodiment, a device receives an unbinding request sent by a peripheral component, obtains a first device identifier of the peripheral component according to the unbinding request, determines a second device identifier associated with the first device identifier, and releases the association between the second device identifier and the first device identifier to unbind the peripheral component from the computing entity corresponding to the second device identifier. In this embodiment, the unbinding of the peripheral component from the computing entity is remotely performed by an unbinding device, and there is no need for the user to unbind the peripheral component by cold plugging or hot plugging, which simplifies the unbinding process of the peripheral component and improves the convenience of unbinding the peripheral component.

[0072] Referring to Figure 3 , Figure 3 This is the second embodiment of the unbinding method of the present invention. Based on the first embodiment, step S203 includes:

[0073] Step S301: Obtain a target computing entity for which the peripheral component requests unbinding according to the unbinding request.

[0074] In this embodiment, the peripheral component is bound to multiple computing entities. Therefore, when the peripheral component sends an unbinding request to the device, the peripheral component specifies the computing entity for which the binding relationship needs to be released, that is, the computing entity requested by the peripheral component to be unbound is carried in the binding request.

[0075] The device parses the unbinding request to obtain the computing entity requested by the peripheral component to be unbound, and this computing entity is defined as the target computing entity.

[0076] Step S302: Determine the device identifier corresponding to the target computing entity as the second device identifier associated with the first device identifier.

[0077] After determining the target computing entity, the device determines the device identifier corresponding to the target computing entity as the second device identifier associated with the first device identifier.

[0078] In this embodiment, the device obtains the target computing entity requested by the peripheral component to be unbound based on the unbinding request, and thus determines the second device identifier associated with the first device identifier based on the device identifier of the target computing entity, without the need for the device to search for the second device identifier associated with the first device identifier from its own massive data, improving the unbinding efficiency.

[0079] Referring to Figure 4 , Figure 4 This is the third embodiment of the unbinding method of the present invention. Based on the first embodiment, step S203 includes:

[0080] Step S401: Determine each third device identifier associated with the first device identifier, where the third device identifier is used to indicate the device identifier of the computing entity to which the peripheral component is bound.

[0081] In this embodiment, a plurality of computing entities are bound to the peripheral component, that is, the first device identifier of the peripheral component stored in the device is associated with the device identifiers of a plurality of entity devices.

[0082] In this regard, the device obtains each third device identifier associated with the first device identifier, and the third device identifier is the device identifier of the computing entity bound to the peripheral component.

[0083] Step S402: Obtain the priority corresponding to each computing entity bound to the peripheral component.

[0084] Each computing entity bound to the peripheral component has a corresponding priority. The device preferentially sends the interaction information of the peripheral component to the computing entity with the highest priority, that is, the priority refers to the computing entity that the peripheral component preferentially controls.

[0085] The priority of the computing entity can be set by the user. Exemplarily, after the peripheral component binds each computing entity, it can obtain the names of each computing entity. The user sets the priorities of each computing entity based on the names of the computing entities, and then the peripheral component sends the setting information to the device for storage by the device. When the device subsequently transmits the interaction information of the peripheral component, it sends the interaction information to the computing entity with the highest priority.

[0086] Step S403: Determine the second device identifier associated with the first device identifier by using the third device identifier corresponding to the computing entity with the highest priority.

[0087] After the device determines the priority of each computing entity, it determines the third device identifier corresponding to the computing entity with the highest priority as the second device identifier associated with the first device identifier, that is, unbinds the computing entity with the highest priority from the peripheral component.

[0088] In this embodiment, when there are multiple bound computing entities for the peripheral component, the device uses the device identifier of the computing entity with the highest priority as the second device identifier associated with the first device identifier, that is, unbinds the computing entity with the highest priority from the peripheral component.

[0089] Refer to Figure 5 , Figure 5 This is the fourth embodiment of the unbinding method of the present invention. Based on any one of the first to third embodiments, before step S201, it further includes:

[0090] Step S501: Receive a binding request sent by the peripheral component.

[0091] Step S502: Obtain the first device identifier of the peripheral component and the second device identifier of the computing entity that the peripheral component requests to bind according to the binding request.

[0092] Step S503, configure and store the association relationship between the first device identifier and the second device identifier.

[0093] In this embodiment, a peripheral component may request to bind an arithmetic entity from the device. Exemplarily, the peripheral component sends a binding request to the device. The binding request may be sent by the user through the peripheral component.

[0094] The binding request contains the device identifier of the peripheral component and the device identifier of the arithmetic entity requested to be bound. By parsing the binding request, the device can obtain the first device identifier of the peripheral component and the second device identifier of the arithmetic entity requested to be bound by the peripheral component.

[0095] After obtaining the second device identifier and the first device identifier, the device configures and stores the association relationship between the first device identifier and the second device identifier, thereby completing the binding between the peripheral component and the arithmetic entity.

[0096] In addition, for the binding between the peripheral component and the arithmetic entity, the peripheral component needs to be registered on the device first. For this, the device obtains the registration request sent by the peripheral component, obtains the fourth device identifier of the peripheral component based on the registration request, and stores the fourth device identifier. The device storing the fourth device identifier means that the peripheral component is successfully registered on the device. After the device obtains the first device identifier, it determines whether the first device identifier matches the fourth device identifier. If the first device identifier matches the fourth device identifier, it can be determined that the peripheral component has been registered on the device, and the device can bind the peripheral component to the physical device, and the device can then configure and store the association relationship between the first device identifier and the second device identifier.

[0097] Further, when the peripheral component requests to bind an arithmetic entity, the device needs to register with the arithmetic entity. For this, the device sends a registration request to the arithmetic entity corresponding to the second device identifier. If the arithmetic entity stores the device identifier of the device, the device is successfully registered on the arithmetic entity, that is, the device can subsequently send information to the arithmetic entity. After the device is successfully registered on the arithmetic entity, the arithmetic entity feeds back a registration success message to the device, that is, when the device receives the registration success message fed back by the arithmetic entity corresponding to the second device identifier, it stores the second device identifier, configures and stores the association relationship between the second device identifier and the second device identifier, thereby completing the binding between the peripheral component and the arithmetic entity.

[0098] In this embodiment, the device receives the binding request sent by the peripheral component, obtains the first device identifier of the peripheral component and the second device identifier of the arithmetic entity requested to be bound by the peripheral component based on the binding request, thereby configuring and storing the association relationship between the first device identifier and the second device identifier to complete the binding between the peripheral component and the arithmetic entity.

[0099] The present invention also provides a unbinding device, referring to Figure 6 , the unbinding device 600 includes:

[0100] The receiving module 610 is used to receive an unbinding request sent by a peripheral component;

[0101] An acquisition module 620, configured to acquire a first device identifier of the peripheral component according to the unbinding request;

[0102] A determination module 630, configured to determine a second device identifier associated with the first device identifier;

[0103] The release module 640 is used to release the association between the second device identifier and the first device identifier, so as to unbind the peripheral component from the computing entity corresponding to the second device identifier.

[0104] Optionally, the determination module 630 is specifically configured to:

[0105] Acquire, according to the unbinding request, a target computing entity for which the peripheral component requests to be unbinded;

[0106] The device identifier corresponding to the target computing entity is determined as the second device identifier associated with the first device identifier.

[0107] Optionally, the determination module 630 is specifically configured to:

[0108] Determine each third device identifier associated with the first device identifier, wherein the third device identifier is used to indicate a device identifier of a computing entity to which the peripheral component is bound;

[0109] Obtaining the priority corresponding to each computing entity bound to the peripheral component;

[0110] The third device identifier corresponding to the computing entity corresponding to the highest priority is used to determine the second device identifier associated with the first device identifier.

[0111] Optionally, the unbinding device 600 further includes:

[0112] The receiving module 610 is further configured to receive a binding request sent by the peripheral component;

[0113] The acquisition module 620 is further configured to acquire, according to the binding request, a first device identifier of the peripheral component and a second device identifier of a computing entity to which the peripheral component requests to be bound;

[0114] A configuration module is used to configure and store the association relationship between the first device identifier and the second device identifier.

[0115] Optionally, the configuration module is specifically used for:

[0116] Obtain a registration request sent by the peripheral component;

[0117] Based on the registration request, obtain a fourth device identifier of the peripheral component and store the fourth device identifier;

[0118] When the first device identifier matches the fourth device identifier, determine that the peripheral component has been registered, and configure and store the association relationship between the first device identifier and the second device identifier.

[0119] Optionally, the configuration module is specifically configured to:

[0120] Send a registration request to the computing entity corresponding to the second device identifier;

[0121] When receiving the registration success information fed back by the computing entity corresponding to the second device identifier, store the second device identifier, and configure and store the association relationship between the first device identifier and the second device identifier.

[0122] Figure 7 It is a hardware structure diagram of an unbinding device shown according to an exemplary embodiment.

[0123] The unbinding device 700 may include: a processor 701, such as a CPU, a memory 702, and a transceiver 703. Those skilled in the art can understand that Figure 7 The structure shown in does not constitute a limitation on the unbinding device, and may include more or fewer components than shown in the figure, or combine some components, or have different component arrangements. The memory 702 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0124] The processor 701 can call a computer program (computer execution instruction) stored in the memory 702 to complete all or part of the steps of the above unbinding method.

[0125] The transceiver 703 is used to receive information sent by an external device and send information to the external device.

[0126] A non-transitory computer-readable storage medium, when the instructions (computer execution instructions) in the storage medium are executed by the processor of the unbinding device, enable the unbinding device to execute the above unbinding method.

[0127] A computer program product includes a computer program which, when executed by a processor of an unlocking device, enables the unlocking device to perform the above unlocking method.

[0128] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses, or adaptations of the present disclosure, which follow the general principles of the present disclosure and include known common knowledge or conventional technical means in the technical field not disclosed by the present disclosure. The specification and examples are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the following claims.

[0129] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A method for unbinding, characterized in that, Applied to an unbinding device, the unbinding device is communicatively connected with an external device component and a computing entity, and the unbinding method includes: Receiving an unbinding request sent by the peripheral component; Acquire a first device identifier of the peripheral component according to the unbinding request; Determine a second device identifier associated with the first device identifier; The association relationship between the second device identifier and the first device identifier is released to unbind the peripheral component from the computing entity corresponding to the second device identifier.

2. The unbinding method according to claim 1, wherein The step of determining the second device identifier associated with the first device identifier comprises: Acquire, according to the unbinding request, a target computing entity for which the peripheral component requests to be unbinded; The device identifier corresponding to the target computing entity is determined as the second device identifier associated with the first device identifier.

3. The unbinding method according to claim 1, wherein The step of determining the second device identifier associated with the first device identifier comprises: Determine each third device identifier associated with the first device identifier, wherein the third device identifier is used to indicate a device identifier of a computing entity to which the peripheral component is bound; Obtaining the priority corresponding to each computing entity bound to the peripheral component; The third device identifier corresponding to the computing entity corresponding to the highest priority is used to determine the second device identifier associated with the first device identifier.

4. The unbinding method according to claim 1, characterized in that, Before the step of removing the association relationship between the second device identifier and the first device identifier, the method further includes: Receiving a binding request sent by the peripheral component; Acquire, according to the binding request, a first device identifier of the peripheral component and a second device identifier of a computing entity to which the peripheral component requests to be bound; Configure and store an association relationship between the first device identifier and the second device identifier.

5. The unbinding method according to claim 4, wherein The step of configuring and storing the association relationship between the first device identifier and the second device identifier comprises: Obtaining a registration request sent by the peripheral component; Acquire a fourth device identification of the peripheral component based on the registration request, and store the fourth device identification; When the first device identifier matches the fourth device identifier, it is determined that the peripheral component has been registered, and an association relationship between the first device identifier and the second device identifier is configured and stored.

6. The unbinding method according to claim 4, characterized in that, The step of configuring and storing the association relationship between the first device identifier and the second device identifier comprises: Sending a registration request to a computing entity corresponding to the second device identifier; When receiving the registration success information fed back by the computing entity corresponding to the second device identifier, the second device identifier is stored, and an association relationship between the first device identifier and the second device identifier is configured and stored.

7. An unlocking device, characterized in that, include: A receiving module, used for receiving an unbinding request sent by a peripheral component; An acquisition module, configured to acquire a first device identifier of the peripheral component according to the unbinding request; A determination module, configured to determine a second device identifier associated with the first device identifier; The releasing module is used to release the association between the second device identifier and the first device identifier, so as to unbind the peripheral component from the computing entity corresponding to the second device identifier.

8. An unbinding device, characterized in that, include: Memory and processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the unbinding method according to any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Computer-executable instructions are stored in the computer-readable storage medium, and when the computer-executable instructions are executed by a processor, they are used to implement the unbinding method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it is used to implement the unbinding method according to any one of claims 1 to 6.

Images