JP7186043B2 - Management device, system and program - Google Patents

Description

The present invention relates to a management device, system and program.

There is known a technique of setting an upper limit on the number of accesses that can be made within a predetermined period of time in a Web server device (see, for example, Patent Document 1).
[Prior art documents]
[Patent Literature]
[Patent Document 1] JP-A-2017-215901

It is desired to suppress the number of service requests arriving from the client device to the server device to an appropriate number according to the capabilities of the server device.

In a first aspect of the invention, a management device is provided. The management device described above includes, for example, a management unit that manages the number of client devices permitted to transmit service requests to the server device. The management device described above includes, for example, a request receiving unit that receives request information requesting permission to transmit a service request from a client device. For example, when the request receiving unit receives the request information, the management device transmits a service request to the client device on condition that the number managed by the management unit is less than a predetermined upper limit. a judgment unit for judging that the The management device described above includes, for example, a transmission unit that transmits permission information to the client device when the determination unit determines that the transmission of the service request to the client device is permitted.

The management unit may manage information indicating whether or not each piece of permission information has been transmitted to the client device. The determining unit determines, based on the information managed by the managing unit, that the client device is permitted to transmit the service request when there is permission information that has not been transmitted to the client device among the plurality of pieces of permission information. you can

The above-described management device may include a termination notification receiving unit that receives a termination notification transmitted from the client device after the client device receives a response from the server device in response to the service request. The management unit increases a first permission issuance number indicating the number of times the client device is permitted to transmit the service request in response to the transmission of the permission information, and issues the first permission in response to the reception of the end notification. You can reduce the number.

The management unit may further add the identification information of the client device to the queue when the request reception unit receives the request information and the number managed by the management unit has reached the upper limit. The transmitting unit may transmit the permission information to the client device identified by the identification information included in the queue when the termination notification receiving unit receives the termination notification.

When the request receiving unit receives the request information, the transmitting unit sets the waiting time until the client device transmits the service request to the server device when the number managed by the managing unit reaches the upper limit. You may send permission information including:

The above-described management apparatus may include an allowance receiving unit that receives information indicating an allowance for the server apparatus to accept service requests from the server apparatus. The management unit may adjust the upper limit according to the allowable amount.

An upper limit value may be defined for each of a plurality of priorities. The management unit may manage a first permission issue count indicating the number of permission issued to the client device to transmit the service request, in association with each of the plurality of priorities. When the request receiving unit receives the request information, the determining unit determines the first number of permission issuances managed by the management unit in association with the priority of service provision to the client device for the priority. It may be determined that the client device is permitted to send a service request if it is less than the specified upper limit.

The manager may also manage priorities for multiple client devices. When the first number of permission issuances managed by the management unit in association with the priority of the client device that is the transmission source of the request information is less than the upper limit value set for the priority, the determination unit , may decide to allow the client device to send the service request.

The request information transmitted from the client device may include priority information indicating the priority of the service request. The determination unit determines whether the number of first permission issuances managed by the management unit in association with the priority indicated by the priority information included in the request information is less than the upper limit value set for the priority. If so, it may be determined to allow the client device to send a service request.

The management unit manages a second permission issue count indicating the number of permission to transmit service requests to client devices having a higher priority for service provision than each priority, in association with each of the plurality of priorities. good. The determination unit issues a first permission managed by the management unit in association with the first priority when the priority of service provision to the client device that is the source of the request information is the first priority. Even if the number reaches the upper limit set for the first priority, the second priority managed by the management unit is associated with the second priority lower than the first priority. 2 may be determined to allow the client device to send a service request provided that the number of issued grants of 2 is less than a predetermined threshold that is less than the upper limit value determined for the second priority.

In a second aspect of the invention, a system is provided. The system includes, for example, the management device described above and the client device described above.

In a third aspect of the invention, a program is provided. The above program may be a program for causing a computer to function as the above management apparatus. The program may be a program for causing a computer to execute information processing in the management apparatus. A computer readable medium storing the above program may be provided. The computer-readable medium may be non-transitory computer-readable medium. The computer-readable medium may be a computer-readable recording medium.

It should be noted that the above summary of the invention does not list all the necessary features of the invention. Subcombinations of these feature groups can also be inventions.

1 schematically shows an example of the configuration of system 10 in one embodiment. 3 is a block diagram showing the functional configuration of a management device 40; FIG. 3 shows a processing sequence in the client device 20, the server device 30, and the management device 40. FIG. An example of information managed by the management unit 240 is shown in a table format. 4 is a flowchart showing processing in the management device 40; 4 is a flowchart showing processing in the client device 20; 4 shows a time chart when an access ticket including waiting time is transmitted to the client device 20. FIG.

Hereinafter, the present invention will be described through embodiments of the invention, but the following embodiments do not limit the invention according to the claims. Also, not all combinations of features described in the embodiments are essential for the solution of the invention. In addition, in the drawings, the same or similar parts may be denoted by the same reference numerals to omit redundant description.

FIG. 1 schematically shows an example configuration of a system 10 in one embodiment. In this embodiment, the system 10 includes a server device 30 , a client device 20 a, a client device 20 b, a client device 20 c and a client device 20 d, and a management device 40 . In this embodiment, the client device 20a, the client device 20b, the client device 20c, and the client device 20d may be collectively referred to as the "client device 20".

The server device 30 , client device 20 and management device 40 are connected via the network 12 . Network 12 may include any communication line. For example, network 12 may include at least one of leased lines, public lines, and local lines. Public lines may include at least one of the Internet, mobile communication lines, telephone lines, and the like. The mobile communication network may include so-called 3G (3rd Generation), LTE (Long Term Evolution), 4G (4th Generation) and 5G (5th Generation).

