Service provision system and program

Abstract

To provide a service provision system that can issue coupons based on the purchase or the like of commodities at partner stores, without requiring access to other systems or being restricted by the type of a receipt.SOLUTION: A terminal program 38 implemented on a user terminal 12 acquires payment image data generated from a screenshot of an electronic payment screen or payment image data generated by capturing an image of a receipt (S137, S141). The terminal program 38 reads a payment store name from the payment image data (S143). The terminal program 38 transmits the read payment store name to a management server 11 (S145). A server program 27 of the management server 11 issues a coupon (S158, S159) on the basis of the fact that the payment store name matches a partner store name (S148: Yes). The coupon is used to reduce or discount usage fees at an operating store.SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a system used to provide a space rental service by the hour. [Background technology]

[0002] Patent Document 1 discloses an information processing system for settling parking fees attached to a commercial facility, which provides discounts based on the purchase prices of products at the commercial facility.

[0003] Specifically, the information processing system includes an information processing server, a payment management server, and a terminal device carried by the user (parking lot user). The payment management server performs electronic payment for the user's purchase of goods at the commercial facility and transmits the payment history to the information processing server. The information processing server calculates the usage fee by applying a discount to the regular usage fee based on the parking time and payment history. Alternatively, the user receives a receipt issued when purchasing goods at the commercial facility. The user has the terminal device read the information code printed on the receipt. The terminal device transmits the payment information indicated by the information code to the information processing server. The information processing server calculates the usage fee based on the acquired payment information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 7241950 Summary of the Invention [Problem to be solved by the invention]

[0005] In the system disclosed in Patent Document 1, the information processing server obtains payment history from the payment management server, and therefore must conform to the specifications of the payment management server. However, there are multiple electronic payment systems that can be used in commercial facilities. In other words, there are various payment management servers. Therefore, the information processing server must be able to support various payment management servers. Furthermore, every time a new electronic payment system is introduced, the specifications of the information processing server must be changed.

[0006] In addition, in the system disclosed in Patent Document 1, the terminal device reads the information code printed on the receipt. However, there are also receipts that do not have an information code such as a barcode or QR code (registered trademark). In such cases, the information processing server cannot obtain the payment history from the receipt.

[0007] As described above, the system disclosed in Patent Document 1 has problems in both cases, electronic payment and receipts.

[0008] The present invention has been made in consideration of the above circumstances, and its purpose is to provide a service provision system that can issue coupons based on the purchase of products at affiliated stores, regardless of the specifications of other systems or the type of payment record sheet (receipt). [Means for solving the problem]

[0009] (1) A service providing system according to the present invention includes a management server having a first communication interface connected to the Internet, a server memory storing a management database, and a first controller; and a user terminal having a second communication interface connected to the Internet, a terminal memory storing user identification information for identifying a user, an input interface, a display, a camera with an image sensor, and a second controller. The management database stores affiliated store names and store identification information in association with each other. The second controller executes a check-in application process that transmits a check-in application including the store identification information and the user identification information to the management server via the second communication interface, a payment image data acquisition process that, based on receiving a first instruction via the input interface, captures an image of a payment record sheet using the camera to acquire it as payment image data, or, based on receiving a second instruction via the input interface, acquires screen data of an electronic payment screen displayed on the display as payment image data, and, after executing the check-in application process, transmits a coupon issuance application including the payment image data or the payment store name acquired from the payment image data and the user identification information to the management server via the second communication interface.The first controller executes the following processes: a check-in registration process for registering the store identification information and the user identification information contained in the check-in application in association with a check-in date and time in the management database based on receiving the check-in application through the first communication interface; a payment store name acquisition process for acquiring a payment store name obtained from the payment image data contained in the coupon issuance application or a payment store name contained in the coupon issuance application based on receiving the coupon issuance application through the first communication interface; a determination process for acquiring the affiliated store name associated in the management database with the user identification information contained in the coupon issuance application and determining whether the acquired affiliated store name matches the payment store name; and a coupon issuance process for issuing a coupon for the payment amount to the store based on determining in the determination process that the affiliated store name matches the payment store name. The first controller or the second controller executes a reading process for acquiring the payment store name from an image indicated by the payment image data.

[0010] When a user submits a check-in request using a user terminal, the user identification information, the store identification information of the store used by the user, and the check-in date and time are associated and registered in the management database. In the management database, store identification information and affiliated store names are pre-associated. That is, when a user checks in, the user identification information and affiliated store name are associated. Meanwhile, the user purchases a product at an affiliated store and receives a receipt or payment record sheet, which is a receipt issued by the affiliated store, or makes an electronic payment. The user captures an image of the payment record sheet using the camera on the user terminal, or captures screen data of the electronic payment screen displayed on the user terminal by taking a screenshot, for example. That is, the user terminal acquires payment image data in response to the user's instructions. The user terminal transmits a coupon issuance request, including the payment image data or the payment store name read from the payment image data, to the management server. If the management server determines that the payment store name included in the coupon issuance request or the payment store name read from the payment image data is an affiliated store that is affiliated with the store used by the user, it issues a coupon to the user. The service provision system according to the present invention obtains the payment store name from the captured image (payment image data) of the payment record sheet, and can therefore obtain the payment store name even if the payment record sheet does not contain code information. Furthermore, the service provision system according to the present invention obtains the payment store name from the screen data (payment image data) of the electronic payment screen, and does not obtain the payment store name directly from the data sent to the user terminal by the electronic payment server that performed the electronic payment. Therefore, the service provision system according to the present invention can obtain the payment store name regardless of the type of data format sent to the user terminal by the electronic payment server, such as HTML, PDF, or a document file. As a result, the service provision system according to the present invention can issue coupons based on the purchase of products at affiliated stores, regardless of the specifications of other systems or the type of payment record sheet issued by the affiliated store.

[0011] (2) The reading process may include a process of acquiring a payment date and time from the payment image data. In the determination process, the first controller sets a period during which the user is not in the store as a valid period based on the entry / exit record including the check-in date and time registered in the management database, and further determines whether the payment date and time is within the valid period. If it is determined that the payment date and time is within the valid period and the affiliated store name and the payment store name match, the first controller executes the coupon issuing process.

[0012] While the user is in the store, the user cannot make purchases at affiliated stores. The management server issues a coupon if a purchase is made while the user is not in the store, but does not issue a coupon if a purchase is made while the user is in the store. As a result, the service providing system according to the present invention can reject fraudulent coupon issuance requests.

[0013] (3) The validity period may include a period of a predetermined time before the check-in date and time.

[0014] A coupon is issued even if the user checks in and enters the store after purchasing a product or the like at an affiliated store.

[0015] (4) The service providing system according to the present invention may further include a door locking device installed at an entrance of the store, and a store terminal having a third communication interface and a third controller connected to the Internet and locking and unlocking the door locking device. The second controller further executes a temporary leave request process for sending a temporary leave request including the store identification information and the user identification information to the management server via the second communication interface, and a re-entry request process for sending a re-entry request including the store identification information and the user identification information to the management server via the second communication interface. The first controller further executes an unlock instruction sending process for sending an unlock instruction to the store terminal via the first communication interface based on receiving the temporary leave request or the re-entry request via the first communication interface, and a temporary leave registration process for registering a temporary leave date and time and a re-entry date and time in the management database in association with the user identification information. The entry and exit record includes a check-in date and time, a temporary leave date and time, and a re-entry date and time. The validity period includes the period from the time of temporary leaving the room to the time of re-entering the room.

[0016] The entry / exit record includes the check-in date and time, the temporary exit date and time, and the re-entry date and time, and the validity period includes the period from the temporary exit date and time to the re-entry date and time, so even if the user purchases a product or the like at an affiliated store while temporarily leaving the room, the coupon is issued without the coupon issuance application being rejected.

[0017] (5) The reading process may include a process of acquiring at least one of a payment date and time and a payment amount from the payment image data. The coupon issuance process includes a process of registering the payment store name and at least one of the payment date and time and the payment amount in the management database. In the determination process, the first controller further determines whether at least one of the payment date and time and the payment amount acquired in the payment store name acquisition process matches at least one of the payment date and time and the payment amount registered in the management database, where at least one of the payment date and time and the payment amount for which a coupon has been issued, and executes the coupon issuance process based on a determination that at least one of the payment date and time and the payment amount acquired in the payment store name acquisition process does not match at least one of the payment date and time and the payment amount registered in the management database and that the affiliated store name and the payment store name match.

[0018] If a user makes a coupon issuance request again using a payment record sheet or electronic payment for which a coupon issuance request has already been made, the coupon issuance request will be rejected as an illegal coupon issuance request.

[0019] (6) The reading process may include a process of acquiring a payment date and time from the payment image data. In the determination process, the first controller further determines whether the coupon issuance request date and time is within a valid period from the payment date and time until a predetermined time has elapsed, and executes the coupon issuance process based on the determination that the coupon issuance request date and time is within the valid period and that the affiliated store name and the payment store name match.

[0020] If the time that has elapsed since the purchase of a product or the like until the application for coupon issuance exceeds a predetermined time, the application for coupon issuance is rejected as an illegal application for coupon issuance.

[0021] (7) The first controller may further execute a list screen data transmission process to transmit store list screen data including the store identification information and the store name, affiliated store name, and affiliated store type associated in the management database to the user terminal via the first communication interface. The second controller further executes a first display process to display on the display a store list screen indicated by the store list screen data received via the second communication interface.

[0022] The user terminal displays a store list screen on the display, which includes store names, affiliated store names, and affiliated store types. The affiliated store types include, for example, convenience stores, bookstores, cafes, laundromats, and business hotels. The user can search for and make a reservation for a store attached to a convenience store, a store attached to a bookstore, or a store without an affiliated store, among the listed stores, according to their preference.

[0023] (8) The second controller may further execute a reservation request process that transmits a reservation request including the store identification information, the reservation date and time, and the user identification information to the management server via the second communication interface. The first controller, based on receiving the reservation request via the first communication interface, executes a reservation registration process that associates the store identification information, the reservation date and time, and the user identification information and registers them in the management database, and a first notification process that transmits, to the user terminal via the first communication interface, first notification screen data showing a first notification screen having the store identification information included in the reservation request and the affiliated store name associated in the management database. The second controller, based on receiving the first notification screen data via the second communication interface, further executes a second display process that displays the first notification screen on the display.

[0024] When a user makes a reservation at a store, the names of affiliated stores that are affiliated with the store for which the reservation is made are displayed on the user terminal. The user can check the names of affiliated stores displayed at the time of reservation. As a result, user convenience is improved.

[0025] (9) The first controller may further execute a second notification process to transmit, based on receiving the temporary leave request through the first communication interface, second notification screen data indicating a second notification screen having the affiliated store name and coupon notification information to the user terminal as a response to the temporary leave request. The second controller may further execute a third display process to display the second notification screen on the display based on receiving the second notification screen data through the second communication interface.

[0026] When a user applies to temporarily leave the room, the name of the affiliated store and coupon notification information are displayed on the user's terminal. The coupon notification information includes the conditions for issuing the coupon. By reminding the user of the existence of the coupon when temporarily leaving the room, the user can be encouraged to purchase products at the affiliated store.

[0027] (10) The fees paid to the store may include a store usage fee based on the time the store is used and a facility usage fee for the use of facilities installed in the store.

[0028] The facilities installed in the store include, for example, individual booths, massage chairs, multi-function devices with copy functions, personal computers, etc. The coupon may be used to discount or reduce the usage fees for these facilities as well as the usage fees for the store.

[0029] (11) The second controller may further execute a checkout request process to send a checkout request including the store identification information, the user identification information, and an instruction to use the coupon to the management server via the second communication interface. The first controller, based on the fact that the checkout request received via the first communication interface includes the instruction to use, executes a usage time calculation process to calculate a usage time based on the user identification information included in the checkout request and the check-in date and time associated in the management database, and a fee calculation process to calculate the payment fee based on the usage time and the coupon indicated in the instruction to use.

[0030] At the time of checkout, the user can freely decide whether or not to use the coupon.

[0031] (12) The first controller may further execute a judgment data registration process for acquiring sample image data showing a sample of the payment record sheet through the first communication interface, acquiring counterfeit judgment data from the sample image data, and registering the counterfeit judgment data in the management database, and a suitability determination process for determining whether the payment image data is suitable based on the counterfeit judgment data. The first controller executes the coupon issuance process based on the determination that the payment image data is suitable in the suitability determination process and that the affiliated store name and the payment store name match in the determination process.

[0032] In the appropriateness determination process, the first controller compares the counterfeit determination data registered in the management database with the payment image data to determine the appropriateness of the payment record sheet indicated by the payment image data, i.e., whether the payment record sheet indicated by the payment image data is a counterfeit receipt or a legitimate receipt. The first controller issues a coupon if the payment record sheet indicated by the payment image data is a legitimate receipt. Therefore, the service provision system of the present invention can prevent coupons from being erroneously issued due to counterfeit receipts.

[0033] (13) A program according to the present invention includes a server program implemented in a management server having a first communication interface connected to the Internet, a server memory for storing a management database, and a first computer, and a terminal program implemented in a user terminal having a second communication interface connected to the Internet, a terminal memory for storing user identification information for identifying a user, an input interface, a display, a camera with an image sensor, and a second computer. The management database registers names of affiliated stores in association with store identification information. The terminal program causes the second computer to execute the following: a check-in application process that sends a check-in application including the store identification information and the user identification information to the management server via the second communication interface; a payment image data acquisition process that, based on receiving a first instruction via the input interface, captures an image of a payment record sheet using the camera and acquires it as payment image data, or, based on receiving a second instruction via the input interface, acquires screen data of the payment screen displayed on the display as payment image data; and a coupon application process that, after executing the check-in application process, sends a coupon issuance application that includes the payment image data or the payment store name acquired from the payment image data and the user identification information to the management server via the second communication interface.The server program causes the second computer to execute the following: a check-in registration process for, based on receiving the check-in request through the first communication interface, correlating the store identification information and the user identification information contained in the check-in request with a check-in date and time and registering them in the management database; a payment store name acquisition process for, based on receiving the coupon issuance request through the first communication interface, acquiring a payment store name obtained from the payment image data contained in the coupon issuance request or a payment store name contained in the coupon issuance request; a determination process for acquiring the affiliated store name associated in the management database with the user identification information contained in the coupon issuance request and determining whether the acquired affiliated store name matches the payment store name; and a coupon issuance process for issuing a coupon for the payment amount to the store based on the determination process that the affiliated store name matches the payment store name. The server program or the terminal program causes the first computer or the second computer to execute a reading process for acquiring a payment store name from an image indicated by the payment image data.

