Programs, information processing devices, methods, and systems

Abstract

The goal is to streamline the reservation management process for each plot and shorten the lead time from reservation application to reservation confirmation. [Solution] A program to be executed on a computer equipped with a processor, the program to cause the processor to execute the following steps: receiving a reservation application from a user, which includes specific information identifying a business operator that wishes to use a section within a target facility, the target section that the business operator wishes to use, the date of use, and the details of use; storing the status of the received reservation application as a provisional reservation; displaying the contents of the reservation application on a first terminal operated by a person in charge of the target facility and receiving a choice of approval or rejection; if an approval choice is received, generating information requesting online payment and sending it to a second terminal operated by the user; and updating the status of the reservation application to confirmed when completion information indicating that payment has been completed is received from the second terminal or an external device.

Description

Technical Field

[0001] The present disclosure relates to programs, information processing apparatuses, methods, and systems.

Background Art

[0002] Conventionally, the process of reserving sections such as event spaces in commercial facilities and event venues has largely relied on manual means such as telephone, fax, or email. Communication between a business operator wishing to open a store and the person in charge of the facility generally involves individual exchanges being intermittently carried out in a series of processes such as checking the availability of sections, negotiating usage conditions, submitting a reservation application, approval, and settlement. Under such circumstances, information asymmetry and transmission delays are likely to occur, which has been a major factor significantly impairing the efficiency of the entire reservation process.

[0003] To solve such problems, various technologies for managing the reservation process of facilities have been proposed. For example, Patent Document 1 discloses a system that mediates between an event organizer and a food truck operator. In this system, after the food truck operator applies to participate in an event, the event organizer approves this participation application, and then the food truck operator settles the usage fee to confirm participation.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The technology disclosed in Patent Document 1 primarily focuses on managing participation slots for events with predetermined dates, times, and locations. However, the technology disclosed in Patent Document 1 did not adequately consider the management of reservations for physical spaces, such as permanently established sections within a facility, under constantly changing circumstances. Therefore, it had limitations in meeting the needs of more dynamic and complex section reservation management, where usage fees or conditions may fluctuate depending on the event, and where availability needs to be searched across multiple facilities and the facility brands that aggregate them.

[0006] In other words, the technology disclosed in Patent Document 1 is limited to matching within the broad framework of an event. Therefore, there was room for improvement in managing the availability of individual spaces, which fluctuates daily, and the different usage conditions for each event category in real time, as well as seamlessly automating and streamlining the entire reservation process from application to approval, payment, and reservation confirmation. For businesses wishing to set up a booth, it was difficult to quickly find and secure a space that matched the content of their event from among the diverse spaces spread across multiple facilities. Furthermore, for facility staff, there was a challenge in that human errors such as the risk of double booking and missed approvals were likely to occur when manually checking and approving numerous applications.

[0007] This disclosure is made in light of the challenges of the prior art, and its purpose is to provide a new system that automates the entire process of reserving spaces for events and other activities at multiple facilities, from application to approval, payment, and reservation confirmation, thereby enabling fast and reliable space reservation management for both users and facilities. Specifically, this disclosure aims to improve the efficiency of space reservation management operations and shorten the lead time from reservation application to reservation confirmation. [Means for solving the problem]

[0008] To solve the aforementioned problems, a program according to one aspect of the present disclosure is a program to be executed on a computer equipped with a processor, which causes the processor to execute the following steps: receiving a reservation application from a user, which includes specific information identifying a business operator that wishes to use a section provided in a target facility, the target section that the business operator wishes to use, the date and time for using the target section, and the details of how the target section will be used; storing the status of the received reservation application as a provisional reservation; displaying the contents of the reservation application on a first terminal operated by a person in charge of the target facility and receiving a choice of approval or rejection from the person in charge; if an approval choice is received, generating request information requesting online payment and transmitting the request information to a second terminal operated by the user; and, if completion information indicating that payment has been completed is received from the second terminal or an external device that performs payment processing, updating the status of the reservation application from provisional to confirmed. [Effects of the Invention]

[0009] According to this disclosure, it is possible to streamline the reservation management process for each plot of land and shorten the lead time from reservation application to reservation confirmation. [Brief explanation of the drawing]

[0010] [Figure 1] This is a block diagram showing an example of the overall configuration of a system according to the embodiment of this disclosure. [Figure 2] Figure 1 is a block diagram showing an example of the hardware configuration of a user terminal and a facility staff terminal. [Figure 3] Figure 1 is a block diagram showing the functional units realized by the control units of the user terminal and the facility staff terminal. [Figure 4] This block diagram shows an example of the server hardware configuration shown in Figure 1. [Figure 5] This is a block diagram showing the functional units realized by the control unit of the server shown in Figure 1. [Figure 6] This figure shows an example of the data structure of a partition master table. [Figure 7]This figure shows an example of the data structure of a category master table. [Figure 8] This figure shows an example of the data structure of the plot usage permission table. [Figure 9] This figure shows an example of the data structure of a reservation management table. [Figure 10] This figure shows an example of the data structure of a user management table. [Figure 11] Figure 1 is a flowchart showing the basic operation flow of the server. [Figure 12] This is a schematic diagram showing an example screen of a facility staff terminal according to an embodiment of the present disclosure. [Figure 13] This is a schematic diagram showing an example of a user terminal screen related to a modified version of the present disclosure. [Modes for carrying out the invention]

[0011] The embodiments of this disclosure will be described below with reference to the drawings. In all the drawings illustrating the embodiments, common components are denoted by the same reference numerals, and repeated explanations are omitted. The following embodiments are not intended to unduly limit the content of this disclosure as described in the claims. Not all components shown in the embodiments are necessarily essential components of this disclosure. Also, each drawing is a schematic diagram and is not necessarily a strict illustration.

[0012] Furthermore, in the following description, "processor" refers to one or more processors. A processor may be expressed, for example, as processing circuitry. At least one processor is typically a microprocessor such as a CPU (Central Processing Unit), but may be other types of processors such as a GPU (Graphics Processing Unit). At least one processor may be single-core or multi-core. Also, at least one processor may be a general-purpose processor or a purpose-specific processor.

[0013] Further, at least one processor may be a processor in a broad sense, such as a hardware circuit (e.g., FPGA (Field-Programmable Gate Array), ASIC (Application Specific Integrated Circuit)) that performs part or all of the processing.

[0014] In the following description, expressions such as "xxx table" may be used to describe information from which an output is obtained for an input. However, this information may be data of any structure or a learning model such as a neural network that generates an output for an input. Therefore, "xxx table" can be referred to as "xxx information".

[0015] In the following description, the configuration of each table is an example. One table may be divided into two or more tables, or all or part of two or more tables may be one table.

[0016] The program may be pre-installed in the information processing apparatus shown below. For example, it may be on a recording medium (e.g., non-temporary) readable by the information processing apparatus, and this program may be installed in the information processing apparatus. Also, the program may be transmitted from a program distribution server to the information processing apparatus and installed. In the following description, two or more programs may be realized as one program, or one program may be realized as two or more programs.

[0017] In the following description, identification information for various objects is used. However, the identification information may be any information indicating a predetermined object, and the specific data is not limited to the embodiments. The identification information may be an identification number or an identifier including letters and symbols.

[0018] 〔Overview〕 The system according to this embodiment is provided as a cloud service to streamline and automate the process of reserving spaces for events such as pop-up stores and fairs in multiple commercial facilities. The system according to this embodiment enables businesses wishing to set up a booth at a fair to search for available spaces across multiple facilities and complete the entire process from reservation application to payment online.

