Information processing system and program

Abstract

To enhance the possibility of using a reservation object having the possibility of being cancelled after a reservation compared with the case that the possibility of whether or not the reservation person will actually use the reservation object is not known.SOLUTION: A figure indicated by a mark 8A of (B) shows use possibility information about a possibility that a reservation person A will actually use a booth being a reservation object. A time zone indicated by a mark 8B of a figure 8(B) is a reservation time zone reserved by a user A. A CPU acquires the utilization possibility information of the user A about the reservation time zone. More specifically, the CPU acquires the use probability being the probability that the user A will use the booth as the use possibility information at each unit time.SELECTED DRAWING: Figure 8

Description

[Technical field]

[0001] The present invention relates to an information processing system and a program. [Background technology]

[0002] Patent document 1 discloses a reservation management system that includes an item management device that stores facility-related items for using the facility, a memory unit that stores reservation information indicating a reservation for using the facility, a coordination unit that controls the item management device according to the reservation information, and a cancellation waiting reception unit that accepts cancellations of reservations for use. Patent Document 2 discloses a process in which a cancellation availability notification means notifies a user terminal of cancellation availability information according to a queue registered in a cancellation waiting registration means, and inquires about the necessity of a reservation. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-107135 A [Patent Document 2] JP 2002-92440 A Summary of the Invention [Problem to be solved by the invention]

[0004] When a reserving user reserves a reservation object, there are cases where the reservation object is not actually used. In this case, if it is known in advance that there is a possibility that the reservation target will not be used, it is possible, for example, to encourage the user to cancel the reservation or to accept another reservation, thereby increasing the possibility that the reservation target will actually be used. An object of the present invention is to increase the possibility that a reservation object that may be canceled after reservation will be utilized, compared to a case where the possibility that a reserving person will actually utilize the reservation object is unknown. [Means for solving the problem]

[0005] The invention described in claim 1 is an information processing system that includes a processor and processes a reservation object for which a reservation has been made by a reserver, the processor acquiring information about the reserver who made the reservation for the reservation object and / or information about the reservation made by the reserver for the reservation object, and based on the content of the acquired information, Obtain possibility information, which is information about the possibility that the person who made the reservation will actually use the reservation object, A terminal device owned by a person who is about to make a reservation for the reservation target is acquisition The above Possibility information In the information processing system, when the reservation person makes a reservation for the reservation target over a plurality of time periods, the processor outputs the Possibility information of and when acquiring the possibility information for each time period, acquiring the possibility information based on information about the past usage status of the reservation object by the reservationr, which is information about whether the reservation object has been used by the reservationr, or acquiring the possibility information based on situation information, which is information about the situation of the reservationr, which is any of the location information of the reservationr, information about the progress of the work of the reservationr, and health information of the reservationr, or acquiring the possibility information based on attribute information of the reservationr, which is information about whether the reservationr is a corporate user or an individual user, or acquiring the possibility information based on information about the reservation date and time of the reservation object reserved by the reservationr, which is information about whether the time period specified by the reservation date and time is early morning or late night, or acquiring the possibility information based on information about the weather at the reservation date and time of the reservation object reserved by the reservationr, which is information indicating whether it will rain, or acquiring the possibility information based on information declared by the reservationr, which is information about whether the reservation made by the reservation for the reservation object is a preliminary reservation. It is an information processing system. Claim 2 The invention described in is, acquisition The above Possibility information The information processing system according to claim 1, further acquiring information on the possibility that a person other than the person who made the reservation can use the reservation target based on the information. Claim 3 The invention described in is, acquisition The above Possibility identified by the information The information processing system according to claim 1, wherein, if the reservation time is smaller than a predetermined threshold, the reservation of the reservation target made by the reservationr is cancelled, or information is output to prompt the reservationr to cancel the reservation. Claim 4 The invention described in is an information processing system as described in claim 1, in which a further reservation can be made by another reservation user for the reservation object during the time period in which the reservation user has made the reservation for the reservation object. Claim 5 The invention described in claim 1 is characterized in that the number of other reservation users who can make further reservations is limited. 4 The information processing system is as described above. Claim 6The invention described in is an information processing system described in claim 1, in which a reservation made by the reservationr for the reservation target cannot be canceled if the reservationr makes a further reservation for the reservation target during the time period in which the reservationr makes the reservation for the reservation target, the further reservation has not been made by another reservationr, and the predetermined time has passed. Claim 7 The invention described in is a program executed by a computer that performs processing related to a reservation object for which a reservation has been made by a reservationr, and has a function of acquiring information about the reservationr who made the reservation for the reservation object and / or information about the reservation made by the reservationr for the reservation object, and based on the content of the acquired information, Obtain possibility information, which is information about the possibility that the reservation person will actually use the reservation object and a terminal device of a person who is about to make a reservation for the reservation object, acquisition The above Possibility information and a program for causing the computer to realize the above. Possibility information of acquisition When the reservation person makes a reservation for the reservation target over a plurality of time periods, the function of Possibility information of the function of acquiring possibility information, when acquiring the possibility information for each time period, acquires the possibility information based on information about the past usage status of the reservation object by the reservationr, which is information about whether the reservation object has been used by the reservationr, or acquires the possibility information based on situation information, which is information about the situation of the reservationr, which is any of the location information of the reservationr, information about the progress of the work of the reservationr, and health information of the reservationr, or acquires the possibility information based on attribute information of the reservationr, which is information about whether the reservationr is a corporate user or an individual user, or acquires the possibility information based on information about the reservation date and time of the reservation object reserved by the reservationr, which is information about whether the time period specified by the reservation date and time is early morning or late night, or acquires the possibility information based on information about the weather at the reservation date and time of the reservation object reserved by the reservationr, which is information indicating whether it will rain, or acquires the possibility information based on information declared by the reservationr, which is information about whether the reservation made by the reservation for the reservation object is preliminary. It is a program. Effect of the Invention

[0006] According to the invention of claim 1, it is possible to increase the likelihood that a reservation object that may be canceled after reservation will be utilized, compared to a case where it is unknown whether the reservationr will actually use the reservation object. Claim 2 According to the invention, it is possible to obtain information regarding the possibility that a person other than the person who made the reservation can use the reservation object. Claim 3 According to the invention, the utilization rate of the reservation target can be increased compared to when the reservation of the reservation target is not canceled or when information is not output to prompt the reservation target to cancel the reservation. Claim 4 According to the invention, another reserving party can make a further reservation for the reservation target during the time period in which the reserving party is making a reservation for the reservation target. Claim 5 According to the invention, the processing in the information processing system can be simplified compared to a case where the number of other reservation users who can make further reservations is not limited. Claim 6 According to the present invention, the availability rate of the reservation target can be increased compared to a case where the reservation can be canceled even if the predetermined time has passed. Claim 7 According to the invention, the possibility of utilizing a reservation object that may be canceled after reservation can be increased compared to a case where it is unknown whether the reservationr will actually use the reservation object. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an overall configuration of an information processing system. [Diagram 2] FIG. 1 is a diagram showing a booth as an example of a space. [Diagram 3] FIG. 2 is a diagram illustrating the inside of the booth. [Figure 4] 2 is a diagram illustrating an example of a hardware configuration of a space management server. FIG. [Diagram 5] FIG. 2 is a diagram illustrating an example of a hardware configuration of a user terminal. [Figure 6] 13 is a diagram showing an example of a display screen displayed on a user terminal of a booth user when the booth user makes a reservation for the booth. FIG. [Figure 7] FIG. 13 is a diagram showing another example of a display screen displayed on the user terminal. [Figure 8] 1A to 1C are diagrams illustrating an example of processing performed by a CPU. [Figure 9] 13A to 13C are diagrams showing the flow of processing when user B makes a reservation after user A makes a reservation. [Figure 10] 11A to 11C are diagrams showing examples of display screens displayed on user terminals when each user makes a booth reservation. [Figure 11] FIG. 13 is a diagram showing another example of display on the user terminal. [Figure 12] FIG. 13 is a diagram showing another example of display on the user terminal. [Figure 13] FIG. 13 is a diagram showing another configuration example of the booth. [Figure 14] FIG. 13 is a diagram showing another example of a booth reservation format by a user. [Figure 15] FIG. 13 is a diagram showing another example of a display screen displayed on the user terminal. [Figure 16] FIG. 13 shows a display screen when the probability of success in waiting for a cancellation is calculated, taking into account information on whether or not the reservation is preliminary. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a diagram illustrating an overall configuration of an information processing system 1 according to the present embodiment. In this embodiment, a plurality of spaces 2 are provided, which are an example of locations that can be reserved and used by users. In this embodiment, each of the spaces 2 can be reserved, and a user can use the space 2 after reserving the space 2 in advance.

