Free facility management system

Abstract

To efficiently manage a free parking lot.SOLUTION: A free parking lot management system 100 includes: an external camera 10 for imaging a vehicle C to enter / leave parking positions 3a-3d in a free parking lot 2; and computers 20, 40 for processing imaging information captured by the external camera 10. The computers 20, 40 perform: generating vehicle identification information to identify the vehicle C and entering time information and leaving time information of the vehicle C associated with the vehicle identification information, based on the imaging information captured by the external camera 10; comparing a parking time of the vehicle corresponding to the vehicle identification information with a predetermined management time; generating award information when a parking time of the corresponding vehicle C is less than a predetermined management time; and executing processing to give an award point corresponding to the award information to a user corresponding to the vehicle C.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a technique for managing facilities that can be used free of charge, such as free parking lots. [Background technology]

[0002] Various techniques for managing paid parking lots have been proposed (see, for example, Patent Document 1). The technology described in Patent Document 1 calculates fee data based on image information of a vehicle entering and leaving an unmanned paid parking lot, and charges the vehicle based on the time from when the vehicle entered the parking lot until when the vehicle left the parking lot. In addition, restaurants have introduced POS systems that can handle orders, accounting, tallying, and customer management. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Utility Model Registration No. 3222136 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the concept of charging does not exist in free parking lots, so even if people park for long periods of time in a nuisance manner, causing congestion, it is difficult to punish them.

[0005] Furthermore, for example, at facilities such as convenience stores, parking is free, but it may not always be advisable to impose separate charges or fines for people who do not use the facility or who park for long periods of time that exceed the facility's usage.As such, unlike paid parking lots, free parking lots still have issues to be resolved in order to alleviate congestion and manage them more efficiently. In addition, it is difficult for restaurants to charge customers for the time they occupy a seat or the amount of time they spend inside the restaurant separately from the cost of the food and drink.

[0006] The present invention has been made in view of the above-mentioned problems, and has as its object to provide a free parking lot management system that can alleviate congestion in free parking lots. [Means for solving the problem]

[0007] In order to solve the above problem, a free parking lot management system according to one embodiment of the present invention comprises an imaging unit that captures images of vehicles entering and leaving a parking space in a free parking lot, and an information processing unit to which the image information captured by the imaging unit is input. The information processing unit generates vehicle identification information that identifies the vehicle based on the image information, and entry time information and exit time information for the vehicle linked to the vehicle identification information, and compares the parking time of the vehicle corresponding to the vehicle identification information with a predetermined management time, and if the parking time of the vehicle is less than the predetermined management time, generates reward information and grants a benefit according to the reward information to the user corresponding to the vehicle.

[0008] According to one embodiment of the free parking management system of the present invention, if a vehicle's parking time is less than a predetermined management time, reward information is generated, and the user corresponding to the vehicle can be given a benefit according to the reward information. Therefore, instead of imposing separate charges or penalties for long-term parking, it is possible to provide benefits to users who, for example, finish their business and leave the parking lot early. This encourages users of vehicles to leave the free parking lot early, thereby alleviating congestion in the free parking lot and improving operating efficiency. This allows for more efficient management of the free parking lot. Furthermore, when the free facility management system according to the present invention is applied to a restaurant, it is possible to give benefits to customers who finish eating early and leave the restaurant, thereby increasing the turnover rate. [Effects of the Invention]

[0009] As described above, the present invention contributes to alleviating congestion in free parking lots and the like, and enables more efficient management of free parking lots and the like. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a schematic plan view showing a convenience store equipped with a free parking lot management system according to one embodiment of the present invention. [Figure 2] 10 is a flowchart of a free parking lot management process executed by the free parking lot management system of FIG. [Figure 3] 3 is a diagram illustrating an embodiment of the free parking lot management process of FIG. 2. FIG. [Figure 4] This is a schematic plan view showing a self-service restaurant equipped with a "short-time use reward system for restaurants" according to one embodiment of the present invention, and this figure includes example images of the "standard product consumption time table" and "reward management table" used in this system. [Figure 5] This is an example of the image of the "List of User-Selected Products" table data handled by the "Short-Term Use Reward System for Restaurants" shown in Figure 4. [Figure 6] This is an image of the structure (records, fields) of the database data table used in the "Short-time use reward system for restaurants" shown in Figure 4. [Figure 7] This is a diagram explaining the roles of the "cashier" and "management database" in the "short-time use reward system for restaurants" of Figure 4 {in the situation of checking "reward points"}. [Figure 8] This is a diagram explaining the roles of the "checkout cash register" and "management database" in the "short-time use reward system for restaurants" of Figure 4, {when paying with "reward points"}. [Figure 9] This is a diagram explaining the roles of the "handover duty machine" and "management database" in the {product handover scene} in the "short-time use reward system for restaurants" of Figure 4. [Figure 10] This is a diagram explaining the roles of the "coupon issuing machine" and "management database" in the "short-time use reward system for restaurants" of Figure 4 {in the situation of awarding "reward points"}. [Figure 11]In the "Short-time use reward system for restaurants" shown in Figure 4, the "management database" uses the "standard time for total consumption of products and drinks" and the "time spent in the restaurant" to calculate the "number of reward points awarded this time." This is an example of an image of a "flat conversion table" used by the "management database" to calculate the "number of reward points awarded this time." DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the drawings are schematic. Therefore, it should be noted that the relationship between thickness and planar dimensions, ratios, etc. differ from the actual ones, and the drawings also include portions where the relationship and ratio of dimensions differ from each other. Furthermore, the embodiments described below are intended to exemplify devices and methods for embodying the technical ideas of the present invention, and the technical ideas of the present invention do not limit the materials, shapes, structures, arrangements, etc. of the components to the embodiments described below.

[0012] As shown in Fig. 1, this embodiment is an example in which a free parking lot management system 100 according to the present invention is applied to the management of a free parking lot 2 at a convenience store 1 as a facility. This convenience store 1 has a free parking lot 2 on its premises. Parking positions 3a to 3d for four vehicles are set in the free parking lot 2.

[0013] As shown in the figure, the free parking lot management system 100 of this embodiment is configured with an external camera 10, an internal camera 30, and a computer 20 installed on the side of a convenience store 1, a management computer 40 installed at a management headquarters, and a database server 50. The management computer 40 is connected to the database server 50 so that information can be sent and received between them.

[0014] The external camera 10 is installed within the premises so as to be able to capture images of vehicles entering and leaving the free parking lot 2. The internal camera 20 is installed near the cash register counter of the convenience store 1 so as to be able to capture images of customers at the cash register counter. Computer 20 is installed within the premises of convenience store 1, for example in the back yard. Computer 20 is connected to management computer 40 so as to be able to exchange necessary information with it. Image information acquired by external camera 10 and internal camera 20 is input to computer 20 on the premises side.

[0015] The computer 20, as an information processing unit, executes a subordinate program for free parking lot management processing. In this embodiment, the computer 20 performs image processing based on image information of vehicles entering and leaving the free parking lot 2, acquired by the external camera 10, to generate vehicle identification information for identifying the vehicle parked in any of the parking positions 3a to 3d and person identification information for identifying the person in the vehicle, and then executes processing to transmit the identification information together with the time of entry (entry time information) to the management computer 40.

[0016] Computer 20 also performs image processing to generate personal identification information that can identify the person who used the cash register counter based on the image information of the user acquired by internal camera 30, and then executes a process to transmit the personal identification information together with the time of use to management computer 40 as usage information.

