CN116340902A - A device activation method, system and readable storage medium based on domain control - Google Patents

Abstract

The invention discloses a domain control-based equipment activation method, a domain control-based equipment activation system and a readable storage medium, relates to the technical field of batch activation of applications, and aims to solve the problem that the conventional batch activation service cannot accurately control the activation of terminal equipment. The domain control-based device activation method comprises the following steps: a user logs in on a terminal device through a domain account number and a password, a domain management client arranged in the terminal device pushes a login request to a domain control platform server arranged in a first server, after the login request is successfully checked by the domain control platform server, a domain account number login notification is pushed to a batch activation server of a second server, after the domain account number login notification is successfully checked by the batch activation server, the association relation between the terminal device and the domain account number is updated, and a script creating task notification is pushed to the domain control platform server; the domain control platform server creates a script and pushes the script to the domain management client; and the domain management client executes the script to complete the activation of the terminal equipment.

Description

A device activation method, system and readable storage medium based on domain control

technical field

The present invention relates to the technical field of application batch activation, in particular to a domain control-based device activation method, system and readable storage medium.

Background technique

Modern operating systems or business software often employ activation controls to govern their features. The commonly used activation schemes mainly include serial number activation, activation file activation, online activation and batch activation tool activation.

Serial number activation is also called activation code, and the user must manually enter the serial number. There is a risk of the serial number being copied and disseminated, and the security is poor.

Activation file activation is similar to serial number activation. The activation file must be manually imported by the user. There is also the risk of being copied and distributed, which is difficult to control.

Online activation needs to register an account in advance, and it will be activated automatically after logging in to the account. This solution is not suitable for places that cannot connect to the WAN or have a high level of network security.

The batch activation tool is a service that provides batch activation. Devices connected to a specific network can use the serial number imported from the server in rotation. This activation method needs to deploy the batch activation service (Key Management Service, KMS) and import one at a time. From the batch serial number to the batch activation tool, the device/software that needs to be activated only needs to enter the IP port and password of KMS to log in to the batch activation service and complete the automatic activation. Compared with serial number activation and activation file activation, batch activation tool activation has the following advantages: 1. It can prevent users from touching the serial number that can be directly used for activation, which enhances data security; 2. The batch activation service can be deployed according to user scenarios In the public network or LAN, it is more applicable than online activation; 3. For mass activation requirements, there is no need to manually enter a different activation code or manually import a different activation file for each device, which can greatly simplify the activation process. The experience is improved; 4. The serial number is recyclable and shared. The serial number of the service is consumed only when the device is connected to KMS. When the device is disconnected from KMS, the server will recycle the serial number for other devices to use.

For the batch activation server, all devices connected through IP ports and correct passwords are equal, but some organizations need to implement more fine-grained control over the activation of terminal devices at different levels and departments, such as those with strong confidentiality Enterprises only allow some terminal devices to be activated, so the traditional batch activation service obviously cannot meet the demand.

To sum up, the existing batch activation service has the problem of being unable to fine-tune the activation of terminal devices.

Contents of the invention

To this end, the present invention provides a domain control-based device activation method, system and readable storage medium in an attempt to solve or at least alleviate at least one of the above problems.

According to one aspect of the present invention, there is provided a domain controller-based device activation method suitable for domain controller platform servers, including: in response to receiving a login request pushed by a domain management client, updating the domain account number carried in the login request Verify with the password, and push the domain account login notification to the batch activation server after the verification is successful, so that the batch activation server can verify the batch activation server address and password carried in the domain account login notification. verification, and after the verification is successful and the number of domain account activations has a remaining quota, push a creation script task notification to the domain control platform server; and in response to receiving the creation script task notification pushed by the batch activation server, Create a script according to the script creation task notification, and push the created script to the domain management client corresponding to the script, the domain management client is arranged on the terminal device, so that the domain management client executes The script completes the activation of the terminal device.

Optionally, in the domain control-based device activation method according to the present invention, the method further includes: in response to receiving a domain entry request pushed by the domain management client, pushing a domain entry request to the batch activation server Event notification, so that the batch activation server adds a terminal device hardware information record in the database.

Optionally, in the domain controller-based device activation method according to the present invention, the creating script according to the creation script task notification includes: according to the batch activation server address carried in the creation script task notification, the The password and the domain identification code of the terminal device create an activation script.