[0034] The present invention can also be considered as a program. [Effects of the Invention]

[0035] According to this invention, coupons can be issued based on the purchase of products at affiliated stores without accessing other systems or regardless of the type of payment record sheet. [Brief explanation of the drawings]

[0036] [Figure 1] FIG. 1 is a configuration diagram and a functional block diagram of a service providing system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing the user management database. [Figure 3] FIG. 3 is a diagram showing the store management database. [Figure 4] FIG. 4 is a flowchart of the reservation process. [Figure 5] Figure 5(A) is a diagram showing a store list screen, Figure 5(B) is a diagram showing a store selection screen, Figure 5(C) is a diagram showing a date and time specification screen, and Figure 5(D) is a diagram showing a reservation completion notification screen. [Figure 6] FIG. 6 is a flowchart of the check-in process. [Figure 7] FIG. 7(A) is a diagram showing a check-in screen, FIG. 7(B) is a diagram showing a reading screen, FIG. 7(C) is a diagram showing a check-in application screen, and FIG. 7(D) is a diagram showing a check-in completion notification screen. [Figure 8] FIG. 8 is a flowchart of the temporary exit process. [Figure 9] FIG. 9(A) is a diagram showing a temporary exit screen, FIG. 9(B) is a diagram showing a check-in request screen, and FIG. 9(C) is a diagram showing an unlock notification screen. [Figure 10] FIG. 10 is a flowchart of the re-entry process. [Figure 11] FIG. 11(A) is a diagram showing a re-entry screen, FIG. 11(B) is a diagram showing an unlock notification screen, FIG. 11(C) is a diagram showing a confirmation / unlock notification screen, and FIG. 11(D) is a diagram showing a coupon application screen. [Figure 12] FIG. 12 is a flowchart of the coupon issuing process. [Figure 13] Figure 13(A) is a diagram showing the first procedure screen, Figure 13(B) is a diagram showing the second procedure screen, Figure 13(C) is a diagram showing the third procedure screen, and Figure 13(D) is a diagram showing the coupon issuance notification screen. [Figure 14] FIG. 14 is a flowchart of the checkout process. [Figure 15] FIG. 15(A) is a diagram showing a checkout screen, FIG. 15(B) is a diagram showing a checkout completion notification screen, and FIG. 15(C) is a diagram showing a payment notification screen. [Figure 16] FIG. 16 is a diagram showing a store management database according to the third modification. [Figure 17] FIG. 17 is a flowchart of the coupon issuing process according to the third modification. DETAILED DESCRIPTION OF THE INVENTION

[0037] An embodiment of the present invention will be described below. Note that the embodiment described below is merely an example of the present invention, and it goes without saying that the embodiment of the present invention can be modified as appropriate without departing from the spirit of the present invention. For example, the processes executed by the management server 11 and the user terminal 12 may be partially omitted, the order of the processes may be changed, other processes may be replaced, or other processes may be added, without departing from the spirit of the present invention. Furthermore, icons, characters, radio buttons, etc. on the screen displayed on the display 34 of the user terminal 12 may be omitted, their display positions may be changed, or they may be replaced with other text boxes, icons, radio buttons, menus, characters, etc., without departing from the spirit of the present invention.

[0038] [Overview of Service Provision System 10] In this embodiment, a service providing system 10 shown in FIG. 1 will be described. The service providing system 10 is operated by a service provider. The service provider is a party that provides users with a service of renting space by the hour. The space rented by the hour is set up in a store operated by the service provider (hereinafter also referred to as an "operated store").

[0039] All or some of the managed stores are attached to affiliated stores. Affiliated stores are stores operated by affiliated businesses that have a business partnership with the service provider. Affiliated stores include retail stores such as convenience stores, restaurants such as cafes, bookstores, laundromats, and business hotels. When a user purchases a product at an affiliated store, the service provider issues a coupon based on the purchase amount of the product. The coupon is used to reduce or discount the usage fee for the space rented by the hour. The attachment of an managed store is expected to increase sales at the affiliated store. On the other hand, the service provider receives a margin from the affiliated business, for example. Note that a purchase of a product means the purchase of a product sold at the affiliated store as well as the receipt of a service provided at the affiliated store. Furthermore, the purchase amount of a product means the amount paid by the user in exchange for the purchase price of the product and the receipt of a service provided at the affiliated store. The usage fee for the space rented by the hour, i.e., the store usage fee, is an example of a payment fee related to the store.

[0040] The space rented by the service provider by an hour may be part of the premises of an affiliated store. In other words, the service provider may be entrusted by the affiliated store to use part of the premises of the affiliated store as an operating store. The service provider may also enter into a contract with the operator of an existing or new store located near an existing operating store, and designate the existing or new store as an affiliated store. The service provider may also rent out part of the premises of the operating store to the affiliated store.

[0041] In this way, the service providing system 10 is a system that provides users with a space rental service by the hour, a system that issues coupons for the purchase of products at affiliated stores, and a system that accepts the use of coupons and makes payments.

[0042] As shown in FIG. 1, the service providing system 10 includes a management server 11, a user terminal 12, a store terminal 13, and a door lock device 14.

[0043] [Door lock device 14] The door lock device 14 is installed on a door attached to the entrance of the managed store. The door lock device 14 is a device that automatically locks and unlocks the door.

[0044] The door lock device 14 includes a housing and a deadbolt (not shown), a drive unit 52, a control unit 51, and a communication interface 53. The housing is attached to a wall to which the door is attached. The deadbolt is slidably supported by the housing. The drive unit 52 slides the deadbolt. The drive unit 52 is, for example, a solenoid. The control unit 51 controls the drive of the drive unit 52. The control unit 51 is, for example, a microprocessor. The communication interface 53 is connected to a LAN (local area network) attached to the managed store by wire or wirelessly. The door lock device 14 is connected to the store terminal 13 via the LAN. Alternatively, the communication interface 53 may be directly connected to the store terminal 13 by a communication cable.

[0045] The control unit 51 of the door lock device 14 drives the drive unit 52 in response to a lock command input from the store terminal 13 via the communication interface 53. The drive unit 52 slides the deadbolt to lock (lock) the door. The control unit 51 drives the drive unit 52 in response to an unlock command input from the store terminal 13 via the communication interface 53. The drive unit 52 slides the deadbolt to unlock (unlock) the door. Alternatively, the control unit 51 locks the door at all times, and unlocks it for a certain period of time when an unlock command is input.

[0046] A commercially available electric lock or electronic lock is used as the door lock device 14. However, any door lock device 14 may be used as long as it can unlock the door by a command input from the store terminal 13. The following describes an example in which a door lock device 14 is used that locks the door at all times and unlocks it for a certain period of time only when an unlock command is input.

[0047] [QR Code (registered trademark)] A QR code (registered trademark) is attached to the door or wall of the managed store. The QR code (registered trademark) is attached to both the exterior and interior sides of the door and wall. The QR code (registered trademark) has a code that can read the store ID. The QR code (registered trademark) is used by users to check in, check out, temporarily leave the store, and re-enter.

[0048] The store terminal 13 is a personal computer, tablet (registered trademark), smartphone (registered trademark), or the like installed in a managed store. The store terminal 13 includes a CPU 41, which is a central processing unit, a memory 42, and a communication interface 43. The CPU 41 is an example of a third controller.

[0049] The memory 42 is configured by, for example, a ROM, a RAM, an EEPROM, a hard disk drive, a solid state drive, a USB memory, or other storage elements and storage devices.

[0050] The memory 42 stores an OS 46 and a store program 48 executed by the CPU 41, and communication settings such as communication addresses required for communication with the door lock device 14 and the management server 11.

[0051] The communication interface 43 is connected to a LAN provided in the store. The store terminal 13 can communicate with the door lock device 14 through the LAN. The LAN has a gateway device (not shown), such as a router, connected to the Internet 15. The store terminal 13 can communicate with the management server 11 through the LAN, the gateway device, and the Internet 15. The communication interface 43 is an example of a third communication interface.

[0052] Upon receiving an unlock instruction from the management server 11 via the LAN, the gateway device, and the Internet 15, the store terminal 13 transmits an unlock command to the door lock device 14 via the LAN.

[0053] [User terminal 12] The user terminal 12 is a communication terminal that can be carried by a user, such as a smartphone (registered trademark) or a tablet (registered trademark). The user terminal 12 has a CPU 31, which is a central processing unit, a memory 32, a communication interface 33, a display 34, an input interface 35, and a camera 16. The CPU 31 is an example of a second controller and a second computer. Although two user terminals 12 are shown in FIG. 1, there may be three or more user terminals 12.

[0054] The memory 32 is configured by, for example, a ROM, a RAM, an EEPROM, a hard disk drive, a solid state drive, a USB memory, or other storage elements and storage devices. The memory 32 is an example of a terminal memory.

[0055] The memory 32 stores an OS 36, which is an operating system, a browser 37, and a reading program 39. The reading program 39 is, for example, an OCR (Optical Character Recognition / Reader), and is a program that reads characters from image data.

[0056] The memory 32 also has a storage area capable of storing a terminal program 38 and a user ID. The terminal program 38 is a program provided to the user by a service provider. The terminal program 38 may be a so-called application program, or a so-called plug-in application that extends the functionality of the browser 37. Alternatively, the terminal program 38 may be html data including JavaScript. The terminal program 38 and the user ID are stored in the memory 32 by being downloaded to the user terminal 12 by the user. The user ID is an example of user identification information.

[0057] The communication interface 33 is an interface for transmitting and receiving information and data via wireless communication such as mobile communication or Wi-Fi. The communication interface 33 may be a single interface or multiple interfaces. The communication interface 33 is an example of a second communication interface.

[0058] The input interface 35 is, for example, a transparent film-like touch sensor overlaid on the display 34, or a microphone for voice input.

[0059] Camera 16 has a lens and multiple image sensors. Camera 16 outputs image data generated by capturing an image. In other words, camera 16 is a so-called digital camera. Camera 16 is used to capture images of QR codes (registered trademark) attached to managed stores and to capture images of receipts or invoices given to users when they purchase products at affiliated stores.

[0060] For example, the user launches browser 37, accesses a web page provided by the service provider, and enters their name (first and last name), age, gender, address, etc. on the web page to apply for membership in the service provided by the service provider. Based on the application for membership, management server 11 returns a server address, a user ID, and a terminal program 38 to user terminal 12. That is, the server address, user ID, and terminal program 38 are downloaded (installed) to user terminal 12. The downloaded server address, user ID, and terminal program 38 are stored in memory 32.

[0061] The server address is a global IP address assigned to the management server 11. The user ID is identification information that individually identifies a user, a user terminal 12, or a terminal program 38.

[0062] The user uses the downloaded terminal program 38 to make reservations for managed stores (hourly rental spaces), check in, apply for coupon issuance, and check out.

[0063] [Administration Server 11] The management server 11 is a server owned by a service provider or a rental server that the service provider has the right to use, etc. The management server 11 may be one server or multiple servers (so-called cloud servers).

[0064] The management server 11 includes a CPU 21, which is a central processing unit, a memory 22, a communication interface 23, and a clock module 24. The CPU 21 is an example of a first controller and a first computer.

[0065] The communication interface 23 is connected to the Internet 15 via a gateway device, or is directly connected to the Internet 15. The communication interface 23 is an example of a first communication interface.

[0066] The clock module 24 is a module that outputs date and time information. Instead of providing the clock module 24 in the management server 11, the server program 27 may have a function of acquiring date and time information via the Internet 15.

[0067] The memory 22 is configured by, for example, a ROM, a RAM, an EEPROM, a hard disk drive, a solid state drive, a USB memory, or other storage elements and storage devices. Alternatively, a part of the memory 22 may be memory included in a so-called storage server. The memory 22 is an example of server memory.

[0068] The memory 22 stores an operating system OS 26, a server program 27, a user management database, and a store management database. The user management database and the store management database are examples of management databases.

[0069] The server program 27 has a communication function for communicating with the user terminal 12, a management function for the management database, a function for making reservations, checking in, checking out, temporarily entering and leaving the store, and making payments, and a function for issuing coupons. The server program 27 may be a collection of multiple modules (programs) that respectively execute each of the above functions, or may be a single program.

[0070] [User Management Database] As shown in Figure 2, the user management database is a database that manages information about users (top section), reservation information about reservations at managed stores (middle section), and usage information about use of managed stores (bottom section).

[0071] The user management database has multiple columns and multiple records. Each column is assigned an item name. One column is assigned the item name "User ID." A user ID is registered in each field of the column with the item name "User ID." Each record is individually identified by the user ID. In other words, one record corresponds to one user.

[0072] When the server program 27 receives the membership application sent by the user terminal 12, it generates a new record in the user management database, generates an unused unique user ID, and registers the generated user ID in the new record.

[0073] Other columns in the user management database are given the item names "Name," "Sex," "Age," "Address," and "Payment Information."

[0074] In each field of the column with the item name "Name", the user's "Last name" and "First name" are registered, respectively. In each field of the column with the item name "Gender", the user's gender (male or female) is registered, respectively. In each field of the column with the item name "Age", the user's age is registered, respectively. In each field of the column with the item name "Address", the address indicating the user's location is registered, respectively. The server program 27 registers the user's name, gender, age, and address contained in the membership application sent by the terminal program 38 in each field of each column, respectively.

[0075] Each field in the column labeled "Payment Information" stores payment information necessary for automatically paying fees when a user uses a managed store. Payment information is, for example, a credit card number and authentication information for identity verification. As payment information, the card number and authentication information are registered in each field in the column labeled "Payment Information." However, payment information may also be a bank ID, account number, authentication information, etc.

[0076] If the user desires automatic payment, the user uses the terminal program 38 to send payment information to the management server 11. The server program 27 of the management server 11 registers the provided payment information in the user management database.

[0077] The user management database has columns with item names such as "Reservation Information 1" and "Reservation Information 2." Each field in the column is registered with reservation information related to reservations made by users at managed stores. The user management database may also have columns with item names such as "Reservation Information 3" and "Reservation Information 4." In the following explanation, the item names "Reservation Information 1" and "Reservation Information 2" will simply be referred to as the item name "Reservation Information."

[0078] The column with the item name "Reservation Information" has multiple sub-columns with the items "Store ID," "Reservation Date," "Scheduled Check-in Time," "Scheduled End Time," and "Reservation Period."