[0017] Furthermore, the computer 20 similarly performs image processing to generate vehicle identification information that identifies a vehicle that has left any of the parking positions 3a to 3d, as acquired by the external camera 10, and then executes a process of transmitting the vehicle identification information to the management computer 40 together with the time of departure (exit time information).

[0018] In this embodiment, the management computer 40 serves as an information processing unit and executes a main program for managing free parking lots. When the main program for managing free parking lots is executed, the management computer 40 proceeds to step S1 as shown in Fig. 2, and monitors whether entry time information has been acquired by the facility computer 20. If entry time information is acquired, the process proceeds to step S2; otherwise, the process waits in step S1. In step S2, primary identification information is generated, and the process proceeds to step S3. In this embodiment, the primary identification information is a combination of vehicle identification information that identifies vehicle C at the time of entry into the free parking lot 2 (entry time information) and person identification information that identifies the person riding in the vehicle.

[0019] In step S3, it is monitored whether facility usage information has been acquired by the facility-side computer 20. If usage information has been acquired, the process proceeds to step S4, and if not, the process waits in step S3. In step S4, additional identification information is generated based on the usage information, and the process proceeds to step S5. In this embodiment, the additional identification information is a set of purchase information such as the purchase amount at convenience store 1, the time of payment (usage time information), and personal identification information that identifies the person who made the payment. The purchase information is passed to management computer 40 from the system that manages the register.

[0020] In step S5, it is monitored whether or not the departure time information has been acquired by the facility-side computer 20. If the departure time information has been acquired, the process proceeds to step S6, otherwise the process waits in step S5. In step S6, secondary identification information is generated, and the process proceeds to step S7. In this embodiment, the secondary identification information is a set of vehicle identification information that identifies the vehicle at the time of exiting the free parking lot 2 (exit time information) and person identification information that identifies the person riding in the vehicle. Note that the linking of the vehicle to the person riding in the vehicle can be performed by referring to the primary identification information.

[0021] In step S7, it is determined whether the reward condition is satisfied. Here, the reward condition in this embodiment is determined as follows: based on the vehicle identification information and the entry time information and exit time information linked to the vehicle identification information, the parking time of the vehicle corresponding to the vehicle identification information is compared with a predetermined management time, and if the parking time of the vehicle corresponding to the vehicle identification information is less than the predetermined management time, it is determined that the reward condition is satisfied.

[0022] If the reward condition is met, the management computer 40 proceeds to step S8 to perform a predetermined reward point granting process, otherwise the management computer 40 returns to step S8. As the predetermined reward point granting process, various methods can be set as described below, as long as they grant benefits according to the reward information.

[0023] For example, the system determines the weighting of the time value associated with early departure, and awards reward points according to that value to the user corresponding to the vehicle identification information. A good user can receive services according to the reward points at the convenience store 1 or at facilities such as convenience stores in the group.

[0024] Furthermore, if a free parking lot is provided adjacent to a facility, as in this embodiment, the additional identification information can be further used in the award point granting process. For example, the award information can be generated only when a user has used the facility, based on whether the user has used the facility. Furthermore, the more the user uses the facility, the more award points can be granted.

[0025] Next, an embodiment of the free parking lot management process will be described in more detail with reference to FIG. When the free parking lot management process is executed in the free parking lot management system 100, the external camera 10 in the convenience store 1 constantly captures images of the parking lot 2 (step A1 shown in FIG. 3). When computer 20 of convenience store 1 confirms through image processing from the image information captured by external camera 10 that vehicle C that entered the parking lot has been parked in one of the multiple parking positions 3a to 3d, computer 20 generates vehicle identification information using the number obtained from the license plate of vehicle C as a main key or primary key (in the database), and transmits the parking position number and the time of entry as primary identification information linked to the entry information to management computer 40. Management computer 40 records the primary identification information in the database of database server 50 (step A2 shown in FIG. 3).

[0026] In this embodiment, the computer 20 of the convenience store 1 further generates personal identification information for each person (one or more) who gets out of the vehicle C from the face and clothing of the person or people captured by the external camera 10, and transmits this information to the management computer 40. The management computer 40 associates the personal identification information of each person with the primary identification information of the corresponding vehicle C and records it in the database of the database server 50 (step A3 shown in FIG. 3).

[0027] Furthermore, in convenience store 1, an internal camera 30 installed near the cash register counter captures an image of the face and clothing of the person making the payment, and computer 20 in convenience store 1 generates personal identification information identifying the person who used the service from the image information captured by internal camera 30, and transmits this personal identification information to management computer 40 as additional identification information together with the usage information and information on the time of use.

[0028] The management computer 40 records each piece of acquired information in the database of the database server 50 and determines which parking space the person exited from. Then, by referring to the records in the database of the database server 50, if the person exited vehicle C and agreed to the free parking lot management service, the management computer 40 records the person's electronic money ID (step B1 shown in FIG. 3).

[0029] When the computer 20 of the convenience store 1 confirms from the image information of the external camera 10 that the vehicle C has exited from one of the parking positions 3a to 3d, the computer 20 generates vehicle identification information using the number obtained from the license plate of the vehicle C as the main key, and transmits the information to the management computer 40. In this example, since the target vehicle of the generated primary identification information matches the target vehicle of the exit information, the management computer 40 records this as secondary identification information linked to the primary identification information together with the time of the entry in the database of the database server 50 (step C1 shown in Figure 3).

[0030] Next, the management computer 40 refers to the award determination table registered in the database of the database server 50 to determine whether the award conditions are met. If the award conditions are met, the management computer 40 executes a process to grant award points to the electronic money ID of the user of the target vehicle. The award determination table has a predetermined range set according to the parking time, and the corresponding conditions are referenced as appropriate. In this embodiment, if the parking time of the exiting vehicle C is within a predetermined range, reward points according to the reward information are awarded to the electronic money of the user of the corresponding vehicle C. Here, various methods can be adopted for awarding reward points in the reward point awarding process by referring to the reward determination table.

[0031] For example, reward points can be awarded only to the driver of the corresponding vehicle (case 1 in step C2), reward points can be awarded to all users of the corresponding vehicle (case 2 in step C2), or users of the corresponding vehicle can be asked to participate in a lottery using electronic dice, for example, and reward points can be awarded only to the user who rolls the electronic dice (case 3 in step C2).When a lottery is used, the level of reward points (magnitude of benefit) can be determined according to the result of the lottery (for example, a large benefit can be awarded if the result of the lottery is good).

[0032] Furthermore, various levels of reward points can be awarded. For example, by using the additional identification information, the larger the payment amount at the register, the larger the reward points that are awarded (case 1 in step C3). In addition, the amount of time the vehicle has moved faster than the predetermined time is evaluated, and the more time the vehicle has moved faster than the predetermined time, the more reward points are awarded (case 2 in step C3).

[0033] As explained above, this free parking lot management system generates reward information if the parking time of vehicle C is less than the predetermined management time, and can grant reward points according to the reward information as a benefit to the user of vehicle C. This can encourage the user of vehicle C to leave the free parking lot early, which contributes to alleviating congestion in the free parking lot and allows for more efficient management of the free parking lot.

[0034] The free parking lot management system according to the present invention is not limited to the above-described embodiment, and it goes without saying that various modifications are possible without departing from the spirit of the present invention. For example, in the above embodiment, the free parking lot is described as being attached to a facility (convenience store), but the present invention is not limited to this and can be applied to a free parking lot that is not attached to a facility. In this case, additional identification information attached to the facility is not generated, and therefore processing is performed without using this information. However, if the free parking lot is provided as an attachment to the facility, the additional identification information as described above can be generated and used to determine whether or not the user has used the facility, and the reward information can be generated only if the user has used the facility. In this case, reward points can be awarded according to the degree of use of the facility.

