JP6029451B2 - Resource use control device, resource use control method, and resource use control program - Google Patents

Description

  The present invention relates to a resource use control device, a resource use control method, and a resource use control program for limiting the number of users who use resources, for example.

In the realization of the cloud and SaaS (Software As A Service), there is a multi-tenant management technology as a technology for sharing one application with a plurality of users.
One of the purposes of the multi-tenant management technology is to reduce H / W (hardware) and S / W (software) costs by sharing system resources among a plurality of users.
As an item to be considered in order to realize a form in which one application is shared by a plurality of users, there is a data management method.

Data management methods are roughly classified into, for example, the following four types according to requirements for operation, performance, or cost required by the user.
1. 1. A method for sharing a table. 2. a method for separating tables; 3. Method for separating schemas A method of isolating instances.

In a multi-tenant system, since a plurality of users share the system, processing requests may be received from many users. In this case, it is assumed that the resources of the multi-tenant system are exhausted and the response performance is significantly deteriorated.
Further, the response performance of the entire system or other users may be deteriorated due to an operation request from a specific user.

Patent Document 1 proposes a method of setting an upper limit of the number of connections that can be simultaneously connected for each user group as a method of limiting the number of users connected to the system. When the upper limit of the number of connections in the user group is reached, the connections of the users in the user group are discarded, and connections to users with high priority are permitted.
Thus, in the prior art, the maximum number of users who are connected simultaneously is defined. However, the relationship between users sharing resources and the dependency of response performance due to user information in the system are not described in the prior art.
For this reason, the conventional technology cannot avoid a situation in which the response performance of the system to other users is significantly deteriorated due to the dependency between users.

JP 2006-148648 A

  An object of the present invention is to make it possible to limit the use of resources by a propagation group related to a user group having a high load, for example.

The resource use control device of the present invention
For each user group of a plurality of user groups to which a plurality of users who use the resource belong, a group identifier for identifying the user group and the number of users who are allowed to use the resource simultaneously among the users belonging to the user group An authorized user number storage unit for storing the number of authorized users shown in association with each other;
A group attribute value storage unit that stores a group identifier of a user group and a group attribute value indicating an attribute of the user group in association with each other for each user group of the plurality of user groups;
For each user group of the plurality of user groups, a resource usage acquisition unit that acquires usage of the resource by a user group;
A load group selection unit that selects, as a load group identifier, a group identifier of a user group among the plurality of user groups, in which the resource usage acquired by the resource usage acquisition unit satisfies a restriction condition regarding the usage; ,
Among group attribute values stored in the group attribute value storage unit, a group attribute value associated with the same group identifier as the load group identifier selected by the load group selection unit is acquired as a load group attribute value. A load group attribute value acquisition unit;
Among the group identifiers stored in the group attribute value storage unit, a group identifier associated with the same group attribute value as the load group attribute value acquired by the load group attribute value acquisition unit, the load group identifier A propagation group selection unit that selects a group identifier different from the propagation group identifier;
A propagation group control unit that reduces the number of authorized users associated with the same group identifier as the propagation group identifier selected by the propagation group selection unit among the number of authorized users stored in the authorized user number storage unit; Prepare.

  According to the present invention, for example, use of resources by a propagation group related to a user group having a high load can be restricted.

1 is a configuration diagram of a data access control device 100 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a dependency information management table 191 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a tenant management table 192 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a model information management table 193 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a connection management table 194 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a tenant switching control table 195 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a usage history management table 196 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of an accumulated data management table 197 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a spread range management table 101 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a behavior condition management table 102 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of an accumulation condition management table 103 according to Embodiment 1. FIG. 3 is a flowchart illustrating an example of a data access control method according to the first embodiment. 3 is a configuration diagram of a tenant behavior monitoring unit 140 according to Embodiment 1. FIG. 5 is a flowchart illustrating tenant behavior monitoring processing in the first embodiment. 5 is a flowchart showing a spread range minimization process (S260) in the first embodiment. 3 is a configuration diagram of a tenant accumulation monitoring unit 150 according to Embodiment 1. FIG. 5 is a flowchart showing tenant accumulation monitoring processing in the first embodiment. 5 is a flowchart showing a spread range minimization process (S360) in the first embodiment. 6 is a diagram illustrating an example of processing correspondence management data 104 according to Embodiment 1. FIG. 3 is a diagram illustrating an example of hardware resources of the data access control device 100 according to Embodiment 1. FIG. 6 is a diagram illustrating a configuration example of a data access control device 100 according to Embodiment 2. FIG. It is a figure which shows the structural example (1) of the multi-tenant system 107 in Embodiment 2. FIG. It is a figure which shows the structural example (2) of the multi-tenant system 107 in Embodiment 2. FIG.

Embodiment 1 FIG.
A mode for restricting the use of resources by a spreading tenant related to a load tenant having a high load will be described.
A tenant is a user group (for example, a company) that uses system (or computer) resources.
Hereinafter, a user belonging to a tenant is referred to as a tenant user, and tenant data is referred to as tenant data.

FIG. 1 is a configuration diagram of a data access control apparatus 100 according to the first embodiment.
The configuration of data access control apparatus 100 in the first embodiment will be described with reference to FIG.

  The data access control device 100 (an example of a resource usage control device) is a computer that performs access control on the tenant data 181.

The data access control device 100 communicates with one or more tenant terminals 108 and one or more DB servers 180 via a network 109 such as the Internet or a LAN (local area network).
The tenant terminal 108 is a computer that requests data processing (for example, search processing) regarding the tenant data 181.
The DB server 180 is a computer that manages one or more tenant data 181 (database).
The data access control device 100, the tenant terminal 108, and the DB server 180 constitute a multi-tenant system (or multi-user system).

  The data access control device 100 includes an application unit 110, a data access control unit 120, a connection control unit 130, a tenant behavior monitoring unit 140, a tenant accumulation monitoring unit 150, an accumulated data monitoring unit 160, and a control device storage unit 190.

The application unit 110 receives the processing request transmitted from the tenant terminal 108, requests the necessary tenant data 181 from the data access control unit 120 based on the received processing request, and receives the tenant data received from the data access control unit 120. Data processing is performed using 181.
The application unit 110 may be mounted on a device (for example, the tenant terminal 108 or the application server) different from the data access control device 100.

The data access control unit 120 requests connection information for communication with the DB server 180 from the connection control unit 130, and connects the DB server 180 and the connection using the connection information received from the connection control unit 130.
The data access control unit 120 acquires the tenant data 181 requested from the application unit 110 from the DB server 180 and passes the acquired tenant data 181 to the application unit 110.

The connection control unit 130 passes connection information for communicating with the DB server 180 to the data access control unit 120.
However, the connection control unit 130 determines whether to permit the use of the DB server 180. When the use of the DB server 180 is permitted, the connection control unit 130 passes the connection information to the data access control unit 120. When the use of the DB server 180 is not permitted, the connection control unit 130 passes the connection information to the data access control unit 120. Don't give it. In this case, the data access control unit 120 does not acquire the tenant data 181 from the DB server 180.

  The tenant behavior monitoring unit 140 restricts data processing requested from a load tenant with a high load (data processing processing interval or processing time) on the DB server 180 and data processing requested from a spread tenant related to the load tenant. To do.

  The tenant accumulation monitoring unit 150 performs data processing requested from a load tenant with a high load on the DB server 180 (data amount or increase amount of the tenant data 181) and data processing requested from a spreading tenant related to the load tenant. Restrict.

  The accumulated data monitoring unit 160 periodically acquires the data amount of the tenant data 181 from the DB server 180 and sets the acquired data amount in an accumulated data management table 197 described later.

