Facility management device and program thereof

Abstract

To enable a user of a facility to make settlement of fees associated with using the facility by using a mobile terminal.SOLUTION: A facility management device includes linking means, providing means, receiving means, and processing means. The linking means links facility information identifying a facility used by a user with terminal information identifying a mobile terminal used by the user. The providing means provides a fee associated with the use of the facility to the mobile terminal identified by the terminal information linked to the facility information of the facility. The receiving means receives a notification that settlement of the fee has been made on the mobile terminal. The processing means executes processing related to the end of use of the facility identified by the facility information linked to the terminal information of the mobile terminal on which the settlement has been made.SELECTED DRAWING: Figure 6

Description

[Technical field]

[0001] An embodiment of the present invention relates to a facilities management device and a program therefor. [Background technology]

[0002] For example, in facilities that serve food and drink, such as karaoke booths, darts bars, and manga cafes, the fee varies depending on the food and drink consumed, so it is common to settle the bill when you leave the facility. The bill is usually settled using an accounting terminal such as a Point Of Sales (POS) terminal or a self-service POS terminal.

[0003] On the other hand, in recent years, so-called mobile payments, which are cashless payments made using payment application software installed on mobile devices such as smartphones, have become widespread. Making mobile payments available for payment situations at facilities such as those mentioned above is extremely convenient as it can ease congestion at checkouts and also acts as a measure against infectious diseases.

[0004] In order for facility users to pay their fees using mobile payments, the facility's billing system must be linked to the mobile devices owned by the users. However, at present, there is no mechanism for linking the facility's billing system with mobile devices, so mobile payments cannot be used. [Prior art documents] [Patent documents]

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

[0006] The problem that an embodiment of the present invention aims to solve is to provide a facility management device that enables users of the facility to pay fees associated with the use of the facility using their own mobile terminal. [Means for solving the problem]

[0007] In one embodiment, the facility management device includes a linking means, a providing means, a receiving means, and a processing means. The linking means links facility information identifying a facility used by a user with terminal information identifying a mobile terminal used by the user. The providing means provides a fee associated with the use of the facility to the mobile terminal identified by the terminal information linked with the facility information of the facility. The receiving means receives a notification that payment of the fee has been made at the mobile terminal. The processing means executes processing related to the end of use of the facility identified by the facility information linked with the terminal information of the mobile terminal for which payment has been made. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a schematic diagram showing a schematic configuration of a facility management system according to an embodiment. [Diagram 2] FIG. 2 is a sequence diagram illustrating an outline of the operation of the store system. [Diagram 3] FIG. 3 is a schematic diagram showing the data structure of a transaction record stored in a transaction file. [Figure 4] FIG. 4 is a schematic diagram showing the data structure of an order record stored in an order file. [Diagram 5] FIG. 5 is a block diagram showing a main circuit configuration of a mobile terminal. [Figure 6] FIG. 6 is a block diagram showing the main circuit configuration of the infrastructure server. [Figure 7] FIG. 7 is a schematic diagram showing the configuration of the linkage table. [Figure 8] FIG. 8 is a flowchart showing the main operational procedure when the processor of the infrastructure server receives an entry notification event or an exit notification event. [Figure 9]FIG. 9 is a flowchart showing the procedure of main information processing executed by the processor of the mobile terminal based on the store app. [Figure 10] FIG. 10 is a flowchart showing the main steps of a slip reading process executed by a processor of a mobile terminal, and the main steps of information processing executed by a processor of a base server in conjunction with the process. [Figure 11] FIG. 11 is a flowchart showing the main steps of a product order process executed by a processor of a mobile terminal and the main information processing steps executed by a processor of a base server in conjunction with the process. [Figure 12] FIG. 12 is a flowchart showing the main steps of the accounting process executed by the processor of the mobile terminal and the main information processing steps executed by the processor of the infrastructure server in conjunction with the transaction. [Figure 13] FIG. 13 is a sequence diagram for explaining an outline of the operation of the facility management system including the mobile terminal. [Figure 14] FIG. 14 shows an example of a top screen displayed on the touch panel of a mobile terminal. [Figure 15] FIG. 15 is an example of a reading screen displayed on the touch panel of a mobile terminal. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment of a facility management device that enables a user of a facility to pay for the use of the facility using a mobile terminal owned by the user will be described with reference to the drawings. In this embodiment, a karaoke box is exemplified as a facility. A karaoke box is a facility where a user can enjoy karaoke while eating and drinking. A karaoke box can be called a karaoke room or the like. A karaoke box is generally provided in a karaoke store. The karaoke store manages the usage status of the karaoke box. Specifically, the karaoke store manages entry into the karaoke box, so-called check-in, and exit from the karaoke box, so-called check-out. The karaoke store also provides food and drink menu items ordered by the user. When the user checks out, the karaoke store receives payment from the user for a total fee that includes the usage fee for the karaoke box and the price of the food and drink menu items. This embodiment discloses a facility management device that enables a user who uses the karaoke box to pay for the fee associated with the use of the karaoke box with a mobile terminal owned by the user, and a facility management system including the facility management device.

[0010] [Explanation of facility management system] 1 is a schematic diagram showing a general configuration of a facility management system 100. The facility management system 100 includes multiple store systems 1, a mobile server 2, and a platform server 3. The platform server 3 is an example of a facility management device.

[0011] The multiple store systems 1 are a common system established in karaoke stores that are part of a chain. The store system 1 includes a store server 11, a reception terminal 12, an accounting terminal 13, a kitchen terminal 14, and a station 15. The store system 1 connects the store server 11 with the reception terminal 12, the accounting terminal 13, the kitchen terminal 14, and the station 15 via a communication network 16 such as a LAN (Local Area Network).

[0012] The reception terminal 12 and the accounting terminal 13 are installed at the reception of the karaoke booth. The reception is a place where a user stops by before entering the karaoke booth or after leaving the karaoke booth. The reception is also called the front desk.

[0013] The reception terminal 12 accepts entry to the karaoke booth, i.e., check-in. Check-in is a task of inputting the room number, member ID, whether a reservation has been made, the karaoke fee plan and the usage time, etc. The room number is unique identification information assigned to each karaoke booth in order to individually identify the multiple karaoke booths in a karaoke store.

[0014] A member ID is unique identification information assigned to a user who has signed a membership contract with a karaoke store, a so-called member. A user registers as a member by installing store-specific application software, a so-called store app, on a mobile terminal 5 such as a smartphone or tablet terminal that the user owns. By registering as a member, the user becomes a member and is assigned a unique member ID. The member ID is displayed on the screen of the mobile terminal in the form of a machine-readable code such as a barcode or two-dimensional code by activating the store app.

