JP2020052469A - Management device, system and program - Google Patents

Abstract

To suppress the number of service requests arrived at a server device from a client device to an appropriate value according to the capability of the server device.SOLUTION: A management device comprises: a management unit which manages the number permitted for a client device which transmits service requests to a server device; a request reception unit which receives request information which requests transmission permission of the service request, from the client device; a determination unit which permits the client device to transmit the service request, under the conditions that the number managed by the management unit is less than a predetermined upper limit value, when the request reception unit receives the request information; and a transmission unit which transmits permission information to the client device, when the determination unit permits the client device to transmit the service request.SELECTED DRAWING: Figure 3

Description

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

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

  It is desired that the number of service requests arriving at the server device from the client device be suppressed to an appropriate number according to the capability of the server device.

  In a first aspect of the present invention, a management device is provided. The management device 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 includes, for example, a request receiving unit that receives, from a client device, request information for requesting permission to transmit a service request. 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. Is provided. The above management device 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 is permitted to the client device.

  The management unit may manage information indicating whether or not each of the plurality of pieces of permission information has been transmitted to the client device. The determining unit determines, based on the information managed by the management unit, that the client device is allowed to transmit the service request when the plurality of pieces of permission information include permission information that has not been transmitted to the client device. May be.

  The management device may include an end notification receiving unit that receives 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. The management unit increases the 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 increases the first permission issuance in response to receiving the end notification. The number may be reduced.

  The management unit may further add the identification information of the client device to the queue when the number managed by the management unit has reached the upper limit when the request reception unit receives the request information. The transmission 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.

  The transmitting unit, when the request receiving unit receives the request information, when the number managed by the managing unit has reached the upper limit, waits until the client device transmits the service request to the server device. The permission information may be transmitted.

  The management device may include an allowance receiving unit that receives, from the server device, information indicating an allowance amount at which the server device can accept the service request. The management unit may adjust the upper limit according to the allowable amount.

  An upper limit may be set for each of the plurality of priorities. The management unit may manage the first number of permitted issuances indicating the number of client devices permitted 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 a first permission issue number managed by the management unit in association with the priority of service provision to the client device with respect to the priority. If it is less than the upper limit, it may be determined that the client device is allowed to transmit the service request.

  The management unit may further manage 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 request information transmission source client device is less than an upper limit value defined for the priority. It may be determined that the client device is permitted to transmit the service request.

  The request information transmitted from the client device may include priority information indicating the priority for the service request. The determining unit determines that the first number of permitted issuances managed by the management unit in association with the priority indicated by the priority information included in the request information is less than an upper limit value defined for the priority. In this case, it may be determined that the client device is allowed to transmit the service request.

  The management unit manages a second number of permitted issuances indicating the number of times that a client device having a higher priority for service provision is permitted to transmit a service request in association with each of the plurality of priorities. Good. When the priority of service provision to the client device that transmitted the request information is the first priority, the determination unit issues the first permission issuance managed by the management unit in association with the first priority. Even if the number has reached the upper limit value defined for the first priority, the number managed by the management unit in association with the second priority lower than the first priority It may be determined that the client device is permitted to transmit the service request on condition that the number of permitted issuances of No. 2 is less than a predetermined threshold value less than the upper limit value defined for the second priority.

  In a second aspect of the present 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 present invention, a program is provided. The above program may be a program for causing a computer to function as the above management device. The above program may be a program for causing a computer to execute information processing in the above management device. A computer readable medium storing the above program may be provided. The computer readable medium may be a non-transitory computer readable medium. The computer readable medium may be a computer readable recording medium.

  The above summary of the present invention does not list all of the necessary features of the present invention. Further, a sub-combination of these feature groups can also be an invention.

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

  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. In addition, not all combinations of the features described in the embodiments are necessarily essential to the solution of the invention. In the drawings, the same or similar portions are denoted by the same reference numerals, and duplicate description may be omitted.

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

  The server device 30, the client device 20, and the management device 40 are connected via the network 12. Network 12 may include any communication lines. For example, the network 12 may include at least one of a dedicated line, a public line, and a local line. The public line may include at least one of the Internet, a mobile communication line, a telephone line, 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 a service to the client device 20 in response to a service request from the client device 20. The server device 30 performs, for example, the 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 or an application server.

  As an example of a usage form 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 the financial institution. For example, the server device 30 stores transaction data performed in the past between the financial institution and the customer, financial account information owned by the customer, customer credit information, and the like as customer data.

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

  The client device 20a automatically collects customer data from the server device 30 by using a robotic process automation (RPA) function. The client device 20a automatically downloads customer data used in store operations from the server device 30. For example, the client device 20a downloads, from the server device 30, customer data of a business partner to which the liaison officer goes out the next day with reference to the schedule data of the liaison representative on the next day. The client device 20a transmits the customer data downloaded from the server device 30 to the e-mail address of the person in charge of public relations.

  The client device 20b is a terminal used by the person in charge of public relations. Using the client device 20b, the person in charge of public relations can refer to customer data that has arrived at the e-mail address of the person in charge of public relations. Further, the person in charge of public relations can operate the client device 20b to access the server device 30 and download customer data directly from the server device 30.

  The client device 20c is a teller terminal operated by a teller who performs teller operations at a store of a financial institution. The client device 20c is a so-called one-line terminal. The client device 20d is a rear terminal operated by a rear operator who performs the rear job of the window operation. The client device 20d is a so-called two-wire terminal. For example, when the client device 20c and the client device 20d receive a new account opening request from the customer, the client device 20c and the client device 20d download a list of account information that the customer has opened from the server device 30. As a result, the contact person or the back business person can confirm that the customer has not already opened an account of the same kind.

  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 can be processed by the server device 30 is exceeded, and the server device 30 May not be available. For example, in a plurality of stores, when the client device 20a tries to download the customer data by simultaneously accessing the server device 30 at the end time of the banking business, the server device 30 may not be able to provide the client device 20 with a service. is there.

  The management device 40 suppresses transmission of a large amount of service requests from the client device 20 to the server device 30. Specifically, the management device 40 manages an access ticket that permits the client device 20 to access the server device 30. For example, the management device 40 manages the number of access tickets according to the processing capability that can be used in the server device 30 to respond to the service request from the client device 20.

  The client device 20 requests an access ticket from the management device 40 before transmitting a request for transmitting customer data to the server device 30. The management device 40 transmits the access ticket 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 the access ticket managed by the management device 40.

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

  According to the system 10, the number of service requests coming from the client device 20 to the server device 30 can be suppressed to an appropriate number according to the processing capacity of the server device 30. This can prevent the server device 30 from being unable to provide a service to the client device 20 due to an overload.

  FIG. 2 is a block diagram illustrating a functional configuration of the management device 40. 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 client devices 20 that are permitted 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 transmitted from the client device 20 to the server device 30 in the present embodiment is an example of a service request.

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

  When the request receiving unit 210 receives the request information, the determining unit 220 transmits the service request to the client device 20 on condition that the number managed by the management unit 240 is less than a predetermined upper limit. Is determined to be permitted. The transmission unit 230 transmits permission information to the client device 20 when the determination unit 220 determines that transmission of the service request to the client device 20 is permitted. For example, the management unit 240 manages information indicating whether each of the plurality of pieces of permission information has been transmitted to the client device 20. The determining unit 220 transmits a service request to the client device 20 based on the information managed by the management unit 240, when there is permission information not transmitted to the client device 20 among the plurality of permission information. You may decide to allow it. Thereby, it is possible to suppress a large amount of service requests from being transmitted from the client device 20 to the server device 30 at the same time. The access ticket transmitted from the management device 40 to the client device 20 in the present embodiment is an example of permission information.

  The termination notification receiving unit 250 receives a termination 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 the present embodiment is an example of an end notification. In response to the transmission of the permission information, the management unit 240 increases the first number of permitted issuances indicating the number of times that the client device 20 has been permitted to transmit the service request, and in response to receiving the end notification, the first permission issuance number. Reduce the number of permits issued.

  The management unit 240 further adds the identification information of the client device 20 to the queue when the number managed by the management unit 240 has reached the upper limit when the request reception unit 210 receives the request information. . When the termination notification receiving unit 250 receives the termination notification, the transmission unit 230 transmits the permission information to the client device 20 identified by the identification information included in the queue. Thereby, as soon as the access ticket is returned, the transmission of the service request to another client device 20 can be permitted.

  When the request receiving unit 210 receives the request information and the number managed by the management unit 240 has reached the upper limit, the client unit 20 transmits the service request to the server device 30 when the request receiving unit 210 receives the request information. The permission information including the waiting time until may be transmitted. The permission information including the waiting time will be described with reference to FIG.

  Allowable amount receiving section 260 receives, from server device 30, information indicating an allowable amount by which server device 30 can accept a service request. The permissible access number information of the present 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 the service request according to the allowable amount received from the server device 30. Thereby, the allowable number of accesses that permits the client device 20 to access the server device 30 can be dynamically adjusted according to the current load of the server device 30. For example, the allowable number of accesses can be reduced when the load on the server device 30 increases, and the allowable number of accesses can be increased when the load on the server device 30 decreases. Thereby, when the resources of the server device 30 are tight, a service request coming from the client device 20 to the server device 30 can be suppressed.

  An upper limit may be set for each of the plurality of priorities. The management unit 240 may manage the first permission issuance number indicating the number of the client devices 20 permitted 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 determining unit 220 determines that the first permission issuance number managed by the management unit 240 in association with the priority of the service provision to the client device 20 corresponds to the priority. May be determined to permit the client device 20 to transmit the service request.

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

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

  The management unit 240 manages the second number of permitted issuances indicating the number of permitted transmissions of service requests to the client device 20 having a higher priority for service provision than the respective priorities in association with each of the plurality of priorities. May do it. When the priority of service provision to the client device 20 that is the source of the request information is the first priority, the determination unit 220 manages the first priority managed by the management unit 240 in association with the first priority. Even if the number of permitted issuances reaches the upper limit defined for the first priority, the management unit 240 manages the number of permitted issuances 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 second permitted number of issued licenses is less than a predetermined threshold value less than an upper limit value defined for the second priority, You may decide. By this means, while securing a minimum access ticket frame for a low priority service request, if there are few low priority service requests, the access ticket frame can be allocated to a high priority service request. Thereby, the processing capacity of the server device 30 can be effectively used.

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

  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, based on the access number indicated by the allowable access number information, sets the number of access tickets that the management device 40 can issue (issue The upper limit of the number of possible tickets) is adjusted (S304). In S306 and S308, the client device 20c and the client device 20a transmit an access ticket request to the management device 40.

  Here, it is assumed that the difference between the number of issueable tickets managed by the management unit 240 of the management device 40 and the number of tickets issued to the client device 20 is 1. In the management device 40, when the request reception unit 210 receives the access ticket request from the client device 20a and the client device 20c, the transmission unit 230 transmits the access ticket 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 the customer data of the customer designated by the customer designation 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 an access ticket to the client device 20a (S332). Thereby, the client device 20a transmits a request for customer data to the server device 30 in response to the reception of 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 a process using the customer data included in the response received in S324 (S334).

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

  The ticket management table associates a ticket ID, a priority, an issued flag, an issue date and time, an issue destination priority, and an available flag. The “ticket ID” stores information for identifying an access ticket. The “priority” stores information indicating the priority of the access ticket. In the present embodiment, priority 1 means that priority is higher than priority 2.

  The “issued flag” stores information indicating whether the access ticket has been transmitted to the client device 20. In FIG. 4, TRUE indicates that the access ticket has been transmitted to the client device 20, and FALSE indicates that the access ticket has not been transmitted to the client device 20.

  The “issuance date and time” stores information indicating the date and time when the access ticket was issued. 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 among the ticket IDs stored in the ticket management table, a ticket ID whose elapsed time from the “issuing date and time” has exceeded a predetermined time, and accesses the selected ticket ID. The ticket may be invalidated to generate an access ticket with a new ticket ID. In this case, the management unit 240 may newly generate the same number of access tickets as the revoked access tickets. Thereby, even when the access ticket is not returned from the client device 20 for a long time, it is possible to appropriately cope with it.

  The “issuance priority” stores information indicating the priority of service provision for an access ticket request. The priority of service provision for an access ticket request may be determined for each client device 20. Note that, in addition to the access ticket associated with the priority 1 in the ticket management table, the access ticket associated with the priority 2 in the client device 20 that has transmitted the access ticket request with the priority 1 of the service provision. At least a part of the access ticket can be issued. Therefore, priority 1 can be stored in the “issue destination priority” of some access tickets among the priority 2 access tickets.

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

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

  The priority table associates a client ID with a priority. In the “client ID”, information for identifying the client device 20 is stored. In the “priority”, information indicating the priority of service provision to the client device 20 is stored.

  The determining unit 220 specifies the priority associated with the client ID of the client device 20 that has transmitted the access ticket request received by the request receiving unit 210 with reference to the priority table. The determining unit 220 determines the service providing priority 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 priority information is not included in the access ticket request, the determining unit 220 determines the priority associated with the client ID of the client device 20 that has transmitted the access ticket request by using the service provision for the access ticket request. Determined as priority. When the priority information is included in the access ticket request, the determining unit 220 determines the priority indicated by the priority information as the priority of service provision for the access ticket request. When the priority information is included in the access ticket request, 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 has transmitted the access ticket request. The priority of service provision may be determined based on the product of the priority and the product.

  The determining unit 220 refers to the access ticket management table, and when the issued flag is FALS and the available flag is TRUE, among the ticket IDs associated with the determined priorities, Then, it is determined that the client device 20 is permitted to transmit the service request. In the present embodiment, the “access ticket whose issued flag is FALS and the usable flag is identified by the TRUE ticket ID” may be referred to as “unissued access ticket” or the like.

  Here, “issue destination priority” in FIG. 4A 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 transmission of the service request is permitted to the client device 20 that has transmitted the access ticket request. Here, the management device 40 can transmit some access tickets among the access tickets associated with the priority 2 with respect to the access ticket request with the priority 1 of the service provision. For example, the determination unit 220 refers to the ticket management table, and even if there is no unissued access ticket associated with the priority 1, the unissued access ticket associated with the priority 2 Exists and the number of access tickets associated with the 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 date and time are stored, and 1 is stored as the issuer priority. As described above, setting the issued flag, the issued date and time, and the destination priority in the ticket management table may be referred to as “making an access ticket already issued” or the like.

  If the number of access tickets associated with the 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 (N−M) access ticket frames are reserved for the service request of priority 2.

  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 manner, even when a large number of access ticket requests are transmitted from the client device 20a or the client device 20b, the access ticket is issued to the client device 20c or the client device 20d which is a one-wire terminal or a two-wire terminal. Can be transmitted. Therefore, the client devices 20c and 20d can download the customer data from the server device 30 even when a large amount of access ticket requests are transmitted from the client devices 20a and 20b at the same time. As a result, it is possible to reduce the time for keeping the customer waiting at the counter.

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

  The queue associates the client ID, priority, issue destination priority, request priority, and issue order. In the “client ID”, information for identifying the client device 20 is stored. "Priority" stores information indicating the priority of the 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 has transmitted 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 “issuance priority” stores the priority associated with the client ID of the client device 20 that has issued the access ticket request. The “request priority” stores the priority indicated by the priority information included in the access ticket request. The “issuance order” stores the order to be selected as an access ticket issuance 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 “issuing order” based on the issuer priority. For example, the management unit 240 may determine the issuance order 1 for an access ticket request of the issuer priority 1 and determine the issuance order 2 for an access ticket request of the issuer priority 2. As described above, the management unit 240 may determine a higher issue order as the issue destination priority is higher.

  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 and accesses 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 that the access ticket is to be transmitted to the client device 20 identified by the client ID. When 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 determines The client device 20 to which the access ticket is to be transmitted is selected. Specifically, the determination unit 220 selects the client device 20 identified by the client ID associated with the higher “issuing order” with higher priority as the client device 20 to which the access ticket is transmitted. .

  As described above, since the server device 30 manages the access ticket in the queue, the client device 20 does not need to request retransmission of the access ticket. Further, 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. This flowchart is started 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 the received data. When the type of the 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 to the client device 20 that has transmitted the received access ticket request. For example, the determination unit 220 determines the service providing priority 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 the access ticket request including the priority information indicating the priority to the management device 40. When the priority information is included in the access ticket request, the determination unit 220 may determine the priority indicated by the priority information included in the access ticket request as the service provision priority for the client device 20. Further, the determination unit 220 is 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. Alternatively, the priority of service provision may be determined.

  In S506, the determination unit 220 determines whether there is an unissued access ticket matching the priority. For example, the determining unit 220 determines whether there is an access ticket whose issued flag is FALS and whose available flag is TRUE among the access tickets associated with the priority determined in S504. I do. Note that, as described above, the determination unit 220 determines that there is an unissued access ticket in the access ticket associated with a lower priority than the service provision priority determined in S504, and that the 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 is an unissued access ticket matching the priority.

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

  In S512, the transmitting unit 230 transmits the access ticket to the client device 20. Specifically, the transmitting unit 230 transmits the access ticket including the access ticket ID selected in S508.

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

  In S502, when the type of the received data is the 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 as unissued. For example, the management unit 240 stores FALS in the issued flag in association with the ticket ID in the ticket management table, and stores a NULL value in the issued date and time.

  In S522, the determination unit 220 determines whether or not the client ID corresponding to the priority matching the priority of the returned access ticket is stored in the queue managed by the management unit 240. The “priority matching the priority of the returned access ticket” refers to the priority of the returned access ticket in addition to the priority of the returned access ticket, as described in S506 and the like. May include less than a priority. For example, the determination unit 220 determines that the access ticket associated with a lower priority than the returned access ticket has an unissued access ticket, and has been issued in response to a higher priority service request. When the number of access tickets is less than the threshold M, it may be determined that the client ID corresponding to the priority matching the priority of the returned access ticket is stored in the queue.

  If the client ID corresponding to the priority that matches the priority of the returned access ticket is stored in the queue, the returned access ticket is set to issued in S524. In S526, the transmitting 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 in the queue corresponding to the priority that matches the priority of the returned access ticket, the client device 20 to which the access ticket is to be transmitted is placed in the “issuance order” of the queue. Selected according to If it is determined in S522 that the client ID corresponding to the priority that matches the priority of the returned access ticket is not stored in the queue, the processing of this flowchart ends.

  In S502, when the type of the received data is information on the number of permitted accesses from the server device 30, the received data is provided to the permitted amount receiving unit 260. In this case, in S530, the management unit 240 adjusts the number of access tickets whose “available flag” is TRUE so that the number of accesses does not 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. This flowchart is started when an operation of transmitting a service request to the server device 30 is performed in the client device 20. For example, in the client device 20, the process is started after a customer data download button displayed on the web browser is clicked.

  In S602, the client device 20 transmits an access ticket request to the management device 40. For example, a Javascript (registered trademark) function that performs an operation of transmitting an access ticket request to the management device 40 in response to a click of the button is associated with a customer data download button displayed on a web browser operating on the client device 20. The access ticket request may be transmitted to the management device 40 by executing the function by clicking the download button. In addition, a button for accepting the operation of transmitting the access ticket request to the management device 40 is displayed in response to the click of the download button, and the access ticket request may be transmitted to the management device 40 by clicking the button.

  In S604, the client device 20 waits for reception of an access ticket from the management device 40. In S606, the client device 20 determines whether to use the received access ticket. For example, the client device 20 determines that the access ticket is to be used if the download cancel button is not clicked within the period of waiting for the access ticket to be received in S604, and the client device 20 determines whether the download cancel button is clicked. It may be determined that the access ticket is not used.

  When determining that the access ticket received from the management device 40 is to be used, the client device 20 generates a request to the server device 30 in S608. For example, when the client device 20a accesses the server device 30 by the RPA function, the schedule information of the liaison officer is collected, and the request is generated including the customer designation information indicating the customer of the business partner that the liaison officer will go to the next day. . In S610, the request generated in S608 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 that the client device 20 is allowed 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 a normal response, in S614, the client device 20 stores the data provided from the server device 30 by the normal response in a nonvolatile recording medium. Subsequently, in S616, the client device 20 returns the access ticket received in S604 to the management device 40. Specifically, the client device 20 transmits the access ticket return information including the ticket ID received in S604 to the management device 40. Subsequently, in S618, the client device 20 performs processing using the data provided in the response from the server device 30. 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 liaison.

  If the response from the server device 30 is an abnormal response in S612, the client device 20 transmits the access ticket return information to the management device 40 in S620. Also, in S606, when it is determined that the access ticket received from the management device 40 is not used, the client device 20 transmits the 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 for reception of the 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 transmitting the request. Therefore, the time for maintaining the resources secured for the request can be reduced. Further, even if the request is canceled because the access ticket cannot be received for a long time, the request generation is not performed as compared with the method in which the client device 20 transmits the request to the server device 30 without acquiring the access ticket. No time or resources are wasted. Further, after transmitting the request to the server device 30 after receiving the access ticket from the management device 40, the client device 20 may secure resources for processing a response from the server device 30. Therefore, it is possible to reduce the time for the client device 20 to maintain the resources required for the response.

  In the embodiment described above, when the access ticket request is received from the client device 20 and there is no unissued access ticket, the management unit 240 By adding the client ID to the queue, transmission permission of an access request to the client device 20 is managed. The management unit 240 allows the client device 20 to send a service request to the server device 30 in addition to managing the transmission permission of the access request by the queue or instead of managing the transmission permission of the access request by the queue. The transmission permission of the access request may be managed by managing the waiting time until the transmission. For example, in addition to or instead of S514 in FIG. 5, the management unit 240 determines a waiting time until the client device 20 transmits a service request to the server device 30, and the management unit 240 determines the waiting time. 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 transmitting an access ticket including a waiting time to the client device 20. 7, the number of unissued access tickets is X at time t = 0, and Z access ticket requests are transmitted from the client device 20 to the management device 40 in a short time at time t = 0. Is shown. Here, it is assumed that the number of access ticket requests managed by the management unit 240 in the queue is Y. It is also assumed that Z> X + Y.

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

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

  Here, the waiting time T may be equal to or longer than T0. T0 may be, for example, the maximum time required for the server device 30 to respond to X + Y service requests. For example, when a time Tmax from when one service request is received to when a response is returned in the server device 30 is defined, T0 = (X + Y) Tmax may be satisfied. The management unit 240 may set a different value for each client device 20 as the waiting time T. The management unit 240 may transmit an access ticket including a random waiting time T to the client device 20. Thereby, the service request transmitted from the client device 20 to the server device 30 can be distributed.

  The management unit 240 may store the client ID of the client device 20 that has transmitted the access ticket request with a higher service providing priority in the queue with higher priority. 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 IDs of the client devices 20a and 20b having lower priority are accessed. When a ticket request is received, an access ticket including the waiting time T may be transmitted.

  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. Further, according to the system 10, a priority can be assigned to the access ticket request of the client device 20. Therefore, access to the server device 30 by the client device 20c which is a one-wire terminal or the client device 20d which is a two-wire terminal, the client device 20a for collecting customer data by the RPA function, and the The service can be provided separately from the access from the client device 20b to be collected. Therefore, the client device 20c or the client device 20d can preferentially make the server device 30 make a service request without modifying the access control program in the server device 30. Therefore, it is possible to reduce the possibility that a response delay occurs in response to a service request from the client device 20c or the client device 20d due to a service request from the client device 20a or 20b.

  In the system 10 described above, the management unit 240 manages issuance of access tickets in the ticket management table. The management unit 240 can manage the issuance of the access ticket by various methods other than the method of managing the issuance of the access ticket by the table. For example, the management unit 240 may manage the issuance of the access ticket by a linked list method. Further, 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 every time an access ticket is issued, and increment the number of unissued access tickets every time access ticket return information is received.

  Further, in the system 10, all the client devices 20 transmit the access ticket request to the management device 40 before transmitting the service request 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 the other client devices 20 of the client devices 20 The service request may be transmitted to the server device 30 without transmitting the access ticket request to the management device 40. For example, the client device 20a and the client device 20b transmit an access ticket request to the management device 40 before transmitting a service request to the server device 30, and the client devices 20c and 20d transmit the access ticket request to the management device 40. The service request may be transmitted to the server device 30 without performing.

  In the above description, mainly the case where the priority is assigned to each of the client devices 20 has been specifically described. However, the priority may not be assigned to the client device 20. If no priority is assigned to the client device 20, the determination unit 220 determines that the request information includes information indicating a predetermined authority to access the server device 30, and the client device 20 that transmitted the request information Then, the transmission of the service request to the server device 30 may be permitted. For example, the 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 determining unit 220 transmits the 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 receiving unit 210 exists in the ticket management table. You may decide.

  Each unit of the management device 40 may be realized by hardware, may be realized by software, or may be realized by hardware and software. At least a 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 a part of each unit of the management device 40 may be realized on a virtual machine or a cloud system. At least a part of each unit of the management device 40 may be realized by a personal computer or a mobile terminal. Examples of the mobile terminal include a mobile phone, a smartphone, a PDA, a tablet, a notebook computer or a laptop computer, and a wearable computer. The management device 40 may store information using a distributed ledger technology such as a blockchain or a distributed network.

  When at least a part of the components configuring the management device 40 is realized by software, the component realized by the software defines an operation related to the component in an information processing apparatus having a general configuration. It may be realized by starting 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 a GPU, a ROM, a RAM, a communication interface, and the like; 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 devices). Storage device).

  In the information processing device having the general configuration, the data processing device or the storage device may store the software or the program. The above software or program is executed by the processor to cause the information processing device to execute an operation 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 a part thereof.

  As described above, the present invention has been described using the embodiments, but the technical scope of the present invention is not limited to the scope described in the above embodiments. It is apparent to those skilled in the art that various changes or improvements can be made to the above embodiment. In addition, matters described in a specific embodiment can be applied to other embodiments within a technically consistent range. It is apparent from the description of the appended claims that embodiments with such changes or improvements can be included in the technical scope of the present invention.

  The execution order of each processing such as operation, procedure, step, and stage in the apparatus, system, program, and method shown in the claims, the description, and the drawings is particularly “before”, “before”. It should be noted that they can be realized in any order as long as the output of the previous process is not used in the subsequent process. Even if the operation flow in the claims, the specification, and the drawings is described using “first,” “second,” or the like for convenience, it means that it is essential to perform the operation in this order. Not something.

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 (12)