[0035] Another embodiment that takes versatility into consideration will be described below.

[0036] <"Short-time use reward system for restaurants"> FIG. 4 shows an example in which the "short-time use reward system for restaurants" 201 according to the present invention is applied to a self-service restaurant. In particular, in self-service restaurants, even if two customers purchase items at the same price, one customer will finish eating and drinking and immediately leave the restaurant, while the other customer will start reading and continue to occupy the seat, causing inconvenience to the other customers and reducing the turnover rate of the restaurant's equipment.

[0037] However, in response to this situation, the "Short-time use reward system for restaurants" 201 aims to ensure convenience and fairness for users by awarding "reward points" to users who leave the restaurant after a short time in the restaurant, and also aims to increase the profits of the restaurant.

[0038] The "reward points" mentioned here are "store-issued tokens" that promise to give the user a discount on future purchases at the checkout, in order to return a portion of the store's profits generated by the user's short time in the store to the user.

[0039] First, the configuration of the "Short-time use reward system for restaurants" 201 will be explained. The "Short-time use reward system for restaurants" 201 is mainly composed of a "management database" 202, a "cash register" 203, a "handover duty machine" 204, a "coupon issuing machine" 205, and a "communication network" 206 that connects them. In the "Short-time use reward system for restaurants" 201, a "card" 211, a "receipt" 212, and a "reward coupon" 213 (213a, 213b) are treated as media for a "user identification number."

[0040] <"Accounting Counter"> The "checkout counter" 215 is a place (table) where customers can pay after selecting their products. The "checkout counter" 215 is installed near the entrance of the store, and products that do not require cooking are handed over to customers from here. Above the "checkout counter" 215, the "checkout cash register" 203 is installed.

[0041] <"Delivery Counter"> The "handover counter" 216 is a place (table) where cooked products are handed over to customers after the payment process. The "handover counter" 216 is installed near the kitchen inside the store, but in some cases it may be installed in the same place as the "accounting counter" 215. A "handover duty machine" 204 is installed above the "handover counter" 216.

[0042] <"Return Counter"> The "return counter" 217 is a place (table) where customers who have finished eating and drinking can return used trays, etc. The "return counter" 217 is installed near the exit of the store. Above the "return counter" 217, a "coupon issuing machine" 205 is installed.

[0043] <"Accounting cash register"> The "checkout register" 203 processes general payments for products purchased by the user, as well as checking the "reward points" held by the user, using the "reward points" to pay for the payment, and managing the start of the user's use of the store. When the "card" 211 or the "previously issued reward coupon" 213a is held over the "accounting register" 203, it reads the "user identification number" and then proceeds with the process for that user. The "checkout register" 203 displays the results of the transaction on the "display" 223 provided therein, and simultaneously issues a "receipt" 212 stating the results. Such processing is realized by the "checkout register" 203 requesting processing from the "management database" 202 and receiving the results returned from the "management database" 202. The "accounting cash register" 203 transmits the results of the series of accounting processes to the "sales management system" (not shown).

[0044] <"Delivery duty machine"> The "delivery duty machine" 204 manages the delivery of the product to the user. The cooked product is handed over to the customer, who then holds up the "receipt" 212 over the "handover duty machine" 204, which reads the "customer identification number," proceeds with the process for that customer, and lights up the provided "lamp" 224 to indicate that the process is complete. Such processing is realized by the "handover duty machine" 204 requesting processing from the "management database" 202 and receiving the result returned from the "management database" 202.

[0045] <Coupon issuing machine> When a customer holds up the "receipt" 212 just before leaving the store after finishing their use, the "coupon issuing machine" 205 reads the "customer identification number" and performs a process to award "reward points" according to the customer's circumstances such as the "number of hours spent in the store," and issues a "reward coupon issued this time" 213b listing the results. Such processing is realized by the "coupon issuing machine" 205 requesting processing from the "management database" 202 and receiving the result returned from the "management database" 202.

[0046] <Communications Network> The "communication network" 206 is used for data communication between the server machine on which the "management database" 202 is built, and the "accounting register machine" 203, "delivery duty machine" 204, and "coupon issuing machine" 205, and is composed of a "network cable" 218 and a "network device" 219. In some cases, "wireless communication" may also be used.

[0047] <Card> "Card" 211 is distributed to users who request it. "Card" 211 has a "user identification number" printed on it. When a user presents "Card" 211 to the cashier at "Checkout Counter" 215, "reward points" awarded up to the previous visit can be used to pay for the current transaction. However, it is possible to purchase products without presenting "Card" 211.

[0048] <"Receipt"> The "receipt" 212 is printed and issued by the "accounting register" 203 and given to the user, and in addition to listing the general accounting results, it also lists the results of processing related to "reward points," and in particular, it also lists the "user identification number." When the user holds the "receipt" 212 over the "handover duty machine" 204 or the "coupon issuing machine" 205, the process related to the "reward points" is carried out.

[0049] <"Reward Coupon"> The "reward coupon" 213 is printed and issued by the "coupon issuing machine" 205 and given to the user. It contains the results of the processing related to the "reward points", and in particular, the "user identification number". Depending on the processing situation, the "award coupon" 213 may be the "previously issued award coupon" 213a or the "currently issued award coupon" 213b. When a user visits the store and presents the "previously issued reward coupon ticket" 213a to the cashier, the "reward points" that were given up until the user's previous visit can be used to pay for the current transaction.

[0050] <"Management Database"> The "management database" 202 is a database application built into the storage of a server machine, and this server machine is installed in a section such as a staff room in the case of a small-scale store such as an individual shop, or in a data center in the case of a large-scale store such as a chain store. The "management database" 202 includes a "standard product consumption time table" 235 and a "reward management table" 236 as data tables. In addition, the tasks for processing the data held by these include "inquiry processing" 241, "accounting processing" 242, "delivery processing" 243, "grant processing" 244, and "periodic processing" 245.

[0051] <Data table structure> FIG. 6 is an image of the structure of the data table in the "management database" 202. This is an image of a field (drawn as a box) placed on top of each record (drawn as a band). One piece of data (a number or date and time) is recorded in each field according to a predetermined purpose. In the data tables shown in Figures 4 and 5, the horizontal axis represents the records, and the vertical axis represents the fields placed on those records.

[0052] <"Standard Time Table for Consumption of Products"> The "standard time spent eating and drinking for each product" table 235 records the standard time spent eating and drinking for each product sold in the store, with one record for each product. These records are entered in advance by the store. The "Standard Time for Eating a Product Table" 235 has the following fields: "Product Code" field 251f records the "product code" for that product. "Standard Time for Eating" field 252f records the standard number of hours that will be spent eating and drinking that product.

[0053] <"Reward Management Table"> The "reward management table" 236 records matters related to "reward points," with one record being created for each use (from checkout to reward coupon issuance) by one user. The "reward management table" 236 has the following fields: "User identification number" field 270f records the user's "user identification number." "Total purchase amount" field 271f records the total amount of the products purchased by the user this time. "Total number of items purchased" field 272f records the total number of products purchased by the user this time. "Total standard time spent consuming products" field 273f records the total standard time spent consuming all the products purchased by the user this time. "Store usage start date and time" field 274f records the date and time when the user first completed the transaction. "Product delivery date and time" field 275f records the date and time when the user would have first received the product at the "delivery counter" 216. "Store usage hours" field 276f records the number of hours from the "store usage start date and time" to the "reward point award date and time," i.e., the number of hours the user would have actually spent consuming the product. The "reward point grant date and time" field 277f records the date and time when the "reward points" were granted to the user. The "reward point expiration date and time" field 278f records the date and time when the "reward points" granted this time will expire. The "reward point balance" field 279f records the remaining number of "reward points" granted this time. When this "reward point count" is used multiple times, this value is reduced each time until it reaches zero.

