CN116340902A

CN116340902A - Domain control-based device activation method, system and readable storage medium

Info

Publication number: CN116340902A
Application number: CN202310274474.4A
Authority: CN
Inventors: 李鹏伟
Original assignee: Uniontech Software Technology Co Ltd
Current assignee: Uniontech Software Technology Co Ltd
Priority date: 2023-03-20
Filing date: 2023-03-20
Publication date: 2023-06-27

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

Domain control-based device activation method, system and readable storage medium

Technical Field

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

Background

Modern operating systems or business software typically employ activation controls to govern their functional characteristics. Common activation schemes are mainly serial number activation, activation file activation, online activation, and batch activation tool activation.

Serial number activation is also called activation code, and the serial number must be manually input by a user, so that the serial number is risked to be duplicated and propagated, and the security is poor.

Activation of an activation file is similar to serial number activation, the activation file must be manually imported by a user, and there is also a risk of being duplicated and distributed, which is difficult to manage.

The online activation needs to register an account in advance, and the account is automatically activated after logging in, so that the scheme is not suitable for places which cannot be connected with a wide area network or have higher network security level.

The batch activation tool is a service for providing batch activation, and the device connected to the specific network can use the serial number in the import server in a rotating way, and the activation mode needs to deploy the batch activation service (Key Management Service, KMS), import a batch of serial numbers to the batch activation tool at one time, and the device/software needing to be activated can log in the batch activation service only by inputting the IP port and the password of the KMS to complete automatic activation. Batch activation tool activation has the following advantages over serial number activation and activation file activation: 1. the user can be prevented from touching the serial number which can be directly used for activation, and the safety of data is enhanced; 2. the batch activation service can be deployed in a public network or a local area network according to a user scene, so that the applicability is wider than that of online activation; 3. for the requirement of large-batch activation, different activation codes are not required to be manually input for each device or different activation files are not required to be manually imported, so that the activation flow can be greatly simplified, and the user experience is improved; 4. the serial number is recoverable and shared, the device only consumes the serial number of the service when the device is connected with the KMS, and when the device is disconnected from the KMS, the server can recover the serial number for other devices to use.

For the batch activation service, all devices connected through the IP port and the correct password are the same, but some institutions need to implement finer control over the activation of different departments of different levels of terminal devices, for example, enterprises with strong confidentiality, only allow part of terminal devices to be activated, so that the traditional batch activation service obviously cannot meet the requirements.

In summary, the existing batch activation service has the problem that fine control cannot be performed on the activation of the terminal equipment.

Disclosure of Invention

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

According to one aspect of the present invention, there is provided a domain-controlled device activation method applicable to a domain-controlled platform server, including: responding to a login request pushed by a domain management client, checking a domain account and a password carried by the login request, pushing a domain account login notification to a batch activation server after the verification is successful, so that the batch activation server checks a batch activation server address and a password carried by the domain account login notification, and pushing a script creating task notification to the domain control platform server when the verification is successful and the domain account activation number has residual credit; and responding to the received notice of the task of creating the script pushed by the batch activation server, creating the script according to the notice of the task of creating the script, pushing the created script to a domain management client corresponding to the script, wherein the domain management client is arranged on the terminal equipment so as to enable the domain management client to execute the script and complete the activation of the terminal equipment.

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

Optionally, in the domain-based device activation method according to the present invention, the notifying the creation script according to the creation script task includes: and creating an activation script according to the batch activation server addresses, the passwords and the intra-domain identification codes of the terminal equipment, which are carried by the script creating task notification.

According to another aspect of the present invention, there is provided a domain-control-based device activation method suitable for activating service terminals in batches, including: responding to a domain account login notification pushed by a domain control platform server, checking a batch activation server address and a password carried by the domain account login notification, and updating the association relationship between terminal equipment and a domain account after the verification is successful; and pushing a script creation task notification to the domain control platform server when the number of the domain account activations has residual amount, so that the domain control platform server creates a script and pushes the script to a domain management client corresponding to the script, wherein the domain management client is arranged on the terminal equipment, so that the domain management client executes the script to complete the activation of the terminal equipment.

Optionally, in the domain-control-based device activation method according to the present invention, in response to a change of the bulk activation server address and/or password, the changed bulk activation server address and/or password is pushed to the domain management client.

