JP7685178B2 - Information processing device, program, and program set - Google Patents

Description

The present invention relates to an information processing apparatus , a program , and a program set .

Mobile food trucks (hereafter referred to as kitchen cars) that set up shop in a certain space in front of a station or in an office district and sell boxed lunches and other items have been known for some time. In particular, the location of the space greatly affects the sales of a kitchen car, so kitchen car owners would like to set up shop in as good a location as possible, but finding a suitable sales location can be a source of worry due to factors such as permission to set up shop and having to balance it with competing cars.

On the other hand, for those who own and manage space, such as individual or corporate landowners or real estate management companies, there are some locations where it is possible to rent out their own space depending on the day of the week or time of day, and there is a demand for making effective use of vacant space to increase revenue.

In recent years, a vacant space matching system has become known for matching people who want to rent out space with people who want to rent out space. For example, according to the invention described in Patent Document 1, in order to effectively utilize vacant space, such as by renting out vacant space by the hour, an information providing server and a rental management server can match a lessor who wants to rent out vacant space by the hour with a lessee who wants to use the vacant space.

JP 2014-6741 A

In a matching system like the invention described in Patent Document 1, space owners usually publish rental information such as the location, hours, and rent of the space they wish to rent, and food truck owners can apply for the space after determining the conditions, the number of customers, and the amount of sales they can expect. Here, the rent for space is often set higher in locations that are generally considered to be good locations, such as office districts and apartment complexes where there is likely to be a high demand for lunch boxes at lunchtime. However, simply being in a good location may not necessarily result in the sales expected to justify the rent.

In other words, for food truck owners, the value of the rent is based on how much demand there is for the products in that space (and ultimately, whether there is sales), and in the past, it was sometimes difficult to estimate potential purchasing demand simply from the location information of the space published by the lessor.

The present invention has been proposed in light of the above points, and in one aspect aims to provide information for determining the value of a location for selecting a location for a mobile sales truck.

In order to solve the above problems, the information processing device of the present invention is an information processing device that manages rental and borrowing information regarding rental spaces in which a mobile sales store is set up, and has a first display control means that displays, on a first terminal of a mobile sales user , location information of the rental space and a display prompting the user to select the rental space in which the user wishes to request to set up a mobile sales store, a selection control means that causes the first terminal to select the rental space, a receiving means that receives information about the selected rental space from the first terminal, a counting means that counts the number of selections for each rental space when the information about the rental space is received, and a second display control means that displays information regarding the number of selections for each rental space on a second terminal of a mobile sales store owner.

According to an embodiment of the present invention, when selecting a location for a mobile sales truck, information can be provided to determine the value of the location.

1 is a diagram showing an example of the configuration of a rental space management system according to an embodiment of the present invention; FIG. 2 is a diagram illustrating an example of a hardware configuration of a management server according to the present embodiment. 3 is a diagram illustrating an example of the software configuration of the management server, the borrower terminal, and the user terminal according to the embodiment. FIG. 2 is a diagram illustrating an example of a data configuration of a DB according to the embodiment. FIG. 13 is a diagram showing an example 1 of a user screen on the borrower side according to the present embodiment. FIG. 13 is a diagram showing an example 2 of a user screen on the borrower side according to the present embodiment. FIG. 11 is a diagram showing an example 3 of a user screen on the borrower side according to the present embodiment. FIG. 2 is a diagram showing an example 1 of a usage screen on a user side according to the embodiment; FIG. 11 is a diagram showing an example 2 of a usage screen on the user side according to the embodiment; FIG. 11 is a diagram showing an example 3 of a usage screen on the user side according to the embodiment; FIG. 2 is a diagram illustrating an example of a data configuration of an invitation request DB according to the embodiment. FIG. 11 is a diagram showing an example 4 of a user screen on the borrower side according to the present embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS An embodiment of the present invention will be described in detail with reference to the drawings.
[Embodiment 1]
<System Configuration>
(Network Configuration)
Fig. 1 is a diagram showing an example of the configuration of a rental space management system according to the present embodiment. The rental space management system 100 in Fig. 1 includes a rental space management server 10, a lessor terminal 20 of a space lessor, a lessee terminal 30 of a space lessee who operates a kitchen car K, and a user terminal 40 of a general user (customer) who uses the kitchen car K, and is connected via a network 50.