[0054] <Processing tasks for the "Management Database"> The "management database" 202 has the following processing tasks for processing data in the data table. "Query processing" 241 performs a process to tally the "number of reward points" held by the user. "Accounting processing" 242 performs a process to cancel the "number of reward points" to be used for the transaction from the "number of reward points" held by the user. "Delivery processing" 243 performs a process to mark the date and time when the user receives the product and is considered to have started eating and drinking. "Granting processing" 244 performs a process to calculate the "number of reward points" to be awarded this time from the amount of time spent in the store and the product purchased, and grants the "reward points" to the user. "Periodic processing" 245 periodically (when the store is closed, for example, at night) deletes records that have become outdated and are confirmed to no longer be used, in order to maintain the performance of the database.

[0055] <"User Identification Number"> The "user identification number" is a unique number that is assigned to a user and is used to access records related to that user.

[0056] <If you can present your card> The following describes the case where a user can present a "card" 211 with regard to the "user identification number." The "card" 211 is issued to any user who requests it. A "user identification number," which is a unique number for each "card" 211, is assigned and printed on the "card" 211. Furthermore, the "receipt" 212 issued when this "card" 211 is used for payment and the "reward coupon issued this time" 213b will have the same "user identification number" as that "card" 211 printed on them. For a user who presented "card" 211 when paying during their previous visit, the "reward points" awarded during their previous visit are linked to the "user identification number" printed on "card" 211, so by presenting "card" 211 during their current visit, the "reward points" awarded during their previous visit can be used to pay for their current visit.

[0057] <If you cannot present either of these> The following describes a case where a user is unable to present either the "user identification number." When a user is unable to present the "card" 211 or the "previously issued reward coupon" 213a during the checkout process, a unique "user identification number" is assigned at the time of the checkout, and this number is written on the issued "receipt" 212 and the "currently issued reward coupon" 213b. For this user, the "reward points" awarded the previous time they visited the store are linked to the "user identification number" assigned at that time, so when they visit this time, they can use the "reward points" awarded the previous time to pay for their bill by presenting the "previously issued reward coupon ticket" 213a.

[0058] <Example> Up to this point, the embodiment has been explained. Next, an example of the "Short-time use reward system for restaurants" 201 will be explained in more detail.

[0059] <Customer behavior in the store> First, we will organize the conveniences and actions of users in the store that will affect the processing of the "Short-time use reward system for restaurants" 201. First, the convenience of a user looking at products can be {just arrived} or {want to purchase additional products}, the items the user will present at the checkout can be {present a "card" 211}, {present a "previously issued reward coupon" 213a}, or {present nothing}, the place where the user will receive the products can be {from the "checkout counter" 215} or {from the "delivery counter" 216}, when clearing the tray after eating and drinking, can be {use a "coupon issuing machine" 205} or {do not use a "coupon issuing machine" 205}, and the convenience after clearing the tray can be {leave the store as is} or {want to purchase additional products}. Based on the above, we would like to explain in detail below how the "Short-Term Use Reward System for Restaurants" 201 functions from the time a customer enters the store, pays for the selected item, eats and drinks, and leaves the store.

[0060] <Inquiry: First, go to the cash register> The following is the role of the "accounting register" 203 in the {scene of checking "reward points"} (Figure 7). When a customer visits the store, the customer will likely first select multiple items and carry them to the "checkout counter" 215. At the "checkout counter" 215, the accounting staff will receive the items from the customer. At this time, the customer may present the "card" 211 or the "previously issued reward coupon ticket" 213a. If such a card is presented, the accounting staff will hold the "card" 211 or the "previously issued reward coupon ticket" 213a over the "checkout register" 203 to begin investigating the "number of reward points" that the customer may have. The "checkout register" 203 reads the "user identification number" 270a written on the "card" 211 or the "user identification number" 270b written on the "previously issued reward coupon" 213a, and sets this value as the "user identification number" 270s to be used for transmission. (311) The "checkout register" 203 sends a request 401s for the "inquiry process" 241 to the "management database" 202, and also sends the "user identification number" 270s.

[0061] <Query: "Administrative Database"> The role of the "management database" 202 in the "reward points" query scenario is as follows (Figure 7). In the "management database" 202, the "inquiry process" 241 is started and the "user identification number" 270s is received. <Calculating "Available Reward Points"> Below is the process for calculating the "number of available reward points." The "number of available reward points" is the number of reward points the user holds in the "management database" 202. To calculate this, the values ​​in the "reward points remaining" field 279f of the target records, which may include multiple records, are added together. The details of this process are as follows: In the records of the "Reward Management Table" 236 linked to the received "User Identification Number" 270s, the date and time in the "Reward Point Expiration Date and Time" field 278f is not expired, and the value in the "Reward Points Remaining" field 279f is not zero. The "Available Reward Points" 406r to be used in the response is calculated by accumulating the values ​​in the "Reward Points Remaining" field 279f of the records, which may be multiple records, that meet the following conditions: (313) The "Reward Points Remaining" field 279f is not zero. <Response> The "management database" 202 returns the "number of available reward points" 406r to the "accounting register" 203 as a response.

[0062] <Query: Again at the cash register> The following is the role of the "cash register" 203 in the situation where "reward points" are inquired. (Figure 7) The "checkout register" 203 receives the "number of available reward points" 406r and displays it on the "display" 223. (315) Customers will likely refer to this notice when making their next checkout.

[0063] <Accounting: First, the cash register> The following is the role of the "checkout cash register" 203 in the {scene where you pay with "reward points"} (Figure 8). At the "checkout counter" 215, the accounting staff will carry out the accounting process for the items, which may be multiple items, selected by the user. The "item code" 425 and "quantity" 426 of the items, which may be multiple items, that the user will purchase are entered into the "checkout register" 203 (321), and then the "checkout register" 203 calculates the total price of the items and calculates tax (322). This is a typical accounting process.

[0064] The "checkout register" 203 creates a "user selected product list" 208s (Fig. 5) to be used for transmission from the "product code" 425 and "purchase quantity" 426, which may be multiple, entered at this time (323). This "List of products selected by the user" 208s is table-type data in which the "product code" 425 and "quantity purchased" 426 of the products, which may be multiple products, that the user will purchase are recorded in multiple records, each consisting of a "purchased product code" field 225f and a "quantity purchased" field 226f. In addition, the “checkout register” 203 sets the total amount of the multiple items that the user will likely purchase, calculated earlier, as the “total purchase amount” 271s to be used for transmission, and sets the total number of those items as the “total number of items purchased” 272s to be used for transmission.

[0065] The accounting staff informs the user of the number of "available reward points" 406r that was displayed on the "display" 223 earlier, then asks how many "reward points" the user wants to use, and inputs that number into the "accounting register" 203. The "accounting register" 203 uses this number as the "reward points desired to use" 411s to be used for transmission. (324)