The server device 30 provides services to the client device 20 in response to service requests from the client device 20 . The server device 30 , for example, performs processing requested by the client device 20 and returns a response indicating the processing result to the client device 20 . The server device 30 may be, for example, a web server, an application server, or the like.

As an example of usage of the system 10, a case where the system 10 is used in a financial institution will be described. The server device 30 is, for example, a center server of a financial institution. The server device 30 stores customer data relating to customers of financial institutions. For example, the server device 30 stores, as customer data, data on past transactions between financial institutions and customers, information on financial accounts owned by customers, credit information on customers, and the like.

The client device 20a, the client device 20b, the client device 20c, and the client device 20d are installed in the branch of the financial institution. The client device 20 a , the client device 20 b , the client device 20 c , and the client device 20 d acquire customer data stored in the server device 30 .

The client device 20a automatically collects customer data from the server device 30 by a robotic process automation (RPA) function. The client device 20a automatically downloads customer data used in store operations from the server device 30. FIG. For example, the client device 20a refers to the next day's schedule data of the person in charge of public relations, and downloads from the server device 30 the customer data of the business partner to whom the person in charge of public relations will visit the next day. The client device 20a transmits the customer data downloaded from the server device 30 to the e-mail address of the contact person.

The client device 20b is a terminal used by a contact person. The person in charge of public relations can use the client device 20b to refer to the customer data delivered to the e-mail address of the person in charge of public relations. Also, the person in charge of public relations can operate the client device 20 b to access the server device 30 and download the customer data directly from the server device 30 .

The client device 20c is a teller terminal operated by a person in charge of counter operations at a branch of a financial institution. The client device 20c is a so-called first-line terminal. The client device 20d is a back terminal operated by a back office worker who performs back office work. The client device 20d is a so-called two-wire terminal. The client device 20c and the client device 20d download from the server device 30 a list of account information opened by the customer, for example, when receiving a new account opening request from the customer. As a result, the person in charge of the counter or the back office worker can confirm that the customer has not already opened an account of the same type.

Here, if the client device 20a, the client device 20b, the client device 20c, and the client device 20d access the server device 30 all at once, the number of accesses that the server device 30 can process will be exceeded, and the server device 30 will not be able to provide services. may not be available. For example, in a plurality of stores, if the client devices 20a access the server device 30 all at once at the end of banking business and try to download customer data, the server device 30 may not be able to provide services to the client devices 20. be.

The management device 40 prevents transmission of a large number of service requests from the client device 20 to the server device 30 . Specifically, the management device 40 manages access tickets that permit the client device 20 to access the server device 30 . For example, the management device 40 manages the number of access tickets corresponding to the processing capacity of the server device 30 that can be used to respond to service requests from the client device 20 .

The client device 20 requests an access ticket from the management device 40 before transmitting a customer data transmission request to the server device 30 . The management device 40 transmits access tickets to the client device 20 when the number of access tickets already transmitted to the client device 20 is less than the upper limit of access tickets managed by the management device 40 .

After receiving the access ticket from the server device 30 , the client device 20 transmits a customer data service request to the server device 30 . Upon receiving a response including customer data from the server device 30 , the client device 20 returns the access ticket to the management device 40 and performs processing using the customer data received from the server device 30 .

According to the system 10 , the number of service requests arriving from the client device 20 to the server device 30 can be suppressed to an appropriate number according to the processing capability of the server device 30 . As a result, it is possible to prevent the server device 30 from being unable to provide services to the client device 20 due to overload.

FIG. 2 is a block diagram showing the functional configuration of the management device 40. As shown in FIG. The management device 40 includes a processing unit 42 , a storage unit 48 and a storage unit 44 . The processing unit 42 is realized by a processing device including a processor. The storage unit 48 is realized by a volatile storage device. The storage unit 44 is realized by a nonvolatile storage device.

The processing unit 42 includes a request receiving unit 210 , a determining unit 220 , a transmitting unit 230 , a managing unit 240 , an end notification receiving unit 250 and an allowable amount receiving unit 260 .

The management unit 240 manages the number of permitted client devices 20 to transmit service requests to the server device 30 . For example, the management unit 240 manages the number of access tickets transmitted to the client device 20 . Note that the request that the client device 20 transmits to the server device 30 in this embodiment is an example of a service request.

The request receiving unit 210 receives request information requesting permission to transmit a service request from the client device 20 . The access ticket request in this embodiment is an example of request information.

When the request receiving unit 210 receives request information, the determining unit 220 transmits a service request to the client device 20 on condition that the number managed by the managing unit 240 is less than a predetermined upper limit. decide to allow The transmission unit 230 transmits permission information to the client device 20 when the determination unit 220 determines that the client device 20 is permitted to transmit the service request. For example, the management unit 240 manages information indicating whether or not each piece of permission information has been transmitted to the client device 20 . Based on the information managed by the management unit 240, the determination unit 220 instructs the client device 20 to transmit a service request when there is permission information that has not been transmitted to the client device 20 among the plurality of pieces of permission information. You can decide to allow it. Accordingly, it is possible to prevent a large number of service requests from being simultaneously transmitted from the client device 20 to the server device 30 . Note that the access ticket transmitted from the management device 40 to the client device 20 in this embodiment is an example of permission information.

The end notification receiving unit 250 receives the end notification transmitted from the client device 20 after the client device 20 receives a response from the server device 30 in response to the service request. The access ticket return information in this embodiment is an example of a termination notice. In response to the transmission of the permission information, the management unit 240 increases the first permission issue number indicating the number of permission for the client device 20 to transmit the service request, and in response to the reception of the end notification, the first Reduce the number of permits issued.