[0009] Examples of the space 2 that can be reserved include a booth, a guest room in a hotel, a conference room in a company, etc. These are examples of the space 2 that is separated from the surroundings by a wall, a partition, etc. Moreover, the space 2 in this embodiment includes tables and seats at which services are provided in restaurants, barber shops, etc. These are examples of the space 2 that is open to the surroundings.

[0010] An information processing system 1 shown in FIG. 1 is made up of various terminals connected to a cloud network 3. 1 shows a user terminal 4 operated by a user as an example of a terminal connected to the cloud network 3, and a space management server 5 as an example of an information processing device that manages the space 2. The space 2 is also connected to the cloud network 3. More specifically, various devices are provided in the space 2, and these devices are connected to the cloud network 3.

[0011] In this embodiment, an electronic lock is attached to the door of the space 2, and each space 2 can be locked. In this embodiment, a person who has the authority to unlock the space 2 can use this space 2. To unlock the space 2, the person who will be unlocking the space operates their own user terminal 4 to give an instruction to unlock. This instruction is sent to the space management server 5, which receives this instruction. The space management server 5 then gives an instruction to unlock the space 2 for which the instruction to unlock was given. This activates the electronic lock installed in the space 2, and the space 2 is unlocked.

[0012] In this embodiment, a portable smartphone is assumed as the user terminal 4. However, the portable user terminal 4 may be a so-called wearable terminal, a notebook computer, or a game terminal.

[0013] The space management server 5 manages various types of information related to the space 2. The space management server 5 manages, for example, information for identifying a user, information for identifying the space 2 that is the subject of a reservation, the start date and time of the reservation, the end date and time of the reservation, and the like. The information for identifying a user includes, for example, the user's name, sex, age, account, user ID, password, and management information attached to the individual. Furthermore, the information for identifying the space 2 to be used includes, for example, information for identifying the address or location, and management names and numbers. The space management server 5 also functions as a control device, and controls various devices installed in the space 2. Note that a control device may be installed in each space 2 in correspondence with each space 2. In this case, the control device installed in each space 2 controls the various devices installed in each space 2.

[0014] <Exterior composition of Space 2> FIG. 2 is a diagram showing a booth 80 as an example of the space 2. In the example shown in FIG. 2, the interior of a booth 80 is the space 2 that is the object of reservation, and in this embodiment, the space 2 inside this booth 80 can be reserved. The booth 80 of this embodiment may be placed indoors or outdoors, for example, inside train stations, airports, office buildings, commercial facilities such as restaurants and department stores, banks, libraries, art galleries, museums, public institutions and facilities, connecting corridors, parks, etc.

[0015] The booth 80 shown in FIG. 2 is a closed type booth 80 with a ceiling attached. Here, "closed type" does not mean airtight, but refers to a state in which the device has practical soundproofing properties. Moreover, the term "booth 80" refers to a structure in which there is a partition that separates the space 2 from other spaces located around the space 2. Here, it is not essential that there are partitions on all four sides of the space 2, and even a structure in which there is no partition in some parts is considered to be a booth 80. For example, even if the space 2 in which a user sits and uses has partitions only on the right and left sides of the user, it still falls under the category of booth 80. Additionally, a ceiling is not required, and even if the structure does not have a ceiling, it still falls under Booth 80.

[0016] 2 is provided with a housing 81 that constitutes the main part of the booth 80. The housing 81 is formed in a rectangular parallelepiped shape. The booth 80 has a ceiling 20A, a floor 20B, a wall 20C to which an openable and closable door 22 is attached, two walls 20D and 20E located on either side of the wall 20C, and a wall 20F located opposite the door 22. In this embodiment, the space 2 is surrounded by a wall surface 20C, a door 22, a wall surface 20D, a wall surface 20E, and a wall surface 20F, and the space 2 is provided inside these four walls and the door 22. In other words, in this embodiment, the space 2 is provided inside the housing 81.

[0017] In this embodiment, the door 22 is assumed to be a sliding door that can move along the wall surface 20C. In the case of Fig. 2, the door 22 is a single-side sliding door 22 that slides in one direction, but it may be a double sliding door 22 that opens and closes by moving two or more members past each other, or a split door 22 that slides two members left and right. A handle 22A that the user grasps when opening or closing the door 22 is attached to the door 22. The handle is also provided on the inside of the door 22. In addition, the door 22 is fitted with an electronic lock 22C that enables unlocking and locking of the door 22. Furthermore, in this embodiment, an opening / closing sensor S1 that detects whether the door 22 is opened or closed is provided.

[0018] The number of users of the booth 80 is roughly determined by the volume of the booth 80. The booth 80 in this embodiment is basically assumed to be a private room for one person to use. However, the booth 80 may be a large booth 80 capable of accommodating a large number of people. Note that the term "private room" does not mean that it can only be used by one person, but rather that it can accommodate a small number of people, for example 2-3 people. Furthermore, the shape and structure of the housing 81 constituting the booth 80, and the facilities and performance provided are optional.

[0019] Fig. 3 is a diagram illustrating the inside of the booth 80. Fig. 3 shows the booth 80 as viewed from above. In this embodiment, one desk 92 and one chair 91 are arranged inside the booth 80. Further, a luggage container 93 for users to place their luggage therein is provided within the booth 80. In addition, a luggage container 93 for storing the luggage placed therein is provided within the booth 80.

[0020] Inside the booth 80, as shown in Figs. 2 and 3, a monitor 32 which is a display device for displaying images is provided as a built-in device. In this embodiment, a speaker 30A is provided as a sound output device that outputs sound, as shown in Figures 2 and 3. Note that sound may be output from a speaker provided in the monitor 32 without providing a separate speaker 30A. 2 and 3, the present embodiment is provided with an imaging device 24 that captures images of the inside of the booth 80. The imaging device 24 is provided with an imaging element such as a CCD or a CMOS, and the imaging device 24 captures images of the inside of the booth 80 using this imaging element.

[0021] 2, the booth 80 is provided with a human presence sensor 25 that detects a user inside the booth 80. In this embodiment, the booth 80 is also provided with a temperature sensor 26 that detects the temperature inside the booth 80. As shown in FIG. 3, the booth 80 is provided with lighting equipment 40 for brightening the interior of the booth 80 . Furthermore, in this embodiment, as shown in FIG. 2, a window 42 is provided in the door 22, and in this embodiment, the inside of the space 2 can be viewed from the outside of the space 2 through this window 42.