The rental space management server (hereinafter simply referred to as the management server) 10 is a so-called vacant space rental matching server device that matches space rental between lessors who wish to rent space (land) and lessees who wish to rent the space and set up a food truck. The management server 10 publishes rental information (location information, time, rent, etc.) of the space to be rented that is received from the lessor terminal 20 of the space lessor, and also receives reservation applications for the rental of the desired food truck space from the lessee terminal 30 of the food truck owner.

The management server 10 also provides a kitchen car store map based on space rental information to general users (customers) who use the kitchen car K. By mapping kitchen car store information that is currently open or is scheduled to open in the rented store space displayed on the map, it is possible to use the user terminal 40 to search for kitchen car store information that indicates when, where, and what type of kitchen car is open.

Furthermore, the user can make a request to invite a food truck (also called a request to open a shop) to a space displayed on the map. When the management server 10 receives a request to invite a food truck to a space from the user terminal 40, it stores the invitation request information in association with the space.

The landlord terminal 20 is a computer terminal used by a landlord who wishes to rent out space to access the management server 10 to register rental information for the space and manage reservations. For example, a PC, smartphone, or tablet terminal having an operation unit for the landlord to perform various operations and a display unit for displaying reservation information is used.

The tenant terminal 30 is a computer terminal used by tenants who wish to rent space to access the management server 10 and search, refer to, apply for, and manage reservations for space rental information. For example, a PC, smartphone, or tablet terminal having an operation unit for the tenant to perform various operations and a display unit for displaying rental information and reservation information is used.

The user terminal 40 is a computer terminal that is used by a user (customer) who wants to use a kitchen car to access the management server 10 to search for and refer to the kitchen car store map and store information, and even to make an invitation request. For example, a PC, smartphone, or tablet terminal that has an operation unit for the user to perform various operations and a display unit for displaying the kitchen car store map and store information is used.

The network 50 is a communication network that may be wired or wireless. The network 50 may include, for example, the Internet, a public line network, a LAN, or Wi-Fi (registered trademark).

(Hardware configuration)
2 is a diagram showing an example of a hardware configuration of a management server according to this embodiment. The management server 10 includes a central processing unit (CPU) 11, a read only memory (ROM) 12, a random access memory (RAM) 13, a hard disk drive (HDD) 14, and a communication device 15.

The CPU 11 executes various programs and performs calculations. The ROM 12 stores programs required at startup. The RAM 13 is a working area for temporarily storing the processing by the CPU 11 and for storing data. The HDD 14 stores various data and programs. The communication device 15 communicates with other devices via the network 50.

Note that the lender terminal 20, the borrower terminal 30, and the user terminal 40 may be general PCs, smartphones, or tablet terminals, so an explanation of examples of the hardware configuration of these terminals will be omitted.

(Software configuration)
FIG. 3 is a diagram showing an example of the software configuration of the management server, the lessee terminal, and the user terminal according to this embodiment.

The management server 10 has a display control unit 101, a selection control unit 102, a transmission/reception unit 103, a counting unit 104, and a memory unit 109 as main functional units according to this embodiment. The display control unit 101 has a function of causing the user terminal 40 to display location information of the rental space, or a display prompting the user to select the rental space in which the user wishes to request to set up a mobile sales vehicle. The selection control unit 102 has a function of causing the user terminal 40 to select the rental space in which the user wishes to request to set up a mobile sales vehicle. The transmission/reception unit 103 has a function of receiving information on the selected rental space from the user terminal 40. The counting unit 104 has a function of counting the number of requests for each rental space when rental space information is received. The memory unit 109 has the function of storing a landlord/rented space information DB 109a, a tenant/kitchen car information DB 109b, a reservation management DB 109c, a user DB 109d, an invitation request DB 109e, and a map DB 109f.

The main functional units of the lessee terminal 30 according to this embodiment are a display unit 301, an operation unit 302, and a transmission/reception unit 303. The display unit 301 has a function of displaying rental information on the space available for the mobile sales vehicle and information on the number of requests for each space.

The user terminal 40 has a display unit 401, an operation unit 402, and a transmission/reception unit 403 as main functional units according to this embodiment. The display unit 401 has a function of displaying, on a map or the like, location information of a space where a mobile sales vehicle can be set up. The operation unit 402 has a function of allowing the user to select a space in which to request the mobile sales vehicle to be set up.