Further, when the request receiving unit 210 receives the request information and the number managed by the managing unit 240 reaches the upper limit, the management unit 240 adds the identification information of the client device 20 to the queue. . When the termination notification receiving section 250 receives the termination notification, the transmission section 230 transmits permission information to the client device 20 identified by the identification information included in the queue. This allows other client devices 20 to transmit service requests as soon as the access ticket is returned.

When the request receiving unit 210 receives the request information, the transmitting unit 230 causes the client device 20 to transmit a service request to the server device 30 when the number managed by the managing unit 240 reaches the upper limit. You may send permission information including waiting time to. Permission information including the waiting time will be described with reference to FIG. 7 and the like.

The allowable amount receiving unit 260 receives from the server apparatus 30 information indicating the allowable amount with which the server apparatus 30 can receive service requests. The permissible number of accesses information of this embodiment is an example of information indicating the permissible amount. The management unit 240 adjusts the upper limit of the number of permitted transmissions of service requests according to the allowable amount received from the server device 30 . Accordingly, it is possible to dynamically adjust the allowable number of accesses permitted for the client device 20 to access the server device 30 according to the current load of the server device 30 . For example, when the load on the server device 30 increases, the allowable number of accesses can be decreased, and when the load on the server device 30 decreases, the allowable number of accesses can be increased. As a result, service requests arriving from the client device 20 to the server device 30 can be suppressed when the resources of the server device 30 are tight.

An upper limit value may be defined for each of a plurality of priorities. The management unit 240 may manage the first number of permission issues indicating the number of permission issued to the client device 20 to transmit the service request, in association with each of the plurality of priorities. When the request receiving unit 210 receives the request information, the determination unit 220 determines that the number of first permission issuances managed by the management unit 240 in association with the priority of service provision to the client device 20 corresponds to the priority. It may be determined that the client device 20 is permitted to transmit the service request if the value is less than the upper limit value set for the client device 20 .

The management unit 240 may manage priorities for a plurality of client devices 20 . The determination unit 220 determines that the first number of permission issuances managed by the management unit 240 in association with the priority of the client device 20 that is the transmission source of the request information is less than the upper limit set for the priority. , it may be determined that the client device 20 is permitted to transmit a service request.

Note that the request information transmitted from the client device 20 may include priority information indicating the priority of the service request. The determination unit 220 determines that the first number of permission issuances managed by the management unit 240 in association with the priority indicated by the priority information included in the request information is the upper limit value set for the priority. If less than, it may be determined that the client device 20 is permitted to send the service request. Accordingly, different priorities can be set for service requests from the same client device 20 according to the type of service request. As a result, the client device 20 can transmit a service request of a higher priority type to the server device 30 in preference to a service request of a lower priority type.

The management unit 240 manages a second permission issuance count indicating the number of times the client device 20 having a higher priority for service provision than each priority is permitted to transmit a service request, in association with each of the plurality of priorities. You can When the priority of service provision to the client device 20 that is the transmission source of the request information is the first priority, the determination unit 220 determines the first priority managed by the management unit 240 in association with the first priority. even if the number of issued permits has reached the upper limit set for the first priority, it is managed by the management unit 240 in association with the second priority lower than the first priority. If the client device 20 is permitted to transmit a service request on the condition that the number of issued second permissions is less than a predetermined threshold that is less than the upper limit value set for the second priority. You can judge. As a result, while securing the minimum access ticket frame for service requests with low priority, if there are few service requests with low priority, the access ticket frame can be allocated to service requests with high priority. Thereby, the processing capacity of the server device 30 can be effectively used.

FIG. 3 shows the overall sequence of processing in the client device 20, server device 30 and management device 40. As shown in FIG. FIG. 3 shows the overall sequence when the client device 20a and the client device 20c access the server device 30. As shown in FIG.

The server device 30 transmits allowable access number information indicating the number of accesses that can respond to the service request from the client device 20 according to the current load amount of the server device 30 (S302). In the management device 40, when the allowable amount receiving unit 260 receives the allowable access number information, the management unit 240 determines the number of access tickets that can be issued by the management apparatus 40 based on the number of accesses indicated by the allowable access number information. number of possible tickets) is adjusted (S304). In S306 and S308, the client device 20c and the client device 20a transmit access ticket requests to the management device 40. FIG.

Here, it is assumed that the difference between the number of issuable tickets managed by the management unit 240 of the management device 40 and the number of tickets already issued to the client device 20 is one. In the management device 40, when the request receiving unit 210 receives access ticket requests from the client devices 20a and 20c, the transmitting unit 230 transmits access tickets only to the client device 20c (S310). The management unit 240 adds the access request from the client device 20a to the access ticket queue (S312).

Upon receiving the access ticket, the client device 20c generates a request for customer data including customer designation information (S320), and transmits the request to the server device 30 (S322). Upon receiving the request from the client device 20c, the server device 30 transmits a response including customer data of the customer specified by the customer specification information to the client device 20c (S324).

Upon receiving the response from the server device 30, the client device 20c transmits a return notification of the received access ticket to the management device 40 (S330). In the management device 40, upon receiving the return notification from the client device 20c, the end notification receiving unit 250 transmits the access ticket to the client device 20a (S332). Accordingly, the client device 20a transmits a request for customer data to the server device 30 in response to receiving the access ticket in S332 (S336).

After transmitting the access ticket return notification to the management device 40 in S330, the client device 20c performs processing using the customer data included in the response received in S324 (S334).

FIG. 4 shows an example of information managed by the management unit 240 in a table format. (A) of FIG. 4 is an example of a ticket management table managed by the management unit 240 . A ticket management table is stored in the storage unit 44 .

The ticket management table associates a ticket ID, priority, issued flag, issue date and time, issuer priority, and available flag. "Ticket ID" stores information for identifying an access ticket. "Priority" stores information indicating the priority of the access ticket. In this embodiment, priority 1 means a higher priority than priority 2.