According to another aspect of the present invention, there is provided a domain control-based device activation method applicable to batch activation servers, including: in response to receiving a domain account login notification pushed by the domain control platform server, log in the domain account The batch activation server address and password carried in the notification are verified, and after the verification is successful, the association relationship between the terminal device and the domain account is updated; Pushing the script creation task notification, so that the domain control platform server creates the script and pushes the script to the domain management client corresponding to the script, and the domain management client is arranged on the terminal device , so that the domain management client executes the script to complete the activation of the terminal device.

Optionally, in the domain controller-based device activation method according to the present invention, in response to changes in the batch activation server address and/or password, the changed batch activation server address and/or password are pushed to all domain management client.

Optionally, in the domain control-based device activation method according to the present invention, in response to receiving the activation request pushed by the domain management client, verify the batch activation server address and password carried in the activation request ; and returning a serial number to the domain management client after the verification is successful, and binding the serial number with the hardware information of the terminal device.

Optionally, in the domain control-based device activation method according to the present invention, the method further includes: in response to receiving the domain entry event notification pushed by the domain control platform server, adding terminal device hardware information record.

Optionally, in the method for activating a device based on a domain controller according to the present invention, the method further includes: in response to the administrator's operation of activating a specified device, pushing a notification of creating a script task to the server of the domain controller platform, Make the domain control platform server notify the creation script according to the creation script task, and push the created script to the domain management client of the specified device, so that the domain management client executes the script to complete the Activation of the specified device described above.

According to another aspect of the present invention, a domain control-based device activation system is also provided, including: a domain management client and a batch activation client arranged on terminal devices, a domain control platform server arranged on the first server, and The batch activation server arranged on the second server; the domain management client is adapted to send a login request to the domain control platform server and execute the script sent by the domain control platform server, so that it can communicate with the domain management platform The batch activation client arranged on the same terminal device as the client connects to the batch activation server and completes the activation; the domain control platform server is suitable for verifying the legitimacy of the domain account login information sent by the domain management client , pushing a domain account login event notification to the batch activation server, and notifying the creation script according to the creation script task sent by the batch activation server, and sending the created script to the corresponding domain management client; The batch activation server is adapted to verify the batch activation server address and password carried in the domain account login event notification, and update the association relationship between the terminal device and the domain account after the verification is successful, and activate the domain account after the domain account activation When there is a remaining amount in the quantity, a notification of creating a script task is pushed to the server side of the domain control platform.

According to yet another aspect of the present invention, a readable storage medium storing program instructions is also provided. When the program instructions are read and executed by a computing device, the computing device executes the above domain-based Controlled device activation method or domain controller-based device activation method suitable for batch activation server.

According to the domain control-based device activation method, system and readable storage medium of the present invention, at least one of the following beneficial effects can be achieved: on the basis of the batch distribution serial number function of the traditional KMS batch activation scheme, the domain control The device management and control capabilities of the platform, adding terminal devices to the domain through the domain control platform, and verifying the domain account and password of the terminal device that requests to log in, realizes finer-grained control of terminal device activation, which is more secure and reliable; domain account Both the automatic activation triggered by login and the activation of the designated device are realized by issuing scripts. The user does not perceive the existence of the KMS service. Even if the batch activation server modifies the IP address and connection password, the activation of the terminal device will not be affected, and the batch activation service is blocked. The impact of the terminal connection configuration on the terminal equipment simplifies the user's operation process and increases the ease of use and reliability of the above method and system.

Description of drawings

To the accomplishment of the foregoing and related ends, certain illustrative aspects are herein described, taken in conjunction with the following description and drawings, which are indicative of the various ways in which the principles disclosed herein may be practiced, and all aspects and their equivalents are intended to fall within the scope of within the scope of the claimed subject matter. The above and other objects, features and advantages of the present disclosure will become more apparent by reading the following detailed description in conjunction with the accompanying drawings. Like reference numerals generally refer to like parts or elements throughout this disclosure.

FIG. 1 shows a schematic diagram of a domain control-based device activation system 100 according to an embodiment of the present invention;

Fig. 2 shows a schematic diagram of the principle of data synchronization between the domain control platform server and the batch activation server according to an embodiment of the present invention;

FIG. 3 shows a schematic diagram of a computing device 300 according to one embodiment of the present invention;

FIG. 4 shows a flow chart of a domain controller-based device activation method 400 according to an embodiment of the present invention;

FIG. 5 shows a flowchart of a domain control-based device activation method 500 according to an embodiment of the present invention;