[0022] Furthermore, as shown in FIG. 2, an information acquisition device 29 for acquiring individual information of users who use the booth 80 may be provided on the outer surface of the booth 80. This information acquisition device 29 is configured with, for example, a reader that reads a held-up ID card. Alternatively, the information acquisition device 29 may be a reader that reads the fingerprint or vein pattern of a user. Although not shown, the booth 80 is provided with an air conditioner for adjusting the temperature inside the booth 80.

[0023] FIG. 4 is a diagram illustrating an example of the hardware configuration of the space management server 5. As shown in FIG. The space management server 5, as an example of an information processing device, has a control unit 101 that controls the operation of the entire device, a hard disk drive 102 that stores management data, etc., and a network interface 103 that realizes communication via a LAN (Local Area Network) cable, etc.

[0024] The control unit 101 has a CPU (=Central Processing Unit) 111 as an example of a processor, a ROM (=Read Only Memory) 112 in which basic software, a BIOS (=Basic Input Output System), etc. are stored, and a RAM (=Random Access Memory) 113 used as a work area. The CPU 111 may be a multi-core. The ROM 112 may be a rewritable non-volatile semiconductor memory. The control unit 101 is a so-called computer.

[0025] The hard disk drive 102 is a device that reads and writes data from a non-volatile storage medium having a magnetic material applied to the surface of a disk-shaped substrate, although the non-volatile storage medium may also be a semiconductor memory or a magnetic tape. In addition, the space management server 5 is equipped with input devices such as a keyboard and a mouse, and a display device such as a liquid crystal display, as necessary. The control unit 101, the hard disk drive 102, and the network interface 103 are connected via a bus 104 and a signal line (not shown).

[0026] Here, the program executed by CPU 111 can be provided to space management server 5 in a state where it is stored on a computer-readable recording medium such as a magnetic recording medium (magnetic tape, magnetic disk, etc.), an optical recording medium (optical disk, etc.), a magneto-optical recording medium, or a semiconductor memory. Furthermore, the programs executed by the CPU 111 may be provided to the space management server 5 using a communication means such as the Internet.

[0027] Fig. 5 is a diagram showing an example of a hardware configuration of the user terminal 4. The configuration shown in Fig. 5 assumes that the user terminal 4 is a smartphone. The user terminal 4 has a control unit 201 that controls the operation of the entire device, a memory card 202 that stores various data, various communication interfaces 203 that comply with wireless communication standards, an input device 204 such as a touch sensor, a display device 205 such as a liquid crystal display or an organic EL (Electro Luminescence) display, and a GPS (Global Positioning System) sensor 206.

[0028] The control unit 201 includes a CPU 211, a ROM 212 storing firmware, BIOS, and the like, and a RAM 213 used as a work area. The CPU 211 may be a multi-core processor. The ROM 212 may be a rewritable non-volatile semiconductor memory.

[0029] The communication interface 203 is, for example, an interface used for connection to a mobile communication system, or an interface used for connection to a wireless LAN. The GPS sensor 206 is a sensor that receives radio waves from GPS satellites and measures the position of the user terminal 4. Information on latitude, longitude, and altitude output from the GPS sensor 206 provides the current position of the user terminal 4. Note that the GPS sensor 206 may be compatible with an indoor positioning system.

[0030] In this embodiment, the term "processor" refers to a processor in a broad sense, and includes general-purpose processors (e.g., CPU: Central Processing Unit, etc.) and dedicated processors (e.g., GPU: Graphics Processing Unit, ASIC: Application Specific Integrated Circuit, FPGA: Field Programmable Gate Array, programmable logic device, etc.). In addition, the operations of the processor may not only be performed by one processor, but may be performed by multiple processors in physically separate locations working together. The order of the operations of the processor is not limited to the order described in this embodiment, and may be changed.

[0031] FIG. 6 is a diagram showing an example of a display screen displayed on the user terminal 4 of a user of the booth 80 when the user makes a reservation for the booth 80. As shown in FIG. On the display screen shown in FIG. 6, a map is displayed, and the locations of a plurality of booths 80 are displayed on the map. In this embodiment, when a user of the booth 80 reserves the booth 80, he or she first selects an installation location from among the multiple installation locations displayed. The display form is not limited to this, and for example, a plurality of installation locations may be displayed in a list format, and the user may select an installation location from the list.

[0032] Once the installation location is selected, the user terminal 4 displays the vacancy status at the selected installation location by hour, as shown in FIG. 7 (a diagram showing another example of a display screen displayed on the user terminal 4). The display screen displayed on the user terminal 4 will be described in detail later. The user operates this display screen to specify a reservation time for the booth 80. Then, the user presses a confirmation button (not shown).

[0033] As a result, the space management server 5 performs the process of finalizing the reservation. Specifically, the space management server 5 receives information about the location of the booth 80 and the reservation time, registers the information about the location and reservation time in the hard disk drive 102 (FIG. 4), and performs reservation confirmation processing. The result of the reservation confirmation is then sent to the user terminal 4, and the person making the reservation is notified.

[0034] 8(A) to 8(C) are diagrams illustrating an example of processing performed by the CPU 111 (see FIG. 4), which is an example of a processor. More specifically, FIG. 8(A) to 8(C) are diagrams illustrating the flow of processing performed by the CPU 111 when generating the above-mentioned display screen to be displayed on the user terminal 4. In this embodiment, when generating a display screen to be displayed on the user terminal 4, the CPU 111 acquires possibility information (hereinafter referred to as "availability information") which is information about the possibility that a person who has already made a reservation for a booth 80 will actually use the booth 80 that is the subject of the reservation.

[0035] The diagram indicated by reference numeral 8A in FIG. 8B shows availability information regarding the possibility that a reserving person A, who is an example of a reserving person, will actually use the booth 80 that is the subject of the reservation. In this example, the time slot indicated by reference symbol 8B in Fig. 8(B) is the reserved time slot reserved by user A. CPU 111 acquires availability information for user A for this reserved time slot. More specifically, CPU 111 acquires, as the availability information, a usage probability, which is the probability that user A will use booth 80 per unit time.

[0036] For example, the CPU 111 grasps the past usage (usage record) of the booth 80 by the user A, and acquires availability information (usage probability) based on this past usage. In this case, the booth 80 does not have to be the same booth 80 as the booth 80 being reserved, but may include booths 80 installed at multiple locations that user A has used in the past.

[0037] Reference numeral 8T in FIG. 8B denotes the average of user A's past usage. In this example, by examining User A's past usage patterns, it was discovered that User A often left the room in the latter half of the reserved time slot, and also that he often did not arrive in time for the start of the reserved time slot. In this case, the CPU 111 acquires availability information indicating that availability is high in the middle of the first half of the reserved time slot and low in the latter half of the reserved time slot, as shown by reference symbol 8A in FIG. 8B.

[0038] Alternatively, the CPU 111 may obtain this availability information based on situation information, which is information about the situation of the person who made the reservation. Here, the situation information may be, for example, position information (location information) of user A. In this case, CPU 111 acquires the position information of user A as the situation information, and acquires availability information based on this position information. The location information of user A is acquired by obtaining an output from a GPS sensor 206 (see FIG. 5) provided in the user terminal 4 owned by user A.

[0039] More specifically, in this case, the CPU 111 determines, for example, based on traffic information, the shortest time required from the location identified by the location information to the location where the booth 80 is installed, and also determines the elapsed time from the current time to the reservation start time of the booth 80. If the shortest required time is longer than the elapsed time, the CPU 111 determines that the person making the reservation will be late to the booth 80, and grasps that the booth 80 will not be used from the reservation start time of the booth 80 until the time corresponding to the delay has elapsed. In this case, the CPU 111 acquires availability information indicating that the availability of the first half of the reserved time slot is 0%, for example.