Information indicating whether or not the access ticket has been transmitted to the client device 20 is stored in the “issued flag”. In FIG. 4 , TRUE indicates that the access ticket has been sent to the client device 20 and FALSE indicates that the access ticket has not been sent to the client device 20 .

Information indicating the date and time when the access ticket was issued is stored in the “date and time of issue”. The date and time when the access ticket was issued may be the date and time when the access ticket was transmitted to the client device 20 . The management unit 240 selects, from the ticket IDs stored in the ticket management table, ticket IDs whose elapsed time from the "date and time of issuance" exceeds a predetermined time, and accesses the selected ticket IDs. The ticket may be invalidated and an access ticket with a new ticket ID generated. In this case, the management unit 240 may newly generate the same number of access tickets as the invalidated access tickets. As a result, even if the access ticket is not returned from the client device 20 for a long time, it can be dealt with appropriately.

The "priority of issuer" stores information indicating the priority of service provision for an access ticket request. The priority of service provision for access ticket requests may be defined for each client device 20 . In addition to the access ticket associated with the priority 1 in the ticket management table, the access ticket associated with the priority 2 is also sent to the client device 20 that has transmitted the access ticket request with the service provision priority of 1. can issue access tickets for at least a portion of Therefore, priority 1 can be stored in the “issuer priority” of some access tickets of priority 2 access tickets.

The "usable flag" stores information indicating whether the access ticket is usable. In FIG. 4, TRUE indicates that access tickets are available and FALSE indicates that access tickets are not available. When the allowable amount receiving unit 260 receives the allowable number of accesses information from the management device 40, the managing unit 240 makes available the number of access tickets corresponding to the allowable number of accesses indicated by the allowable number of accesses information. For example, the management unit 240 sets the usable flag to TRUE with the allowable number of accesses as the upper limit.

(B) of FIG. 4 is an example of a priority table managed by the management unit 240 . A priority table is stored in the storage unit 44 .

The priority table associates client IDs with priorities. Information for identifying the client device 20 is stored in the “client ID”. “Priority” stores information indicating the priority of service provision to the client device 20 .

The determination unit 220 refers to the priority table to identify the priority associated with the client ID of the client device 20 that is the source of the access ticket request received by the request reception unit 210 . The determination unit 220 determines the priority of service provision for the access ticket request based on the specified priority and the priority indicated by the priority information included in the access ticket request.

For example, when the access ticket request does not include priority information, the determination unit 220 determines the priority associated with the client ID of the client device 20 that has sent the access ticket request as a service provisioning method for the access ticket request. Decide as a priority. When priority information is included in the access ticket request, the determination unit 220 determines the priority indicated by the priority information as the priority of service provision for the access ticket request. If the access ticket request includes priority information, the determination unit 220 associates the priority indicated by the priority information included in the access ticket request with the client ID of the client device 20 that is the source of the access ticket request. The product with priority may determine the priority of service provision.

The determining unit 220 refers to the access ticket management table, and if there is a ticket ID whose issued flag is FALS and whose usable flag is TRUE among the ticket IDs associated with the determined priority First, it determines that the client device 20 is permitted to transmit a service request. In this embodiment, "an access ticket identified by a ticket ID whose issued flag is FALS and whose usable flag is TRUE" may be referred to as an "unissued access ticket" or the like.

Here, the "priority of issuer" in (A) of FIG. 4 will be described. As described above, when there is an unissued access ticket corresponding to the priority of the service request, the determination unit 220 determines that the client device 20 that has transmitted the access ticket request is permitted to transmit the service request. Here, the management device 40 can transmit a part of the access tickets associated with the priority 2 in response to the access ticket request with the service provision priority 1. FIG. For example, the determination unit 220 refers to the ticket management table, and even if there is no unissued access ticket associated with priority 1, the unissued access ticket associated with priority 2 exists and the number of access tickets associated with issuer priority 1 is less than a predetermined threshold M, the transmission of the service request may be permitted. In this case, the management unit 240 selects one of the unissued access tickets associated with priority 2 in the ticket management table, stores TRUE as the issued flag, and sets the issued date and time to the current ticket. Stores the date and time, and stores 1 in the destination priority. Setting the issued flag, the date and time of issuance, and the priority of the issuer in the ticket management table in this manner may be referred to as "making the access ticket issued".

Note that when the number of access tickets associated with priority 2 in the ticket management table is N, it is assumed that M<N. That is, it is assumed that at least one or more (NM) access ticket frames are reserved for a service request with a priority of 2. FIG.

In FIG. 4B, "A", "B", "C", and "D" indicate the client device 20a, the client device 20b, the client device 20c, and the client device 20d, respectively. The priority of service provision to the client device 20c and the client device 20d is higher than the priority of service provision to the client device 20a and the client device 20b. By setting the priority in this way, even if a large number of access ticket requests are transmitted from the client device 20a or the client device 20b, the access ticket can be sent to the client device 20c or the client device 20d, which is a one-line terminal or a two-line terminal. can be sent. Therefore, the client device 20c and the client device 20d can download customer data from the server device 30 even when a large number of access ticket requests are sent from the client device 20a and the client device 20b all at once. As a result, it is possible to reduce the time the customer has to wait at the window.

(C) of FIG. 4 is an example of a queue managed by the management unit 240 . The queue may be stored in volatile memory of management device 40 . A queue may be stored in the storage unit 44 .

The queue associates a client ID, priority, issue destination priority, request priority, and issue order. Information for identifying the client device 20 is stored in the “client ID”. "Priority" stores information indicating the priority of an access ticket to be issued. As described above, the "priority" is based on the priority associated with the client ID of the client device 20 that sent the access ticket request and the priority indicated by the priority information included in the access ticket request. It is determined. "Priority" is an example of information indicating the priority of service provision to the client device 20 identified by the client ID.