[0079] In each field of the sub-column with the item name "Store ID", the store ID assigned to the operated store for which the user has made a reservation is registered.

[0080] Each field in the subcolumn with the item name "Reservation Date" registers the date the user plans to use the managed store. Each field in the subcolumn with the item name "Scheduled Check-in Time" registers the scheduled start time of the period during which the user will use the managed store. Each field in the subcolumn with the item name "Scheduled End Time of Use" registers the scheduled end time of the period during which the user will use the managed store. Each field in the subcolumn with the item name "Reservation Period" registers the period during which the user plans to use the store. Note that "h" indicates hours.

[0081] The user management database has columns with item names such as "Usage Information 1" and "Usage Information 2." The user management database may also have columns with item names such as "Usage Information 3" and "Usage Information 4." In the following explanation, the item names "Usage Information 1" and "Usage Information 2" will simply be referred to as the item name "Usage Information."

[0082] The column with the item name "Usage Information" has multiple sub-columns with the items "Store ID," "Date of Use," "Check-in Time," "Check-out Time," "Usage Duration," "Usage Fee," "Temporary Exit Time," "Re-entry Time," "Coupon Information," and "Payment Information."

[0083] Each field of the subcolumn with the item name "Store ID" registers the store ID assigned to the managed store where the user checked in. Each field of the subcolumn with the item name "Date of Use" registers the date on which the user checked in.

[0084] The time at which a user checked in is registered in each field of the subcolumn with the item name "Check-in time." The time at which a user checked out is registered in each field of the subcolumn with the item name "Check-out time." The period during which a user used a managed store, that is, the time from check-in time to check-out time, is registered in each field of the subcolumn with the item name "Usage duration." The usage fee paid by a user to a managed store used by a user is registered in each field of the subcolumn with the item name "Usage fee."

[0085] Each field of the subcolumn with the item name "Temporary Exit Time" registers the time when a user temporarily exits the managed store. Each field of the subcolumn with the item name "Re-entry Time" registers the time when a user who has temporarily exited re-enters the managed store. The date of use and check-in time are examples of check-in date and time. The date of use, check-in time, temporary exit time, and re-entry time are examples of entry and exit records. The date of use and temporary exit time are examples of temporary exit date and time. The date of use and re-entry time are examples of re-entry date and time.

[0086] Each field in the subcolumn with the item name "Coupon Information" registers the type of coupon issued to the user. In the illustrated example, the coupon types are "1H Free" and "2H Free." There do not have to be two types of coupons. Coupon types may also be discount rates such as "30% Off," "50% Off," or "Fully Free," or may be amounts to be deducted such as "500 Yen Off" or "1000 Yen Off." Note that "-" indicates that no coupon has been issued to the user. The initial value of coupon information is "-."

[0087] The column with the item name "Payment Information" has multiple sub-columns with the items "Store Name," "Time," and "Amount," respectively.

[0088] In each field of the subcolumn with the item name "Payment Store Name", the payment store name, which is the name of the payment store where the user purchased the product, etc., is registered. In each field of the subcolumn with the item name "Time", the payment time, which is the time when the user purchased the product, etc., is registered. In each field of the subcolumn with the item name "Amount", the payment amount, which is the purchase price of the product, etc., is registered. The payment store name is the same as the affiliated store name.

[0089] [Store management database] The store management database is a database that manages information about managed stores, information about affiliated stores to which the managed stores are attached, and information about reservations made to managed stores.

[0090] As shown in Figure 3, the store management database has multiple columns and multiple records. Each column is assigned an item name. The columns are assigned the item names "operated store information," "affiliated store information," and "reservation information," respectively.

[0091] The column with the item name "Operated Store" has multiple sub-columns with the item names "Store ID," "Store Name," "Address," and "Price," respectively. Each field in the column with the item name "Store ID" registers the store ID assigned to each operated store. Each record is individually identified by the store ID. In other words, one record corresponds to one operated store. The store ID is an example of store identification information.

[0092] Store names such as "Itabashi Store," "Tsurumi Store," and "Chikusa Store" are registered in each field of the subcolumn with the item name "Store Name." The location (address) of the managed store is registered in each field of the subcolumn with the item name "Address." The amount used per unit time (15 minutes) is registered in each field of the column with the item name "Price (15 minutes)." The store name of the managed store is an example of store identification information.

[0093] The column with the item name "Partner Store Information" has multiple sub-columns, each with an item name such as "Partner Store ID," "Partner Store Name," "Type," and "Coupon Settings."

[0094] Each field in the subcolumn with the item name "Partner Store ID" contains a partner store ID that uniquely identifies the partner store. Each field in the subcolumn with the item name "Partner Store Name" contains the name of the partner store. Each field in the subcolumn with the item name "Coupon Setting" contains a coupon setting such as A, B, or C. A coupon setting indicates the correspondence between the purchase amount and the free time or discount rate. For example, if the partner store is a retail store, cafe, or bookstore, one of coupon settings A, B, or C applies. Coupon setting A indicates one free hour for purchases of 500 yen or more but less than 1,000 yen, and two free hours for purchases of 1,000 yen or more. Coupon setting B indicates 30 free minutes for purchases of 500 yen or more but less than 1,000 yen, and one free hour for purchases of 1,000 yen or more. Coupon setting C indicates a 30% discount on purchases of items between 500 yen and 1000 yen, and a 60% discount on purchases of items over 1000 yen. Alternatively, if the affiliated store is a coin laundry, either coupon setting D or E will be applied. Coupon setting D indicates 1 free hour for one use, and 2 free hours for two or more uses. Coupon setting E indicates 30 free minutes for one use, and 1 free hour for two or more uses. If the affiliated store is a business hotel, coupon setting F will be applied, and coupon setting F indicates 2 free hours per night. In other words, different discount rates, deductions, and free time can be set for each type of business. Furthermore, even among affiliated stores of the same type, different discount rates, deductions, and free time can be set for each affiliated store.

[0095] The store management database also contains detailed information about managed stores and affiliated stores, such as store photos (image data), opening hours, size (floor area), and available capacity.

[0096] Each field of the sub-column with the item name "Type" registers the type of affiliated store. The type of affiliated store (affiliated store type) is a name indicating the type of business, such as "convenience store," "coin laundry," "bookstore," or "business hotel." A branch number indicating the type of affiliated store, such as "-A," "-B," or "-D," may be added to the affiliated store ID. For example, "-A" indicates a convenience store, "-B" indicates a coin laundry, and "-C" indicates a bookstore. In this case, a table associating the branch number with the type of affiliated store is stored in memory 22 as part of the management database, and the sub-column with the item name "Type" is omitted.

[0097] The column with the item name "Reservation Information" has multiple sub-columns, each with an item name such as "User ID," "Reservation Date," "Start Time," "End Time," and "Reservation Period."

[0098] The user ID of the user who made the reservation is registered in each field of the subcolumn with the item name "User ID." The date (reservation date) on which the user plans to use the Managed Store is registered in each field of the subcolumn with the item name "Reservation Date." The scheduled start time of the period during which the user will use the Managed Store is registered in each field of the subcolumn with the item name "Start Time." The scheduled end time of the period during which the user will use the Managed Store is registered in each field of the subcolumn with the item name "End Time." The scheduled end time of the period during which the user will use the Managed Store is registered in each field of the subcolumn with the item name "Reservation Period."

[0099] The store management database may further include columns with item names other than those mentioned above.

[0100] The following describes the processes that the server program 27 of the management server 11, the terminal program 38 of the user terminal 12, and the store program 48 of the store terminal 13 cause the CPUs 21, 31, and 41 to execute. The processes that the server program 27, the terminal program 38, and the store program 48 cause the CPUs 21, 31, and 41 to execute are also processes executed by the CPUs 21, 31, and 41, and are also processes executed by the management server 11, the user terminal 12, and the store terminal 13.

[0101] In the flowcharts shown in FIGS. 4, 12, and 14, "database" is abbreviated to "DB."

[0102] In the following, screen data of a screen that the terminal program 38 of the user terminal 12 causes to be displayed on the display 34 may be stored in the memory 32 when the terminal program 38 is installed on the user terminal 12, or may be transmitted from the management server 11. Alternatively, the terminal program 38 may generate the screen based on information transmitted from the management server 11. In this case, the information transmitted from the management server 11 to the user terminal 12 is an example of screen data. The screen data of a screen that the user terminal 12 causes to be displayed on the display 34 is, for example, HTML data including JavaScript.

[0103] Furthermore, in the following description, communication between the management server 11, the user terminal 12, the store terminal 13, and the door lock device 14 is performed via the communication interfaces 23, 33, 43, and 53, but the description will omit the communication interfaces 23, 33, 43, and 53. For example, "The user terminal 12 sends an HTTP request to the management server via the communication interface 33 and the Internet 15" should be written as "The user terminal 12 sends an HTTP request to the management server via the Internet 15."

[0104] [Reservation Processing] The reservation process that the terminal program 38 of the user terminal 12 and the server program 27 of the management server 11 cause the CPU 31 and CPU 21 to execute when a user makes a reservation at a managed store using the user terminal 12 will be explained with reference to Figure 4.

[0105] The user starts the terminal program 38 on the user terminal 12. The started terminal program 38 displays a home screen (not shown) on the display 34 (S11).

[0106] The user performs an input via the input interface 35 to display a store list screen (see FIG. 5(A)) on the displayed home screen. Upon receiving the input (S12), the terminal program 38 transmits an HTTP request including the user ID stored in the memory 32 and a store list data request to the management server 11 via the Internet 15 (S13). The store list data request and the various requests, applications, instructions, and commands described below are, for example, commands.

[0107] When the server program 27 of the management server 11 receives the HTTP request (S13), it reads out some of the information on the operated store information and the affiliated store information registered in the store management database as basic information based on the store list data request (S14). The some of the basic information is the store name, the prefecture name of the address, the affiliated store name, and the type of affiliated store. The server program 27 returns an HTTP response including the basic information on the operated store information and the affiliated store information to the user terminal 12 in response to the HTTP request received in step S13 (S15). The processing of step S15 is an example of a list screen data transmission process. The basic information on the operated store information and the affiliated store information is an example of store list screen data.

[0108] The terminal program 38 of the user terminal 12 receives the HTTP response returned by the management server 11 (S15). The terminal program 38 displays the store list screen (see FIG. 5(A)) indicated in the received HTTP response on the display 34 (S16). The processing of step S16 is an example of a first display processing.

[0109] 5(A) shows a store list screen. The store list screen has a plurality of store selection icons 63 each having a store name, which is the name of a managed store. Each store selection icon 63 is associated with a store name, a prefecture name such as Chiba or Tokyo, an affiliated store name, and a type of affiliated store.

[0110] The store list screen also has a "reserve" icon 61 and a "search" icon 62. The user selects the "search" icon 62 to narrow down the list of operated stores by place name or the like. Based on the selection of the "search" icon 62, the terminal program 38 of the user terminal 12 generates screen data showing a store selection screen (see FIG. 5(B)), and displays the store selection screen on the display 34.

[0111] The store selection screen shown in Figure 5(B) shows the search results for operated stores searched for "Tokyo." The store selection screen has multiple store selection icons 63 and a "reservation" icon 61. The store list screen shown in Figure 5(A) and the store selection screen shown in Figure 5(B) are examples of store list screens.

[0112] The user selects a store selection icon 63 indicating the operated store for which the user wishes to make a reservation on the store list screen (see FIG. 5(A)) or the store selection screen (see FIG. 5(B)).

[0113] As shown in FIG. 4, when the terminal program 38 receives the selection of the store selection icon 63 (S17), it sends an HTTP request including the store ID indicating the operated store selected by the user and a request for detailed information to the management server 11 via the Internet 15 (S18).

[0114] The management server 11 receives the HTTP request (S18). The server program 27 of the management server 11 identifies a record in the store management database that has a store ID that matches the received store ID. The server program 27 reads out detailed information registered in the identified record (S19). The detailed information includes, for example, the addresses, photos, business hours, site area, number of users allowed, usage fees, and coupon information indicated by the coupon settings of the managed store and affiliated store. A coupon condition may be, for example, "purchase a product worth 500 yen or more at an affiliated store to receive one hour of free store use." The server program 27 returns an HTTP response including the read detailed information to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S18 (S20).

[0115] The user terminal 12 receives the HTTP response sent back by the management server 11 (S20). The terminal program 38 of the user terminal 12 displays a shop details screen (not shown) showing the received detailed information on the display 34 (S21).

[0116] The shop details screen has the above detailed information and a "reservation" icon 61 (see FIG. 5(A)). After checking the detailed information, the user selects the "reservation" icon 61.

[0117] The terminal program 38 of the user terminal 12, upon receiving the selection of the "reservation" icon 61 on either the store list screen, the store selection screen, or the store details screen (S22), causes the display 34 to display a date and time specification screen (see Figure 5(D)) (S23).

[0118] 5(D), the date and time specification screen has a calendar 65 consisting of a plurality of "date" icons, and a "confirm" icon 66. The user selects the "date" icon for the date for which the reservation is to be made.

[0119] The terminal program 38 of the user terminal 12 displays a reservation period input screen (not shown) on the display 34 based on the user's selection of the "Date" icon and the "Confirm" icon 66. The reservation period input screen has, for example, a pull-down menu for selecting the planned start time of use of the managed store, a pull-down menu for selecting the planned end time of use of the managed store, and an "OK" icon. After selecting the planned start time and planned end time of use of the managed store on the reservation period input screen, the user selects the "OK" icon to complete the reservation.

[0120] When the terminal program 38 receives the selection of the "OK" icon on the reservation period input screen (not shown) (S24), it generates a reservation request including the store ID, the selected date (reservation date), the scheduled start time of use, the scheduled end time of use, and the user ID (S25). The terminal program 38 sends an HTTP request including the generated reservation request to the management server 11 via the Internet 15 (S26). The reservation date, the scheduled start time of use, and the scheduled end time of use are examples of reservation dates and times. The processing of step S26 is an example of reservation request processing.

[0121] The management server 11 receives the HTTP request (S26). The server program 27 of the management server 11 identifies a record in the user management database that has the same user ID as the user ID included in the received reservation request. The server program 27 creates a new column with the item name "reservation information" in the identified record. The server program 27 registers the reservation information, including the store ID, reservation date, scheduled start time of use (start time), scheduled end time of use (end time), and reservation period included in the reservation request, in each field of the created column (S27). The processing of step S27 is an example of a reservation registration process.