[0019] Specifically, a server constituting the system according to this embodiment receives conditions such as the category of area usage and the desired dates for area usage from a user terminal, which is also a component of the system, and presents information on available areas in real time based on these conditions. The user selects a desired area from the presented information and submits a reservation request. The reservation request is notified via the server to a facility staff terminal, which is a component of the system according to this embodiment. The facility staff approves or rejects the reservation request. If approved, a payment request is sent to the user terminal, and the reservation is confirmed once online payment is completed. This series of processes significantly streamlines the reservation management process, which was previously manual and cumbersome, and enables quick and reliable area reservations.

[0020] [Overall System Configuration] Figure 1 is a block diagram showing an example of the overall configuration of System 1. System 1 provides a platform service for matching facilities that wish to rent out space with businesses that wish to use that space (e.g., pop-up store owners and tenant companies conducting various promotional activities) online.

[0021] The facilities that are the target of the services provided by System 1 (hereinafter referred to as "target facilities") are, for example, commercial facilities. Commercial facilities are facilities used for the purpose of selling various goods or providing various services, and include, for example, shopping malls, department stores, retail stores, clinic malls, amusement facilities, etc.

[0022] However, the facilities covered are not limited to commercial facilities, but include any facility where a section can be rented out for temporary use. Specifically, these include commercial facilities, transportation hubs (e.g., train stations, airport terminal buildings, highway service areas or parking areas, roadside rest areas), office-related facilities (e.g., entrance halls or common areas in office buildings, event areas in co-working spaces), public / cultural facilities (e.g., halls in government buildings such as city or ward offices, parks, library or art museum entrances), accommodation / public gathering facilities (e.g., hotel lobbies or banquet halls, event venues, exhibition halls, or halls, stadium or arena concourses), and educational institutions (e.g., plazas or student halls on university campuses).

[0023] The areas covered by the services provided by System 1 are specific spaces rented out within the target facility and within the area under the jurisdiction of said target facility (e.g., "A Department Store, 1st Floor, Event Space in Front of the Main Entrance"). Furthermore, "use of a section" as used herein refers to all commercial activities, promotional activities, or similar activities conducted by a business operator using a specific space within the target facility or within the area under the jurisdiction of said target facility. Hereinafter, a specific space (section) within the target facility that a business operator wishes to use will be referred to as the "target section."

[0024] There are no specific restrictions on how businesses may use the designated spaces. Examples of uses include: product sales / marketing activities (e.g., pop-up stores, event sales, inventory sales), promotion / advertising activities (e.g., product / service exhibitions, sample distribution, PR events), food and beverage provision (e.g., food trucks, test marketing), art galleries, and recruitment activities (e.g., company information sessions, interviews).

[0025] System 1 includes a user terminal 10, a server 20, and a facility staff terminal 30. The user terminal 10, server 20, and facility staff terminal 30 are connected to each other via a network 80 such as the Internet or a LAN (Local Area Network), using protocols such as TCP / IP. In this embodiment, the server 20 also cooperates with an external payment system 40 via an API (Application Programming Interface) to realize online payment.

[0026] In Figure 1, an example is shown in which System 1 includes one user terminal 10 and one facility staff terminal 30. However, for example, System 1 may include two or more of at least one of the user terminals 10 and facility staff terminals 30. Also, while Server 20 is assumed to consist of one unit, in other examples, it may be configured as a collection of multiple devices. The method of distributing the multiple functions required to realize Server 20 to multiple devices can be appropriately determined according to the processing capacity of each device and / or the specifications required for Server 20.

[0027] User terminal 10 is an example of a "second terminal" relating to one aspect of this disclosure, and is a client terminal (computer, information processing device) used by a user. In this specification, "user" refers to a business operator who wishes to use a section provided in the target facility, or a representative of an agency that handles reservation procedures on behalf of the business operator. Furthermore, "business operator" as used herein broadly refers to any entity that conducts commercial or promotional activities, regardless of whether it has legal personality, and includes, for example, corporations, sole proprietors, and voluntary associations. The user accesses server 20 via a web browser installed on an information terminal such as a personal computer (PC), tablet, or smartphone, and uses various functions provided by system 1. Specifically, user terminal 10 can perform cross-facility section searches, check availability, make reservations, make payments, and download reservation slips.

[0028] Server 20 is the core information processing device of System 1 and is typically composed of one or more computers. Server 20 runs application programs 220 (see Figure 4) that provide key functions such as user management, facility management, area management, reservation management, and payment integration. Server 20 has a database 400 (see Figure 4), such as a relational database that holds various data tables described later, and processes, provides, and stores data in response to HTTP requests from user terminals 10 and facility staff terminals 30. Server 20 may be configured as a single physical server or may be implemented on a cloud computing environment where functions are distributed across multiple servers.

[0029] The facility staff terminal 30 is an example of the "first terminal" relating to one aspect of this disclosure, and is a client terminal (computer, information processing device) used by the facility staff (hereinafter referred to as the facility staff). The facility staff manages, for example, all sections located within the target facility, including the target facility itself. The facility staff accesses the server 20 via a web browser and utilizes management functions such as confirming and approving or denying reservation applications, setting available usage categories and fees for each section, and setting usage restriction rules for specific businesses. Details of usage categories and usage restriction rules will be described later.

[0030] The payment system 40 is an example of an "external device" according to one aspect of this disclosure, and is a computer system operated by an external service provider that provides online payment functions such as credit card payments or bank transfers. The server 20 cooperates with the payment system 40 via a RESTful API or the like to safely and reliably process payment requests. However, cooperation between the server 20 and the payment system 40 is not mandatory, and for example, the server 20 may be configured to perform payment processing itself.

[0031] [Configuration of user terminals and facility staff terminals] Figure 2 is a block diagram showing an example of the hardware configuration of the user terminal 10 and the facility staff terminal 30 shown in Figure 1. Since the configurations and functions of the user terminal 10 and the facility staff terminal 30 are common to both, the configuration of the user terminal 10 will be described primarily. The configuration of the facility staff terminal 30 will be described in a simplified manner.

[0032] <User terminal configuration> As shown in Figure 2, the user terminal 10 comprises a control unit 101, a storage unit 102, a communication unit 103, an input unit 104, an output unit 105, a camera 106, a position sensor 107, and an acceleration sensor 108. Each block included in the user terminal 10 is electrically connected, for example, by a bus.

[0033] The control unit 101 executes various processes by running various programs stored in the memory unit 102. The control unit 101 is, for example, a processor such as a CPU. A processor is hardware for executing instruction sets written in a program. A processor consists of an arithmetic unit, registers, peripheral circuits, etc.

[0034] The storage unit 102 includes a main memory and an auxiliary memory. The storage unit 102 stores various programs and various information. For example, the storage unit 102 stores an application program 120. The application program 120 includes, for example, a programming language that runs on a web browser application (not shown) stored in the storage unit 102.

[0035] The communication unit 103 performs modulation and demodulation processing for the user terminal 10 to communicate with an external device (e.g., server 20). The communication unit 103 performs transmission processing on the signal generated by the control unit 101 and transmits it to the external device. The communication unit 103 performs reception processing on the signal received from the external device and outputs it to the control unit 101.

[0036] The input unit 104 receives instructions or information input from the user. The input unit 104 may be implemented by, for example, a touch-sensitive device that inputs instructions, etc., by touching an operating surface. If the user terminal 10 is a PC, the input unit 104 may be implemented by a reader, keyboard, mouse, etc. The input unit 104 converts the instructions, etc., input by the user into electrical signals and outputs them to the control unit 101. The input unit 104 may also include, for example, a receiving port that receives electrical signals input from an external input device. The input unit 104 may also include a microphone that receives audio input.