The "priority of issuer" stores the priority associated with the client ID of the client device 20 that issued the access ticket request. The "request priority" stores the priority indicated by the priority information included in the access ticket request. The "issue order" stores the order to be selected as an access ticket issue target when a plurality of access ticket requests from the client device 20 having the same "priority" are stored in the queue. The management unit 240 determines the "issue order" based on the issue destination priority. For example, the management unit 240 may determine issue order 1 for an access ticket request with issuer priority 1 and issue order 2 for an access ticket request with issuer priority 2 . In this way, the management unit 240 may determine a higher issue order for a higher issue destination priority.

When the end notification receiving unit 250 receives the access ticket return information from the client device 20, the determination unit 220 refers to the “priority” of the queue to determine the access ticket ID included in the received access ticket return information. If there is a client ID associated with "priority" that matches the priority associated with , it is determined to transmit the access ticket to the client device 20 identified by the client ID. Note that if there are a plurality of client IDs associated with the same "priority" as the priority associated with the access ticket ID included in the access ticket return information, the determination unit 220, according to the "issue order", Select the client device 20 to which the access ticket is to be sent. Specifically, the determination unit 220 preferentially selects the client device 20 identified by the client ID associated with the higher “issue order” as the client device 20 to which the access ticket is to be transmitted. .

In this way, the server device 30 manages access tickets in a queue, so the client device 20 does not need to request retransmission of the access ticket. In addition, the client device 20 can quickly acquire the access ticket as soon as the access ticket is returned to the management device 40 .

FIG. 5 is a flowchart showing processing in the management device 40. As shown in FIG. This flowchart starts when the management device 40 receives data from the client device 20 or the server device 30 .

In S502, the processing unit 42 of the management device 40 determines the type of received data. If the type of received data is an access ticket request, the received data is provided to the request receiving unit 210 . In this case, in S504, the determination unit 220 determines the priority of service provision for the client device 20 that is the source of the received access ticket request. For example, the determination unit 220 determines the priority of service provision based on the priority stored in the priority table in association with the client ID of the client device 20 that has transmitted the access ticket request.

As described above, the client device 20 may transmit an access ticket request including priority information indicating priority to the management device 40 . If the access ticket request includes priority information, the determination unit 220 may determine the priority indicated by the priority information included in the access ticket request as the priority of service provision to the client device 20 . Further, the determination unit 220 determines based on the product of the priority included in the access ticket request and the priority stored in the priority table in association with the client ID of the client device 20 that has transmitted the access ticket request. , may determine the priority of service provision.

In S506, the determination unit 220 determines whether or not there is an unissued access ticket matching the priority. For example, the determining unit 220 determines whether or not there is an access ticket whose issued flag is FALS and whose usable flag is TRUE among the access tickets associated with the priority determined in S504. do. Note that, as described above, the determining unit 220 determines that there is an unissued access ticket associated with a lower priority than the service provision priority determined in S504, and a service request with a higher priority. If the number of access tickets issued to is less than the threshold M, it may be determined that there are unissued access tickets that match the priority.

If it is determined in S506 that there is an unissued access ticket that matches the priority, the management unit 240 selects one unissued access ticket (S508), and sets the access ticket to issued in S510.

In S<b>512 , the transmission unit 230 transmits the access ticket to the client device 20 . Specifically, the transmission unit 230 transmits an access ticket including the access ticket ID selected in S508.

If it is determined in S506 that there is no unissued access ticket that matches the priority, in S514 the client ID of the client device 20 that sent the access ticket request and the priority of service provision are added to the queue. do.

In S<b>502 , if the type of received data is an access ticket return notification, the received data is provided to the end notification receiving unit 250 . The access ticket return notification includes the ticket ID of the access ticket. The management unit 240 sets the access ticket identified by the ticket ID included in the access ticket return notification to unissued. For example, in the ticket management table, the management unit 240 stores FALS in the issued flag in association with the ticket ID, and stores a NULL value in the date and time of issue.

In S522, the determination unit 220 determines whether or not the queue managed by the management unit 240 stores a client ID corresponding to a priority that matches the priority of the returned access ticket. The “priority matching the priority of the returned access ticket” means, as described in S506 and the like, the priority of the returned access ticket in addition to the same priority as the priority of the returned access ticket. may contain a priority of less than For example, the determination unit 220 determines that an access ticket associated with a lower priority than the returned access ticket has an unissued access ticket and that the access ticket has been issued for a service request with a higher priority. If the number of access tickets is less than the threshold M, it may be determined that the queue contains client IDs corresponding to priorities that match the priorities of the returned access tickets.

If a client ID corresponding to a priority matching the priority of the returned access ticket is stored in the queue, then at S524 the returned access ticket is set to issued. In S526, the transmission unit 230 transmits the access ticket to the client device 20 identified by the client ID corresponding to the priority that matches the priority of the returned access ticket. As described above, when there are a plurality of client IDs corresponding to priorities matching the priority of the returned access ticket in the queue, the client device 20 to which the access ticket is to be transmitted is assigned the "issue order" in the queue. ”. If, in S522, the client ID corresponding to the priority matching the priority of the returned access ticket is not stored in the queue, the process of this flowchart ends.

In S<b>502 , if the type of received data is allowable access number information from the server device 30 , the allowable amount receiving section 260 is provided with the received data. In this case, in S530, the management unit 240 adjusts the number of access tickets whose “usable flag” is TRUE so as not to exceed the number of accesses indicated by the allowable access number information received by the allowable amount receiving unit 260.