FIG. 6 shows schematic diagrams of a method 400 and a method 500 according to an embodiment of the present invention;

Fig. 7 shows a flow chart of re-initiating an activation request according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

Aiming at the problem that the existing batch activation service cannot realize the activation management and control only for devices meeting specific conditions, a domain control-based device activation method, system and readable storage medium are provided.

Fig. 1 shows a schematic diagram of a domain controller-based device activation system 100 according to an embodiment of the present invention.

As shown in FIG. 1 , a domain control-based device activation system 100 includes a domain management client 111 and a batch activation client 112 arranged in a terminal device 110, a domain control platform server 121 arranged in a first server 120, and a domain control platform server 121 arranged in a The batch activation server 131 of the second server 130 . The domain management client 111 is suitable for sending a login request to the domain control platform server 121 and executing the script sent by the domain control platform server 121, so that the batch activation client 121 arranged on the same terminal device as the domain management client 111 is connected to Activate the server 131 in batches and complete the activation; the domain control platform server 121 is suitable for verifying the validity of the domain account login information sent by the domain management client 11, pushing the domain account login event notification to the batch activation server 131, and Create a script according to the script creation task notification sent by the batch activation server 131, and send the created script to the corresponding domain management client 111; the batch activation server 131 is suitable for the batch activation service carried in the domain account login event notification Verify the terminal address and password, and update the terminal device-domain account association relationship after the verification is successful, and push the creation script task notification to the domain control platform server 121 when the number of domain account activations has a remaining quota. Wherein, the first server 120 and the second server 130 may be two servers, or one server. When the first server 120 and the second server 130 are two servers, the two servers implement information synchronization through the HTTP POST interface. The batch activation server 131 communicates with the batch activation client 112 through TLS encrypted TCP messages.

Based on the traditional KMS batch activation, the system 100 adds the following activation access checks: 1. Whether the terminal device has joined the domain; 2. Whether the domain account used by the terminal device has consumed all the allocated activation codes. Through the above verification, more fine-grained management and control of terminal equipment can be realized.

In this embodiment, a KMS domain management module is added to the routine batch activation server 131 program for docking with the domain control platform server 121 . The domain account information and terminal device information of the batch activation server 131 and the domain control platform server 121 are synchronized. If the data of the domain control platform server 121 changes, the changed data will be synchronized to the batch activation server 131 . As shown in Figure 2, data synchronization includes, but is not limited to: domain account deactivation events, domain account deletion events, terminal deletion/terminal de-domain events, terminal deactivation events, and terminal activation events. For domain account deactivation and domain account deletion events, the batch activation server 131 needs to set the serial number quota of the deactivated or deleted domain account to 0, that is, no serial number is available under the deactivated or deleted domain account. For terminal deletion/terminal de-domain events and terminal deactivation events, the batch activation server 131 needs to record hardware information of deleted terminals, de-domain terminals, and deactivated terminals. For the event of enabling a terminal, the batch activation server 131 needs to add the hardware information record of the enabled terminal device.

The administrator creates the organizational structure and domain accounts in the domain control platform according to actual needs, and imports a batch of serial numbers into the domain control platform, and assigns these serial numbers to each domain account, and each domain account contains several. Taking an enterprise as an example, the organizational structure includes different departments at different levels, and each department contains several terminal devices. A domain account can be assigned to each department, and the number of domain accounts assigned to each department can be determined according to the number of terminal devices in each department. The number of serial numbers.

In an embodiment, the user can also apply for joining the domain on the terminal device 110 . The user sends a domain entry request on the terminal device 110; the domain management client 111 pushes the domain entry request to the domain control platform server 121, and the domain entry request carries the hardware device information of the terminal device 110 (such as the motherboard serial number, hard disk serial number, etc.) number, etc.); the domain control platform server 121 pushes a domain entry event notification to the batch activation server 131, and the domain entry event notification carries the above hardware device information; the batch activation server 131 adds the above hardware device information to the domain management hardware information During the recording, the domain entry of the terminal device 110 is completed.