The control device storage unit 190 is a storage unit that stores data used in the data access control device 100.
For example, the control device storage unit 190 stores a dependency information management table 191, a tenant management table 192, a model information management table 193, a connection management table 194, a tenant switching control table 195, a usage history management table 196, and an accumulated data management table 197. To do.
In addition, the control device storage unit 190 stores a spread range management table 101, a behavior condition management table 102, an accumulation condition management table 103, and processing correspondence management data 104.
Each table contains one or more records (rows). The contents of each table will be described separately.

FIG. 2 is a diagram illustrating an example of the dependency information management table 191 according to the first embodiment.
The dependency information management table 191 in the first embodiment will be described with reference to FIG.

The dependency information management table 191 (an example of a group attribute value storage unit) is data in which information related to the dependency relationship of tenant data 181 between tenants is set.
The dependency information management table 191 associates “tenant ID”, “dependency information (1)”, and “dependency information (2)”. However, the dependency information may be one type or three or more types instead of two types.
“Tenant ID” indicates an identifier for identifying a tenant.
“Dependency information (1)” indicates first information regarding the dependency relationship between tenants. For example, it is assumed that tenant data 181 is managed by the DB server 180 in units of buildings in which one or more tenants occupy. In this case, the dependency information (1) indicates an identifier for identifying the building in which the tenant occupies.
“Dependency information (2)” indicates second information regarding the dependency relationship between tenants. For example, it is assumed that the tenant data 181 is managed by the DB server 180 in units of devices shared by a plurality of tenants. In this case, the dependency information (2) indicates an identifier for identifying a device that the tenant shares with other tenants.

FIG. 3 is a diagram illustrating an example of the tenant management table 192 according to the first embodiment.
The tenant management table 192 in the first embodiment will be described with reference to FIG.

The tenant management table 192 (an example of a group attribute value storage unit) is data for managing data processing that can be used by a tenant.
The tenant management table 192 associates “tenant ID” and “processing identifier”.
“Tenant ID” indicates an identifier for identifying a tenant.
“Processing identifier” indicates an identifier for identifying the type of data processing that can be used by the tenant.

FIG. 4 is a diagram illustrating an example of the model information management table 193 according to the first embodiment.
The model information management table 193 in the first embodiment will be described with reference to FIG.

The model information management table 193 (an example of a group attribute value storage unit) is data in which information indicating the management method of the tenant data 181 used by the tenant (hereinafter referred to as model information) is set.
The model information management table 193 associates “tenant ID”, “placement ID”, and “model type”.
“Tenant ID” indicates an identifier for identifying a tenant.
“Arrangement ID” indicates an identifier for identifying a record in the connection management table 194 described later.
“Model type” indicates a management method of the tenant data 181 used by the tenant.
As management methods of the tenant data 181, there are methods (models) such as table sharing, table separation, schema separation, instance separation, and DB server separation.
Table sharing is a model in which a table (table) in which one or more tenant data 181 is set is shared with other tenants.
Table separation is a model that uses a table (table) for each tenant.
Schema separation is a model that uses a tenant-specific schema.
Instance separation is a model that uses tenant-specific instances.
DB server separation is a model that uses a tenant-specific DB server 180.

FIG. 5 is a diagram illustrating an example of the connection management table 194 according to the first embodiment.
The connection management table 194 in the first embodiment will be described with reference to FIG.

The connection management table 194 is data for managing connection information for communicating with the DB server 180.
The connection management table 194 associates “arrangement ID”, “model type”, “IP address”, “port number”, “maximum number”, “keep idle”, “user name”, “password”, and “instance ID”.
“Arrangement ID” indicates an identifier for identifying a record in the connection management table 194.
“Model type” indicates a management method of the tenant data 181 used by the tenant.
“IP address” indicates the IP address of the DB server 180.
“Port number” indicates an identifier for identifying a port to be used among the ports provided in the DB server 180.
“Maximum number” indicates the upper limit number of connections to which the DB server 180 can connect.
“Keep idle” indicates the number of connections that the DB server 180 maintains.
“User name” indicates a user name defined in the DB server 180.
“Password” indicates a password for using the DB server 180.
“Instance ID” indicates an identifier for identifying an instance to be used among instances of the DB server 180. However, the instance ID may be replaced with an identifier for identifying a data storage destination (for example, schema).

FIG. 6 is a diagram illustrating an example of the tenant switching control table 195 according to the first embodiment.
The tenant switching control table 195 in the first embodiment will be described with reference to FIG.

The tenant switching control table 195 is data for managing the number of connections that can be connected to the DB server 180.
The tenant switching control table 195 associates “tenant ID”, “processing identifier”, and “number of remaining connections”.
“Tenant ID” indicates an identifier for identifying a tenant.
“Processing identifier” indicates an identifier for identifying the type of data processing.
“Number of remaining connections” indicates the number of connections that can be connected to the DB server 180.

FIG. 7 is a diagram illustrating an example of the usage history management table 196 according to the first embodiment.
The usage history management table 196 according to Embodiment 1 will be described with reference to FIG.

The usage history management table 196 is data for managing the history of executed data processing.
The usage history management table 196 associates “tenant ID”, “processing identifier”, “lending time”, and “return time”.
“Tenant ID” indicates an identifier for identifying a tenant who has requested data processing.
“Processing identifier” indicates an identifier for identifying the type of requested data processing.
“Lending time” indicates the time (and date) at which data processing was started.
“Return time” indicates the time (and date) when the data processing ends.

FIG. 8 is a diagram illustrating an example of the accumulated data management table 197 according to the first embodiment.
The accumulated data management table 197 in the first embodiment will be described with reference to FIG.

The accumulated data management table 197 is data for managing the number of tenant data 181 (records) stored in the DB server 180.
The accumulated data management table 197 associates “time”, “tenant ID”, “data area”, and “number of records”.
“Time” indicates the time (and date) at which the number of records is set.
“Tenant ID” indicates an identifier for identifying a tenant.
“Data area” indicates an identifier (for example, a data area name or a table name) for identifying a data area (for example, a table) in which the tenant data 181 is set.
“Number of records” indicates the number of records included in the data area.

The accumulated data monitoring unit 160 communicates with the DB server 180 periodically (every time the predetermined accumulated data monitoring time elapses), and the number of records included in each data area from the DB server 180 together with the tenant ID and the table name. get.
Then, the accumulated data monitoring unit 160 generates a record in which the acquired tenant ID, table name (data area), and number of records are set, and adds the generated record to the accumulated data management table 197.

FIG. 9 is a diagram illustrating an example of the spread range management table 101 according to the first embodiment.
The spreading range management table 101 in the first embodiment will be described with reference to FIG.

The spillover range management table 101 is data in which information for specifying a tenant (hereinafter referred to as spillover range) in which the influence of response performance on data processing occurs is set.
The spillover range management table 101 associates “ID”, “processing identifier”, “data area”, and “spillover range”. The “Ripple range” includes “Ripple type” and “Ripple target”.
“ID” indicates an identifier for identifying a record of the spread range management table 101.
“Processing identifier” indicates an identifier for identifying the type of data processing.
“Data area” indicates an identifier (for example, a data area name or a table name) for identifying a data area (for example, a table) in which the tenant data 181 is set.
“Ripple type” indicates the type (dependence information or model type) of “spread target”.
“Ripple target” indicates information for specifying a spread range.

FIG. 10 is a diagram illustrating an example of the behavior condition management table 102 according to the first embodiment.
The behavior condition management table 102 in the first embodiment will be described with reference to FIG.

The behavior condition management table 102 is data in which a condition related to the amount of data processing (hereinafter referred to as behavior condition) is set.
The behavior condition management table 102 associates “ID”, “target tenant”, “processing identifier”, and “behavior condition”. The “behavior condition” includes “condition type” and “condition value”.
“ID” indicates an identifier for identifying a record in the behavior condition management table 102.
“Target tenant” indicates an identifier for identifying a tenant.
“Processing identifier” indicates an identifier for identifying the type of data processing.
“Condition type” indicates the type of “condition value” (processing interval, processing time, etc.).
“Condition value” indicates the condition value of the behavior condition.