FIG. 6 is a flowchart showing processing in the client device 20. As shown in FIG. This flowchart starts when an operation is performed in the client device 20 to transmit a service request to the server device 30 . For example, on the client device 20, it is started after the customer data download button displayed on the web browser is clicked.

At S<b>602 , the client device 20 transmits an access ticket request to the management device 40 . For example, a customer data download button displayed on the web browser running on the client device 20 is associated with a JavaScript (registered trademark) function that transmits an access ticket request to the management device 40 in response to clicking the button. The access ticket request may be transmitted to the management device 40 by executing the function when the download button is clicked. Alternatively, when the download button is clicked, a button for receiving an operation of transmitting an access ticket request to the management device 40 may be displayed, and the access ticket request may be transmitted to the management device 40 by clicking the button.

At S<b>604 , the client device 20 waits to receive an access ticket from the management device 40 . In S606, the client device 20 determines whether or not to use the received access ticket. For example, the client device 20 determines that the access ticket will be used if the download cancel button is not clicked during the period of waiting for reception of the access ticket in S604, and if the download cancel button is clicked: , it may be determined that the access ticket is not used.

When the client device 20 determines to use the access ticket received from the management device 40, it generates a request to the server device 30 in S608. For example, when the client device 20a accesses the server device 30 using the RPA function, the schedule information of the person in charge of public relations is collected, and a request is generated that includes customer designation information indicating the customer of the business partner that the person in charge of public relations will go to on the next day. . At S<b>610 , the request generated at S<b>608 is transmitted to the server device 30 . Note that the client device 20 does not transmit the access ticket to the server device 30 . The access ticket is information exchanged only between the client device 20 and the server device 30 in order to notify the client device 20 of permitting the client device 20 to transmit a service request to the server device 30. .

In S612, the client device 20 determines whether the response from the server device 30 is a normal response or an abnormal response. If the response is normal, in S614 the client device 20 stores the data provided by the server device 30 as a normal response in the non-volatile recording medium. Subsequently, in S<b>616 , the client device 20 returns the access ticket received in S<b>604 to the management device 40 . Specifically, the client device 20 transmits access ticket return information including the ticket ID received in S604 to the management device 40 . Subsequently, the client device 20 performs processing using the data provided in the response from the server device 30 in S618. For example, the client device 20a transmits the customer data included in the response received from the server device 30 to the e-mail address of the person in charge of public relations.

In S612, if the response from the server device 30 is an abnormal response, the client device 20 transmits access ticket return information to the management device 40 in S620. Further, even when it is determined in S606 that the access ticket received from the management device 40 is not to be used, the client device 20 transmits access ticket return information to the management device 40 in S620.

As described with reference to FIG. 6 and the like, the client device 20 waits to receive an access ticket transmitted from the management device 40, collects information for generating a service request, and generates a service request. . Since the number of accesses to the server device 30 is managed by the management device 40, the client device 20 can immediately receive a response from the server device 30 after sending the request. Therefore, it is possible to shorten the time to maintain the resource secured for the request. Moreover, even if the access ticket cannot be received for a long time and the request is canceled, compared to the method in which the client device 20 transmits the request to the server device 30 without obtaining the access ticket, the generation of the request is relatively difficult. No time or resources are wasted on Further, the client device 20 may secure resources for processing the response from the server device 30 at the stage of transmitting the request to the server device 30 after receiving the access ticket from the management device 40 . Therefore, it is possible to shorten the time for the client device 20 to maintain the resource required for the response.

In the above-described embodiment, when an access ticket request is received from the client device 20, if there is no unissued access ticket, the management unit 240 receives the access ticket request from the client device 20 that has sent the access ticket request. Permission to transmit access requests to client devices 20 is managed by adding client IDs to the queue. In addition to managing access request transmission permission using the queue, or instead of managing access request transmission permission using the queue, the management unit 240 allows the client device 20 to send a service request to the server device 30. Permission to transmit an access request may be managed by managing the waiting time before transmission. For example, in addition to or instead of S514 in FIG. The transmission unit 230 may transmit the access ticket including the waiting time to the client device 20 .

FIG. 7 shows a time chart for sending the access ticket including the waiting time to the client device 20 . In FIG. 7, at time t=0, the number of unissued access tickets is X, and at time t=0, Z access ticket requests are transmitted from the client device 20 to the management device 40 in a short period of time. indicate. Here, it is assumed that the number of access ticket requests managed in the queue by the management unit 240 is Y. Also assume that Z>X+Y.

The management unit 240 selects one access ticket from unissued access tickets for each of the X access ticket requests. Accordingly, the transmission unit 230 transmits access tickets corresponding to each of the X access ticket requests to the client device 20 . Also, the management unit 240 stores Y access ticket requests in a queue.

The management unit 240 transmits access tickets including waiting time T to the client device 20 for the remaining ZXY access ticket requests. When receiving an access ticket including a waiting time T, the client device 20 transmits a service request to the server device 30 on the condition that the waiting time T has passed after receiving the access ticket.

Here, the waiting time T may be T0 or longer. T0 may be, for example, the maximum time required for the server device 30 to respond to X+Y service requests. For example, if the time Tmax from when the server device 30 receives one service request to when it returns a response is determined, T0=(X+Y)Tmax. Note that the management unit 240 may set a different value for each client device 20 as the waiting time T. FIG. The management unit 240 may transmit an access ticket including a random waiting time T to the client device 20 . As a result, service requests transmitted from the client device 20 to the server device 30 can be distributed.

Note that the management unit 240 may preferentially store the client ID of the client device 20 that has transmitted an access ticket request with a higher service provision priority in the queue. For example, when an access ticket request is received from the client device 20c or the client device 20d, the client ID of the client device 20c or the client device 20d is stored in a queue, and the client device 20a or the client device 20b with lower priority accesses. An access ticket including a waiting time T may be sent when a ticket request is received.