After the terminal device 110 enters the domain, the batch activation server 131 will automatically return the IP address and password of the second server 130 to the terminal device 110. The user enters the domain account and password on the terminal device, and the domain management client 111 uses the domain account and password to , and the IP address and password of the second server 130 to generate a login request, and push the login request to the domain control platform server 121, the domain control platform server 121 checks the validity of the domain account number and password, and after the check is passed Push a domain account login event notification to the batch activation server 131, and the batch activation server 131 updates the association relationship between the terminal device and the domain account in the database. The specific method of updating is: the hardware information of the terminal device 110 carried in the domain account login event notification The association relationship with the domain account is updated. After the update is completed, check whether the domain account has an idle serial number. If there is an idle serial number, assign an idle serial number to the terminal device 110 and provide service to the domain control platform. Terminal 121 pushes a creation script task notification, which carries the above-mentioned serial number information in the creation script task notification, domain control platform server 121 creates a script according to the creation script task notification, and the function of the script is to connect the batch activation client 112 to the batch activation The server 131 completes the activation, and then calls the application programming interface (API) of the domain control platform server 121 to send the script content to the domain management client 111, and the domain management client 111 executes the script to complete the activation.

In one embodiment, when a terminal device 110 is in the activated state, if the IP address and/password of the batch activation server 131 changes, the batch activation server 131 will automatically pass the changed IP address and/password through the domain The control platform server 121 feeds back to the domain management client 111, and the domain management client 111 feeds back to the batch activation client 112, and the batch activation client 112 re-initiates an activation request to the batch activation server 131 according to the new IP address and password.

In one embodiment, the batch activation server 131 is embedded with a domain management module, and a list of online terminal devices is displayed on the domain management module interface. The administrator can issue activation scripts to the selected terminal devices on this interface to realize the activation of the specified device. activation.

It should be noted that the present invention does not limit the specific types of the terminal device 110 , the first server 120 and the second server 130 . For example, the first server 120 and the second server 130 may be implemented as computing devices such as desktop computers, notebook computers, processor chips, mobile phones, and tablet computers.

In one embodiment, the terminal device 110, the first server 120 and the second server 130 of the present invention can be implemented as a computing device, so that the domain control-based device activation method of the present invention can be executed in the computing device. The computing device can be any device with storage and computing capabilities, which can be implemented as a server, workstation, etc., or as a personal computer such as a desktop computer or a notebook computer, or as a mobile phone, a tablet computer, or a smart wearable device. , IoT devices and other terminal devices, but not limited thereto.

FIG. 3 shows a schematic diagram of a computing device 300 according to one embodiment of the invention. It should be noted that the computing device 300 shown in FIG. 3 is only an example. In practice, the computing device used to implement the domain control-based device activation method of the present invention may be any type of device, and its hardware configuration may be It is the same as the computing device 300 shown in FIG. 3 , or it may be different from the computing device 300 shown in FIG. 3 . In practice, the computing device used to implement the domain control-based device activation method of the present invention can add or delete hardware components of the computing device 300 shown in FIG. 3 , and the present invention does not limit the specific hardware configuration of the computing device .

It should be noted that the domain control-based device activation method of the present invention requires multiple computing devices 300 to be jointly implemented, and each computing device 300 is responsible for implementing a part of the domain control-based device activation method of the present invention.

As shown in FIG. 3 , the computing device 300 typically includes a memory 310 and a processor 320 , and the memory 310 and the processor 320 communicate through a bus 330 . Depending on the desired configuration, processor 320 may be any type of processing including, but not limited to, a microprocessor (μP), microcontroller (μC), digital signal processor (DSP), or any combination thereof. Depending on the desired configuration, memory 310 may be any type of memory including, but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. The memory 310 may include an operating system 311, program instructions 312 for executing a domain controller-based device activation method, and program data 313. The program data 313 may include files for recording associations between terminal devices and domain accounts and terminal device hardware information recording files. .

The computing device 300 can be implemented as a server, such as a file server, a database server, an application program server, and a WEB server, etc., and can also be implemented as a personal computer including a configuration of a desktop computer and a notebook computer. Of course, the computing device 300 can also be implemented as a part of a small-sized portable (or mobile) electronic device.

A domain control-based device activation method 400 according to an embodiment of the present invention is applicable to a domain control platform server. The method 400 includes: in response to receiving a login request pushed by a domain management client, verifying the domain account number and password carried in the login request command to verify, and after the verification is successful, push the domain account login notification to the batch activation server, so that the batch activation server can verify the batch activation server address and password carried in the domain account login notification, and After success, and when the number of domain account activations has a remaining quota, push the creation script task notification to the domain control platform server; and in response to receiving the creation script task notification pushed by the batch activation server, create a script according to the creation script task notification, and send The created script is pushed to the domain management client corresponding to the script, and the domain management client is arranged on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device.