Optionally, in the domain control-based device activation method according to the present invention, in response to receiving an activation request pushed by the domain management client, a batch activation server address and password carried by the activation request are checked; 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 equipment.

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

Optionally, in the domain-based device activation method according to the present invention, the method further includes: and in response to the operation of activating the appointed equipment by an administrator, pushing a script creating task notification to the domain control platform server side so that the domain control platform server side creates a script according to the script creating task notification, pushing the created script to a domain management client side of the appointed equipment, enabling the domain management client side to execute the script, and completing activation of the appointed equipment.

According to still another aspect of the present invention, there is also provided a domain-based device activation system, including: the system comprises a domain management client and a batch activation client which are arranged on terminal equipment, a domain control platform server which is arranged on a first server, and a batch activation server which is arranged on a second server; the domain management client is suitable for sending a login request to the domain control platform server and executing a script sent by the domain control platform server, so that a batch activation client which is arranged at the same terminal equipment as the domain management client is connected to the batch activation server and completes activation; the domain control platform server is suitable for verifying the validity of domain account login information sent by the domain management client, pushing domain account login event notification to the batch activation server, creating a script according to the script creating task notification sent by the batch activation server, and sending the created script to the corresponding domain management client; the batch activation server is suitable for verifying the batch activation server address and password carried by the domain account login event notification, updating the association relation between the terminal equipment and the domain account after verification is successful, and pushing the script creating task notification to the domain control platform server when the domain account activation number has residual amount.

According to still another aspect of the present invention, there is also provided a readable storage medium storing program instructions that, when read and executed by a computing device, cause the computing device to perform the domain-controlled device activation method applicable to a domain-controlled platform service or the domain-controlled device activation method applicable to a batch activation service as described above.

According to the domain control-based device activation method, the domain control-based device activation system and the readable storage medium, 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 device management and control capability of a domain control platform is increased, terminal devices are added into a domain through the domain control platform, and the domain account number and the password of the terminal devices requesting login are checked, so that the terminal devices are activated to be managed and controlled in finer granularity, and the system is safer and more reliable; the automatic activation of the domain account login trigger and the activation of the designated equipment are realized by issuing scripts, a user cannot perceive the existence of KMS service, the activation of the terminal equipment is not affected even if the batch activation server modifies an IP address and a connection password, the influence of the batch activation server connection configuration on the terminal equipment is shielded, the operation flow of the user is simplified, and the usability and the reliability of the method and the system are improved.

Drawings

To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings, which set forth the various ways in which the principles disclosed herein may be practiced, and all aspects and equivalents thereof are intended to fall within the scope of the claimed subject matter. The above, as well as additional objects, features, and advantages of the present disclosure will become more apparent from the following detailed description when read in conjunction with the accompanying drawings. Like reference numerals generally refer to like parts or elements throughout the present disclosure.

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

FIG. 2 is a schematic diagram illustrating a data synchronization principle between a domain control platform server and a 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 invention;

FIG. 4 illustrates a flow chart of a domain-based device activation method 400 according to one embodiment of the invention;

FIG. 5 illustrates a flow chart of a domain-based device activation method 500 according to one embodiment of the invention;

FIG. 6 shows a schematic diagram of a method 400 and a method 500 according to one embodiment of the invention;

FIG. 7 illustrates a flow diagram for reinitiating an activation request, according to one embodiment of the invention.

Detailed Description

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While 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 to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Aiming at the problem that the existing batch activation service can not realize the activation control of the equipment meeting the specific conditions, the method, the system and the readable storage medium for activating the equipment based on domain control are provided.

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

As shown in fig. 1, the domain-based device activation system 100 includes a domain management client 111 and a bulk activation client 112 disposed in a terminal device 110, a domain control platform server 121 disposed in a first server 120, and a bulk activation server 131 disposed in a second server 130. The domain management client 111 is adapted to send a login request to the domain control platform server 121 and execute a script sent by the domain control platform server 121, so that the batch activation client 121 arranged at the same terminal device as the domain management client 111 is connected to the batch activation server 131 and completes activation; the domain control platform server 121 is adapted to verify the validity of the domain account login information sent from the domain management client 11, push a domain account login event notification to the batch activation server 131, create a script according to the created script task notification sent from the batch activation server 131, and send the created script to the corresponding domain management client 111; the batch activation server 131 is adapted to verify the address and password of the batch activation server carried by the domain account login event notification, update the association relationship between the terminal device and the domain account after the verification is successful, and push the creation script task notification to the domain control platform server 121 when the domain account activation number has the remaining amount. 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 achieve information synchronization through the HTTP POST interface. The bulk activation server 131 communicates with the TCP messages encrypted by the bulk activation client 112 via TLS.