[0066] The "checkout register" 203 sends a request 402s for "checkout processing" 242 to the "management database" 202, along with the "user identification number" 270s, "reward points to be used" 411s, "list of products selected by the user" 208s, "total purchase amount" 271s, and "total number of items purchased" 272s. At this time, if the user does not have the "card" 211 or the "previously issued reward coupon" 213a, the value of the "user identification number" 270s will be undetermined.

[0067] <Accounting: In the "Management Database"> The following explains the role of the "management database" 202 in the {scene of paying with "reward points"} (Figure 8). In the "management database" 202, the "accounting process" 242 is started, and the "user identification number" 270s, "reward points to be used" 411s, "list of products selected by the user" 208s, "total purchase amount" 271s, and "total number of items purchased" 272s are received. If the value of the "user identification number" 270s received here is undetermined, the "management database" 202 does nothing after this until the process to generate a new "user identification number."

[0068] <Delete reward points based on the number of points you wish to use> The following is the {"Delete process using the number of reward points you wish to use"}, that is, the process to delete the "number of reward points" used for payment in the accounting process. This process subtracts the value in the "Remaining number of reward points" field 279f of the target records (which may be multiple) by the value in the "Number of reward points you wish to use" 411s, in order of the oldest date and time in the "Reward point expiration date and time" field 278f.

[0069] The details of this process are as follows: In the record of the "Reward Management Table" 236 linked to the received "User Identification Number" 270s, the date and time in the "Reward Point Expiration Date and Time" field 278f is not expired, and among the records whose value in the "Reward Point Reward Point Expiration Date and Time" field 279f is not zero, the value in the "Reward Point Reward Point Expiration Date and Time" field 279f is the oldest. The value in the received "Reward Point Reward" field 279f is subtracted by the value in the received "Reward Point Reward" 411s. If the subtraction does not result in a zero, the value in the "Reward Point Reward" field 279f is subtracted by the value in the received "Reward Point Reward" field 279f. If a "deficiency" occurs in the value in the "Reward Points Remaining" field 279f of the record that matches the condition that the "Reward Point Expiration Date and Time" field 278f has the next oldest date and time, the "deficiency" that just occurred is subtracted from the value in that record's "Reward Points Remaining" field 279f. This subtraction process is repeated until the "Reward Points Wanted to Use" 411s values ​​have been subtracted from the "Reward Points Remaining" field 279f of all records, which may be multiple records. The number actually subtracted in this process is used as the "Reward Points Cancelled" 414r to be used in the response. (331)

[0070] <Calculating the "number of available reward points" after the cancellation process> The following is {Calculating the "Number of available reward points" after the cancellation process}, that is, calculating the "Number of available reward points" that will have been updated immediately after the "reward points" have been cancelled. The details of this process are as follows: In the records of the "Reward Management Table" 236 linked to the received "User Identification Number" 270s, the date and time in the "Reward Point Expiration Date and Time" field 278f is not expired, and the value in the "Reward Point Balance" field 279f is not zero. The "Available Reward Points" 407r to be used in the response is calculated by accumulating the values ​​in the "Reward Point Balance" field 279f of the records, which may be multiple records, that meet the following conditions: (332) The "Reward Point Balance" field 279f is not zero.

[0071] <Processing for starting in-store use> Below is the {processing for starting in-store use}, but this process branches off depending on whether it is the "first process" or the "second or subsequent process." The "first process" is {the first transaction process on that day, or a second transaction process immediately after the process that awarded "reward points" on the same day}, and the "second or subsequent process" is {the second or subsequent transaction process on the same day without the process of awarding "reward points"}.

[0072] <In-store use start: First processing> Below is the {"initial process" for starting in-store use}. The details of this condition are as follows: {If the received "user identification number" 270s is undecided}, or {If there is no record in the "reward management table" 236 linked to the "user identification number" 270s}, or {If there is no record in the "reward management table" 236 linked to the "user identification number" 270s where the date and time in the "store usage start date and time" field 274f is the date and time of that day}, then as "initial processing", the following {process to generate a new "user identification number"}, {process to generate a new record}, ​​and {process to mark the "store usage start date and time"} are performed.

[0073] <Generate a new "user identification number"> Below is the process to generate a new "user identification number." The details of this process are as follows: if the value of the received "user identification number" 270s is undetermined, the "management database" 202 generates a new unique value, and thereafter uses this value as the received "user identification number" 270s, and also sets this value as the "user identification number" 270r to be used in the response.

[0074] <Create a new record> The following is the process for creating a new record in the "award management table" 236. In detail, in this process, the "management database" 202 generates a new record linked to the received "user identification number" 270s in the "award management table" 236. Furthermore, in the processes that follow this process, this new record is also the "record to be processed."

[0075] <Mark "In-store use start date and time"> Below is the process to mark the "in-store usage start date and time." The "in-store usage start date and time" is the date and time of the first transaction for that customer that day. The details of this process are that the current date and time is recorded in the "in-store use start date and time" field 274f of the "processing target record," and this date and time is used as the "in-store use start date and time" 274r to be used in the response. The above is the initial process for starting in-store use. (333)

[0076] <In-store use start: Processing from the second time onwards> Below is the {"Processing from the second time onwards" for starting in-store use}. The details of this condition are as follows: {among the records in the "Reward Management Table" 236 linked to the received "User Identification Number" 270s, if there is a record that meets the condition that the date and time in the "Store Usage Start Date and Time" field 274f is the date and time of that day, and the date and time in the "Reward Points Grant Date and Time" field 277f is undecided}, then as "processing from the second time onwards", the following {processing to obtain the "Store Usage Start Date and Time"} and {processing to adjust the "Product Delivery Date and Time"} are performed. In these processes and the processes that follow them, the record that meets the above conditions is the "record to be processed".

[0077] <Get "in-store usage start date and time"> Below is the process to obtain the "in-store usage start date and time." The "in-store usage start date and time" is the date and time of the first transaction for that customer that day. In detail, this process extracts the date and time from the "in-store use start date and time" field 274f of the "processing target record" and sets this as the "in-store use start date and time" 274r to be used in the response.

[0078] <Adjust the "product delivery date and time"> The following is the process for adjusting the "product delivery date and time." The "product delivery date and time" is the first date and time when the product is handed over to the user from the "delivery counter" 216, and is considered to be the date and time when the user starts eating and drinking. However, if the "product delivery date and time" is not yet determined for the second or subsequent transaction of the day, the product will have been handed over from the "checkout counter" 215 for the first transaction, and this "product delivery date and time" must be adjusted. In detail, if the date and time in the "item delivery date and time" field 275f in the "record to be processed" is undecided, the date and time in the "store use start date and time" field 274f is recorded in the "item delivery date and time" field 275f. The above is the process for starting in-store use. (334) The branched processes will merge from this point onwards.

[0079] <Calculating the "standard time spent eating and drinking"> The following is the process for calculating the "Total Standard Time for Eating Products." The "Total Standard Time for Eating Products" is the standard time that a user is likely to spend eating the multiple products that they will purchase. This is calculated by comparing the "List of Products Selected by User" 208s with the "Table of Standard Time for Eating Products" 235. The details of this process are as follows: the "Purchase Product Code" field 255f of the received "User Selected Product List" 208s (Fig. 5) is linked to the "Product Code" field 251f of the "Standard Product Eating Time Table" 235, the value in the "Quantity Purchased" field 256f of the "User Selected Product List" 208s and the number of seconds in the "Standard Eating Time" field 252f of the "Standard Product Eating Time Table" 235 are added together, and the value obtained by accumulating these values ​​is added to the value extracted from the "Total Standard Product Eating Time" field 273f of the "Record to be Processed" (zero in the "First Processing"). The value obtained by this addition is recorded in the original "Total Standard Product Eating Time" field 273f, and the value obtained by this addition is set as the "Total Standard Product Eating Time" 273r to be used in the response. (336)

