Registration management system, and registration management method

Abstract

To provide a registration management system capable of reliably managing the registration of prescribed matters even when the upper limit of the number of registrations is set.SOLUTION: A registration management system 1 includes: a storage unit that stores the upper limit of the number of registrations of prescribed matters; and a processing unit that is configured to receive a request for registration of prescribed matter from a respective user interface 40 and store the number of the received requests for registration, and receive a request for cancellation of the registration from the respective user interface 40, which has transmitted the requested registration and store the number of the received requests for cancellation, and when receiving a request for registration of prescribed matter, from any user interface 40 other than the user interface 40 that has transmitted the registration request, and when determining that the value obtained by subtracting the number of stored cancellation requests from the number of stored registration requests is equal to or less than the upper limit of the number of registrations, store the registration contents indicated in the received registration request.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a registration management system and a registration management method. [Background technology]

[0002] It has been common practice to accept registrations of specified information from a large number of applicants using a network such as the Internet, such as when reserving goods or services for purchase. In this case, when a large number of applicants make registration requests (reservations) at the same time, it is necessary to accurately grasp the order in which the registrations are accepted.

[0003] For example, Patent Document 1 discloses such a technology in which each server determines the synchronization status of reservation slots, and if the reservation information becomes unsynchronized, it allocates, for each reservation slot, some servers that cannot accept the request and some that can. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2010-152654 Summary of the Invention [Problem to be solved by the invention]

[0005] A typical situation where managing the order of acceptance becomes important is when the number of registrations that can be accepted is limited. In such a case, the representative methods for first-come-first-served management are row locking and optimistic exclusion.

[0006] However, the row locking method is prone to processing delays due to waiting for lock acquisition, and the optimistic exclusion method also causes rollbacks or retries due to optimistic exclusion errors at commit time, which also leads to processing delays.

[0007] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a registration management system and registration management method that can manage registrations of specified items without error even when an upper limit on the number of registrations is set. [Means for solving the problem]

[0008] One aspect of the present invention for solving the above problem is a registration management system that includes a storage device that stores an upper limit on the number of registrations for specified items, and a calculation device that executes the following processes: a registration numbering process that receives requests to register the specified items from each terminal and stores the number of registration requests received; a cancellation process that receives requests to cancel the registration from each terminal that sent the registration request and stores the number of cancellation requests received; and a determination process that, when a request to register the specified items is received from a terminal other than the terminal that sent the registration request, determines whether the value obtained by subtracting the number of cancellation requests stored from the number of registration requests stored is less than or equal to the upper limit on the number of registrations, and if it determines that the value obtained by subtracting the number of cancellation requests from the number of registration requests is less than or equal to the upper limit on the number of registrations, stores the registration content indicated by the received registration request. [Effects of the Invention]

[0009] According to the present invention, it is possible to manage registrations of predetermined items without error even when an upper limit is set on the number of registrations. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of a configuration of a registration management system according to an embodiment of the present invention. [Figure 2] FIG. 2 illustrates an example of a functional unit included in a server. [Figure 3] FIG. 10 is a diagram illustrating an example of reservation definition information acquired from a database. [Figure 4] FIG. 10 is a diagram illustrating an example of reservation management information acquired from a database. [Figure 5]FIG. 10 is a flow diagram illustrating an example of a registration management process. [Figure 6] FIG. 10 is a flow diagram illustrating details of a registration process. [Figure 7] FIG. 10 is a flowchart illustrating details of a registration cancellation process. [Figure 8] FIG. 10 is a flowchart illustrating details of a correction process. [Figure 9] FIG. 10 is a diagram illustrating a specific example of correction processing. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0012] 1 is a diagram showing an example of the configuration of a registration management system 1 according to this embodiment. The registration management system 1 includes a server 10, a database 20, one or more user interfaces 40, and a management device 30.

[0013] The server 10 is an information processing device that manages the registration and cancellation of purchase reservations for predetermined products. Specifically, the server 10 includes an arithmetic unit 91 such as a CPU (Central Processing Unit), a memory 92 such as a RAM (Random Access Memory) or a ROM (Read Only Memory), an auxiliary storage device 93 such as a HDD (Hard Disk Drive) or an SSD (Solid State Drive), an input interface 94 including a keyboard, a mouse, a touch panel, etc., an output interface 95 for displaying information on a screen such as a monitor (display), and a communication interface 96 including a NIC (Network Interface Card), a wireless communication module, a USB (Universal Serial Interface) module, a serial communication module, etc.