The system 100 adds the following activation admission checks on the basis of conventional KMS batch activation: 1. whether the terminal equipment has joined the domain; 2. whether the domain account number used by the terminal device has consumed the assigned activation code. Through the verification, finer control over the terminal equipment can be realized.

In this embodiment, a KMS domain management module is added to the conventional batch activation server 131 program, so as to interface with the domain control platform server 121. The batch activation server 131 is synchronous with the domain account information and the terminal device information of the domain control platform server 121, and if the data of the domain control platform server 121 is changed, the changed data is synchronized to the batch activation server 131. As shown in fig. 2, data synchronization includes, but is not limited to: disabling domain account events, deleting terminal/terminal leave domain events, disabling terminal events, enabling terminal events, etc. For the event of disabling the domain account and the event of deleting the domain account, the batch activation server 131 needs to set the serial number limit of the disabled or deleted domain account to 0, that is, no available serial number under the disabled or deleted domain account. For the delete terminal/terminal leave domain event and the deactivate terminal event, the bulk activation server 131 needs to record the hardware information of the deleted terminal, the terminal leave domain, and the deactivated terminal. For an enabled terminal event, the bulk activation server 131 needs to add a hardware information record of the enabled terminal device.

An administrator creates an organization architecture and domain accounts in the domain control platform according to actual needs, introduces a batch of serial numbers into the domain control platform, distributes the serial numbers to each domain account, and comprises a plurality of each domain account. Taking an enterprise as an example, the organization architecture comprises different departments of different levels, each department further comprises a plurality of terminal devices, a domain account number can be allocated to each department, and the number of serial numbers allocated to each domain account number is determined according to the number of the terminal devices of each department.

In one embodiment, the user may also apply for entering the domain on terminal device 110. A user sends a request for entering a domain on the terminal equipment 110; the domain management client 111 pushes a domain entry request to the domain control platform server 121, where the domain entry request carries hardware device information (such as a motherboard serial number, a hard disk serial number, etc.) of the terminal device 110; the domain control platform server 121 pushes a domain entry event notification to the batch activation server 131, wherein the domain entry event notification carries the hardware device information; the batch activation server 131 adds the hardware device information to the domain management hardware information record, so as to complete the domain entry of the terminal device 110.

After the terminal device 110 enters the domain, the batch activation server 131 automatically returns the IP address and password of the second server 130 to the terminal device 110, the user inputs the domain account number and password on the terminal device, the domain management client 111 generates a login request according to the domain account number and password and the IP address and password of the second server 130, and pushes 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, pushes a domain account number login event notification to the batch activation server 131, the batch activation server 131 updates the association relationship between the terminal device and the domain account number in the database in the following specific ways: updating the association relationship between the hardware information of the terminal equipment 110 carried by the domain account login event notification and the domain account, after updating, inquiring whether the domain account has an idle serial number, if yes, allocating an idle serial number for the terminal equipment 110, pushing a script creating task notification to the domain control platform server 121, wherein the script creating task notification carries the serial number information, the domain control platform server 121 creates a script according to the script creating task notification, the function of the script is to connect the batch activation client 112 to the batch activation server 131 and complete activation, then call an Application Programming Interface (API) of the domain control platform server 121 to send script content to the domain management client 111, and the domain management client 111 executes the script to complete activation.

In one embodiment, when a certain terminal device 110 is in an active state, if the IP address and/or password of the bulk activation server 131 change, the bulk activation server 131 automatically feeds back the changed IP address and/or password to the domain management client 111 through the domain control platform server 121, the domain management client 111 feeds back to the bulk activation client 112, and the bulk activation client 112 re-initiates an activation request to the bulk 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 domain management module interface displays an online terminal device list, so that an administrator can issue an activation script to a selected terminal device on the interface to activate a designated device.

It should be noted that the present invention is not limited to the specific kind 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, cell phones, tablet computers, and the like.