[0040] Other examples of the status information include information about the progress of user A's work, information about user A's physical condition, and information about the means of transportation used by user A. Here, when the information identified by the information on the progress of the work indicates that the work is behind schedule, the CPU 111 acquires availability information indicating, for example, that the availability of the first half of the reserved time slot is low. In addition, when the information identified by the information on the progress of the work indicates that the work is behind schedule, the CPU 111 acquires availability information indicating that availability will be low throughout the entire reserved time period, for example. Information about the progress of the work is acquired, for example, from information registered in User A's electronic calendar (not shown) or the like.

[0041] In addition, when the information specified by the user A's physical condition information indicates poor physical condition, the CPU 111 acquires availability information indicating that the availability will be low throughout the entire reserved time period, for example. The physical condition information is acquired, for example, from a wristwatch-type electronic device (not shown) worn by the user A. In addition, when the information about the transportation used by user A indicates a delay in departure or arrival, or indicates the occurrence of traffic congestion, the CPU 111 acquires availability information indicating, for example, that the availability of the first half of the reserved time slot will be low.

[0042] Additionally, the CPU 111 may obtain the availability information based on the attribute information of the user A. Specifically, the CPU 111 acquires, for example, information on whether the user A is a corporate user as attribute information of the user A. If the user A is a corporate user, the CPU 111 acquires availability information indicating that the availability is low throughout the entire time period of the reservation time period.

[0043] Corporate users tend to have more last-minute cancellations than individual users, which means that the availability of booth 80 tends to be lower. Therefore, when user A is a corporate user, CPU 111 acquires availability information indicating that the availability is low throughout the entire time period of the reservation time slot, as described above. On the other hand, if user A is an individual user, CPU 111 acquires availability information indicating that availability is high.

[0044] Additionally, the CPU 111 acquires information on the user A's attributes, such as the user A's gender, age, and the like. Then, based on the information on gender and age, the CPU 111 acquires information on the tendency of users of the same gender as the user A to use the booth 80, and information on the tendency of users of the same generation as the user A to use the booth 80. In this case, CPU 111 acquires availability information based on the acquired information on the usage tendency. For example, if the usage tendency of users of the same generation as user A for booth 80 indicates a tendency to be late for the reservation start time, CPU 111 acquires availability information indicating that the availability of the first half of the reservation time slot will be low.

[0045] Additionally, the CPU 111 may acquire availability information based on information about a reservation made by the user A for the booth 80. The information about the reservation may be, for example, information about the reservation date and time of the booth 80 reserved by the user A. In this case, the CPU 111 obtains availability information based on the information about the reservation date and time. Specifically, for example, if the reservation date and time is in the early morning or late night, making the reservation more likely to be canceled, the CPU 111 acquires availability information indicating that the booth 80 is less likely to actually be used.

[0046] Furthermore, the CPU 111 may obtain, as information on the reservation date and time of the booth 80, information on the weather at the reservation date and time, and obtain availability information based on this weather information. Specifically, for example, when information about the weather at the reservation date and time indicates that it will rain or snow, CPU 111 obtains availability information indicating that the beginning of the reserved time slot is unlikely to be used, or availability information indicating that the entire reserved time slot is unlikely to be used.

[0047] In addition, for example, if the information about the weather at the reservation date and time indicates that the temperature is high (indicates that it is an extremely hot day), the CPU 111 obtains availability information indicating that there is a high possibility that the user will use the booth 80 even in the latter half of the reservation time period. The booth 80 of this embodiment is provided with an air conditioner (not shown), so that even if the temperature outside the booth 80 is high, the temperature inside the booth 80 remains low. In this case, the user will tend to remain in booth 80, and CPU 111 will acquire availability information indicating that there is a high possibility that the user will utilize booth 80 even in the latter half of the reserved time slot.

[0048] Additionally, the CPU 111 may obtain the availability information based on the information declared by the user A. More specifically, when user A indicates that the reservation for booth 80 is preliminary, CPU 111 obtains availability information for this reservation indicating that it is unlikely that booth 80 will actually be used. Details of the preliminary reservation of the booth 80 will be described later.

[0049] In this manner, in this embodiment, the CPU 111 obtains availability information, which is information about the possibility that the user A will actually use the booth 80. In other words, in this embodiment, among the time slots reserved by user A, the time slots during which user A is likely to actually use booth 80 and the time slots during which user A is unlikely to actually use booth 80 are estimated.

[0050] In this embodiment, based on the acquired availability information, CPU 111 further acquires information (hereinafter referred to as "success probability information") about the possibility (hereinafter referred to as "success probability") that a cancellation wait by a person other than the reservation user A will be successful. In other words, based on the obtained availability information, the CPU 111 further obtains information regarding the possibility that a user other than the user A who made the reservation and who has waited for a cancellation of the booth 80 can use the booth 80. Here, "cancellation waiting" refers to a reservation mode in which, when a reservation that has a confirmed reservation for the reservation object has been made, a further reservation (hereinafter referred to as an "additional reservation") is made for this reservation object, and when the confirmed reservation is cancelled, this additional reservation is switched to the confirmed reservation.

[0051] FIG. 8C is a diagram showing success probability information acquired by CPU 111. The CPU 111 acquires success probability information based on the acquired availability information. More specifically, the CPU 111 acquires the success possibility information shown in FIG. 8(C) based on the availability information indicated by reference numeral 8A in FIG. 8(B). More specifically, the CPU 111 subtracts the availability information (availability probability) for each time slot from 100% to obtain the success probability information shown in FIG. 8C.

[0052] In this embodiment, as indicated by reference symbol 8A in FIG. 8B, the possibility (probability of utilization) of the booth 80 by user A is high in the first half of the user A's reservation time slot. 8C, in the first half of the reservation time slot of user A, the probability that users other than user A will be able to successfully wait for a cancellation is low. In other words, the possibility that users other than user A will be able to use booth 80 is low.

[0053] In contrast, in the latter half of the user A's reservation time slot, the user A's availability to the booth 80 becomes low. In this case, as shown by reference symbol 8S in FIG. 8C, in the latter half of the user A's reservation time slot, the probability that users other than user A will be able to successfully wait for a cancellation becomes high. More specifically, in the latter half of user A's reservation time slot, the value specified by the success probability information becomes larger, and the probability that a user other than user A will be able to successfully wait for a cancellation increases. In other words, in the latter half of user A's reservation time slot, the possibility that a user other than user A will be able to use booth 80 increases.

[0054] FIG. 8(A) shows the success probability information before user A makes a reservation for booth 80. It should be noted that the "success possibility information" here is not information indicating the possibility that the cancellation waiting will be successful, but information indicating the possibility that user A's reservation will be successful. In this example, since there are no reservations at all before user A reserves booth 80, the value specified by the success probability information is 100% at all times. In other words, user A is able to reserve and use booth 80 at all times.

[0055] In contrast, when user A makes a reservation for booth 80, the value specified by the success probability information becomes smaller for the time period in which user A makes the reservation, as shown in FIG. 8(C). More specifically, in this embodiment, the utilization probability shown by reference symbol 8A in Fig. 8(B) is subtracted from the success probability shown in Fig. 8(A) to obtain the success probability information shown in Fig. 8(C). Therefore, as shown in Fig. 8(C), the value specified by the success probability information becomes smaller for the time slot in which user A has made a reservation. In particular, since there is a high possibility that user A will use booth 80 during the first half of the reservation time slot, the probability of success is low during the first half of the reservation time slot for user A.

