A license multiplexing method and apparatus

Abstract

This application relates to the field of license management technology, and in particular to a license reuse method and apparatus. The method is applied to a license server deployed independently of a primary disaster recovery system. The primary disaster recovery system includes a first system as the primary disaster recovery system and a second system as the backup disaster recovery system. The method includes: receiving a first license acquisition request sent by the first system, carrying a target license information and the system identifier information of the first system; establishing a binding relationship between a target license and the system identifier of the first system, and authorizing the target license to the first system; receiving a second license acquisition request sent by the second system, carrying the system identifiers of the first and second systems; determining a target license based on the system identifier of the first system, and authorizing the target license to the second system.

Description

Technical Field

[0001] This application relates to the field of license licensing technology, and in particular to a license reuse method and apparatus. Background Technology

[0002] Off-site disaster recovery scenarios refer to deploying two systems at two physical locations, such as two cities. These two systems serve as backups for each other. One system acts as the primary system, handling business operations; the other system acts as a backup. When the primary system fails, the backup system takes over the business operations and becomes the primary system.

[0003] A license is an authorization management mechanism. A license file is an authorization document used to control whether special system functions are allowed and the amount of resources managed. In off-site disaster recovery scenarios, the primary system and the backup system manage the same set of equipment resources, eliminating the need for users to purchase two sets of licenses.

[0004] Currently, to address the issue of sharing license files between two systems in a disaster recovery scenario, a license server can be deployed on both the primary and backup systems. Then, the Electronic Sequence Number (ESN) of each system can be collected. Both the primary and backup ESNs are bound to the license file on the license website. Before uploading the license file, it's necessary to identify the primary system, log in to it, and then upload the license file.

[0005] However, when the system's ESN changes, since the license file is bound to the ESN, it is necessary to re-collect the ESNs of the primary and backup systems, log in to the license website to update the binding relationship between the license file and the ESN, download the updated license file, and upload it to the latest primary system. The change process is cumbersome. Summary of the Invention

[0006] This application provides a license reuse method and apparatus.

[0007] Firstly, this application provides a license reuse method applied to a license server, wherein the license server is deployed independently of a primary disaster recovery system, the primary disaster recovery system comprising a first system as the primary disaster recovery system and a second system as the backup disaster recovery system; the first system and the second system respectively establish connections with the license server, and the method includes:

[0008] Receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system;

[0009] Obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system;

[0010] The system receives a second license acquisition request sent by the second system. After detecting a fault in the first system and switching to the main system, the second system obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server.

[0011] Based on the system identifier of the first system included in the second license acquisition request, the target license bound to the system identifier of the first system is determined, the target license authorization issued to the first system is revoked, a binding relationship is established between the target license authorization and the system identifier of the second system, and the target license authorization is granted to the second system.

[0012] Optionally, client accounts are pre-configured for the first system and the second system. The first system logs into the license server using the first client account and establishes a connection with the license server; the second system logs into the license server using the second client account and establishes a connection with the license server.

[0013] Optionally, the step of revoking the target license authorization issued to the first system includes:

[0014] Remove the binding relationship between the target license authorization and the system identifier of the first system.

[0015] Optionally, the License server maintains an identifier set consisting of the system identifier of the first system and the system identifier of the second system; the method further includes:

[0016] Upon receiving the first license acquisition request sent by the first system, the target license is obtained from the license resource pool, a binding relationship is established between the target license and the identifier set, and the target license is authorized to the first system.

[0017] Optionally, the method further includes:

[0018] If a second license acquisition request is received from the second system, the target license bound to the identified set is determined based on the system identifier of the second system included in the second license acquisition request, the target license authorization issued to the first system is revoked, and the target license authorization is granted to the second system.

[0019] Secondly, this application provides a license multiplexing device applied to a license server, wherein the license server is deployed independently of a primary disaster recovery system, the primary disaster recovery system including a first system as the primary disaster recovery system and a second system as the backup disaster recovery system; the first system and the second system are respectively connected to the license server, and the device includes:

[0020] The receiving unit is configured to receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system;

[0021] The establishment unit is used to obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system;

[0022] The receiving unit is further configured to receive a second license acquisition request sent by the second system, wherein after the second system detects a fault in the first system and switches to the main system, it obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server.

[0023] The revoke unit is used to determine the target license bound to the system identifier of the first system based on the system identifier of the first system included in the second license acquisition request, and revoke the target license authorization issued to the first system.