[0080] <Other> As other processing, the value of "total purchase amount" 271s is recorded in the "total purchase amount" field 271f, and the value of "total number of items purchased" 272s is recorded in the "total number of items purchased" field 272f. <Response> The "management database" 202 replies to the "checkout register" 203 with the "user identification number" 270r, "in-store usage start date and time" 274r, "number of reward points cancelled" 414r, "number of available reward points" 407r, and "total standard time for eating and drinking" 273r.

[0081] <Accounting: Back at the cash register> The following is the role of the "checkout cash register" 203 in the situation where "reward points" are used for payment. (Figure 8) The "checkout register" 203 receives the "user identification number" 270r, "in-store usage start date and time" 274r, "number of cancelled reward points" 414r, "number of available reward points" 407r, and "total standard time for eating and drinking" 273r. The “checkout register” 203 verifies the consistency of the received “number of cancelled reward points” 414r, and then calculates the final amount to be paid by the user (341) with the store paying the amount of this number, and displays the result on the “display” 223 (342). The user sees the notice and pays the bill. After the accounting staff confirms the payment, the accounting process is completed. The "accounting register" 203 sends the results of this accounting process to the "sales management system" (not shown). (343) The "accounting register" 203 displays the results of general accounting processing, as well as the "user identification number" 270r, "in-store usage start date and time" 274r, "number of cancelled reward points" 414r, "number of available reward points" 407r, and "standard total number of hours for eating and drinking" 273r on the "display" 223, and at the same time prints and issues a "receipt" 212 showing these results. (344) The customer receives the issued "receipt" 212. After that, items that can be handed over to the customer immediately are handed over from the "checkout counter" 215, and items that require cooking are handed over from the "delivery counter" 216 located near the kitchen.

[0082] <Delivery: First, the "Delivery Duty Machine"> The following is the role of the "delivery duty machine" 204 in the {product delivery scene} (Figure 9). When the food requiring cooking is ready for delivery, an announcement is made to the customer. At the "delivery counter" 216, the customer receives the cooked food and holds the "receipt" 212 over the "delivery duty machine" 204. The "delivery duty machine" 204 reads the "user identification number" 270r written on the "receipt" 212 and sets this value as the "user identification number" 270s to be used for transmission. (351) The "handover duty machine" 204 transmits a request 403s for the "handover process" 243 to the "management database" 202, and also transmits the "user identification number" 270s.

[0083] <Delivery: In the "Management Database"> The following is the role of the "management database" 202 in the {product delivery scene} (Figure 9). In the "management database" 202, the "handover process" 243 is started and the "user identification number" 270s is received. <Mark "Product delivery date and time"> The following is the process for marking the "product delivery date and time." In this process, only the first delivery is marked with the date and time at that time. The "product delivery date and time" is the first date and time of the day when the product is handed over to the customer from the "delivery counter" 216. This date and time is then considered to be the date and time when the customer started eating and drinking. In detail, the "management database" 202 performs the following process on records in the "reward management table" 236 linked to the received "user identification number" 270s that meet the conditions that the date and time in the "store usage start date and time" field 274f is the date and time of the day and the date and time in the "reward point grant date and time" field 277f is undetermined (i.e., records generated on that day for which the "reward points" grant process has not yet been performed). If the date and time in the "product delivery date and time" field 275f is undetermined (in the case of the first delivery), the "management database" 202 records the current date and time in the "product delivery date and time" field 275f, and also sets this date and time as the "product delivery date and time" 275r to be used in the response. Also, if there is a date and time in the "product delivery date and time" field 275f (in the case of the second or subsequent delivery), the date and time in the "product delivery date and time" field 275f is set as the "product delivery date and time" 275r to be used in the response. (353) <Response> The "management database" 202 returns the "product delivery date and time" 275r to the "delivery duty machine" 204 as a response.

[0084] <Delivery: Once again at the "Delivery Duty Machine"> The following is the role of the "delivery duty machine" 204 in the {scene of delivering goods} again (Figure 9). The "delivery duty machine" 204 receives the "product delivery date and time" 275r. The "handover duty machine" 204 turns on the "lamp" 224. (355) Customers receive their items, take their seats, and begin eating and drinking.

[0085] <Granting: First, use the coupon issuing machine> The following is the role of the "coupon issuing machine" 205 in the {scene of awarding "reward points"} (Figure 10). When the customer has finished eating and drinking, he or she takes the used tray and the "receipt" 212 and heads to the "return counter" 217. At the "return counter" 217, the customer disposes of the used tray and holds the "receipt" 212 over the "coupon issuing machine" 205. The "coupon issuing machine" 205 reads the "user identification number" 270r written on the "receipt" 212 and sets this value as the "user identification number" 270s to be used for transmission. (361) The "coupon issuing machine" 205 sends a request 404s for the "granting process" 244 to the "management database" 202, and also sends the "user identification number" 270s.

[0086] <Grant:"Management Database"> The role of the "management database" 202 in the {situation of awarding "reward points"} is as follows (Figure 10). In the "management database" 202, the "assignment process" 244 is started and the "user identification number" 270s is received.

[0087] <Granting reward points> Below is the process for granting reward points to the user. This process consists of multiple steps: marking the reward point grant date and time, calculating the number of hours spent in the store, calculating the number of reward points granted this time, and calculating the reward point expiration date and time. Furthermore, the "records to be processed" in the "award management table" 236 in these processes are records generated on that day that have not yet been processed to grant "award points." In detail, the "record to be processed" is the record in the "reward management table" 236 linked to the received "user identification number" 270s, which matches the conditions that the date and time in the "store usage start date and time" field 274f is the date and time of that day, and the date and time in the "reward point grant date and time" field 277f is undecided.

[0088] <Mark "Reward point award date and time"> The following is the process for marking the "award point grant date and time." The "award point grant date and time" is the date and time when the "award points" were granted to the user. The details of this process are as follows: the date and time at that time is recorded in the "award point grant date and time" field 277f, and this date and time is used as the "award point grant date and time" 277r to be used in the response. (363)

[0089] <Calculating "hours spent in store"> Below is the process for calculating the "number of hours spent in the restaurant." The "number of hours spent in the restaurant" is the number of hours that the customer actually spent eating and drinking. Regarding the details of this process, first, the method for calculating the "number of hours spent in store" differs depending on where the customer received the product. If the customer received the product at the "checkout counter" 215, the date and time in the "product delivery date and time" field 275f is undetermined. In this case, the number of seconds elapsed from the date and time in the "store use start date and time" field 274f to the date and time in the "reward points awarded date and time" field 277f is calculated, and this is recorded in the "number of hours spent in store" field 276f. This is also used as the "number of hours spent in store" 276r to be used in the response. If the customer received the product at the "delivery counter" 216, the date and time is recorded in the "product delivery date and time" field 275f. In this case, the number of seconds elapsed from the date and time in the "product delivery date and time" field 275f to the date and time in the "reward points awarded date and time" field 277f is calculated, and this is recorded in the "number of hours spent in store" field 276f. This is also used as the "number of hours spent in store" 276r to be used in the response. (364)