FIG. 11 is a diagram illustrating an example of the storage condition management table 103 according to the first embodiment.
The accumulation condition management table 103 in the first embodiment will be described with reference to FIG.

The accumulation condition management table 103 (an example of a group attribute value storage unit) is data in which conditions relating to the data amount of the tenant data 181 (hereinafter referred to as accumulation conditions) are set.
The storage condition management table 103 associates “ID”, “target tenant”, “data area”, and “storage condition”. The “accumulation condition” includes “condition type” and “condition value”.
“ID” indicates an identifier for identifying a record in the storage condition management table 103.
“Target tenant” indicates an identifier for identifying a tenant.
“Condition type” indicates the type of “condition value” (number of records, number of increases, etc.).
“Condition value” indicates the condition value of the accumulation condition.

FIG. 12 is a flowchart illustrating an example of the data access control method according to the first embodiment.
A data access control method according to the first embodiment will be described with reference to FIG.

In S110, the tenant user operates the tenant terminal 108 to start communication between the tenant terminal 108 and the data access control apparatus 100.
The tenant user inputs processing information for designating data processing related to the tenant data 181 to the tenant terminal 108. For example, a search process for searching for tenant data 181 or a tabulation process for totaling data values of tenant data 181 is an example of data processing.
The tenant terminal 108 generates a processing request based on the processing information input from the tenant user, and transmits the generated processing request to the data access control apparatus 100.
The processing request includes a “tenant ID” that identifies the tenant to which the tenant user belongs, a “processing identifier” that identifies the specified data processing, “target data information” that specifies the tenant data 181 that is the target of the data processing, and the like. It is data.
The application unit 110 of the data access control apparatus 100 receives the processing request transmitted from the tenant terminal 108.
After S110, the process proceeds to S120.

In S120, the application unit 110 generates a data request for requesting the tenant data 181 specified by the target data information included in the processing request, and passes the generated data request to the data access control unit 120.
The data request is data including a tenant ID, a processing identifier, and target data information included in the processing request.
The data access control unit 120 receives a data request from the application unit 110.
After S120, the process proceeds to S130.

In S <b> 130, the data access control unit 120 generates a connection request for requesting connection information for communicating with the DB server 180, and passes the generated connection request to the connection control unit 130.
The connection request is data including a tenant ID and a process identifier included in the data request.
The connection control unit 130 receives a connection request from the data access control unit 120.
After S130, the process proceeds to S140.

In S140, the connection control unit 130 is associated with the same tenant ID and processing identifier as the tenant ID and processing identifier included in the connection request among the remaining number of connections included in the tenant switching control table 195 (see FIG. 6). Get the remaining number of connections.
The connection control unit 130 determines whether there is a free connection based on the acquired number of remaining connections. When the remaining connection number is zero (or a value less than the remaining threshold value), there is no connection space, otherwise there is a connection space.
If it is determined that there is a free connection (YES), the process proceeds to S150.
If it is determined that there is no free connection (NO), the process proceeds to S141.

In S141, the connection control unit 130 waits for a predetermined connection waiting time to elapse. After S141, the process returns to S140.
If the remaining number of connections is increased by the connection control unit 130, the tenant behavior monitoring unit 140, or the tenant accumulation monitoring unit 150 during the connection waiting time, it is determined in S140 that there is an empty connection, and the process proceeds to S150. Become.
That is, S140 and S141 are repeated until the remaining number of connections is increased.
However, the application unit 110 may respond to the tenant terminal 108 with an error message notifying that data processing could not be performed without waiting for an increase in the remaining number of connections. In this case, the process of the data access control method ends.

In S150, the connection control unit 130 acquires an arrangement ID associated with the same tenant ID as the tenant ID included in the connection request among the arrangement IDs included in the model information management table 193 (see FIG. 4).
The connection control unit 130 acquires a record in which the acquired arrangement ID is set from the connection management table 194, and passes the acquired record to the data access control unit 120 as connection information.
The data access control unit 120 receives connection information from the connection control unit 130.

Further, the connection control unit 130 is associated with the same tenant ID and processing identifier as the tenant ID and processing identifier included in the connection request among the remaining number of connections included in the tenant switching control table 195 (see FIG. 6). The remaining number of connections is updated by subtracting the number of connections “1” from the remaining number of connections.
After S150, the process proceeds to S160.

In S160, the data access control unit 120 uses the connection information (such as the IP address and port number of the DB server 180) to connect a connection for communication with the DB server 180.
After S160, the process proceeds to S161.

In S <b> 161, the data access control unit 120 acquires the tenant data 181 specified by the target data information included in the data request from the DB server 180, and passes the acquired tenant data 181 to the application unit 110.
The application unit 110 receives the tenant data 181 from the data access control unit 120.
After S161, the process proceeds to S170.

In S170, the application unit 110 uses the tenant data 181 received from the data access control unit 120 to execute data processing identified by the processing identifier included in the processing request.
After S170, the process proceeds to S171.

In S171, the application unit 110 generates data including a processing result of data processing as a processing response, and transmits the generated processing response to the tenant terminal 108.
The tenant terminal 108 receives the processing response and displays the processing result included in the received processing response on the display.

Further, the application unit 110 notifies the data access control unit 120 of the end of the data processing, and the data access control unit 120 disconnects the connection connected in S160.
Then, the data access control unit 120 notifies the connection control unit 130 of the disconnection of the connection, and the connection control unit 130 adds the number of connections “1” to the number of remaining connections obtained by subtracting the number of connections “1” in S150, and the number of remaining connections. Update.
After S171, the process of the data access control method ends.

  Next, it is set in the tenant switching control table 195 in order to limit data processing requested from a load tenant having a high load on the DB server 180 and data processing requested from a spreading tenant related to the load tenant. The tenant behavior monitoring unit 140 and the tenant accumulation monitoring unit 150 that adjust the number of remaining connections will be described.

FIG. 13 is a configuration diagram of the tenant behavior monitoring unit 140 according to the first embodiment.
The configuration of the tenant behavior monitoring unit 140 in the first embodiment will be described with reference to FIG.

The tenant behavior monitoring unit 140 includes a load tenant selection unit 141 (an example of a load group selection unit and a load group attribute value acquisition unit), a load amount acquisition unit 142 (an example of a resource usage amount acquisition unit), and a connection remaining number minimization. Unit 143 (an example of a propagation group control unit) and a propagation tenant selection unit 144 (an example of a propagation group selection unit).
The load tenant selection unit 141 selects a tenant (load tenant) satisfying the behavior condition set in the behavior condition management table 102 by the tenant load amount acquired by the load amount acquisition unit 142 from among a plurality of tenants.
Based on the usage history management table 196, the load amount acquisition unit 142 acquires the tenant load amount (data processing processing interval or processing time) for the DB server 180 for each tenant.
The connection remaining number minimizing unit 143 is selected by the load tenant connection remaining number selected by the load tenant selecting unit 141 from the connection remaining number set in the tenant switching control table 195 and the propagation tenant selecting unit 144. Minimize the remaining number of connected tenants.
The spread tenant selection unit 144 selects a spread tenant related to the load tenant selected by the load tenant selection unit 141 based on the spread range management table 101.

FIG. 14 is a flowchart showing tenant behavior monitoring processing in the first embodiment.
Tenant behavior monitoring processing executed by the tenant behavior monitoring unit 140 (see FIG. 13) will be described with reference to FIG.
The tenant behavior monitoring unit 140 performs tenant behavior monitoring processing shown in FIG. 14 periodically (every time the predetermined behavior monitoring interval elapses) or when the administrator instructs the data access control device 100 to perform tenant behavior monitoring processing. Execute.
However, the tenant behavior monitoring unit 140 may execute the tenant behavior monitoring process at other timing (for example, the timing of executing the data processing requested from the tenant terminal 108).

In S210, the load tenant selection unit 141 selects one unselected record from the tenant management table 192 (see FIG. 3).
After S210, the process proceeds to S211.