[0015] The accounting terminal 13 accepts exit from the karaoke booth, that is, check-out. The accounting terminal 13 also processes the payment of fees associated with the use of the karaoke booth. The accounting terminal 13 supports various payment methods, such as cash, credit card, electronic money, and code payment. The accounting terminal 13 may be one that supports only one of the payment methods. The accounting terminal 13 can also be called a payment terminal, a POS (Point Of Sales) terminal, etc.

[0016] Incidentally, the reception terminal 12 and the accounting terminal 13 may be face-to-face terminals operated by a store clerk, or may be self-service terminals operated by the customer themselves. Alternatively, they may be terminal devices that combine the functions of the reception terminal 12 and the accounting terminal 13 in one device.

[0017] Kitchen terminal 14 is a device for outputting information on food and beverage menu items ordered by karaoke booth patrons. There are two types of kitchen terminal 14: one that outputs information on food and beverage menu items by displaying it on a display device, and one that outputs information on food and beverage menu items by printing it on recording paper using a printer. Kitchen terminal 14 is generally installed in the kitchen of the karaoke store. The kitchen staff uses the information output from kitchen terminal 14 to ascertain the food and beverage menu items ordered by karaoke booth patrons, prepares them, and serves them to the patrons.

[0018] Station 15 manages information on food and drink menu items ordered by users of the karaoke booth. Station 15 stores information on the food and drink menu items ordered by each user of the karaoke booth. Station 15 then calculates the price of the food and drink menu items ordered by each user based on the stored information.

[0019] The store server 11 is a computer that supports the operations of a karaoke store by controlling the reception terminal 12, the accounting terminal 13, the kitchen terminal 14, and the station 15. For example, the store server 11 manages the usage status of karaoke booths based on data processed by the reception terminal 12 and the accounting terminal 13. Specifically, the store server 11 manages a karaoke booth for which check-in has been accepted by the reception terminal 12 as being in use. After that, when payment for the karaoke booth user is completed by the accounting terminal 13, the store server 11 manages that karaoke booth as being unused.

[0020] The store server 11 also calculates the fee for using the karaoke box for each user from the karaoke box usage fee based on the karaoke fee course and usage time received at the reception terminal 12, and the prices of food and drink menu items calculated by the station 15. The user pays this fee when checking out. Therefore, the store system 1 can be said to be a fee billing system for a karaoke store.

[0021] 2 is a sequence diagram for explaining the general operation of the store system 1. The reception terminal 12 accepts check-in. The operator of the reception terminal 12 inputs the room number of the karaoke booth that the user will be using. The operator also inputs the karaoke fee course and usage time that the user desires. If the user is a member, the operator inputs the member ID. If the user is the person who made the reservation, the operator inputs a reservation code. The operator may be a store clerk or the user himself.

[0022] The reception terminal 12 that has accepted the check-in transmits a reception request event Ea to the store server 11. The reception request event Ea includes the room number, member ID, karaoke fee course, and usage time entered at the time of check-in. If there is a reservation, the reservation number is also included in the reception request event Ea.

[0023] The store server 11, which has received the reception request event Ea, executes the entry process. The entry process is a process of creating a transaction record 61 having the data structure shown in Fig. 3 and saving it in the transaction file 6. The store server 11 uses a part of the memory area of ​​a built-in or external storage device as the transaction file 6.

[0024] 3, the transaction record 61 includes the room number, the entry time, the scheduled exit time, the karaoke fee course, the usage time, the usage fee, the slip number, the member ID, and the status. The room number, the course, the usage time, and the member ID are data included in the reception request event Ea.

[0025] The entry time is the time when check-in is performed at the reception terminal 12. Alternatively, the entry time is the time when the store server 11 receives the reception request event Ea. The scheduled exit time is the time after the usage time has elapsed from the entry time.

[0026] The usage fee is an amount derived from the karaoke fee course and the usage time, etc. Normally, a basic fee per unit time is set for the course, so the store server 11 calculates the usage fee by multiplying the basic fee by an integer obtained by rounding up the quotient obtained by dividing the usage time by the unit time.

[0027] The slip number is a unique number that is issued by the store server 11 each time a reception request event Ea is received. After a user has checked in, the user is identified by the slip number until the user checks out.

[0028] The status indicates the state of the karaoke booth identified by the room number. The karaoke booth can be in use or unused. The transaction record 61 is created in response to receiving the reception request event Ea, that is, after check-in, so the status at the time of creating the transaction record indicates the in use state.

[0029] Returning to the explanation of Figure 2. After completing the entry process, the store server 11 transmits a receipt issuance event Eb to the reception terminal 12. The receipt issuance event Eb includes information of the transaction record 61. The reception terminal 12 that receives the receipt issuance event Eb issues a reception slip. The reception slip is printed with the room number, entry time, expected exit time, karaoke fee course, usage time, usage fee, slip number, etc. In addition, a machine-readable code such as a barcode or two-dimensional code is printed on the reception slip. The machine-readable code is a representation of the store code and slip number in the form of a machine-readable code. The store code is unique identification information set for each store to identify each karaoke store in a chain.

[0030] Furthermore, when the store server 11 completes the entry process, it transmits an entry notification event Ec to the station 15 and the infrastructure server 3. The entry notification event Ec is an event that notifies the user that they have entered the karaoke booth. The entry notification event Ec includes the room number included in the reception request event Ea and the slip number issued by the store server 11. If a member ID was included in the reception request event Ea, the member ID is also included. The entry notification event Ec also includes a store code. The operation of the infrastructure server 3 that receives the entry notification event Ec will be described later.

[0031] The station 15 that receives the entry notification event Ec creates an order record 71 having the data structure shown in Fig. 4 and stores it in the order file 7. The station 15 uses a part of the storage area of ​​a built-in or external storage device as the order file 7.

[0032] As shown in FIG. 4, order record 71 includes a room number, a receipt number, order data, and a status. The room number and receipt number are data included in the entry notification event Ec. The order data is data on the food and drink menu items ordered by a patron who entered the karaoke booth identified by the room number. The status, like transaction record 61, indicates the state of the karaoke booth identified by the room number. Since order record 71 is created in response to receiving an entry notification event Ec, that is, after check-in, the status at the time the order record is created indicates that it is in use.

[0033] Returning to the explanation of Figure 2. The reception terminal 12 has an order reception function. The order reception function is a function for receiving data on food and beverage menu items ordered by a user. An operator of the reception terminal 12 inputs the item code, order quantity, etc. of the food and beverage menu item ordered by the user. The item code is unique identification information assigned to each food and beverage menu item. The reception terminal 12 transmits an order event Ed to the store server 11 each time data on a food and beverage menu item is input. The order event Ed includes the room number of the karaoke booth used by the user, and the item code, order quantity, etc. of the food and beverage menu item ordered by the user.

[0034] The store server 11, which receives the order event Ed, transfers the order event Ed to the station 15. The station 15 executes order processing each time it receives an order event Ed. The order processing creates order data based on the item code and order quantity included in the order event Ed. The order data includes the item code, the item name and price of the food and drink menu item identified by the item code, the order quantity, and the amount calculated by multiplying the price by the order quantity. The station 15 adds the order data to the order record 71 in which the room number included in the order event Ed is set.