[0024] The establishment unit is further configured to establish a binding relationship between the target license authorization and the system identifier of the second system, and to authorize the target license authorization to the second system.

[0025] Optionally, client accounts are pre-configured for the first system and the second system. The first system logs into the license server using the first client account and establishes a connection with the license server; the second system logs into the license server using the second client account and establishes a connection with the license server.

[0026] Optionally, when revoking the target license authorization issued to the first system, the revoke unit is specifically used for:

[0027] Remove the binding relationship between the target license authorization and the system identifier of the first system.

[0028] Optionally, the License server maintains an identifier set consisting of the system identifier of the first system and the system identifier of the second system;

[0029] The receiving unit is further configured to receive the first License acquisition request sent by the first system;

[0030] The establishment unit is further configured to obtain the target license from the license resource pool, establish a binding relationship between the target license and the identifier set, and authorize the target license to the first system.

[0031] Optionally, the receiving unit is further configured to receive a second license acquisition request sent by the second system;

[0032] The recycling unit is further configured to, based on the system identifier of the second system included in the second license acquisition request, determine the target license bound to the identified set, and reclaim the target license authorization issued to the first system;

[0033] The establishment unit is also used to authorize the target license to the second system.

[0034] Thirdly, embodiments of this application provide a license multiplexing device, the device comprising:

[0035] Memory, used to store program instructions;

[0036] A processor is configured to invoke program instructions stored in the memory and execute the steps of the method as described in any one of the first aspects above, according to the obtained program instructions.

[0037] Fourthly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions for causing a computer to perform the steps of the method as described in any of the first aspects above.

[0038] In summary, the license reuse method provided in this application is applied to a license server, which is deployed independently of the primary and backup disaster recovery systems. The primary and backup disaster recovery systems include a first system as the primary disaster recovery system and a second system as the backup disaster recovery system. The first system and the second system respectively establish connections with the license server. The method includes: receiving a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system; acquiring the target license from the license resource pool, establishing a binding relationship between the target license and the system identifier of the first system, and transferring the target license to the system identifier of the first system. The system grants a license to the first system; it receives a second license acquisition request from the second system, wherein, after detecting a fault in the first system and switching to the main system, the second system obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server; based on the system identifier of the first system included in the second license acquisition request, it determines the target license bound to the system identifier of the first system, revoks the target license authorization issued to the first system, establishes a binding relationship between the target license authorization and the system identifier of the second system, and authorizes the target license to the second system.

[0039] The license reuse method provided in this application pre-configures fixed system identifiers for each primary / backup system in the disaster recovery system. After allocating a license file to the current primary system, the license server records the mapping relationship between the license file and the system identifier of the primary system. When the primary system experiences a failure and the backup system switches to the primary system, the license server can authorize the new primary system to request a license by binding the license with the system identifier of the requesting system. The system identifier is fixed and will not change according to changes in system hardware, simplifying the license authorization switching process during primary / backup system switching and improving the service reliability of the disaster recovery system. Attached Figure Description

[0040] 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 of this application or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings of the embodiments of this application.

[0041] Figure 1 A detailed flowchart of a license reuse method provided for embodiments of this application;

[0042] Figure 2 A network diagram of a disaster recovery system provided in this application embodiment;

[0043] Figure 3 A schematic diagram illustrating the first type of license authorization provided in this application embodiment;

[0044] Figure 4 This is a schematic diagram illustrating a second type of license authorization provided in an embodiment of this application;

[0045] Figure 5 A schematic diagram illustrating a third type of license authorization provided in this application embodiment;

[0046] Figure 6 This is a schematic diagram illustrating the fourth type of license authorization provided in an embodiment of this application;

[0047] Figure 7 A diagram illustrating the relationship between a disaster recovery system and a license server, provided for embodiments of this application;

[0048] Figure 8 A schematic diagram of a license multiplexing device provided in an embodiment of this application;

[0049] Figure 9 This is a schematic diagram of the hardware architecture of a license multiplexing device provided in an embodiment of this application. Detailed Implementation

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

[0051] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" may also be interpreted as "when," "when," or "in response to a determination."