[0014] In this embodiment, the number of items that can be reserved is limited to one per reservation, and the total number of items (total of all reservations) is set to a predetermined upper limit.

[0015] The database 20 stores data necessary for managing product purchase reservations and their cancellations. The management device 30 transmits input data to the server 10 and displays data received from the server 10 on a predetermined screen. The database 20 and the management device 30 are equipped with the same hardware as the server 10.

[0016] The server 10, the database 20, and the management device 30 are managed by, for example, a product manager.

[0017] The user interface 40 is an information processing device used by customers (reservation seekers) who make reservations for purchasing products or cancel such reservations. The user interface 40 inputs predetermined data into the server 10, or displays data received from the server 10 on a predetermined screen. The user interface 40 has the same hardware as the server 10.

[0018] The server 10, database 20, management device 30, and user interface 40 are connected by a wired or wireless communication network 5 such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), or a dedicated line.

[0019] Here, the database 20 has the following functional units: a sequence memory unit 21 that stores reservation number sequences and cancellation number sequences described later; a reservation definition memory unit 22 that stores reservation definition information described later; and a reservation information memory unit 23 that stores reservation management information described later.

[0020] 2 is a diagram showing an example of the functional units included in the server 10. The server 10 has a reservation function unit 11, a cancellation function unit 12, and a correction function unit 13. The server 10 also stores a reservation number sequence 14 and a cancellation number sequence 15 received from the database 20 in the memory 92 or the auxiliary storage device 93. The server 10 also stores reservation definition information 300 and reservation management information 400 in the memory 92 or the auxiliary storage device 93.

[0021] The reservation number sequence 14 is the number of reservations that have been accepted so far. The value of the reservation number sequence 14 is incremented (1, 2, 3, ...) each time a reservation is accepted from a person who wishes to reserve a product. The reservation number sequence 14 is initially set to 0.

[0022] The cancellation number sequence 15 is the number of reservation cancellations that have been accepted. The value of the cancellation number sequence 15 is incremented (1, 2, 3, ...) each time a reservation cancellation is accepted from a reservation seeker who has reserved a product. The cancellation number sequence 15 is initially set to 0.

[0023] The reservation definition information 300 is information on the conditions relating to the reservation of each product (for example, the upper limit of the number of reservations for each product).

[0024] The reservation management information 400 is information in which information on reservation details and reservation cancellation details accepted from each user is accumulated.

[0025] In this embodiment, the server 10 uses a predetermined storage area (cache) in controlling the sequence for the database 20 (for example, in the case of PostgreSQL). That is, the reservation number sequence 14 and the cancellation number sequence 15 are stored in the cache on the memory 92 or auxiliary storage device 93 of the server 10. In this case, the server 10 stores (reserves) the numbering using the reservation number sequence 14 and the cancellation number sequence 15 in the cache prior to accepting a reservation or reservation cancellation request for the reservation management information 400. However, in this case, if the server 10 is restarted, a discrepancy will occur between the reservation number sequence 14 and the cancellation number sequence 15 in the cache and the reservation management information registered in the database.

[0026] (Reservation definition information) 3 is a diagram showing an example of reservation definition information 300 acquired from the database 20. The reservation definition information 300 has each piece of data: an item number 301 which is the ID of the data, a product code 302 which is the ID of each product, and a reservation upper limit number 303 which is the upper limit number of reservations for each product. The reservation definition information 300 is set by, for example, the management device 30.

[0027] (Reservation management information) 4 is a diagram showing an example of reservation management information 400 acquired from database 20. Reservation management information 400 is information that accumulates information on reservations and reservation cancellations from each user that has been received by server 10. Specifically, reservation management information 400 includes the following data: product code 401 for each product; reserver information 405, which is the ID of the user who requested the reservation or reservation cancellation; reservation status 404 for the product based on each request; reservation number 402 set for each user's request; and reservation cancellation number 403 set for each user's request. Reservation management information 400 can be set for each type of product.