[0035] The accounting terminal 13 accepts check-out of patrons who have used the karaoke booth. An operator of the accounting terminal 13 inputs the slip number of the reception slip issued to the patron who is leaving the karaoke booth at the time of reception. The operator inputs the slip number by reading the machine-readable code printed on the reception slip with a scanner. The operator may be a store clerk or the patron himself.

[0036] When the accounting terminal 13 accepts the checkout, it sends an accounting request event Ee to the store server 11. The accounting request event Ee includes the slip number. Upon receiving the accounting request event Ee, the store server 11 sends an order call event Ef to the station 15. The order call event Ef includes the slip number obtained from the accounting request event Ee.

[0037] The station 15 that has received the order call event Ef acquires the order record 71 including the slip number acquired from the order call event Ef. The station 15 then returns the order data included in the order record 71 to the store server 11.

[0038] The store server 11 executes a totaling process. This process adds up the cost of the food and drink menu items calculated based on the order data obtained from the station 15 to the usage fee of the transaction record 61, which includes the slip number obtained from the accounting request event Ee. If the departure time at which check-out occurs is later than the scheduled departure time, the store server 11 adds an extension fee to the usage fee. The store server 11 then adds up the cost of the food and drink menu items to the usage fee to which the extension fee has been added.

[0039] After completing the total processing, the store server 11 transmits the fee data to the accounting terminal 13. The fee data is the total amount of the karaoke booth usage fee and the cost of the food and drink menu items, that is, data on the fee for using the karaoke booth. The fee data also includes details of the fee, such as the karaoke booth usage fee, the names and prices of the food and drink menu items, and the number of items ordered.

[0040] Upon receiving the fee data, the accounting terminal 13 displays the fee on a display device and accepts payment of the fee. Then, upon accepting payment, the accounting terminal 13 executes a settlement process. When the fee is paid with cash, for example, the settlement process subtracts the fee from the payment amount and calculates the difference as change. When the fee is paid with a credit card, for example, the settlement process requests authentication of the credit card from the settlement server of that credit card, and if authentication is successful, issues a credit slip. When the fee is paid with electronic money, for example, the settlement process subtracts the fee from the balance of that electronic money.

[0041] When the payment process is completed, the accounting terminal 13 issues a receipt. The receipt may be printed on a paper medium or may be issued as an electronic receipt that can be viewed on the user's smartphone. The accounting terminal 13 also sends a payment completion event Eg to the store server 11. The payment completion event Eg includes the slip number entered at checkout. Upon receiving the payment completion event Eg, the store server 11 updates the status of the transaction record 61 in which the slip number obtained from the payment completion event Eg is set from in use to unused. The store server 11 also sends an exit notification event Eh to the station 15 and the infrastructure server 3. The exit notification event Eh includes the slip number obtained from the payment completion event Eg and the room number of the transaction record 61 in which the slip number is set. The exit notification event Eh also includes the store code. The station 15 that has received the exit notification event Eh updates the status of the order record 71, including the room number and slip number acquired from the exit notification event Eh, from "in use" to "unused." The operation of the infrastructure server 3 that has received the exit notification event Eh will be described later.

[0042] Returning to the explanation of Figure 1. The facility management system 100 connects the store server 11 of each store system 1, the mobile server 2, and the infrastructure server 3 via an inter-server network 4. The inter-server network 4 is typically the Internet or an intranet.

[0043] The mobile server 2 provides a two-way data communication service with a mobile terminal 5 owned by a user of the karaoke booth. The mobile server 2 provides the data communication service using a short-range wireless communication network such as Wi-Fi (registered trademark) or a mobile communication network.

[0044] The infrastructure server 3 links the store system 1, which functions as a billing system, with the mobile terminal 5 owned by a user who uses a karaoke box in a karaoke store in which the store system 1 is installed. The infrastructure server 3 provides a first service that enables a user of the karaoke box to order food and drink menu items by operating the mobile terminal 5. The infrastructure server 3 also provides a second service that enables a user of the karaoke box to pay the fee for using the karaoke box by mobile payment using the mobile terminal 5. The infrastructure server 3 may provide the service in an on-premise environment or in a cloud computing environment.

[0045] [Mobile device configuration explanation] 5 is a block diagram showing the main circuit configuration of the mobile terminal 5. The mobile terminal 5 includes a processor 51, an internal storage 52, a wireless communication unit 53, a memory interface 54, a touch panel 55, a camera 56, and a system transmission path 57. The system transmission path 57 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 57 connects the processor 51 to each of the other units directly or via a signal input / output circuit, and transmits data signals exchanged between them.

[0046] The mobile terminal 5 constitutes a computer by connecting the processor 51, the internal storage 52, and the wireless communication unit 53 through a system transmission path 57. The mobile terminal 5 connects the memory interface 54, the touch panel 55, the camera 56, and the like to the system transmission path 57 via a signal input / output circuit (not shown). The memory interface 54 is an interface for transmitting and receiving data signals to and from an external memory 58 that is detachably attached. The external memory 58 is typically an SD memory card, a miniSD card, a microSD card, or the like. The touch panel 55 functions as a display device and an input device of the mobile terminal 5. The camera 56 functions as an imaging device of the mobile terminal 5. Note that the interfaces, devices, and the like connected to the system transmission path 57 are not limited to those described above. Other interfaces, devices, and the like may be connected.

[0047] The processor 51 corresponds to the central part of the computer. The processor 51 controls each part to realize various functions of the mobile terminal 5 according to an operating system or an application program. The processor 51 is, for example, a CPU (Central Processing Unit).

[0048] The internal storage 52 is a storage device built into the housing of the mobile terminal 5. The internal storage 52 stores an operating system or an application program. The internal storage 52 may also store data necessary for the processor 51 to execute processes for controlling each unit.

[0049] The wireless communication unit 53 performs wireless data communication with the mobile server 2, for example, by using a short-distance wireless communication network such as Wi-Fi or a mobile communication network.

[0050] For example, a smartphone, tablet terminal, or the like carried by a user can be the mobile terminal 5. The mobile terminal 5 stores a store app 521 in its internal storage. The mobile terminal 5 also stores a payment app 522 in its internal storage. The payment app 522 is application software for processing mobile payments. Mobile payment refers to cashless payment using the mobile terminal 5. By registering information on a credit card, electronic money, etc., along with the payment app 522 in the mobile terminal 5, the mobile terminal 5 becomes capable of mobile payment.

[0051] The installation destination of the store application 521 and the payment application 522 is not limited to the internal storage 52. The store application 521 and the payment application 522 may be installed in the external memory 58. Alternatively, one application, for example, the store application 521, may be installed in the internal storage, and the other application, that is, the payment application 522, may be installed in the external memory 58.