[0052] For example, see Figure 1 The diagram shown is a detailed flowchart of a license reuse method provided in an embodiment of this application. This method is applied to a license server, which is deployed independently of the primary and backup disaster recovery system. The primary and backup disaster recovery system includes a first system as the primary disaster recovery system and a second system as the backup disaster recovery system. The first system and the second system respectively establish connections with the license server. The method includes the following steps:

[0053] Step 100: Receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system.

[0054] In this embodiment, the License server is independent of the disaster recovery primary and backup system. The primary and backup systems of the disaster recovery primary and backup system are respectively connected to the License server. The primary system can obtain the required License from the License server to control the managed devices, etc.

[0055] For example, see Figure 2The diagram shown is a network topology diagram of a disaster recovery system provided in an embodiment of this application. The disaster recovery system includes a primary system and a backup system. The primary system manages the devices it manages, and the backup system is used for high-availability backup. A heartbeat link and a data replication link are established between the primary system and the backup system. When the backup system detects a failure in the primary system, the backup system switches to become the primary system, and the new primary system manages the devices. The primary system and the backup system are connected via a license communication connection.

[0056] It should be noted that, in a preferred embodiment of this application, client accounts are pre-configured for the first system and the second system. The first system logs into the License server through the first client account and establishes a connection with the License server; the second system logs into the License server through the second client account and establishes a connection with the License server.

[0057] In this embodiment of the application, the user pre-purchases a set of licenses. When using it later, the user can customize the target license required by the main system (e.g., the first system) through the system interface (UI / Web interface). Then, the main system generates a license acquisition request (e.g., the first license acquisition request) that includes the required target license information and its own system identifier.

[0058] In practical applications, the system identifiers of each system are predefined, and a system identifier can uniquely identify the system in a disaster recovery system.

[0059] Step 110: Obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system.

[0060] In this embodiment of the application, after receiving a first license acquisition request sent by the first system, the license server parses the first license acquisition request, obtains the target license information required by the first system and the system identifier of the first system, then obtains the target license from the license resource pool, establishes a binding relationship between the target license and the system identifier of the first system, and finally authorizes the target license to the first system.

[0061] For example, if a user purchases a license set including 5 License 1s, and the target license required by the first system includes 5 License 1s, then when the license server authorizes the target license for the first system, the license file corresponding to License 1 will record the number of License 1s authorized for the first system (used License 1s) as 5, and the number of License 1s currently available for the disaster recovery system mentioned in the first system will be 0. That is, it records that 5 License 1s have been allocated to the disaster recovery system. If other systems in the disaster recovery system (e.g., the second system) also need these 5 License 1s, they can only apply for use after the license server authorizes the 5 License 1s to the first system.

[0062] Step 120: Receive a second license acquisition request sent by the second system, wherein after the second system detects a fault in the first system and switches to the master system, it obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server.

[0063] In practical applications, when the first system fails, and the second system detects the failure, it will switch to the new master system. In this case, the second system needs to manage all the devices managed by the disaster recovery system, so it needs to obtain the corresponding license authorization from the license server (e.g., 5 licenses 1). The second system will send a license acquisition request (e.g., a second license acquisition request) to the license server. This license acquisition request needs to include the system identifier of the first system and the system identifier of the second system. Therefore, the second system needs to obtain the system identifier of the first system and send its own system identifier and the system identifier of the first system in the license acquisition request to the license server.

[0064] Step 130: Based on the system identifier of the first system included in the second license acquisition request, determine the target license bound to the system identifier of the first system, reclaim the target license authorization issued to the first system, establish a binding relationship between the target license authorization and the system identifier of the second system, and authorize the target license authorization to the second system.

[0065] In this embodiment, when the License server receives a License acquisition request (e.g., a second License acquisition request) sent by the second system, it parses the License acquisition request to obtain the system identifier of the first system. Then, based on the system identifier of the first system, it determines the target License bound to the system identifier of the first system. Subsequently, due to a failure of the first system, the disaster recovery system master system switches to the second system. At this time, it is necessary to revoke the target License authorized to the first system and then authorize the revoked target License to the second system so that the second system can manage the devices managed by the disaster recovery system.

[0066] Specifically, in this embodiment of the application, when revoking the target license authorization issued to the first system, a preferred implementation is to remove the binding relationship between the target license authorization and the system identifier of the first system.

[0067] In other words, when the license server determines that it needs to reclaim the target license issued to the first system (e.g., 5 License 1 licenses), it will remove the binding relationship between the target license and the system identifier of the first system, and change the number of License 1 licenses that the disaster recovery system can use from 0 to 5 as recorded in the target license file.