Fig. 4 shows a flow chart of a domain controller-based device activation method 400 according to an embodiment of the present invention. The method 400 is executed in a computing device (such as the aforementioned computing device 300 ), and is used for finely managing and controlling the activation of the terminal device. As shown in FIG. 4 , method 400 begins at 410 .

In 410, in response to receiving the login request pushed by the domain management client 111, verify the domain account number and password command carried in the login request, and push the domain account login notification to the batch activation server 131 after the verification is successful, To enable the batch activation server 131 to verify the batch activation server address and password carried in the domain account login notification, and push the creation to the domain control platform server 121 after the verification is successful and the number of domain account activations has a remaining quota. Script task notification.

The user performs a login operation on the terminal device 110 through a domain account and password, and the domain management client 111 arranged on the terminal device 110 pushes a login request to the domain control platform server 121 arranged on the first server 120 . The domain control platform server 121 verifies the domain account and password carried in the login request, and pushes a domain account login notification to the batch activation server 131 after the verification is successful. The batch activation server 131 verifies the batch activation server address and password carried in the domain account login notification, and pushes the creation script to the domain control platform server 121 after the verification is successful and the number of domain account activations has a remaining quota. Task notification.

Next, in 420, after the domain control platform server 121 receives the script creation task notification pushed by the batch activation server 131, it creates a script according to the script creation task notification, for example, according to the batch activation server The address password and the domain identification code of the terminal device create an activation script, and then push the created script to the domain management client 111 corresponding to the script, and the domain management client 111 executes the script to complete the activation of the terminal device.

The domain management client 111 can also push a domain entry request to the domain control platform server 121. After receiving the domain entry request, the domain control platform server 121 pushes a domain entry event notification to the batch activation server 131, and the batch activation server 131 receives the domain entry event notification. After the domain entry event is notified, a new terminal device hardware information record is added in the database, and thus the terminal device 110 enters the domain.

A domain control-based device activation method 500 according to an embodiment of the present invention is suitable for batch activation of the server 131, including: in response to receiving the domain account login notification pushed by the domain control platform server 121, the domain account login notification carried Batch activation server addresses and passwords are verified, and after the verification is successful, the association relationship between the terminal device 110 and the domain account is updated; and when the number of domain account activations has a remaining quota, push the creation script task notification to the domain control platform server 121 , so that the domain control platform server 121 creates a script, and pushes the script to the domain management client 111 corresponding to the script, and the domain management client 111 is placed on the terminal device 110, so that the domain management client 111 executes the script and completes Activation of the terminal device 110 .

Fig. 5 shows a flow chart of a domain control-based device activation method 500 according to an embodiment of the present invention. The method 500 is executed in a computing device (such as the aforementioned computing device 300 ), and is used for finely managing and controlling the activation of the terminal device. As shown in FIG. 5 , method 500 begins at 510 .

In 510, in response to receiving the domain account login notification pushed by the domain control platform server 121, verify the batch activation server address and password carried in the domain account login notification, and update the terminal device 110 and Domain account association relationship.

The user performs a login operation on the terminal device 110 through a domain account and password, and the domain management client 111 arranged on the terminal device 110 pushes a login request to the domain control platform server 121 arranged on the first server 120 . The domain control platform server 121 verifies the domain account and password carried in the login request, and pushes a domain account login notification to the batch activation server 131 after the verification is successful. The batch activation server 131 verifies the batch activation server address and password carried in the domain account login notification, and updates the association relationship between the terminal device 110 and the domain account in the database after the verification is successful.

Next, in 520, when there is a remaining amount in the number of domain account activations, a notification of creating a script task is pushed to the domain control platform server 121, so that the domain control platform server 121 creates a script and pushes the script to the script corresponding to the script. The domain management client 111 is arranged on the terminal device 110 so that the domain management client 111 executes a script to complete the activation of the terminal device 110 .

Firstly, it is judged whether the number of domain account activations is still remaining, and if so, a notification of creating a script task is pushed to the domain control platform server 121, and the domain control platform server 121 starts to create the script after receiving the notification of creating the script task, and then uploads the created script The script is pushed to the domain management client 111 corresponding to the script, and the domain management client 111 executes the script to complete the activation of the terminal device 110 .

Based on the method 400 and the method 500, the embodiment of the present application provides a schematic diagram of a complete domain control-based device activation method, as shown in FIG. 6 .