[0056] 9(A) to 9(C) are diagrams showing the flow of processing when user B makes a reservation after user A makes a reservation. 9(A) shows the success possibility information after user A reserves booth 80 and before user B reserves booth 80. In other words, the success possibility information shown in FIG. 9(A) is the same as the success possibility information shown in FIG. 8(C).

[0057] FIG. 9B is a diagram showing availability information for user B during the time period in which user B desires to use booth 80. In FIG. In this example, like user A above, as indicated by reference symbol 9X, it is highly likely that user B will use booth 80 in the first half of the reserved time slot. In this case, as shown by reference symbol 9B, availability information is acquired which indicates that availability is high in the first half of the reserved time slot and low in the second half of the reserved time slot.

[0058] In this example, the user B reserves the booth 80 for a time period before the reserved time period of the user A, as indicated by reference numeral 9D. In this example, as indicated by reference numeral 9G, user B reserves booth 80 on a cancellation waiting list for the reservation time slot that user A has already reserved.

[0059] FIG. 9C is a diagram showing the success probability information after a reservation is made by user B. When CPU 111 obtains the availability information for user B, it subtracts the availability information for user B (availability information indicated by symbol 9B in FIG. 9(B)), which is the availability information (usage probability) for each time period, from the success possibility information shown in FIG. 9(A), to obtain the success possibility information shown in FIG. 9(C). In this example, in addition to the reservation by user A, a reservation by user B is also made, so the value specified by the success probability information becomes lower over a wider time period, as shown in Fig. 9(C). In other words, the success probability of the cancellation waiting becomes lower over a wider time period. In particular, in the time period when both user A and user B have reservations (the time period when user B is on the waiting list), the probability of successful cancellation is extremely small.

[0060] 10(A) to 10(C) are diagrams showing examples of display screens displayed on user terminal 4 when each user makes a reservation for booth 80. FIG. In this embodiment, by the above process, success possibility information is generated, and this success possibility information is reflected on the display screen displayed on the user terminal 4. Figures 10(A) to (C) show the state in which the success possibility information is reflected on the display screen.

[0061] FIG. 10(A) is a diagram showing a display screen displayed on the user terminal 4 of the user A when the user A makes a reservation for the booth 80. As shown in FIG. When user A makes a reservation for booth 80, the success probability information is displayed in the field indicated by reference symbol 10A in FIG. 10(A). In this example, the success probability for each time slot is 100%. In other words, when user A makes a reservation, there are no other reservations, and the probability that user A's reservation will be successful is 100% for each time slot.

[0062] User A then operates this display screen to reserve booth 80. In this example, a case is illustrated in which user A has made reservations for booth 80 for four time slots: "10:00~", "10:15~", "10:30~", and "10:45". In this case, in this embodiment, a mark "o" is displayed for each of the four time slots, indicating that the reservation has been confirmed.

[0063] FIG. 10B is a diagram showing a display screen displayed on the user terminal 4 of the above-mentioned user B when the user B makes a reservation for the booth 80. As shown in FIG. In this case, the success probability of waiting for cancellation (success possibility information) is displayed on the display screen as shown by reference numeral 10D. When user B makes a reservation for booth 80, the probability of success in waiting for a cancellation differs depending on the time of day.

[0064] More specifically, in this embodiment, as described above, there is a high probability that user A will use booth 80 during the first half of user A's reservation time slot, and accordingly, the probability of successful cancellation waiting is low during the time slot corresponding to this first half. Specifically, in the time period corresponding to this first half, as shown by reference numeral 9E in FIG. 10(B), the probability of successful cancellation waiting is 30% and 10%.

[0065] On the other hand, the success rate of the cancellation waiting list is high for time slots where no reservations have been made by user A or time slots where user A is unlikely to actually use the service. Specifically, for time slots where no reservations are made by user A, the probability of successful cancellation waiting is 100%. Furthermore, for the time slot (time slot indicated by reference symbol 9F) where user A is unlikely to actually use the service, the success rate of the cancellation waiting list is 80%.

[0066] User B refers to the display screen shown in FIG. 10(B) to make a reservation. In this example, a case is illustrated in which user B makes reservations for four time slots, "09:30~", "09:45", "10:00~", and "10:15~". For the time slots "09:30~" and "09:45~", the success rate is 100%, so reservations for these time slots are confirmed as is.

[0067] In contrast, for the two time slots "10:00~" and "10:15~", reservations have already been made by user A, so they will be placed on the waiting list for cancellations. In other words, for the two time slots "10:00~" and "10:15~", the success rate of the waiting list for cancellations is less than 100%, so in this case they will be placed on the waiting list for cancellations. In this embodiment, the success rate of the cancellation waiting is displayed on the user terminal 4 of the user B, and the user B makes a reservation after grasping the possibility of whether or not the cancellation waiting he / she makes will be successful. Specifically, the user B makes a reservation after grasping the probability indicating the degree of possibility that the booth 80 can be used. Therefore, user B does not have to wait for a cancellation without knowing that there is a high possibility that booth 80 will not be available to him / her.

[0068] FIG. 10C is a diagram showing a display screen displayed on the user terminal 4 of the user C when the user C makes a reservation for the booth 80. As shown in FIG. In this case as well, the display screen displays the probability of success in waiting for cancellation (success possibility information) as shown by reference numeral 10G. When user C makes a reservation for booth 80, the probability of success in waiting for a cancellation also varies depending on the time of day.

[0069] Specifically, when user C makes a reservation for booth 80, reservations have already been made by users A and B, and during the time period when reservations are made by these two users, the probability of successful cancellation waiting is 0%, as shown by symbol 10J in Figure 10(C). On the other hand, for time slots with no reservations or time slots used by only user A or only user B (time slots indicated by symbol 10K), the probability of successful cancellation waiting is higher than for time slots reserved by both user A and user B. User C refers to this display screen shown in FIG. 10(C) to make a reservation.

[0070] In this embodiment, on the display screens of Figures 10(B) and (C), the color of the background 10X of the display area in which the success probability is displayed is changed, the pattern of the background 10X is changed, or the color density of the background 10X is changed depending on the success probability. This makes it easier for the user to intuitively grasp the probability of success in waiting for a cancellation, compared to when the color of background 10X is white.

[0071] In this embodiment, when a user reserves booth 80 over multiple time periods, CPU 111 acquires availability information (usage probability) for each time period. In other words, CPU 111 acquires availability information for each predetermined unit time. In this embodiment, this predetermined unit time is 15 minutes. Then, based on this availability information (availability probability) acquired for each time slot, the CPU 111 grasps success possibility information (cancellation waiting success probability) for each time slot. As a result, the probability of success in waiting for a cancellation is displayed for each time period, as shown in FIGS.

[0072] Each user who uses a booth 80 is uncertain as to whether they will be able to arrive at the reserved booth 80 on time, or whether they will be able to complete their work within the reserved time, and so they tend to reserve the booth 80 for a period of time longer than the time they will actually use the booth 80. In this case, the beginning part of the reserved time may not actually be used, or the latter part of the reserved time may not actually be used. In contrast, in this embodiment, the beginning and latter parts are more likely to be reserved by other users, and even if a booth 80 is canceled, the canceled part is more likely to be used by another user. This increases the utilization rate of the booth 80.

[0073] Here, for example, a display mode may be considered in which, without displaying the success possibility information (probability of success in waiting for cancellation), only information regarding whether or not a reservation has already been made is displayed on the display screen of the user terminal 4. In this case, even if booth 80 is canceled, users who are waiting for a cancellation (hereinafter referred to as "users waiting for a cancellation") are less likely to be able to use booth 80, and the utilization rate of booth 80 is likely to decrease.

