KR101745403B1 - User authority management system and meyhod thereof - Google Patents

Abstract

A user authority management system and a method for providing the same are disclosed. The user rights management system according to an embodiment of the present invention includes rights information corresponding to user information including information on each user account and a plurality of license rights, the rights information corresponding to each of the license rights Information about the permitted license types, and information on the number of allowed user accounts allowed for each license type; an execution module for collecting execution information of an access user account connected to the license target system; A license module for analyzing information and classifying a corresponding license type according to each of the connection user accounts; and an application module for receiving application authority information corresponding to the application license authority held by the license use entity, The type classification information for the license type is managed by the manager And a control module for transmitting to the end.

Description

Technical Field [0001] The present invention relates to a user authority management system and a method for providing the same,

The present invention relates to a user rights management system and a method for providing the same. More particularly, the present invention relates to a user rights management system and a method for providing the same, By distinguishing the type (role) of the user (account) based on the usage information (usage record), the user account having unnecessary privilege can be easily managed, so that the usage rights are not actually used but unnecessary charges are made And to prevent the cost from being wasted.

In an organization such as a company, a license target system for managing an organization such as an intranet is widely used. Through these licensed systems, management of all aspects such as logistics, materials, finance, and production is carried out through Enterprise Resource Planning (ERP) system. These ERP systems are widely used in many companies and organizations. Many companies and organizations purchase and use programs to implement such ERP systems.

Among these ERP programs, there are cases where users are directly charged in the ERP program and generate a profit by conducting a charge based on the user account performing the actual work.

In other words, there may be users who directly modify / modify / add data through the ERP program, except for members who do not directly run the ERP program. Through the ERP program, various information There may be a user who simply browses some of the information. The differences in these business privileges may vary depending on the licensing policy when purchasing the first ERP program, and the user accounts allowed for each task authority may also vary accordingly.

Depending on the number of user accounts for each of these licenses, there may be a large difference in the cost of billing. The number of user accounts participating in actual work during the actual work over time compared to the license policy anticipated when purchasing the first ERP program There is a risk that it will change or not be properly managed.

In such a case, a company or an organization that purchases and uses an ERP program may incur an unexpected burden of exceeding the license cost, which may cause unnecessary expense.

Korean Registered Patent (Registration No. 10-1054319, "Rights Information Management Device, Information Processing System and Computer Readable Storage Medium")

Accordingly, the technical problem to be solved by the present invention is to classify the license types for each user (account) by using the access information of the user (account) and the execution information according to the actual business execution, To provide the technical idea that the user authority management can be performed in accordance with the charging policy of the ERP program and the like.

According to an aspect of the present invention, there is provided a user rights management system including user information including information on each user account and rights information corresponding to a plurality of license rights, Includes information on a license type allowed by each of the license rights, and information on the number of allowable user accounts allowed for each license type. The DB includes execution information of an access user account connected to the license target system A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts, and a license module for analyzing the application right information corresponding to the application license authority held by the license use entity, The license module classified by the license module A type classification information for may include a control module for transmitting to the administrator terminal.

The user rights management system may further include a connection module for collecting user connection information and storing the collected connection information in the DB, wherein the license module further analyzes the connection information, And the license type to be applied to the license type.

The control module may perform connection control of a user account based on the connection information.

In addition, the control module may transmit a recommended license type for each user account to the administrator terminal based on the application right information and the type classification information.

In addition, the control module may transmit the recommendation authority information among the authority information to the administrator terminal based on the type classification information.

The control module may perform execution control on each user account based on the recommended license type.

According to an aspect of the present invention, there is provided a system for managing a user rights according to an embodiment of the present invention. The system includes a management server for managing user information including information on each user account and a plurality of license entitlements corresponding to application license entitlements The license information includes information on a license type including a first type and a second type in which at least one task is limited as compared to the first type, An execution module for collecting execution information of an access user account connected to the license target system, and an analyzing module for analyzing the execution information and calculating a corresponding A license module for classifying the license type, and a control module, Wherein the module is configured to classify at least one of the connection user accounts if the number of the connection user accounts classified as the first type among the license types exceeds the number of the allowed user accounts for the first type as a result of the classification of the license module The recommended type of license is recommended to change from the first type to the second type to the administrator terminal.