[0028] The reservation number 402 is set to a value (reservation acceptance number) obtained by adding 1 to the reservation number sequence 14 when the reservation request is accepted. The reservation cancellation number 403 is set to a value (reservation cancellation acceptance number) obtained by adding 1 to the cancellation number sequence 15 when the reservation cancellation request is accepted. The status 404 is set to either "Reserved" indicating that the purchase reservation for the product has been accepted, "Reservation Cancelled" indicating that the cancellation of the purchase reservation for the product has been accepted, or "Reservation Not Concluded" indicating that the purchase reservation for the product has not been accepted.

[0029] Next, the reservation function unit 11 receives product purchase reservation requests from each user interface 40, and stores the number of received purchase reservation requests (reservation number sequence 14).

[0030] The cancellation function unit 12 receives requests to cancel product purchase reservations from each user interface 40 that has transmitted a purchase reservation request, and stores the number of cancellation requests received (cancellation number sequence 15).

[0031] Here, when the reservation function unit 11 receives a request to reserve a product purchase from a user interface 40 other than the user interface 40 that has previously sent a purchase reservation request, it determines whether the value obtained by subtracting the cancellation number sequence 15 from the reservation number sequence 14 is less than or equal to the maximum reservation number 303, and if it determines that the value obtained by subtracting the cancellation number sequence 15 from the reservation number sequence 14 is less than or equal to the maximum reservation number 303, it stores the reservation details indicated in the received purchase reservation request in the reservation management information 400.

[0032] The correction function unit 13 estimates whether the reservation number sequence 14 or cancellation number sequence 15 in the cache of the memory 92 is inconsistent with the number of registrations or the number of registration cancellations specified by the contents registered in the reservation management information 400, and if it estimates that there is no consistency, it performs consistency by adding new registration information and registration cancellation information to the reservation management information 400.

[0033] The functions of the registration management system 1 described above are realized by the hardware of each device in the registration management system 1, or by the computing device of each device reading and executing each program stored in memory or an auxiliary storage device. These programs are stored in a storage device such as a secondary storage device, nonvolatile semiconductor memory, hard disk drive, or SSD, or a recording medium readable by each device, such as an IC card, SD card, or DVD. All or part of each device may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, or the like, such as a virtual server provided by a cloud system. All or part of the functions provided by these devices may be realized by services provided by the cloud system via an API (Application Programming Interface), for example. Next, the processing performed by the registration management system 1 will be described.

[0034] 5 is a flow diagram illustrating an example of the registration management process. The registration management process is started after the server 10 is started, for example.

[0035] The server 10 determines (s11) whether or not a purchase reservation request or a purchase reservation cancellation request for a product has been received from each user interface 40. The purchase reservation request or purchase reservation cancellation request includes, for example, the user ID and product code.

[0036] If a request to reserve a product for purchase is received (s11: Reserve), the server 10 executes the process of s12; if a request to cancel a product purchase reservation is received (s11: Cancel), the server 10 executes the process of s13; if neither a purchase reservation request nor a purchase reservation cancellation request is received (s11: Other), the server 10 executes the process of s14.

[0037] In s12, the server 10 executes registration processing s12, which is processing of a purchase reservation for the user (hereinafter referred to as the reservation seeker) of the user interface 40 who has transmitted the purchase reservation request, based on the received purchase reservation request. After that, processing of s14 is performed.

[0038] In s13, the server 10 executes a registration cancellation process s13, which is a process for canceling a purchase reservation for the user of the user interface 40 who has sent the purchase reservation cancellation request (hereinafter referred to as the person who wishes to cancel the reservation), based on the received purchase reservation cancellation request. After that, the process of s14 is carried out.

[0039] In s14, the server 10 estimates whether the contents of the cache (reservation number sequence 14, cancellation number sequence 15) are inconsistent with the contents of the reservation management information 400. For example, the server 10 determines whether the server 10 has just been restarted by checking the execution result of a predetermined process monitoring program.

[0040] If the contents of the cache are not consistent with the contents of the reservation management information 400 (s14: YES), the server 10 executes the process of s15, and if the contents of the cache are consistent with the contents of the reservation management information 400 (s14: NO), the server 10 repeats the process from s11 onwards.