The above-mentioned functional units of the management server 10 are realized by computer programs executed on the hardware resources such as the CPU, ROM, and RAM of the computer that constitutes the server.

The above-mentioned functional units of the borrower terminal 30 are realized by a computer program executed on hardware resources such as the CPU, ROM, and RAM of the computer constituting the borrower terminal 30. Furthermore, the computer program is provided in a downloadable format, particularly as an application program for the borrower, and is installed on the borrower terminal 30.

The above-mentioned functional units of the user terminal 40 are realized by a computer program executed on the hardware resources such as the CPU, ROM, and RAM of the computer constituting the user terminal 40. Furthermore, the computer program is provided in a downloadable format, particularly as an application program for general users, and is installed in the user terminal 40.

The application program for borrowers and the application program for general users may be provided separately as a set of related applications from the same provider, or may be provided as a single application. In this case, it is possible to switch between available functions depending on whether the application user is a borrower or a general user.

Furthermore, these functional units may be interpreted as "means," "modules," "units," or "circuits," and these programs may be stored in a computer-readable storage medium.

(Various databases)
4 is a diagram showing an example of the data configuration of DBs according to this embodiment. The following shows examples of the data configuration of a lessor/rented space information DB 109a, a lessee/kitchen car information DB 109b, a reservation management DB 109c, a user DB 109d, and an invitation request DB 109e.

The landlord/rented space information DB 109a has data items such as "Landlord ID", "Landlord Name", "Rented Space ID", "Location", "Number of Vehicles", "Surrounding Information", and "Image", for example. Of these, "Number of Vehicles" indicates the number of food trucks that can be set up. Depending on the size of the space, some locations allow for one vehicle, while others allow for multiple vehicles. "Surrounding Information" is information that can be used as a reference when selecting a space for a food truck to set up, such as the location, characteristics, surrounding environment, and customer demographics of the space. "Image" is an image file that includes photos of the space, surrounding area, and a layout diagram of the location.

The tenant/kitchen car information DB 109b has data items such as "tenant ID," "tenant name (store name)," "vehicle number," "food genre," and "store URL," for example. "Lenant ID" can also be called the kitchen car ID. "Lenant name (store name)" is the store name of the kitchen car. "Vehicle number" is the vehicle number written on the license plate of the kitchen car. "Food genre" is the genre (category) of food products sold by the kitchen car. Note that "food genre" may be conceptually divided into a hierarchy such as genre 1 (Western food, Japanese food, bread, etc.) and genre 2 (pizza, yakitori/fried chicken, sweets). "Store URL" is the URL of the kitchen car store's website (HP), which contains an introduction to the kitchen car, menu, main opening areas, opening schedule such as location and time, various images and photos, etc.

The reservation management DB 109c has data items such as "rental space ID", "reservable date and time", "reservable time", "fee per time", "availability", "reservation ID", and "renter ID". The "rental space ID" is linked to the lessor/rental space information DB 109a, and each "rental space ID" has "reservable time", "fee per time", and "availability". When a reservation is made for a rental space, a "reservation ID" is issued and is linked to the "renter ID" that indicates the renter who made the reservation.

The user DB 109d has data items such as "user ID", "name", "address", "age", "gender", and "favorite food genre", for example. The "favorite food genre" is the genre (category) of food that the user likes. The "favorite food genre" may be conceptually divided into a hierarchy such as genre 1 (Western food, Japanese food, bread, etc.) and genre 2 (pizza, yakitori/fried chicken, sweets), but the user DB 109d may also store the data items in the above-mentioned renter/kitchen car information DB 109b.
Make sure to match the hierarchical level with the "food genre."

The invitation request DB 109e has data items such as "rented space ID", "number of invitation requests", and "number of invitation requests by food genre", for example. The "rented space ID" is linked to the lessor/rented space information DB 109a, that is, the "number of invitation requests" and "number of invitation requests by food genre" are linked and saved for each rented space. As described above, users can request a food truck to be invited to a space displayed on the map. Therefore, for example, when the management server 10 receives a request from a user to invite a food truck to a certain space, it counts up the "number of invitation requests" by 1. Also, if the food genre arbitrarily specified by the user at the time of the invitation request is pizza, or if the user's "favorite food genre" is pizza, it counts up "pizza" by 1 in the "number of invitation requests by food genre".