The control module may further include a connection user account to which the license type is to be changed based on the frequency of the tasks that are permitted to the first type but not to the second type among the connection user accounts classified into the first type And then determining whether or not the result of the determination is positive.

According to an aspect of the present invention, there is provided a method for providing a user authority management system, the method comprising: receiving a user authority information including information on each user account and a plurality of license rights The rights information includes storing information on a license type allowed by each of the license rights and information on the number of allowed user accounts allowed for each license type; Collecting execution information of a connected user account connected to the license target system, analyzing the execution information by the user authority management system and classifying the corresponding license type for each of the access user accounts, Among the rights information, And transmitting the type classification information for the license type classified by the license module to the administrator terminal.

The user authority management system may further include a step of the user authority management system collecting the user's access information and storing the collected access information, The step of classifying the license type to be applied to the user account by analyzing the information and the execution information may further include classifying the license type to be applied to the user account by analyzing the access information by the user authority management system .

In addition, the method of providing a user rights management system may further include the step of the user rights management system performing access control of a user account based on the access information.

The user rights management system providing method may include transmitting the recommended license type for each user account to the administrator terminal based on the application right information and the type classification information .

The method of providing a user authority management system may further include transmitting the recommendation authority information among the at least one authority information to the administrator terminal based on the type classification information.

In addition, the method of providing a user rights management system may further include the step of the user rights management system performing execution control on a user account based on the recommendation license type.

According to another aspect of the present invention, there is provided a method for providing a user rights management system, the method comprising: providing a user authority management system including user information including information on each user account and a plurality of license entities among a plurality of license entities, Wherein the right information corresponds to a license type that includes a first type and a second type in which at least one task is restricted compared to the first type, the right information corresponding to the license type Including information on the number of allowed user accounts allowed per license type, collecting execution information of an access user account connected to the license target system by the user rights management system, The management system analyzes the execution information to determine whether each connection If the number of access user accounts classified as the first type among the license types exceeds the number of allowed user accounts for the first type, the step of classifying the corresponding license type for each user account, And transmitting a recommendation license type recommended by the rights management system to at least one of the connection user accounts from the first type to the second type to the administrator terminal.

The step of transmitting the recommended license type recommended by the user rights management system to change from the first type to the second type for at least one of the connection user accounts to the administrator terminal may include: Determining a connection user account to which the license type is to be changed based on the frequency of performing the tasks of the first type and the types of tasks that are permitted to the first type but not the second type among the connected user accounts classified as the first type .

In addition, a computer program recorded in a recording medium installed in a data processing apparatus to perform the method for providing the user rights management system may be provided to accomplish the technical idea of the present invention.

According to the technical idea of the present invention, by classifying license types for respective users (accounts) by using access information of a user (account) and execution information according to actual business execution, and managing possible business privileges for each license type User rights management can be performed so as to comply with a charging policy corresponding to a contracted license right of the software such as an ERP program, thereby reducing the cost consumed or unnecessary expenses.

BRIEF DESCRIPTION OF THE DRAWINGS A brief description of each drawing is provided to more fully understand the drawings recited in the description of the invention.
FIG. 1 schematically illustrates components for implementing a user rights management system according to an embodiment of the present invention.
FIG. 2 shows a schematic configuration of a user rights management system according to an embodiment of the present invention.
3 to 5 are diagrams for explaining an operation process of the user authority management system according to the embodiment of the present invention.
FIG. 6 is a flowchart illustrating a method of providing a user rights management system according to an embodiment of the present invention.

In order to fully understand the present invention, operational advantages of the present invention, and objects achieved by the practice of the present invention, reference should be made to the accompanying drawings and the accompanying drawings which illustrate preferred embodiments of the present invention.

Further, in the present specification, when any one element 'transmits' data to another element, the element may transmit the data directly to the other element, or may transmit the data through at least one other element Data may be transmitted to the other component.

Conversely, when one element 'directly transmits' data to another element, it means that the data is transmitted to the other element without passing through another element in the element.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, the present invention will be described in detail with reference to the preferred embodiments of the present invention with reference to the accompanying drawings. Like reference symbols in the drawings denote like elements.

FIG. 1 schematically illustrates components for implementing a user rights management system according to an embodiment of the present invention.