In one embodiment, the terminal device 110, the first server 120, and the second server 130 of the present invention may be implemented as one computing device, such that the domain-based device activation method of the present invention may be performed in the computing device. The computing device may be any device having storage and computing capabilities, and may be implemented, for example, as a server, a workstation, or the like, or may be implemented as a personal configured computer such as a desktop computer, a notebook computer, or may be implemented as a terminal device such as a mobile phone, a tablet computer, an intelligent wearable device, or an internet of things device, but is 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, and in practice, the computing device used to implement the domain-based device activation method of the present invention may be any type of device, and the hardware configuration of the computing device may be the same as that of the computing device 300 shown in fig. 3 or may be different from that of the computing device 300 shown in fig. 3. In practice, the computing device for implementing the domain-based device activation method of the present invention may add or delete hardware components of the computing device 300 shown in fig. 3, and the present invention is not limited to the specific hardware configuration of the computing device.

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

As shown in fig. 3, computing device 300 typically includes memory 310 and processor 320, with communication between memory 310 and processor 320 via bus 330. Depending on the desired configuration, processor 320 may be any type of processing including, but not limited to: a microprocessor (μp), a microcontroller (μc), a digital information 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 to perform a domain-based device activation method, and program data 313, and the program data 313 may include a file for recording an association relationship of a terminal device-domain account number and a terminal device hardware information recording file.

Computing device 300 may be implemented as a server, such as a file server, database server, application server, WEB server, etc., as well as a personal computer including desktop and notebook computer configurations. Of course, computing device 300 may also be implemented as part of a small-sized portable (or mobile) electronic device.

The domain control-based device activation method 400 according to the embodiment of the present invention is applicable to a domain control platform server, and the method 400 includes: responding to a login request pushed by a domain management client, checking a domain account number and a password carried by the login request, pushing a domain account number login notification to a batch activation server after the verification is successful, so that the batch activation server checks a batch activation server address and a password carried by the domain account number login notification, and pushing a script creating task notification to a domain control platform server after the verification is successful and when the domain account number activation number has residual credit; and responding to the received notice of the task of creating the script pushed by the batch activation server, creating the script according to the notice of the task of creating the script, pushing the created script to a domain management client corresponding to the script, and arranging the domain management client on the terminal equipment so as to enable the domain management client to execute the script to complete the activation of the terminal equipment.

Fig. 4 shows a flow chart of a domain-based device activation method 400 according to one embodiment of the invention. The method 400 is performed in a computing device (e.g., the aforementioned computing device 300) for fine-grained management of activation of a 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, the domain account number and password carried by the login request are checked, and after the verification is successful, a domain account number login notification is pushed to the batch activation server 131, so that the batch activation server 131 verifies the batch activation server address and password carried by the domain account number login notification, and after the verification is successful, and when the domain account number activation number has residual amount, a script task creation notification is pushed to the domain control platform server 121.

The user performs a login operation on the terminal device 110 through a domain account number and a password, and the domain management client 111 disposed on the terminal device 110 pushes a login request to the domain control platform server 121 disposed on the first server 120. The domain control platform server 121 checks the domain account number and password carried by the login request, and pushes a domain account number login notification to the batch activation server 131 after the verification is successful. The batch activation server 131 checks the batch activation server address and password carried in the domain account login notification, and pushes the creation script task notification to the domain control platform server 121 after the verification is successful and when the domain account activation number has the remaining amount.

Next, in 420, after receiving the task notification of the creation script pushed by the batch activation server 131, the domain control platform server 121 creates a script according to the task notification of the creation script, for example, the activation script may be created according to the address password of the batch activation server and the domain id code of the terminal device carried by the task notification of the creation script, and then the created script is pushed to the domain management client 111 corresponding to the script, and the domain management client 111 executes the script to complete activation of the terminal device.

The domain management client 111 may also push a domain entering request to the domain control platform server 121, after receiving the domain entering request, the domain control platform server 121 pushes a domain entering event notification to the batch activation server 131, and after receiving the domain entering event notification, the batch activation server 131 adds a hardware information record of the terminal device in the database, so as to complete the domain entering of the terminal device 110.