[0041] In s15, the server 10 executes a correction process s15 to resolve any discrepancies between the reservation number sequence 14 and cancellation number sequence 15 stored in the cache of the server 10 and the information registered in the reservation management information 400. After that, the processes from s11 onwards are repeated. Each process will be described in detail below.

[0042] <Registration process> 6 is a flow diagram illustrating the details of the registration process s12. The reservation function unit 11 acquires the current reservation number sequence 14 (e.g., 5 or 6) for the product indicated in the purchase reservation request (target product), adds 1 to the acquired reservation number sequence 14, sets the value obtained by adding 1 to the reservation requester's reservation reception number (e.g., 6 or 7), and updates the reservation number sequence 14 with the set value (s121). The reservation function unit 11 also acquires the current cancellation number sequence 15 (e.g., 1) for the target product (s122). Furthermore, the reservation function unit 11 acquires the maximum reservation number 303 (e.g., 5) from the reservation definition information 300 for the target product (s123).

[0043] The reservation function unit 11 determines whether or not the reservation seeker can make a reservation for the purchase of the target product (s124). Specifically, the reservation function unit 11 determines whether or not the value obtained by subtracting the cancellation number sequence 15 acquired in s122 from the reservation reception number of the reservation seeker set in s121 is equal to or less than the reservation upper limit number 303 acquired in s123.

[0044] If it is determined that the reservation seeker can make a reservation to purchase the target product (s124: YES), the reservation function unit 11 executes the process of s125, and if it is determined that the reservation seeker cannot make a reservation to purchase the target product (s124: NO), the reservation function unit 11 executes the process of s126.

[0045] In s125, the reservation function unit 11 registers information relating to the reservation made by the reservation seeker in the reservation management information 400. Specifically, the reservation function unit 11 sets a new record in the reservation management information 400, sets the code of the target product in the product code 401 of the set record, registers the set reservation reception number (for example, 6) in the reservation number 402, sets the status 404 to "reserved," and sets the name of the reservation seeker, etc. in the reservation seeker information, etc. 405. This completes the registration process s12.

[0046] In s126, the reservation function unit 11 updates the reservation cancellation reception number 15. Specifically, the reservation function unit 11 adds 1 to the cancellation number sequence 15 acquired in s122.

[0047] Then, the reservation function unit 11 registers information indicating that the reservation by the reservation seeker is not possible (not established) in the reservation management information 400 (s127). Specifically, the reservation function unit 11 registers the updated value (for example, 2) of the cancellation number sequence 15 in the reservation number 402 of the reservation management information 400, sets the status 404 to "reservation not established", and sets the name, etc. of the reservation seeker in the reservation person information, etc. 405. This completes the registration process s12.

[0048] <Registration cancellation process> 7 is a flow diagram illustrating details of the registration cancellation process s13. The cancellation function unit 12 acquires the cancellation number sequence 15 (e.g., 2) for the product (target product) indicated in the purchase cancellation reservation request, sets the value obtained by adding 1 to the acquired cancellation number sequence 15 as the reservation cancellation acceptance number (e.g., 3), and updates the cancellation number sequence 15 with the set value (s131).

[0049] Then, the cancellation function unit 12 registers the information regarding the reservation cancellation set in s121 in the reservation management information 400 (s132). Specifically, the cancellation function unit 12 sets the reservation cancellation reception number set above in the reservation cancellation number 403 of the record related to the person wishing to cancel the reservation and the target product in the reservation management information 400, and sets "reservation canceled" in the status 404. This completes the registration cancellation process s13.

[0050] <Correction processing> 8 is a flow diagram illustrating the details of the correction process s15. The correction process s15 is executed for each product registered in the reservation management information 400.

[0051] First, the correction function unit 13 acquires the reservation number sequence 14, i.e., the current reservation acceptance number (s141). The correction function unit 13 also acquires the cancellation number sequence 15, i.e., the current reservation cancellation acceptance number (s142).

[0052] On the other hand, the correction function unit 13 acquires the maximum value of the reservation number 402 in the reservation management information 400 (s143). Also, the correction function unit 13 acquires the maximum value of the reservation cancellation number 403 in the reservation management information 400 (s144).

[0053] The correction function unit 13 determines whether the current reservation number is greater than the maximum reservation number 402 in the reservation management information 400, or whether the current reservation cancellation number is greater than the maximum reservation cancellation number 403 in the reservation management information 400 (s145).