[0122] The server program 27 also identifies a record in the store management database that has the same store ID as the store ID included in the reservation request. The server program 27 registers the reservation information, such as the user ID, reservation date, scheduled start time of use (start time), scheduled end time of use (end time), and reservation period, included in the reservation request, in the identified record (S28).

[0123] After registering the reservation information, the server program 27 returns an HTTP response including a reservation completion notification indicating that the reservation has been completed to the user terminal 12 as a response to the HTTP request received in step S26 (S29). The reservation completion notification is an example of first notification screen data. The processing of step S29 is an example of first notification processing.

[0124] The user terminal 12 receives the HTTP response (S29). The terminal program 38 of the user terminal 12 displays a reservation completion notification screen (see FIG. 5(D)) indicated by the received reservation completion notification on the display 34 (S30). The reservation completion notification screen is an example of a first notification screen. The processing of step S30 is an example of a second display processing.

[0125] The reservation completion notification screen shown in FIG. 5(D) includes the text "Your reservation is complete," the store name, which is the name of the operated store where the reservation was made, the reservation date and time, the reservation period, the name and type of affiliated store, text indicating whether or not a coupon issuance service is available, text indicating the coupon conditions, and an "OK" icon 67. In the example shown in FIG. 5(D), the store name is "Akasaka Store, Tokyo," and the type of affiliated store is a convenience store. The text indicating whether or not a coupon issuance service is available reads, "A coupon will be issued when you purchase a product at an affiliated store," and the text indicating the coupon conditions reads, "One hour free with a purchase of 1,000 yen or more, two hours free with a purchase of 2,000 yen or more." After checking the store name, the name of the affiliated store, and the coupon conditions, the user selects the "OK" icon 67.

[0126] Upon receiving the selection of the "OK" icon 67, the terminal program 38 of the user terminal 12 ends the reservation process (END).

[0127] [Check-in process] Next, the check-in process that the terminal program 38 of the user terminal 12, the server program 27 of the management server 11, and the store program 48 of the store terminal 13 cause the CPU 31, CPU 21, and CPU 41 to execute when a user checks in will be described.

[0128] The user operates the user terminal 12 to start the terminal program 38. The started terminal program 38 displays the above-mentioned home screen (not shown) on the display 34. On the displayed home screen, the user selects an icon to instruct the display of a check-in screen (see FIG. 7(A)).

[0129] As shown in FIG. 6, upon receiving the selection of the icon on the home screen (S41), the terminal program 38 of the user terminal 12 displays a check-in screen on the display 34 (S42).

[0130] 7A, the check-in screen has a "check-in" icon 90. When the user wants to check in, the user selects the "check-in" icon 90.

[0131] As shown in FIG. 6, upon receiving the selection of the "Check-in" icon 90 (S43), the terminal program 38 displays the reading screen (see FIG. 7(B)) on the display 34 and activates the camera 16 (S44).

[0132] 7(B), the reading screen has an image display area 91 that displays an image captured by the camera 16. The user points the camera 16 at a QR code (registered trademark) installed in a store and inputs an instruction to capture an image of the QR code (registered trademark).

[0133] 6, upon receiving an image capture instruction from the user (S45), the terminal program 38 acquires image data output by the camera 16 (S46). The terminal program 38 reads the store ID from the acquired image data (S47). Note that the process of reading the store ID from the image data may be executed by a QR Code (registered trademark) reading application (not shown) installed in the user terminal 12.

[0134] The terminal program 38 sends an HTTP request including the acquired store ID, the user ID stored in the memory 22, and a reservation confirmation request to the management server 11 via the Internet 15 (S48).

[0135] The management server 11 receives the HTTP request (S48). The server program 27 of the management server 11 identifies a record in the user management database that has the same user ID as the received user ID. The server program 27 determines whether the identified record contains reservation information that has the same date as the current date and the same store ID as the received store ID (S49). In other words, the server program 27 determines whether the user has made a reservation (S49).

[0136] Although not shown in the flowchart, when the server program 27 determines that no reservation has been made (S49: No), it determines whether the upper limit of the number of people that can use the managed store has been reached, that is, whether the check-in applicant can use the managed store. When the server program 27 determines that the check-in applicant cannot use the managed store, it returns an HTTP response including an unavailable notice indicating that the check-in applicant cannot use the managed store to the user terminal 12 via the Internet 15. When the server program 27 determines that the check-in applicant can use the managed store, it returns an HTTP response including a no-reservation notice to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S48 (S50). The no-reservation notice is a notice indicating that no reservation has been made.

[0137] If the server program 27 determines that a reservation has been made (S49: Yes), it reads out the reservation information registered in the identified record (S51). The server program 27 then returns an HTTP response including the read-out reservation information to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S48 (S52).

[0138] The user terminal 12 receives the HTTP response including the no-reservation notification (S50), or receives the HTTP response including the reservation information (S52).

[0139] If the received HTTP response contains a no-reservation notification, the terminal program 38 displays an input screen (not shown) on the display 34 (S53). The input screen is a screen for accepting input of specifications such as the planned end time of use and the planned duration of use. The user enters the planned end time of use and the planned duration of use on the input screen. The terminal program 38 accepts the input of the planned duration of use and other information entered by the user on the input screen (S54).

[0140] The terminal program 38 displays a check-in application screen on the display 34 (S55) based on the selection of the "OK" icon on the input screen (S54) or based on the reception of an HTTP response including reservation information (S52).

[0141] As shown in Figure 7(C), the check-in application screen has the text "Checking in," the name of the managed store where the check-in will be performed, the name of the affiliated store which is the name of the affiliated store that is affiliated with the managed store, the type of affiliated store, text indicating whether or not a coupon issuance service is available, text indicating the coupon conditions, and a "Check-in" icon 92. The text indicating whether or not a coupon is available and the text indicating the coupon conditions are the same as the text indicating whether or not a coupon is available and the text indicating the coupon conditions on the reservation completion notification screen (see Figure 5(D)).

[0142] To check in, the user selects the "Check In" icon 92.

[0143] 6, upon receiving the user's selection of the "Check-in" icon 92 (S56), the terminal program 38 generates a check-in request (S57). The check-in request includes the user ID stored in the memory 32 and the store ID acquired from the QR code (registered trademark). If no reservation has been made, the check-in request further includes the planned end time of use and the planned duration of use, which were received as input on the input screen described above.

[0144] The terminal program 38 transmits an HTTP request including the generated check-in application to the management server 11 via the Internet 15 (S58). The processing of step S58 is an example of check-in application processing.

[0145] The management server 11 receives the HTTP request including the check-in request (S58). The server program 27 of the management server 11 identifies a record in the user management database that has the same user ID as the user ID included in the received check-in request. The server program 27 creates a new column named "usage information" for the identified record, and registers the current date (usage date), the current time (check-in time), and the store ID included in the check-in request (S59). The processing of step S59 is an example of check-in registration processing.

[0146] Meanwhile, the store program 48 of the store terminal 13 installed in the managed store periodically transmits an HTTP request including an inquiry request inquiring whether an unlock instruction has been issued to the management server 11 via the Internet 15 (S60). For example, the store program 48 periodically transmits the HTTP request including the inquiry request to the management server 11 at intervals of several to several tens of seconds.

[0147] Upon receiving the check-in application (S58), the server program 27 returns an HTTP response including an unlock instruction to the shop terminal 13 via the Internet 15 as a response to the HTTP request received in step S60 (S61).

[0148] The store terminal 13 receives the HTTP response including the unlock instruction (S61). Based on the reception of the unlock instruction (S61), the store program 48 of the store terminal 13 transmits an unlock command to the door locking device 14 via a LAN attached to the managed store (S62). The unlock command is, for example, a command that can be processed by the control unit 51 of the door locking device 14.

[0149] Upon receiving the unlock command (S62), the door lock device 14 releases (unlocks) the lock (S63).

[0150] After transmitting the unlock command (S62), the store program 48 of the store terminal 13 transmits an HTTP request including an unlock notification indicating that the door has been unlocked to the management server 11 via the Internet 15 (S64).

[0151] The management server 11 receives the HTTP request including the unlock notification (S64). Upon receiving the unlock notification, the server program 27 of the management server 11 returns an HTTP response including a check-in completion notification to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S58 (S65).

[0152] The user terminal 12 receives the HTTP response including the check-in completion notification (S65). Based on the reception of the check-in completion notification, the terminal program 38 of the user terminal 12 displays on the display 34 a check-in completion notification screen (see FIG. 7(D)) indicating that check-in has been completed (S66).

[0153] 7(D), the check-in completion notification screen displays the text "Check-in completed," the name of the managed store where the user checked in, the date and time of check-in, the planned check-out time, and the planned period of use. The check-in completion notification screen also displays the name and type of affiliated store, text indicating whether or not a coupon issuance service is available, text indicating the coupon conditions, and a "Coupon application" icon 93.

[0154] The "Coupon Request" icon 93 is an icon that accepts a user's request for coupon issuance. When a user checks in after purchasing a product at an affiliated store, the user can request a coupon at the same time as checking in. When the "Coupon Request" icon 93 is selected, the coupon issuance process shown in FIG. 12 is executed. Details will be described later.

[0155] [Temporary Exit Processing] Next, with reference to Figure 8, the temporary exit processing that the terminal program 38 of the user terminal 12, the server program 27 of the management server 11, and the store program 48 of the store terminal 13 cause the CPU 31, CPU 21, and CPU 41 to execute when a user temporarily leaves an operating store will be explained.

[0156] The user selects an icon on the above-mentioned home screen or the like to instruct the display of the temporary exit screen (see FIG. 9(A)).

[0157] As shown in FIG. 8, upon receiving the selection of the icon on the home screen or the like (S71), the terminal program 38 displays a temporary exit screen (see FIG. 9(A)) on the display 34 (S72).

[0158] As shown in Figure 9(A), the temporary exit screen has the text "Do you want to temporarily leave the store?", the text "If you temporarily leave, your use will continue," an "OK" icon 69, and a "Back" icon 70.

[0159] If the user does not want to leave the room temporarily, the user selects the "Back" icon 70, and if the user wants to leave the room temporarily, the user selects the "OK" icon 69.

[0160] 8, upon receiving the selection of the "OK" icon 69 (S73), the terminal program 38 displays the reading screen (see FIG. 7(B)) on the display 34 and activates the camera 16 (S74). The user points the camera 16 at a QR code (registered trademark) installed in the managed store and inputs an instruction to capture an image of the QR code (registered trademark).

[0161] The terminal program 38 acquires image data output by the camera 16 based on receiving an image capture instruction input from the user (S75) (S76). The terminal program 38 acquires a store ID from the image data (S77). The terminal program 38 generates a temporary leave application including the acquired store ID, the user ID stored in memory 22, and a temporary leave request (S78). The terminal program 38 transmits an HTTP request including the generated temporary leave application to the management server 11 via the Internet 15 (S79). The processing of step S79 is an example of temporary leave application processing.

[0162] The management server 11 receives an HTTP request including a temporary leave request (S79). The server program 27 of the management server 11 identifies, in the user management database, usage information having the same user ID and store ID as the user ID and store ID included in the received temporary leave request (S80). The server program 27 determines whether a check-in time is registered in the identified usage information (S81). In other words, the server program 27 determines whether the user has checked in.

[0163] If the server program 27 determines that the user has not checked in (S81: No), it returns an HTTP response including a non-check-in notification to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S79 (S82). After the server program 27 determines that the user has checked in (S81: Yes), the server program 27, the store program 48 of the store terminal 13, and the control unit 51 of the door lock device 14 execute the processes from step S60 to step S64 described above (see FIG. 6). That is, the door of the managed store is unlocked. After unlocking the door of the managed store, the server program 27 registers the current time as the temporary exit time in the record (use reservation) identified in step S80 (S83). The process of step S61 in which the management server 11 sends an unlock instruction to the store terminal 13 in the temporary exit process (see FIG. 8) is an example of an unlock instruction sending process. The process of step S83 is an example of a temporary exit registration process.

[0164] The server program 27 of the management server 11 returns an HTTP response including an unlock notification indicating that the door has been unlocked to the user terminal 12 via the Internet 15 in response to the HTTP request received in step S79 (S84). The unlock notification is an example of second notification screen data. The process of step S84 is an example of second notification process.

[0165] The user terminal 12 receives an HTTP response including a non-check-in notification (S82) or an HTTP response including an unlock notification (S84). The terminal program 38 of the user terminal 12 determines whether the notification included in the received HTTP response is a non-check-in notification or an unlock notification (S85). If the terminal program 38 determines that the received notification is a non-check-in notification (S85: non-check-in notification), it displays a check-in request screen (see FIG. 9(B)) on the display 34 (S86).

[0166] As shown in FIG. 9(B), the check-in request screen has the text "You are not checked in. Please check in." and a "Check in" icon 71. The user selects the "Check in" icon 71 on the check-in request screen. In other words, if the user accidentally enters a managed store with another person, the user cannot leave the managed store, even temporarily, unless the user checks in. In other words, being checked in is a requirement for temporarily leaving a managed store.

[0167] As shown in FIG. 8, the terminal program 38 executes the processing from step S42 (see FIG. 6) onward, in which the check-in screen (see FIG. 7(A)) is displayed on the display 34, based on the selection of the "Check-in" icon 71 on the check-in request screen.

[0168] If the terminal program 38 determines in step S85 that the received notification is an unlock notification (S85: unlock notification), it displays an unlock notification screen (see FIG. 9(C)) on the display 34 (S87). The unlock notification screen is an example of a second notification screen. The processing of step S87 is an example of a third display processing.

[0169] As shown in FIG. 9(C), the unlock notification screen includes the text "The lock has been released. You may temporarily leave the room," the name of the affiliated store, text indicating the coupon conditions, and a "Back" icon 72. Although not shown in the flowchart of FIG. 8, the terminal program 38 displays, for example, the above-mentioned home screen on the display 34 based on the selection of the "Back" icon 72. The unlock notification screen is an example of a second notification screen. The text indicating the coupon conditions is an example of coupon notification information.

[0170] [Re-entry processing] Next, with reference to Figure 10, the re-entry processing that the terminal program 38 of the user terminal 12, the server program 27 of the management server 11, and the store program 48 of the store terminal 13 cause the CPU 31, CPU 21, and CPU 41 to execute when a user re-enters an operated store will be explained.

[0171] For example, the user selects an icon on the above-mentioned home screen or the like to instruct the display of the re-entry screen (see FIG. 11(A)).