A domain-based device activation method 500 according to an embodiment of the present invention is applicable to a batch activation server 131, and includes: in response to receiving a domain account login notification pushed by the domain control platform server 121, verifying a batch activation server address and a password carried by the domain account login notification, and updating the association relationship between the terminal equipment 110 and the domain account after verification is successful; and pushing a script creation task notification to the domain control platform server 121 when the number of domain account number activations has residual credit, 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, wherein the domain management client 111 is arranged on the terminal equipment 110, so that the domain management client 111 executes the script to complete activation of the terminal equipment 110.

Fig. 5 shows a flow chart of a domain-based device activation method 500 according to one embodiment of the invention. The method 500 is performed in a computing device (e.g., the aforementioned computing device 300) for fine-grained management of activation of a 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, verifying the batch activation server address and the password carried by the domain account login notification, and updating the association relationship between the terminal device 110 and the domain account after the verification is successful.

The user performs a login operation on the terminal device 110 through a domain account number and a password, and the domain management client 111 disposed on the terminal device 110 pushes a login request to the domain control platform server 121 disposed on the first server 120. The domain control platform server 121 checks the domain account number and password carried by the login request, and pushes a domain account number login notification to the batch activation server 131 after the verification is successful. The batch activation server 131 checks 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 the number of domain accounts activated has the remaining amount, a task notification of creating a script is pushed to the domain control platform server 121, so that the domain control platform server 121 creates the script and pushes the script to the domain management client 111 corresponding to the script, and the domain management client 111 is disposed on the terminal device 110, so that the domain management client 111 executes the script, and activation of the terminal device 110 is completed.

Firstly, judging whether the number of domain account number activations is remained, if so, pushing a script creating task notification to the domain control platform server 121, starting to create a script after the domain control platform server 121 receives the script creating task notification, then pushing the created script to the domain management client 111 corresponding to the script, and executing the script by the domain management client 111 to complete activation of the terminal equipment 110.

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

The user performs a login operation on the terminal device 110 through the domain account number and the 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 transmits the IP address and password of the correct batch activation server 131 can be activated.

In one embodiment, a certain number of activation codes (i.e., domain account number activation code amounts) are assigned to each domain account number by an administrator on the bulk activation server 131. The user may apply for entering the domain on the terminal device 110. After a user sends a domain entering request operation on the terminal device 110, the domain management client 111 pushes a domain entering request to the domain control platform server 121, the domain entering request carries hardware device information of the terminal device 110 requesting to enter a domain, and the domain control platform server 121 generates a digest by using SHA according to the hardware device information and takes the generated digest as a domain ID of the terminal device 110 requesting to enter the domain. Next, the domain control platform server 121 pushes a domain-in event notification to the batch activation server 131, the domain-in notification carrying hardware device information and the domain ID of the terminal device 110 requesting the domain-in. After receiving the notification of the event of entering the domain, the batch activation server 131 newly adds the domain ID and the hardware device information record of the terminal device 110 requesting to enter the domain in the file of the hardware information of the device in the database.

The device in the domain can log in the domain control platform through the domain account number and the password. The user inputs a domain account number and a password on the device in the domain, initiates login, and the domain management client 111 generates a login request according to the domain account number, the password, the batch activation server IP address and the password, and pushes the login request to the domain control platform server 121. The domain account number and password information carried by the login request are the domain account number and password input by the user, and the IP address and password of the batch activation server 131 carried by the login request are automatically fed back to the terminal equipment 110 by the batch activation server 131 after the terminal equipment 110 enters the domain and are stored in the terminal equipment 110, so that the user cannot touch the IP address and password.

After receiving the login request pushed by the domain management client 111, the domain control platform server 121 checks the domain account number and the password carried by the login request, and pushes a domain account number 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 checks the IP address and password of the batch activation server 131 carried by the domain account login notification, updates the association relationship between the terminal device and the domain account after the verification is successful, and pushes the creation script task notification to the domain control platform server 121 when the remaining amount of the domain account activation number is greater than 0 (i.e., the number of activation codes in a use state under the domain account is less than the amount of the domain account activation code).