[0052] [Configuration of the infrastructure server] 6 is a block diagram showing the main circuit configuration of the infrastructure server 3. The infrastructure server 3 includes a processor 31, a main memory 32, an auxiliary storage device 33, a clock 34, a communication interface 35, and a system transmission path 36. The system transmission path 36 includes an address bus, a data bus, a control signal line, and the like. The system transmission path 36 connects the processor 31 to each of the other components, and transmits data signals exchanged between them. The infrastructure server 3 constitutes a computer by connecting the processor 31 to the main memory 32, the auxiliary storage device 33, the clock 34, and the communication interface 35 via the system transmission path 36.

[0053] The processor 31 corresponds to the central part of the computer. The processor 31 controls each part to realize various functions of the infrastructure server 3 according to an operating system or an application program. The processor 31 is, for example, a CPU. The processor 31 is preferably a multi-core processor that includes multiple processor cores and is capable of executing multiple processes in parallel.

[0054] The main memory 32 corresponds to the main storage portion of the computer. The main memory 32 includes a nonvolatile memory area and a volatile memory area. The main memory 32 stores an operating system or an application program in the nonvolatile memory area. The main memory 32 may store data required for the processor 31 to execute processes for controlling each part in the nonvolatile or volatile memory area. The main memory 32 uses the volatile memory area as a work area where data is appropriately rewritten by the processor 31. The nonvolatile memory area is, for example, a ROM (Read Only Memory). The volatile memory area is, for example, a RAM (Random Access Memory).

[0055] The auxiliary storage device 33 corresponds to the auxiliary storage portion of the computer. For example, an EEPROM (registered trademark) (Electric Erasable Programmable Read-Only Memory), a HDD (Hard Disk Drive), or an SSD (Solid State Drive) can be the auxiliary storage device 33. The auxiliary storage device 33 stores data used by the processor 31 in performing various processes, data created by the processes in the processor 31, etc. The auxiliary storage device 33 may also store the above-mentioned application programs.

[0056] The clock 34 keeps track of the date and time. The processor 31 processes the date and time kept by the clock 34 as the current date and time.

[0057] The communication interface 35 is an interface for performing data communication with other servers connected to the inter-server network 4, that is, the store server 11 and the mobile server 2.

[0058] In order to realize the first and second services described above, the infrastructure server 3 configured as above uses part of the memory area in the auxiliary memory device 33 as an area for a product file 331, a member file 332, and a linkage table 333 by store.

[0059] The product file 331 stores data related to various food and drink menu items provided to customers at the karaoke store. Specifically, the product file 331 stores data such as the item name, price, etc. in association with the product code of each menu item.

[0060] Member file 332 stores data on users who have become members of the karaoke store. Specifically, member file 332 stores data such as the user's name, email address, and membership validity period in association with the user's membership ID.

[0061] The linkage table 333 is prepared for each karaoke store that is part of a chain. Each linkage table 333 has the same configuration and is identified by a store code. As shown in FIG. 7, the linkage table 333 is composed of a column Ca of room numbers, a column Cb of slip numbers, a column Cc of member IDs, and a column Cd of linkage flags F. The column Ca describes the room numbers of each karaoke booth provided in the karaoke store identified by the store code. The columns Cb and Cc describe the slip number of the reception slip issued to the user when the user enters the karaoke booth identified by the room number in the same row, and the member ID of the user. If the user is not a member, the member ID is not described in column Cc. The column Cd describes the linkage flag F. The linkage flag F is one-bit data for identifying whether the karaoke booth identified by the room number in the same row and the mobile terminal 5 of the user who entered the karaoke booth are in a linked state. In this embodiment, the link flag F indicating that the two devices are not in a linked state is set to "0," and the link flag F indicating that the two devices are in a linked state is set to "1."

[0062] Furthermore, in order to realize the first and second services described above, the infrastructure server 3 is configured such that the processor 31 has the functions of a linking means 311, a providing means 312, a receiving means 313, a processing means 314, a billing acceptance means 315, and an order acceptance means 316. These functions are realized by a control program installed in the main memory 32 or the auxiliary storage device 33 of the infrastructure server 3. The method of installing the control program in the main memory 32 or the auxiliary storage device 33 is not particularly limited. The control program distributed by communication via the inter-server network 4 can be received and installed in the main memory 32 or the auxiliary storage device 33. Alternatively, the control program can be recorded on a removable recording medium and installed in the main memory 32 or the auxiliary storage device 33. The recording medium may be in any form, such as a CD-ROM or a memory card, as long as it can store a program and is readable by a device.

[0063] The linking means 311 is a function for linking facility information identifying a facility used by a user with terminal information identifying a mobile terminal 5 used by the user. A member ID is set in the store app 521 installed in the mobile terminal 5 as information for identifying the owner. That is, the member ID can be terminal information identifying the mobile terminal 5 used by the user. Meanwhile, a karaoke booth, which is a facility used by a user, is identified by a room number. That is, the room number can be facility information identifying a facility used by a user. The linking means 311 uses the linking table 333 to link the room number as facility information identifying the facility used by the user, that is, the karaoke booth, with the member ID as terminal information identifying the mobile terminal 5 used by the user who uses the karaoke booth.

[0064] The provision means 312 is a function that provides the fee associated with the use of a facility to the mobile terminal 5 specified by terminal information linked to the facility information of the facility. That is, the provision means 312 provides the fee associated with the use of the facility, that is, the fee associated with the use of the karaoke booth, to the mobile terminal 5 specified by the member ID linked to the room number of the karaoke booth. Specifically, the provision means 312 transmits data on the fee associated with the use of the karaoke booth to the mobile terminal 5 via the mobile server 2 by wireless communication.

[0065] The receiving means 313 is a function that receives a notification that a fee payment has been executed on the mobile terminal 5. As described above, the mobile terminal 5 is capable of mobile payment by utilizing the payment application 522. The receiving means 313 receives a notification that a fee payment has been executed by mobile payment on the mobile terminal 5. Specifically, the receiving means 313 receives a notification that a payment has been executed by receiving, via the mobile server 2, a payment completion event Eg that is output when a fee payment is executed by mobile payment on the mobile terminal 5, thereby receiving a notification that a payment has been executed.

[0066] The processing means 314 has a function of executing a process related to the end of use of a facility identified by facility information linked to the terminal information of the mobile terminal 5 on which the mobile payment was executed. That is, the processing means 314 executes a process related to the end of use of a karaoke booth identified by a room number linked to the member ID of the mobile terminal 5 on which the mobile payment was executed. Specifically, the processing means 314 changes the link flag F, which is associated with the room number of the karaoke booth and stored in the link table 333, from "1" to "0". The processing means 314 also transmits a payment completion event Eg to the store server 11 via the inter-server network 4.