[0172] As shown in FIG. 10, upon receiving the selection of the icon on the home screen or the like (S101), the terminal program 38 of the user terminal 12 displays a re-entry screen on the display 34 (S102).

[0173] As shown in FIG. 11(A), the re-entry screen has the text "Do you want to re-enter the store?", an "OK" icon 94, and a "Back" icon 95.

[0174] If the user does not want to re-enter the room, the user selects the "Back" icon 95, and if the user wants to re-enter the room, the user selects the "OK" icon 94.

[0175] 10, upon receiving the selection of the "OK" icon 94 (S103), the terminal program 38 of the user terminal 12 displays a reading screen (see FIG. 7(B)) on the display 34 and activates the camera 16 (S104). The user points the camera 16 at a QR code (registered trademark) installed in the managed store and inputs an instruction to capture an image of the QR code (registered trademark).

[0176] Upon receiving an image capture instruction from the user (S105), the terminal program 38 acquires image data output by the camera 16 (S106). The terminal program 38 acquires a store ID from the image data (S107). The terminal program 38 generates a re-entry request including the acquired store ID, the user ID stored in memory 22, and a re-entry request (S108). The terminal program 38 sends an HTTP request including the generated re-entry request to the management server 11 via the Internet 15 (S109). The processing of step S109 is an example of a re-entry request process.

[0177] The management server 11 receives an HTTP request including a re-entry request via the Internet 15 (S109). The server program 27 of the management server 11 identifies a record (usage information) in the user management database that has the same user ID and store ID as the user ID and store ID included in the received re-entry request (S110). The server program 27 determines whether a check-in time is registered in the identified record (usage information) (S111). In other words, the server program 27 determines whether the user has checked in.

[0178] If the server program 27 determines that the user has not checked in (S111: No), it returns an HTTP response including a non-check-in notification to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S109 (S112). If the server program 27 determines that the user has checked in (S111: Yes), it registers the current time as the re-entry time in the record (usage information) identified in step S110 (S113). The processing of step S113 is an example of temporary exit registration processing.

[0179] Next, the server program 27 of the management server 11, the store program 48 of the store terminal 13, and the control unit 51 of the door lock device 14 execute the above-mentioned processes from step S60 to step S64 (see FIG. 6). That is, the door of the managed store is unlocked. The process of step S61 in which the management server 11 sends an unlock instruction to the store terminal 13 in the re-entry process (see FIG. 10) is an example of an unlock instruction sending process.

[0180] After unlocking the door of the managed store, the server program 27 of the management server 11 determines whether a temporary exit time is registered in the record (usage information) identified in step S110 (S114). For example, if a user who checks in and enters the managed store temporarily leaves the managed store with another user who checks out and leaves, and then re-enters the store, a situation may occur in which the user has checked in but the temporary exit time is not registered. If the server program 27 determines that the user has checked in but the temporary exit time is not registered (S111: Yes and S114: No), it returns an HTTP response including a confirmation and unlock notification to the user terminal 12 via the Internet 15 as a reply to the HTTP request received in step S109 (S115). On the other hand, if the server program 27 determines that check-in has been performed and the temporary exit time has been registered (S111: Yes and S114: Yes), it sends an HTTP response including an unlock notification to the user terminal 12 via the Internet 15 as a reply to the HTTP request received in step S109 (S116).

[0181] The user terminal 12 receives an HTTP response including a not-checked-in notification, a confirmation and unlock notification, or an unlock notification (S112, S115, S116). The terminal program 38 of the user terminal 12 determines whether the notification included in the received HTTP response is a not-checked-in notification, a confirmation and unlock notification, or an unlock notification (S117). If the terminal program 38 determines that the received notification is a not-checked-in notification (S117: not-checked-in notification), it displays a check-in request screen (see FIG. 9(B)) on the display 34 (S118). In response to receiving the user's selection of the "check-in" icon 71 on the check-in request screen, the terminal program 38 executes the processes from step S42 (see FIG. 6) onward for accepting the check-in.

[0182] As shown in FIG. 10, when the terminal program 38 determines that the received notification is an unlock notification (S117: unlock notification), it displays an unlock notification screen (see FIG. 11(B)) on the display 34 (S120).

[0183] As shown in FIG. 11(B), the unlock notification screen has the text "Your lock has been released. You can re-enter the room.", the text "Do you want to request a coupon?", a "Request a coupon" icon 93, and an "OK" icon 96. For example, the user selects the "Request a coupon" icon 93 if they have not yet requested a coupon or if the issued coupon has not reached the upper limit of the discount. The case where the upper limit of the discount has not been reached means that the coupon conditions are set to two discount levels: "one hour free with purchase of goods etc. over 500 yen" and "two hours free with purchase of goods etc. over 1000 yen," and a coupon for "one hour free with purchase of goods etc. over 500 yen" has been issued.

[0184] If the user wishes to request the issuance of a coupon later, or if a coupon that has reached the discount limit has already been issued, the user selects the "OK" icon 96. Although not shown in the flowchart of Figure 10, upon receiving the selection of the "OK" icon 96, the terminal program 38 displays another screen, such as the home screen described above, on the display 34, and ends the re-entry process (END).

[0185] As shown in FIG. 10, when the terminal program 38 determines that the received notification is a confirmation / unlock notification (S117: confirmation / unlock notification), it displays a confirmation / unlock notification screen (see FIG. 11(C)) on the display 34 (S119).

[0186] As shown in FIG. 11(C), the confirmation / unlock notification screen has the text "Your lock has been released. You may re-enter the room," the text "Caution: There is no record of you temporarily leaving the room," and the text "When did you leave the room?" The confirmation / unlock notification screen also has a radio button 73 associated with the text "30 minutes ago," a radio button 74 associated with the text "1 hour ago," a radio button 75 associated with the text "1.5 hours ago," and a radio button 76 associated with the text "2 hours ago." The user selects one of radio buttons 73 to 76.

[0187] The confirmation / unlock notification screen also includes the text "Apply for coupon issuance?", a "Coupon application" icon 93, and an "OK" icon 77. For example, if the user has not yet applied for a coupon or if the issued coupon has not reached its discount limit, the user selects the "Coupon application" icon 93. If the user plans to apply for a coupon issuance later, or if a coupon that has reached its discount limit has already been issued, the user selects the "OK" icon 77. Although not shown in the flowchart of FIG. 10, upon receiving the selection of the "OK" icon 77, the terminal program 38 displays another screen, such as the home screen described above, on the display 34, and ends the re-entry process (END).

[0188] [Coupon issuing process] Next, the coupon issuing process that the terminal program 38 of the user terminal 12 and the server program 27 of the management server 11 cause the CPU 31 and CPU 21 to execute when the user applies for the issuance of a coupon will be described with reference to FIG.

[0189] A user applies for a coupon using the user terminal 12 when checking in to a managed store, when re-entering the store, and during the period from check-in to check-out. Specifically, the user applies for a coupon by selecting the "Coupon Request" icon 93 on the check-in completion notification screen (see FIG. 7(D)) displayed on the user terminal 12 at check-in. Alternatively, the user applies for a coupon by selecting the "Coupon Request" icon 93 on the lock release notification screen (see FIG. 11(B)) or the confirmation / lock release notification screen (see FIG. 11(C)) displayed on the user terminal 12 at re-entry. Alternatively, the user selects an icon on the home screen or the like to display the coupon request screen (see FIG. 11(D)), causing the coupon request screen to be displayed on the display 34. As shown in FIG. 11(D), the coupon request screen includes the message "Apply for a coupon?", the "Coupon Request" icon 93, and a "Back" icon 97. The user applies for the issuance of a coupon by selecting the "Coupon Application" icon 93 on the coupon application screen.

[0190] The terminal program 38 of the user terminal 12 accepts selection of the "Coupon application" icon 93 on the check-in completion notification screen, the lock release notification screen, the confirmation / lock release notification screen, or the coupon application screen (S131). When the terminal program 38 accepts selection of the "Coupon application" icon 93, it causes the display 34 to display a first procedure screen (see FIG. 13(A)) (S132).

[0191] As shown in FIG. 13(A), the first procedure screen has the words "Coupon Issuance Application", an "Electronic Payment" icon 81, and a "Receipt" icon 82.

[0192] When a user makes an electronic payment at an affiliated store, the user selects the "Electronic Payment" icon 81. Electronic payment is a cashless payment that does not use cash and is made using a card or the user terminal 12. For example, so-called QR code (registered trademark) payment is an example of electronic payment. Here, in an electronic payment system that makes electronic payments, an electronic payment server that manages the electronic payment system transmits electronic payment data to the user terminal 12, which includes the name of the payment store where the user made a purchase, the date and time of payment, and the payment amount. The user's selection of the "Electronic Payment" icon 81 is an example of a second instruction.

[0193] When the user receives a receipt or invoice from an affiliated store, the user selects the "Receipt" icon 82. The receipt or invoice will include the name of the store where the payment was made, the date and time of the payment, and the payment amount. A receipt or invoice is given to the user by an affiliated store when the user purchases a product using cash, a credit card, or a prepaid card, for example. A receipt or invoice is an example of a payment record sheet.

[0194] Note that even with electronic payment, a receipt may be issued and electronic payment data may be sent to the user terminal 12. In this case, the user may select either the "Electronic Payment" icon 81 or the "Receipt" icon 82.

[0195] 12, the terminal program 38 of the user terminal 12 receives a selection of the "electronic payment" icon 81 or the "receipt" icon 82 (S133). The terminal program 38 determines whether the received icon is the "electronic payment" icon 81 or the "receipt" icon 82 (S134).

[0196] When the terminal program 38 determines that the accepted icon is the "electronic payment" icon 81 (S134: electronic payment), it displays the second procedure screen (see FIG. 12(B)) on the display 34 (S135).

[0197] As shown in FIG. 13(B), the second procedure screen includes the text "After displaying the electronic payment screen and taking a screenshot, select the coupon issuance icon." and a "Coupon issuance" icon 83.

[0198] The user displays the electronic payment screen indicated by the electronic payment image data sent by the electronic payment server on the display 34 of the user terminal 12, and then inputs an instruction to take a screenshot into the user terminal 12 via the input interface 35. The user terminal 12 stores the payment image data generated by the screenshot in the memory 32. The user then selects the "Issue coupon" icon 83 on the second procedure screen.

[0199] As shown in FIG. 12, upon receiving selection of the "Issue coupon" icon 83 (S136), the terminal program 38 of the user terminal 12 acquires payment image data stored in the memory 32 (S137). Specifically, the terminal program 38 requests the OS 36 to acquire a file path indicating the image data associated with the most recent date and time (S137). Alternatively, the terminal program 38 requests the OS 36 to display a list of image data. The user selects payment image data that the user instructed to be generated by taking a screenshot from the displayed list of image data. The terminal program 38 acquires a file path indicating the image data selected by the user (S137). The terminal program 38 waits until the user selects the "Issue coupon" icon 83 on the second procedure screen (S138: No).

[0200] On the other hand, if the terminal program 38 determines in step S134 that the selected icon is the "receipt" icon 82 (S134: Receipt), it displays the third procedure screen (see FIG. 13(C)) on the display 34 (S139).

[0201] 13(C), the third procedure screen has the text "Select the camera icon and take a picture of the receipt," the text "After taking the picture, select the coupon issue icon," a "camera" icon 84, and a "coupon issue" icon 83. The user selects the "camera" icon 84 on the third procedure screen.

[0202] As shown in FIG. 12, upon receiving the selection of the "camera" icon 84 (S140), the terminal program 38 of the user terminal 12 acquires payment image data (S141). More specifically, the terminal program 38 activates the camera 16 via the OS 36 and displays a screen similar to the reading screen (see FIG. 7(B)) on the display 34. The user uses the activated camera 16 to capture an image of a receipt or invoice provided by the payment store (affiliated store). The camera 16 returns a file path indicating the payment image data generated by capturing the image to the terminal program 38 via the OS 36. The terminal program 38 acquires the file path indicating the payment image data (S141). The terminal program 38 waits until the user selects the "coupon issue" icon 83 on the third procedure screen (S142: No). The user's selection of the "camera" icon 84 is an example of a first instruction. The processing of steps S137 and S141 in which the terminal program 38 acquires payment image data is an example of payment image data acquisition processing.

[0203] The terminal program 38 of the user terminal 12, upon determining that the "Coupon Issue" icon 83 was selected on the second and third procedure screens (S138: Yes, S142: Yes), acquires payment information from the payment image data (S143). More specifically, the terminal program 38 designates the payment image data via the OS 36 and launches the reading program 39. The launched reading program 39 reads character strings indicating the name of the payment store, the date and time of the payment, and the payment amount from the designated payment image data, and generates a document file or read data containing character codes indicating the read character strings as payment information. The reading program 39 returns a file path indicating the generated payment information to the terminal program 38 via the OS 36. The terminal program 38 acquires the file path indicating the payment information (S143). The processing of step S143 is an example of a reading process.

[0204] Although not shown in the flowchart, if the reading program 39 is unable to read characters from the specified payment image data, the terminal program 38 displays a screen on the display 34 prompting the user to re-image the receipt. The user re-images the receipt according to the instructions displayed on the screen. If the terminal program 38 is unable to obtain characters from the receipt even after re-imaging the receipt a predetermined number of times pre-stored in memory 32, it displays a "reading not possible" screen on the display 34. The "reading not possible" screen notifies the user that the payment store name, payment date and time, and payment amount could not be read from the receipt and that a coupon cannot be issued. The predetermined number of times is, for example, between two and five times. If a user images a receipt they found at an affiliated store, they may be unable to read characters from the captured image of the receipt. In such a case, the coupon issuance is rejected.

[0205] The terminal program 38 generates a coupon issuance application including the user ID, payment information, and a coupon issuance request (S144), and sends an HTTP request including the generated coupon issuance application to the management server 11 via the Internet 15 (S145). The processing of step S145 is an example of coupon application processing.

[0206] The management server 11 receives an HTTP request including a coupon issuance request (S145). The server program 27 of the management server 11 acquires the user ID, payment store name, payment date and time, and payment amount included in the received coupon issuance request (S146). The server program 27 identifies a record (usage information) that matches the acquired user ID in the user management database (S147). The processing of step S146 in which the server program 27 acquires the payment store name is an example of a payment store name acquisition process.

[0207] The server program 27 also reads out the store ID registered in the identified record and identifies a record in the store management database that has a store ID that matches the read store ID. The server program 27 determines whether the affiliated store name registered in the identified record matches the payment store name (S148). The processing of steps S147 and S148 is an example of a determination process.