[0074] In a mode in which the success probability information is not displayed and only whether or not a reservation has already been made is displayed, the expectations of users on a waiting list are likely to decrease. In this case, the users on the waiting list pay less attention to the booth 80, and even if the booth 80 is actually canceled, the users on the waiting list tend not to use the booth 80. In this case, the utilization rate of the booth 80 tends to decrease.

[0075] In contrast, in the present embodiment, when success probability information is displayed and, for example, the probability of success in waiting for a cancellation specified by this success probability information is high, the expectations of users who are waiting for a cancellation become high. In this case, if a cancellation actually occurs for the booth 80, there is a high possibility that a user waiting for a cancellation will use this booth 80. In this case, the utilization rate of the booth 80 increases.

[0076] As another example of processing, for a time slot in which the availability (usage probability) is 0% or the availability (usage probability) is less than a predetermined threshold, the reservation for that time slot may be cancelled. In addition, for time periods when the availability (probability of use) is 0% or when the availability (probability of use) is less than a predetermined threshold, a notification (hereinafter referred to as a "cancellation promotion notification") may be sent to encourage the user to cancel the reservation for that time period.

[0077] In other words, for a time period whose availability information (usage probability) is less than a predetermined threshold, such as the time period indicated by symbol 8X in Figure 8(B), CPU 111 cancels the reservation for that time period or outputs information to prompt cancellation. When the information for issuing a cancellation promotion notice is output, a notice is issued to the user via the user terminal 4, urging the user to cancel the reservation by himself / herself. In addition, the "notification urging the user to cancel the reservation themselves" may be a direct notification of information such as "Please cancel your reservation," or it may be a notification of information such as "You will be charged even if you do not use the booth."

[0078] 11(A) to (C) and FIG. 12 are diagrams showing other display examples on the user terminal 4. In FIG. FIG. 11(A) is a diagram showing a display screen displayed on the user terminal 4 of the user A when the user A makes a reservation for the booth 80. As shown in FIG. This display screen displays whether or not a reservation can be made for each time period. More specifically, as shown by reference numeral 11A, this display screen has a column indicating whether or not a reservation can be made, and whether or not a reservation can be made is displayed in this column indicating whether or not a reservation can be made. In the reservation availability column, "O" indicates that a reservation is possible, while "X" (described later) indicates that a reservation is not possible.

[0079] In this example, similar to the above, when user A makes a reservation, there are no reservations at all and reservations can be made at any time slot. More specifically, "O" is displayed for every time slot, meaning that reservations can be made during every time slot. In addition, on this display screen, the "Reservations" column located on the far right shows whether or not there are reservations. In this example, there are no reservations, and "No" is displayed for all time slots, indicating that there are no reservations.

[0080] 11B shows a display screen after user A has made reservations for four time slots. Specifically, the display screen shows a display screen after user A has made reservations for four time slots: "09:45~", "10:00~", "10:15~", and "10:30~". Here, normal reservations (hereinafter referred to as "normal reservations") have been made for the two time slots "10:00~" and "10:15~", and when a normal reservation is made, "Completed" is displayed in the "Reservation Possible / Not Possible" column. Also, "Yes (A)" is displayed in the "Reservation Availability" column. Here, "(A)" indicates that a reservation has been made by user A.

[0081] Moreover, the two time slots "09:45~" and "10:30~" indicate cases where backup reservations have been made by user A. In other words, the two time slots "09:45~" and "10:30~" indicate cases where buffer reservations have been made by user A. In this case, the "Reservation Possible" field displays "Completed (Ba)," and the "Reservation Available" field displays "Available (ABa)." The "Ba" display indicates that this is a backup reservation.

[0082] However, there is a high possibility that this preliminary reservation will not actually be utilized. As described above, a user who uses a booth 80 is uncertain as to whether he or she will be able to arrive at the reserved booth 80 on time, or whether the work will be completed within the reserved time. For this reason, users tend to make reservations for a period longer than the time they will actually use the booth 80, and in this case, they may make a preliminary reservation at the beginning or end of the reservation time. In other words, users may make reservations at the beginning or end of the reservation time with a lower desire to use the booth 80 than in a normal reservation. In this embodiment, the user is asked to declare whether or not the reservation is a preliminary reservation, and if it is a preliminary reservation, the user registers information indicating that it is a preliminary reservation.

[0083] In this embodiment, the time slot reserved by the preliminary reservation is allowed to be reserved by other users. In other words, the time slot reserved by the preliminary reservation is allowed to be put on hold for cancellations. On the other hand, in this embodiment, a time slot reserved by a normal reservation cannot be reserved by other users. In other words, a time slot reserved by a reservation other than a backup reservation cannot be put on hold for a cancellation.

[0084] In this embodiment, if a reservation made by a reserving person for a booth 80 is a reservation in which the reserving person has made a declaration indicating a low degree of desire to use the booth 80, further reservations can be made for the booth 80. Specifically, further reservations can be made by other reservation holders for the booth 80 during a time period in which a reservation has been made that indicates a low degree of desire to use the booth 80. On the other hand, if the reservation made by a reserving person for booth 80 is a reservation for which the above-mentioned declaration has not been made, further reservations by other reserving persons cannot be made.

[0085] In this embodiment, a case has been described in which a preliminary reservation is identified based on a voluntary declaration from the user. However, in addition to this, for example, the user may be inquired via the user terminal 4 as to whether or not the reservation is a preliminary reservation. More specifically, an inquiry may be made as to whether or not the first and last time slots of the entire reservation time slot are preliminary reservations. Then, for the time slot for which a reply is received that the reservation is a preliminary reservation, information indicating that the reservation is a preliminary reservation is registered, and further, the time slot is made available for reservation by other users.

[0086] FIG. 11C shows a display screen that other users who are going to make a reservation after user A refer to when making the reservation. On this display screen, for the two time slots "10:00~" and "10:15~" for which regular reservations are made, an "X" is displayed in the "Reservation Availability" column, indicating that reservations cannot be made on a waiting list for cancellations. In addition, for the two time slots "10:00~" and "10:15~" for which regular reservations were made, "Yes (A)" is displayed in the "Reservation Available" column, indicating that a regular reservation has been made by user A.

[0087] In addition, for the two time slots for which preliminary reservations were made, "09:45~" and "10:30~," the "Reservation Availability" column shows "--." This "--" indicates that reservations can be made on a waiting list for cancellations. In addition, for the two time slots "09:45~" and "10:30~", which are time slots for which preliminary reservations have been made, "Yes (Aba)" is displayed in the "Reservation Availability" column. The display of "(Aba)" indicates that preliminary reservations have been made by user A.

[0088] In this processing example shown in FIG. 11 as well, availability information, which is information about the possibility that user A will actually use booth 80, is acquired. Specifically, in this processing example, information as to whether or not a reservation is a preliminary reservation serves as availability information, and availability information is obtained by obtaining information as to whether or not a reservation is a preliminary reservation. In this embodiment, for the time period in which information indicating that the reservation is preliminary has been acquired, possibility information has been acquired indicating that there is a low possibility that booth 80 will actually be used by user A.

[0089] Furthermore, in this embodiment, the success possibility information is displayed on the display screen shown in Fig. 11 (C). Specifically, in this embodiment, the information "-" is displayed as the success possibility information, and the information "Yes (A-ba)" is also displayed. In this case, a user who is waiting for a cancellation will know that there is a certain probability of success in waiting for a cancellation during the time period when the ``-'' display and the information ``Available (A-ba)'' are displayed.