[0067] The transaction approval means 315 is a function that, in response to a transaction request from a mobile terminal 5, checks whether the terminal information of the mobile terminal 5 is linked to facility information, and approves the transaction only if it is linked. That is, when the transaction approval means 315 receives a transaction request event Ee from a mobile terminal 5, it searches the association table 333 and checks whether the member ID of the mobile terminal 5 is linked to the room number. If the member ID of the mobile terminal 5 is linked to the room number, the transaction approval means 315 approves the transaction for the mobile terminal 5. Specifically, the transaction approval means 315 transmits fee data for use of the karaoke booth to the mobile terminal 5 via the mobile server 2 by wireless communication.

[0068] The order allowing means 316 is a function that, in response to a product order request from a mobile terminal 5, checks whether the terminal information of the mobile terminal 5 is linked to facility information, and accepts the product order only if it is linked. That is, when the order allowing means 316 receives an order event Ed from a mobile terminal 5, it searches the linkage table 333 and checks whether the member ID of the mobile terminal 5 is linked to a room number. Then, if the member ID of the mobile terminal 5 is linked to a room number, the order allowing means 316 accepts the order of the product requested by the mobile terminal 5. Specifically, the order allowing means 316 transmits the order event Ed to the store server 11 via the inter-server network 4.

[0069] [Explanation of operation of mobile terminals and infrastructure servers] First, the operation of the infrastructure server 3 when receiving an entry notification event Ec or an exit notification event Eh from the store server 11 of the store system 1 will be described.

[0070] 8 is a flow chart showing the main operational steps when the processor 31 of the infrastructure server 3 receives an entry notification event Ec or an exit notification event Eh. That is, when the processor 31 receives the entry notification event Ec as ACT1, the processor 31 proceeds to ACT2. The processor 31 acquires the store code from the entry notification event Ec as ACT2. The processor 31 also acquires the room number from the entry notification event Ec as ACT3. The processor 31 further acquires the slip number from the entry notification event Ec as ACT4.

[0071] Thereafter, processor 31 checks whether or not a member ID is included in the entry notification event Ec in ACT5. If a member ID is not included in the entry notification event Ec, processor 31 proceeds to ACT6. Processor 31 searches linkage table 333 identified by the store code obtained from the entry notification event Ec in ACT6, and writes the slip number obtained from the entry notification event Ec in column Cb corresponding to the room number obtained from the entry notification event Ec. Processor 31 also sets linkage flag F in column Cd corresponding to the room number to "0" in ACT7.

[0072] On the other hand, if the entry notification event Ec includes a member ID, processor 31 proceeds to ACT8. Processor 31 searches linkage table 333 identified by the store code obtained from the entry notification event Ec in ACT8, and writes the slip number and member ID obtained from the entry notification event Ec in columns Cb and Cc corresponding to the room number obtained from the entry notification event Ec. Processor 31 also sets linkage flag F in column Cd corresponding to the room number to "1" in ACT9. Processor 31 then realizes the function of linkage means 311 by processing ACT8 and ACT9.

[0073] On the other hand, when the processor 31 receives an exit notification event Eh in ACT 11, the processor 31 proceeds to ACT 12. The processor 31 acquires a store code from the exit notification event Eh in ACT 12. The processor 31 also acquires a room number from the exit notification event Eh in ACT 13.

[0074] Next, processor 31 searches linkage table 333 identified by the store code obtained from the exit notification event Eh in ACT14, and deletes the slip number and member ID written in columns Cb and Cc corresponding to the room number obtained from the exit notification event Eh. Processor 31 also sets linkage flag F in column Cd corresponding to the room number to "0" in ACT15. Here, processor 31 realizes a function as linkage cancellation means that cancels the linkage state between facility information and terminal information linked by linkage means 311 through the processing of ACT14 and ACT15.

[0075] Next, the operation of the mobile terminal 5 and the operation of the infrastructure server 3 related to that operation will be described. Fig. 9 is a flowchart showing the procedure of main information processing executed by the processor 51 of the mobile terminal 5 based on the store application 521. When the store application 521 is started, the processor 51 starts information processing of the procedure shown in the flowchart of Fig. 9. First, the processor 51 sets the screen of the touch panel 55 to the top screen SCa (see Fig. 14) as ACT21.

[0076] FIG. 14 is an example of a display of the top screen SCa. As shown in FIG. 14, the top screen SCa displays a machine-readable code indicating a member ID, such as a barcode BC. In addition, various soft key buttons, such as a receipt read button BTa, a product order button BTb, a checkout button BTc, and an end button BTd, are displayed. The receipt read button BTa is an operator that instructs the reading of the receipt number printed on the receipt. The product order button BTb is an operator that instructs the ordering of new food and drink items. The checkout button BTc is an operator that instructs payment by mobile payment. Therefore, in a mobile terminal 5 that does not have the payment application 522 installed, the checkout button BTc is not displayed on the top screen SCa. Alternatively, the checkout button BTc is grayed out and disabled. The end button BTd is an operator that instructs the end of the store application 521.

[0077] Returning to the explanation of Figure 9. The processor 51 of the mobile terminal 5 displaying the top screen SCa waits for the receipt reading button BTa to be input as ACT22, the product order button BTb to be input as ACT23, the checkout button BTc to be input as ACT24, or the end button BTd to be input as ACT25.

[0078] When the slip reading button BTa is pressed in the standby state of ACT22 to ACT25, the processor 51 proceeds to ACT26. The processor 51 executes the slip reading process in ACT26. The details of the slip reading process will be described later. When the slip reading process ends, the processor 51 returns to ACT21. That is, the processor 51 sets the screen of the touch panel 55 to the top screen SCa.

[0079] When the product order button BTb is pressed in the standby state of ACT22 to ACT25, the processor 51 proceeds to ACT27. The processor 51 executes a product order process in ACT27. The product order process will be described in detail later. When the product order process ends, the processor 51 returns to ACT21. That is, the processor 51 sets the screen of the touch panel 55 to the top screen SCa.

[0080] When the checkout button BTc is pressed during the standby state of ACT22 to ACT25, processor 51 proceeds to ACT28. Processor 51 executes the checkout process in ACT28. Details of the checkout process will be described later. When the checkout process is completed, processor 51 returns to ACT21. That is, processor 51 sets the screen of touch panel 55 to the top screen SCa.

[0081] When the end button BTd is input in the standby state of ACT22 to ACT25, the processor 51 proceeds to ACT29. The processor 51 erases the top screen SCa in ACT29. Thus, the processor 51 ends the information processing based on the store application 521.

[0082] <Invoice reading process> FIG. 10 is a flowchart showing the main steps of the slip reading process executed by the processor 51 of the mobile terminal 5 and the main information processing steps executed by the processor 31 of the base server 3 in conjunction with the process.

[0083] When the processor 51 of the mobile terminal 5 starts the slip reading process, it displays the screen of the touch panel 55 as the read screen SCb (see FIG. 15) in ACT31.