[0068] In this embodiment of the application, after pre-assigning system identifiers to the first system and the second system, the License server maintains an identifier set consisting of the system identifiers of the first system and the system identifiers of the second system. Therefore, the above-mentioned License reuse method may further include the following steps: upon receiving the first License acquisition request sent by the first system, obtaining the target License from the License resource pool, establishing a binding relationship between the target License and the identifier set, and authorizing the target License to the first system.

[0069] In other words, the first license acquisition request includes the system identifier of the first system and the target license information required by the first system. Based on the target license information required by the first system, the license server determines the target license from the license resource pool. Then, it establishes a binding relationship between the identifier set including the system identifier of the first system and the target license. That is, the target license maps the system identifier of the first system and the system identifier of the second system at the same time, and authorizes the target license to the first system.

[0070] Furthermore, if a second license acquisition request is received from the second system, the target license bound to the identified set is determined based on the system identifier of the second system included in the second license acquisition request, the target license authorization issued to the first system is revoked, and the target license authorization is granted to the second system.

[0071] In other words, when the first system fails, and the second system detects the failure, it will switch to the new master system. Then, the second system needs to manage all the devices under the disaster recovery system, so it needs to obtain the corresponding license authorization from the license server (e.g., 5 licenses 1). The second system will send a license acquisition request (e.g., a second license acquisition request) to the license server. This license acquisition request only needs to include the system identifier of the second system (it does not need to include the system identifier of the first system), and sends its own system identifier in the license acquisition request to the license server.

[0072] After receiving a second license acquisition request from the second system, the license server parses the request to obtain the system identifier of the second system. Based on the system identifier of the second system, it determines the target license bound to the identifier set including the system identifier of the second system. Then, it revoks the target license authorization issued to the first system and authorizes the target license to the second system.

[0073] Clearly, the second system does not need to obtain the system identifier of the first system, and the license server does not need to unbind the binding relationship between the target license and the system identifier of the first system, and establish the binding relationship between the target license and the system identifier of the second system.

[0074] The license reuse method provided in this application embodiment will be described in detail below with reference to specific application scenarios. For example, see [link to relevant documentation]. Figure 3The diagram illustrates a license authorization method provided in this application. The first system has a pre-defined client account (A), and the second system has a pre-defined client account (B). An owner mechanism is introduced to isolate different systems; the first system is set as owner A, and the second system as owner B. Client account A is associated with owner A, and client account B is associated with owner B. The first system logs into the license server using client account A and establishes a connection. The second system logs into the license server using client account B and establishes a connection. The first system is the master system. The first system sends a license retrieval request to the license server, requesting license file 1, license file 2, and license file 3. After receiving the license retrieval request, the license server binds license file 1, license file 2, and license file 3 to owner A and assigns them to the first system. Of course, the license server may also include other license files (e.g., license file 4, license file 5). License file 4 can be bound to owner C associated with client account C, and license file 5 can be bound to owner D associated with client account D. License file 4 and license file 5 will be distributed to other systems for use.

[0075] For example, see Figure 4 The diagram illustrates a license authorization process provided in this application embodiment. When the second system detects a fault in the first system and switches to the main system, the second system sends a license acquisition request to the license server, carrying its own system identifier and the system identifier of the first system. Based on the system identifier of the first system, the license server determines the license files 1, 2, and 3 that have been assigned to the first system, removes the binding relationship between license files 1, 2, and 3 and owner A, and establishes the binding relationship between license files 1, 2, and 3 and owner B. In this way, while reclaiming the license files of the first system, the license files originally assigned to the first system are authorized to the second system, enabling the second system to control and manage the devices under the management of the system based on the license files.

[0076] Furthermore, in this embodiment, the concept of an owner group is introduced, adding the system identifiers (owners) of the primary and backup systems included in the disaster recovery system to the same identifier set (owner group). For example, see [link to relevant documentation]. Figure 5The diagram shown is a license authorization illustration provided in an embodiment of this application. Owner A and owner B both belong to owner group m. The first system is the main system. The first system sends a license acquisition request to the license server to request license file 1, license file 2 and license file 3. After receiving the license acquisition request, the license server binds license file 1, license file 2 and license file 3 to owner group m and allocates them to the first system.