The user rights management system 100 may include hardware resources and / or software required to implement the technical idea of the present invention. The user rights management system 100 necessarily means one physical component or one device It is not. That is, the user rights management system 100 may mean a logical combination of hardware and / or software provided to implement the technical idea of the present invention. If necessary, May be implemented as a set of logical structures for implementing the technical idea of the present invention.

According to an embodiment of the present invention, the user rights management system 100 may be implemented by a predetermined server. When the user rights management system 100 is implemented as a server, the user rights management system 100 is connected to a predetermined license target system 200, a user terminal 300 and / or an administrator terminal 400 via a network The technical idea of the present invention may be realized by transmitting and receiving predetermined data while performing communication.

The license target system 200 may refer to an information system (for example, an intranet or the like) that integrates tasks within a predetermined organization. The license target system 200 may include a license It can mean the target system. Each user can access the license target system 200 through the user terminal 300 to perform a predetermined task.

A predetermined management program (for example, an enterprise resource planning (ERP) program) may be installed in the license target system 200, and at least one user may access the license target system 200, And can perform predetermined tasks using the management program.

According to another embodiment, the configuration of a part of the user rights management system 100 is included in a predetermined server, and the rest of the configuration is included in the license target system 200, the user terminal 300, and / (400). Then, the server, the license target system 200, the user terminal 300, and / or the administrator terminal 400 may be organically combined to implement the technical idea of the present invention.

Hereinafter, the user rights management system 100 will be described in the form of a server for convenience of description. However, the scope of the present invention is not limited thereto, (100) may be distributed to the server, the license target system (200), the user terminal (300), and / or the administrator terminal (400).

The user rights management system 100 may be installed in the license target system 200, the user terminal 300, and / or the administrator terminal 400 to perform operations for implementing the technical idea of the present invention can do. For example, the user rights management system 100 may be implemented in the form of an application system and installed in the license target system 200, the user terminal 300, and / or the administrator terminal 400. The application system may include software (i.e., application) installed in the license target system 200, the user terminal 300 and / or the administrator terminal 400 to implement the technical idea of the present invention and the license target system 200 ), The user terminal 300 and / or the administrator terminal 400 to implement the technical idea of the present invention.

In addition, the user terminal 200 may include any type of data processing apparatus that can be connected to a network such as a computer to implement the technical idea of the present invention, and may be implemented as a smart phone, a tablet PC, Or may be implemented as a mobile terminal.

Hereinafter, components and operations of the user rights management system 100 will be described with reference to FIG.

FIG. 2 shows a schematic configuration of a user rights management system according to an embodiment of the present invention.

Referring to FIG. 2, a user rights management system 100 according to an embodiment of the present invention includes a DB 110, a connection module 120, an execution module 130, a license module 140, and / 150).

Herein, a module may mean a functional and structural combination of hardware for carrying out the technical idea of the present invention and software for driving the hardware. For example, the module may mean a logical unit of a predetermined code and a hardware resource for executing the predetermined code, and it does not necessarily mean a physically connected code or a kind of hardware. Can be easily deduced to the average expert in the technical field of the present invention.

The DB 110 may store user information including information on each user account and rights information corresponding to a plurality of license rights.