In S211, the load tenant selection unit 141 acquires a tenant ID and a processing identifier from the record selected in S210.
After S211, the process proceeds to S220.

In S220, the load tenant selection unit 141 determines whether or not there is a record in the behavior condition management table 102 (see FIG. 10) in which the same tenant ID and processing identifier as the tenant ID and processing identifier acquired in S211 are set. judge.
However, a group tenant ID for identifying a group tenant composed of one or more tenants may be defined in the behavior condition management table 102. In addition, a group tenant table in which one or more tenant IDs and group tenant IDs are associated may be provided. In this case, the load tenant selection unit 141 has, based on the group tenant table, the group tenant ID associated with the same tenant ID as the tenant ID acquired in S211 and the same processing identifier as the processing identifier acquired in S211. It is determined whether or not the set record exists in the behavior condition management table 102.
If there is a corresponding record (YES), the process proceeds to S221.
If there is no corresponding record (NO), the process proceeds to S270.

In S221, the load tenant selection unit 141 acquires the behavior condition from the record corresponding in S220. The behavior condition includes a condition type and a condition value (see FIG. 10).
After S221, the process proceeds to S230.

In S230, the load amount acquisition unit 142 acquires a record including the same tenant ID and processing identifier as the tenant ID and processing identifier acquired in S211 among the records of the usage history management table 196 (see FIG. 7).
The load amount acquisition unit 142 uses the acquired record to acquire a load amount (data processing processing interval or processing time) according to the condition type included in the behavior condition.
For example, the load amount acquisition unit 142 acquires the load amount as follows.

When the condition type included in the behavior condition is “processing interval”, the load amount acquisition unit 142 sets the latest record whose lending time is the newest among the acquired records and the second newest lending time. Select a second record.
The load amount acquisition unit 142 calculates a time difference between the lending time set in the latest record and the lending time set in the second record as a load amount. This load amount indicates a processing interval (time) of data processing.
However, the load amount acquisition unit 142 may calculate the load amount using a record other than the latest record or the second record.
For example, the load amount acquisition unit 142 selects records in order from the newest lending time, and calculates the time difference between the lending times of the record selected for each selected record and the record immediately before the selected record. And the load amount acquisition part 142 calculates the average value of the time difference of rental time as a load amount.

When the condition type included in the behavior condition is “processing time”, the load amount acquisition unit 142 selects the latest record having the latest lending time among the acquired records.
The load amount acquisition unit 142 calculates the time difference between the lending time and the return time set in the latest record as the load amount. This load amount indicates the processing time required for data processing.
However, the load amount acquisition unit 142 may calculate the load amount using a record other than the latest record.
For example, the load amount acquisition unit 142 selects records in order from the newest lending time, and calculates the time difference between the lending time and the return time set in the selected record for each selected record. Then, the load amount acquisition unit 142 calculates the average value of the time difference between the lending time and the return time as the load amount.
Moreover, the load amount acquisition unit 142 may calculate the total value of the time difference between the lending time and the return time as the load amount.
After S230, the process proceeds to S240.

  In S240, the load tenant selection unit 141 compares the condition value included in the behavior condition with the load amount acquired in S230, and determines whether the load amount satisfies the behavior condition.

For example, when the condition type included in the behavior condition is “processing interval”, the load tenant selection unit 141 determines as follows.
When the load amount indicates a short time that is less than or equal to the condition value, the load amount satisfies the behavior condition.
When the load amount indicates a time longer than the condition value, the load amount does not satisfy the behavior condition.

When the condition type included in the behavior condition is “processing time”, the load tenant selection unit 141 determines as follows.
When the load amount indicates a long time that is equal to or greater than the condition value, the load amount satisfies the behavior condition.
When the load amount indicates a time shorter than the condition value, the load amount does not satisfy the behavior condition.

If the load amount satisfies the behavior condition (YES), the process proceeds to S250.
When the load amount does not satisfy the behavior condition (NO), the process proceeds to S270.

In S250, the remaining connection number minimizing unit 143 sets the tenant ID that is the same as the processing identifier and the tenant ID (the tenant ID of the load tenant) acquired in S211 among the records included in the tenant switching control table 195 (see FIG. 6). Select a record with a process identifier.
Then, the remaining connection number minimizing unit 143 minimizes the remaining connection number set in the selected record.
For example, the remaining connection number minimizing unit 143 updates the remaining connection number to the minimum connection value (for example, zero). It is assumed that the minimum connection value is predetermined and stored. The connection minimum value may be a value other than zero (for example, a value of 1 or more). The minimum connection value may be determined for each tenant ID, for each processing identifier, or for each combination of tenant ID and processing identifier.
After S250, the process proceeds to S260.

In S260, the propagation tenant selection unit 144 selects the tenant ID and processing identifier of the transmission tenant related to the load tenant based on the transmission range management table 101, and the connection remaining number minimization unit 143 performs the tenant ID and processing of the transmission tenant. Minimize the number of remaining connections associated with the identifier.
Details of the spread range minimizing process (S260) will be described separately.
After S260, the process proceeds to S270.

In S270, the load tenant selection unit 141 determines whether there is an unselected record that is not selected in S210 among the records included in the tenant management table 192.
If there is an unselected record (YES), the process returns to S210.
If there is no unselected record (NO), the tenant behavior monitoring process ends.

The tenant behavior monitoring unit 140 may recover the number of remaining connections minimized in S250 or S260 when a predetermined connection time limit has elapsed after the tenant behavior monitoring process is completed. For example, the tenant behavior monitoring unit 140 recovers the minimized number of remaining connections to the initial value of the number of remaining connections, or recovers the number of remaining connections increased by the number reduced when the number is minimized.
Further, the tenant behavior monitoring unit 140 may determine whether or not the load amount satisfies the behavior condition on a regular basis (every time when the connection limit time elapses) similarly to S240. When it is determined that the load amount does not satisfy the behavior condition, the tenant behavior monitoring unit 140 recovers the remaining connection number minimized in S250 or S260.
Information necessary for recovery of the remaining number of connections, such as the record that minimizes the remaining number of connections, the remaining number of connections before minimization, and the initial value of the remaining number of connections, is stored when the remaining number of connections is minimized And

FIG. 15 is a flowchart showing the spread range minimization process (S260) in the first embodiment.
The spread range minimizing process (S260) in the first embodiment will be described with reference to FIG.

In S261, the transmission tenant selection unit 144 selects a record in which the same processing identifier as the processing identifier acquired in S211 (see FIG. 14) is set from among the records included in the transmission range management table 101 (see FIG. 9). To do.
After S261, the process proceeds to S262.

In S262, the propagation tenant selection unit 144 refers to the propagation type set in the record selected in S261.
If the propagation type is “model type”, the process proceeds to S263.
If the propagation type is “dependency information (1)” or “dependence information (2)”, the process proceeds to S265.

In S263, the transmission tenant selection unit 144 has the same model type as the transmission target (for example, table sharing) set in the record selected in S261 among the records included in the model information management table 193 (see FIG. 4). Select a set record.
The spread tenant selection unit 144 acquires the tenant ID set in the record for each selected record as the tenant ID of the spread tenant.
After S263, the process proceeds to S264.

In S264, the connection remaining number minimizing unit 143, for each tenant ID of the propagated tenant acquired in S263, out of the records included in the tenant switching control table 195 (see FIG. 6), the same tenant ID as the tenant ID of the propagated tenant. And a record in which the same process identifier as the process identifier acquired in S211 (see FIG. 14) is set.
Then, the remaining connection number minimizing unit 143 minimizes the remaining connection number set in the record for each selected record (similar to S250 in FIG. 14).
After S264, the spread range minimization process (S260) ends.