[0077] For example, see Figure 6 The diagram shown is a license authorization illustration provided in an embodiment of this application. When the second system detects a fault in the first system and switches to the main system, the second system sends a license acquisition request carrying its own system identifier to the license server. Since owner B belongs to owner group m, the license server can determine the license files 1, 2, and 3 that are bound to owner group m and have been allocated to the first system based on the system identifier (owner B) of the second system. The license server can then reclaim the license files of the first system and authorize the second system with the license files originally allocated to the first system, so that the second system can control and manage the devices under the management of the system based on the license files.

[0078] For example, see Figure 7The diagram illustrates the association between a disaster recovery system and a license server according to an embodiment of this application. The disaster recovery system includes system A and system B. Client A corresponds to system A, and client B corresponds to system B. System A is set as owner A, and system B is set as owner B. Owner A and owner B form owner Group m. Client A is associated with owner A, and client B is associated with owner B. System A logs into the license server through client A, and system B logs into the license server through client B. System A is the currently primary system. When it obtains license files 1, 2, and 3 from the license server, the license server binds license files 1, 2, and 3 to owner Group m (i.e., owner A and owner B) and authorizes system A to use license files 1, 2, and 3. If the license server also serves other systems (e.g., system C), then the client C assigned by system C can also be associated with owner C. Owner C belongs to owner group p, and license file 4 establishes a binding relationship with owner group p, authorizing system C to use license file 4.

[0079] For example, see Figure 8 The diagram shown is a structural schematic of a license multiplexing device provided in an embodiment of this application. This device is applied to a license server, which is deployed independently of the primary and backup disaster recovery system. The primary and backup disaster recovery system includes a first system as the primary disaster recovery system and a second system as the backup disaster recovery system. The first system and the second system are respectively connected to the license server. The device includes:

[0080] The receiving unit 80 is configured to receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system;

[0081] Establishment unit 81 is used to obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system;

[0082] The receiving unit 80 is further configured to receive a second license acquisition request sent by the second system, wherein after the second system detects a fault in the first system and switches to the main system, it obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server.

[0083] The recycling unit 82 is used to determine the target license bound to the system identifier of the first system based on the system identifier of the first system included in the second license acquisition request, and to reclaim the target license authorization issued to the first system.

[0084] The establishment unit 81 is further configured to establish a binding relationship between the target license authorization and the system identifier of the second system, and to authorize the target license authorization to the second system.

[0085] Optionally, client accounts are pre-configured for the first system and the second system. The first system logs into the license server using the first client account and establishes a connection with the license server; the second system logs into the license server using the second client account and establishes a connection with the license server.

[0086] Optionally, when revoking the target license authorization issued to the first system, the revoke unit 82 is specifically used for:

[0087] Remove the binding relationship between the target license authorization and the system identifier of the first system.

[0088] Optionally, the License server maintains an identifier set consisting of the system identifier of the first system and the system identifier of the second system;

[0089] The receiving unit 80 is further configured to receive the first license acquisition request sent by the first system;

[0090] The establishment unit 81 is further configured to obtain the target license from the license resource pool, establish a binding relationship between the target license and the identifier set, and authorize the target license to the first system.

[0091] Optionally, the receiving unit 80 is further configured to receive a second license acquisition request sent by the second system;

[0092] The recycling unit 82 is further configured to, based on the system identifier of the second system included in the second license acquisition request, determine the target license bound to the identified set, and reclaim the target license authorization issued to the first system;

[0093] The establishment unit 81 is further configured to authorize the target license to the second system.

[0094] These units can be one or more integrated circuits configured to implement the above methods, such as one or more Application Specific Integrated Circuits (ASICs), one or more digital signal processors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs). Alternatively, when one of these units is implemented using processing element scheduler code, the processing element can be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. Furthermore, these units can be integrated together to form a system-on-a-chip (SOC).

[0095] Furthermore, regarding the license multiplexing device provided in this application embodiment, from a hardware perspective, the hardware architecture diagram of the license multiplexing device can be found in [reference needed]. Figure 9 As shown, the license multiplexing device may include: a memory 90 and a processor 91.

[0096] The memory 90 is used to store program instructions; the processor 91 calls the program instructions stored in the memory 90 and executes the above method embodiment according to the obtained program instructions. The specific implementation method and technical effect are similar, and will not be described again here.

[0097] Optionally, this application also provides a license server, including at least one processing element (or chip) for performing the above method embodiments.