[0090] <Calculate the number of reward points awarded this time> Below is the process to calculate the "Number of Reward Points Granted This Time." The "Number of Reward Points Granted This Time" is the "Number of Reward Points" that will be granted to the user this time. The details of this process are as follows: the "number of hours spent in the store" is evaluated based on the standard number of hours that the user would spend eating and drinking this time, which is derived from the products purchased by the user, and the "number of hours spent in the store" is evaluated based on the standard number of hours that the user would spend eating and drinking this time, and the shorter the "number of hours spent in the store", the more "award points" are awarded, and further, the more "award points" are awarded to the user who presents "card" 211. There are at least two possible ways of doing this:

[0091] The first method involves subtracting the value in the "Number of Hours Spent in Store" field 276f from the value in the "Standard Total Hours Spent on Products and Drinks" field 273f. If the result is greater than zero, the subtraction result is multiplied by the "Use A Coefficient." This multiplication result is recorded as the "Number of Award Points Granted This Time" in the "Remaining Award Points" field 279f, and is also used as the "Number of Award Points Granted This Time" 416r for responses. The "Use A Coefficient" is set to a higher value for users who present the "Card" 211 than for users who do not present the "Card" 211. The "Use A Coefficient" is set to an optimal value for converting hours into "Number of Award Points."

[0092] The details of the second method are as follows: a "flat conversion table" (Fig. 11) is created in advance; in the squares on one axis, a numerical value representing the range assigned to each square for the "standard time for total consumption of products and drinks" field 273f is placed; in the squares on the other axis, a numerical value representing the range assigned to each square for the "time spent in the store" field 276f is placed; and in the squares where the two axes intersect, a numerical value that is a candidate for the "number of reward points awarded this time" is placed; and the "total number of products and drinks consumed" that actually occurred is calculated. The "number of reward points awarded this time" is calculated by extracting the value placed in the box indicated by the value in the "standard number of hours spent eating and drinking" field 273f and the value in the "number of hours spent in the store" field 276f. Furthermore, two such "flat conversion tables" are prepared, and one "flat conversion table" for users who present "card" 211 is set to have larger values ​​placed in each box compared to the other "flat conversion table" for users who do not present "card" 211. The "number of reward points awarded this time" obtained from this is recorded in the "reward points remaining" field 279f, and is also set as the "number of reward points awarded this time" 416r used in the response. Above are the two ways to calculate the "Number of reward points awarded this time."

[0093] <Other ways to find the answer> Furthermore, as another method of calculation, in the process of calculating the "Number of Reward Points Granted This Time" described above, the "Number of Hours Spent in the Store" was evaluated based on the "Standard Total Hours Spent in the Store" to determine the "Number of Reward Points Granted This Time." However, instead of using the "Standard Total Hours Spent in the Store" as the basis, it is also possible to calculate the "Number of Reward Points Granted This Time" by evaluating the "Number of Hours Spent in the Store" based on the value obtained by multiplying the value in the "Total Purchase Amount" field 271f by the "Use B Coefficient." The "Use B Coefficient" is set to an optimal value for converting the "Total Purchase Amount" to the number of hours.

[0094] Alternatively, instead of using the "Standard Time for Total Product Eating and Drinking" as the basis, the "Number of Hours Spent in the Store" can be evaluated based on the value obtained by multiplying the value in the "Total Purchases" field 272f by the "Use C Coefficient" to determine the "Number of Award Points Granted This Time." The "Use C Coefficient" is set to an optimal value for converting the "Total Purchases" into hours. The above is how to calculate the number of reward points awarded this time. (365)

[0095] <Find the "reward point expiration date and time"> The following is the process for calculating the "reward point expiration date and time." The "reward point expiration date and time" is the expiration date and time for the "number of reward points granted this time." This is designed so that the larger the "number of reward points granted this time," the more validity period dates and times are given, and furthermore, the more validity period dates and times are given to the user who presents the "card" 211, and the "reward point expiration date and time" is calculated.

[0096] The details of this process are as follows: multiply the value of "Number of Reward Points Granted Currently" 416r by the "Use D Coefficient," set the result of this multiplication as the number of days and times of the validity period, add this to the current date and time, record the result of this addition in the "Reward Point Expiration Date and Time" field 278f, and set it as the "Reward Point Expiration Date and Time" 278r to be used in the reply. Furthermore, the "Use D Coefficient" setting value is set to a larger value for users who present the "Card" 211 than for users who do not present the "Card" 211. The "Use D Coefficient" is set to an optimal value for converting the "Number of Reward Points" to the number of days and times of the validity period.

[0097] Also, unlike the above-mentioned idea, it is also possible to simply determine the number of days and hours of a validity period and calculate the "reward point expiration date and time" 278r. The details of this process are to add the validity period date and time, which is set to a certain value, to the current date and time, and record the result of this addition in the ``Reward point expiration date and time'' field 278f, and also use it as the ``Reward point expiration date and time'' 278r to be used in the reply. The above is the process to find the "reward point expiration date and time." (366) The above is a series of processes for granting "reward points" consisting of multiple processes: marking the "reward point granting date and time", calculating the "number of hours spent in the store", calculating the "number of reward points granted this time", and calculating the "reward point expiration date and time".

[0098] <Calculating the "Number of available reward points" after the awarding process> The following is {Calculating the "number of available reward points" after the awarding process}, that is, calculating the "number of available reward points" that will have been updated immediately after the "reward points" have been awarded. The details of this process are as follows: In the records of the "Reward Management Table" 236 linked to the received "User Identification Number" 270s, the date and time in the "Reward Point Expiration Date and Time" field 278f is not expired, and the value in the "Reward Points Remaining" field 279f is not zero. The "Available Reward Points" 408r to be used in the response is calculated by accumulating the values ​​in the "Reward Points Remaining" field 279f of the records, which may be multiple records, that meet the following conditions: (367)

[0099] <Response> In response to the coupon issuing machine 205, the "management database" 202 returns the "reward point award date and time" 277r, "number of hours spent in the store" 276r, "number of reward points awarded this time" 416r, "reward point expiration date and time" 278r, and "number of available reward points" 408r.

[0100] <Grant: Again at the "Coupon issuing machine"> The following is the role of the "coupon issuing machine" 205 in the situation where "reward points" are awarded. (Figure 10) The "coupon issuing machine" 205 receives the "reward point award date and time" 277r, "number of hours spent in store" 276r, "number of reward points awarded this time" 416r, "reward point expiration date and time" 278, and "number of available reward points" 408. The "coupon issuing machine" 205 prints and issues the "reward coupon issued this time" 213b, which contains the "user identification number" 270r, "reward point award date and time" 277r, "number of hours used in the store" 276r, "number of reward points awarded this time" 416r, "reward point expiration date and time" 278r, and "number of available reward points" 408r. (369) The customer receives this and leaves the store. This "reward coupon issued this time" 213b can be used to pay for the next purchase when visiting the store.

[0101] <Summary> We have explained in detail how the "Short-Time Restaurant Usage Reward System" 201 functions from the time a customer enters a restaurant, pays for the selected items, eats, and leaves. In particular, the "Reward Coupon Issued This Time" 213b received by this customer lists the "Number of Reward Points Awarded This Time" 416r. This number is calculated based on the "Standard Total Product and Drink Time," which is the standard time the customer would spend eating and drinking in the restaurant this time, calculated from the items purchased by the customer. The shorter the "Time in the Restaurant," the more "Reward Points" are awarded. The "Number of Reward Points Awarded This Time" is the amount printed on a "Token" that the customer can use to pay their bill the next time they visit the restaurant.

