Free facility management system
A system that tracks and rewards early departure or short stays in free parking lots and facilities addresses congestion and inefficiencies by providing benefits, enhancing management efficiency and turnover rates.
Patent Information
- Application Number
- JP2024155199
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-09
- Publication Date
- 2024-11-15
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Free parking lots face challenges in managing congestion and inefficiencies due to the lack of charging mechanisms, while facilities like restaurants struggle to manage seat occupancy based on time usage without separate charges or fines.
A system that uses imaging units to identify vehicles and customers, tracks parking and occupancy times, and rewards users with benefits for early departure or short stays, thereby encouraging timely use and reducing congestion.
The system effectively alleviates congestion in free parking lots and enhances facility management efficiency by incentivizing early departure and short stays, improving turnover rates.
Smart Images

Figure 2024161283000001_ABST
Abstract
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 according to the time from when a vehicle enters the parking lot to when it leaves the parking lot, based on image information of the vehicle entering and leaving the parking lot, and charges the vehicle. In addition, restaurants have introduced POS systems that can handle orders, accounting, tallying up data, and managing customers. [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, in free parking lots, the concept of charging does not exist. Therefore, even if people park for long periods of time in a nuisance manner, causing congestion, it is difficult to punish them.
[0005] In addition, for example, at facilities such as convenience stores, parking is free, but it may not be a good idea to impose separate charges or fines for those who do not use the facility or for those who park for long periods of time that exceed the facility's usage. Thus, unlike paid parking lots, free parking lots have issues that need 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 consideration of such problems, and an object of the present invention is 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 problems, a free parking lot management system according to one embodiment of the present invention comprises an imaging unit that images vehicles entering and leaving a parking space 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 for identifying a vehicle based on the imaging information, and entry time information and exit time information of 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. If the parking time of the vehicle is less than the predetermined management time, the information processing unit generates reward information and grants a benefit corresponding 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 the parking time of a vehicle is less than a predetermined management time, reward information is generated, and a benefit according to the reward information can be granted to the user corresponding to the vehicle. Therefore, instead of imposing a separate fee or penalty for long-term parking, it is possible to give a benefit to a user who, for example, finishes his / her business and leaves the parking lot early. This makes it possible to encourage users of vehicles to leave the free parking lot early, thereby easing congestion in the free parking lot and improving operating efficiency. As a result, the free parking lot can be managed more efficiently. Furthermore, when the free facility management system according to the present invention is applied to a restaurant, a benefit can be given to customers who finish eating quickly and leave the restaurant early, thereby increasing the turnover rate. Effect of the Invention
[0009] As described above, the present invention contributes to alleviating congestion in free parking lots and the like, and enables free parking lots and the like to be managed more efficiently. [Brief description of the drawings]
[0010] [Figure 1] 1 is a schematic plan view showing a convenience store equipped with a free parking management system according to an embodiment of the present invention. [Diagram 2] 2 is a flowchart of a free parking lot management process executed in the free parking lot management system of FIG. 1. [Diagram 3] FIG. 3 is a diagram for explaining one embodiment of the free parking lot management process of FIG. 2. [Figure 4] FIG. 1 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 includes example images of a "standard product consumption time table" and a "reward management table" used in the system. [Diagram 5] This is an example of an image of table-type data of "List of Products Selected by User" handled by the "Short-time Usage 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 usage reward system for restaurants" shown in Figure 4. [Figure 7] This is a diagram explaining the roles of the "cash register" 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 "delivery machine" and the "management database" in the {product delivery 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]This is an example image of a "flat conversion table" used by the "management database" in the "short-time usage reward system for restaurants" in Figure 4 to calculate the "number of reward points awarded this time" from the "total standard time for eating and drinking" and "time spent in the store." DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[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. are different from the actual ones, and the drawings also include parts where the relationship and ratio of dimensions differ from each other. Furthermore, the embodiments described below are merely examples of 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 of a convenience store 1 as a facility. This convenience store 1 has a free parking lot 2 on its premises. In the free parking lot 2, parking positions 3a to 3d for four vehicles are set.
[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 in a management headquarters, and a database server 50. The management computer 40 is connected to the database server 50 so that information can be exchanged 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 users at the cash register counter. Computer 20 is installed within the premises of convenience store 1, for example in a back yard. Computer 20 is connected to management computer 40 so as to be able to send and receive necessary information. Imaging 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 the imaging information of a vehicle entering and leaving the free parking lot 2 acquired by the external camera 10, generates vehicle identification information for identifying a vehicle parked in any of the parking positions 3a to 3d and person identification information for identifying a person riding in the vehicle, and executes processing to transmit the identification information to the management computer 40 together with the time of entry (entry time information).
[0016] Computer 20 also performs image processing to generate personal identification information capable of identifying the person using the cash register counter based on the image information of the user captured by internal camera 30, and executes a process of transmitting 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 captured by the external camera 10, and executes a process of transmitting the vehicle identification information to the management computer 40 together with the time of departure (exit time information).
[0018] The management computer 40 of this embodiment executes a main program for free parking lot management processing as an information processing unit. When the main program for free parking lot management processing 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 the 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 set of vehicle identification information that identifies the 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 or not 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 the 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 leaving time information is acquired by the facility side computer 20. If the leaving time information is 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 leaving the free parking lot 2 (leaving 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, the entry time information and the 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 the process. As the predetermined reward point granting process, various methods can be set as described later, so long as they grant benefits according to the reward information.
[0023] For example, the weighting of the time value according to early departure is determined, and reward points according to the value are given 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 facilities such as convenience stores of the group.
[0024] In addition, as in this embodiment, if a free parking lot is provided in association with a facility, the additional identification information can be further used in the reward point granting process. For example, the reward information can be generated only when a user uses the facility by determining whether the user has used the facility. In addition, the reward points can be granted in accordance with the degree of facility use, with more points being granted the greater the degree of facility use.
[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 the computer 20 of the convenience store 1 confirms through image processing from the image information captured by the external camera 10 that the vehicle C that entered the parking lot has been parked in one of the parking positions 3a to 3d, it generates vehicle identification information using the number acquired from the license plate of the 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 the management computer 40. The management computer 40 records the primary identification information in the database of the 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 from the image information captured by the external camera 10, and transmits the information to the management computer 40. The management computer 40 links the personal identification information of each person with the primary identification information of the corresponding vehicle C and records the information in the database of the database server 50 (step A3 shown in FIG. 3).
[0027] Furthermore, in convenience store 1, internal camera 30 installed near the cash register captures an image of the face and clothing of the person making the payment, and computer 20 of convenience store 1 generates personal identification information that identifies the person who used the service from the image information captured by internal camera 30, and transmits this personal identification information together with the usage information and information on the time of usage to management computer 40 as additional identification information.
[0028] The management computer 40 records each of the acquired information in the database of the database server 50, and judges whether the person has exited a vehicle parked in any parking space. Then, by referring to the records in the database of the database server 50, if the person has exited vehicle C and agreed to the free parking 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 captured by 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 vehicle identification information to the management computer 40. In this example, since the subject vehicle of the generated primary identification information matches the subject vehicle of the entry information, the management computer 40 records this as secondary identification information linked to the primary identification information together with the time of 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 condition is met. If the award condition is met, the management computer 40 executes a process of granting award points to the electronic money ID of the user of the target vehicle. In the award determination table, a predetermined range is set according to the parking time, and the corresponding condition is referred to as appropriate. In this embodiment, if the parking time of the vehicle C that has entered the race 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 of awarding reward points in the reward point awarding process by referring to the reward determination table can be adopted.
[0031] For example, reward points can be given only to the driver of the corresponding vehicle (case 1 in step C2), reward points can be given 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 given only to the one 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 (e.g., a large benefit can be given if the result of the lottery is good).
[0032] Furthermore, various degrees of reward points can be awarded. For example, the additional identification information can be used to set the amount of payment at the register so that the larger the payment amount, the larger the reward points will be given (case 1 in step C3). Also, the amount of time the vehicle is moved faster than a predetermined time is evaluated, and the more time the vehicle is moved faster than the predetermined time, the more reward points are awarded (case 2 in step C3).
[0033] As described above, according to this free parking lot management system, if the parking time of vehicle C is less than a predetermined management time, reward information is generated, and reward points according to the reward information can be awarded as a benefit to the user corresponding to the vehicle C. Therefore, the user corresponding to vehicle C can be encouraged to leave the free parking lot early, which contributes to alleviating congestion in the free parking lot and allows the free parking lot to be managed more efficiently.
[0034] The free parking lot management system according to the present invention is not limited to the above-described embodiment, and 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, when a free parking lot is provided in association with a facility, the additional identification information as described above can be generated and used to, for example, determine whether or not a user has used the facility, and generate reward information 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 now be described.
[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 leaving the store immediately, while the other customer will start reading and continue occupying the seat, causing inconvenience to the other customers and slowing down the turnover of the store's equipment.
[0037] However, in response to such circumstances, the "Short-time usage 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 usage time, and also aims to increase the profits of the restaurant.
[0038] The "reward points" mentioned here are "certificates (tokens) issued by the store" that promise to allow the user to purchase products at a discounted price from the next time they make a purchase, in order to give back to the user a portion of the profits that the store makes by having the user spend time in the store in a short amount of time.
[0039] First, the configuration of the "Short-time use reward system for restaurants" 201 will be described. The "Short-time use reward system for restaurants" 201 is mainly composed of a "management database" 202, a "cash register" 203, a "delivery machine" 204, a "coupon issuing machine" 205, and a "communications 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 make a payment 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. The "checkout cash register" 203 is installed above the "checkout counter" 215.
[0041] <"Delivery Counter"> The "handover counter" 216 is a place (table) where cooked products are handed over to the customer after the accounting process. The "handover counter" 216 is installed near the kitchen in 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 and the like. 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 "cash register" 203 not only processes the general accounting for the products purchased by the user, but also checks the "reward points" held by the user, uses the "reward points" to pay for the accounting, and manages 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 thereafter continues processing for that user. The "accounting cash register" 203 displays the results of the transaction on a "display" 223 provided therein, and at the same time issues a "receipt" 212 showing the results. Such processing is realized by the "checkout register" 203 making a processing request to the "management database" 202 and receiving a result returned from the "management database" 202. The "accounting cash register" 203 transmits the results of a series of accounting processes to a "sales management system" (not shown).
[0044] <"Delivery duty machine"> The "delivery duty machine" 204 manages the delivery of products to users. When the cooked food is handed over to the customer, the customer 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 "lamp" 224 provided to indicate the completion of the process. Such processing is realized by the result returned from the "management database" 202 in response to a processing request from the "handover duty machine" 204 to the "management database" 202.
[0045] <"Coupon issuing machine"> When a customer holds up the "receipt" 212 over the "coupon issuing machine" 205 just before leaving the store after finishing their use, the "coupon issuing machine" 205 reads the "user identification number" and performs a process of awarding "reward points" according to the user's circumstances such as the "length of time spent in the store," and issues a "currently issued reward coupon" 213b listing the results. Such processing is realized by the result returned from the "management database" 202 in response to a processing request made by the "coupon issuing machine" 205 to the "management database" 202.
[0046] <Communications Network> The "communication network" 206 is for data communication between the server machine on which the "management database" 202 is constructed, and the "accounting register machine" 203, the "delivery duty machine" 204, and the "coupon issuing machine" 205, and is composed of a "network cable" 218 and a "network device" 219. In some cases, it is also possible to use "wireless communication."
[0047] <Card> "Card" 211 is distributed to users who request it. "Card" 211 has a "user identification number" printed on it. When the user presents "card" 211 to the cashier at "checkout counter" 215, the "reward points" given up until 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. In addition to showing the general accounting results, it also shows the results of processing related to "reward points", and in particular, the "user identification number". When the user holds the "receipt" 212 over the "handover 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 Issuer" 205 and given to the user. It contains the results of the transaction 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 presents the "previously issued reward coupon ticket" 213a to the cashier when visiting the store, the "reward points" 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 constructed in 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 individual store, and is installed in a data center in the case of a large-scale 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, there are “inquiry processing” 241, “accounting processing” 242, “delivery processing” 243, “grant processing” 244, and “periodic processing” 245 as tasks for processing the data they hold.
[0051] <Data table structure> FIG. 6 is an image of the structure of a data table in the 'management database' 202. This is an image of each field (drawn as a box) placed on top of each record (drawn as a band). A single piece of data (a number or date and time) is recorded in each field according to a predefined purpose. In the data tables of Figures 4 and 5, the horizontal axis represents the records, and the vertical axis represents the fields placed on the records.
[0052] <"Standard time table for eating and drinking products"> The "Standard time spent eating and drinking for each product" table 235 records the standard time that would be 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 spent eating a product table" 235 has the following fields: "Product code" field 251f records the "product code" for that product. "Standard time spent eating" field 252f records the standard amount of time that would be spent eating 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 accounting to reward coupon issuance) by one user. The "reward management table" 236 has the following fields. The "user identification number" field 270f records the "user identification number" of the user. The "total purchase amount" field 271f records the total amount of the products purchased by the user this time. The "total number of purchases" field 272f records the total number of products purchased by the user this time. The "total standard time for eating and drinking products" field 273f records the total standard time that the user will spend eating and drinking all the products purchased by the user. The "start date and time of in-store use" field 274f records the date and time when the user first completed the transaction. The "product delivery date and time" field 275f records the date and time when the user will first receive the product at the "delivery counter" 216. The "number of hours in-store use" field 276f records the number of hours from the "start date and time of in-store use" to the "reward point grant date and time", that is, the number of hours that the user will actually spend eating and drinking. 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 expiration date and time of the "reward points" granted this time. The "reward points remaining" field 279f records the remaining number of "reward points" granted this time. When the "reward points" are used several times, this value is reduced each time until it becomes zero.
[0054] <Processing tasks for the "Management Database"> The "management database" 202 has the following processing tasks for processing the data in the data table. "Inquiry process" 241 performs a process to tally up the "number of reward points" held by the user. "Accounting process" 242 performs a process to cancel the "number of reward points" to be used for the accounting from the "number of reward points" held by the user. "Delivery process" 243 performs a process to mark the date and time when the user receives the product and begins eating and drinking. "Giving process" 244 performs a process to calculate the "number of reward points" to be given this time from the amount of time spent in the store and the product purchased, and gives the "reward points" to the user. "Periodic process" 245 performs a process to delete records that have become outdated and are confirmed to no longer be used periodically (at night, etc., when the store closes) 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 "user identification number" in the case where the user can present a "card" 211. The "card" 211 is issued to a user who requests it. A "user identification number" that is unique to each "card" 211 is assigned and printed on the "card" 211. Also, the "receipt" 212 issued when this "card" 211 is used for the transaction and the "reward coupon ticket 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 a previous visit, the "reward points" granted during the previous visit are linked to the "user identification number" printed on "card" 211, so that by presenting "card" 211 during a current visit, the "reward points" granted during the previous visit can be used to pay for the current visit.
[0057] <If you cannot provide any of these> The following describes a case where a user cannot 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 transaction process, a unique "user identification number" is assigned at the time of the transaction, and this number is written on the issued "receipt" 212 and the "currently issued reward coupon" 213b. For this user, the "reward points" granted the previous time the user visited the store are linked to the "user identification number" assigned at that time, so that when the user visits the store this time, the "reward points" granted the previous time can be used to pay for the 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 within the store> First, let us organize the convenience and behavior of users in a store that may affect the processing of the "Short-time use reward system for restaurants" 201. First, the convenience of a user looking at products may be {just arrived at the store} or {want to purchase additional products}, the items the user presents at the cash register may be {present a "card" 211}, {present a "previously issued reward coupon" 213a}, or {present nothing}, the place where the user receives the products may be {from the "cash register" 215} or {from the "delivery counter" 216}, when clearing the tray after eating and drinking, may be {use the "coupon issuing machine" 205} or {do not use the "coupon issuing machine" 205}, and the convenience after clearing the tray may 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 a 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 cash register" 203 in the scene where "reward points" are inquired. (Figure 7) When a customer comes to the store, he or she will probably first select multiple items and take 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 a "card" 211 or a "previously issued reward coupon ticket" 213a. If such a case occurs, 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 possess. 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: "Management Database"> The role of the "Management Database" 202 in the {Scene when checking "Reward Points"} is as follows. (Figure 7) In the 'management database' 202, the 'reference process' 241 is started and the 'user identification number' 270s is received. <Calculating "Available Reward Points"> The following is the process for calculating the "Number of Available Reward Points." The "Number of Available Reward Points" is the "Number of Reward Points" held by the user in the "Management Database" 202. To calculate this, the values in the "Remaining Reward Points" field 279f of the target records, which may be multiple, are added up. 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 "Number of 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: (1) the date and time in the "Reward Point Expiration Date and Time" field 278f has not expired, and (2) the value in the "Reward Points Remaining" field 279f is not zero. (313) <Response> The “management database” 202 returns the “number of available reward points” 406r to the “accounting register” 203 as a response.
[0062] <Inquiry: Again at the "Accounting Cash Register"> The following is again the role of the "cash register" 203 in the scene where "reward points" are inquired. (Figure 7) The "accounting register" 203 receives the "available reward points" 406r and displays it on the "display" 223. (315) Customers will likely use this notice as a reference when making their next checkout.
[0063] <Accounting: First, the cash register> The following is the role of the "accounting cash register" 203 in the {scene of paying with "reward points"}. (Figure 8) At the "checkout counter" 215, the accounting staff performs the accounting process for the items, which may be multiple, selected by the user. The "item code" 425 and "quantity purchased" 426 of the items, which may be multiple, that the user will purchase are entered (321) into the "checkout register" 203, after which the "checkout register" 203 calculates the total price of the items and calculates tax (322). This is a typical accounting process.
[0064] The "accounting register" 203 creates a "user selected product list" 208s (FIG. 5) to be used for transmission from the "product code" 425 (which may be multiple) and "purchase quantity" 426 entered at this time (323). This “User selected product list” 208s is table type data in which the “product code” 425 and “purchase quantity” 426 of the products, which may be multiple products, that the user will purchase are recorded in multiple records made up of a “purchase product code” field 225f and a “purchase quantity” field 226f. In addition, the “accounting register” 203 sets the total amount of the multiple items that the user is likely to purchase, calculated above, as the “total purchase amount” 271s to be transmitted, and sets the total number of those items as the “total purchase number” 272s to be transmitted.
[0065] The accounting staff informs the user of the "available reward points" 406r displayed on the "display" 223 earlier, then asks how many "reward points" the user would like 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 sent. (324)
[0066] The "accounting register" 203 sends a request 402s for "accounting processing" 242 to the "management database" 202, as well as a "user identification number" 270s, "reward points to be used" 411s, "list of products selected by user" 208s, "total purchase amount" 271s, and "total number of items purchased" 272s. At this time, if the user does not have a "card" 211 or a "previously issued reward coupon" 213a, the value of the "user identification number" 270s remains undetermined.
[0067] <Accounting: In the "Management Database"> The following is the role of the "Management Database" 202 in the {Scene of Accounting 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 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 undecided, the "management database" 202 does nothing after this until the process of generating a new "user identification number."
[0068] <Cancellation process based on "Number of reward points you wish to use"> The following is the {Cancellation process using the "reward points you wish to use"}, that is, the process to cancel the "reward points" to be used for payment in accounting. This process subtracts the value in the "reward points remaining" field 279f of the target records (which may be multiple) by the value in the "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 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 among the records whose value in the "Reward Point Remaining Number" field 279f is not zero, the value in the "Reward Point Remaining Number" field 279f is the oldest, and the value in the "Reward Point Remaining Number" field 279f is subtracted by the value in the received "Number of Reward Points to Use" 411s. If the subtraction does not result in a zero, the value in the "Reward Point Remaining Number" field 279f is subtracted by the value in the "Reward Point Remaining Number" field 279s. If a "shortage" occurs in the value in the "reward points remaining" field 279f, subtract the "shortage" that just occurred from the value in the "reward points remaining" field 279f for the record that matches the condition that the date and time in the "reward point expiration date and time" field 278f is the next oldest. This subtraction process is repeated in this manner until the values in the "reward points to use" 411s have been subtracted from the values in the "reward points remaining" field 279f for all records, which may be multiple. The number that was actually subtracted in this process is set 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 Points Remaining" 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 Points Remaining" field 279f of the records (which may be multiple records) that meet the following conditions: (1) the date and time in the "Reward Point Expiration Date and Time" field 278f has not expired, and (2) the value in the "Reward Points Remaining" field 279f is not zero. (332)
[0071] <Processing for starting in-store use> The following is the {processing for starting in-store use}, which branches out depending on whether it is the "first processing" or the "second or subsequent processing." The "first processing" is {the first transaction processing on that day, or a second transaction processing immediately after the processing that granted "reward points" on the same day}, and the "second or subsequent processing" is {the second or subsequent transaction processing on the same day without the processing that granted "reward points"}.
[0072] <Starting in-store use: 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 "in-store usage start date and time" field 274f is the date and time of that day}, then as the "initial processing", the following {process to generate a new "user identification number"}, {process to generate a new record}, and {process to mark the "in-store usage start date and time"} are performed.
[0073] <Generate a new "user identification number"> Below is the process for generating 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. In the processes following this process, this new record is also the "record to be processed."
[0075] <Mark "In-store start date and time"> The following is a 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 by the customer on 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 also used as the "in-store use start date and time" 274r to be used in the response. The above was the "initial process" for starting in-store use. (333)
[0076] <Start of in-store use: 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: if there is a record in the "reward management table" 236 linked to the received "user identification number" 270s that matches the condition {the date and time in the "in-store use 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 undecided}, the following {processing to obtain the "in-store use start date and time"} and {processing to adjust the "product delivery date and time"} are performed as "processing from the second time onwards". In these processes and the processes that follow them, the record that matches the above condition is the "process target record".
[0077] <Get "in-store usage start date and time"> The following is a 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 made by the customer on that day. The details of this process are as follows: the date and time is extracted from the "in-store use start date and time" field 274f of the "processing target record" and this is set 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 date and time when the product is first handed over to the user from the "delivery counter" 216, and is considered to be the date and time when the user started eating and drinking. However, if the "product delivery date and time" is undecided for the second or subsequent billing process of the day, the product is handed over from the "billing counter" 215 for the first billing, and this "product delivery date and time" must be adjusted. In detail, in the "record to be processed", if the date and time in the "product delivery date and time" field 275f is undecided, the date and time in the "store use start date and time" field 274f is recorded in the "product delivery date and time" field 275f. The above is the "second and subsequent processing" for in-store use. (334) The branched processes will now merge.
[0079] <Calculate "Standard time spent eating and drinking total products"> 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 he or she purchases. This is calculated by matching the "User Selected Product List" 208s with the "Standard Time for Eating Products Table" 235. The details of this process are as follows: while linking the "Purchased Product Code" field 255f of the received "User Selected Product List" 208s (FIG. 5) with the "Product Code" field 251f of the "Standard Product Eating Time Table" 235, the value of the "Number of Purchases" field 256f of the "User Selected Product List" 208s and the number of seconds of 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 taken from the "Total Standard Product Eating Time" field 273f in the "Record to be Processed" (zero in the "initial process"). 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 returns to the "accounting register" 203, in reply, 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.
[0081] <Accounting: Back at the "Accounting Cash Register"> The following is again the role of the "accounting cash register" 203 in the {scene of paying with "reward points"}. (Figure 8) The "accounting 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 "standard total number of hours for eating and drinking" 273r. The “accounting cash 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 this amount, and displays the result on the “display” 223 (342). The user sees the notice and pays the bill. When the accounting staff confirms the payment, the accounting process is completed. The "Accounting Cash Register" 203 sends the results of this accounting process to the "Sales Management System" (not shown). (343) The "accounting register" 203 displays the "user identification number" 270r, "in-store use 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 in addition to the results of general accounting processing, and at the same time prints and issues the "receipt" 212 showing these. (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 {scene of delivering the product}. (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 "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, the date and time at that time is marked only in the case of the first delivery. The "product delivery date and time" is the date and time when the product is first handed over to the customer from the "delivery counter" 216 that day. This date and time is regarded as 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 "award management table" 236 linked to the received "user identification number" 270s that meet the condition that the date and time in the "store use start date and time" field 274f is the date and time of the day, and the date and time in the "award point grant date and time" field 277f is undecided (that is, on records generated on the day for which the "award points" have not yet been granted). If the date and time in the "product delivery date and time" field 275f is undecided (in the case of the first delivery), the "product delivery date and time" field 275f records the date and time at that time, and this date and time is set 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 again the role of the "delivery duty machine" 204 in the {scene of delivering the product}. (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 granting "reward points"}. (Figure 10) When the customer has finished eating and drinking, he or she takes the used tray and the “receipt” 212 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 printed 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 transmits a request 404s for the "granting process" 244 to the "management database" 202, and also transmits the "user identification number" 270s.
[0086] <Grant:"Managed Database"> The following is the role of the "management database" 202 in the {scene of granting "reward points"}. (Figure 10) In the 'management database' 202, the 'assignment process' 244 is initiated and the 'user identification number' 270s is received.
[0087] <Granting "Reward Points"> The following is a series of processes to grant "reward points" to the user. This series of processes consists of multiple processes, such as 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". In addition, 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 more detail, the "record to be processed" is the record in the "reward management table" 236 linked to the received "user identification number" 270s that meets 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 a 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 set as the "award point grant date and time" 277r to be used in the response. (363)
[0089] <Calculating "hours spent in store"> The following 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 of calculating the "number of hours of in-store use" differs depending on the place where the user received the product. If the product was received from the "checkout counter" 215, the date and time in the "product delivery date and time" field 275f is undecided. In this case, the number of seconds elapsed from the date and time in the "start date and time of in-store use" field 274f to the date and time in the "reward point grant date and time" field 277f is calculated, and this is recorded in the "number of hours of in-store use" field 276f, and also becomes the "number of hours of in-store use" 276r to be used in the response. If the product was received from the "delivery counter" 216, the date and time is in the "product delivery date and time" field 275f, and 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 point grant date and time" field 277f is calculated, and this is recorded in the "number of hours of in-store use" field 276f, and also becomes the "number of hours of in-store use" 276r to be used in the response. (364)
[0090] <Calculate the number of reward points awarded this time> The following is the process to calculate the "number of reward points currently given." The "number of reward points currently given" is the "number of reward points" to be given to the user this time. The details of this process are as follows: the "number of hours spent in the restaurant" is evaluated based on the "standard number of hours spent in the restaurant" which is the standard number of hours the user would spend eating and drinking this time, which is derived from the products the user purchased, and the shorter the "hours spent in the restaurant", the more "award points" are awarded, and further, the more "award points" are awarded to the user who presented the "card" 211. At least the following two methods are conceivable for this.
[0091] The details of the first method are as follows: subtract the value in the "Number of hours spent in the store" field 276f from the value in the "Total standard hours spent eating and drinking" field 273f, and if the result of the subtraction is greater than zero, multiply the subtraction result by the "Use A coefficient", and record the multiplication result as the "Number of reward points given this time" in the "Remaining number of reward points" field 279f, and also set it as the "Number of reward points given this time" 416r to be used in the response. In addition, the setting value of the "Use A coefficient" is set to a larger value for the user who presents the "Card" 211 compared to the "Use A coefficient" for the user who does not present the "Card" 211. The "Use A coefficient" is set to an optimal value for converting the number of hours into the "number of reward 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 allocated to each square for the "total standard number of hours spent on products and drinks" field 273f is placed; in the squares on the other axis, a numerical value representing the range allocated to each square for the "number of hours 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 given this time" is placed. The "number of reward points given this time" is calculated by taking 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, and further, two such "flat conversion tables" are prepared, and the "flat conversion table" for one user who presents "card" 211 is set so that larger values are placed in each box compared to the other "flat conversion table" for a user who does not present "card" 211. The "number of reward points given this time" obtained from this is recorded in the "reward points remaining" field 279f, and is also set as the "number of reward points given 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 way of calculating, in the process of calculating the "Number of reward points given this time" described above, the "Number of hours spent in the store" was evaluated based on the "Standard hours of total products and drinks" to calculate the "Number of reward points given this time", but instead of using the "Standard hours of total products and drinks" as the basis, it is also possible to calculate the "Number of hours spent in the store" by evaluating it based on the numerical 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 consumption of products and drinks" as a standard, the "Time spent in the store" can be evaluated based on the value obtained by multiplying the value in the "Total number of purchases" field 272f by the "Use C coefficient" to determine the "Number of reward points given this time." The "Use C coefficient" is set to an optimal value for converting the "Total number of purchases" into the number of hours. The above is how to calculate the number of reward points awarded this time. (365)
[0095] <Get reward point expiration date> 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 currently awarded reward points." This is designed so that the larger the "number of currently awarded reward points" is, the more valid period dates and times are given, and further so that the user who presents the "card" 211 is given more valid period dates and times, 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 given this time" 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 date and time at that time, record the result of this addition in the "Reward point use expiration date and time" field 278f, and set it as the "Reward point use expiration date and time" 278r to be used in the reply. In addition, the setting value of the "Use D coefficient" is set to a larger value for the "Use D coefficient" for a user who presents the "Card" 211 compared to the "Use D coefficient" for a user who does 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 concept, a method of calculating the "reward point usage expiration date and time" 278r by simply determining one validity period date and time can be considered. The details of this process are to add the validity period date and time, which is set to a fixed value, to the current date and time, and record this addition result 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 obtain the "reward point expiration date and time." (366) The above is a series of processes {to award "reward points"} consisting of multiple processes, such as marking the "reward point awarding date and time", calculating the "number of hours spent in the store", calculating the "number of reward points awarded 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 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 again the role of the "coupon issuing machine" 205 in the {scene of awarding "reward points"} (Figure 10). The “coupon issuing machine” 205 receives “reward point grant date and time” 277r, “number of hours used in store” 276r, “number of reward points granted 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 includes the "user identification number" 270r, "reward point grant date and time" 277r, "number of hours used in the store" 276r, "number of reward points granted this time" 416r, "reward point expiration date and time" 278r, and "number of available reward points" 408r. (369) The customer receives it and leaves the store. This "reward coupon issued this time" 213b can be used to pay for the next purchase the next time the customer visits the store.
[0101] <Summary> We have explained in detail above how the "Short-time restaurant use reward system" 201 functions from when a user enters a restaurant, pays for the selected product, eats, and leaves the restaurant. In particular, the "reward points given this time" 416r is written on the "reward coupon issued this time" 213b received by the user, and this value is calculated based on the "standard time for total product and drink consumption" that the user would spend on eating and drinking this time, which is derived from the products purchased by the user, and the shorter the "time spent in the restaurant", the more "reward points" are given. The "reward points given this time" is the amount written on the "token" that the user can use to pay the bill the next time he or she visits the restaurant.
[0102] In this case, if the user is able to finish using the store in a shorter time, the expenses for the in-store equipment that were spent on the products purchased by the user will become a profit for the store, and by returning a portion of that to the user as "reward points", the user will be able to be provided with products at a fairer price. This is expected to increase 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 "in-store usage time" will be shortened, which is expected to increase the turnover rate of the dining space, which tends to get crowded, and increase the opportunities for other users to use the dining space, which is expected to increase the number of times other users use the store, and increase the store's sales. In other words, the "short-time restaurant usage reward system" 201 of 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 without departing from the essence of the present invention. For example, this system can be applied to paid coin lockers (priced at 400 yen / day) 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 usage time of the coin locker is within the normal usage time for such facilities (e.g., 3 hours), reward information can be generated to give the user benefits such as points that can be used at the facility. Also, in a city restaurant, during a time period such as lunchtime, reward information may be provided to customers who finish eating and drinking within an ideal stay time (e.g., 15 minutes) that allows for a desired turnover rate for the restaurant and leave, so that the restaurant may be given a service such as a free dish the next time they visit.In this case, since the restaurant provides food and drink and is in the business of receiving payment for it, the seats themselves can be considered to be provided free of charge, and the above-mentioned system regarding free parking 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, reward information may be provided 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 Server 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 "Communications Network" 208s "User selected product list" 211 "Card" 212 "Receipt" 213a "Last 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 hours table for eating and drinking products" 236 "Reward Management Table" 241 "Inquiry Processing" 242 "Accounting Procedures" 243 "Delivery Processing" 244 "Processing 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 product consumption standard time" 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 in store" field 276r “Number of hours used in store” 277f "Reward points awarded date and time" field 277r "Reward point award date and time" 278f "Reward points expiry date and time" field 278r "Reward point 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 a query 321 Enter the information of the product selected by the user 322 Calculate the total price and tax of the item 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 you wish to use" 332 Calculate the "Number of available reward points" after the cancellation process 333 "Initial Processing" for Starting In-Store Use 334 "Processing for the second or subsequent times" regarding in-store use 336 Calculate the "Total Standard Time for Eating and Drinking" 341 Accounting treatment including the number of cancelled reward points 342 Output the payment amount calculation result 343 Transmit the results of accounting processing to the "Sales Management System" 344 Print general accounting results and "reward points" results 351 Enter your user identification number. 353 Mark "Product delivery date and time" 355 Output the results of the delivery process 361 Enter your user identification number. 363 Mark "Reward points awarded 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 granting process 369 Output the result of the grant process 401s "Referral Processing" Requests 402s "Accounting" Request 403s "Process for Delivery" Request 404s "Processing for Grant" Request 406r "Number of available reward points" 407r "Number of available reward points" 408r "Number of 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 a parking space 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 of 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 corresponding to the reward information to the user corresponding to the vehicle.
2. The free parking lot is provided in association with the facility, It is determined whether the user has used the facility, and only if the user has used the facility The free parking management system according to claim 1, wherein the benefit is given according to the amount of the parking lot.
3. 3. The free parking management system according to claim 2, wherein the profit is determined according to the degree of use of the facility, the greater the degree of use, the greater the profit is.
4. 4. The free parking 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 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 is information that identifies a user of a 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 a user entity based on the target identification information, and information on the start time of free facility usage and the end time of free facility usage of 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 corresponding to the reward information to the user entity or the owner of the user entity.
7. The free facilities are provided as an accessory 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 fee.
8. The free facility management system according to claim 7, wherein the profit is based on 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 utilization 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.
Citation Information
Patent Citations
Service providing apparatus
JP2004178326A
Parking fee collecting device and parking fee collecting method
JP2004280234A
Parking lot management system and portable recording medium
JP2008059341A
Customer guidance support system and customer guidance support method
JP2012068751A
Service provision device, service provision method, and program
JP2015153194A