[0098] Optionally, this application also provides a program product, such as a computer-readable storage medium storing computer-executable instructions for causing the computer to perform the above-described method embodiments.

[0099] Here, a machine-readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, a machine-readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

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

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

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

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

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

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

[0106] The above description is merely a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A license reuse method, characterized in that, The method is applied to a license server, which is deployed independently of the primary and backup disaster recovery system. The primary and backup disaster recovery system includes a first system serving as the primary disaster recovery system and a second system serving as the backup disaster recovery system. The first system and the second system respectively establish connections with the license server. Receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system; Obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system; The system receives a second license acquisition request sent by the second system. After detecting a fault in the first system and switching to the main system, the second system obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server. Based on the system identifier of the first system included in the second license acquisition request, the target license bound to the system identifier of the first system is determined, the target license authorization issued to the first system is revoked, a binding relationship is established between the target license authorization and the system identifier of the second system, and the target license authorization is granted to the second system.

2. The method as described in claim 1, characterized in that, The first system and the second system are pre-configured with client accounts. The first system logs into the license server using the first client account and establishes a connection with the license server; the second system logs into the license server using the second client account and establishes a connection with the license server.

3. The method as described in claim 1, characterized in that, The steps for revoking the target license authorization issued to the first system include: Remove the binding relationship between the target license authorization and the system identifier of the first system.

4. The method according to any one of claims 1-3, characterized in that, The license server maintains an identifier set consisting of the system identifier of the first system and the system identifier of the second system; the method further includes: Upon receiving the first license acquisition request sent by the first system, the target license is obtained from the license resource pool, a binding relationship is established between the target license and the identifier set, and the target license is authorized to the first system.

5. The method as described in claim 4, characterized in that, The method further includes: If a second license acquisition request is received from the second system, the target license bound to the set of identifiers is determined based on the system identifier of the second system included in the second license acquisition request, the target license authorization issued to the first system is revoked, and the target license authorization is granted to the second system.

6. A license multiplexing device, characterized in that, An apparatus for use with a license server, wherein the license server is deployed independently of a primary disaster recovery system, the primary disaster recovery system comprising a first system as the primary disaster recovery system and a second system as the backup disaster recovery system; the first system and the second system are respectively connected to the license server, and the apparatus comprises: The receiving unit is configured to receive a first license acquisition request sent by the first system, wherein the first license acquisition request includes target license information required by the first system and pre-configured system identifier information of the first system; The establishment unit is used to obtain the target license from the license resource pool, establish a binding relationship between the target license and the system identifier of the first system, and authorize the target license to the first system; The receiving unit is further configured to receive a second license acquisition request sent by the second system, wherein after the second system detects a fault in the first system and switches to the main system, it obtains the system identifier of the first system and sends a second license acquisition request including the system identifier of the first system and the system identifier of the second system to the license server. The revoke unit is used to determine the target license bound to the system identifier of the first system based on the system identifier of the first system included in the second license acquisition request, and revoke the target license authorization issued to the first system. The establishment unit is further configured to establish a binding relationship between the target license authorization and the system identifier of the second system, and to authorize the target license authorization to the second system.

7. The apparatus as claimed in claim 6, characterized in that, The first system and the second system are pre-configured with client accounts. The first system logs into the license server using the first client account and establishes a connection with the license server; the second system logs into the license server using the second client account and establishes a connection with the license server.

8. The apparatus as claimed in claim 6, characterized in that, When revoking the target license authorization issued to the first system, the revocation unit is specifically used for: Remove the binding relationship between the target license authorization and the system identifier of the first system.

9. The apparatus according to any one of claims 6-8, characterized in that, The License server maintains an identifier set consisting of the system identifier of the first system and the system identifier of the second system; The receiving unit is further configured to receive the first License acquisition request sent by the first system; The establishment unit is further configured to obtain the target license from the license resource pool, establish a binding relationship between the target license and the identifier set, and authorize the target license to the first system.

10. The apparatus as claimed in claim 9, characterized in that, The device further includes: The receiving unit is further configured to receive a second license acquisition request sent by the second system; The recycling unit is further configured to, based on the system identifier of the second system included in the second license acquisition request, determine the target license bound to the identifier set, and reclaim the target license authorization issued to the first system; The establishment unit is further configured to authorize the target license to the second system.

Images