[0090] FIG. 12 shows the display screen after users B and C have performed operations on the display screen shown in FIG. 11(C). The display screen shown in Figure 12 shows that a reservation (reservation on a cancellation waiting list) has been made by User C for the time period "from 9:45", and in this case, the "Reservation availability" column displays "X (K)". Here, "x (K)" indicates that you cannot wait any longer for a cancellation.

[0091] In addition, when user C makes a reservation (reservation on a waiting list for a cancellation) for the time period "09:45~", in the "Reservation available" column, in addition to "Available (A-Ba)", "Waiting (C-Ba)" will be displayed. Here, "Ki-waiting" indicates a reservation due to a cancellation waiting list, and "(C)" indicates a reservation by user C.

[0092] Also, for the time slot "from 10:30", a reservation has been made by user B (a reservation on a waiting list for cancellations), and in this case too, "x" is displayed in the "Reservation Availability" column. In this case, other users will no longer be able to make reservations for this "10:30" time slot. Also, when user B makes a reservation for the time slot "10:30~", in the "Reservation" column, in addition to the display "Available (Aba)", "Waiting (B)" is additionally displayed. Here, "Waiting" indicates waiting for a cancellation as described above, and "(B)" indicates a reservation by user B.

[0093] In this processing example, only one person can make a reservation on a cancellation waiting list for each time slot. For this reason, when one user makes a reservation on the waiting list for a cancellation, like User B and User C above, other users will be unable to make reservations (on the waiting list for a cancellation) for that time period thereafter.

[0094] (others) In the present embodiment, as described above, the case has been described where the booth 80 is reserved and then used, but it is also possible to make it possible to cancel this reservation. However, when canceling a reservation, if a predetermined condition is satisfied, the reservation may not be cancelled. Specifically, if a reservation is cancelled after a predetermined time, such as 5 minutes before the reservation start time, and there are no other users waiting for a cancellation for that reservation, the reservation may not be cancelled.

[0095] In other words, if a reservation is made for a booth 80 during the time period in which the reservation is made by a reservationr, and this further reservation has not been made by another reservationr, and if the predetermined time has passed, the reservation for the booth 80 by this reservationr may not be able to be canceled.

[0096] In such a case, if cancellation of a reservation were permitted, a new user wishing to use the booth 80 whose reservation has been cancelled would not be found immediately, and the booth 80 would end up empty, resulting in a drop in the utilization rate of the booth 80. In contrast, if reservations cannot be canceled as described above, the possibility that the booth 80 will be used increases, and the operating rate of the booth 80 improves.

[0097] Additionally, information may be provided to users who are waiting for a cancellation near the booth 80, such as in front of the booth 80, via a display device or speaker installed at the booth 80. Specifically, for example, as shown in FIG. 13 (a diagram showing another example configuration of booth 80), a display device 89 and a speaker (not shown) may be provided on the outside of booth 80, and information may be communicated through this display device 89 and speaker.

[0098] Specifically, for example, a message may be displayed on the display device 89 indicating that the cancellation waiting was unsuccessful, and a user (not shown) who is waiting for a cancellation near the booth 80 may be notified that the cancellation waiting was unsuccessful (not realized). In this embodiment, when the success rate of the cancellation waiting is, for example, 80%, a user who is waiting for a cancellation may come to the front of the booth 80, for example, and wait for the start time of his / her reservation to arrive.

[0099] On the other hand, a user who is currently inside booth 80 may choose to continue using booth 80 without cancelling his or her reservation. In this case, as described above, users waiting in front of the booth 80 for a cancellation are notified via the display device 89 or speaker installed in the booth 80 that their waiting for a cancellation was unsuccessful.

[0100] More specifically, if the user in booth 80 does not issue a cancellation instruction even at a predetermined time, for example, 5 minutes before the start time of the reservation made by the user on the cancellation waiting list, a notification is sent via the display device 89 and speaker that the cancellation waiting list was not successful. In this embodiment, the user is notified through the display device 89 and speaker provided in the booth 80. Alternatively, the user may be notified through the user terminal 4.

[0101] In addition, when a user makes a reservation on the waiting list for a cancellation, the reservation may not be accepted solely on the waiting list for a cancellation. More specifically, for example, if a user makes a reservation for 15 minutes, which is one unit of time, and this reservation is a reservation due to a cancellation waiting list, this reservation due to a cancellation waiting list may not be accepted. Also, for example, if a user makes a reservation that spans multiple consecutive unit times, and all of the multiple times are reserved on a cancellation waiting list, the reservation may not be accepted.

[0102] A reservation based solely on waiting for a cancellation receives less attention from the user (the user who made the reservation) than a normal reservation, and in some cases, the user may forget that they were on waiting for a cancellation. In this case, even if the cancellation waiting list is successful, the user may not show up at booth 80, and booth 80 may not be used at all. In contrast, if reservations based solely on waiting for cancellations are not accepted, the reservation will be either a regular reservation only, or a reservation in which regular reservations and reservations based on waiting for cancellations are consecutive in time, which increases the likelihood that a user will show up at booth 80 if the waiting for cancellations is successful.

[0103] In other words, in this embodiment, with respect to a further reservation by another reservationr for booth 80 during a reservation time period during which a reservationr has made a reservation for booth 80, this further reservation may or may not be accepted depending on the reservation type of the other reservationr. Specifically, in this embodiment, if another reservation user also makes a reservation for another time period adjacent to the above-mentioned reserved time period, for which no reservation has been made, this further reservation will be accepted. On the other hand, if other reservation users do not make reservations for other time slots, or if other reservation users also make reservations for other time slots adjacent to the reserved time slot and for which reservations have already been made, no further reservations will be accepted.

[0104] More specifically, for example, in the case of the reservation type shown by reference numeral 10Z in Fig. 10(B), a normal reservation and a reservation due to a cancellation waiting are consecutively made. In other words, the reservation type shown by reference numeral 10Z in Fig. 10(B) is a reservation type in which one user makes a reservation in a state where a normal reservation and a reservation due to a cancellation waiting are consecutively made. In this case, if the reservation through the cancellation waiting list is successful, the user will be able to use the booth 80 through the cancellation waiting list following the normal reservation, and the booth 80 will likely be used during the time period for which the cancellation waiting list was in place. In contrast, for example, as shown in FIG. 14 (a diagram showing another example of a reservation format for booth 80 by a user), if the reservation format is a reservation format based only on waiting for a cancellation, even if the waiting for a cancellation is successful, the user on the waiting list will be less likely to show up at booth 80.

[0105] Alternatively, the number of users who can wait for a cancellation for each reservation time slot may be set to a predetermined threshold value or less, such as one. In other words, in this embodiment, a further reservation for booth 80 during the time period in which a reservation holder has made a reservation for booth 80 can be made by another reservation holder, but the number of other reservation holders who can make such a further reservation may be limited to a number below a predetermined threshold, such as one person.

[0106] If a large number of people were allowed to wait for cancellations for each reservation time slot, the system would become complicated, but by limiting the number of people in this way, this can be prevented. In addition, if a large number of people are allowed to wait for cancellations, users who are low on the waiting list will pay less attention to their own waiting, and as mentioned above, they will be more likely to forget that they were waiting for a cancellation.

[0107] In this case, if the cancellation waiting list for this user who is ranked low is successful, it is likely that this user will not actually come to booth 80. In the present embodiment, by limiting the number of users who can wait for a cancellation to a number equal to or less than a predetermined threshold, and narrowing down the users who can wait for a cancellation, such a situation is less likely to occur.