In S265, the transmission tenant selection unit 144 selects the same dependency information (1) or dependency information (1) as the transmission target set in the record selected in S261 among the records included in the dependency information management table 191 (see FIG. 2). 2) Select the record that is set.
The spread tenant selection unit 144 acquires the tenant ID set in the record for each selected record as the tenant ID of the spread tenant.
After S265, the process proceeds to S266.

In S266, the connection remaining number minimizing unit 143, for each tenant ID of the propagated tenant acquired in S265, out of the records included in the tenant switching control table 195 (see FIG. 6), the same tenant ID as the tenant ID of the propagated tenant. And a record in which the same process identifier as the process identifier acquired in S211 (see FIG. 14) is set.
Then, the remaining connection number minimizing unit 143 minimizes the remaining connection number set in the record for each selected record (similar to S250 in FIG. 14).
After S266, the spread range minimizing process (S260) ends.

FIG. 16 is a configuration diagram of the tenant accumulation monitoring unit 150 according to the first embodiment.
The configuration of the tenant accumulation monitoring unit 150 in the first embodiment will be described with reference to FIG.

The tenant accumulation monitoring unit 150 includes a load tenant selection unit 151 (an example of a load group selection unit and a load group attribute value acquisition unit), a load amount acquisition unit 152 (an example of a resource usage amount acquisition unit), and a connection remaining number minimization. Unit 153 (an example of a propagation group control unit) and a propagation tenant selection unit 154 (an example of a propagation group selection unit).
The load tenant selection unit 151 selects a tenant (load tenant) that satisfies the storage condition in which the load amount of the tenant acquired by the load amount acquisition unit 152 is set in the storage condition management table 103 from among a plurality of tenants.
The load amount acquisition unit 152 acquires the tenant load amount (data amount or data increase amount) for the DB server 180 for each tenant based on the accumulated data management table 197.
The remaining connection number minimizing unit 153 is selected by the load tenant remaining number selected by the load tenant selecting unit 151 from the remaining connection numbers set in the tenant switching control table 195 and the propagated tenant selecting unit 154. Minimize the remaining number of connected tenants.
The spread tenant selection unit 154 selects a spread tenant related to the load tenant selected by the load tenant selection unit 151 based on the spread range management table 101.

FIG. 17 is a flowchart illustrating tenant accumulation monitoring processing according to the first embodiment.
Tenant accumulation monitoring processing executed by the tenant accumulation monitoring unit 150 will be described with reference to FIG.

In S310, the load tenant selection unit 151 selects one of the unselected records from the tenant management table 192 (see FIG. 3).
After S310, the process proceeds to S311.

In S311, the load tenant selection unit 151 acquires a tenant ID and a process identifier from the record selected in S310.
After S311, the process proceeds to S320.

In S320, the load tenant selection unit 151 determines whether there is a record in the storage condition management table 103 (see FIG. 11) in which the same tenant ID as the tenant ID acquired in S311 is set.
If there is a corresponding record (YES), the process proceeds to S321.
If there is no corresponding record (NO), the process proceeds to S370.

In S321, the load tenant selection unit 151 acquires the data area and the accumulation condition from the record corresponding in S320. The accumulation condition includes a condition type and a condition value (see FIG. 11).
After S321, the process proceeds to S330.

In S330, the load amount acquisition unit 152 has the same tenant ID as the tenant ID acquired in S311 and the same data area as the data area acquired in S321 in the record of the accumulated data management table 197 (see FIG. 8). Get the set record.
The load amount acquisition unit 152 uses the acquired record to acquire a load amount (the number of records in the tenant data 181 or the increase in the number of records) according to the condition type included in the accumulation condition.
For example, the load amount acquisition unit 152 acquires the load amount as follows.

When the condition type included in the accumulation condition is “number of records”, the load amount acquisition unit 152 selects the latest record in which the latest time is set from the acquired records, and sets it as the selected latest record. Get the number of records being loaded as the load.
However, the load amount acquisition unit 152 may acquire the load amount using a record other than the latest record.

When the condition type included in the accumulation condition is “increase number”, the load amount acquisition unit 152 sets the latest record with the newest time among the acquired records and the second newest time. Select the second record.
The load amount acquisition unit 152 sets the difference between the number of records set in the latest record and the number of records set in the second record, the time set in the latest record, and the second record. The time difference from the current time is calculated.
The load amount acquisition unit 152 calculates the increase number of records per unit time (for example, one day) as a load amount using the difference in the number of records and the time difference.
However, the load amount acquisition unit 152 may calculate the load amount using a record other than the latest record or the second record.
After S330, the process proceeds to S340.

  In S340, the load tenant selection unit 151 compares the condition value included in the accumulation condition with the load amount acquired in S330, and determines whether the load amount satisfies the accumulation condition.

For example, when the condition type included in the accumulation condition is “number of records”, the load tenant selection unit 151 determines as follows.
When the load amount is the number of records equal to or greater than the condition value, the load amount satisfies the accumulation condition.
When the load amount is less than the condition value, the load amount does not satisfy the accumulation condition.

Further, when the condition type included in the accumulation condition is “increase number”, the load tenant selection unit 151 determines as follows.
When the load amount is an increase number greater than or equal to the condition value, the load amount satisfies the accumulation condition.
When the load amount is an increase number smaller than the condition value, the load amount does not satisfy the accumulation condition.

If the load amount satisfies the accumulation condition (YES), the process proceeds to S350.
If the load amount does not satisfy the accumulation condition (NO), the process proceeds to S370.

In S350, the remaining connection number minimizing unit 153 includes the tenant ID that is the same as the processing identifier and the tenant ID (the tenant ID of the load tenant) acquired in S311 among the records included in the tenant switching control table 195 (see FIG. 6). Select a record with a process identifier.
Then, the connection remaining number minimizing unit 153 minimizes the connection remaining number set in the selected record (similar to S250 in FIG. 14).
After S350, the process proceeds to S360.

In S360, the transmission tenant selection unit 154 selects the tenant ID and processing identifier of the transmission tenant related to the load tenant based on the transmission range management table 101, and the connection remaining number minimization unit 153 performs the tenant ID and processing of the transmission tenant. Minimize the number of remaining connections associated with the identifier.
Details of the spread range minimizing process (S360) will be described separately.
After S360, the process proceeds to S370.

In S370, the load tenant selection unit 151 determines whether there is an unselected record that has not been selected in S310 among the records included in the tenant management table 192.
If there is an unselected record (YES), the process returns to S310.
When there is no unselected record (NO), the tenant accumulation monitoring process ends.

The tenant accumulation monitoring unit 150 may recover the number of remaining connections minimized in S350 or S360 when a predetermined connection time limit has elapsed after the tenant accumulation monitoring process is completed. For example, the tenant accumulation monitoring unit 150 recovers the minimized connection remaining number to the initial value of the connection remaining number, or increases the connection remaining number that is increased by the number reduced when it is minimized.
Further, the tenant accumulation monitoring unit 150 may determine whether or not the load amount satisfies the accumulation condition at regular intervals (every time when the connection limit time elapses) as in S340. When it is determined that the load amount does not satisfy the accumulation condition, the tenant accumulation monitoring unit 150 recovers the remaining connection number minimized in S350 or S360.
Information necessary for recovery of the remaining number of connections, such as the record that minimizes the remaining number of connections, the remaining number of connections before minimization, and the initial value of the remaining number of connections, is stored when the remaining number of connections is minimized And

FIG. 18 is a flowchart showing the spread range minimizing process (S360) in the first embodiment.
The spread range minimizing process (S360) in the first embodiment will be described with reference to FIG.

  In S361a, the spreading tenant selection unit 154 acquires a process identifier associated with the same data area as the data area acquired in S321 among the process identifiers included in the process correspondence management data 104.

FIG. 19 is a diagram illustrating an example of the processing correspondence management data 104 according to the first embodiment.
As shown in FIG. 19, the processing correspondence management data 104 includes one or more SQL statements including a processing identifier described in the first line and a data area set in the from phrase.
The processing correspondence management data 104 is data used when the application unit 110 executes data processing, and is data in which a processing identifier and a data area are associated with each other.

  After S361a (see FIG. 18), the process proceeds to S361b.