Under the condition that the IP address and the password carried by the domain account login notification are correct, the batch activation server 131 updates the file recording the association relationship between the terminal equipment and the domain account in the following update mode: and adding the hardware equipment information to the domain account according to the hardware equipment information and the domain account of the terminal equipment 110 carried by the domain account login notification to realize the association of the hardware equipment information and the domain account, and simultaneously, releasing the association relationship between the hardware equipment information and other domain accounts. And then inquires the remaining amount of the activation number of the domain account number associated with the hardware device information of the terminal device 110. Each domain account number is pre-assigned a certain number of activation codes, the activation codes are recyclable and shareable, each terminal device 110 consumes one activation code when connected to the batch activation service 131, the consumed activation code is in use, and the activation code is recycled when the terminal device 110 exits from the batch activation service 131. The remaining activated number of the domain account refers to the number of activated codes of the domain account which are not in use, and if the remaining activated number of the domain account is greater than 0, the available activated codes can be allocated to the devices in the domain logged in by using the domain account. The script task creation notification includes an activation code assigned to the currently logged-in terminal device 110, an IP address of the batch activation server 131, a password, and an ID of the terminal device.

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

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

The method 400 and the method 500 add the in-domain verification based on the 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 the password of the batch activation server 131 leak, if the device of the batch activation client 112 does not join the domain, the activation cannot be completed, so that the security of the KMS service is enhanced, and at the same time, the management and control of activating the terminal device with finer granularity is also realized. In addition, the method 400 and the method 500 simplify the activation process, the user does not need to pay attention to the IP address and the password of the batch activation server 131, and can automatically complete the connection with the batch activation server and realize automatic activation only by inputting the domain account number and the password, and the change of the IP address and the password of the batch 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 bulk 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 bulk activation scheme needs to manually modify the IP address and the password on the terminal device 110 by the user, and the activation request is restarted, which not only has complicated operation, but also has a leakage risk of the IP address and the password. According to the embodiment of the application, the mode of automatically initiating the activation request is adopted to avoid manual operation of a user, and meanwhile, the leakage of the IP address and the password is avoided.

In one embodiment, a method of automatically initiating an activation request includes the following: after the IP address and/or password of the batch activation server 131 are changed, the batch activation server 131 pushes the changed batch activation server address IP and/or password 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 fig. 7, the activation request is sent to the batch activation server 131 in the form of a connection password, and the batch activation server 131 verifies the IP address and the 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 allocates an idle serial number information to the terminal device 110, binds the serial number with hardware device information of the terminal device 110, and feeds back the serial number information to the batch activation client 112, where it should be noted that although the terminal device 110 receives the serial number information, the serial number information corresponds to the serial number one by one, the serial number information cannot be directly used, so there is no risk of copy leakage; next, the operating system of the terminal device 110 checks the serial number, and sends a verification status to the bulk activation server 131, if the verification status is that the verification is successful, the bulk activation server 131 sends confirmation activation information to the bulk activation client 112, after that, the bulk activation client 112 periodically initiates a heartbeat packet to the bulk activation server 131, if the bulk activation server 131 does not receive the heartbeat packet sent by a certain terminal device 110 for a long time, the connection between the terminal device 110 and the bulk activation server 131 is considered to be disconnected, and when the bulk activation server 131 actively deactivates the serial number or monitors that the connection between the bulk activation client 112 and the bulk activation server 131 is disconnected, the binding relationship between the serial number and the terminal device 110 is released, and the serial number is recovered. When the bulk activation server 131 actively deactivates the serial number, the bulk activation client 112 is forced to disconnect from the bulk activation server 131, after which the bulk activation client 112 initiates an activation request to the bulk activation server 131 at fixed time intervals.

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

The various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions of the methods and apparatus of the present invention, may take the form of program code (i.e., instructions) embodied in tangible media, such as removable hard drives, U-drives, floppy diskettes, CD-ROMs, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.

In the case of program code execution on programmable computers, the computing device will generally include 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 code; the processor is configured to execute the domain-based device activation method of the present invention in accordance with instructions in said program code stored in the memory.

By way of example, and not limitation, readable media comprise readable storage media and communication media. The readable storage medium stores 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, algorithms and displays are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with examples of the invention. The required structure for a construction of such a system is apparent from the description above. In addition, the present invention is not directed to any particular programming language. It should be appreciated that the teachings of the present invention as described herein may be implemented in a variety of programming languages and that the foregoing descriptions of specific languages are provided for disclosure of 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 an understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment, or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into a plurality of sub-modules.

Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any 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 appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. Furthermore, some of the embodiments are described herein as methods or combinations of method elements that may be implemented by a processor of a computer system or by other means of performing the functions. Thus, a processor with the necessary instructions for implementing the described method or method element forms a means for implementing the method or method element. Furthermore, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is for carrying out the functions performed by the elements for carrying out the objects of the invention.