According to the system 10 described above, simultaneous transmission of service requests from the client device 20 to the server device 30 can be suppressed. System 10 also allows priority to be assigned to client device 20 access ticket requests. Therefore, access to the server device 30 by the client device 20c, which is a one-line terminal, or the client device 20d, which is a two-line terminal or the like, to the server device 30, the client device 20a which collects customer data by the RPA function, and the customer data of the business trip destination of the next day. The service can be provided by separating the access from the collecting client device 20b. Therefore, without modifying the access control program in the server device 30, the client device 20c or the client device 20d can preferentially request the server device 30 to make a service request. Therefore, it is possible to reduce the possibility that the response to the service request from the client device 20c or the client device 20d will be delayed due to the service request from the client device 20a or the client device 20b.

In the system 10 described above, the management unit 240 manages issuance of access tickets using a ticket management table. The management unit 240 can manage the issuance of access tickets by various methods other than the method of managing the issuance of access tickets using a table. For example, the management unit 240 may manage issuance of access tickets using a linked list method. Alternatively, the management unit 240 may manage only the number of unissued access tickets. For example, the management unit 240 may decrement the number of unissued access tickets each time an access ticket is issued, and increment the number of unissued access tickets each time access ticket return information is received.

Also, in the system 10 , all of the client devices 20 are assumed to transmit access ticket requests to the management device 40 before transmitting service requests to the server device 30 . However, only some of the client devices 20 transmit the access ticket request to the management device 40 before transmitting the service request to the server device 30, and other client devices 20 out of the client devices 20 The service request may be sent to the server device 30 without sending the access ticket request to the management device 40 . For example, the client devices 20a and 20b transmit access ticket requests to the management device 40 before transmitting service requests to the server device 30, and the client devices 20c and 20d transmit access ticket requests to the management device 40. Alternatively, the service request may be sent to the server device 30 without doing so.

In the above description, a case where priority is mainly assigned to each client device 20 has been specifically described, but priority may not be assigned to the client device 20 . If no priority is assigned to the client device 20, and if the request information includes information indicating a predetermined authority to access the server device 30, the determination unit 220 determines whether the client device 20 that has transmitted the request information may be permitted to send a service request to the server device 30 . For example, priority information included in the access ticket request may be applied as the information indicating the authority to access the server device 30 . In this case, the determination unit 220 transmits an access ticket when an unissued access ticket matching the priority indicated by the priority information included in the access ticket request received by the request reception unit 210 exists in the ticket management table. Then you can judge.

Note that each unit of the management device 40 may be implemented by hardware, software, or both hardware and software. At least part of each unit of the management device 40 may be realized by a single server or may be realized by a plurality of servers. At least part of each part of the management device 40 may be implemented on a virtual machine or a cloud system. At least part of each unit of the management device 40 may be implemented by a personal computer or a mobile terminal. Examples of mobile terminals include mobile phones, smart phones, PDAs, tablets, notebook computers or laptop computers, wearable computers, and the like. The management device 40 may store information using a distributed ledger technology such as blockchain or a distributed network.

When at least part of the components that make up the management device 40 are implemented by software, the components implemented by the software define the operations of the components in an information processing device with a general configuration. It may be implemented by activating software or a program. The information processing apparatus having the above general configuration includes (i) a data processing apparatus having a processor such as a CPU and GPU, a ROM, a RAM, a communication interface, and the like; and (ii) a keyboard, pointing device, touch panel, camera, voice input Input devices such as devices, gesture input devices, various sensors, and GPS receivers, (iii) output devices such as display devices, audio output devices, and vibration devices, and (iv) storage devices such as memories, HDDs, and SSDs (external including a storage device).

In the information processing apparatus having the general configuration described above, the data processing apparatus or storage device may store the software or program described above. The software or program is executed by the processor to cause the information processing device to perform operations defined by the software or program. The above software or program may be stored in a non-transitory computer-readable recording medium. The above software or program may be a program for causing a computer to function as the management device 40 or a part thereof. The above software or program may be a program for causing a computer to execute information processing in the management device 40 or part thereof.

Although the present invention has been described above using the embodiments, the technical scope of the present invention is not limited to the scope described in the above embodiments. It is obvious to those skilled in the art that various modifications and improvements can be made to the above embodiments. In addition, matters described with respect to a specific embodiment can be applied to other embodiments as long as they are not technically inconsistent. It is clear from the description of the scope of claims that forms with such modifications or improvements can also be included in the technical scope of the present invention.

The execution order of each process such as actions, procedures, steps, and stages in the devices, systems, programs, and methods shown in the claims, the specification, and the drawings is particularly "before", "before etc., and it should be noted that they can be implemented in any order unless the output of the previous process is used in the subsequent process. Regarding the operation flow in the claims, the specification, and the drawings, even if the description is made using "first," "next," etc. for the sake of convenience, it means that it is essential to carry out in this order. not a thing

10 System 12 Network 20 Client device 30 Server device 40 Management device 42 Processing unit 44 Storage unit 48 Storage unit 210 Request reception unit 220 Judgment unit 230 Transmission unit 240 Management unit 250 End notification reception unit 260 Allowable amount reception unit

Claims (10)