The user performs a login operation on the terminal device 110 through a domain account and password, and the domain management client 111 pushes a login request to the domain control platform server 121 . The terminal device 111 that has entered the domain is called an intra-domain device, and only the intra-domain device that sends the correct batch activation server 131 IP address and password can be activated.

In one embodiment, the administrator assigns a certain number of activation codes (ie domain account activation code quota) to each domain account on the batch activation server 131 . The user can apply for joining the domain on the terminal device 110 . After the user sends a domain entry request operation on the terminal device 110, the domain management client 111 pushes the domain entry request to the domain control platform server 121. The domain entry request carries the hardware device information of the terminal device 110 requesting to enter the domain, and the domain control platform The server 121 uses the SHA to generate a digest according to the above hardware device information, and uses the generated digest as the intra-domain ID of the terminal device 110 requesting to enter the domain. Next, the domain control platform server 121 pushes a domain entry event notification to the batch activation server 131, and the domain entry notification carries the hardware device information and the domain ID of the terminal device 110 requesting to enter the domain. After the batch activation server 131 receives the domain entry event notification, it adds the above-mentioned in-domain ID and hardware device information record of the terminal device 110 requesting to enter the domain to the file in the database that records the hardware information of the in-domain device.

Devices in the domain can log in to the domain control platform through the domain account and password. The user enters the domain account and password on the device in the domain, and initiates a login. The domain management client 111 generates a login request according to the domain account, password, batch activation server IP address and password, and pushes the login request to the domain control platform server 121 . The domain account and password information carried in the login request is the domain account and password entered by the user, and the IP address and password of the batch activation server 131 carried in the login request are automatically fed back by the batch activation server 131 after the terminal device 110 enters the domain. Given to the terminal device 110 and stored in the terminal device 110, the user cannot access the above-mentioned IP address and password.

After receiving the login request pushed by the domain management client 111, the domain control platform server 121 verifies the domain account and password carried in the login request, and pushes a domain account login notification to the batch activation server 131 after the verification is successful. . The domain account login notification is generated by the domain control platform server 121 according to the domain account, the IP address and password of the batch activation server 131 and the hardware device information of the terminal device 110 .

After receiving the domain account login notification pushed by the domain control platform server 121, the batch activation server 131 verifies the IP address and password of the batch activation server 131 carried in the domain account login notification, and updates the terminal after the verification is successful. The association relationship between the device and the domain account, and when the remaining amount of activation number of the domain account is greater than 0 (that is, the number of activation codes in use under the domain account is less than the amount of activation codes of the domain account), push creation to the domain control platform server 121 Script task notification.

When the IP address and password carried in the domain account login notification are correct, the batch activation server 131 updates the file that records the terminal device-domain account association relationship. The update method is: according to the terminal Device 110 hardware device information and domain account, add the hardware device information to the domain account, realize the association between the hardware device information and the domain account, and at the same time, disassociate the hardware device information from other domain accounts. Then query the remaining amount of activation quantity of the domain account associated with the hardware device information of the terminal device 110 above. Each domain account is pre-assigned a certain number of activation codes, which are recyclable and shareable. Each terminal device 110 will consume an activation code when connected to the batch activation server 131, and the consumed activation code is in use , when the terminal device 110 exits from the batch activation server 131, the activation code is recycled. The remaining activation quantity of the domain account refers to the number of activation codes that are not in use for the domain account. If the remaining activation quantity of the domain account is greater than 0, it means that an available activation code can be assigned to the device in the domain logged in with the domain account. The creation script task notification includes the activation code assigned to the currently logged-in terminal device 110, the IP address of the batch activation server 131, the password, and the ID of the terminal device.

After receiving the script creation task notification pushed by the batch activation server 131, the domain control platform server 121 creates a script according to the script creation task notification, and pushes the created script to the domain management client 111 corresponding to the script. The function of the script is to point the activation address of the terminal device 110 to the KMS service, thereby triggering an activation application and automatically completing the activation.

After receiving the script pushed by the domain control platform server 121, the domain management client 111 executes the script. After the script is executed, the batch activation client 112 of the terminal device 110 connects to the batch activation server 131 and completes the activation. 110 activations.

Method 400 and method 500 add domain entry verification on the basis of traditional KMS batch activation, that is, verify whether the currently logged-in terminal device 110 has joined the domain, even if the IP port and password of the batch activation server 131 are leaked, if The device where the batch activation client 112 is located cannot complete the activation without joining the domain, which enhances the security of the KMS service and also realizes finer-grained control over the activation of terminal devices. In addition, method 400 and method 500 also simplify the activation process. Users do not need to pay attention to the IP address and password of the batch activation server 131. They only need to enter the domain account number and password to automatically complete the connection with the batch activation server and realize automatic activation. The change of the IP address and password of the activation server 131 does not affect the normal use of the terminal device 110 by the user.