In S361b, the transmission tenant selection unit 154 includes the same data area as the data area acquired in S321 and the same processing identifier as the processing identifier acquired in S361a among the records included in the transmission range management table 101 (see FIG. 9). Select a record with.
After S361b, the process proceeds to S362.

In S362, the transmission tenant selection unit 154 refers to the transmission type set in the record selected in S362.
If the propagation type is “model type”, the process proceeds to S363.
When the propagation type is “dependency information (1)” or “dependence information (2)”, the process proceeds to S365.

In S363, the transmission tenant selection unit 154 has the same model type as the transmission target (for example, table sharing) set in the record selected in S361b among the records included in the model information management table 193 (see FIG. 4). Select a set record.
The spread tenant selection unit 154 acquires the tenant ID set in the record for each selected record as the tenant ID of the spread tenant.
After S363, the process proceeds to S364.

In S364, the remaining connection number minimizing unit 153, for each tenant ID of the affected tenant acquired in S363, out of the records included in the tenant switching control table 195 (see FIG. 6), the same tenant ID as the tenant ID of the affected tenant. And a record in which the same processing identifier as the processing identifier acquired in S361a is set.
Then, the connection remaining number minimizing unit 153 minimizes the connection remaining number set in the record for each selected record (similar to S250 in FIG. 14).
After S364, the spread range minimization process (S360) ends.

In S365, the transmission tenant selection unit 154 includes the same dependency information (1) or dependency information (1) as the transmission target set in the record selected in S361b among the records included in the dependency information management table 191 (see FIG. 2). 2) Select the record that is set.
The spread tenant selection unit 154 acquires the tenant ID set in the record for each selected record as the tenant ID of the spread tenant.
After S365, the process proceeds to S366.

In S366, the remaining connection number minimizing unit 153, for each tenant ID of the affected tenant acquired in S365, out of the records included in the tenant switching control table 195 (see FIG. 6), the same tenant ID as the tenant ID of the affected tenant. And a record in which the same processing identifier as the processing identifier acquired in S361a is set.
Then, the connection remaining number minimizing unit 153 minimizes the connection remaining number set in the record for each selected record (similar to S250 in FIG. 14).
After S366, the spread range minimization process (S360) ends.

FIG. 20 is a diagram illustrating an example of hardware resources of the data access control apparatus 100 according to the first embodiment.
20, the data access control device 100 (an example of a computer) includes a CPU 901 (Central Processing Unit). The CPU 901 is connected to hardware devices such as a ROM 903, a RAM 904, a communication board 905 (communication device), a display 911 (display device), a keyboard 912, a mouse 913, a drive 914, and a magnetic disk device 920 via a bus 902. Control hardware devices. The drive 914 is a device that reads and writes storage media such as an FD (Flexible Disk), a CD (Compact Disc), and a DVD (Digital Versatile Disc).
The ROM 903, the RAM 904, the magnetic disk device 920, and the drive 914 are examples of storage devices. A keyboard 912, a mouse 913, and a communication board 905 are examples of input devices. The display 911 and the communication board 905 are examples of output devices.

  The communication board 905 is wired or wirelessly connected to a communication network such as a LAN (Local Area Network), the Internet, or a telephone line.

  The magnetic disk device 920 stores an OS 921 (operating system), a program group 922, and a file group 923.

  The program group 922 includes programs that execute the functions described as “units” in the embodiments. A program (for example, a resource use control program) is read and executed by the CPU 901. That is, the program causes the computer to function as “to part”, and causes the computer to execute the procedures and methods of “to part”.

  The file group 923 includes various data (input, output, determination result, calculation result, processing result, etc.) used in “˜part” described in the embodiment.

In the embodiment, arrows included in the configuration diagrams and flowcharts mainly indicate input and output of data and signals.
The processing of the embodiment described based on the flowchart and the like is executed using hardware such as the CPU 901, a storage device, an input device, and an output device.

  In the embodiment, what is described as “to part” may be “to circuit”, “to apparatus”, and “to device”, and “to step”, “to procedure”, and “to processing”. May be. That is, what is described as “to part” may be implemented by any of firmware, software, hardware, or a combination thereof.

  In the first embodiment, the data area of the DB server 180 is an example of a system resource (also referred to as a computer resource). Other system resources include a CPU, a memory, an input / output device, a communication device, or a network.

Embodiment 1 has the following effects, for example.
In multi-tenant management technology that shares system resources using data management methods (table sharing, table separation, schema separation, instance separation, etc.), the right to use an application is controlled for each user.
Even when a specific company (tenant) issues an unnecessary processing request in a short time, the request from the company is reduced to the minimum. As a result, it is possible to avoid a situation in which the response performance of the entire system is deteriorated due to the depletion of the system resources of the multi-tenant system and the shortage of system resources allocated to other companies.
Processing requests from a specific company require an unnecessarily long processing time, system resources of the multi-tenant system are depleted, and system resources allocated to other companies are insufficient, resulting in degraded response performance of the entire system Can avoid the situation.
The entire system takes longer than necessary due to data accumulated unnecessarily by a specific company, the system resources of the multi-tenant system are depleted, and the system resources allocated to other companies are insufficient. The situation where the response performance of the system deteriorates can be avoided.
In addition, by minimizing processing requests for high-load processing by spreading companies, it is possible to minimize the range of influence on the entire system.

In the first embodiment, for example, the following resource usage control device (100) has been described. The code | symbol or name of a corresponding structure is described in a parenthesis.
The resource usage control device includes an authorized user number storage unit (195), a group attribute value storage unit (191, 192, 193, 103), a resource usage acquisition unit (142, 152), and a load group selection unit ( 141, 151), a load group attribute value acquisition unit (141, 151), a propagation group selection unit (144, 154), and a propagation group control unit (143, 153).
The permitted user number storage unit includes a group identifier (tenant ID) for identifying a user group for each user group of a plurality of user groups (tenant) to which a plurality of users (tenant users) using the resource belong, and a user group The number of allowed users (number of connections) indicating the number of users who are allowed to use the resource at the same time among the users belonging to the user is stored in association with each other.
The group attribute value storage unit includes, for each user group of the plurality of user groups, a group identifier of the user group and a group attribute value (processing identifier, model type, dependency information, data area) indicating an attribute of the user group, and Are stored in association with each other.
The resource usage acquisition unit acquires the usage (load) of the resource by the user group for each user group of the plurality of user groups.
The load group selection unit is a user group whose usage amount acquired by the resource usage acquisition unit satisfies a restriction condition (behavioral condition, accumulation condition) regarding the usage amount among the plurality of user groups. Select the group identifier as the load group identifier.
The load group attribute value acquisition unit is a group attribute associated with the same group identifier as the load group identifier selected by the load group selection unit among the group attribute values stored in the group attribute value storage unit Get the value as a load group attribute value.
The spreading group selection unit is a group identifier associated with the same group attribute value as the load group attribute value acquired by the load group attribute value acquisition unit among the group identifiers stored in the group attribute value storage unit Then, a group identifier different from the load group identifier is selected as the spreading group identifier.
The spreading group control unit determines the number of allowed users associated with the same group identifier as the spreading group identifier selected by the spreading group selection unit among the number of permitted users stored in the permitted user number storage unit. cut back.

  The resource usage control device is configured to reduce a number of permitted users associated with the same group identifier as the load group identifier among the number of permitted users stored in the number of permitted users storage unit (143, 153). ).

The resource usage control device includes a usage request receiving unit (110) and a usage permission determining unit (130).
The use request receiving unit includes a use request including a request group identifier for identifying a user group to which the requesting user belongs from a user terminal (108) used by a requesting user who requests use of the resource among the plurality of users. (Processing request) is received.
The use permission determining unit is associated with the same group identifier as the request group identifier included in the use request received by the use request receiving unit among the user permission numbers stored in the user permission number storage unit. It is determined whether to permit the use of the resource by the requesting user based on the number of user permissions.