The user information may be information about a user account that can perform predetermined tasks such as editing (modifying, changing, adding, deleting, etc.) and / or browsing various data by accessing the license target system 200, and / Or information (e.g., personal information, etc.) about the organization members in the predetermined organization using the license target system 200. [

In addition, the rights information may include information on a license type allowed by each of the license rights and information on the number of allowable user accounts allowed for each license type. Hereinafter, among the plurality of license rights, the license rights applied to the subject of use of the license (for example, the subject purchasing the software) are referred to as application license rights, and the rights information corresponding to the applicable license rights is referred to as application rights information .

According to an example, the rights information may be set at a time of a license contract of a predetermined software such as an ERP program, and may be a license type classified by task authority performed by each user (for example, (License type based on each authority, such as permission to perform all tasks such as modification, change, and addition of data in the license use entity, permission for only simple data reading operation), and information And information on the number of accounts (i.e., the maximum allowable number of user accounts that can perform tasks according to business privileges corresponding to a particular license type).

The license type may be information on whether each user account is authorized to perform a task by accessing the license target system 200 for each type . For example, the first user having the first license type authority among the users included in the user information accesses the license target system 200 through the user terminal 300 and edits (for example, input And the second user having the second license type authority may have the authority to perform a simple browsing operation in the license target system 200. In this case,

The number of user accounts that are allowed to access the license target system 200 with the first license type authority may be limited to a predetermined number in advance, and the number of such allowable user accounts may be limited according to the respective license rights Can be set differently. Such a plurality of license rights may be determined in accordance with a predetermined standard predetermined by the seller of the software, or may be determined by agreement between the seller and the purchaser.

Also, depending on the implementation, it may be possible to change the license right to be applied to the user as needed on the side of using the software (i.e., the user of the license). According to an example, in this case, the license authority may be set through the administrator terminal 400. [ For example, the administrator can change the license rights to be applied based on the respective user information stored in the DB 110 via the administrator terminal 400. The administrator can change the license information, that is, the license information and the license type The number of allowed user accounts may change.

In order to manage the license right itself, the user rights management system 100 according to the technical idea of the present invention grasps a task pattern and the like actually performed by the user when the user accesses the license target system 200, If the pattern does not conform to the license right set at the initial contract, the administrator terminal 400 can recommend a more suitable license right.

Or, by recommending the recommended license type to the administrator terminal 400 to adjust the user account to be matched to each license type so that the actually performed business pattern matches the currently applied license right, the more efficient license management may be performed have.

For example, the user rights management system 100 can identify a task (for example, edit or browse) that is mainly performed by a specific user accessing the license target system 200 and recommend (or change) the corresponding license type, can do. According to an exemplary embodiment, the user authority management system 100 may allow a user who does not access the license target system 200 for a predetermined period or more, or a user who repeatedly performs a simple browsing task, You can recommend (or change) the type.

In addition, according to an embodiment, the user rights management system 100 grasps the actual task execution pattern of each user account (i.e., collects execution information), and then determines whether the current license right, that is, the applicable license applied to the license- The administrator terminal 400 transmits information on license types (i.e., type classification information - described later) according to the application authority information on the authority and the operation pattern actually performed by the connection user accounts connected to the license target system, And it is also possible to classify various types of recommended license types suitable for each user account according to the execution information and transmit the same to the administrator terminal 400 and recommend it to the administrator or the like so that more efficient license management can be performed have.

On the other hand, with regard to license management, the authority to access the license target system 200 and to modify / change / add data may be relatively high. Such a high-level user A user account set as a rating), the billing for the program installed in the license target system 200 may be changed. For example, the higher the number of high-grade user accounts, the greater the cost of billing.

Therefore, if there is a user account with a high level of authority despite the fact that it is not used for actual work, there is a risk that the software sales side may audit the software seller unnecessarily, It may be very important to manage the license type of these users (accounts), that is, the license type according to the usage history of each user account.

In other words, according to the technical idea of the present invention, the user rights management system 100 is configured to determine whether the application rights information and the actual business performance patterns of the respective users (user accounts) And execution information), it is possible to check whether or not the license right according to each business right is implemented as the original contract, and to correct it. According to the implementation example, the license fee You can also have a beneficial effect in that you can set new licensing rights to save money.

Meanwhile, the connection module 120 collects connection information of a user (user account), that is, whether the user account is connected to the license target system 200, and transmits the collected connection information to the DB 110 ). ≪ / RTI >

The execution module 130 may collect information related to a task executed by a user connected to the license target system 200, that is, execution information, that is, execution information. According to an embodiment, the execution module 130 may store the collected execution information in the DB 110. [ Such execution information may be stored for each user account.

The connection information and / or the execution information may be information collected over a predetermined period. For example, the connection information and / or the execution information may refer to information on tasks performed by accessing and / or connecting to the license target system 200 for a predetermined period of one month, three months, or the like. The period of collecting the connection information and / or the execution information may be variously determined as needed.

The license module 140 analyzes the authorization information, the access information, and the execution information, and classifies the license type for each user account. In this case, the license module 140 classifies each license type according to each user account. The license module 140 classifies each of the access user accounts into license types (i.e., license information) according to a task pattern (i.e., execution information) It can mean simple classification.

The license type may mean, for example, authority per task that a user can perform. That is, license types can be classified according to the number of tasks that can be performed. For example, the name of each license type can be classified according to need, for example, a first type in which data editing (for example, data input / correction / deletion) is possible, a second type in which data can be newly input, A third type in which only the data can be browsed, and / or a fourth type in which connection to the license target system 200 is restricted, and the like.

Also, even if the license type is the same as the first type, the range in which data can be edited may vary depending on the user account. For example, the scope of data editing may be limited to the personnel field or the financial field, depending on the type of work that the user or the user corresponding to the user account mainly performs.

On the other hand, in the case of the fourth type, the license module 140 can be classified based on the connection information collected and / or stored by the connection module 120. That is, the license type in the case where it is necessary to limit the connection itself to a specific user account can be classified based on the connection information collected by the connection module 120 by the license module 140. According to an embodiment, a user account corresponding to a user who does not need to use the software may be classified into the fourth type according to each user's department or business field even if there is no access information.

In the case of the first to third types, the license module 140 can be classified based on the execution information collected by the execution module 130. For example, if a particular user account is primarily responsible for editing data in the field of human resources after connection, the license module 140 may classify the user account into a first type of personnel field.

If the license module for each user account is classified by the license module 140 as described above, the control module 150 determines whether the license information corresponding to the applicable license right currently being applied to the license- The type classification information for the authority information and the classified license type may be transmitted (reported) to a predetermined manager, that is, the administrator terminal 400, thereby facilitating license management by the administrator.

Here, the type classification information for the classified line-life type may include at least one of a license type per access user account and / or a license type per access user account of a connection user account that accesses the license target system 200 for a predetermined period, The number of connected user accounts classified by the number of connected user accounts. For example, the classification result information indicating that the first user account is classified into the first type, the second user is classified into the third type, the number of the connection user accounts classified into the first type is 10, Information on the number of connection user accounts for each license type such as 50 number of connection user accounts can be included in the type classification information.

When the control module 150 transmits the application right information and the type classification information to the administrator terminal 400, the administrator can confirm that the task performed by each user account is the application right information That is, the application license authority). If the number of user accounts performing a specific license type of business (for example, the first type) is larger than the rights information at the time of contracting the software, the administrator may restrict the business rights of some excess user accounts, By performing license management such as renewing the contract (ie, replacing the applicable license authority with another kind), it will be possible for the licensee of the software vendor to pay a large license fee .

According to another embodiment of the present invention, the control module 150 may not simply report the license type for each user account currently classified by the license module 140, And recommends a recommendation license type suitable for each user account to the administrator terminal 400 using the information and / or the connection information.

For example, there is a user account having a license type classified as a first type capable of editing data (data modification, modification, deletion, addition, etc.) The control module 150 determines that the license type of the corresponding user account is changed from the first type to the third type if the reading task is not performed 400) can be recommended. That is, in this case, the recommended license type for the user account may be the third type.