For the activated terminal device 110, if the IP address of the batch activation server 131 changes (for example, the second server 130 is migrated from one device to another device), or the password changes, the existing KMS batch activation scheme needs to The user manually modifies the IP address and password on the terminal device 110 and re-initiates the activation request. Not only is the operation cumbersome, but there is also a risk of leakage of the IP address and password. The embodiment of the present application adopts the method of automatically initiating an activation request to avoid manual operation by the user, and also prevents the IP address and password from being leaked.

In one embodiment, the method for automatically initiating an activation request includes the following process: after the IP address and/or password of the batch activation server 131 are changed, the batch activation server 131 sends the changed batch activation server address IP and/or The password is pushed to the domain management client 111, and the domain management client 111 initiates an activation request to the batch activation server 131 according to the new IP address and password; as shown in Figure 7, the activation request is sent to the batch activation server in the form of a connection password 131, the batch activation server 131 checks the IP address and password in the connection password; after the verification is passed, the batch activation client 112 sends the hardware device information of the terminal device 110 to the batch activation server 131; the batch activation server 131 Allocate an idle serial number information for the terminal device 110, bind the serial number with the hardware device information of the terminal device 110, and feed back the serial number information to the batch activation client 112. It should be noted that the terminal device 110 received the serial number information, and the serial number information corresponds to the serial number one by one, the serial number information cannot be used directly, so there is no risk of being copied and leaked; next, the operating system of the terminal device 110 The serial number is verified, and the verification status is sent to the batch activation server 131. If the verification status is that the verification is successful, the batch activation server 131 sends a confirmation activation message to the batch activation client 112. After that, the batch activation client 112 regularly Send a heartbeat packet to the batch activation server 131. If the batch activation server 131 has not received a heartbeat packet from a certain terminal device 110 for a long time, it is considered that the connection between the terminal device 110 and the batch activation server 131 is disconnected. When the activation server 131 actively deactivates the serial number or detects that the batch activation client 112 is disconnected from the batch activation server 131, it releases the binding relationship between the serial number and the terminal device 110, and reclaims the serial number. When the volume activation server 131 actively deactivates the serial number, the volume activation client 112 is forced to disconnect from the volume activation server 131, after that, the volume activation client 112 initiates activation to the volume activation server 131 at a fixed time interval ask.

In one embodiment, the method 400 and the method 500 also support the administrator to activate the designated terminal device 110 . The administrator selects a terminal device 110 on the interface of the domain management module embedded in the batch activation server 131 and initiates an activation operation, and the batch activation server 131 will push the creation script to the domain control platform server 121 for the selected terminal device 110 Task notification.

The various techniques described herein can be implemented in conjunction with hardware or software, or a combination thereof. Thus, the method and device of the present invention, or certain aspects or parts of the method and device of the present invention may be embedded in a tangible medium, such as a removable hard disk, USB flash drive, floppy disk, CD-ROM or any other machine-readable storage medium In the form of program code (ie, instructions) in a machine such as a computer, when the program is loaded into a machine such as a computer and executed by the machine, the machine becomes an apparatus for practicing the invention.

In the case of program code execution on a programmable computer, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein, the memory is configured to store program codes; the processor is configured to execute the domain control-based device activation method of the present invention according to instructions in the program codes stored in the memory.

Readable media include, by way of example and not limitation, readable storage media and communication media. Readable storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of readable media.

In the description provided herein, the algorithms and displays are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used with examples of the invention. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing preferred embodiments of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention requires more features than are expressly recited in each claim. Those skilled in the art will understand that the modules or units or components of the devices in the examples disclosed herein may be arranged in the device as described in this embodiment, or alternatively may be located in a different location than the device in this example. in one or more devices. The modules in the preceding examples may be combined into one module or furthermore may be divided into a plurality of sub-modules.

Those skilled in the art can understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, those skilled in the art will understand that although some embodiments described herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant to be within the scope of the invention. and form different embodiments. Furthermore, some of the described embodiments are described herein as a method or combination of method elements that may be implemented by a processor of a computer system or by other means for performing the described function. Thus, a processor with the necessary instructions for carrying out the described method or element of a method forms a means for carrying out the method or element of a method. Furthermore, elements described herein of an apparatus embodiment are examples of means for carrying out the function performed by the element for the purpose of carrying out the invention.