The resource usage control device stores, for each user group of the plurality of user groups, a history information storage unit (196) that stores a plurality of use times (lending time, return time) when a user belonging to the user group used the resource. Is provided.
The resource usage acquisition unit is configured to use the resource usage (processing interval, processing) of the user group for each user group of the plurality of user groups based on the plurality of usage times stored in the history information storage unit. Time).

The resource usage acquisition unit is configured to determine, for each user group of the plurality of user groups, a time interval (processing interval) at which the user group uses the resource based on the plurality of usage times stored in the history information storage unit. ) As the usage amount of the resource.
The load group selection unit selects, as the load group identifier, a group identifier of a user group having a time interval shorter than a time interval that is the restriction condition among the plurality of user groups.

The resource usage amount acquiring unit is configured to use a usage time (processing time) when a user group uses the resource for each user group of the plurality of user groups based on the plurality of usage times stored in the history information storage unit. ) As the usage amount of the resource.
The load group selection unit selects, as the load group identifier, a group identifier of a user group whose usage amount of the resource is longer than a usage time that is the restriction condition among the plurality of user groups.

The resource usage control device includes a data amount storage unit (197) that stores a data amount (number of records) for a user group for each user group of the plurality of user groups.
The resource usage acquisition unit calculates the usage (data amount, increase) of the resource of the user group for each user group of the plurality of user groups based on the data amount stored in the data amount storage unit. calculate.

The resource usage acquisition unit acquires, for each user group of the plurality of user groups, the data amount of the user group among the data amounts stored in the data amount storage unit as the usage amount of the resource.
The load group selection unit selects, as the load group identifier, a group identifier of a user group having a data amount that is larger than a data amount that is the restriction condition among the plurality of user groups.

The data amount storage unit stores a data amount according to time for each user group.
The resource usage amount acquiring unit calculates an increase amount of data for a user group for each user group of the plurality of user groups based on a data amount for each user group stored in the data amount storage unit. Calculated as the resource usage.
The load group selection unit selects, as the load group identifier, a group identifier of a user group in which the usage amount of the resource is an increase amount larger than the increase amount that is the restriction condition among the plurality of user groups.

The resource usage control device includes a first group attribute value storage unit (192) and a second group attribute value storage unit (193) as the group attribute value storage unit.
The first group attribute value storage unit stores, as the group attribute value, a process identifier for identifying data processing for a user group in association with a group identifier of the user group for each user group of the plurality of user groups. To do.
The second group attribute value storage unit associates, for each user group of the plurality of user groups, a usage identifier (model type) of the resource used by the user group in association with a group identifier of the user group. Store as a value.
The resource usage control device includes a propagation range storage unit (101) that stores processing identifiers included in a plurality of processing identifiers and usage types included in a plurality of usage types (spreading types) in association with each other.
The load group attribute value acquisition unit uses a process identifier associated with the same group identifier as the load group identifier among the process identifiers stored in the first group attribute value storage unit as the load group attribute value. get.
The propagation group selection unit acquires, as a load usage type, a usage type associated with the same processing identifier as the load group attribute value among the usage types stored in the transmission range storage unit.
The propagation group selection unit selects, as the propagation group identifier, a group identifier associated with the same usage type as the load usage type among the group identifiers stored in the second group attribute value storage unit.

The resource usage control device includes a first group attribute value storage unit (103) and a second group attribute value storage unit (191) as the group attribute value storage unit.
The first group attribute value storage unit associates, for each user group of the plurality of user groups, a data area name that identifies a data area used by the user group in association with a group identifier of the user group. Remember as.
The second group attribute value storage unit associates, for each user group of the plurality of user groups, a usage identifier (dependency information) of the resource used by the user group in association with a group identifier of the user group. Store as a value.
The resource usage control device includes a spread range storage unit (101) and a processing correspondence storage unit (104).
The propagation range storage unit stores a processing identifier included in a plurality of processing identifiers, a data region name included in a plurality of data region names, and a usage type included in a plurality of usage types (spreading types) in association with each other.
The process correspondence storage unit associates and stores a process identifier included in a plurality of process identifiers and a data area name included in a plurality of data area names.
The load group attribute value acquisition unit selects a data region name associated with the same group identifier as the load group identifier among the data region names stored in the first group attribute value storage unit. Get as a value.
The propagation group selection unit acquires, as a load process identifier, a process identifier associated with the same data area name as the load group attribute value among the process identifiers stored in the process correspondence storage unit.
The propagation group selection unit is a usage associated with the same processing identifier as the load processing identifier and the same data area name as the load group attribute value among the usage types stored in the propagation range storage unit. Acquires the type as the load usage type.
The propagation group selection unit selects, as the propagation group identifier, a group identifier associated with the same usage type as the load usage type among the group identifiers stored in the second group attribute value storage unit.

Embodiment 2. FIG.
A configuration example of the multi-tenant system will be described.

FIG. 21 is a diagram illustrating a configuration example of the data access control apparatus 100 according to the second embodiment.
As shown in FIG. 21, the data access control device 100 may include a plurality of application units 110A and 110B.

FIG. 22 is a diagram illustrating a configuration example (1) of the multi-tenant system 107 according to the second embodiment.
As illustrated in FIG. 22, the multi-tenant system 107 may include an application device 106 that functions as the application unit 110.
The application device 106 includes an application unit 110 instead of the data access control device 100.

FIG. 23 is a diagram illustrating a configuration example (2) of the multi-tenant system 107 according to the second embodiment.
As shown in FIG. 23, the multi-tenant system 107 may include a plurality of application devices 106A and 106B that function as application units 110A and 110B.
Each of the application devices 106A and 106B includes application units 110A and 110B instead of the data access control device 100.

As shown in FIG. 21 or FIG. 23, when a plurality of application units 110A and 110B are provided, the application units 110A and 110B can be distinguished by using different processing identifiers for each application unit.
For example, the application unit 110A uses process identifiers “j0001” to “j0100”, and the application unit 110B uses process identifiers “j0101” to “j0200”.

  DESCRIPTION OF SYMBOLS 100 Data access control apparatus, 101 Ripple range management table, 102 Behavior condition management table, 103 Accumulation condition management table, 104 Process management management data, 106 Application apparatus, 107 Multi-tenant system, 108 Tenant terminal, 109 Network, 110 Application part, 120 Data access control unit, 130 Connection control unit, 140 Tenant behavior monitoring unit, 141 Load tenant selection unit, 142 Load amount acquisition unit, 143 Connection remaining number minimization unit, 144 Propagation tenant selection unit, 150 Tenant accumulation monitoring unit, 151 Load tenant selection unit, 152 Load amount acquisition unit, 153 Connection remaining number minimization unit, 154 Spread tenant selection unit, 160 Accumulated data monitoring unit, 180 DB server, 181 Tenant data, 190 Control device storage unit, 191 Dependent information management table, 192 Tenant management table, 193 Model information management table, 194 Connection management table, 195 Tenant switching control table, 196 Usage history management table, 197 Accumulated data management table, 901 CPU, 902 bus , 903 ROM, 904 RAM, 905 communication board, 911 display, 912 keyboard, 913 mouse, 914 drive, 920 magnetic disk device, 921 OS, 922 program group, 923 file group.

Claims (13)