[0102] In this case, if the user were to finish using the store in a shorter time, the costs of the in-store equipment that were spent on the products purchased by the user would become a profit for the store, and by returning a portion of that to the user as "reward points," the user would be able to receive products at a fairer price. This is expected to raise the user's awareness of in-store use, and therefore increase the user's opportunities to use the store. At the same time, it is expected that the user's "number of hours spent in the store" will be shortened, which is expected to increase the turnover rate of the eating and drinking space, which tends to get crowded, and increase the opportunities for other users to use the eating and drinking space, which is expected to increase the number of times other users will use the store, and increase the store's sales. In other words, the "short-time use reward system for restaurants" 201 related to the present invention is an innovative system that is expected to bring benefits and convenience to the store, the user, and other users. <Modification> The embodiments of the present invention are not limited to those described above, and various modifications are provided within the scope that does not impair the essence of the present invention. For example, this system can be applied to paid coin lockers (priced at 400 yen / day, for example) installed at stations and airports, or free coin lockers installed at entertainment facilities such as game centers or bathing facilities such as day spas, and if the coin locker's usage time is within the normal usage time for such facilities (for example, 3 hours), reward information can be generated to grant the user benefits such as points that can be used at the facility. Furthermore, in urban restaurants, reward information may be provided to customers who finish their meal and leave within an ideal stay time (for example, 15 minutes) during lunchtime, which allows for a desirable turnover rate for the restaurant, so that the customer will receive a free dish the next time they visit. In this case, since the restaurant is in the business of providing food and drink and receiving payment for it, the seat itself can be considered to be provided free of charge, and the system related to free parking described above can be applied in a similar manner. Furthermore, if a user who has a ticket for an amusement facility that is valid for one year (a so-called annual passport) that allows entry at any time of the day enters in the afternoon, i.e., does not exercise the right to enter in the morning, the user may be given reward information that provides some kind of benefit (for example, a badge with a character printed on it). [Explanation of symbols]

[0103] 1. Convenience store (facility) 2. Free parking 3a~3d Parking position 10 External camera (imaging unit) 20 Facility Computer (Information Processing Section) 30 Internal camera (imaging unit) 40 Management Computer (Information Processing Section) 50 Database Servers 100 Free Parking Management System C vehicle 201 "Short-time use reward system for restaurants" 202 "Management Database" 203 "Accounting cash register" 204 "Delivery Duty Machine" 205 "Coupon issuing machine" 206 "Communication Network" 208s "User Selected Product List" 211 "Card" 212 "Receipt" 213a "Previously issued reward coupon" 213b "Reward coupon issued this time" 215 "Accounting Counter" 216 "Delivery Counter" 217 "Return Counter" 218 "Network Cable" 219 "Network Equipment" 223 "Display" 224 "Lamp" 235 "Standard Time Table for Food and Drink" 236 "Reward Management Table" 241 "Inquiry Processing" 242 "Accounting Procedures" 243 "Delivery Processing" 244 "Procedure for granting" 245 "Periodic Processing" 251f "Product Code" field 252f "Standard hours for eating and drinking" field 270a "User Identification Number" 270b “User identification number” 270f "User Identification Number" field 270r "User identification number" 270s "User identification number" 271f "Total Purchase Amount" field 271s "Total purchase amount" 272f "Total Purchase Quantity" field 272s "Total number of purchases" 273f "Total standard time spent eating and drinking" field 273r “Total standard number of hours spent on food and beverages” 274f "In-store use start date and time" field 274r "Date and time of in-store use start" 275f "Product delivery date and time" field 275r "Product delivery date and time" 276f "Number of hours spent in the store" field 276r “Number of hours used in store” 277f "Reward points awarded date and time" field 277r "Reward points award date and time" 278f "Reward points expiration date and time" field 278r "Reward points expiration date and time" 279f "Remaining Reward Points" field 311 Enter your "User Identification Number" 313 Calculate "Available Reward Points" 315 Processing the results of query processing 321 Enter information about the product selected by the user 322 Calculate the total price and tax amount of the product 323 Create a "User Selected Product List" 324 Enter the number of reward points you wish to use 331 Cancellation process based on "Number of reward points desired to use" 332 Calculate the "Number of available reward points" after the cancellation process 333 "Initial Processing" for In-Store Use 334 "Processing from the second time onwards" regarding the start of in-store use 336 Calculate the "standard time spent eating and drinking" 341 Accounting treatment including the number of cancelled reward points 342 Output the payment amount calculation result 343 Sending the results of accounting processing to the "Sales Management System" 344 Output general accounting results and "reward points" results 351 Enter "User Identification Number" 353 Mark "Product Delivery Date" 355 Output the results of the delivery process 361 Enter "User Identification Number" 363 Mark "Reward Points Award Date and Time" 364 Calculate "hours spent in store" 365 Find the "Number of reward points awarded this time" 366 Request "reward point expiration date and time" 367 Calculate the "Number of available reward points" after the awarding process 369 Output the result of the granting process 401s "Referral Processing" Requests 402s "Accounting" requests 403s "Process for Delivery" Request 404s "Grant Processing" Request 406r "Available reward points" 407r "Available Reward Points" 408r "Available reward points" 411s "Number of reward points you would like to use" 414r "Number of reward points destroyed" 416r "Number of reward points awarded this time" 425 "Product Code" 426 "Number of purchases"

Claims

1. An imaging unit that captures images of vehicles entering and leaving parking spaces in a free parking lot, and an information processing unit to which imaging information captured by the imaging unit is input, The information processing unit generates vehicle identification information that identifies the vehicle based on the imaging information, and entry time information and exit time information for the vehicle linked to the vehicle identification information, and compares the parking time of the vehicle corresponding to the vehicle identification information with a predetermined management time, and if the parking time of the vehicle is less than the predetermined management time, generates reward information and grants a benefit according to the reward information to the user corresponding to the vehicle.

2. The free parking lot is provided as an attachment to the facility, It is determined whether the user has used the facility, and only if the user has used the facility, The free parking lot management system according to claim 1, wherein the benefit is given based on the amount of the parking lot.

3. 3. The free parking lot management system according to claim 2, wherein the profit is given in accordance with the degree of use of the facility, the greater the degree of use, the greater the amount of profit given.

4. 4. The free parking lot management system according to claim 1, wherein the profit is increased as the parking time is shorter than the predetermined management time.

5. 5. The free parking lot management system according to claim 1, wherein the amount of the profit is determined according to the result of a lottery drawn by the user or a random number.

6. an information acquisition unit that acquires target identification information that identifies a user of the free facility; and an information processing unit to which the target identification information acquired by the information acquisition unit is input; The information processing unit generates user entity identification information that identifies the user entity based on the target identification information, and information on the start time and end time of free facility usage for the user entity linked to the user entity identification information, and compares the usage time of the user entity corresponding to the user entity identification information with a predetermined management time, and if the usage time of the user entity is less than the predetermined management time, generates reward information and grants a benefit according to the reward information to the user entity or the owner of the user entity.

7. The free facilities are provided as an attachment to the facility, It is determined whether the user has used the facility, and only if the user has used the facility, The free facility management system according to claim 6, wherein the benefit is given based on the amount of the free facility management fee.

8. The free facility management system according to claim 7, wherein the profit is given in accordance with the degree of use of the facility, the greater the degree of use, the greater the amount of profit given.

9. 9. The free facility management system according to claim 6, wherein the profit is increased as the usage time is shorter than the predetermined management time.

10. The free facility management system according to any one of claims 6 to 9, wherein the amount of the profit is determined according to the result of a lottery drawn by the user or a random number.

Images