As used herein, unless otherwise specified, the use of ordinal numbers "first," "second," "third," etc. to describe generic objects merely means referring to different instances of similar objects and is not intended to imply such The described objects must have a given order temporally, spatially, sequentially or in any other way.

While the invention has been described in terms of a limited number of embodiments, it will be apparent to a person skilled in the art having the benefit of the above description that other embodiments are conceivable within the scope of the invention thus described. In addition, it should be noted that the language used in the specification has been chosen primarily for the purpose of readability and instruction rather than to explain or define the inventive subject matter.

Claims (10)

1. A domain control-based device activation method, suitable for domain control platform servers, including: In response to receiving the login request pushed by the domain management client, verify the domain account number and password token carried in the login request, and push a domain account login notification to the batch activation server after the verification is successful, so that the The batch activation server verifies the batch activation server address and password carried in the domain account login notification, and after the verification is successful and the number of domain account activations has a remaining quota, pushes the creation server to the domain control platform server. Script task notifications; and In response to receiving the script creation task notification pushed by the batch activation server, create a script according to the script creation task notification, and push the created script to the domain management client corresponding to the script, the domain management The client is arranged on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device. 2. The domain control-based device activation method according to claim 1, further comprising: In response to receiving the domain entry request pushed by the domain management client, push a domain entry event notification to the batch activation server, so that the batch activation server adds a terminal device hardware information record in the database. 3. The domain control-based device activation method according to claim 1 or 2, wherein the creating script task notification according to the creating script comprises: An activation script is created according to the batch activation server address, the password, and the intra-domain identity code of the terminal device carried in the script creation task notification. 4. A domain controller-based device activation method, suitable for batch activation of servers, including: In response to receiving the domain account login notification pushed by the domain control platform server, verify the batch activation server address and password carried in the domain account login notification, and update the association between the terminal device and the domain account after the verification is successful relationship; and When the activation quantity of the domain account has a remaining amount, push the creation script task notification to the domain control platform server, so that the domain control platform server creates a script, and pushes the script to a location corresponding to the script A domain management client, the domain management client is arranged on the terminal device, so that the domain management client executes the script to complete the activation of the terminal device. 5. The domain control-based device activation method according to claim 4, further comprising: In response to the change of the batch activation server address and/or password, the changed batch activation server address and/or password are pushed to the domain management client. 6. The domain control-based device activation method according to claim 4 or 5, further comprising: In response to receiving the activation request pushed by the domain management client, verifying the batch activation server address and password carried in the activation request; and After the verification is successful, return the serial number to the domain management client, and bind the serial number with the hardware information of the terminal device. 7. The domain control-based device activation method according to any one of claims 4 to 6, further comprising: In response to receiving the domain entry event notification pushed by the domain control platform server, a new terminal device hardware information record is added in the database. 8. The domain control-based device activation method according to any one of claims 4 to 7, further comprising: Responding to the administrator's operation of activating the specified device, push the creation script task notification to the domain control platform server, so that the domain control platform server notifies the creation script according to the creation script task, and sends the created script The script is pushed to the domain management client of the designated device, so that the domain management client executes the script to complete the activation of the designated device. 9. A device activation system based on domain control, including a domain management client and a batch activation client arranged on terminal devices, a domain control platform server arranged on the first server, and a batch activation server arranged on the second server ; The domain management client is adapted to send a login request to the domain control platform server and execute the script sent by the domain control platform server, so that the batch activation client arranged on the same terminal device as the domain management client connect to the batch activation server and complete the activation; The domain control platform server is adapted to verify the legitimacy of the domain account login information sent by the domain management client, push a domain account login event notification to the batch activation server, and according to the batch activation service The script creation task sent by the terminal notifies the creation script, and sends the created script to the corresponding domain management client; The batch activation server is adapted to verify the batch activation server address and password carried in the domain account login event notification, and update the association relationship between the terminal device and the domain account after the verification is successful, and When the number of account activations has a remaining quota, a notification of creating a script task is pushed to the server side of the domain control platform. 10. A readable storage medium storing program instructions. When the program instructions are read and executed by a computing device, the computing device executes the domain-based control system according to any one of claims 1-3. The device activation method or the domain control-based device activation method described in any one of claims 4-8.

Images