[0208] The determination of whether the affiliated store name and the payment store name match may be based on an exact match or an approximation. For example, the affiliated store name and the payment store name may be determined to match if a portion of the affiliated store name matches a portion of the payment store name. The range of approximation may be optimized by AI learning, such as so-called "supervised learning," "unsupervised learning," "reinforcement learning," and "deep learning."

[0209] If the server program 27 determines that the affiliated store name and the payment store name do not match (S148: No), it returns an HTTP response including a rejection notice indicating that the coupon issuance request has been rejected to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S145 (S149). In other words, even if the user purchases a product at a store that is not affiliated with the operated store where the user checked in, no coupon will be issued. The rejection notice may include information indicating that the affiliated store name and the payment store name did not match.

[0210] Furthermore, if the server program 27 determines that the affiliated store name and the payment store name match (S148: Yes), it acquires the date of use, check-in time, temporary exit time, and re-entry time from the record identified in step S147 (S150). The server program 27 sets the validity period based on the acquired date of use, check-in time, temporary exit time, and re-entry time (S151). To explain in more detail, for example, on the date of use, the period between the check-in time and a predetermined time before the check-in time is set as the validity period. The predetermined time is, for example, one hour. For example, if the date of use and check-in time are 9:00 a.m. on January 15th, the validity period is set as the period from 8:00 a.m. to 9:00 a.m. on January 15th. Furthermore, on the date of use, the period from the temporary exit time to the re-entry time is set as the validity period. For example, if the date of use and temporary exit time are 10:00 on January 15th and the re-entry time is 10:30, the validity period is set to the period from 10:00 to 10:30 on January 15th. The period between the check-in time and the time a predetermined time before the check-in time, and the period between the temporary exit time and the re-entry time are examples of periods when the user is not in the store.

[0211] The server program 27 determines whether the payment date and time acquired in step S146 is within the validity period set in step S150 (S152). If the server program 27 determines that the payment date and time is not within the validity period set (S152: No), it returns an HTTP response including a rejection notice to the user terminal 12 via the Internet 15 in response to the HTTP request received in step S145 (S149). The rejection notice may include information indicating that the payment date and time is not within the validity period. For example, even if a user applies for a coupon using a receipt found while visiting an affiliated store, the coupon will not be issued if the receipt's issue date and time is more than one hour before the check-in date and time. Furthermore, even if a user applies for a coupon using a receipt issued during a period when the user was in the operated store and could not purchase products at the affiliated store, the coupon will not be issued.

[0212] If payment information is already registered in the record identified in step S147, the server program 27 reads the payment information as coupon-issued payment information (S153). The server program 27 then determines whether the payment amount in the read coupon-issued payment information matches the payment amount in the payment information acquired in step S146 (S154). That is, in step S154, it determines whether a new coupon issuance request has been made for a receipt or electronic payment that has already been used to issue a coupon. If the server program 27 determines that the two payment amounts match (S154: Yes), it returns an HTTP response including a rejection notice to the user terminal 12 via the Internet 15 in response to the HTTP request received in step S145 (S149). The rejection notice may include information indicating that a coupon issuance request has been made for a receipt or electronic payment for which a coupon has already been issued.

[0213] If the server program 27 determines that the two payment amounts do not match (S154: No), it determines whether the payment date and time included in the coupon-issued payment information matches the payment date and time included in the payment information acquired in step S146 (S155). That is, in step S155, it determines whether a new coupon issuance request has been made for a receipt or electronic payment that has already been used to issue a coupon. If the server program 27 determines that the two payment dates and times match (S155: Yes), it returns an HTTP response including a rejection notice to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S145 (S149). The rejection notice may include information indicating that the two payment dates and times match. The processes of steps S154 and S155 are an example of a determination process.

[0214] If the server program 27 determines that the two payment dates and times do not match (S155: No), it adds the payment amount included in the payment information acquired in step S146 to the payment amount included in the coupon-issued payment information to calculate the total payment amount (S156). Note that if the payment information is not registered in the user management database, the processing of step S156 may be skipped, or the payment amount included in the payment information acquired in step S146 may be used as the total payment amount.

[0215] The server program 27 determines whether the calculated total payment amount is equal to or exceeds the minimum amount (S157). The minimum amount is the amount specified in the coupon issuance conditions. For example, if the coupon issuance conditions are "one hour free with purchases of products worth 500 yen or more," then "500 yen" is the minimum amount. In step S148, the server program 27 reads the coupon conditions along with the affiliated store name from the store management database, and obtains the minimum amount from the read coupon conditions.

[0216] If the server program 27 determines that the calculated total payment amount is less than the minimum amount (S157: No), it returns an HTTP response including a rejection notice to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S145 (S149). The rejection notice may include information indicating that the payment amount is less than the minimum amount required to issue a coupon.

[0217] If the server program 27 determines that the calculated total payment amount is equal to or greater than the minimum amount (S157: Yes), it generates coupon information (S158). Coupon information may be "1 hour free," "2 hours free," "30% off," "50% off," or "all free." The server program 27 registers the generated coupon information and the payment information acquired in step S146 in the user management database (usage information) (S158). Note that the new payment information is registered separately from the payment information already registered in the user management database.

[0218] The server program 27 returns an HTTP response including a coupon issuance notification having coupon information to the user terminal 12 via the Internet 15 as a response to the HTTP request received in step S145 (S159). Steps S158 and S159 are an example of a coupon issuance process.

[0219] The user terminal 12 receives the HTTP response returned by the management server 11 (S149, S159). The terminal program 38 of the user terminal 12 determines whether a rejection notice or a coupon issuance notice has been received (S160). If the terminal program 38 determines that a rejection notice has been received (S160: rejection notice), it displays a rejection notice screen (not shown) on the display 34 (S161). The rejection notice screen may include, for example, the text "Coupon cannot be issued," text indicating the reason the coupon cannot be issued, and an "OK" icon. The text (text) indicating the reason the coupon cannot be issued may be, for example, "This receipt (electronic payment) is not from an affiliated store," "This receipt (electronic payment) is no longer valid," "This receipt (electronic payment) has already been used to issue a coupon," or "The purchase amount for this receipt (electronic payment) is less than 500 yen."

[0220] When the terminal program 38 determines that a coupon issuance notification has been received (S160: Issuance notification), it displays a coupon issuance notification screen (see FIG. 13(D)) on the display 34 (S162).

[0221] As shown in Fig. 13(D), the coupon issuance notification screen is a screen that notifies the user that a coupon has been issued, the type of coupon issued, and how to use the coupon. In the illustrated example, the coupon issuance notification screen has the text "A coupon for two hours free of charge has been issued," the text "Please select to use the coupon at checkout," and an "OK" icon 86. Although not shown in the flowchart shown in Fig. 12, the terminal program 38 of the user terminal 12 ends the coupon issuance process (END) when the "OK" icon 86 is selected on the coupon issuance notification screen.

[0222] [Checkout process] Next, the checkout process that the terminal program 38 of the user terminal 12, the server program 27 of the management server 11, and the store program 48 of the store terminal 13 cause the CPU 31, CPU 21, and CPU 41 to execute when the user checks out will be explained with reference to Figure 14.

[0223] The user selects an icon on the above-mentioned home screen or the like to instruct the display of the checkout screen (see FIG. 15(A)).

[0224] As shown in FIG. 14, upon receiving the selection of the icon on the home screen (S171), the terminal program 38 of the user terminal 12 displays the checkout screen (see FIG. 15(A)) on the display 34 (S172).

[0225] As shown in FIG. 15(A), the checkout screen has the text "Checking out," the name of the store, the check-in time, text indicating that a coupon has been issued and the type of coupon issued, a "Check out using coupon" icon 87, and a "Check out" icon 88. In the illustrated example, the text indicating that a coupon has been issued and the type of coupon issued is the text "A coupon for two hours free has been issued." Note that if a coupon has not been issued, the text indicating that a coupon has been issued and the type of coupon issued, and the "Check out using coupon" icon 86 are not displayed on the checkout screen.

[0226] If the user wishes to check out using the issued coupon, the user selects the "Check out using coupon" icon 87, and if the user does not wish to check out using the coupon, the user selects the "Check out" icon 88.

[0227] As shown in FIG. 14, upon receiving the selection of the "Use coupon checkout" icon 87 or the "Checkout" icon 88 (S173), the terminal program 38 of the user terminal 12 displays a reading screen (see FIG. 17(B)) on the display 34 and activates the camera 16 (S174).

[0228] The user points the camera 16 at a QR code (registered trademark) placed in the managed store and inputs an instruction to capture an image of the QR code (registered trademark).

[0229] 14, upon receiving an image capture instruction from the user (S175), the terminal program 38 of the user terminal 12 acquires image data output by the camera 16 (S176). The terminal program 38 then acquires a store ID from the image data (S177).

[0230] The terminal program 38 generates a checkout request including the acquired store ID, the user ID stored in the memory 22, the coupon usage type, and a checkout request (S177). The terminal program 38 sends an HTTP request including the generated checkout request to the management server 11 via the Internet 15 (S178). The coupon usage type is, for example, an identification flag of "1" indicating that a coupon will be used or "0" indicating that a coupon will not be used. In step S173, the terminal program 38 generates an identification flag of "1" based on the acceptance of selection of the "Use coupon checkout" icon 87. In addition, in step S173, the terminal program 38 generates an identification flag of "0" based on the acceptance of selection of the "Checkout" icon 88. The identification flag indicating the coupon usage type is an example of a coupon usage instruction. The processing of step S178 is an example of checkout request processing.

[0231] The management server 11 receives an HTTP request including a check-out request (S178). The server program 27 of the management server 11 identifies a record (usage information) having a user ID that matches the user ID included in the received HTTP request in the user management database (S179). The server program 27 reads out the check-in time registered in the identified record. The server program 27 calculates the usage time based on the check-in time and the current time (check-out time) (S180). The processing of step S180 is an example of a usage time calculation process.

[0232] Furthermore, the server program 27 determines whether to use a coupon to calculate the usage fee based on the identification flag included in the received HTTP request (S181). If the server program 27 determines not to use a coupon (S181: No), it reads the fee per unit time of the managed store used by the user from the store management database based on the store ID registered in the record identified in step S179. The server program 27 calculates the usage fee based on the read fee per unit time and the usage time calculated in step S180 (S182).

[0233] When the server program 27 determines that a coupon should be used (S181: Yes), it reads out the coupon information registered in the record identified in step S179 (S183). The server program 27 calculates the usage fee based on the read out coupon information, the fee per unit time, and the usage time calculated in step S180 (S184). The processing of step S184 is an example of a fee calculation process.

[0234] The server program 27 registers the check-in time (current time), the usage time, and the usage fee in the record identified in step S179 (S185).

[0235] The server program 27, the store program 48 of the store terminal 13, and the control unit 51 of the door lock device 14 execute the processes of steps S60 to S64 described above (see FIG. 6). That is, the door of the managed store is unlocked. After unlocking the door of the managed store, the server program 27 returns an HTTP response including a check-out completion notification to the user terminal 12 as a response to the HTTP request received in step S178 (S186). The check-out completion notification includes the name of the managed store used by the user, the check-in date and time, the check-out date and time, the usage time, whether or not a coupon was used, the type of coupon used, and the usage fee.

[0236] The user terminal 12 receives the HTTP response sent back by the management server 11 (S186). Based on the received check-out completion notification, the terminal program 38 of the user terminal 12 displays a check-out completion notification screen (FIG. 15(B)) on the display 34 (S187).

[0237] As shown in Figure 15 (B), the check-out completion notification screen includes the text "Check-out is complete," the text "Door has been unlocked," the name of the operating store, the check-in date and time, the check-out date and time, the usage period, coupon information, whether or not a coupon was used and the type of coupon, the usage fee, and an "OK" icon 89.

[0238] Although not shown in the flowchart, the terminal program 38 of the user terminal 12 displays another screen, such as the home screen, on the display 34 based on the acceptance of the selection of the "OK" icon 89, and ends the checkout process (END). Meanwhile, the server program 27 of the management server performs payment processing using the usage fee determined in step S185 and the payment information registered in the user management database, and ends the checkout process (END).

[0239] [Effects of the embodiment] In this embodiment, some or all of the managed stores operated by the service provider are attached to affiliated stores. When a user purchases a product or the like at an affiliated store, a coupon that can be used at the managed store is issued. The coupon is used to reduce or discount the usage fee at the managed store. The affiliated store is expected to see an increase in sales from users of the managed store. Furthermore, users will enjoy improved convenience as an affiliated store is attached to the managed store. Furthermore, the service provider is expected to see an increase in the managed store's ability to attract customers due to the improved user convenience. Furthermore, the service provider can earn a commission fee by operating the managed store under a contract for the use of some of the space of the affiliated store. Furthermore, an affiliated store can increase sales and attract more customers by contracting the operation and management of some of the space to the service provider.

[0240] In this embodiment, the terminal program 38 of the user terminal 12 captures an image of a receipt or invoice using the camera 16 to acquire payment image data (S141). Alternatively, the terminal program 38 acquires image data generated by taking a screenshot of the electronic payment screen as payment image data (S137). The terminal program 38 then reads the name of the payment store from the acquired payment image data (S143) and transmits the name of the payment store along with a coupon issuance request to the management server 11 (S145). In other words, the service providing system 10 can acquire the name of the payment store and determine whether to issue a coupon (S148) without accessing the payment device installed at the affiliated store that performs the payment or the electronic payment server that performs the electronic payment, and regardless of the data format of the electronic payment image data generated by the electronic payment server. Therefore, in this embodiment, coupons can be issued based on the purchase of products at affiliated stores, etc., without accessing other systems or regardless of the type of payment record sheet (receipt or invoice).

[0241] In the embodiment, the period before the check-in time and the period from the temporary exit time to the re-entry time are set as the validity period for which the coupon can be issued. In other words, the validity period is the period during which the user is not in the managed store and can make purchases, etc. at affiliated stores, and the coupon is issued only if a purchase, etc. of a product is made within the validity period. Therefore, in the embodiment, fraudulent coupon issuance requests can be rejected. Note that in a system for settling parking fees, the user does not purchase products at affiliated stores before parking their car.

[0242] In this embodiment, the validity period for issuing a coupon is the period from a predetermined time before the check-in time to the check-in time. Therefore, even if a user purchases a product at an affiliated store and then enters an operated store, the coupon is issued. As a result, user convenience is improved.