Note that if the user specifies multiple food genres at the time of the invitation request or the user has multiple "favorite food genres," for example, sweets and bread, then "sweets" in the "number of invitation requests by food genre" is counted up by one, and "bread" is counted up by one. At this time, the "number of invitation requests" may be counted up by one, or it may be counted up by two. Also, if the user does not specify a genre at the time of the invitation request or has no "favorite food genre," then the "number of invitation requests by food genre" may not be counted up, and only the "number of invitation requests" may be counted up by one.

Needless to say, the data configuration example of the DB according to this embodiment is just one example, and it is possible to freely design how each DB is constructed and in which DB the information is stored when saving and managing each piece of information. For example, the lessor/rented space information DB 109a may be divided into separate DBs such as a lessor DB and a rented space information DB, and the lessee/kitchen car information DB 109b may be divided into separate DBs such as a lessee DB and a kitchen car information DB. Also, for example, of the reservation management DB 109c, the "reservation available date and time", "reservation available time", and "fee per time" may be stored in the lessor/rented space information DB 109a. In particular, the map DB 109f may use a commercial map DB provided from outside.

<Usage screen example>
(Food truck owner)
First, a food truck owner who wants to rent a space accesses the management server 10 using the renter terminal 30 and logs in to the shop space renter site. Next, the food truck owner can input search conditions such as the current location, local address, or date and time to search for space rental information.

Figure 5 is a diagram showing an example of a lessee's usage screen 1 according to this embodiment. As shown in this figure, the example of usage screen 1 displays space rental information 71 in the form of a list 70. The space rental information 71 mainly displays the rental space ID, location, rent, surrounding information, number of invitation requests, images, etc. When the food truck owner finds any of the space rental information 71 that he or she would like to see in more detail, he or she presses "View details (reserve)" 72.

Figure 6 shows an example of a tenant's usage screen 2 according to this embodiment. When the above-mentioned "View details (reservation)" 72 is pressed, a details screen like that shown in this figure is displayed. As shown in this figure, in addition to rental information similar to the space rental information 71, the example of usage screen 2 displays "Invitation request information" 73 and "Availability information/fees/reservation" 74.