a management unit that manages the number of client devices permitted to send service requests to the server device;
a request receiving unit that receives, from the client device, request information requesting permission to transmit the service request;
permitting the client device to transmit the service request on condition that the number managed by the management unit is less than a predetermined upper limit when the request reception unit receives the request information; a judgment unit that judges;
a transmission unit configured to transmit permission information to the client device when the determination unit determines that the client device is permitted to transmit the service request;
an end notification receiving unit configured to receive an end notification transmitted from the client device after the client device receives a response from the server device in response to the service request;
with
The management unit increases, in response to transmission of the permission information, a first permission issuance number indicating the number of permission issued to the client device to transmit the service request, and in response to reception of the termination notification, Decrease the number of issuance of the first permission;
The management unit further queues the identification information of the client device when the request reception unit receives the request information and the number managed by the management unit reaches the upper limit. add,
The transmitting unit transmits the permission information to the client device identified by the identification information included in the queue when the termination notification receiving unit receives the termination notification.
management device. a management unit that manages the number of client devices permitted to send service requests to the server device;
a request receiving unit that receives, from the client device, request information requesting permission to transmit the service request;
permitting the client device to transmit the service request on condition that the number managed by the management unit is less than a predetermined upper limit when the request reception unit receives the request information; a judgment unit that judges;
a transmission unit configured to transmit permission information to the client device when the determination unit determines that the client device is permitted to transmit the service request;
with
When the number managed by the management unit reaches the upper limit when the request reception unit receives the request information, the transmission unit causes the client device to transmit the service request to the server device. Send said authorization information including a waiting time before sending to
management device. further comprising an allowance reception unit for receiving information indicating an allowance for the server device to accept the service request from the server device,
The management device according to claim 1 or 2 , wherein the management unit adjusts the upper limit value according to the allowable amount. The upper limit value is defined for each of a plurality of priorities,
the management unit manages a first permission issue count indicating the number of permission issued to the client device to transmit the service request, in association with each of the plurality of priorities;
When the request receiving unit receives the request information, the determining unit determines that the first number of permission issues managed by the management unit in association with the priority of service provision to the client device 4. The management device according to any one of claims 1 to 3 , wherein the management device determines that the client device is permitted to transmit the service request when the priority is less than the upper limit value set for the priority. a management unit that manages the number of client devices permitted to send service requests to the server device;
a request receiving unit that receives, from the client device, request information requesting permission to transmit the service request;
permitting the client device to transmit the service request on condition that the number managed by the management unit is less than a predetermined upper limit when the request reception unit receives the request information; a judgment unit that judges;
a transmission unit configured to transmit permission information to the client device when the determination unit determines that the client device is permitted to transmit the service request;
with
The upper limit value is defined for each of a plurality of priorities,
the management unit manages a first permission issue count indicating the number of permission issued to the client device to transmit the service request, in association with each of the plurality of priorities;
When the request receiving unit receives the request information, the determining unit determines that the first number of permission issues managed by the management unit in association with the priority of service provision to the client device determining that the client device is permitted to transmit the service request if the priority is less than the upper limit value;
The management unit further manages the priorities for the plurality of client devices,
The determination unit determines that the first permission issuance number managed by the management unit in association with the priority of the client device that is the transmission source of the request information is determined for the priority. If the value is less than the upper limit, it is determined that the client device is permitted to transmit the service request.
management device. a management unit that manages the number of client devices permitted to send service requests to the server device;
a request receiving unit that receives, from the client device, request information requesting permission to transmit the service request;
permitting the client device to transmit the service request on condition that the number managed by the management unit is less than a predetermined upper limit when the request reception unit receives the request information; a judgment unit that judges;
a transmission unit configured to transmit permission information to the client device when the determination unit determines that the client device is permitted to transmit the service request;
with
The upper limit value is defined for each of a plurality of priorities,
the management unit manages a first permission issue count indicating the number of permission issued to the client device to transmit the service request, in association with each of the plurality of priorities;
When the request receiving unit receives the request information, the determining unit determines that the first number of permission issues managed by the management unit in association with the priority of service provision to the client device determining that the client device is permitted to transmit the service request if the priority is less than the upper limit value;
the request information transmitted from the client device includes priority information indicating a priority for the service request;
The determination unit determines whether the first permission issuance number managed by the management unit in association with the priority indicated by the priority information included in the request information is determined for the priority. is less than the upper limit value, it is determined that the client device is permitted to transmit the service request.
management device. a management unit that manages the number of client devices permitted to send service requests to the server device;
a request receiving unit that receives, from the client device, request information requesting permission to transmit the service request;
permitting the client device to transmit the service request on condition that the number managed by the management unit is less than a predetermined upper limit when the request reception unit receives the request information; a judgment unit that judges;
a transmission unit configured to transmit permission information to the client device when the determination unit determines that the client device is permitted to transmit the service request;
with
The upper limit value is defined for each of a plurality of priorities,
the management unit manages a first permission issue count indicating the number of permission issued to the client device to transmit the service request, in association with each of the plurality of priorities;
When the request receiving unit receives the request information, the determining unit determines that the first number of permission issues managed by the management unit in association with the priority of service provision to the client device determining that the client device is permitted to transmit the service request if the priority is less than the upper limit value;
The management unit further associates each of the plurality of priorities with a second permission indicating the number of times the client device having a higher priority for service provision than each priority is permitted to transmit the service request. manage the number of issuance,
When the priority of the service provision to the client device which is the transmission source of the request information is the first priority, the determination unit is managed by the management unit in association with the first priority. corresponds to a second priority lower than the first priority even if the number of the first permission issuances that are in use reaches the upper limit set for the first priority on the condition that the number of second permission issuances managed by the management unit is less than a predetermined threshold value less than the upper limit value determined for the second priority, determining that the client device is permitted to send the service request;
management device. a management device according to any one of claims 1 to 7 ;
A system comprising the client device. 9. The system according to claim 8 , wherein the client device waits for reception of the permission information transmitted from the management device, collects information for generating the service request, and generates the service request. A program for causing a computer to function as the management device according to any one of claims 1 to 7 .

Images