[0084] 15 is an example of the display of the read screen SCb. As shown in the figure, the read screen SCb displays a read area Ar for reading a machine-readable code (barcode or two-dimensional code) printed on a reception slip with the camera 56. The machine-readable code is read by pointing the lens of the camera 56 over the reception slip so that the machine-readable code falls within this read area Ar.

[0085] The processor 51 of the mobile terminal 5 that has displayed the reading screen SCb proceeds to ACT32. The processor 51 waits for the machine-readable code to be read in ACT32. When the machine-readable code is read by the camera 56, the processor 51 proceeds to ACT33. The processor 51 acquires a store code from the machine-readable code in ACT33. The processor 51 also acquires a slip number from the machine-readable code in ACT34. The processor 51 further acquires a member ID registered in the store app 521 in ACT35.

[0086] The processor 51 controls the wireless communication unit 53 to transmit a link request event Ei to the infrastructure server 3 in ACT36. This control causes the link request event Ei to be wirelessly transmitted from the mobile terminal 5. The link request event Ei is received by the mobile server 2 and transmitted to the infrastructure server 3 via the inter-server network 4. The link request event Ei includes the store code obtained in ACT33, the slip number obtained in ACT34, and the member ID obtained in ACT35.

[0087] The processor 31 of the infrastructure server 3 that has received the collaboration request event Ei searches the collaboration table 333 identified by the store code included in the collaboration request event Ei in ACT101. Then, the processor 31 checks whether the slip number included in the collaboration request event Ei is described in column Cb of the collaboration table 333 in ACT102. If the slip number is not described in column Cb of the collaboration table 333, the processor 31 proceeds to ACT107. The processor 31 transmits a collaboration failure response event Ej to the mobile terminal 5 that is the sender of the collaboration request event Ei in ACT107.

[0088] On the other hand, if the slip number is described in column Cb of association table 333, processor 31 proceeds to ACT103. In ACT103, processor 31 checks association flag F of the row in association table 333 in which the slip number is described. If association flag F is "1", the member ID has been associated with the slip number by processing the entry notification event Ec received from store server 11. Processor 31 proceeds to ACT106. In ACT106, processor 31 transmits an association completion response event Eb to mobile terminal 5, which is the sender of the association request event Ei.

[0089] On the other hand, if the linkage flag F is "0", the processor 31 proceeds to ACT104. In ACT104, the processor 31 writes the member ID included in the linkage request event Ei in column Cc of the row in which the slip number is written in the linkage table 333. The processor 31 also sets the linkage flag F in the same row to "1". Thereafter, the processor 31 proceeds to ACT106. In ACT106, the processor 31 transmits a linkage completion response event Ek to the mobile terminal 5 that is the sender of the linkage request event Ei. 3. An image indicating that the linking of the room number and the member ID has been completed is displayed in a part of the top screen SCa. The processor 51 also stores the store code and the slip number obtained from the machine-readable code on the reception slip as ACT39.

[0090] On the other hand, when an event Ej of a response indicating that linkage is not possible is received from the infrastructure server 3 via the wireless communication unit 53, the processor 51 proceeds to ACT 40. The processor 51 displays an image indicating that linkage between the room number and the member ID is not possible in ACT 40 in a part of the top screen SCa.

[0091] Thus, the user of the mobile terminal 5 can easily check from the image on the top screen SCa whether or not his / her member ID is linked to the room number of the karaoke booth in which he / she is staying.

[0092] <Product order processing> FIG. 11 is a flowchart showing the main steps of a product order process executed by the processor 51 of the mobile terminal 5 and the main information processing steps executed by the processor 31 of the base server 3 in conjunction with the process.

[0093] When the processor 51 of the mobile terminal 5 starts the product order process, it controls the wireless communication unit 53 to transmit a menu request event Em as ACT 51 to the infrastructure server 3. This control causes the menu request event Em to be wirelessly transmitted from the mobile terminal 5. The menu request event Em is received by the mobile server 2 and transmitted to the infrastructure server 3 via the inter-server network 4.

[0094] The processor 31 of the infrastructure server 3 that has received the menu request event Em creates menu data based on the data related to the food and drink menu items stored in the product file 331 as ACT111. The menu data is data for displaying a menu screen on the touch panel 55 of the mobile terminal 5. The menu screen displays a list of the names and prices of the food and drink menu items that can be ordered at the karaoke store. The processor 31 transmits the menu data to the mobile terminal 5 that is the sender of the menu request event Em as ACT112.

[0095] The processor 51 of the mobile terminal 5 that transmitted the menu request event Em waits for menu data in ACT 52. When the processor 51 receives the menu data via the wireless communication unit 53, the processor 51 proceeds to ACT 53. In ACT 53, the processor 51 displays a menu screen on the touch panel 55 based on the menu data.

[0096] After checking the menu screen, the user selects the food and drink menu items they wish to order and inputs the number of items to order. After selecting the food and drink menu items, the user presses the order button located on the menu screen.

[0097] The processor 51 of the mobile terminal 5 displaying the menu screen waits for the order button to be input as ACT54. When the order button is input, the processor 51 proceeds to ACT55. The processor 51 controls the wireless communication unit 53 to transmit an order event Ed to the infrastructure server 3 as ACT55. This control causes the order event Ed to be wirelessly transmitted from the mobile terminal 5. The order event Ed is received by the mobile server 2 and transmitted to the infrastructure server 3 via the inter-server network 4. The order event Ed includes order data, that is, the product code and the order quantity of the food and drink menu item selected from the menu screen. The order event Ed also includes the member ID registered in the store app 521 and the store code obtained from the machine-readable code on the reception slip.

[0098] The processor 31 of the infrastructure server 3 that has received the order event Ed acquires a store code from the order event Ed in ACT 113. The processor 31 also acquires a member ID from the order event Ed in ACT 114. Then, the processor 31 searches the association table 333 of the store identified by the store code in ACT 115 to confirm whether the member ID is associated with a room number.

[0099] If the member ID is not associated with the room number, the processor 31 proceeds to ACT 116. In ACT 116, the processor 31 transmits an order impossible response event En to the mobile terminal 5 that is the transmission source of the order event Ed.

[0100] On the other hand, if the member ID is linked to the room number, the processor 31 proceeds to ACT117. The processor 31 determines the karaoke store identified by the store code as the destination of the order event Ed in ACT117. The processor 31 transmits the order event Ed to the store server 11 of the karaoke store determined as the destination in ACT118. The processor 31 also transmits an order completion response event Eo to the mobile terminal 5 which is the source of the order event Ed in ACT119.

[0101] In this way, when the processor 31 of the infrastructure server 3 receives an order event Ed from the mobile terminal 5, if the member ID included in the order event Ed is not associated with a room number, it sends an order impossible response event En to the mobile terminal 5. On the other hand, if the member ID included in the order event Ed is associated with a room number, it sends an order completion response event Eo to the mobile terminal 5. Here, the processor 31 realizes the function as the order permission means 316 by the processing of ACT113 to ACT119.