[0054] If any of the above conditions is met (s145: YES), the correction function unit 13 executes the process of s146, and if none of the above conditions is met (s145: NO), the correction process s14 ends.

[0055] In s146, the correction function unit 13 determines whether the current reservation number is greater than the maximum value of the reservation number 402 in the reservation management information 400. If the current reservation number is greater than the maximum value of the reservation number 402 in the reservation management information 400 (s146: YES), the correction function unit 13 executes the process of s148, and if the current reservation number is not greater than the maximum value of the reservation number 402 in the reservation management information 400 (s146: NO), the correction function unit 13 executes the process of s147.

[0056] In s147, the correction function unit 13 updates the reservation number sequence 14 by incrementing the value by 1. After that, the process of s148 is performed.

[0057] In s148, the correction function unit 13 determines whether the current reservation cancellation number is greater than the maximum reservation cancellation number 403 in the reservation management information 400. If the current reservation cancellation number is greater than the maximum reservation cancellation number 403 in the reservation management information 400 (s148: YES), the correction function unit 13 executes the process of s150, and if the current reservation cancellation number is not greater than the maximum reservation cancellation number 403 in the reservation management information 400 (s148: NO), the correction function unit 13 executes the process of s149.

[0058] In s149, the correction function unit 13 updates the value of the cancellation number sequence 15 by incrementing it by 1. After that, the process of s150 is performed.

[0059] In s150, the correction function unit 13 corrects the reservation management number 400. Specifically, the correction function unit 13 creates a new record in the reservation management information 400, sets the reservation number 402 of that record to the next value (a value that is 1 larger) of the reservation number of the immediately preceding record (the current reservation number), sets the reservation cancellation number 403 to the next value (a value that is 1 larger) of the reservation cancellation number of the immediately preceding record (the current reservation cancellation number), and sets the status 404 to "correction". After that, the processing from s141 onwards is repeated.

[0060] 9 is a diagram illustrating a specific example of the correction process s15. It is assumed that immediately before the execution of the correction process s15, a reservation number 901 and a reservation cancellation number 902 have been set in advance in the cache of the server 10 prior to the data registration in the reservation management information 400. That is, it is assumed that the value of the reservation number sequence 14 stored in the cache of the memory 92 of the server 10 is 20, the value of the cancellation number sequence 15 is 10, the maximum value of the reservation number 401 registered in the reservation management information 400 in the database 20 is 8 (reference numeral 903), and the maximum value of the reservation cancellation number 402 registered in the reservation management information 400 is 3 (reference numeral 904).

[0061] In this case, correction process s15 adds dummy records to the reservation management information 400 until the maximum value of the reservation number 501 becomes "20," which is the value of the reservation number sequence 14 (reference numeral 905), and sets a dummy reservation reception number to the reservation number 401 of that record (reference numeral 906). Also, dummy reservation cancellation reception numbers are set to each added dummy record until the maximum value of the reservation cancellation number 402 becomes "10," which is the value of the cancellation number sequence 15 (reference numeral 907). Furthermore, since the number of currently valid reservations in the reservation management information 400 is "8" - "3" = "5," the cancellation number sequence 15 is changed to "20" - "5" = "15," which is the value of the reservation number sequence 14 (reference numeral 908). Then, corresponding to this updated value of the cancellation number sequence 15, further dummy reservation cancellation reception numbers are set to the reservation cancellation number 402 of each of the dummy records until the value reaches "15" (reference numeral 909).

[0062] In this way, the values ​​indicated by the reservation number sequence 14 and the cancellation number sequence 15 are made to match the maximum reservation reception number and the maximum reservation cancellation reception number indicated by the reservation management information 400, respectively.

[0063] As described above, the registration management system 1 of this embodiment receives product purchase reservation requests (purchase reservation requests) from each user interface 40, stores the number of received purchase reservation requests (reservation number sequence 14), and also receives purchase reservation cancellation requests (purchase reservation cancellation requests) from each user interface 40 that sent the purchase reservation request, and stores the number of received purchase reservation cancellation requests (cancellation number sequence 15).When the registration management system 1 receives a purchase reservation request from a user interface 40 other than the user interface 40 that sent the purchase reservation cancellation request, and determines that the value obtained by subtracting the cancellation number sequence 15 from the reservation number sequence 14 is equal to or less than the maximum reservation number 303, it stores the purchase reservation details indicated in the received purchase reservation request in the reservation management information 400.