[0243] It is difficult to imagine that a user would check in to a managed store more than a predetermined time (e.g., one hour) after making a purchase at an affiliated store. In the embodiment, the validity period is the period from a time a predetermined time before the check-in time to the check-in time, and a coupon will not be issued even if a purchase is made at an affiliated store during a period even earlier than the time a predetermined time before the check-in time. As a result, in the embodiment, it is possible to reject fraudulent coupon issuance applications using receipts found at affiliated stores.

[0244] In the embodiment, a user can temporarily leave the managed store, and the period between the time of temporary exit and the time of re-entry is set as the validity period for issuing a coupon. Therefore, the user can temporarily leave the managed store and purchase products at the affiliated store. As a result, user convenience is further improved, and the user's purchases at the affiliated store can be expected to increase.

[0245] In this embodiment, if the receipt or electronic payment for which a coupon has already been issued is the same as the receipt or electronic payment for which a new coupon issuance request is made (S154: Yes, S155: Yes), the coupon issuance request is rejected (S149). Therefore, in this embodiment, it is possible to prevent a second coupon issuance request using a receipt or electronic payment for which a coupon has already been issued.

[0246] In the embodiment, during the reservation process (see FIG. 4), a list of managed stores is displayed on the display 34 of the user terminal 12 in association with the names and types of affiliated stores (see FIGS. 5(A) and 5(B)). The user narrows down the managed stores for which a reservation is to be made, for example, by the type of affiliated store. This improves user convenience compared to when the type of affiliated store is not displayed on the user terminal 12.

[0247] In this embodiment, when a user makes a reservation at a managed store, the managed store name, which is the name of the managed store that has made the reservation, and the affiliated store name, which is the name of the affiliated store that is affiliated with the managed store, are displayed on the display 34 of the user terminal 12. Therefore, in this embodiment, the user can confirm the affiliated stores that are affiliated with the managed store that the user has reserved at the time of reservation. As a result, user convenience is improved.

[0248] In the embodiment, when a user temporarily leaves a managed store, the name of the affiliated store and coupon notification information such as "Get 1 hour free with purchase of 1000 yen or more" are displayed on the display 34 of the user terminal 12 (see FIG. 9(C)). This can further encourage the user to purchase products at affiliated stores.

[0249] In this embodiment, a coupon is issued (S158, S159), and at checkout, the user is allowed to decide whether or not to use the coupon (S177, S178). Therefore, in this embodiment, the user is more likely to purchase products, etc. at the affiliated store than if the usage fee at the managed store were automatically reduced (discounted) by purchasing a product, etc. at the affiliated store. To explain in more detail, a service in which a parking fee is reduced by purchasing a product, etc., when a user who arrives by car uses the attached parking lot, is provided nationwide. On the other hand, a service in which the usage fee at the managed store is reduced (discounted) by purchasing a product, etc. at the affiliated store is not recognized nationwide. In this embodiment, by issuing a coupon, the user can be impressed with the idea that the usage fee at the managed store is reduced (discounted) by purchasing a product, etc. at the affiliated store. As a result, the user is more likely to purchase products, etc. at the affiliated store.

[0250] [Variation 1] In the embodiment, an example was described in which the validity period is the period before the check-in time and the period from the temporary exit time to the re-entry time, and a coupon is not issued even if a product is purchased outside the validity period. In this modified example, the setting of another validity period will be described. Note that the configuration and processing other than those described below are the same as the configuration and processing described in the embodiment.

[0251] In this modification, instead of or in addition to the processing of step S151, the server program 27 of the management server 11 executes processing to set the period from the payment date and time acquired in step S146 until a predetermined time has elapsed as the validity period for which a coupon issuance request is permitted. Between steps S148 and S157, the server program 27 executes processing to determine whether the date and time at which the coupon issuance request was received (S145) is within the validity period from the payment date and time until a predetermined time has elapsed. If the server program 27 determines that the date and time at which the coupon issuance request was received is not within the validity period from the payment date and time until a predetermined time has elapsed, the server program 27 rejects the coupon issuance request (S149). If the server program 27 determines that the date and time at which the coupon issuance request was received is within the validity period from the payment date and time until a predetermined time has elapsed, the server program 27 issues the coupon (S158, S159). The predetermined period is, for example, between one and two hours. The date and time at which the management server 11 received the coupon issuance request (S145) is an example of the coupon issuance request date and time.

[0252] In this modified example, it is possible to prevent coupons from being issued using old receipts or invoices found at affiliated stores.

[0253] [Variation 2] In the embodiment, an example has been described in which a coupon is used to reduce (discount) the usage fee (store usage fee) of a managed store rented by the hour. However, the fee reduced (discounted) by a coupon is not limited to the store usage fee. For example, a shared space and private rooms (individual booths) may be provided within the managed store. The usage fee for the shared space is set as the store usage fee, and the usage fee for the private room is set as an additional fee. The coupon may reduce (discount) the additional fee or may allow use of the private room. Furthermore, the managed store may be equipped with relaxation facilities such as massage chairs, and paid facilities such as personal computers and multi-function devices with copy functions, etc. The coupon may reduce (discount) the facility usage fee, which is the fee for using the paid facilities. The additional fee and facility usage fee are examples of payment fees related to the store.

[0254] [Variation 3] In this modified example, an example will be described in which the server program 27 of the management server 11 determines whether or not a receipt or invoice is a counterfeit. Specifically, in this modified example, the server program 27 of the management server 11 further executes a process of accepting sample image data for each affiliated store and registering it in the store management database (see FIG. 16). Furthermore, instead of the coupon issuance process shown in FIG. 12, the server program 27 executes the coupon issuance process shown in FIG. 17. The coupon issuance process shown in FIG. 17 adds a process (S197) for determining whether or not a receipt or invoice is a counterfeit. Note that the configurations and processes other than those described below are the same as the configurations and processes described in the embodiment.

[0255] The manager (or store manager) of an affiliated store, or an employee instructed by the manager, provides sample image data to the service provider when subscribing to a service provided by the service provider or when replacing or adding a device (or cash register) that issues receipts or invoices (hereinafter also referred to as receipts, etc.). The sample image data is data representing receipts, etc. issued by the affiliated store. For example, the manager or employee of the affiliated store uses a communication terminal such as a smartphone (registered trademark) owned by the store to capture an image of a receipt, etc. issued by the affiliated store and generate sample image data on the communication terminal. The manager or employee of the affiliated store uses the communication terminal to send an e-mail containing the name of the affiliated store (or affiliated store ID) and sample image data to an address specified by the service provider. Alternatively, the manager or employee of the affiliated store uses the communication terminal to upload the name of the affiliated store (or affiliated store ID) and sample image data to a web server or management server 11 operated by the service provider. The server program 27 of the management server 11 acquires the affiliated store name (or affiliated store ID) and sample image data provided by the manager or employee of the affiliated store.

[0256] The server program 27 of the management server 11 generates counterfeit determination data and specific item location data from the acquired sample image data, and registers the data in the store management database (see FIG. 16) in association with the store ID, affiliated store ID, and affiliated store name. The process in which the server program 27 registers the counterfeit determination data acquired from the sample image data in the store management database is an example of a determination data registration process.

[0257] Counterfeit determination data includes, for example, data indicating the shape of letters, numbers, and symbols (known as fonts) displayed on the sample receipt, data indicating the shape of graphics such as logos, data indicating the ratio of line or character spacing to character size, data indicating the layout of letters and graphics, and data indicating other characteristics. Data indicating layout is, for example, coordinate information indicating the absolute position of letters and graphics on the receipt, or the relative position between letters and graphics. Data indicating other characteristics is, for example, character strings that do not change even if the purchase date and time or purchased item changes.

[0258] The specific item location data includes data indicating the location where the affiliated store name is displayed, data indicating the location where the date is displayed, data indicating the location where the time is displayed, data indicating the location where the name of the purchased product is displayed, and data indicating the location where the price of the purchased product is displayed.

[0259] 16 is a diagram showing the store management database in this modified example. The store management database has multiple columns with the item names "operated store information," "affiliated store information," and "reservation information." The same information as in the embodiment is registered in each field of the columns with the item names "operated store information" and "reservation information."

[0260] The column with the item name "Affiliate Store Information" has sub-columns with the items "Affiliate Store ID," "Affiliate Store Name," "Type," and "Coupon Settings," as well as a sub-column with the item name "Counterfeit Determination Data" and a sub-column with the item name "Specific Item Position Data." The same information as in the embodiment is registered in each field of the sub-columns with the item names "Affiliate Store ID," "Affiliate Store Name," "Type," and "Coupon Settings." The counterfeit determination data obtained from the sample image data or the file path of the counterfeit determination data is registered in each field of the sub-column with the item name "Specific Item Position Data." The specific item position data obtained from the sample image data or the file path of the specific item position data is registered in each field of the sub-column with the item name "Specific Item Position Data."

[0261] In the case of a chain of stores with multiple affiliated stores that use the same receipt standard, the same counterfeit determination data and specific item location data may be registered in the store management database for the multiple affiliated stores. However, the store management database can register counterfeit determination data and specific item location data for each affiliated store. In other words, even within a chain of stores, the models of devices that issue receipts, etc. (known as cash registers) may be different, so it is desirable to register counterfeit determination data and specific item location data for each affiliated store, even within a chain of stores.

[0262] The server program 27 of the management server 11 executes the coupon issuing process shown in Fig. 17 instead of the coupon issuing process shown in Fig. 12. Note that in the coupon issuing process shown in Fig. 17, the processes described in the first embodiment (see Fig. 12) are assigned the same step numbers as in the first embodiment, and descriptions thereof will be omitted.

[0263] As shown in FIG. 17, the terminal program 38 of the user terminal 12 executes steps S131 to S142. That is, the terminal program 38 accepts user input (S133, S140) and acquires payment image data (S137, S141). The terminal program 38 generates a coupon issuance request (S191) that includes a user ID, payment image data, an image type flag, and a coupon issuance request. The image type flag indicates whether the payment image data is image data generated by capturing an image of a receipt or the like, or image data generated by taking a screenshot of an electronic payment screen. For example, an image type flag of "0" indicates that the payment image data is image data generated by capturing an image of a receipt or the like, and an image type flag of "1" indicates that the payment image data is image data generated by taking a screenshot of an electronic payment screen.

[0264] The terminal program 38 sends an HTTP request including the generated coupon issuance request to the management server 11 via the Internet 15 (S192). In other words, in this modified example, the terminal program 38 does not acquire payment information from the payment image data, but includes the payment image data itself in the coupon issuance request and sends it to the management server 11.

[0265] The server program 27 of the management server 11 receives an HTTP request including a coupon issuance request via the communication interface 23 (S192). The server program 27 acquires the user ID, payment image data, and image type flag included in the received coupon issuance request (S193). The server program 27 determines whether the acquired image type flag is "0," indicating a receipt or the like, or "1," indicating electronic payment (S194).

[0266] When the server program 27 determines that the image type flag indicates a receipt or the like (S194: Receipt), it identifies the record having the user ID acquired in step S193 in the store management database (see FIG. 16) and acquires the counterfeit determination data and specific item position data registered in the identified record (S195). In addition, the server program 27 acquires (generates) data indicating the shapes (fonts) of letters, numbers, and symbols displayed on the receipt or the like, data indicating the shapes of graphics such as logos, and data indicating the ratio of line spacing and character spacing to the character size, etc., from the payment image data acquired in step S193.

[0267] The server program 27 determines whether the counterfeit determination data acquired in step S195 matches or is similar to the data acquired in step S196 (S197). That is, in step S197, it is determined whether the receipt or the like indicated by the payment image data is a counterfeit receipt. The determination of approximation is made by calculating the match rate for each of several determination items, such as the match rate with the shape of characters in the counterfeit determination data, the match rate with the shape of graphics such as logos, the match rate with the ratio of line spacing to character size, and the match rate with the ratio of character spacing to character size, and determining whether each match rate is equal to or greater than a threshold. Each item may also be weighted. The weighting and threshold may be optimized by AI learning, such as so-called "supervised learning," "unsupervised learning," "reinforcement learning," or "deep learning." Furthermore, the server program 27 stores image data determined to not match or be similar to the counterfeit determination data in memory 22 as learning data. AI learning using the learning data may improve the accuracy of the determination in step S197. The process of step S197 is an example of the suitability determination process.

[0268] If the server program 27 determines that the counterfeit determination data acquired in step S195 does not match or approximate the data acquired in step S196 (S197: No), it sends an HTTP response including a rejection notice indicating that the coupon issuance application has been rejected to the user terminal 12 via the Internet 15 in response to the HTTP request received in step S192 (S149).

[0269] If the server program 27 determines that the counterfeit determination data acquired in step S195 matches or is similar to the data acquired in step S196 (S197: Yes), it acquires payment information from the payment image data (S198). The processing of step S198 is executed in the same manner as the processing of S141. The server program 27 acquires the payment information using the specific item position data acquired in step S195. The server program 27 identifies the position on the receipt indicated by the payment image data using the position data indicating the position of the affiliated store name, and acquires the character string written at that position as the affiliated store name. The server program 27 similarly acquires other payment information such as the purchase date and time (date and time), the purchased product name, and the purchase amount. The server program 27 executes the processing from step S148 onwards using the payment information acquired in step S198.

[0270] If the server program 27 determines in step S194 that the image type flag indicates an electronic payment image (S194: electronic payment), it acquires payment information based on the payment image data (S199). The process of step S199 is executed in the same manner as the process of S141. The server program 27 executes the processes from step S148 onward using the payment information acquired in step S199.

[0271] [Effects of Modification 3] In this modification, in step S197, it is determined whether the receipt or the like captured by the user is a counterfeit receipt or the like. Therefore, the service providing system 10 can prevent a coupon from being erroneously issued based on a counterfeit receipt or the like.

[0272] In this modification, the payment information is obtained from the payment image data using the specific item location data contained in the receipt sample data (S198). Therefore, the server program 27 can more reliably obtain payment information such as the affiliated store name, purchase date and time, purchased product name, and purchase amount from the payment image data.

[0273] If, in step S197, the server program 27 finds that the match rate with the counterfeit determination data is within a predetermined range that is within a range where it can be reliably determined to be appropriate, but not within a range where it can be reliably determined to be inappropriate, it may return an HTTP response including a re-imaging request screen requesting the user to re-image and send the receipt to the user terminal 12 over the Internet 15 in response to the HTTP request received in step S192. In other words, if, in step S197, it cannot be reliably determined whether the receipt is counterfeit or an appropriate receipt issued by an affiliated store, the user may be requested to re-image the receipt.