[0102] Fig. 13 is a sequence diagram for explaining the general operation of the facility management system 100 including the mobile terminal 5. In Fig. 13, parts common to Fig. 2 are given the same reference numerals. As shown in Fig. 13, the store server 11 of the store system 1 that receives an order event Ed from the infrastructure server 3 transfers the order event Ed to the station 15 of the same store system 1. The station 15 executes order processing every time it receives an order event Ed. The station 15 adds order data to the order record 71 in which the room number included in the order event Ed is set.

[0103] In this way, the store system 1 including the store server 11 and the station 15 processes the order data input via the mobile terminal 5 in the same manner as the order data input via the reception terminal 12.

[0104] The processor 51 of the mobile terminal 5 that transmitted the order event Ed waits for an event from the infrastructure server 3 in ACT 56. When the processor 51 receives an order completion response event Eo from the infrastructure server 3 via the wireless communication unit 53, the processor 51 proceeds to ACT 57. The processor 51 displays an image on the touch panel 55 indicating that the order of the food and beverage menu item has been completed in ACT 57. In contrast, when the processor 51 receives an order unavailable response event En from the infrastructure server 3, the processor 51 proceeds to ACT 58. The processor 51 displays an image on the touch panel 55 indicating that the order of the food and beverage menu item was unavailable in ACT 58.

[0105] In this way, a user of a karaoke booth can order food and drink menu items using a mobile terminal 5 in which a member ID linked to the room number of the karaoke booth is registered, that is, a mobile terminal 5 linked to the karaoke booth. Note that even if a mobile terminal 5 is not linked to the karaoke booth, the user can still view menu images of food and drink menu items using that mobile terminal 5.

[0106] <Accounting> FIG. 12 is a flowchart showing the main steps of the transaction processing executed by the processor 51 of the mobile terminal 5 and the main information processing steps executed by the processor 31 of the base server 3 in conjunction with the transaction processing.

[0107] When the processor 51 of the mobile terminal 5 starts transaction processing, it controls the wireless communication unit 53 to send a transaction request event Ee as ACT61 to the infrastructure server 3. This control causes the transaction request event Ee to be wirelessly transmitted from the mobile terminal 5. The transaction request event Ee is received by the mobile server 2 and transmitted to the infrastructure server 3 via the inter-server network 4. The transaction request event Ee contains the member ID registered in the store app 521 and the store code obtained from the machine-readable code on the reception slip.

[0108] The processor 31 of the infrastructure server 3 that receives the transaction request event Ee acquires a store code from the transaction request event Ee as ACT 121. The processor 31 also acquires a member ID from the transaction request event Ee as ACT 122. The processor 31 then searches the association table 333 for the store identified by the store code as ACT 123 to confirm whether the member ID is associated with a room number.

[0109] If the member ID is not associated with the room number, the processor 31 proceeds to ACT 124. In ACT 124, the processor 31 transmits an accounting failure response event Ep to the mobile terminal 5 that is the source of the accounting request event Ee.

[0110] On the other hand, if the member ID is associated with the room number, the processor 31 proceeds to ACT125. The processor 31 sends a transaction permission response event Eq to the mobile terminal 5 that is the sender of the transaction request event Ee in ACT125. The processor 31 also determines the karaoke store identified by the store code as the destination of the order event Ed in ACT126. The processor 31 sends the transaction request event Ee to the store server 11 of the karaoke store determined as the destination in ACT126.

[0111] 13, upon receiving the transaction request event Ee, the store server 11 transmits an order call event Ef to the station 15. The order call event Ef includes the slip number obtained from the transaction request event Ee.

[0112] The station 15 that has received the order call event Ef acquires the order record 71 including the slip number acquired from the order call event Ef. The station 15 then returns the order data included in the order record 71 to the store server 11.

[0113] The store server 11 executes a totaling process. This process adds up the cost of the food and drink menu items calculated based on the order data obtained from the station 15 to the usage fee of the transaction record 61, which includes the slip number obtained from the accounting request event Ee. If the departure time at which check-out occurs is later than the scheduled departure time, the store server 11 adds an extension fee to the usage fee. The store server 11 then adds up the cost of the food and drink menu items to the usage fee to which the extension fee has been added.

[0114] After completing the total processing, the store server 11 transmits the fee data to the infrastructure server 3. The fee data is the sum of the karaoke box usage fee and the cost of the food and drink menu items, that is, data on the fee associated with the use of the karaoke box. The fee data also includes details of the fee, such as the karaoke box usage fee, the food and drink menu items' names, prices, and the number of items ordered.

[0115] Returning to the explanation of Figure 12. The processor 31 of the infrastructure server 3 that sent the transaction request event Ee waits for fee data to be sent from the store server 11 in ACT128. Upon receiving the fee data, the processor 31 proceeds to ACT129. In ACT129, the processor 31 sends the fee data to the mobile terminal 5 that sent the transaction request event Ee.

[0116] The processor 51 of the mobile terminal 5 that has received the fee data displays the fee associated with the use of the karaoke booth on the touch panel 55 in ACT 64. The processor 51 then waits for the mobile payment to be executed in ACT 65. When the user launches the payment application 522 and issues a command to execute the mobile payment, the processor 51 proceeds to ACT 66. The processor 51 executes the mobile payment process for the fee associated with the use of the karaoke booth in ACT 66. For example, if credit card payment is selected as the mobile payment, the cashless payment is executed using the credit card data registered in the mobile terminal 5. For example, if electronic money payment is selected as the mobile payment, the cashless payment is executed using the electronic money data registered in the mobile terminal 5.

[0117] The processor 51 waits for the mobile payment to be completed in ACT67. When the mobile payment is completed, the processor 51 proceeds to ACT68. The processor 51 controls the wireless communication unit 53 to transmit a payment completion event Eg to the infrastructure server 3 in ACT68. This control causes the payment completion event Eg to be wirelessly transmitted from the mobile terminal 5. The payment completion event Eg is received by the mobile server 2 and transmitted to the infrastructure server 3 via the inter-server network 4. The payment completion event Eg includes the member ID registered in the store app 521, and the store code and the slip number obtained from the machine-readable code on the reception slip.

[0118] The processor 31 of the infrastructure server 3 that transmitted the fee data to the mobile server 2 waits to receive a payment completion event Eg in ACT130. When the processor 31 receives the payment completion event Eg from the mobile server 2, the processor 31 proceeds to ACT131. The processor 31 acquires the store code from the payment completion event Eg in ACT131. The processor 31 then searches the association table 333 identified by the store code in ACT132. The processor 31 rewrites the association flag F described in column Cd of the association table 333 in which the store code and slip number included in the payment completion event Eg are described in columns Cb and Cc, respectively, from "1" to "0" in ACT133.