[0064] That is, the registration management system 1 can appropriately accept and register reservation applicants so as not to exceed the upper limit of product purchase reservations by managing the reservation number sequence 14 and the cancellation number sequence 15. Processing delays that tend to occur with row locking and optimistic exclusion methods are also unlikely to occur.

[0065] In this way, according to the registration management system 1 of this embodiment, management of registrations to predetermined items can be performed without error even when an upper limit is set on the number of registrations.

[0066] In addition, if the value obtained by subtracting the cancellation number sequence 15 from the reservation number sequence 14 exceeds the maximum reservation number 303, the registration management system 1 of this embodiment registers information indicating that the registration content indicated by the received purchase reservation request is invalid (reservation not completed) in the status 404 of the reservation management information 400.

[0067] This allows a reservation candidate to register and manage the fact that he or she was unable to make a reservation due to the registration limit.

[0068] In addition, the registration management system 1 of this embodiment stores the reservation number sequence 14 and registers the registration details indicated by the purchase reservation request in the reservation management information 400 ("Reserved"), and stores the cancellation number sequence 15 and registers the cancellation details of the registration indicated by the purchase reservation cancellation request in the reservation management information 400 ("Reservation Cancelled").

[0069] This allows detailed results of each user's reservation requests to be registered and managed.

[0070] Furthermore, when the registration management system 1 of this embodiment estimates that the reservation number sequence 14 or cancellation number sequence 15 in the cache of memory 92 does not match the number of registrations (maximum value of reservation number 402) or the number of registration cancellations (maximum value of reservation cancellation number 403) respectively specified by the contents registered in the reservation management information 400 (for example, when the server 10 is restarted), it adds new registration information and registration cancellation information (dummy records) to the reservation management information 400, thereby matching the reservation number sequence 14 and cancellation number sequence 15 in the cache with the number of registrations (maximum value of reservation number 402) and the number of registration cancellations (maximum value of reservation cancellation number 403) respectively specified by the reservation management information 400.

[0071] This allows the sequence data in the cache in the registration management system 1 to be corrected to match the contents of the database, and reservation registration and cancellation can be managed correctly.

[0072] Furthermore, the registration management system 1 of this embodiment performs the above-mentioned matching by further changing the reservation cancellation number 403 in the cache.

[0073] This allows a correction to be made so that the cancellation number sequence 15 in the cache in the registration management system 1 matches the reservation cancellation information in the database, thereby enabling reservation cancellation to be managed correctly.

[0074] The above description of the embodiments is intended to facilitate understanding of the present invention, and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit thereof, and the present invention includes equivalents thereof.

[0075] For example, part of the hardware provided in each device of this embodiment may be provided in another device.

[0076] Furthermore, each program of each device may be provided in another device, a program may consist of multiple programs, or multiple programs may be integrated into one program.

[0077] Furthermore, the registration management system 1 of this embodiment is designed to manage reservations for the purchase of specific products and their cancellations, but it can also manage any registration and cancellation of any event (for example, a product or service).

[0078] In addition, in this embodiment, the timing for performing the correction process s15 is immediately after the server 10 is restarted, but the correction process s15 may be performed at other times. That is, the correction process s15 may be performed at other times when the sequence data in the cache and the data in the reservation management information 400 are inconsistent. For example, the correction process s15 may be performed when time has passed since the server 10 was restarted, or when an inconsistency occurs due to a program malfunction. [Explanation of symbols]

[0079] 1 registration management system, 10 server, 20 database, 30 management device, 40 user interface

Claims

1. a storage device that stores an upper limit of the number of registrations for a predetermined item; and a registration numbering process for receiving a request for registration of the predetermined items from each terminal and storing the number of the received registration requests; a cancellation process for receiving a request for canceling the registration from each terminal that has transmitted the request for registration and storing the number of the cancellation requests received; a computing device that executes a determination process in which, when a request for registration of the predetermined items is received from a terminal other than the terminal that transmitted the request for registration, it determines whether a value obtained by subtracting the number of stored cancellation requests from the number of registration requests is equal to or less than the upper limit of the number of registrations, and, when it determines that the value obtained by subtracting the number of cancellation requests from the number of registration requests is equal to or less than the upper limit of the number of registrations, it stores the registration content indicated in the received request for registration. A registration management system comprising:

2. When the calculation device determines in the determination process that the value obtained by subtracting the number of cancellation requests from the number of registration requests exceeds the upper limit of the number of registrations, the calculation device stores information indicating that the registration content indicated by the received registration request is invalid. The registration management system of claim 1 .

3. The computing device In the registration numbering process, the number of the received registration requests is stored and the registration contents indicated by the registration requests are registered in a predetermined database; In the cancellation process, the number of the cancellation requests received is stored, and the cancellation details of the registration indicated by the cancellation requests are registered in the database. The registration management system of claim 1 .

4. The computing device In the registration numbering process, the number of the received registration requests is stored in a predetermined storage area; In the cancellation process, the number of the received cancellation requests is stored in the storage area; estimate whether the number of registration requests or the number of cancellation requests in the storage area is inconsistent with the number of registrations or the number of cancellations of registrations, respectively, specified by the content registered in the specified database, and if it is estimated that the number of registration requests or the number of cancellation requests is inconsistent with the number of registrations or the number of cancellations of registrations, respectively, specified by the content registered in the specified database, perform a correction process to make the number of registration requests and the number of cancellation requests in the storage area consistent with the number of registrations and the number of cancellations of registrations, respectively, specified by the database, by adding new registration information and new cancellation information to the specified database; The registration management system of claim 3 .

5. The computing device In the correction process, new registration information and deregistration information are added to the predetermined database and the deregistration requests are changed in the storage area, thereby aligning the number of registration requests and the number of deregistration requests in the storage area with the number of registrations and the number of deregistrations specified by the database, respectively. The registration management system of claim 4.

6. A registration management method for an information processing device including a storage device that stores an upper limit of the number of registrations for a predetermined item, and a calculation device, the calculation device comprising: a registration numbering process for receiving a request for registration of the predetermined items from each terminal and storing the number of the received registration requests; a cancellation process for receiving a request for canceling the registration from each terminal that has transmitted the request for registration and storing the number of the cancellation requests received; When a request for registration of the predetermined items is received from a terminal other than the terminal that transmitted the request for registration, the device determines whether or not a value obtained by subtracting the number of stored cancellation requests from the number of stored registration requests is equal to or less than the upper limit of the number of registrations, and when it determines that the value obtained by subtracting the number of cancellation requests from the number of registration requests is equal to or less than the upper limit of the number of registrations, the device executes a determination process of storing the registration contents indicated by the received request for registration. Registration management methods.

7. When the calculation device determines in the determination process that the value obtained by subtracting the number of cancellation requests from the number of registration requests exceeds the upper limit of the number of registrations, the calculation device stores information indicating that the registration content indicated by the received registration request is invalid. The registration management method according to claim 6.

8. The computing device In the registration numbering process, the number of the received registration requests is stored and the registration contents indicated by the registration requests are registered in a predetermined database; In the cancellation process, the number of the cancellation requests received is stored, and the cancellation details of the registration indicated by the cancellation requests are registered in the database. The registration management method according to claim 6.

9. The computing device In the registration numbering process, the number of the received registration requests is stored in a predetermined storage area; In the cancellation process, the number of the received cancellation requests is stored in the storage area; estimate whether the number of registration requests or the number of cancellation requests in the storage area is inconsistent with the number of registrations or the number of cancellations of registrations, respectively, specified by the content registered in the specified database, and if it is estimated that the number of registration requests or the number of cancellation requests is inconsistent with the number of registrations or the number of cancellations of registrations, respectively, specified by the content registered in the specified database, perform a correction process to make the number of registration requests and the number of cancellation requests in the storage area consistent with the number of registrations and the number of cancellations of registrations, respectively, specified by the database, by adding new registration information and new cancellation information to the specified database; The registration management method according to claim 8.

10. The computing device In the correction process, new registration information and deregistration information are added to the predetermined database and the deregistration requests are changed in the storage area, thereby aligning the number of registration requests and the number of deregistration requests in the storage area with the number of registrations and the number of deregistrations specified by the database, respectively. The registration management method of claim 9.

Images