A management unit that manages the number of client devices permitted to transmit service requests to the server device;
From the client device, a request receiving unit that receives request information requesting permission to transmit the service request,
When the request receiving unit receives the request information, on condition that the number managed by the management unit is less than a predetermined upper limit, the client device is allowed to transmit the service request. A judgment unit for judging,
A transmitting unit that transmits permission information to the client device when the determining unit determines that the client device is permitted to transmit the service request. An end notification receiving unit that receives 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,
The management unit, in response to the transmission of the permission information, increases the first permission issuance number indicating the number of the client device is permitted to transmit the service request, in response to the reception of the end notification, The management device according to claim 1, wherein the number of first permission issuances is reduced. The management unit may further include, when the request reception unit receives the request information, when the number managed by the management unit has reached the upper limit, the identification information of the client device is queued. Add
The transmission unit according to claim 2, wherein the transmission 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. The transmitting unit, when the request receiving unit receives the request information, when the number managed by the management unit has reached the upper limit, the client device the service request the server device The management device according to any one of claims 1 to 3, wherein the permission information includes a waiting time until the permission information is transmitted. The server apparatus further includes an allowance receiving unit that receives information indicating an allowance at which the server apparatus can accept the service request,
The management device according to claim 1, wherein the management unit adjusts the upper limit according to the allowable amount. The upper limit is determined for each of a plurality of priorities,
The management unit manages a first permission issue number indicating a number of the client devices permitted to transmit the service request in association with each of the plurality of priorities,
The determination unit, when the request receiving unit receives the request information, the first permission issuance number managed by the management unit in association with the priority of service provision to the client device, the The management device according to claim 1, wherein the management device determines that the client device is allowed to transmit the service request when the priority is less than the upper limit value defined for the priority. The management unit further manages the priority for a plurality of the client devices,
The determination unit is configured such that the first permission issuance number managed by the management unit in association with the priority of the client device from which the request information is transmitted is determined for the priority. The management device according to claim 6, wherein when the value is less than the upper limit, the management device determines that the client device is allowed to transmit the service request. The request information transmitted from the client device includes priority information indicating a priority for the service request,
The determination unit may determine the first number of permitted issuances managed by the management unit in association with the priority indicated by the priority information included in the request information, for the priority. 7. The management apparatus according to claim 6, wherein the management apparatus determines that the client apparatus is allowed to transmit the service request when the service request is less than the upper limit. The management unit further associates each of the plurality of priorities with a second permission indicating a number of transmissions of the service request to the client device having a higher priority for providing the service than each priority. Manage the number of issues,
When the priority of providing the service to the client device as the transmission source of the request information is a first priority, the determination unit is managed by the management unit in association with the first priority. Even if the number of first permitted issuances has reached the upper limit value defined for the first priority, it corresponds to a second priority lower than 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 defined for the second priority. The management device according to claim 6, wherein the management device determines that transmission of the service request is permitted to the client device. A management device according to any one of claims 1 to 9,
A system comprising the client device. The system according to claim 10, 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 9.

Images