[0108] In addition, the display screen displayed on the user terminal 4 may be a combination of the display screen shown in FIG. 10 and the display screen shown in FIG. 11(C), as shown in FIG. 15 (a diagram showing another example of a display screen displayed on the user terminal 4). Specifically, the display screen shown in FIG. 10 displays the probability of success in waiting for a cancellation, and the display screen shown in FIG. 11(C) displays information as to whether or not the reservation is a preliminary reservation. The display screen shown in FIG. 15 displays both the probability of success in waiting for a cancellation and information as to whether or not the reservation is a preliminary reservation. In this case, a user who is waiting for a cancellation can obtain more information to help decide whether or not to wait for a cancellation.

[0109] Additionally, the probability of success in waiting for a cancellation shown in FIG. 15 may be acquired together with the information on whether or not a reservation can be made, also shown in FIG. In other words, the probability of success in waiting for a cancellation shown in FIG. 15 may be acquired by taking into consideration information on whether or not the reservation is a preliminary reservation. More specifically, the probability of success in waiting for a cancellation shown in Figure 15 is obtained based on the reservation's past usage history and the reservation's status information. In addition to this usage history and status information, information on whether or not the reservation is a preliminary reservation may also be taken into consideration to obtain the probability of success in waiting for a cancellation. In addition, for portions where normal reservations have been made, the probability of success in waiting for a cancellation may be obtained by taking into consideration information on whether or not the reservation is a preliminary reservation.

[0110] FIG. 16 is a diagram showing a display screen in the case where the probability of success in waiting for a cancellation is acquired taking into consideration information on whether or not the reservation is preliminary. The display screen shown in Fig. 16 does not display information on whether a reservation is possible, that is, whether it is a preliminary reservation or not. Since the information on whether a reservation is possible or not is reflected in the success probability of waiting for a cancellation on this display screen, the information on whether a reservation is possible or not is not displayed.

[0111] In this display screen, the success probability in the time slot indicated by reference symbol 16A is 60%. More specifically, in the display screen shown in Fig. 15, it was 30%, but as a result of taking into consideration that this is a preliminary reservation, the success probability has been increased to 60%. The success rate for the time slot indicated by reference symbol 16B is 95%. More specifically, the success rate was 80% on the screen shown in Fig. 15, but taking into consideration that this is a preliminary reservation, the success rate has increased to 95%.

[0112] Also, in this example, the success probability in the time slots during which normal reservations are made (time slots indicated by reference characters 16C and 16D) is 0%. In this embodiment, as described above, during the time slots where regular reservations are made, waiting for a cancellation cannot be performed. Therefore, in this example, the fact that waiting for a cancellation cannot be performed is reflected in the success probability, and the success probability during the time slots where regular reservations are made is set to 0%.

[0113] The above-described functions may be disabled by the user operating a setting screen (not shown) displayed on the user terminal 4 or the like according to the user's preference. Specifically, the functions of displaying information on the possibility of success on the display screen and displaying information as to whether or not the reservation is a preliminary reservation may be made possible for the user to disable by operating a settings screen displayed on the user terminal 4.

[0114] In addition, in the above, booth 80 (space 2) has been described as an example of a reservation object, but the reservation object is not limited to booth 80, and may be in any form, whether tangible or intangible, as long as it can be used after reservation. An example of an intangible item is a service provided to a user. Examples of tangible things include things that are lent to users, such as rental cars, videos, CDs, DVDs, books, and ski equipment, which are lent to users for a set period of time. Other examples of reservation targets include tickets for concerts, sporting events, movies, etc., and seats on public transport such as trains. [Explanation of symbols]

[0115] 1...information processing system, 2...space, 4...user terminal, 5...space management server, 80...booth, 101...control unit, 111...CPU

Claims

1. an information processing system including a processor, the information processing system being configured to process a reservation object reserved by a reserver, The processor, Acquire information about the person who made the reservation for the reservation object and / or information about the reservation made by the person who made the reservation for the reservation object, Based on the content of the acquired information, possibility information is acquired which is information regarding the possibility that the reservation person will actually use the reservation object; The obtained possibility information is output to a terminal device of a person who is going to make a reservation for the reservation target. An information processing system, The processor, When the reservation person makes a reservation for the reservation target over a plurality of time periods, the possibility information is acquired for each of the time periods; When acquiring the possibility information for each time period, acquiring the possibility information based on information on the past usage status of the reservation object by the reservation person, the information being on whether or not the reservation object has been used by the reservation person; Or, The possibility information is acquired based on status information, which is information about the status of the person who made the reservation, and which is any one of location information of the person who made the reservation, information about the progress of the work of the person who made the reservation, and physical condition information of the person who made the reservation; Or, acquiring the possibility information based on attribute information of the reservation user, the information being about whether the reservation user is a corporate user or an individual user; Or, The possibility information is acquired based on information on the reservation date and time of the reservation target reserved by the reservationr, the information being whether the time period specified by the reservation date and time is early morning or late night, Or, acquiring the possibility information based on information about the weather at the reservation date and time of the reservation target reserved by the reservationr, the information indicating whether it will rain or not; Or, acquiring the possibility information based on information declared by the reserving person, which is information as to whether the reservation made by the reserving person for the reservation target is a preliminary reservation; Information processing system.

2. The processor, The information processing system according to claim 1 , further acquiring information on the possibility that a person other than the person who made the reservation can use the reservation object based on the acquired possibility information.

3. The processor, An information processing system as described in claim 1, wherein if the possibility identified by the acquired possibility information is smaller than a predetermined threshold, information is output to cancel the reservation of the reservation target made by the reservationr or to prompt the reservationr to cancel the reservation.

4. The information processing system according to claim 1 , wherein the reservationr can make a further reservation for the reservation object during a time period during which the reservationr makes a reservation for the reservation object, the further reservation being made by another reservationr.

5. The information processing system according to claim 4 , wherein the number of said other reservation users who can make said further reservation is limited.

6. An information processing system as described in claim 1, wherein if a further reservation for the reservation object is made during the time period in which the reservationr makes the reservation for the reservation object, and the further reservation has not been made by another reservationr, and if the further reservation has passed a predetermined time, the reservation for the reservation object by the reservationr cannot be canceled.

7. A program executed on a computer that processes a reservation object reserved by a reserver, A function for acquiring information about a person who has made a reservation for a reservation object and / or information about a reservation made by the person who has made the reservation for the reservation object; A function of acquiring possibility information, which is information about the possibility that the reservation person will actually use the reservation object, based on the content of the acquired information; a function of outputting the obtained possibility information to a terminal device of a person who is about to make a reservation for the reservation target; A program for causing the computer to realize the above, The function of acquiring the possibility information includes, when the reservation user has made a reservation for the reservation target across a plurality of time periods, acquiring the possibility information for each of the time periods; The function of acquiring the possibility information is When acquiring the possibility information for each time period, acquiring the possibility information based on information on the past usage status of the reservation object by the reservation person, the information being on whether or not the reservation object has been used by the reservation person; Or, The possibility information is acquired based on status information, which is information about the status of the person who made the reservation, and which is any one of location information of the person who made the reservation, information about the progress of the work of the person who made the reservation, and physical condition information of the person who made the reservation; Or, acquiring the possibility information based on attribute information of the reservation user, the information being about whether the reservation user is a corporate user or an individual user; Or, The possibility information is acquired based on information on the reservation date and time of the reservation target reserved by the reservationr, the information being whether the time period specified by the reservation date and time is early morning or late night, Or, acquiring the possibility information based on information about the weather at the reservation date and time of the reservation target reserved by the reservationr, the information indicating whether it will rain or not; Or, acquiring the possibility information based on information declared by the reserving person, which is information as to whether the reservation made by the reserving person for the reservation target is a preliminary reservation; program.

Images