[0119] The processor 31 also determines, as a destination of the payment completion event Eg, the karaoke store identified by the store code acquired from the payment completion event Eg (ACT 134). The processor 31 transmits the payment completion event Eg to the store server 11 of the karaoke store determined as the destination (ACT 135).

[0120] As shown in FIG. 13, upon receiving the payment completion event Eg, the store server 11 updates the status of the transaction record 61 in which the slip number obtained from the payment completion event Eg is set from an in-use state to an unused state. The store server 11 also sends an exit notification event Eh to the station 15 and the infrastructure server 3. The exit notification event Eh includes the slip number obtained from the payment completion event Eg and the room number of the transaction record 61 in which the slip number is set. The exit notification event Eh also includes the store code. Upon receiving the exit notification event Eh, the station 15 updates the status of the order record 71 in which the room number and slip number obtained from the exit notification event Eh are set from an in-use state to an unused state.

[0121] On the other hand, the infrastructure server 3 that has received the exit notification event Eh executes the processes of ACT12 to ACT15 in FIG.

[0122] In this way, when the processor 31 of the infrastructure server 3 receives a billing request event Ee from the mobile terminal 5, if the member ID included in the billing request event Ee is not associated with the room number, it sends a billing impossibility response event Ep to the mobile terminal 5. In contrast, if the member ID included in the billing request event Ee is associated with the room number, it sends a billing completion response event Eq to the mobile terminal 5. Here, the processor 31 realizes the function as billing approval means 315 by processing ACT121 to ACT125.

[0123] Furthermore, having sent the transaction completion response event Eq to the mobile terminal 5, the processor 31 sends a transaction request event Ee to the store server 11 of the karaoke store identified by the store code included in the transaction request event Ee. Then, upon receiving fee data indicating the fee calculated by the store server 11 in response to this transaction request event Ee, the processor 31 sends the fee data to the mobile terminal 5. Here, the processor 31 realizes the function of provision means 312 by the processing of ACT126 to ACT129.

[0124] Moreover, the processor 31, which has transmitted the fee data to the mobile terminal 5, waits to receive a payment completion event Eg from the mobile terminal 5. Here, the processor 31 realizes the function of the receiving means 313 by the processing of ACT130.

[0125] Then, upon receiving the payment completion event Eg, the processor 31 executes the processing of ACT131 to ACT135. That is, the processor 31 rewrites the linkage flag F of the room number in which the slip number and member ID included in the payment completion event Eg are described from "1" to "0" in the linkage table 333. The processor 31 also transmits the payment completion event Eg to the store server 11 included in the payment completion event Eg. Here, the processor 31 realizes the function as the processing means 314 by the processing of ACT131 to ACT135.

[0126] [Effects of facility management systems] As described above in detail, the facility management system 100 of this embodiment enables the fee for using a karaoke booth to be paid by mobile terminal 5 owned by a user using the karaoke booth.

[0127] Furthermore, when a mobile payment is made with the mobile terminal 5, the status of the transaction record 61 and order record 71 is changed from in use to unused, just as when a payment is made with the accounting terminal 13. Therefore, the karaoke booth used by the user who made the mobile payment will not remain in use after the payment, and the order record including the order data ordered by that user will not remain in use. The unused status includes states such as awaiting cleaning, being cleaned, available for use, etc.

[0128] [Other embodiments] In the above embodiment, the processor 31 of the infrastructure server 3 has the functions of the linking means 311, the providing means 312, the receiving means 313, the processing means 314, the transaction approval means 315, and the order approval means 316. In another embodiment, these means may be provided in the processor of the store server 11. In other words, the store server 11 is one aspect of a facility management device. Such another embodiment is effective as a facility management device that manages one facility.

[0129] Also, for example, by providing the mobile server 2 with a data table equivalent to the linkage table 333, the processor of the mobile server 2 can have the functions of the transaction permission means 315 and the order permission means 316. In this case, the infrastructure server 3 and the mobile server 2 constitute a facility management device.

[0130] In the above embodiment, the facility is a karaoke booth. The facility is not limited to a karaoke booth. For example, the present embodiment can be applied to facilities such as darts bars and manga cafes, allowing mobile payment using the mobile terminal 5.

[0131] In the above embodiment, a member ID is exemplified as terminal information for identifying the mobile terminal 5 used by the user. The terminal information is not limited to the member ID. For example, if the mobile terminal 5 is a smartphone, a telephone number may be used as the terminal information. Furthermore, the facility information is not limited to the room number. For example, any information that can identify a facility, such as a room name or seat number, can be facility information.

[0132] Although several other embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope of the invention and the scope of the invention and its equivalents described in the claims. [Explanation of symbols]

[0133] 1...store system, 2...mobile server, 3...basic server, 4...inter-server network, 5...mobile terminal, 6...transaction file, 7...order file, 11...store server, 12...reception terminal, 13...accounting terminal, 14...kitchen terminal, 15...station, 31...processor, 32...main memory, 33...auxiliary storage device, 34...clock, 35...communication interface, 311...linking means, 312...providing means, 313...receiving means, 314...processing means, 315...accounting acceptance means, 316...order acceptance means, 331...product file, 332...member file, 333...linking table, 521...store app, 522...payment app.

Claims

1. A linking means for linking facility information that identifies a facility used by a user with terminal information that identifies a mobile terminal used by the user; a providing means for providing a fee for use of the facility to the mobile terminal identified by terminal information associated with facility information of the facility; a receiving means for receiving a notification that the fee has been paid at the mobile terminal; a processing means for executing a process related to the end of use of the facility identified by facility information linked to terminal information of the mobile terminal on which the payment was made; A facility management device comprising:

2. 2. The facility management device according to claim 1, wherein the linking means links terminal information inputted at a reception terminal that accepts the start of use of the facility with facility information of the facility that accepted the start of use.

3. The facility management device according to claim 1, wherein the linking means links terminal information of a mobile terminal that reads a slip issued by a reception terminal that accepts the start of use of the facility with facility information of the facility that accepted the start of use, based on information from the mobile terminal.

4. an accounting permission means for, in response to a billing request from the mobile terminal, checking whether terminal information of the mobile terminal is linked to the facility information, and allowing the billing only if linked; The facility management device according to claim 1 , further comprising:

5. an order acceptance means for, in response to a product order request from the mobile terminal, confirming whether terminal information of the mobile terminal is linked to the facility information, and accepting the product order only if the terminal information is linked; The facility management device according to claim 1 , further comprising:

6. The facility management device computer, A linking means for linking facility information that identifies a facility used by a user with terminal information that identifies a mobile terminal used by the user; a provision means for providing a fee for use of the facility to the mobile terminal identified by terminal information associated with facility information of the facility; a receiving means for receiving a notification that the fee has been paid at the mobile terminal; and A processing means for executing a process related to the end of use of the facility identified by facility information linked to terminal information of the mobile terminal on which the payment was made; A program to function as a

Images