[0274] [Other variations] In the embodiment, the service providing system 10 is described as being capable of handling both receipts and electronic payments. However, the service providing system 10 may be capable of handling only receipts or invoices, or may be capable of handling only electronic payments.

[0275] In the embodiment, an example has been described in which the terminal program 38 of the user terminal 12 reads the name of the payment store, the date and time of payment, and the payment amount from the payment image data. However, the server program 27 of the management server 11 may read the name of the payment store, the date and time of payment, and the payment amount from the payment image data. In that case, the terminal program 38 of the user terminal 12 skips step S143 in the coupon issuance process (see FIG. 12 ), in which the name of the payment store, the date and time of payment, and the payment amount are read from the payment image data, and generates a coupon issuance request including the payment image data (S144). The process in which the server program 27 reads the name of the payment store, the date and time of payment, and the payment amount from the payment image data is an example of a reading process.

[0276] In the embodiment, an example has been described in which the camera 16 of the user terminal 12 captures an image of a QR code (registered trademark) affixed to the door of a managed store at the time of check-in, temporary leaving, re-entering, and check-out. That is, an example has been described in which the terminal program 38 of the user terminal 12 reads a store ID from the QR code (registered trademark) captured by the camera 16. However, the terminal program 38 of the user terminal 12 may acquire a store ID by a method other than capturing an image of a QR code (registered trademark). For example, the terminal program 38 may display an input screen for accepting input of a store ID or the name of a managed store on the display 34 at the time of check-in, temporary leaving, re-entering, and check-out. Alternatively, the terminal program 38 may acquire the store ID or the name of a managed store from the store terminal 13 by short-range wireless communication with the store terminal 13. That is, the terminal program 38 may acquire the store ID or the name of a managed store by any method.

[0277] In the embodiment, an example was described in which the conditions for issuing a coupon were that the affiliated store name and the name of the payment store match (S148: Yes), that the payment date and time are within the validity period (S152: Yes), and that the receipt or electronic payment used to issue the coupon is not the same as the receipt or electronic payment used to request issuance of the current coupon (S154: No, S155: No). However, the condition for issuing a coupon may be that only the affiliated store name and the name of the payment store match. Alternatively, the conditions for issuing a coupon may be that the affiliated store name and the name of the payment store match and that the payment date and time are within the validity period. Alternatively, the conditions for issuing a coupon may be that the affiliated store name and the name of the payment store match and that the receipt or electronic payment used to issue the coupon is not the same as the receipt or electronic payment used to request issuance of the current coupon.

[0278] In the embodiment, the operated store is described as having the door lock device 14 installed on the door. However, the operated store may be provided with a gate having a bar that restricts entry instead of the door and the door lock device 14.

[0279] In the embodiment, the operated store is described in which the door lock device 14 is installed on the door. However, the operated store may be a store in which the door lock device 14 is not installed on the door, or may be an open-space store. In such a case, the process of unlocking the door is omitted.

[0280] In the embodiment, an example has been described in which a coupon is used to reduce (discount) the usage fee of a managed store on the issue date. That is, an example has been described in which a coupon is valid only on the issue date. However, a coupon may be valid for a predetermined period from the issue date. The predetermined period may be, for example, three days or one week.

[0281] In the embodiment, an example has been described in which both a determination of whether the payment amounts match in step S153 and a determination of whether the payment dates and times match in step S154 are performed. However, only one of the determination processes in step S153 and S154 may be performed. That is, whether the receipt or electronic payment used to request the issuance of a coupon is a receipt or electronic payment for which a coupon has already been issued may be determined based on at least one of a match in the payment amounts and a match in the payment dates and times. Alternatively, if the payment amounts and the payment dates and times match, a rejection notice (s149) may be sent.

[0282] In the embodiment, an example was described in which whether a receipt or electronic payment used to issue a coupon is the same as the receipt or electronic payment used to request the current coupon issuance is determined based on whether the payment date and time and the payment amount match. However, this determination may also be made based on whether the names of the purchased products written on the receipts match.

[0283] In the embodiment, a managed store that can accept user reservations has been described. However, a managed store may not accept reservations. Furthermore, all managed stores may not accept reservations, or only some managed stores may not accept reservations. In other words, there may be a mixture of managed stores that do not accept reservations and managed stores that can accept reservations. Managed stores that do not accept reservations may be determined according to the type of affiliated store, or may be determined individually for each managed store. For example, a flag indicating whether reservations can be accepted is registered in the store management database (see FIG. 3) in association with the store ID of the managed store. For managed stores that do not accept reservations, the server program 27 of the management server 11 does not execute reservation processing (see FIG. 4) and directly registers the check-in date and time, check-out date and time, etc. in the usage information in the user management database (see FIG. 2).

[0284] In the embodiment, an example has been described in which the terminal program 38 and the reading program 39 are different programs. However, the terminal program 38 and the reading program 39 may be a single program. For example, the reading program 39 may be incorporated into the terminal program 38 as a module.

[0285] In this embodiment, the validity period for which a coupon can be issued is the period from a time a predetermined time before the check-in time to the check-in time (S151). The predetermined period may be changed depending on the type of affiliated store. Alternatively, it may be changed for each managed store. For example, a predetermined period for calculating the validity period may be registered for each managed store, i.e., for each record, in the store management database.

[0286] The vertical length of a receipt increases depending on the number of items purchased by the user. If the vertical length of a receipt increases, there is a possibility that the user terminal 12 will not be able to capture the entire receipt in one capture. After capturing an image with the camera 16, the terminal program 38 of the user terminal 12 may display on the display a screen that includes, for example, the text "Do you want to continue capturing images or stop capturing images?" along with a "Continue" icon and an "End" icon. When the "Continue" icon is selected, the terminal program 38 acquires multiple captured image data as payment image data. [Explanation of symbols]

[0287] 10. Service provision system 11. Management Server 12. User terminal 13. Store terminal 14 Door lock device 15. Internet 16. Camera 21. CPU 22. Memory 23 Communication Interface 27. Server program 31 CPU 32...Memory 33 Communication Interface 34 Display 35 Input interface 37. Browser 38. Terminal Program 39 Reading program 41 CPU 42 Memory 43 Communication Interface 48···Store Program 51 Control unit 52 Drive unit 53 Communication Interface

Claims

1. a management server having a first communication interface connected to the Internet, a server memory for storing a management database, and a first controller; a user terminal including a second communication interface connected to the Internet, a terminal memory that stores user identification information that identifies a user, an input interface, a display, a camera having an image sensor, and a second controller, The management database stores the names of affiliated stores in association with store identification information, The second controller a check-in application process for transmitting a check-in application including the store identification information and the user identification information to the management server via the second communication interface; a payment image data acquisition process that, based on receiving a first instruction through the input interface, captures an image of the payment record sheet using the camera and acquires it as payment image data, or, based on receiving a second instruction through the input interface, acquires screen data of the electronic payment screen displayed on the display as payment image data; After the check-in application process is executed, a coupon application process is executed to transmit a coupon issuance application including the payment image data or the payment store name acquired from the payment image data and the user identification information to the management server via the second communication interface; The first controller a check-in registration process for registering the store identification information and the user identification information included in the check-in application in association with a check-in date and time in the management database based on reception of the check-in application via the first communication interface; a payment store name acquisition process for acquiring a payment store name acquired from the payment image data included in the coupon issuance application or a payment store name included in the coupon issuance application based on receiving the coupon issuance application through the first communication interface; a determination process of acquiring the affiliated store name associated in the management database with the user identification information included in the coupon issuance application, and determining whether the acquired affiliated store name matches the payment store name; a coupon issuing process for issuing a coupon for the payment amount to the store based on the determination that the affiliated store name and the payment store name match in the determination process; The first controller or the second controller A service providing system that executes a reading process to obtain the name of the payment store from the image represented by the payment image data.

2. The reading process includes a process of acquiring a payment date and time from the payment image data, The first controller In the determination process, a period during which the user is not in the store is set as a valid period based on the entry / exit record including the check-in date and time registered in the management database, and a determination is further made as to whether the payment date and time is within the valid period; 2. The service providing system according to claim 1, wherein the coupon issuing process is executed based on the determination that the payment date and time is within the validity period and the affiliated store name and the payment store name match.

3. The service providing system according to claim 2 , wherein the validity period includes a period of a predetermined time before the check-in date and time.

4. A door lock device installed at the entrance of the store; a store terminal having a third communication interface and a third controller connected to the Internet, and for locking and unlocking the door lock device, The second controller a temporary leave application process for transmitting a temporary leave application including the store identification information and the user identification information to the management server via the second communication interface; a re-entry request process for transmitting a re-entry request including the store identification information and the user identification information to the management server via the second communication interface; The first controller an unlock instruction sending process for sending an unlock instruction to the store terminal through the first communication interface based on receiving the temporary exit request or the re-entry request through the first communication interface; a temporary exit registration process for registering the temporary exit date and time and the re-entry date and time in the management database in association with the user identification information; The entry and exit record includes the check-in date and time, the temporary exit date and time, and the re-entry date and time. The service providing system according to claim 2 , wherein the validity period includes a period from the date and time of temporary leaving the room to the date and time of re-entering the room.

5. The reading process includes a process of acquiring at least one of a payment date and time and a payment amount from the payment image data, The coupon issuing process includes a process of registering the name of the store where the payment is made and at least one of the date and time of the payment and the amount of the payment in the management database, The first controller In the determination process, it is further determined whether or not at least one of the payment date and time and payment amount acquired in the payment store name acquisition process matches at least one of the payment date and time and payment amount registered in the management database, and at least one of the payment date and time and payment amount for which a coupon has been issued; The service provision system of claim 1, wherein the coupon issuance process is executed based on the determination that at least one of the payment date and time and payment amount acquired in the payment store name acquisition process does not match at least one of the payment date and time and payment amount registered in the management database, and that the affiliated store name and the payment store name match.

6. The reading process includes a process of acquiring a payment date and time from the payment image data, The first controller In the determination process, it is further determined whether the coupon issuance request date and time is within the validity period from the payment date and time until a predetermined time has elapsed, 2. The service providing system according to claim 1, wherein the coupon issuing process is executed based on the determination that the coupon issuance request date and time is within the validity period and that the affiliated store name and the payment store name match.

7. The first controller further executing a list screen data transmission process for transmitting store list screen data including the store identification information and the store name, affiliated store name, and affiliated store type associated in the management database to the user terminal via the first communication interface; The second controller 2. The service providing system according to claim 1, further comprising a first display process for displaying, on the display, a store list screen indicated by the store list screen data received through the second communication interface.

8. The second controller further executing a reservation request process to transmit a reservation request including the store identification information, the reservation date and time, and the user identification information to the management server via the second communication interface; The first controller, based on receiving the reservation request through the first communication interface, a reservation registration process for registering the store identification information, the reservation date and time, and the user identification information in the management database in association with each other; a first notification process for transmitting first notification screen data showing a first notification screen having the store identification information included in the reservation application and the affiliated store name associated in the management database to the user terminal via the first communication interface; 2. The service providing system according to claim 1, wherein the second controller further executes a second display process for displaying the first notification screen on the display based on receiving the first notification screen data through the second communication interface.

9. The first controller further executes a second notification process to transmit, based on receiving the temporary leave request through the first communication interface, second notification screen data showing a second notification screen having the affiliated store name and coupon notification information to the user terminal as a response to the temporary leave request through the first communication interface; 5. The service providing system according to claim 4, wherein the second controller further executes a third display process for displaying the second notification screen on the display based on receiving the second notification screen data through the second communication interface.

10. 2. The service providing system according to claim 1, wherein the fees paid to the store include a store usage fee according to the time the store is used and a facility usage fee for the use of facilities installed in the store.

11. The second controller execute a checkout request process to transmit a checkout request including the store identification information, the user identification information, and an instruction to use the coupon to the management server via the second communication interface; The first controller based on the checkout request received through the first communication interface including the use instruction; a usage time calculation process for calculating usage time based on the user identification information included in the check-out request and the check-in date and time associated in the management database; 2. The service providing system according to claim 1, further comprising: a fee calculation process for calculating the fee to be paid based on the usage time and the coupon indicated by the usage instruction.

12. The first controller a judgment data registration process for acquiring sample image data showing a sample of the payment record sheet through the first communication interface, acquiring counterfeit judgment data from the sample image data, and registering the counterfeit judgment data in the management database; and further executing a suitability determination process for determining the suitability of the payment image data based on the counterfeit determination data. The first controller 2. The service providing system according to claim 1, wherein the coupon issuing process is executed based on the determination that the transaction is appropriate in the appropriateness determination process and the determination that the affiliated store name and the payment store name match in the determination process.

13. a server program installed in a management server having a first communication interface connected to the Internet, a server memory for storing a management database, and a first computer; a terminal program implemented in a user terminal having a second communication interface connected to the Internet, a terminal memory that stores user identification information that identifies a user, an input interface, a display, a camera having an image sensor, and a second computer, The management database stores the names of affiliated stores in association with store identification information, The above terminal program is a check-in application process for transmitting a check-in application including the store identification information and the user identification information to the management server via the second communication interface; a payment image data acquisition process for acquiring payment image data by capturing an image of a payment record sheet using the camera based on receipt of a first instruction through the input interface, or acquiring screen data of a state in which a payment screen is displayed on the display based on receipt of a second instruction through the input interface, as payment image data; After the check-in application process is executed, the second computer executes a coupon application process for transmitting a coupon issuance application including the payment image data or the payment store name acquired from the payment image data and the user identification information to the management server via the second communication interface; The server program is a check-in registration process for registering the store identification information and the user identification information included in the check-in application in association with a check-in date and time in the management database based on reception of the check-in application via the first communication interface; a payment store name acquisition process for acquiring a payment store name acquired from the payment image data included in the coupon issuance application or a payment store name included in the coupon issuance application based on receiving the coupon issuance application through the first communication interface; a determination process of acquiring the affiliated store name associated in the management database with the user identification information included in the coupon issuance application, and determining whether the acquired affiliated store name matches the payment store name; and causing the second computer to execute a coupon issuing process for issuing a coupon related to the payment amount to the store based on the determination that the affiliated store name and the payment store name match in the determination process; The server program or the terminal program is A program that causes the first computer or the second computer to execute a reading process to obtain the name of the payment store from the image represented by the payment image data.

Images