When displaying the "attraction request information" 73, the management server 10 refers to the attraction request DB 109e, obtains the information on the "number of attraction requests" and "number of attraction requests by food genre" corresponding to the rental space ID (e.g., 001-01), and displays it on the screen. Furthermore, the management server 10 highlights, among the "number of attraction requests by food genre," the number of attraction requests by food genre (e.g., "pizza") that corresponds to the "food genre" registered in the tenant/kitchen car information DB 109b of the currently logged-in tenant (e.g., K001's XX Kitchen) using a color, font, etc., so that the tenant can easily see it.

When displaying "Availability information/fees/reservations" 74, the management server 10 refers to the reservation management DB 109c, obtains the information on "Availability date and time," "Availability time," "Fees/one time," and "Availability" corresponding to the rental space ID (e.g., 001-01), and displays it on the screen.

As described above, the "attraction request information" 73 is information indicating the user's desire for a food truck to come to a space displayed on the map, so a space with a large number of "attraction requests" is located in a location where many users have expressed their desire for a food truck to come. Therefore, food truck owners can use the "attraction request information" 73 as an indicator to determine how much demand there is for products in that space.

In addition, since the "number of requests to attract food trucks by food genre" is information that indicates the type of food that users would like to see from food trucks, food truck owners can use it as an indicator to determine whether there is demand for the type of food products they are selling in that space, by comparing it with the type of food products they are selling. For example, in the case of the rental space shown in this diagram, a food truck that sells sweets and bread can expect demand for sweets in the rental space, while a food truck that sells yakitori and fried chicken can expect almost no demand for its products in the rental space.

In the display format of the list 70 in FIG. 5, the display "Number of invitation requests: 653/65" in the space rental information 71 indicates the "number of invitation requests" (e.g., 653) and the invitation request number column corresponding to the "food genre" registered for the currently logged-in tenant in the tenant/kitchen car information DB 109b (e.g., "pizza" 65).

When a food truck owner wishes to rent this space, they can reserve the space by checking the available date and time, fee, and availability in "Availability information/fees/reservation" 74, and then pressing "reserve" 75. Needless to say, the management server 10 may also be equipped with a settlement means for the borrower to pay the fee to the lessor during the reservation process.

In addition, instead of displaying and expressing the number of invitation requests, "attraction request information" 73 may be displayed and expressed as predetermined evaluation criteria information (e.g., A, B, C) corresponding to the number of invitation requests. For example, if the "number of invitation requests" exceeds 500, it is displayed as A, 499-300 as B, 300 or less as C, and 100 or less as no evaluation. For the "number of invitation requests by food genre", 100 or more as A, 99-50 as B, 49 or less as C, and 10 or less as no evaluation are displayed, and the evaluation is performed according to a predetermined threshold.

Figure 7 is a diagram showing a tenant-side usage screen example 3 according to this embodiment. The food truck owner can operate the map display 76, input search conditions such as the current location and local address, and search for space rental information on the actual map based on the map DB 109f. As shown in this figure, the usage screen example 3 shows space rental information 77 associated with the location of the space on the map. The space rental information 77 mainly shows the rental space ID, rent, and "number of invitation requests/number of invitation requests by food genre" 78. If the food truck owner wants to see more details about any of the space rental information 77, he or she can press the space location on the screen to transition to a detailed screen like that shown in Figure 6 above.

The "number of invitation requests/number of invitation requests by food genre" 78 for a space may be highlighted on the map in a color or font that makes it easy for renters to see depending on the number. When searching for rental information for a space on the map, the number of invitation requests or the number of invitation requests by food genre may be added to the search conditions, making it possible to extract and filter spaces that have a certain number of invitation requests and/or invitation requests by food genre or more.

As described above, when searching for a space to set up a food truck, the presence or absence and number of requests from users, which indicates whether there is demand for products in that space, can be used as a basis for deciding when to set up a food truck, thereby contributing to an increase in the food truck's sales.

(General user)
Next, a description will be given of a usage screen for a general user who uses a kitchen car. The user accesses the management server 10 using the user terminal 40 and logs in to the user site.

Figure 8 is a diagram showing a user-side usage screen example 1 according to this embodiment. The user can operate the map display 80a, input search conditions such as the current location and local address, and search for kitchen car store information on the actual map. As shown in this figure, the usage screen example 1 displays kitchen car store information 81 in association with the kitchen car store location on the map. The kitchen car store information 81 displays the store name, food genre, business hours, etc. If the user wants to see more detailed information about the kitchen car store information 81, the user can press the space on the screen to transition to the store URL of the kitchen car. In this way, the user can use the user terminal 40 to search for kitchen car store information that shows when, where, and what kind of kitchen car is open, such as what kind of lunch box kitchen car is coming to the vicinity of the company today.

Figure 9 is a diagram showing an example 2 of a user's usage screen according to this embodiment. The user operates the invitation request 80b, inputs search criteria such as the current location and local address, and displays the kitchen car's shop space on a map. Of the kitchen car's shop spaces displayed on the map, the user can submit a request to invite a kitchen car to the shop space located in the desired location, i.e., the shop space desired by the user.

To reduce the effort required to input search conditions, users may be asked to input and register location information for specific locations such as their home or workplace in advance, and a map of their living area including the registered location (e.g., a map of a specific distance range centered on the registered location) may be displayed by default. This is because users often want the food truck to come to the area near their home or workplace.

As shown in this figure, example usage screen 2 displays the message "Please select the space in which you would like to request to open (attract) a food truck.", the spaces 82 registered on the map by the lessor where food trucks can be opened, the current "number of requests to attract food trucks/number of requests to attract food trucks by food genre" 83 associated with the spaces, and an operation icon 84 for making an attraction request.

If a user wants the food truck to come to a desired space (e.g., a space near their home or workplace), they can select (e.g., press) the operation icon 84 of the space 83 to indicate their intention and make a request to the space. When the operation icon 84 is selected, the icon 85 of the requested food truck will, for example, change color or be marked with the message "Come," and at the same time the "Number of requests to come/Number of requests to come by food genre" 86 will be counted up.

Figure 10 is a diagram showing an example 3 of a user's usage screen according to this embodiment. When a user wishes to make a request to invite a food truck to a space displayed on a map, a request food genre selection field 87 is displayed by performing a specific operation. The user can make a request to invite a specific food genre to the space by selecting one or more food genres from the request food genre selection field 87.

When the user selects the operation icon 84, the user terminal 40 sends the invitation request information to the management server 10. The invitation request information includes the tenant ID and the rental space ID, and in some cases, information on the requested food genre. When the management server 10 receives the invitation request information from the user terminal 40, it associates the information with the rental space ID of the space in the invitation request DB 109e and performs counting processing of the "number of invitation requests" and the "number of invitation requests by food genre" as follows.

In the invitation request DB 109e, the "number of invitation requests" is simply counted up by one.
When a user specifies a food genre that they wish to request when making an invitation request (when the invitation request information includes information on the requested food genre) or when a food genre is registered in the user's "favorite food genre" in the user DB 109d (when there is a "food genre" corresponding to the borrower ID included in the invitation request information), the food genre corresponding to the user-specified or user-registered food genre among the "number of invitation requests by food genre" in the invitation request DB 109e is counted up by one. In this case, the "number of invitation requests" may also be counted up by another one.
The food genre that the user wishes to request may be more than one. In other words, if the user specifies more than one food genre that he/she wishes to request when making an invitation request, or if multiple food genres are registered in the "favorite food genre" of the user in the user DB 109d, the "number of invitation requests by food genre" in the invitation request DB 109e is counted up by one for each food genre that corresponds to all food genres specified or registered by the user. In this case, the "number of invitation requests" may also be counted up by one or more.

As described above, by making an invitation request to a food truck that serves a user's favorite food, the food truck can encourage the user to open a store near the customer's living area. On the other hand, the invitation request made by the user is used by the food truck to determine the space to open a store, so that the user's invitation to open a store can realize or increase the possibility of opening a food truck in the desired space.

[Embodiment 2]
In the above-described embodiment, by associating invitation request information (number of invitation requests/number of invitation requests by food genre) from general users who are kitchen car users with rental space where kitchen car can be set up, it is possible to use this as an indicator for determining how much demand there is for kitchen car to set up in that space.

In this embodiment, it is also possible to attach invitation request information naming a specific food truck itself to the food truck stall space displayed on the map. In other words, invitation request information (number of invitation requests) that specifically names a specific food truck or store name that general users would like to visit is associated with the rental space where a food truck can set up shop.

Specifically, for example, a user uses a user terminal 40 to refer to the website of a specific food truck store, and operates an invitation request operation icon or the like provided on the screen, and then specifies the space by selecting a space located at the user's desired store location from a map or by inputting a rental space ID. Alternatively, the user selects the user's desired space, for example, from a map, and then searches for and inputs the store name of a specific food truck to specify it by name. In other words, it is sufficient to associate a "rental space ID" for identifying the user's desired space with a "renter ID" for identifying a specific food truck.

Figure 11 is a diagram showing an example of the data configuration of the invitation request DB according to this embodiment. The invitation request DB 109e according to this embodiment has data items such as "rental space ID", "renter ID", and "number of invitation requests" as examples. The "rental space ID" is saved in association with the "number of invitation requests" for each "renter ID".

Figure 12 is a diagram showing an example 4 of a tenant's usage screen according to this embodiment. As shown in this figure, the example 4 of the usage screen displays space rental information 77 in association with the location of the space on a map. The space rental information 77 mainly displays the rental space ID, rent, and the "number of invitation requests" 90 corresponding to the currently logged-in tenant (kitchen car owner), as the space rental information.

Here, the "number of invitation requests" 90 in this embodiment indicates the number of invitation requests that name a specific food truck or store name. When displaying the space rental information 77, the management server 10 refers to the invitation request DB 109e shown in FIG. 11, and displays the "number of invitation requests" associated with the login ID (e.g., K001) from among the "number of invitation requests" associated with the "rental space ID" of the space as the "number of invitation requests" 90.

As described above, the "number of requests to attract" 90 is information indicating the user's desire for a specific food truck to come to a space displayed on the map, so a space with a high "number of requests to attract" from the perspective of a logged-in food truck owner is a location where many users have expressed their desire for your food truck to come. In other words, the food truck owner can use the "number of requests to attract" 90 as an indicator to determine how much demand there is for designated purchases of their product in that space.

The following points are also mentioned:
・The space does not have to be a "rented" space at the time of the invitation request. By making an invitation request to any space on the map (such as an empty space in the user's own apartment), the owner or manager of the arbitrary space can clearly recognize that there is a need for a food truck to operate in that space, and even if the space is currently unused or being used for other purposes, it can be encouraged to rent it out as a rental space in the near future. This will increase the supply of rental space, leading to an increase in the options for food trucks to operate their stores.
-In this embodiment, depending on the position of the entity handling the space, it can be called a rented space or a borrowed space from the perspective of the lessor and lessee, and a store space from the perspective of the lessee (kitchen car owner) and general users.
The rental space management system according to this embodiment can be called a vehicle sales store invitation system from the user's point of view, and a vehicle sales store location (rental space) evaluation system from the lessor and lessee's point of view.
The system of this embodiment can be applied not only to mobile food trucks such as food trucks, but also to management systems for temporary mobile food stalls, such as festival stalls, in part of the space at event venues, parks, and public facilities.

<Summary>
In the past, if a general user (customer) had a favorite restaurant, for example, they had to go to the store themselves. However, by focusing on the mobility of kitchen cars as in this embodiment, the user (customer) can make an invitation request to a kitchen car that serves their favorite food, and the kitchen car can work to attract a store to open near the customer's living area.

Furthermore, finding a space to set up shop is a major headache for food truck operators, so by using the presence and number of requests from users, which indicates whether there is demand for products in that space, as a basis for deciding on a space to set up shop, the system can contribute to increasing sales for food trucks.

In addition, for those who own, manage, and rent out the space, they can expect higher rents by adding value to the space by showing that it is a space that users have requested to be used, rather than simply determining the rent based on the land price of the space.

Although the present invention has been described by showing specific examples according to preferred embodiments of the present invention, it is clear that various modifications and changes can be made to these examples without departing from the broad spirit and scope of the present invention as defined in the claims. In other words, the details of the examples and the accompanying drawings should not be construed as limiting the present invention.

10 Rental space management server 20 Lessor terminal 30 Lessee terminal 40 User terminal 40
50 Network 100 Rental space management system 101 Display control unit 102 Selection control unit 103 Transmission/reception unit 104 Count unit 109 Memory unit 301 Display unit 302 Operation unit 303 Transmission/reception unit 401 Display unit 402 Operation unit 403 Transmission/reception unit

Claims (5)

An information processing device that manages rental information regarding rental space for a mobile store ,
a first display control means for displaying, on a first terminal of the mobile sales user, location information of the rental space and a display for prompting the user to select a rental space in which the user wishes to request to set up a mobile sales store ;
A selection control means for causing the first terminal to select a rental space;
A receiving means for receiving information on the selected rental space from the first terminal;
a counting means for counting the number of selections for each rental space when the rental space information is received;
a second display control means for causing a second terminal of the mobile sales booth owner to display information regarding the number of times for each rental space;
13. An information processing device comprising: An acquisition means for acquiring information on the genre preferences of a mobile sales user who has selected a rental space;
having
the counting means, when receiving the information on the rental space, counts the number of times for each rental space and for each genre corresponding to the preference genre of the mobile sales user;
the second display control means displays information regarding the number of times for each rental space and for each genre;
2. The information processing apparatus according to claim 1, an input means for inputting location information of at least one of a user's home and a user's workplace into the first terminal;
having
The first display control means displays location information of rental spaces located within a predetermined distance of the input location information;
2. The information processing apparatus according to claim 1, On the computer,
a first display means for displaying location information of a space available for the mobile store and a display for prompting the user to select a space in which the user wishes to request the mobile store to open;
A selection operation means for selecting a store space;
a second display means for displaying rental information of shop spaces available for the mobile store and information regarding the number of selections for each shop space;
A program that makes it work. On the mobile sales user's computer,
a first display means for displaying location information of a space available for the mobile store and a display for prompting the user to select a space in which the user wishes to request the mobile store to open;
A first program that functions as a selection operation means for selecting a store space;
On the mobile vendor's computer,
a second program that functions as a second display means for displaying rental information of store spaces available for the mobile store and information regarding the number of selections for each store space;
A set of programs each offered as a separate program.