For each user group of a plurality of user groups to which a plurality of users using the resource belong, a group identifier for identifying the user group and the number of users allowed to use the resource among the users belonging to the user group are indicated. An authorized user number storage unit for storing the number of authorized users in association with each other;
A group attribute value storage unit that stores a group identifier of a user group and a group attribute value indicating an attribute of the user group in association with each other for each user group of the plurality of user groups;
For each user group of the plurality of user groups, a resource usage acquisition unit that acquires usage of the resource by a user group;
A load group selection unit that selects, as a load group identifier, a group identifier of a user group among the plurality of user groups, in which the resource usage acquired by the resource usage acquisition unit satisfies a restriction condition regarding the usage; ,
Among group attribute values stored in the group attribute value storage unit, a group attribute value associated with the same group identifier as the load group identifier selected by the load group selection unit is acquired as a load group attribute value. A load group attribute value acquisition unit;
Among the group identifiers stored in the group attribute value storage unit, a group identifier associated with the same group attribute value as the load group attribute value acquired by the load group attribute value acquisition unit, the load group identifier A propagation group selection unit that selects a group identifier different from the propagation group identifier;
A spreading group control unit that reduces the number of allowed users associated with the same group identifier as the spreading group identifier selected by the spreading group selection unit out of the number of permitted users stored in the permitted user number storage unit; A resource use control device comprising: The load group control part which reduces the number of authorized users matched with the same group identifier as the said load group identifier among the number of authorized users memorize | stored in the said authorized user number memory | storage part is provided. Resource usage controller. A use request receiving unit that receives a use request including a request group identifier that identifies a user group to which the requesting user belongs, from a user terminal used by a requesting user that requests use of the resource among the plurality of users;
Based on the user permission number associated with the same group identifier as the request group identifier included in the use request received by the use request receiving unit among the user permission number stored in the user permission number storage unit, The resource usage control apparatus according to claim 1, further comprising: a use permission determination unit that determines whether to permit use of the resource by the requesting user. The resource usage control device includes a history information storage unit that stores, for each user group of the plurality of user groups, a plurality of use times when a user belonging to the user group uses the resource,
The resource usage acquisition unit calculates the resource usage of the user group for each user group of the plurality of user groups based on the plurality of usage times stored in the history information storage unit. 4. The resource use control device according to claim 1, wherein the resource use control device is characterized in that: The resource usage acquisition unit sets a time interval at which a user group uses the resource for each user group of the plurality of user groups based on the plurality of usage times stored in the history information storage unit. As usage of
The load group selection unit selects, as the load group identifier, a group identifier of a user group having a time interval shorter than a time interval that is the restriction condition among the plurality of user groups. The resource use control device according to claim 4. The resource usage acquisition unit is configured to calculate, for each user group of the plurality of user groups, a usage time during which the user group used the resource based on the plurality of usage times stored in the history information storage unit. As usage of
The load group selection unit selects, as the load group identifier, a group identifier of a user group whose usage amount of the resource is longer than a usage time that is the restriction condition among the plurality of user groups. The resource use control device according to claim 4. The resource usage control device includes a data amount storage unit that stores a data amount for a user group for each user group of the plurality of user groups,
The resource usage acquisition unit calculates the resource usage of the user group for each user group of the plurality of user groups based on the data amount stored in the data amount storage unit. The resource use control apparatus according to any one of claims 1 to 3. The resource usage amount acquiring unit acquires, for each user group of the plurality of user groups, a data amount of the user group out of the data amount stored in the data amount storage unit as a usage amount of the resource,
The load group selection unit selects, as the load group identifier, a group identifier of a user group having a data amount that is larger than a data amount that is the restriction condition among the plurality of user groups. The resource use control device according to claim 7. The data amount storage unit stores a data amount by time for each user group,
The resource usage amount acquiring unit calculates an increase amount of data for a user group for each user group of the plurality of user groups based on a data amount for each user group stored in the data amount storage unit. Calculate as the resource usage,
The load group selection unit selects, as the load group identifier, a group identifier of a user group whose usage amount of the resource is an increase amount larger than the increase amount that is the restriction condition among the plurality of user groups. The resource use control device according to claim 7. The resource use control device includes a first group attribute value storage unit and a second group attribute value storage unit as the group attribute value storage unit,
The first group attribute value storage unit stores, as the group attribute value, a process identifier for identifying data processing for a user group in association with a group identifier of the user group for each user group of the plurality of user groups. And
The second group attribute value storage unit stores, as the group attribute value, the use type of the resource used by the user group in association with the group identifier of the user group for each user group of the plurality of user groups. ,
The resource usage control device includes a spread range storage unit that stores a processing identifier included in a plurality of processing identifiers and a usage type included in the plurality of usage types in association with each other,
The load group attribute value acquisition unit uses a process identifier associated with the same group identifier as the load group identifier among the process identifiers stored in the first group attribute value storage unit as the load group attribute value. Acquired,
The propagation group selection unit acquires, as a load usage type, a usage type associated with the same processing identifier as the load group attribute value among the usage types stored in the propagation range storage unit,
The propagation group selection unit selects, as the propagation group identifier, a group identifier associated with the same usage type as the load usage type among group identifiers stored in the second group attribute value storage unit. 10. The resource usage control device according to claim 1, wherein The resource use control device includes a first group attribute value storage unit and a second group attribute value storage unit as the group attribute value storage unit,
The first group attribute value storage unit associates, for each user group of the plurality of user groups, a data area name that identifies a data area used by the user group in association with a group identifier of the user group. Remember as
The second group attribute value storage unit stores, as the group attribute value, the use type of the resource used by the user group in association with the group identifier of the user group for each user group of the plurality of user groups. ,
The resource usage control device includes a spread range storage unit and a processing correspondence storage unit,
The spread range storage unit associates and stores process identifiers included in a plurality of process identifiers, data area names included in a plurality of data area names, and use types included in a plurality of use types,
The processing correspondence storage unit stores a processing identifier included in a plurality of processing identifiers and a data region name included in a plurality of data region names in association with each other,
The load group attribute value acquisition unit selects a data region name associated with the same group identifier as the load group identifier among the data region names stored in the first group attribute value storage unit. As a value,
The propagation group selection unit acquires, as a load process identifier, a process identifier associated with the same data area name as the load group attribute value among the process identifiers stored in the process correspondence storage unit,
The propagation group selection unit is a usage associated with the same processing identifier as the load processing identifier and the same data area name as the load group attribute value among the usage types stored in the propagation range storage unit. Get the type as a load usage type,
The propagation group selection unit selects, as the propagation group identifier, a group identifier associated with the same usage type as the load usage type among the group identifiers stored in the second group attribute value storage unit. 10. The resource usage control device according to claim 1, wherein Resource use comprising an authorized user number storage unit, a group attribute value storage unit, a resource usage acquisition unit, a load group selection unit, a load group attribute value acquisition unit, a propagation group selection unit, and a propagation group control unit A resource usage control method using a control device,
The permitted user number storage unit may use a group identifier for identifying a user group for each user group of a plurality of user groups to which a plurality of users using the resource belongs, and use the resource among the users belonging to the user group. A storage unit that stores the number of permitted users indicating the number of permitted users in association with each other;
The group attribute value storage unit is a storage unit that stores a group identifier of a user group and a group attribute value indicating an attribute of the user group in association with each user group of the plurality of user groups,
The resource usage acquisition unit acquires the usage of the resource by a user group for each user group of the plurality of user groups,
The load group selection unit uses, as a load group identifier, a group identifier of a user group among the plurality of user groups whose usage amount of the resource acquired by the resource usage acquisition unit satisfies a restriction condition regarding the usage amount Selected,
The group attribute associated with the same group identifier as the load group identifier selected by the load group selection unit among the group attribute values stored in the group attribute value storage unit by the load group attribute value acquisition unit Get the value as a load group attribute value,
The group identifier associated with the same group attribute value as the load group attribute value acquired by the load group attribute value acquisition unit among the group identifiers stored in the group attribute value storage unit by the propagation group selection unit A group identifier different from the load group identifier is selected as a spreading group identifier,
The spreading group control unit, the number of authorized users associated with the same group identifier as the spreading group identifier selected by the spreading group selection unit among the number of authorized users stored in the authorized user number storage unit A resource usage control method characterized by reducing.   A resource use control program for causing a computer to function as the resource use control device according to claim 1.

Images