As used herein, unless otherwise specified the use of the ordinal terms "first," "second," "third," etc., to describe a general object merely denote different instances of like objects, and are not intended to imply that the objects so described must have a given order, either temporally, spatially, in ranking, or in any other manner.

While the invention has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of the above description, will appreciate that other embodiments are contemplated within the scope of the invention as described herein. Furthermore, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter.

Claims

1. The device activation method based on domain control is suitable for a domain control platform server and comprises the following steps:

responding to a login request pushed by a domain management client, checking a domain account and a password carried by the login request, pushing a domain account login notification to a batch activation server after the verification is successful, so that the batch activation server checks a batch activation server address and a password carried by the domain account login notification, and pushing a script creating task notification to the domain control platform server when the verification is successful and the domain account activation number has residual credit; and

and responding to the received notice of the task of creating the script pushed by the batch activation server, creating the script according to the notice of the task of creating the script, pushing the created script to a domain management client corresponding to the script, wherein the domain management client is arranged on the terminal equipment so as to enable the domain management client to execute the script and complete the activation of the terminal equipment.

2. The domain-based device activation method of claim 1, further comprising:

and in response to receiving a domain entering request pushed by the domain management client, pushing a domain entering event notification to the batch activation server, so that the batch activation server adds a terminal equipment hardware information record in a database.

3. The domain-based device activation method of claim 1 or 2, wherein the notifying creation script according to the creation script task comprises:

and creating an activation script according to the batch activation server addresses, the passwords and the intra-domain identification codes of the terminal equipment, which are carried by the script creating task notification.

4. A device activation method based on domain control is applicable to a batch activation server and comprises the following steps:

responding to a domain account login notification pushed by a domain control platform server, checking a batch activation server address and a password carried by the domain account login notification, and updating the association relationship between terminal equipment and a domain account after the verification is successful; and

pushing a script creating task notification to the domain control platform server when the number of the domain account number activations has residual amount, so that the domain control platform server creates a script and pushes the script to a domain management client corresponding to the script, wherein the domain management client is arranged on the terminal equipment, so that the domain management client executes the script to complete activation of the terminal equipment.

5. The domain-based device activation method of claim 4, further comprising:

and in response to the change of the batch activation server address and/or password, pushing the changed batch activation server address and/or password to the domain management client.

6. The domain-based device activation method of claim 4 or 5, further comprising:

responding to the received activation request pushed by the domain management client, and checking a batch activation server address and a password carried by the activation request; and

and after the verification is successful, returning a serial number to the domain management client, and binding the serial number with the hardware information of the terminal equipment.

7. The domain-based device activation method of any one of claims 4 to 6, further comprising:

and in response to receiving the domain entering event notification pushed by the domain control platform server, newly adding a terminal equipment hardware information record in a database.

8. The domain-based device activation method of any one of claims 4 to 7, further comprising:

and in response to the operation of activating the appointed equipment by an administrator, pushing a script creating task notification to the domain control platform server side so that the domain control platform server side creates a script according to the script creating task notification, pushing the created script to a domain management client side of the appointed equipment, enabling the domain management client side to execute the script, and completing activation of the appointed equipment.

9. The domain control-based equipment activation system comprises a domain management client and a batch activation client which are arranged on terminal equipment, a domain control platform server arranged on a first server and a batch activation server arranged on a second server;

the domain management client is suitable for sending a login request to the domain control platform server and executing a script sent by the domain control platform server, so that a batch activation client which is arranged at the same terminal equipment as the domain management client is connected to the batch activation server and completes activation;

the domain control platform server is suitable for verifying the validity of domain account login information sent by the domain management client, pushing domain account login event notification to the batch activation server, creating a script according to the script creating task notification sent by the batch activation server, and sending the created script to the corresponding domain management client;

the batch activation server is suitable for verifying the batch activation server address and password carried by the domain account login event notification, updating the association relation between the terminal equipment and the domain account after verification is successful, and pushing the script creating task notification to the domain control platform server when the domain account activation number has residual amount.

10. A readable storage medium storing program instructions which, when read and executed by a computing device, cause the computing device to perform the domain-based device activation method of any one of claims 1-3 or the domain-based device activation method of any one of claims 4-8.