These recommended license types are not only determined according to the currently classified license types but can be utilized to control the number of allowed user accounts for each license type according to the currently applied application license right.

For example, if the rights information (application right information) of the applicable license right is 10 allowable user accounts in the first type and 50 allowable user accounts in the second type, and the license classified by the license module 140 , It is assumed that the number of connection user accounts classified into the first type is 12 and the number of connection user accounts classified into the second type is 40.

Generally, the stronger the business privileges that are allowed (ie, the greater the number of tasks that can be performed), the higher the cost of billing the account.

That is, in the above-mentioned example, the first type that can edit data is classified into a larger number of connected user accounts than the number of allowed user accounts, and there is a risk that the cost for the number of accounts exceeded at the time of audit for later software is large .

In this case, since the second type has a sufficient number of allowable user accounts, it is possible to prevent the risk if the two types of accounts exceeding the connection user account classified into the first type are changed to the second type.

According to an embodiment of the present invention, in this case, the execution information for the connection user accounts classified into the first type is analyzed to select two connection user accounts in the order of the lowest frequency of actual data editing, Effective license management can be achieved by recommending changing the two selected connection user accounts to the second type (i.e., the recommended license type).

In other words, according to the technical idea of the present invention, when the number of connection user accounts classified as a specific license type, particularly, a license type having a higher business authorization level exceeds the number of allowed user accounts, the corresponding type (for example, (E.g., the second type) by changing at least one of the access user accounts classified as the access user account into the different type of access user account (for example, the second type) so that the effective license management can be effected without changing the license right itself have.

In some implementations, the control module 150 may control the license module 140 to change the license type for a user account that needs to be changed in the license type. The changed license type may be updated in the DB 110. [ For this, the license module 140 may classify the license type for each user account, and may also be capable of changing the license type applied to each user account.

When the license type management can be performed by the user rights management system 100, the administrator can purchase the first software (e.g., an ERP program) through the administrator terminal 400. [ You can manage the number of user accounts allowed by the corresponding license types so that they do not exceed the allowed range according to the established contractual content (ie, according to the license rights). For example, if the number of user accounts allowed for the first type of data to be edited is 10, the number of user accounts performing the data editing job is 11 or more In the event of an audit by a later salesperson, the amount may be overpaid depending on the number of user accounts exceeded. Accordingly, the administrator or the user authority management system 100 can manage the license type so that the total number of user accounts corresponding to the license type of the first type is 10 or less (or ten).

Also, as the case may be, at least eleven user accounts needing to perform a task (e.g., a data editing task) corresponding to the first type in the current situation as compared to the initial contract may be required. That is, the number of user accounts allowed for the first type is not unnecessarily exceeded, and a situation that is necessarily necessary for business progress may occur.

In this case, the control module 150 transmits a recommendation license right more suitable to the current execution information among the plurality of license rights stored in the DB 110, to the administrator terminal 400). ≪ / RTI >

This can be very useful when the initial contract is beyond the scope of the licensing rights and the cost of additional licenses can be reduced rather than the cost of additional charges at a later audit.

The control module 150 may provide various information collected and classified by the access module 120, the execution module 130, and / or the license module 140, (E.g., access information, execution information, and / or type classification information) of the plurality of license rights stored in the DB 110, And transmit the determined authority to the administrator terminal 400.

Meanwhile, according to another embodiment of the present invention, the control module 150 determines whether or not each of the user accounts (or the user accounts) based on the license type classified by the license module 140 or the license type managed through the administrator terminal 400 And / or execution control for the mobile terminal.

For example, the connection control may be such that, when a specific user account has no access information for a predetermined period or more, that is, for a user account having no record connected to the license target system 200 for a predetermined period or longer, This may mean allowing access to this restricted user account. For example, when the user account classified as the fourth type by the license module 140 tries to access the license target system 200, the control module 150 may restrict access to the corresponding user account have.

In addition, the execution control may mean that the connected user accounts divide the tasks that can be performed by limiting the tasks themselves that the user can perform. For example, when accessing a specific user account, it is possible to edit the data according to the license type corresponding to the specific user account, or to control the specific user account so that it can not perform other tasks other than simple browsing can do. For example, when a user account classified as the third type is accessed, the corresponding user account can restrict the data editing service to not perform the data editing service itself.

In the case where the control module 150 performs the connection control and / or the execution control as described above, it is possible to prevent the risk that the additional license fee due to the subsequent audit will be charged Can be prevented in advance.

3 to 5 are diagrams for explaining an operation process of the user authority management system according to the embodiment of the present invention.

3, the user authority management system 100 according to the embodiment of the present invention collects and stores access information for a user connected to the license target system 200 through the user terminal 300 , And may perform connection control for the user by analyzing the connection information according to an implementation example.

4, the user right management system 100 can collect and analyze execution information on a task actually performed by a user connected to the license target system 200, Execution information can be stored.

5, the user rights management system 100 analyzes the access information and / or execution information collected in the above-described FIG. 3 to FIG. 4, and classifies the license type for the user account based on the analysis result And transmits the classified license type to the administrator terminal 400 or manages the license authority by recommending a recommended license type more suitable for the current task execution pattern.

As described above, the user authority management system 100 classifies and manages the rights (license type) for each user (account) according to the actual usage record (i.e., access information and / or execution information) And can effectively manage licensing rights according to the charging policy according to the contract contents. Accordingly, it is possible to prevent a risk that a surplus cost may be charged in a future audit process in advance, and it is possible to advantageously reduce a license cost by selecting a more appropriate license right according to a current business execution pattern .

FIG. 6 is a flowchart illustrating a method of providing a user rights management system according to an embodiment of the present invention.

Referring to FIG. 6, the user rights management system 100 according to the embodiment of the present invention may store user information and rights information (s100).

In addition, the user authority management system 100 accesses the license target system 200 through the user terminal 300. The user authority management system 100 determines whether access to the user (account) The execution information may be collected and analyzed (s110).

Then, the user rights management system 100 can classify the license type of the user based on the analysis result of the execution information (s120). In addition, the user rights management system 100 may perform access control for the user using the collected user's access information as described above.

The user right management system 100 can manage the right to perform a task that the user can actually perform, that is, the license type (s130), by classifying the license type of the user.

The term "managing the license type" may mean recommending a license type to be applied to each user account or recommending the license right itself according to the current license right as described above.

The final change in accordance with the recommended license type or recommended licensing rights may be performed by the administrator via the administrator system 400 as described above, and may be implemented in accordance with an implementation, including at least some changes (e.g., Change) may be performed automatically by the user authority management system 100.

The method of providing a user rights management system according to an embodiment of the present invention can be implemented as computer-readable codes on a computer-readable recording medium. A computer-readable recording medium includes all kinds of recording apparatuses in which data that can be read by a computer system is stored. Examples of the computer-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, hard disk, floppy disk, optical data storage, and the like. The computer readable recording medium may also be distributed over a networked computer system so that computer readable code can be stored and executed in a distributed manner. And functional programs, codes, and code segments for implementing the present invention can be easily inferred by programmers skilled in the art to which the present invention pertains.

While the present invention has been particularly shown and described with reference to exemplary embodiments thereof, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

Claims (17)

User information including information on each user account and rights information corresponding to a plurality of license rights, wherein the rights information includes information on a license type allowed by each of the license rights and allowed for each license type A database containing information on the number of allowed user accounts;
An execution module for collecting execution information of a connected user account connected to the license target system;
A connection module for collecting user connection information and storing the collected connection information in the DB;
A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts, for classifying a license type to be applied to the user account by analyzing the connection information; And
And transmits the application authority information corresponding to the application license authority held by the license use entity and the type classification information on the license type classified by the license module among the rights information to the administrator terminal, And a control module for performing connection control of the account.
delete delete User information including information on each user account and rights information corresponding to a plurality of license rights, wherein the rights information includes information on a license type allowed by each of the license rights and allowed for each license type A database containing information on the number of allowed user accounts;
An execution module for collecting execution information of a connected user account connected to the license target system;
A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts; And
And a control module for transmitting, to the administrator terminal, application authority information corresponding to the applicable license authority held by the license use entity and type classification information on the license type classified by the license module among the authority information,
The control module includes:
And further transmits a recommendation license type for each user account to the administrator terminal based on the application right information and the type classification information.
User information including information on each user account and rights information corresponding to a plurality of license rights, wherein the rights information includes information on a license type allowed by each of the license rights and allowed for each license type A database containing information on the number of allowed user accounts;
An execution module for collecting execution information of a connected user account connected to the license target system;
A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts; And
And a control module for transmitting, to the administrator terminal, application authority information corresponding to the applicable license authority held by the license use entity and type classification information on the license type classified by the license module among the authority information,
The control module includes:
And transmits the recommendation authority information among the authority information to the administrator terminal based on the type classification information.
User information including information on each user account and rights information corresponding to a plurality of license rights, wherein the rights information includes information on a license type allowed by each of the license rights and allowed for each license type A database containing information on the number of allowed user accounts;
An execution module for collecting execution information of a connected user account connected to the license target system;
A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts; And
And a control module for transmitting, to the administrator terminal, application authority information corresponding to the applicable license authority held by the license use entity and type classification information on the license type classified by the license module among the authority information,
The control module includes:
Further transmitting a recommendation license type for each user account to the administrator terminal based on the application right information and the type classification information,
And performs execution control on each user account based on the recommended license type.
A user information including information on each user account and a license information corresponding to a license license possessed by the license use subject among a plurality of license rights, the license information allowing each of the license rights, And a second type in which at least one task is limited as compared to the first type, and information on the number of permitted user accounts allowed per license type;
An execution module for collecting execution information of a connected user account connected to the license target system;
A license module for analyzing the execution information and classifying a corresponding license type for each of the connection user accounts; And
A control module,
The control module includes:
Wherein if the number of connected user accounts classified as the first type among the license types exceeds the number of allowed user accounts for the first type as a result of the classification of the license module, To the manager terminal, recommending a recommended license type to change from the first type to the second type,
And determines a connection user account whose license type is to be changed based on the frequency of performing the tasks among the connected user accounts classified as the first type, which are permitted for the first type but not for the second type. Rights management system.
delete The user rights management system includes user information including information on each user account and rights information corresponding to a plurality of license rights, the rights information being information about a license type allowed by each of the license rights, Storing information on the number of allowed user accounts allowed for each license type;
Collecting execution information of an access user account connected to the license target system by the user rights management system;
The user rights management system collecting the user's access information and storing the collected access information;
Analyzing the execution information by the user authority management system and classifying the corresponding license type for each of the access user accounts;
The user rights management system analyzing the access information and classifying a license type to be applied to the user account; And
Wherein the user authority management system transmits, to the administrator terminal, the application authority information corresponding to the applicable license authority held by the license use entity and the type classification information on the classified license type among the authority information,
The method of claim 1,
Wherein the user rights management system performs access control of a user account based on the access information.
delete delete The user rights management system includes user information including information on each user account and rights information corresponding to a plurality of license rights, the rights information being information about a license type allowed by each of the license rights, Storing information on the number of allowed user accounts allowed for each license type;
Collecting execution information of an access user account connected to the license target system by the user rights management system;
Analyzing the execution information by the user authority management system and classifying the corresponding license type for each of the access user accounts;
Transmitting, by the user authority management system, application authority information corresponding to application license authority held by the license use entity and type classification information on the classified license type among the authority information to the administrator terminal; And
And the user rights management system transmitting the recommended license type for each user account to the administrator terminal based on the application right information and the type classification information.
The user rights management system includes user information including information on each user account and rights information corresponding to a plurality of license rights, the rights information being information about a license type allowed by each of the license rights, Storing information on the number of allowed user accounts allowed for each license type;
Collecting execution information of an access user account connected to the license target system by the user rights management system;
Analyzing the execution information by the user authority management system and classifying the corresponding license type for each of the access user accounts;
Transmitting, by the user authority management system, application authority information corresponding to application license authority held by the license use entity and type classification information on the classified license type among the authority information to the administrator terminal; And
And the user rights management system transmitting the recommendation right information among the right information to the administrator terminal based on the type classification information.
The user rights management system includes user information including information on each user account and rights information corresponding to a plurality of license rights, the rights information being information about a license type allowed by each of the license rights, Storing information on the number of allowed user accounts allowed for each license type;
Collecting execution information of an access user account connected to the license target system by the user rights management system;
Analyzing the execution information by the user authority management system and classifying the corresponding license type for each of the access user accounts;
Transmitting, by the user authority management system, application authority information corresponding to application license authority held by the license use entity and type classification information on the classified license type among the authority information to the administrator terminal;
The user rights management system transmitting a recommendation license type for each user account to the administrator terminal based on the application right information and the type classification information; And
Wherein the user rights management system further comprises performing execution control on a user account based on the recommendation license type.
Wherein the user rights management system includes user information including information on each user account and rights information corresponding to application license rights held by the license use subject among a plurality of license rights, And information on a license type including a first type and a second type in which at least one task is limited as compared to the first type and information on the number of allowable user accounts allowed per license type step;
Collecting execution information of an access user account connected to the license target system by the user rights management system;
The user rights management system analyzing the execution information and classifying a corresponding license type for each of the access user accounts; And
If the number of access user accounts classified as the first type among the license types exceeds the number of allowed user accounts for the first type as a result of the classification, the user rights management system notifies the at least one of the access user accounts And transferring a recommendation license type recommended to change from the first type to the second type to the administrator terminal,
Wherein the step of transmitting a recommendation license type recommended by the user right management system to change from the first type to the second type for at least one of the connection user accounts to the administrator terminal,
The user rights management system determines an access user account whose license type is to be changed based on the frequency of performing tasks that are allowed to the first type but not to the second type among the access user accounts classified into the first type The method comprising the steps of:
delete A computer program recorded on a computer-readable recording medium for performing the method according to any one of claims 9 to 12, installed in a data processing apparatus.

Images