[0037] The output unit 105 presents information to the user. The output unit 105 is implemented, for example, by a display. The display displays various information according to the control of the control unit 101. The display is implemented, for example, by an LCD (Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. The output unit 105 may also include an output port that outputs electrical signals to an external output device. The output unit 105 may also include a speaker that outputs sound. In other words, the presentation includes display on the display unit and output to a speaker or other output device.

[0038] Camera 106 is an imaging device that captures images using visible light. In other words, camera 106 is a device that receives visible light using a photodetector and outputs image data as a capture signal.

[0039] The location information sensor 107 is a sensor that detects the position of the user terminal 10, and is generally a GNSS device, such as a GPS module. A GPS module is a receiving device used in a satellite positioning system. In a satellite positioning system, signals are received from at least three or four satellites, and based on the received signals, the current position of the user terminal 10, which is equipped with a GPS module, is detected as coordinate values. The location information sensor 107 may also detect the current position of the user terminal 10 from the position of a wireless base station to which the user terminal 10 is connected via the communication unit 103.

[0040] The acceleration sensor 108 is a sensor that detects the acceleration applied to the user terminal 10. Preferably, the acceleration sensor 108 has the function of detecting the tilt around each axis (X axis, Y axis, Z axis) of the three-dimensional coordinate system with the position of the user terminal 10 as the origin. An acceleration sensor 108 having such a function can detect the orientation of the user terminal 10, that is, its direction with respect to the X, Y, and Z axes, by detecting the gravitational acceleration of the Earth's gravity.

[0041] Figure 3 is a block diagram showing the functional units realized by the control unit 101 and the control unit 301, respectively. As shown in Figure 3, the control unit 101 includes an operation reception unit 131, a transmission / reception unit 132, and a presentation control unit 133 as functional units. Specifically, the control unit 101 realizes each functional unit by reading the application program 120 stored in the storage unit 102 and executing the instructions contained in the application program 120.

[0042] The operation reception unit 131 processes instructions or information input from the input unit 104. The transmission / reception unit 132 processes data for the user terminal 10 to send and receive data with an external device according to a communication protocol. Specifically, the transmission / reception unit 132 transmits instructions or information input from the user to the server 20. The transmission / reception unit 132 receives information transmitted from the server 20. The presentation control unit 133 controls the output unit 105 to present various information to the user.

[0043] <Configuration of facility staff terminals> As shown in Figure 2, the facility staff terminal 30 includes a control unit 301, a storage unit 302, a communication unit 303, an input unit 304, an output unit 305, a camera 306, a position sensor 307, and an acceleration sensor 308.

[0044] The storage unit 302 stores, for example, an application program 320. The application program 320 includes, for example, a programming language that runs on a web browser application (not shown) stored in the storage unit 302. The input unit 304 receives instructions or information input from the facility staff. The output unit 305 presents information to the facility staff. The location information sensor 307 is a sensor that detects the location of the facility staff terminal 30. The acceleration sensor 308 is a sensor that detects the acceleration being applied to the facility staff terminal 30.

[0045] As shown in Figure 3, the control unit 301 comprises, as functional units, an operation reception unit 331, a transmission / reception unit 332, and a presentation control unit 333. Specifically, the control unit 301 reads the application program 320 stored in the storage unit 302 and implements each functional unit by executing the instructions contained in the application program 320.

[0046] [Server Configuration] Figure 4 is a block diagram showing an example of the hardware configuration of the server 20 shown in Figure 1. As shown in Figure 4, the server 20 comprises a control unit 201, a storage unit 202, a communication unit 203, and an input / output IF 204. The control unit 201 performs various processes by executing various programs stored in the storage unit 202. The control unit 201 is, for example, a processor such as a CPU.

[0047] The storage unit 202 includes a main memory and an auxiliary memory. The storage unit 202 stores various programs and various information. In this embodiment, the storage unit 202 stores, for example, an application program 220, a partition master table 401, a category master table 402, a partition usage permission table 403, a reservation management table 404, and a user management table 405. In other words, the storage unit 202 stores a database 400 constructed from each of these tables.

[0048] Application program 220 is application software for executing and managing services provided by system 1. Application program 220 includes, for example, a programming language such as JavaScript® that runs on a web browser application stored on user terminal 10.

[0049] The Section Master Table 401 is a table that stores information about sections of multiple facilities, including the target facility. The Category Master Table 402 is a table that stores information about usage categories. Usage categories classify the content of section usage, such as "apparel sales," "general merchandise sales," "food (no cooking)," or "promotional events." The Section Usage Permit Table 403 is a table that stores information about the association between sections and usage categories. The Reservation Management Table 404 is a table that stores information about section reservation applications. The User Management Table 405 is a table that stores information about users. Details of each of these tables will be described later.

[0050] The communication unit 203 performs processing such as modulation and demodulation for the server 20 to communicate with an external device (e.g., a user terminal 10). The input / output IF 204 functions as an interface for an input device (not shown) to receive input operations from the administrator of the server 20, and an output device (not shown) to output information to the administrator.

[0051] Figure 5 is a block diagram showing the functional units implemented by the control unit 201. The control unit 201 comprises a communication control unit 211, an information management unit 212, a reservation processing unit 213, and an information presentation unit 214 as functional units. Specifically, the control unit 201 implements each functional unit by reading a program (including an application program 220) stored in the storage unit 202 and executing the instructions contained in the program.

[0052] The communication control unit 211 controls data communication between the user terminal 10 and the facility staff terminal 30. Specifically, it receives requests from the web browser of each terminal using protocols such as HTTPS and sends the processing results as responses. The information management unit 212 centrally manages various information handled by System 1 in the database 400. As mentioned above, the database 400 includes the partition master table 401, the category master table 402, the partition usage permission table 403, the reservation management table 404, and the user management table 405.

[0053] The reservation processing unit 213 executes a series of business processes related to the reservation of a space. Specifically, it executes the following processes:

[0054] Specifically, the reservation processing unit 213 searches the database 400 in the storage unit 202 based on the search conditions (such as usage category and usage schedule) received from the user terminal 10, and generates a list of available partitions.

[0055] The reservation processing unit 213 also accepts reservation requests from users. A reservation request includes at least specific information that identifies the business operator, the target area, the usage schedule, and the details of the usage. The specific information is information that uniquely identifies the business operator, such as the business operator's name, the name of the person in charge, and contact information (email address and telephone number). The target area is identified by the area ID, etc. The usage schedule includes the start date and time and the end date and time of use of the target area. The details of the usage include the specific details of the event, etc., to be held in the target area (e.g., selling specialty products from □ prefecture from ○ / ○ / ○ to ○ / △ / △), and the usage category. The reservation processing unit 213 registers the details of the received reservation request in the reservation management table.

[0056] Furthermore, the reservation processing unit 213 accepts the operation of approving or denying reservation requests by facility staff. The reservation processing unit 213 may also have a function that allows the system to automatically determine whether to approve or deny based on pre-set automatic approval conditions and usage restriction rules. Details of the automatic approval conditions will be described later.

[0057] Furthermore, when a reservation is approved, the reservation processing unit 213 generates request information to request online payment in cooperation with the external payment system 40. This request information includes the payment amount, payment due date, and the URL of the payment page provided by the payment system 40. This request information is then sent to the user terminal 10. Once the payment is complete, the reservation processing unit 213 receives completion information from the payment system 40 indicating that the payment has been completed. Alternatively, the reservation processing unit 213 may have payment functions such as processing credit card information without coordinating with the payment system 40. In this case, the reservation processing unit 213 receives completion information from the user terminal 10.

[0058] Furthermore, the reservation processing unit 213 manages the status of the reservation request throughout its entire lifecycle. The status is information indicating the current state of the reservation request, such as "tentatively reserved," "awaiting approval," "approved (awaiting payment)," "confirmed," "denied," or "cancelled."

[0059] When an application is received, the status is "tentatively reserved," and it is only updated to "confirmed" when the final payment is completed. Therefore, since the reservation is not yet "confirmed" at the "tentatively reserved" stage, it is systemically possible for other users to submit reservation applications for the same plot and date. However, since the facility staff are presented with the reservation applications in the order they were received, the user who submitted the reservation application can systematically secure the right to negotiate on a first-come, first-served basis based on the date and time of application submission, before any manual verification by the facility staff takes place.

[0060] After a "provisional reservation" is made, the status is updated to "awaiting approval" once the facility manager has been notified and the status is awaiting their confirmation and decision. The two are conceptually different in that "provisional reservation" is a systemic indication that the application has been received, while "awaiting approval" refers to a state where the application is managed as an active task requiring human judgment by the facility manager. After approval by the facility manager, the status becomes "approved (awaiting payment)".

[0061] The information presentation unit 214 generates HTML, CSS, and JavaScript data to present the results of various processes and various information obtained from the database 400 in the storage unit 202 to each client terminal. The information presentation unit 214 also transmits the generated data via the communication unit 203.

[0062] <Data structure> Figures 6 to 10 show examples of the data structure of tables stored in the memory unit 202. Note that Figures 6 to 10 are merely examples and do not exclude data not shown. Furthermore, even data listed in the same table may be stored in separate memory areas within the memory unit 202.

[0063] The tables shown in Figures 6 to 10 refer to relational databases, which are data sets in a tabular format, structurally defined by rows and columns, and are used to manage and associate these tables with each other. In databases, tables are called tables, the columns of a table are called columns, and the rows of a table are called records. In relational databases, relationships can be established and linked between tables.

[0064] Typically, each table has a primary key column to uniquely identify records, but setting a primary key column is not mandatory. The control unit 201 can instruct the processor to add, delete, or update records in specific tables stored in the storage unit 202 according to various programs.

[0065] Figure 6 shows an example of the data structure of the partition master table 401. The partition master table 401 manages the physical information of each partition located in each of the multiple facilities managed by the server 20. The partition master table 401 includes columns such as partition ID, partition name, facility ID, facility brand ID, location, area, equipment information, and registration date and time.

[0066] The "Section ID" column is the primary key for uniquely identifying each section, storing identification information such as "SP0001". The "Section Name" column stores the specific name of each section, such as "Shibuya Square Main Entrance Event Space". The "Facility ID" column stores identification information for uniquely identifying the facility to which each section belongs (e.g., "F053"). The "Facility Brand ID" column stores identification information for identifying the facility brand to which each facility belongs (e.g., "B004"). This ensures that each section (Section ID) is clearly associated and stored in database 400 with which facility (Facility ID) it belongs, and further, which facility brand (Facility Brand ID) that facility belongs. Details about facility brands will be described later. The "Location" column stores address information indicating the location of each facility, such as "Shibuya-ku, Tokyo...". The "Area" column stores the area value of each section, such as "25.5" (square meters). The "Equipment Information" column stores information about ancillary facilities, such as "Power outlets: 2, Wi-Fi: Available". The "Registration Date and Time" column stores the date and time each record was created (e.g., "2025-10-01 10:00:00").

[0067] Figure 7 shows an example of the data structure of category master table 402. Category master table 402 includes columns such as category ID, category name, parent category ID, and display order.

[0068] The "Category ID" column is the primary key for uniquely identifying each usage category, storing identification information such as "C01". The "Category Name" column stores the specific name of each usage category, such as "Apparel Sales". The "Parent Category ID" column stores identification information (e.g., "C00") to uniquely identify the higher-level category when managing usage categories in a hierarchical structure. The "Display Order" column stores a numerical value (e.g., "1") to control the order in which the list of usage categories is displayed on the screen.

[0069] Figure 8 shows an example of the data structure of the plot usage permission table 403. The plot usage permission table 403 manages which usage categories are permitted for which plots, and the corresponding usage fees. The plot usage permission table 403 includes columns such as permission ID, plot ID, category ID, usage fee, fee type, and remarks.

[0070] The "Permission ID" column is the primary key that uniquely identifies each record and stores the identification information necessary to uniquely identify each record. The "Area ID" (e.g., "SP0001") and "Category ID" (e.g., "C01") columns function as foreign keys to the Area Master Table 401 and Category Master Table 402, respectively, linking the two. The "Usage Fee Unit Price" column stores the usage fee unit price (e.g., "50000") when using a specific area for a specific usage category. The "Unit Price Type" column stores the unit of each usage fee unit price (e.g., "Daily Rate" or "Hourly Rate"). The "Remarks" column stores supplementary information such as "20% surcharge on Saturdays, Sundays, and public holidays."

[0071] Figure 9 shows an example of the data structure of the reservation management table 404. The reservation management table 404 manages information for each reservation application in chronological order. The reservation management table 404 includes columns such as reservation ID, user ID, section ID, application date and time, start date and time of use, end date and time of use, status, and payment status.

[0072] The "Reservation ID" column is the primary key that uniquely identifies each reservation application, storing identification information to uniquely identify each reservation application, such as "R0000123". The "User ID" (e.g., "U789") and "Parking Lot ID" (e.g., "SP0001") columns function as foreign keys to the user management table 405 and the parking lot master table 401, respectively, linking the two. The "Application Date and Time" column stores the date and time each reservation application was made. The "Usage Start Date and Time" and "Usage End Date and Time" columns store the usage period of the target parking lot desired by the user. The "Status" column stores a code indicating the current status of each reservation application (e.g., "1": tentatively reserved, "2": awaiting approval, "3": confirmed, "4": rejected). The "Payment Status" column stores information indicating the payment status (e.g., "Pending", "Completed", or "Expired"). The reservation management table 404 may also store the details of the usage (or usage category) of the target area related to each reservation application.

[0073] Figure 10 shows an example of the data structure of user management table 405. User management table 405 manages basic user information, attribute information, etc. User management table 405 includes columns such as user ID, company name, contact person name, email address, phone number, availability flag, and registration date and time.

[0074] The "User ID" column is the primary key that uniquely identifies each user, storing identification information to uniquely identify each user, such as "U789". The "Business Name" column stores the name of the business if the user is a business. The "Contact Person Name" column stores the name of the contact person for the business or agency. The "Email Address" column stores the email address of the contact person for the business or agency. The "Telephone Number" column stores the main telephone number of the business or agency, or the direct telephone number of the contact person for the business or agency. The information stored in each column from "Business Name" to "Telephone Number" functions as identifying information to identify the business, used when making a reservation request. The "Availability Flag" column stores a flag indicating whether each user is permitted to use the system (1: permitted) or denied (0: denied). The "Registration Date and Time" column stores the date and time each user was first registered with server 20. Furthermore, the user management table 405 may also store each user's past usage history (not limited to the target facility and target area).

[0075] [Example of operation] The following describes an example of server 20 operation, referring to the flowchart in Figure 11. Figure 11 is a flowchart showing the basic operation flow of server 20.

[0076] First, in step S501 (step for accepting reservation applications), the user enters data for the reservation application, including the desired area to use, usage dates, usage details, and specific information identifying the service provider, via an input form displayed on the web browser of the user terminal 10. The operation reception unit 131 receives this data input, and the transmission / reception unit 132 transmits the received data to the server 20 via the communication unit 103. This transmission is typically performed as a POST request (reservation application request) using the HTTPS protocol. The communication control unit 211 receives and accepts the reservation application request sent from the user terminal 10 via the communication unit 203.

[0077] Next, in step S502 (the memory step), the reservation processing unit 213 verifies the validity of the application details of the received reservation request. Specifically, for example, the reservation processing unit 213 performs basic checks such as whether all required fields are filled in and whether the start date and time of the usage schedule is before the end date and time. In addition, to prepare for the case where multiple users submit reservation requests for the same section and the same date almost simultaneously, the reservation processing unit 213 records the time the application was received in milliseconds and performs exclusive control by managing transactions during the database writing process. If there are no deficiencies as a result of the verification, the reservation processing unit 213 generates a reservation ID (e.g., a unique string such as a UUID) to uniquely identify this reservation request. Then, the reservation processing unit 213 writes the contents of the received reservation request (user ID, section ID, and usage schedule, etc.) and the generated reservation ID, along with the current timestamp (application date and time), as a new record in the reservation management table 404. In this case, the "Status" column in the reservation management table 404 will be set to a value that indicates a tentative reservation (e.g., code value "1").

[0078] Next, in step S503 (the step in which the selection of approval or rejection is accepted), the reservation processing unit 213 requests approval from the facility manager in charge of the applied-for area. Specifically, the reservation processing unit 213 refers to the area master table 401 based on the area ID (identification information) stored in the reservation management table 404 to identify the facility ID (identification information) of the facility to which the area belongs. Subsequently, the reservation processing unit 213 uses the identified facility ID to obtain the contact information of the facility manager or the manager ID (identification information) of the manager from a facility manager management table (not shown). Then, based on the various information obtained, the reservation processing unit 213 displays a notification such as "There is a new reservation application" on the display of the facility manager terminal 30. Alternatively, based on the various information obtained, the reservation processing unit 213 sends a notification email to the registered email address containing an overview of the application and a URL to the detailed confirmation page. As an alternative notification method, the reservation processing unit 213 may be configured to integrate with the API of an external business chat tool (e.g., Slack® or Microsoft Teams®) and send notification messages to a specific channel to which the facility manager belongs.

[0079] Next, in step S504 (the step in which the selection of approval or rejection is accepted), the facility staff member who received the notification operates the facility staff member terminal 30 to access the management screen 1200 as shown in Figure 12. The facility staff member then selects the relevant reservation application from the reservation application list 1201 displayed on the management screen 1200 and checks the details. The management screen 1200 displays the applicant's business name and past usage history obtained from the user management table 405, as well as the desired dates and usage details obtained from the reservation management table 404. Based on this information, the facility staff member makes a comprehensive judgment considering the balance with other usage details and the reliability of the business, and presses the approval button 1204 or rejection button 1205 on the management screen 1200. The operation reception unit 331 accepts this press operation. The transmission / reception unit 332 transmits the selection result of approval or rejection, along with the corresponding reservation ID, to the server 20 via the communication unit 303. Furthermore, facility staff can maintain various information and pricing settings related to each plot by pressing the plot / category management button 1202 from the management screen 1200, or they can register specific businesses on a blacklist by pressing the usage restriction rule setting button 1203.

[0080] The reservation processing unit 213 receives and accepts the selection result sent from the facility staff terminal 30. If the selection result is "No" in step S504, the reservation processing unit 213 updates the status of the corresponding record in the reservation management table 404 to "Denied" and terminates the process (step S508).

[0081] If the approval selection result is accepted (step S504: Yes: Send), the reservation processing unit 213 proceeds to payment processing. Next, the reservation processing unit 213 retrieves information indicating the usage fee unit price from the area usage permission table 403 based on the reserved area ID and the category ID (identification information) of the usage content, and calculates the billing amount by multiplying the number of days of use, etc., by the usage fee unit price.

[0082] Next, in step S505 (the transmission step), the reservation processing unit 213 generates payment request data including the invoice amount, reservation ID, and pre-configured authentication information for the payment system 40, and transmits it to the external payment system 40 via API. Based on the received payment request data, the payment system 40 generates a payment page URL unique to this reservation application and responds to the server 20. The reservation processing unit 213 generates request information including this payment page URL and transmits it to the user terminal 10. If the server 20 does not cooperate with the payment system 40, the reservation processing unit 213 generates payment request data including the invoice amount and reservation ID as request information and transmits it to the user terminal 10. Furthermore, the payment method is not limited to online credit card payment, and bank transfer or invoice payment may be included as alternative embodiments. In this case, the reservation processing unit 213 may include the bank account information or information for issuing an invoice in the request information and transmit it, and the completion information may be entered by accepting a payment confirmation operation from a screen operated separately by the administrator.

[0083] Next, the web browser on the user terminal 10 displays a screen prompting the user to make a payment, based on the received request information. When the operation reception unit 131 receives a press operation by the user, such as pressing a payment button on the screen, the display control unit 133 transitions the display screen to the payment page. The user enters their credit card information on the payment page and completes the payment.

[0084] Next, once the payment is successfully completed, the payment system 40 sends completion information (fact of payment completion, transaction ID, and payment date and time, etc.) as an HTTP request to a URL (callback URL) that was previously specified by the server 20.

[0085] If the server 20 does not cooperate with the payment system 40, the payment process will be executed on the user terminal 10. The transmitting / receiving unit 132 sends completion information indicating the result of the payment execution to the server 20.

[0086] Next, in step S506 (the update step), the reservation processing unit 213 receives and accepts completion information from the user terminal 10 or the payment system 40, and verifies whether the transaction ID and other information included in the completion information are valid. If there are no problems as a result of the verification (Yes in step S506: the update step), the reservation processing unit 213 accesses the reservation management table 404 and updates the "Status" column of the corresponding record to a value that means "Confirmed" (e.g., code value "3"), which indicates the final confirmed status (step S507: the update step). At the same time, the reservation processing unit 213 also updates the "Payment Status" column to "Completed". With this, the series of reservation processes is completed, and the reservation is officially concluded.

[0087] On the other hand, if payment is not made or fails (No in step S506), the reservation is not confirmed. In this case, the reservation processing unit 213 sends incomplete information to the user terminal 10 notifying the user that payment was not completed, and a link to a screen prompting the user to make the payment again. If the user does not make the payment again within a predetermined period (for example, 72 hours from approval), the reservation processing unit 213 updates the "Status" column in the reservation management table 404 to "Cancelled" or the like, and invalidates the reservation application (step S509).

[0088] <Summary> Thus, according to this embodiment, the reservation process for the target area can be automated from application to payment and reservation confirmation in a seamless manner. This eliminates the need for manual interaction, significantly reduces the lead time to reservation confirmation, and enables fast and reliable area reservation management for both users and facility staff.

[0089] [Variation] <First variation> In this embodiment, the approval process was based on manual verification by facility staff, but a more sophisticated configuration of this approval process is also conceivable.

[0090] In the first modified example, the reservation processing unit 213 accepts additional data, including business information, when accepting a reservation application. The business information is at least one piece of information selected from the group consisting of (a) identity verification information such as a certified copy of the business's registration or scanned data of the representative's identification document, (b) licensing information indicating that the business has obtained the necessary licenses and permits from the national government, local governments, or other organizations (e.g., fire department, industry association), and (c) performance information indicating the business's past usage record (including cancellation rate) of the area (not limited to the target area). Licensing information includes, for example, information showing a business license from the public health center required for the operation of a restaurant, information showing a secondhand goods dealer's license required for the sale of used goods, and information showing a certificate of notification to the fire department in connection with holding an event.

[0091] The reservation processing unit 213 can, for example, use the received business information to perform processes such as expanding the information presented to the facility manager and scoring the business. Regarding expanding the information presented to the facility manager, the reservation processing unit 213 can, for example, display the received identity verification information and license information data (or links thereof) together when the facility manager checks the application details on the management screen 1200 (see Figure 12). This allows the facility manager to make more accurate approval decisions based not only on the application details but also on objective information that supports the reliability and qualifications of the business.

[0092] For the operator's scoring, the reservation processing unit 213 scores the user's reliability using a predetermined algorithm based on the received performance information (e.g., past usage count, total usage amount, cancellation rate, etc.). The predetermined algorithm may be rule-based or implemented by an AI model. For example, as a rule-based algorithm, the score can be calculated using a formula such as "Score = (Past usage count × Coefficient A) - (Cancellation rate for the past year (%) × Coefficient B)". Here, coefficient A is set to a value such as 10, and coefficient B is set to a value such as 5. The calculated score is presented to the facility manager as reference information when making approval decisions, and can also be used to determine the automatic approval conditions described later, and to determine the discount rate for usage fees.

[0093] For example, the reservation processing unit 213 can branch the application process before accepting the reservation request. That is, before accepting the user's operation to submit a reservation request, the reservation processing unit 213 dynamically determines whether or not the submission of data including business information is required in the reservation request, depending on the content of the request (e.g., combination of business operator and target area). Then, the reservation processing unit 213 branches the application process to determine whether or not to request the submission of data, depending on the determination result. "Branching the application process" means dynamically changing at least one of the procedures and documents required for the application, depending on the attributes of the applicant user and the characteristics of the area being requested.

[0094] Specifically, for example, the reservation processing unit 213 refers to rules pre-stored in the database 400 (e.g., a table defining the types of permit information required for specific combinations of space types and usage categories). When a user selects a space and usage category, the reservation processing unit 213 determines whether the combination matches the aforementioned rules. If it does, the reservation processing unit 213 dynamically displays the required permit information upload field on the availability check / reservation application screen 1300 (described later) and sets submission as a mandatory item. For example, if a business with a restaurant operating license applies for a space exclusively for food trucks, the reservation processing unit 213 will require the upload of the operating license as a mandatory item on screen 1300. On the other hand, if an apparel business applies for a regular retail space, the reservation processing unit 213 proceeds with the application process without requesting any special document submission.

[0095] By branching the application process in this way, users are not forced to go through the trouble of submitting unnecessary documents, and facility staff can reliably obtain the information necessary for approval at the application stage, resulting in even more efficient reservation management.

[0096] For example, the reservation processing unit 213 can branch the approval process depending on the content or type of the business information received. "Branching the approval process" means dynamically changing the procedures required for approval or the approvers depending on the attributes of the reservation application. For example, based on a pre-configured workflow definition, the reservation processing unit 213 automatically applies a simplified approval process (single-person approval process) that can be completed with the approval of only one person in charge if the application is from a reputable business that has used the system many times in the past and has a low cancellation rate. On the other hand, if the application is from a business that is using System 1 for the first time, or if the application includes usage that requires special permission, such as the use of fire, it is automatically routed to a more stringent approval process (staged approval process) that requires multi-stage approval (first-stage approval, second-stage approval) by personnel from multiple departments (e.g., sales department and facility management department). This configuration makes it possible to achieve both risk management and operational efficiency.

[0097] <Second variation> For example, it's conceivable to provide a user interface that allows users to visually search and select available spaces before submitting a reservation request.

[0098] As a premise for the second modification, the database 400 managed by the server 20 stores a correspondence between multiple partitions established in the facility and the categories of usage permitted for each of those partitions. Specifically, this correspondence is achieved by the partition usage permission table 403 shown in Figure 8, which associates the partitions managed by the partition master table 401 shown in Figure 6 with the categories managed by the category master table 402 shown in Figure 7.

[0099] In the second modified example, the user first operates the user terminal 10 and starts a search for available spaces from the website's top page or elsewhere. Upon receiving this operation, the user terminal 10 sends a request to the server 20 requesting the display of the available space search screen. Triggered by this request, the server 20 generates an availability confirmation / reservation application screen 1300, as shown in Figure 13, and sends it to the user terminal 10.

[0100] The availability check / reservation application screen 1300 includes a calendar format display. In this specification, "calendar format" refers to a graphical user interface (e.g., Gantt chart format display) that visualizes the reservation status of each space in chronological order, with a list of spaces on the vertical axis and dates or times on the horizontal axis.

[0101] The upper area of ​​the availability check / reservation application screen 1300 contains a usage category selection dropdown 1301 and a facility / space filtering area 1302. Here, users can narrow their search to their desired usage category or a specific facility brand. A facility brand is identification information used to group multiple facilities, such as "○○ Department Store Group" or "△△ Shopping Center Chain." When a user selects multiple facility brands on the screen, the reservation processing unit 213, which receives the selection information from the user terminal 10, extracts available spaces from the database 400 across multiple facility brands, all facilities belonging to each selected facility brand, and displays them all together in the calendar display area 1303 described later. This resolves the problem of conventional technology, where it was difficult to quickly find a space that matched the user's usage needs from a wide variety of spaces spanning multiple facilities, allowing users to find the optimal space from a wide range of options in a single operation.

[0102] A calendar display area 1303 is located in the central area of ​​the availability check / reservation application screen 1300. Based on the aforementioned request received from the user terminal 10, the information display unit 214 generates the calendar display area 1303 by referring to the information in the reservation management table 404. The information display unit 214 then sends information to the user terminal 10 for displaying the generated calendar display area 1303. By looking at the calendar display area 1303, the user can see at a glance which spaces are available and when. In addition, the calendar display area 1303 displays the "usage category" name of the usage content to be used for already reserved time slots 1304. This makes it possible to plan store openings while taking into account the competitive situation.

[0103] The lower area of ​​the availability check / reservation application screen 1300 contains the estimate display area 1305. When a user selects their desired usage date from the usage category selection dropdown 1301 or the calendar display area 1303, the user terminal 10 sends the selected information to the server 20 as search criteria. The reservation processing unit 213, upon receiving the search criteria, refers to the usage fee unit price for each category of usage permitted in each of the multiple partitions stored in the database 400, and calculates an estimated amount based on the corresponding usage fee unit price and the usage date included in the search criteria. The reservation processing unit 213 then sends screen update information to the user terminal 10 to display the calculated estimated amount in the estimate display area 1305. Each time the user changes the search criteria, these processes are performed using asynchronous communication (such as Ajax), and partitions that do not match at least one of the selected usage content and usage date are dynamically excluded from the calendar display area 1303.

[0104] In addition, user-facing screens may include a case list / details screen for checking the status of the user's own reservation requests, and a payment screen (neither shown) for performing payment procedures after approval. On the case list / details screen, the user can check a list of the reservation requests they have made and their respective statuses (e.g., "tentatively booked," "awaiting approval," "confirmed"). On the payment screen, an input form provided by the payment system 40 is typically embedded, allowing the user to securely enter credit card information and make payments.

[0105] Furthermore, the second modified example may be implemented with a configuration that only displays in a calendar format, without performing cross-facility brand searches, calculation of estimated costs, or dynamic exclusion of areas. Alternatively, the second modified example may be implemented with a configuration that displays in a calendar format and calculates estimated costs, etc., without performing cross-facility brand searches.

[0106] <Third variation> In the approval process, it is also conceivable to automate the approval process for reservation requests to further reduce the burden on facility staff and shorten the time until reservations are confirmed.

[0107] In the third modification, an automated approval condition is introduced. The automated approval condition is a condition used for the server 20 to automatically approve reservation applications that meet predefined rules without the intervention of the facility staff. The facility staff can register rules in the database 400 that specify at least one of the following: a specific business, a specific usage category, or a specific usage date, for example, from the management screen 1200. A "specific business" refers to a reputable business that the facility has judged to be reliable with a wealth of past usage records, and its technical significance lies in quickly processing standardized applications from reputable businesses and improving customer satisfaction. A "specific usage category" refers to a low-risk usage category (e.g., merchandise sales only) that the facility has judged not to require special review, and its technical significance lies in simplifying the approval process for applications that are uniform in content and safe. A "specific usage date" refers to a period when the facility is actively seeking reservations, such as the off-season, and its technical significance lies in functioning as an incentive to improve the facility's occupancy rate. Furthermore, the rules regarding the usage schedule are not limited to a specific number of days, such as "the number of usage days is N days or less (where N is an integer greater than or equal to 1)," but include a range that can be arbitrarily set by the facility staff.

[0108] Specifically, facility staff can register rules in the database 400, for example, from the management screen 1200, such as "when the application is from a specific excellent business" or "when the usage period is 3 days or less and the usage is 'sale of miscellaneous goods'."

[0109] The reservation processing unit 213 compares the specific information, usage category, and usage dates included in the received reservation application with these automatic approval conditions. If the reservation processing unit 213 determines that the application content meets any of the conditions, it skips the request for approval from the facility staff and the approval operation by the staff, and immediately proceeds to processing the payment request.

[0110] <Fourth variation> In the approval process, it is also conceivable to have a configuration that automatically rejects reservation applications from inappropriate businesses at an early stage.

[0111] In the fourth variation, the reservation processing unit 213 automates the denial process based on usage restriction rules pre-set by the facility staff. The usage restriction rules define a list of specific businesses that will be refused use of the facility, and may target businesses that have previously violated the terms of service or failed to pay fees.

[0112] Facility staff can, for example, access a dedicated screen (not shown) via the usage restriction rule setting button 1203 on the management screen 1200 to register specific information about the target businesses (business name, contact person's contact information, etc.). The registered specific information is stored in the database 400 as a list of specific businesses whose use of the target facility is denied, by setting the usage availability flag for the corresponding user (business) to "No" in the user management table 405.

[0113] When the reservation processing unit 213 receives a reservation request, it determines whether the business operator identified by the specific information included in the received reservation request is included in a list of specific business operators whose use of the target facility has been denied. If the determination is that the business operator is included in the list, the reservation processing unit 213 immediately updates the status in the reservation management table 404 to "denied" without requesting approval from the facility manager. The reservation processing unit 213 then generates denial information indicating that the reservation request has been denied and sends it to the user terminal 10 to notify the user of this fact.

[0114] Specifically, facility staff register businesses that have previously violated the terms of service or failed to pay fees in this list by setting the availability flag to "No" on the user management table 405. When the reservation processing unit 213 receives a reservation request, it identifies the user ID from the specific information included in the reservation request and checks the availability flag for that user by referring to the user management table 405. If the flag is "No," the reservation processing unit 213 immediately updates the status in the reservation management table 404 to "Denied" without requesting approval from the facility staff and notifies the applicant user accordingly.

[0115] <Fifth variation> After a reservation is confirmed, a configuration can be added to issue an electronic reservation slip to certify its contents. The reservation slip is an electronic certificate issued by server 20 after the reservation is confirmed to certify the contents of the reservation request.

[0116] Specifically, triggered by the update of the reservation status to "Confirmed" in step S507 of the flowchart shown in Figure 11, the reservation processing unit 213 aggregates the necessary information from various tables associated with the corresponding reservation ID (reservation management table 404, user management table 405, and area master table 401, etc.). The reservation processing unit 213 then embeds the aggregated information (e.g., business name, area to be used, usage dates, and confirmed amount, etc.) into a pre-prepared template (e.g., a form layout written in HTML or XML) and generates a reservation slip file in PDF format using a server-side PDF generation library. The generated reservation slip file is stored in the storage unit 202 so that the user can download it from the user terminal 10 at any time, and the download link is notified to the user.

[0117] <Other variations> Although embodiments of the present disclosure have been described above, the present invention is not limited thereto, and various modifications are possible without departing from the spirit of the invention. For example, it is possible to combine the configuration of one embodiment with the configuration of another embodiment. Specifically, a configuration can be considered that combines the "business operator scoring" described in the first modified example with the "automatic approval conditions" described in the third modified example. For example, if the business operator score calculated by the reservation processing unit 213 is equal to or greater than a preset threshold (e.g., 80 points), it is determined that the business operator falls under one of the automatic approval conditions, "a specific business operator," and the approval process is automated. Such a combination makes it possible to process applications from highly reliable business operators more efficiently, and synergistic effects can be expected.

[0118] Furthermore, in a calendar-style display, instead of limiting the information displayed for reserved slots to the usage category name, it is conceivable to display the business name in an anonymized form (e.g., "Apparel Company A") or to display a summary of the purpose of use. This would allow for increased usefulness of competitive information while respecting privacy.

[0119] Furthermore, in the estimation process, it is possible to not only change the unit price between weekdays and holidays, but also to introduce dynamic pricing that fluctuates depending on the season or time of day. This can help maximize the facility's revenue.

[0120] Furthermore, regarding the issuance of reservation slips, it is conceivable to add a function that not only allows users to download PDF files but also generates electronic reservation slips with QR codes (registered trademarks) that can be saved to a wallet app installed on a smartphone (user terminal 10). This would make on-site entry management smoother.

[0121] [Note] The details described in each of the above embodiments are noted below.

[0122] <Note 1> A program to be executed on a computer equipped with a processor, the program causing the processor to execute the following steps: receiving a reservation application from a user, which includes specific information identifying a business operator that wishes to use a section of a facility, the section the business operator wishes to use, the date of use of the section, and the details of use of the section; storing the status of the received reservation application as a provisional reservation; displaying the contents of the reservation application on a first terminal operated by a person in charge of the facility and receiving a choice of approval or rejection from the person in charge; if an approval choice is received, generating request information requesting online payment and sending said request information to a second terminal operated by the user; and, if completion information indicating that payment has been completed is received from the second terminal or an external device that performs payment processing, updating the status of the reservation application from provisional reservation to confirmed.

[0123] <Note 2> The program described in Appendix 1 further accepts data in the step of accepting reservation applications, which includes at least one piece of business information selected from a group consisting of the business operator's identity verification information, licensing information indicating that the business operator has obtained the necessary permits and licenses from the national government, local government, or other organizations for conducting the business, and performance information indicating the business operator's past usage record.

[0124] <Note 3> The program described in Appendix 2 causes the processor to perform a further step before the step of accepting the reservation application, which determines whether or not data submission is required in the reservation application depending on the combination of the business operator and the target plot, and branches the application process to determine whether or not to request the submission of such data.

[0125] <Note 4> The program described in Appendix 2 causes the processor to further execute a step that branches the approval process until the person in charge makes a choice between approval or rejection, depending on the content or type of the data received.

[0126] <Note 5> A program described in any of the following (Appendix 1) to (Appendix 4): A database is stored that associates multiple sections within a facility with the categories of usage permitted for each section. Before accepting a reservation request, the program accepts the user's selection of usage, and based on the selected usage, it refers to the database and causes the processor to further execute a step that displays the availability of permitted sections in a calendar format on a second terminal. In the step of displaying on the second terminal, the calendar format display identifies the category of usage for each reserved time slot.

[0127] <Note 6> The program described in Appendix 5 further stores in a database the usage fee per category for each permitted usage content in each of the multiple sections, and in the step of displaying on the second terminal, when the user selects the usage content and usage date, the program further causes the processor to execute the step of excluding sections that do not match at least one of the selected usage content and usage date from the calendar display, and when the user selects the usage content and usage date, calculates and presents an estimated amount based on the selected usage date and usage fee per category.

[0128] <Note 7> The program, as described in (Appendix 5) or (Appendix 6), stores in a database an associated facility brand, which is identification information for grouping multiple facilities, and multiple sections provided in each of the multiple facilities belonging to the facility brand, and in the step of displaying on a second terminal, displays in a calendar format the availability of sections for which use is permitted across one or more of the aforementioned facility brands.

[0129] <Note 8> A program as described in any of (Appendix 1) to (Appendix 7) that compares specific information, category of use, and date of use included in a received reservation application with an automated approval condition that specifies at least one of a specific business operator, a specific category of use, or a specific date of use, and if the reservation application satisfies the automated approval condition, causes the processor to further execute a step of approving the reservation application without executing a step of accepting selection.

[0130] <Note 9> A program as described in any of (Appendix 1) to (Appendix 8) that determines whether the business operator identified by the specific information contained in the received reservation application is included in a list of specific business operators whose use of the target facility has been refused, and if the determination result is that the business operator is included in the said list, causes the processor to further execute a step of rejecting the reservation application without executing the step of accepting the selection.

[0131] <Note 10> A program described in any of the notes (1) to (9) that, when the status of a reservation request is updated to confirmed, causes the processor to further execute the step of issuing a reservation slip that certifies the contents of the reservation request.

[0132] <Note 11> An information processing device comprising a processor, wherein the processor executes all steps in any of the programs described in (Appendix 1) to (Appendix 10).

[0133] <Note 12> A method to be performed on a computer equipped with a processor, wherein the processor performs all steps in any of the programs described in (Appendix 1) to (Appendix 10).

[0134] <Note 13> A system comprising one or more of the aforementioned processors that perform all steps in any of the programs described in (Appendix 1) to (Appendix 10). [Explanation of Symbols]

[0135] 1... System 10…User terminal (second terminal) 20... Server 30…Facility staff terminal (Terminal 1) 40…Payment system (external device) 80…Network 131, 331... Operation reception desk 132, 332... Transceiver Unit 133, 333… Display Control Unit 211...Communication Control Unit 212…Information Management Department 213...Reservation Processing 214…Information presentation section 400... Database 401... Partition Master Table 402…Category Master Table 403... Table of Permits for Use of Lots 404…Reservation Management Table 405...User management table 1200…Management screen 1201...List of reservation requests 1202... Section / Category Management Button 1203...Usage restriction rule setting button 1204... Approval button 1205... Deny button 1300... Availability check / reservation application screen 1301...Selection of usage category dropdown 1302…Facility / area filtering area 1303...Calendar display area 1304...Booked time slot 1305... Estimate display area

Claims

1. A program to be executed on a computer equipped with a processor, Multiple sections within the facility and the categories of permitted uses for each of these sections are associated and stored in a database. The aforementioned processor, A step of receiving a reservation application from a user that includes identifying information that identifies a business operator wishing to use a section of the facility, the section the business operator wishes to use, the date of use for the section, and the details of use for the section. A step to record the status of the received reservation request as a provisional reservation, The steps include displaying the contents of the reservation application on a first terminal operated by the person in charge of the aforementioned facility, and receiving the person in charge's choice to approve or deny the application, If the aforementioned approval selection is accepted, the process includes generating request information to request online payment and transmitting the request information to a second terminal operated by the user, When completion information indicating that the aforementioned payment has been completed is received from the second terminal or an external device that performs the payment processing, the status of the reservation application is updated from the provisional reservation to confirmed, and the following steps are performed: Prior to the step of accepting the reservation request, the user's selection of usage content is received, and based on the selected usage content, the database is referenced to display the availability of permitted spaces in a calendar format on the second terminal. In the step of displaying on the second terminal, the program displays, in the calendar format, the category of the reservation content related to the reserved time slot in an identifiable manner.

2. The program according to claim 1, which in the step of receiving the reservation application further receives data including at least one business information selected from the group consisting of identity verification information of the business operator, licensing information indicating that the business operator has obtained the necessary licenses and permits from the national government, local government or other organizations in order to carry out the business, and performance information indicating the business operator's past usage record.

3. The usage fee per category for each of the permitted uses in each of the aforementioned multiple sections is further stored in the database. In the step of displaying on the second terminal, when the user has selected the usage content and usage schedule, any sections that do not match at least one of the selected usage content and usage schedule are excluded from the calendar display. The program according to claim 1, which, upon receiving the user's selection of usage details and usage dates, further causes the processor to perform the step of calculating and presenting an estimated amount based on the selected usage dates and usage fees.

4. The facility brand, which is identification information for grouping multiple facilities, and the multiple sections provided in each of the multiple facilities belonging to that facility brand are stored in association with the database. The program according to claim 1, wherein in the step of displaying on the second terminal, the program displays the availability of spaces that are permitted to be used across one or more facility brands in the calendar format.

5. The program according to claim 1, which further causes the processor to perform a step of approving the reservation application without performing the step of accepting the selection if the reservation application satisfies the automatic approval conditions, which include the specific information, the category of use, and the usage date included in the received reservation application.

6. The program according to claim 1, which determines whether the business operator identified by the specific information included in the received reservation application is included in a list of specific business operators whose use of the target facility has been refused, and if the determination result is that the business operator is included in the list, causes the processor to further execute a step of rejecting the reservation application without executing the step of accepting the selection.

7. The program according to claim 1, which causes the processor to further execute the step of issuing a reservation slip that certifies the contents of the reservation application when the status of the reservation application is updated to confirmed.

8. A program to be executed by a computer equipped with a processor, The aforementioned processor, A step of receiving a reservation application from a user that includes identifying information that identifies a business operator wishing to use a section of the facility, the section the business operator wishes to use, the date of use for the section, and the details of use for the section. A step to record the status of the received reservation request as a provisional reservation, The steps include displaying the contents of the reservation application on a first terminal operated by the person in charge of the aforementioned facility, and receiving the person in charge's choice to approve or deny the application, If the aforementioned approval selection is accepted, the process includes generating request information to request online payment and transmitting the request information to a second terminal operated by the user, When completion information indicating that the aforementioned payment has been completed is received from the second terminal or an external device that performs the payment processing, the status of the reservation application is updated from the provisional reservation to confirmed, and the following steps are performed: In the step of accepting the aforementioned reservation application, the data further includes at least one business information selected from the group consisting of the business operator's identity verification information, licensing information indicating that the business operator has obtained the necessary licenses and permits from the national government, local government, or other organizations for conducting the business, and performance information indicating the business operator's past usage record. A program that, prior to the step of accepting the aforementioned reservation application, causes the processor to further execute a step of determining whether or not the submission of the aforementioned data is necessary in the reservation application, depending on the combination of the business operator and the target area, and branching the application process to determine whether or not to request the submission of said data.

9. A program to be executed by a computer equipped with a processor, The aforementioned processor, A step of receiving a reservation application from a user that includes identifying information that identifies a business operator wishing to use a section of the facility, the section the business operator wishes to use, the date of use for the section, and the details of use for the section. A step to record the status of the received reservation request as a provisional reservation, The steps include displaying the contents of the reservation application on a first terminal operated by the person in charge of the aforementioned facility, and receiving the person in charge's choice to approve or deny the application, If the aforementioned approval selection is accepted, the process includes generating request information to request online payment and transmitting the request information to a second terminal operated by the user, When completion information indicating that the aforementioned payment has been completed is received from the second terminal or an external device that performs the payment processing, the status of the reservation application is updated from the provisional reservation to confirmed, and the following steps are performed: In the step of accepting the aforementioned reservation application, the data further includes at least one business information selected from the group consisting of the business operator's identity verification information, licensing information indicating that the business operator has obtained the necessary licenses and permits from the national government, local government, or other organizations for conducting the business, and performance information indicating the business operator's past usage record. A program that causes the processor to further execute a step that branches the approval process until the person in charge makes a choice between approval or rejection, depending on the content or type of the data received.

10. An information processing device comprising a processor, wherein the processor executes all steps in any one of claims 1 to 9.

11. A method to be performed on a computer having a processor, wherein the processor performs all steps of a program according to any one of claims 1 to 9.

12. A system comprising one or more of the processors that perform all steps in the program according to any one of claims 1 to 9.

Images