TW200933380A - Hierarchical authorization management system and method thereof - Google Patents

Abstract

A hierarchical authorization management system and a method thereof are provided. The purpose of said system and said method is to solve the heavy loading and the difficulties to manage the authorization amount resulting from processing authorization procedures through single authorization management server. By authorizing each managing server via the authorization server, and managing the authorization amount by the managing server, said system and said method can therefore promote the efficiency of processing authorization management.

Description

200933380 IX. Description of the invention: [Technical field to which the invention pertains] An authorization management system and method, in particular, for managing a server by authorizing the server to be uniformly authorized to the management server and managing the number of authorizations by the management server. Hierarchical authorization management system and method. [Prior Art] Due to the rapid development of computer storage media and network technology, programs on computer executable platforms such as beta systems, anti-virus software and general applications can not only use the burner to perform optical discs without restrictions. Copying can be spread unrestrictedly through a network with a high transmission speed. Therefore, the convenience of copying and distributing the program has been greatly improved compared to the technology that can be achieved by computers in the past. However, in the case of programmers and producers, the excessive and illegal dissemination of programs has caused the plagiarism of the technology developed by the programmers, which has also made the program producers lose their money, thus seriously infringing the developers and producers. s right. In view of this phenomenon, program developers and producers have constructed a set of authorization mechanisms. Authorization is a way to protect the intellectual property rights of the program. It can be directly sent to the authorization management server through the network by the user terminal of the application. The registration message transmitted by the authorization management server through the user terminal can be Whether the authentication client has the permission to use, if the client is confirmed to have the permission to use, it can be authorized to start and use the program. If the client does not have the permission, the program will not be used because it is not available. With authorization management, programmers and producers can avoid excessive and illegal dissemination of programs by the general public. For example, please refer to "Figure 1". The general program will be divided into different authorization quantity limits for users of different groups 200933380. For example, the program uses the target company, the school institution, etc., or the individual to distinguish the user side. The number of licenses, etc. The different groups in the meal are group A11, group and group. Each group has at least one client. In the previous authorization management method, the client (1) and m in the group A11 are required to transmit the registration/anti-registration request to the authorized management server through each user age. When the authorization management server first judges that the user terminals ιη and ιΐ2 符合 meet the usage rights, the authorization management server 100 transmits the authorization file to the users U1 and 112 in the group A110. Similarly, the authorization management service device will transmit the authorization to the group_house 121 and the group C_the client 131. After the user knows that the authorization file has been received, the registration status can be changed and the program can be started. However, in this conventional shop management mode, the ageing server 100 must simultaneously distribute authorization documents for different users from different groups, and when it is in the same group, it is required to connect to the authorized management. When the number of clients of the server 100 is too large, the authorization management system (10) may cause excessive network traffic, thereby affecting the processing performance of the granting program. In addition, the authorization management server 100 assigns 5 main book/anti-registration requests to each user terminal. [Because each user terminal is an independent source, it does not manage the number of user authorizations in the same group. Therefore, it is necessary to propose improved technical means to solve the above problems. SUMMARY OF THE INVENTION The present invention has been proposed in the prior art by a single authorization server. The program "causes the veneer (4) to be overburdened, and the authorization 6 200933380 is not easy to be used." The hierarchical authorization management system and method 'can be used to solve the problem to be solved in the prior art. The hierarchical authorization management system disclosed in the present invention includes: an authorization server 'to receive at least one authorization request, and to transmit a corresponding authorization file according to each authorization request, wherein each authorization file further includes an authorization quantity value; At least one management server, wherein each management server is further configured to: transmit an authorization request to the authorization server and activate the authorization management mode when receiving the authorization file transmitted by the authorization server; and receive at least one The registration end/re-registration request sent by the client and corresponding to each client, and the corresponding registration status is transmitted according to the authorized quantity value in the management server, and the registration quantity value in the management server is updated; and at least one user end, wherein Each of the UEs is further configured to execute an install/uninstall program, and transmit each registration/anti-registration request to each management server when executing each install/uninstall program, and the receiving management server transmits the request according to each registration/anti-registration request. Each registration status. The hierarchical authorization management method disclosed in the present invention includes: the management server transmits an authorization request to the authorization server; and the authorization server transmits the corresponding authorization file according to the authorization request, wherein the authorization file further includes the authorized quantity. Value; when the management server receives the authorization file, the authorization management mode is activated; when the client performs the installation/uninstallation process, the client transmits a registration/anti-registration request to the management server; when the management server receives the registration / When the registration request is reversed, the corresponding registration status is transmitted to the client according to the authorized quantity value in the management server; and the user terminal receives the registration status. Through the above technical means, the present invention can achieve the technical effect of improving the authorization management performance 7 200933380. [Embodiment] The embodiments of the present invention will be described in detail below with reference to the drawings and embodiments, thereby how the invention can be uniformly authorized to the management server by the authorization server, and how the management server is directed to the authorized number. Management is carried out to solve the problem that the authorization management device is overloaded by the single-authorization management ship, and the authorization quantity management is not easy, and the implementation process of how to achieve the authorization management performance is explained. For full understanding and implementation. First, please refer to "FIG. 2", a system block diagram of the hierarchical authorization management system of the present invention, which will explain the operation of each component block of the system of the present invention. The hierarchical authorization system of the present invention comprises an authorization server, at least one management server A211 and management server B221, and at least one client 212, 213, 222 and 223.

The authorization server 200 is configured to receive an authorization request from at least one of the management server A2U and the management server B221 and transmit a corresponding authorization file according to each authorization request from the management server A211 and the management server B221. The authorization file may include the authorization quantity value, and may also include the information required for any authorization such as the user name, the product serial number, the product serial number, and the version number, and the present invention is not limited herein. At least one management server A211 and management server B221, each management server 211 and management server B221 can be respectively set according to different groups A210 and group B220, and can also be used to transmit an authorization request to the authorization 8 200933380 server 200. In order to obtain an authorization file. For example, a company can set up a management server A211 dedicated to its own company. Through the management server A2u, it can transmit an authorization request to the authorization device 2GG, and the authorization server receives the authorization. After the authorization is requested in May, it will be based on Authorize the request to generate the corresponding authorization file,

* After the authorization file is transferred to the management ship A211 as a towel. After the management ship A2U receives the license, the button is received, and at this time, the user terminals 212 and 213 from the group A21 belonging to the management server A211 are executed to perform the installation/uninstallation process. The registered/anti-registration request transmitted. Similarly, the operation mode between the management server B221 and the authorization management server 2, the client terminals 222 and 223 is similar, and will not be described herein. When the management of the H A211 and the management pin (4) B221 receives the registration/anti-registration request, the current registration quantity value and the authorized quantity value in the authorization item will be compiled. When the client terminals 212, 213, 222, and 223 execute the installation program, a registration request is issued to the management server A211 and the management server B221. If the number of registered registers is not greater than the authorized number, the current number of registrations has not exceeded the authorization. The number of users of the program can be used, so the management server A21l and the management ship 1 B221 will pass the registration status to the client terminals 212, 213, 222 and 223 of the request for registration - when the user terminals 212, 213, 222 and When the 223 receives the registered registration status, the installation program can be continued until the installation operation is completed, and the local registry of the users 212, 213, 222, and 223 can also be updated. If the number of registered values is greater than the authorized number when executing the installer, it means that the number of users to be registered has exceeded the number of users allowed to use the program, then the management server A211 and the management server B22l will reject the note 9 200933380 and transmit Registered registration status, at this time the client terminals 212, 213, 222 and 223 will jump out of the Anshang program. In addition, if the client terminals 212'213' 222 and 223 execute the uninstallation procedure, an anti-registration request is issued. At this time, the management 'ship A211 and management II B221 will return the unregistered registration status message. However, since the registration status before the identification of the user terminals 212, 213, 222, and 223 is achieved by the registered system through the touch network card address, the network card of the user terminal cannot be arbitrarily disassembled. Similarly, the management server A211 and the management server are In the B221, the network card is also provided, so that the network card address can be used as the unique identification when authorized. Next, the operation of the present invention will be described with reference to an embodiment with "Fig. 2" and "Fig. 3". Assume that the existing two groups 'group A21〇 and group B22, respectively, each have their own management server, as shown in Figure 2, ❹ Group A210 is set to manage The server A2U, the group B220 is provided with a management server B221', and the management word server A211 is used for authorizing management of the clients 212 and 213 to be registered, and the management server B221 is used for the s main book. Users 222 and 223 perform authorization management. As shown in "Figure 3", first, the management server and the management server B221 can respectively transmit the authorization request to the authorization server 2 (step 3〇1) 'When the authorization server 200 receives the authorizations After the request, the corresponding authorization file is transmitted to the management server A2U and the management server B221 according to each authorization request (step 302). The authorization management file contains the authorized quantity values of each group 200933380 A210 and group B220. When the management server A2n and the management server B221 receive the authorization file generated by the authorization server 2, the authorization management mode is started (step 303). When the client terminals 212 and 213 in the group A210 execute the install/uninstall program, 'the registration/anti-registration request will be transmitted to the management server A211 (step 3〇4) 'samely' the client terminal 222 among the group B220. And when the installation/uninstallation program is executed 223, a registration/anti-registration request is transmitted to the management server B221. ❹ When the management server A211 and the management server B221 receive the registration/anti-registration request, they will perform authorization management according to the authorization file received from the authorization server 2〇〇, that is, the management server 211 and the management device. The server 221 will transmit the corresponding registration status to the clients 212, 2, 222, and 223 according to the authorization category and the authorized quantity value (step 305). Finally, the client terminals 212, 213, 222, and 223 receive the corresponding registration status (step 3〇6). It is necessary to say it in a special way. _Yes, it is determined after the registration/anti-injection request and the authorized quantity value. For example, when the client 2丨2 executes the installer and sends a registration request, the management server A calls the value of the credit still less than the authorized number, or the previous registration status of the client 212 is (10). , the management of the fresh A2U will return the registered registration status 'When the user terminal 212 receives the registered registration status', you can continue to perform the women's clothing & order until the installation is completed, and more _ terminal 2丨2 of the registry, as well as the notification manager 趟 update the authorized quantity value. If the user terminal 212 has exceeded the authorized quantity value when issuing the request, the management server will return the unregistered registration status, and the user terminal 212 will jump out when receiving the unregistered registration status 200933380. Installer. In addition, each of the clients 212, 213, 222, and 223 and each of the management server A211 and the management word processor B221 have a network card, and the network card address can be used for identification of an authorization request and a registration/anti-registration request. • Finally, please refer to the system diagram of the first embodiment of the present invention and the second diagram of the system block diagram of the present invention. The previous authorization management system is for users from different groups through a single authorization management server 1GG. Authorization, the same group ❹ When connecting to the authorization management server through the user terminal, the authorization management server 100 may cause excessive load due to too many users connected, and at the same time 'authorization management The server 100 has to manage the number of authorized users of the same group. It is impossible to determine the group to which the user belongs, which often causes difficulty in managing the number of authorizations. iTij The invention passes the authorization of the lion service H to the management server, and manages the feeding device for the authorized quantity. In addition to reducing the load of the authorization server 200, it can also be sure for the same group _ Lai Weiquan manages, so that it can improve the effectiveness of authorization management. , Miscellaneous invention _ The age of the dew is as above, but the rider does not use the alpha straight to determine the patent position of the invention. Any person having ordinary skill in the art will be able to make some changes in the form and details of the implementation without departing from the spirit and scope of the invention. The scope of patent protection of the present invention must still be determined by the appended claims. [Simple description of the diagram] Fig. 1 is a schematic diagram of the architecture of the authorization management system of the prior art. 12 200933380 Figure 2 is a system block diagram of the hierarchical authorization management system of the present invention. Figure 3 is a flow chart showing the method of the hierarchical authorization management method of the present invention. [Main component symbol description] 100 Authorization management server

110 Group A

111 Client 112 Client

120 Group B 121 Client

130 Group C 131 Client 132 Client 200 Authorized Server

210 Group A

211 Management Server A 212 Client 213 Client

220 Group B

221 Management Server B 222 Client 223 Client 13 200933380 Step 301 Manages the Feeder Transfer Authorization Request to the Authorized Ship Step View _ The server transmits the corresponding authorization file to the management server according to the authorization request. Step 303 Start Authorization Management Mode. Step 304: When the client executes the install/uninstall procedure, the registration/anti-registration request is sent to the management server. Step 305: When the management server receives the registration/anti-registration request, the corresponding registration status is transmitted according to the license quantity value to Client Step 306 User Receives Registration Status 14

Claims (1)

200933380 X. Patent application scope: 1. A hierarchical authorization management system, the system comprises: an authorization server for receiving at least one authorization request, and transmitting corresponding authorization files according to each of the authorization requests, wherein each authorization The file further includes: an authorization quantity value; at least one management server, wherein each management server is further configured to: transmit the authorization request to the authorization server, and when receiving the authorization file transmitted by the authorization server And initiating an authorization management mode; and receiving a registration/anti-registration request issued by at least one client and corresponding to each client, and transmitting a corresponding registration status according to the authorized quantity value in the management server, and updating the management One of the number of registrations in the server; and at least one client, wherein each of the clients is further configured to execute an install/uninstall program, and each of the registration/re-registration is transmitted to each of the install/uninstall programs Each of the management servers, and receiving each of the notes transmitted by the management server according to each of the registration/anti-registration requests Book status. 2. The hierarchical authorization management system according to claim 1, wherein each of the user terminals and each of the management servers uses a network card address as a basis for unique identification of each terminal. 3. The hierarchical authorization management system according to claim 1, wherein: the registration request is transmitted when the client executes the installation program, wherein: if the registration quantity value is not greater than the authorization quantity value, or the user terminal 15 The registration status of 200933380 is already registered, the status of the registered book is registered, and the authorized number of the temple is _, the registration status of the management servo οσ transmission is unregistered; and the anti-registration request is transmitted when the client executes the uninstall program. Then the registration status of the management server transmission is unregistered. 4. The hierarchical authorization management system described in claim 3, wherein when the client executes the installation program: if the user terminal is ready to be installed, each client completes the installation procedure; And if the registration status received by the user terminal is not registered, each user terminal jumps out of the installation program; and when the user end performs the uninstallation process: if the registration status received by the user terminal is not registered, each user terminal completes The uninstaller. Note that the management server transmits the message. 5. The hierarchical authorization management system described in claim 4, wherein each client updates the registry of each client and completes the notification when the installation/uninstallation procedure is completed/bounced. The management server updates the registration quantity value. 6. A hierarchical authorization management method, the method comprising the following steps: a management server transmits an authorization request to an authorized feeding device, and the fifth authorization server transmits a corresponding authorization file according to the authorization request. The authorization file is further encapsulated by the authorized quantity value; when the management server receives the authorization file, the activation-authorization pipe 16 200933380 is in the mode; when a client performs an installation/uninstallation process, the client transmits a registration/anti-registration request to the management server; when the management server receives the registration/anti-registration request, transmitting a corresponding registration status to the user terminal according to the authorized quantity value in the management server ; and Λ The client receives the registration status. 7. The hierarchical authorization management method according to claim 6, wherein the user terminal and each of the management servers use the network card address as the sole identification basis of each terminal. 8. The hierarchical hard management method described in Item 6 of the claim, wherein the method further comprises the following steps: when the client executes the installer, a registration request is transmitted, wherein: if the registered quantity value is not greater than the young If the weight quantity value, or the registration status of the user end is already registered, the registration status of the management feeder is registered; and if the registration quantity value is greater than the authorized quantity value, the management server transmits the ti book Status silk registration; and when the Ueda user performs the uninstallation procedure, the old status of the management server transmission is unregistered. ** 9. As described in Item 8 of the patent application system, the layer authorization management method, wherein the method further comprises the following steps: Although the client executes the installer: 200933380 The status of the book is one coffee::==book_ ,, _ When the client executes the uninstaller: When the registration status received by each right client is unregistered, the client completes the uninstaller. e 10. If the number of the hierarchical authorization management methods described in item 9 of the patent track is more than the number 3, the method of package 3 is completed/bounced out of the installation/uninstallation procedure at each client, And notifying the management feeding device to update the raw value.