JP7617825B2 - Management system, management method, and program for boarding type mobile body - Google Patents

Description

The present invention relates to a management system, a management method, and a program for a vehicle-mounted vehicle.

Conventionally, there are systems that provide services during periods when a passenger-type mobile object such as an autonomous vehicle is not in use based on a pre-set schedule (see, for example, Patent Document 1).

International Publication No. 2019/163186

However, if no schedule is set, even if the boarding type vehicle is not in use at certain times, it is difficult to effectively utilize the vehicle during these times.

The present invention was made in consideration of these circumstances, and one of its objectives is to provide a management system, management method, and program for a boarding type mobile object that can effectively utilize the boarding type mobile object when it is not in use.

The management system, management method, and program for a boarding type vehicle according to the present invention employ the following configuration.
(1): A management system for a boarded mobile body according to one embodiment of the present invention is a management system for a boarded mobile body that controls a boarded mobile body in which a user boards, and is equipped with an estimation unit that estimates a non-use time for which the user will not be using the boarded mobile body based on the location of the user when he or she dismounts from the boarded mobile body, and a decision unit that decides the operation of the boarded mobile body based on the estimated non-use time.

(2): In the aspect of (1) above, the decision unit decides to put the operation of the boarding type mobile body on standby if the non-use time is equal to or less than a reference time.

(3): In the above aspect (1) or (2), when the non-use time exceeds a reference time, the determination unit determines the operation of the boarding type mobile body to be an operation based on an execution list that the boarding type mobile body can execute for each non-use time.

(4): In the aspect of (3) above, the motion is a motion for shopping, and the determination unit determines the motion of the boarding type moving body to be a motion in which another device other than the own device executes the motion on behalf of the own device.
It is something.

(5): In any of the above aspects (1) to (4), the decision unit decides the operation of the boarding type mobile body based further on the remaining charge of the driving power of the boarding type mobile body.

(6): In the aspect of (5) above, the decision unit decides that the operation of the ride-on type mobile body is to travel around a specified area when the remaining charge exceeds a specified value.

(7): A method for managing a boarding type mobile object according to one aspect of the present invention is a method for managing a boarding type mobile object in which a computer estimates a non-use time during which a user will not be using the boarding type mobile object based on the location of the user when the user dismounts from the boarding type mobile object, and determines the operation of the boarding type mobile object based on the estimated non-use time.

(8): A program according to one aspect of the present invention is a program that causes a computer to estimate a non-use time during which a user will not be using a boarding type mobile object, based on the location of the user when the user dismounts from the boarding type mobile object, and determines the operation of the boarding type mobile object based on the estimated non-use time.

According to aspects (1) to (8), the ride-on type mobile body can be effectively utilized when not in use.

FIG. 1 is an explanatory diagram illustrating an overview of a mobile object management system according to an embodiment. 1 is a configuration diagram showing an example of a boarding type vehicle 100. FIG. 1 is a perspective view showing the internal structure of the boarding type vehicle 100. FIG. FIG. 1 is a perspective view of an omnidirectional wheel 112. 1A and 1B are diagrams for explaining the configuration and operation of an omnidirectional wheel 112 of a boarding type vehicle 100. FIG. 2 is a diagram showing an example of a configuration of a terminal device 200. FIG. 4 is a diagram illustrating an example of a configuration of a management server 400. FIG. 4 is a diagram showing an example of the contents of a reservation management list 451. 13 is a diagram showing an example of the contents of a lending management list 452. FIG. FIG. 13 is a diagram showing an example of the contents of an execution list 453. 4 is a flowchart showing an example of processing by a control device 150. 13 is a flowchart showing an example of a process of dismount control. 10 is a flowchart showing an example of a process of the server control device 420. 13 is a flowchart showing an example of a process for determining the execution content in a determination unit 425. 13 is a flowchart showing an example of a lending judgment process in a lending judgment unit 426.

The following describes an embodiment of the management system, management method, and program for a boarding type mobile object of the present invention with reference to the drawings.

The management system for boarding type mobile objects (hereinafter, mobile object management system) comprises a boarding type mobile object, a terminal device, and a management server. The boarding type mobile object is installed, for example, in amusement facilities such as amusement parks and theme parks. The boarding type mobile object matches the vehicle with a user who owns a terminal device, for example, based on an electrical signal transmitted by the owned terminal device, and grants the matched user a right of use. The boarding type mobile object is rented out to the user who has been granted the right of use. The management server communicates with the boarding type mobile object and the terminal device, and manages the boarding type mobile object in the amusement facility.

The boarding type mobile object may be one that a user has brought into an amusement facility. The user may have exclusive rights to use the boarding type mobile object brought into an amusement facility, or the boarding type mobile object may be one that can be set up for a person other than the user. In the following description, of two users, the user who uses the boarding type mobile object 100 first is called the first user, and the user (other person) who uses the boarding type mobile object 100 after the first user is called the second user. When there is no distinction between the first user and the second user, they are collectively referred to as users.

FIG. 1 is an explanatory diagram for explaining an overview of a mobile object management system 1 according to an embodiment. The mobile object management system 1 includes, for example, a boarding type mobile object 100, a terminal device 200, and a management server 400. A plurality of boarding type mobile objects 100 are deployed in an amusement facility P. Boarding type mobile objects 100 for which a right of use has not been set are, for example, stored in a parking pool PP provided near the entrance P-IN of the amusement facility P, or travel around the grounds of the amusement facility P. Boarding type mobile objects 100 for which a right of use has been set run in response to the operation of a user U who has boarded the boarding type mobile object 100, or wait for the user U to reboard when the user U disembarks from the boarding type mobile object 100. The terminal device 200 is, for example, owned by the user U.

The management server 400 is installed within the amusement facility P. The management server 400 manages multiple boarding type mobile bodies 100 within the amusement facility P. The management server 400 recognizes the positions of the boarding type mobile bodies 100 within the amusement facility P. The management server 400 manages the movement of boarding type mobile bodies 100 for which the user U has not been granted usage rights.

The boarding type mobile body 100 includes a control device that matches the user U with the boarding type mobile body 100, for example, by operating a terminal device 200 held by the user U. The user U acquires the right to use the boarding type mobile body 100 to be used within the amusement facility P by operating the terminal device 200. For example, when entering the amusement facility P, the user U may acquire the right to use the boarding type mobile body 100 located near the entrance P-IN, or may acquire the right to use the boarding type mobile body 100 to travel around the amusement facility P. The user U who has been granted the right to use the boarding type mobile body 100 may, for example, board the boarding type mobile body 100 to travel, or park the boarding type mobile body 100 near the on-site facility B, which is an installed facility within the amusement facility P such as an attraction or restaurant, and use the on-site facility B.

Figure 2 is a configuration diagram showing an example of a boarding type mobile body 100. The boarding type mobile body 100 includes, for example, a body 110, a communication device 120, a vehicle position detection device 130, a sensor 140, a control device 150, and a battery 135. The body 110 includes, for example, a cover panel 111, omnidirectional wheels 112, a seat 113, a step 114, and an alarm device 115.

Figure 3 is a perspective view showing the internal structure of the boarding type mobile body 100. In Figure 3, the width direction of the boarding type mobile body 100 is called the x direction, the front-to-rear direction is called the y direction, and the up-down direction is called the z direction. The front direction of the boarding type mobile body 100 is the positive direction of the y axis (the direction from the back of the paper to the front of the paper, hereafter referred to as the +y axis direction), and the rear direction is the negative direction of the y axis (the direction from the front of the paper to the back of the paper, hereafter referred to as the -y axis direction).

The cover panel 111 is made of resin, for example. Omnidirectional wheels 112 are provided on the lower inside of the cover panel 111. FIG. 4 is a perspective view of the omnidirectional wheels 112. The omnidirectional wheels 112 include large diameter wheels 112A, small diameter wheels 112B, turning wheels 112C, a first motor MT1, a second motor MT2, and a third motor MT3. The large diameter wheels 112A are rotatable around the x-axis. The large diameter wheels 112A are rotated by the first motor MT1.

The small diameter wheel 112B is a wheel that can rotate around an axis perpendicular to a radial line in the widthwise central cross section of the large diameter wheel 112A. The omnidirectional wheel 112 is equipped with multiple small diameter wheels 112B. The multiple small diameter wheels 112B are arranged at approximately equal intervals along the circumferential direction of the large diameter wheel 112A. The multiple small diameter wheels 112B are rotated in unison by the second motor MT2.

The swivel wheel 112C is a wheel that can rotate around the y-axis. The swivel wheel 112C has a smaller diameter than the large diameter wheel 112A. The swivel wheel 112C is rotated by the third motor MT3. The omnidirectional wheel 112 moves the ride-on mobile body 100 by rotating at least one of the large diameter wheel 112A, the small diameter wheel 112B, and the swivel wheel 112C. The operation of the omnidirectional wheel 112 will be described later.

The seat 113 is attached above the cover panel 111. The seat 113 is a member on which the user U riding on the boarding type vehicle 100 sits. The step 114 is attached to the front lower part of the cover panel 111. The step 114 is a member on which the user U places his/her legs. The step 114 is a variable step whose width and height can be adjusted.

The alarm device 115 includes, for example, a lamp and a speaker. The alarm device 115 is operated under the control of the control device 150. The lamp is attached to the periphery of the aircraft 110, and outputs a light alarm around the aircraft 110 by emitting light such as by lighting up or blinking. The speaker is provided on the outside of the aircraft 110, and outputs an alarm sound around the aircraft 110.

Next, the configuration and operation of the omnidirectional wheel 112 of the boarding type mobile body 100 will be described. FIG. 5 is a diagram for explaining the configuration and operation of the omnidirectional wheel 112 of the boarding type mobile body 100. The omnidirectional wheel 112 is a wheel that enables the vehicle to immediately move forward in any direction (all directions of 360 degrees) from its current position without making a preparatory movement such as turning. The omnidirectional wheel 112, for example, comprises a large diameter wheel 112A as the front wheel and a turning wheel 112C as the rear wheel, and comprises multiple small diameter wheels 112B on the ground contact portion (radial edge portion) of the large diameter wheel 112A of the front wheel.

The large diameter wheel 112A is a wheel that mainly realizes linear movement in the forward and backward directions. The small diameter wheel 112B is a wheel that mainly realizes lateral movement on the spot by rotating around the rotation direction (circumferential direction) of the large diameter wheel 112A. On the other hand, the rear turning wheel 112C is a wheel that has a smaller diameter than the large diameter wheel 112A and mainly realizes turning movement by rotating around a rotation axis perpendicular to the rotation axis of the large diameter wheel 112A. The omnidirectional wheel 112 is equipped with a motor (not shown) that can independently control the rotation of the large diameter wheel 112A, the small diameter wheel 112B, and the turning wheel 112C. With this configuration, the omnidirectional wheel 112 can move in various directions such as straight sideways and diagonally by utilizing the difference in the lateral movement speed of the front and rear wheels in addition to moving forward and backward, and can also realize agile movements such as turning and turning on the spot.

Here, the forward direction of the ride-on vehicle 100 is the positive direction of the y axis in FIG. 3 (the direction from the back of the page to the front of the page, hereafter referred to as the +y axis direction), and the backward direction is the negative direction of the y axis (the direction from the front of the page to the back of the page, hereafter referred to as the -y axis direction). For example, as shown in operation example M1 (forward/reverse) in FIG. 5, the omnidirectional wheel 112 moves forward by rotating the large diameter wheel 112A in the direction of arrow A1, and moves backward by rotating it in the direction of arrow A2.

As shown in the operation example M2 (left-right movement) of FIG. 5, the omnidirectional wheel 112 can move leftward on the spot without changing its direction by rotating the small diameter wheel 112B in the direction of the arrow A3. In this case, the turning wheel 112C may be configured to rotate naturally in the direction of the arrow A4 in response to the left-right movement, or may be controlled to rotate in the direction of the arrow A4 in response to the amount of rotation of the small diameter wheel 112B. The omnidirectional wheel 112 can move rightward on the spot without changing its direction by rotating the small diameter wheel 112B in the opposite direction to the arrow A3. The leftward direction here is the leftward direction in FIG. 3, which corresponds to the negative direction of the x-axis (-x-axis direction), and the rightward direction is the rightward direction in FIG. 3, which corresponds to the positive direction of the x-axis (+x-axis direction). The multiple small diameter wheels 112B may be configured so that all the wheels rotate simultaneously, or only the wheels on the ground may rotate.

As shown in operation example M3 (turning on the spot) in Figure 5, the omnidirectional wheel 112 can turn on the spot in the direction of arrow A6 around the ground contact point P1 of the large diameter wheel 112A by rotating the turning wheel 112C in the direction of arrow A5, and can turn on the spot in the direction opposite to arrow A6 by rotating it in the opposite direction to arrow A5.

As shown in operation example M4 (turning) in FIG. 5, the omnidirectional wheel 112 can move forward while turning in the direction of arrow A9 by rotating the large diameter wheel 112A in the direction of arrow A7 and the turning wheel 112C in the direction of arrow A8 (turning). The omnidirectional wheel 112 can also move backward while turning in the direction opposite to arrow A9 by rotating the large diameter wheel 112A in the direction opposite to arrow A7 and rotating the turning wheel 112C in the direction of arrow A8. In this example, the omnidirectional wheel 112 can move forward or backward with the turning center on the right side by rotating the turning wheel 112C in the direction opposite to arrow A8.

The method of realizing the omnidirectional wheels 112 is not limited to the method shown in FIG. 5. The omnidirectional wheels 112 may be realized by any existing technology. The boarding type mobile body 100 may be equipped with one omnidirectional wheel 112 or multiple omnidirectional wheels 112. Furthermore, the boarding type mobile body 100 may be equipped with normal wheels as auxiliary wheels in addition to the omnidirectional wheels 112.

Returning to FIG. 2, the communication device 120 performs wireless communication based on, for example, Wi-Fi, DSRC, Bluetooth (registered trademark), or other communication standards. The communication device 120 receives electrical signals transmitted by the terminal device 200 and the management server 400, and outputs them to the control device 150. The communication device 120 transmits electrical signals output by the control device 150 to the terminal device 200 and the management server 400. In addition to the communication device 120, the communication device 120 may be provided with a near field communication function for performing near field communication (NFC) with the terminal device 200.

The vehicle position detection device 130 detects the position of the vehicle, which is the boarding type mobile body 100. The vehicle position detection device 130 is, for example, a GNSS (Global Navigation Satellite System) device. The vehicle position detection device 130 outputs a vehicle position signal indicating the detected position of the vehicle (boarding type mobile body 100) to the communication device 120. The communication device 120 transmits the output vehicle position signal to the terminal device 200 and management server 400 owned by the user U for whom the usage right has been set.

The battery 135 stores driving power for driving the boarding type vehicle 100. The battery 135 supplies the stored power to the motor of the omnidirectional wheel 112. The battery 135 can be charged by a charging device provided outside the boarding type vehicle 100. The battery 135 can also be charged with electricity regenerated by the motor of the omnidirectional wheel 112.

The sensor 140 includes, for example, a seating sensor 141, a surrounding sensor 142, an acceleration sensor 143, an angular velocity sensor 144, and a charge remaining amount sensor 145. The seating sensor 141 detects whether or not a passenger is seated in the seat 113. The seating sensor 141 outputs a seating signal indicating the passenger's seating state to the control device 150.

The surrounding sensor 142 is a sensor that detects objects in the vicinity of the boarding type mobile body 100. The surrounding sensor 142 detects, for example, the distance between the detected object and the boarding type mobile body 100. The surrounding sensor 142 outputs a surrounding object signal related to the distance between the detected object and the boarding type mobile body 100 to the control device 150. The surrounding sensor 142 may be, for example, an ultrasonic sensor using ultrasonic waves as a medium, an optical sensor using light as a medium, or an image sensor that captures an image of the vicinity of the boarding type mobile body 100.

The acceleration sensor 143 is attached to one or more arbitrary locations on the airframe 110 or the seat 113. The acceleration sensor 143 detects the acceleration acting on the attachment location and outputs the result to the control device 150. Similarly, the angular velocity sensor 144 is attached to one or more arbitrary locations on the airframe 110 or the seat 113. The angular velocity sensor 144 detects the angular velocity acting on the attachment location and outputs the result to the control device 150.

The charge remaining amount sensor 145 detects the charge remaining amount in the battery 135, which stores driving power and supplies the stored power to the motor of the omnidirectional wheel 112. The charge remaining amount sensor 145 outputs a charge remaining amount signal indicating the detected charge remaining amount to the control device 150. The control device 150 outputs the charge remaining amount signal to the communication device 120. The communication device 120 transmits the charge remaining amount signal output by the control device 150 to the management server 400.

The control device 150 includes, for example, an authentication processing unit 160, a command generation unit 170, a motor control unit 180, and an alarm control unit 190. The authentication processing unit 160 includes, for example, an authentication unit 161, a release unit 162, and an adjustment unit 163. The command generation unit 170 includes, for example, a determination unit 171, a detection unit 172, a generation unit 173, a center of gravity estimation unit 174, and a balance control unit 175.

These components are realized, for example, by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI (Large Scale Integration), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), or a GPU (Graphics Processing Unit), or may be realized by a combination of software and hardware. The program may be stored in advance in a storage device (a storage device with a non-transient storage medium) such as an HDD (Hard Disk Drive) or flash memory, or may be stored in a removable storage medium (non-transient storage medium) such as a DVD or CD-ROM, and installed in the storage device by attaching the storage medium to a drive device. The storage device stores the mobile object ID assigned to the vehicle.

Before explaining the functions of each part of the control device 150, we will explain the functions of the terminal device 200.

Figure 6 is a configuration diagram showing an example of a terminal device 200. The terminal device 200 is, for example, a mobile terminal such as a smartphone or tablet owned by the user U. In the terminal device 200, an application program for using a service using the boarding type mobile object 100, or a browser, etc. is started, and supports the service described below. In the following explanation, it is assumed that the terminal device 200 is a smartphone and an application program (mobile object rental app) is started. The terminal device 200 has a memory unit and stores a user ID corresponding to the application program.

The terminal device 200 includes, for example, a touch panel 210, a terminal communication unit 220, a terminal control unit 230, and a terminal position detection unit 240. The touch panel 210 displays, for example, a GUI (Graphical User Interface) image and accepts input operations such as a user U touching the GUI image with his or her finger. The touch panel 210 outputs an electrical signal corresponding to the accepted input operation to the terminal control unit 230.

For example, when the user U executes an operation to request a reservation of the boarding type mobile body 100, the touch panel 210 outputs a reservation request signal to the terminal control unit 230 to request a reservation of the boarding type mobile body 100. The reservation request signal includes information such as the start time of use, the duration of use, the start location of use, the number of people making a reservation (the number of people accompanying), the specified requirements, and the mode of use. The information on the start time of use, the duration of use, and the start location of use are all information regarding the time the user wishes to use the vehicle. The specified requirements are, for example, requirements for requesting a boarding type mobile body 100 by specifying the type. The types of the boarding type mobile body 100 include, for example, types such as for adults and children, the number of passengers when the number of passengers varies, and the type of characters drawn on the boarding type mobile body 100. For example, when the user U executes an operation to request the dispatch of the boarding type mobile body 100, the touch panel 210 of the terminal device 200 outputs a dispatch request signal to the terminal communication unit 220 to request the dispatch of the boarding type mobile body 100. The usage status includes information on whether the vehicle was used for a test drive or for normal use.

For example, when the user U performs an operation requesting the setting of the usage rights of the boarding type mobile body 100, the touch panel 210 outputs a usage rights setting request signal requesting the setting of the usage rights to the terminal control unit 230. For example, when the user U for whom the usage rights have been set performs an operation requesting identity verification when moving away from the boarding type mobile body 100 and then approaching it again, the touch panel 210 outputs an identity verification request signal requesting identity verification to the terminal control unit 230.

The terminal control unit 230 adds the user ID stored in the memory unit to the reservation request signal, vehicle dispatch request signal, usage right setting request signal, and identity verification request signal output by the touch panel 210, and outputs them to the terminal communication unit 220.

The terminal communication unit 220 performs wireless communication based on, for example, Wi-Fi, DSRC, Bluetooth (registered trademark), or other communication standards. The terminal communication unit 220 transmits a usage right setting request signal and an identity verification request signal output by the terminal control unit 230 to the boarding type mobile body 100, and transmits a reservation request signal and a vehicle dispatch request signal to the management server 400. The terminal communication unit 220 receives electrical signals transmitted by the boarding type mobile body 100 and the management server 400, for example, a vehicle position signal transmitted by the boarding type mobile body 100, and outputs the electrical signals to the terminal control unit 230 specified by the authentication unit 161.

The terminal control unit 230 executes display control of the touch panel 210 in response to the electrical signal output by the terminal communication unit 220. For example, the terminal control unit 230 identifies the position of the boarding type mobile body 100 matched with the user U based on the vehicle position signal transmitted by the boarding type mobile body 100, and displays an image of the boarding type mobile body 100 matched with the user U together with an AR (Augmented Reality) image on the touch panel 210.

The AR image is, for example, an image that displays the boarding type mobile body 100 in a decorative manner. The memory unit of the terminal device 200 stores the shape (appearance) of the boarding type mobile body 100, and the terminal control unit 230 may adjust the position of the boarding type mobile body based on the vehicle position signal transmitted by the boarding type mobile body 100 and the shape of the boarding type mobile body 100 stored in the memory unit.

The terminal position detection unit 240 detects the position of the terminal device 200. The terminal position detection unit 240 is, for example, a GNSS device. The position of the terminal device 200 detected by the terminal position detection unit 240 indicates the position of the user U who carries the terminal device 200, so the terminal position detection unit 240 detects the position of the user U. The terminal position detection unit 240 outputs a user position signal indicating the detected user position to the terminal communication unit 220. The terminal communication unit 220 transmits the user position signal to the management server 400.

The functions of each part of the control device 150 of the boarding type mobile body 100 will be explained again below. The command generation unit 170 of the control device 150 mainly generates movement commands when the user U is not boarding (has disembarked) the boarding type mobile body 100. The authentication unit 161 acquires the usage right setting request signal transmitted by the terminal device 200 and output by the communication device 120, and matches the user ID attached to the usage right setting request signal with the mobile body ID.

The authentication unit 161 matches the user U with the boarding type mobile body 100 by matching the user ID with the mobile body ID. The authentication unit 161 sets usage rights for the user U who has the user ID that is matched with the mobile body ID. The authentication unit 161 designates the terminal device 200 owned by the user who has set the usage rights as the terminal device 200 to which the communication device 120 will transmit a GNSS signal. The authentication unit 161 outputs to the communication device 120 the matched user ID and a matching signal including the user ID.

When the authentication unit 161 receives a reservation signal transmitted by the management server 400, it limits the users U for whom the right of use is to be set to those users U who possess the terminal device 200 that transmitted the reservation request signal to the management server 400. When a user ID is transmitted by the terminal device 200 of the user U for whom the right of use is to be set, the authentication unit 161 matches the user ID with the mobile ID.

The release unit 162 measures the elapsed time after the user U leaves the boarding type mobile body 100. After a predetermined time has elapsed since the user U left the boarding type mobile body 100, the release unit 162 releases the user's right to use the boarding type mobile body 100 as the release condition is satisfied. The predetermined time may be constant or may vary depending on specific conditions. The specific conditions may be, for example, the stopping position of the boarding type mobile body 100, the time period, the number of people who visited the amusement facility P together with the user U, or human relationships such as family and friends. The release condition may be other conditions. For example, the release condition may be that the user U performs an operation indicating an intention to release the right to use and the release unit 162 acquires a signal corresponding to the operation.

The adjustment unit 163 receives a usage right setting request signal (hereinafter, other person request signal) transmitted by the terminal device 200 of a user (hereinafter, other person) other than the user who set the usage right, and when the other person requests the usage right of the boarding type mobile body 100, determines whether the usage right has been set for the user U. When the usage right has not been set for the user U, the adjustment unit 163 sets the usage right of the boarding type mobile body 100 for the other person.

The determination unit 171 in the command generation unit 170 determines whether the user U is seated or not based on the seating signal output by the seating sensor 141. After the user U sits on the seat 113 once, the determination unit 171 determines whether the user U has left the boarding type mobile body 100 or not. For example, if the user U sits on the seat 113 once and then leaves, the determination unit 171 determines that the user U has left the boarding type mobile body 100. When the user U leaves the boarding type mobile body 100, the command generation unit 170 outputs a usage interruption signal to the communication device 120. The communication device 120 transmits the output usage interruption signal to the management server 400.

The detection unit 172 and the generation unit 173 in the command generation unit 170 function when the user U is not on board the boarding type mobile body 100. The detection unit 172 detects the intention of another person other than the user U to use the boarding type mobile body 100. The detection unit 172 detects the presence or absence of an object approaching the boarding type mobile body 100 around the boarding type mobile body 100 based on, for example, a peripheral object signal output by the peripheral sensor 142. The detection unit 172 determines whether or not the communication device 120 has received an other person request signal to which the other person's user ID is added.

The detection unit 172 detects the intention of another person other than the user U with respect to the boarding type mobile body 100, for example, when an object approaches the boarding type mobile body 100 and the communication device 120 receives a request signal from another person. The detection unit 172 may detect the intention of another person other than the user U with respect to the boarding type mobile body 100 under other conditions. For example, the detection unit 172 may detect the intention of another person with respect to the boarding type mobile body 100 when an object approaches the boarding type mobile body 100, or may detect the intention of another person with further added conditions.

When the determination unit 171 determines that the user U has left the boarding type mobile body 100 and the detection unit 172 detects another person's intention to use the boarding type mobile body 100, the generation unit 173 generates an action command for the boarding type mobile body 100 based on the usage right set for the user U, and generates a control command based on the generated action command. The generation unit 173 generates, for example, an action command to cause the boarding type mobile body 100 to perform a leaving action to move away from another person.

When an execution signal is transmitted by the management server 400, the generation unit 173 generates an action command for the boarding type mobile body 100 based on the transmitted execution signal, and generates a control command based on the generated action command. When the execution signal is, for example, a signal indicating shopping, the generation unit 173 generates an action command to cause the boarding type mobile body 100 to go shopping.

Furthermore, the generation unit 173 generates an action command for causing the alarm device 115 to perform an alarm operation such as emitting light or outputting sound, and generates a control command based on the generated action command. The command generation unit 170 outputs the control command generated by the generation unit 173 to the motor control unit 180 and the alarm control unit 190.

When a preparation start signal is transmitted by the management server 400, the generation unit 173 generates an action command to be executed by the boarding type mobile body 100 based on the transmitted preparation start signal, and generates a control command to prepare for start of use based on the generated action command. For example, as preparation for start of use, the generation unit 173 warms up the boarding type mobile body 100 or turns on a lamp provided in the alarm device 115, thereby making the boarding type mobile body 100 easier to understand for the user U.

The center of gravity estimation unit 174 and balance control unit 175 in the command generation unit 170 function when the user U is riding on the boarding type mobile body 100. The center of gravity estimation unit 174 estimates the center of gravity of an object including the user U riding on the boarding type mobile body 100, the aircraft 110, the seat 113, etc., based on the output of the acceleration sensor 143 and the angular velocity sensor 144.

The balance control unit 175 generates a control command in a direction to return the position of the center of gravity estimated by the center of gravity estimation unit 174 to a reference position (the position of the center of gravity in a stationary state). For example, when the position of the center of gravity is shifted to the right rear from the reference position, the balance control unit 175 generates information instructing an acceleration toward the right rear as a control command.

For example, if the action command is to accelerate forward and the position of the center of gravity is behind the reference position, the balance control unit 175 may suppress the acceleration so that the position of the center of gravity does not shift further backward due to the accelerated forward movement, or may move backward once to guide the position of the center of gravity forward before starting the accelerated forward movement. The command generation unit 170 outputs the control command generated by the balance control unit 175 to the motor control unit 180.

The motor control unit 180 individually controls each motor attached to the omnidirectional wheels 112 based on the control command output by the command generation unit 170. The motor control unit 180 executes different controls depending on whether the user U is on board (seated) the boarding type vehicle 100 or not.

When a user U is riding on the boarding type mobile body 100, this type of control allows the user U riding on the boarding type mobile body 100 to move the boarding type mobile body 100 in the desired direction by changing his or her own posture to move the center of gravity in the desired direction. In other words, the boarding type mobile body 100 recognizes the movement of the user U's center of gravity as a steering operation for the boarding type mobile body 100, and performs a moving operation in accordance with the steering operation.

The alarm control unit 190 outputs a light alarm from a lamp and an alarm sound from a speaker based on the control command output by the command generation unit 170. The light alarm and alarm sound notify the user that the ride-on vehicle 100 has already been granted a right of use and is not available to others.

The management server 400 is installed, for example, in the amusement facility P. The management server 400 manages multiple boarding type mobile bodies 100 in the amusement facility P. The management server 400 recognizes the positions of the boarding type mobile bodies 100 in the amusement facility P. The management server 400 manages the movement of the boarding type mobile bodies 100 for which the user U has not been granted usage rights.

Figure 7 is a configuration diagram showing an example of the management server 400. The management server 400 includes, for example, a server communication device 410, a server control device 420, and a storage unit 450. The server communication device 410 performs wireless communication based on, for example, Wi-Fi, DSRC, Bluetooth (registered trademark), or other communication standards.

The server communication device 410 receives electrical signals transmitted by the boarding type mobile body 100 and the terminal device 200, and outputs them to the server control device 420. The server communication device 410 receives, for example, a vehicle position signal, a usage interruption signal, and a remaining charge signal transmitted by the boarding type mobile body 100, and a dispatch request signal transmitted by the terminal device 200, and outputs them to the server control device 420.

The server control device 420 includes, for example, a mobile management unit 421, a vehicle dispatch management unit 422, a reception unit 423, an estimation unit 424, a determination unit 425, a rental judgment unit 426, a preparation control unit 427, and an assignment unit 428. The server control device 420 is realized, for example, by a hardware processor such as a CPU executing a program (software). Some or all of these components may be realized by hardware (including circuitry) such as an LSI, ASIC, FPGA, or GPU, or may be realized by collaboration between software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device having a non-transient storage medium), or may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium), and may be installed in the storage device by attaching the storage medium to a drive device. The storage device functions as the storage unit 450.

The storage unit 450 stores, for example, a reservation management list 451, a rental management list 452, and an execution list 453. These lists are for managing reservations for rental of the boarding type mobile body 100 by the user U. The reservation management list 451 includes information regarding the user U who has transmitted a reservation request signal from the terminal device 200 and reserved the boarding type mobile body 100, and the contents of the reservation. Figure 8 is a diagram showing an example of the contents of the reservation management list 451. The reservation management list 451 includes information such as the user ID, start time of use, duration of use, start location of use, number of people making a reservation, and specified requirements.

The lending management list 452 is a list for managing the correspondence between the user U to whom the boarding type mobile body 100 has been lent and the boarding type mobile body 100. FIG. 9 is a diagram showing an example of the contents of the lending management list 452. The lending management list 452 includes information on the user to whom the boarding type mobile body 100 has been lent and the boarding type mobile body 100. The lending management list 452 includes, for example, the mobile body ID of the lent boarding type mobile body 100, the user ID of the user U to whom the boarding type mobile body 100 has been lent, and information on the usage time during which the user U uses the boarding type mobile body 100. The lending management list 452 also includes information on the time during which the user U allows the boarding type mobile body 100 to be lent to others during the user U's usage time (hereinafter, the lending permission time).

The execution list 453 is a list that sets the execution contents of the boarding type mobile body 100 during the non-use time of the boarding type mobile body 100 lent to the user U. It includes information that sets the execution contents that the boarding type mobile body 100 can execute for each non-use time when the user U is not using the boarding type mobile body 100. FIG. 10 is a diagram showing an example of the contents of the execution list 453. In the execution list 453, when the remaining charge of the battery 135 is large, "travel" is set as the execution content of the boarding type mobile body 100 regardless of the non-use time. In the execution list 453, when the remaining charge of the battery 135 is small, "standby" is set when the non-use time is less than a first reference time, for example, 15 minutes, "receive shopping" is set when the non-use time exceeds the first reference time and is less than a second reference time, for example, 60 minutes, and "shopping" is set when the non-use time exceeds the second reference time.

"Touring" means, for example, that the boarding type mobile body 100 travels alone within a given area, for example within an amusement facility P, without carrying the user U. During the tour, the boarding type mobile body 100 captures images of the amusement facility P with an installed camera (not shown) and transmits information about the captured images to the user U's terminal device 200. An image based on the image transmitted by the boarding type mobile body 100 is displayed on the user U's terminal device 200. By viewing the image displayed on the terminal device 200, the user U can have a virtual experience in which, for example, the boarding type mobile body 100 becomes an avatar and the user U enjoys the amusement facility P.

"Waiting" is an action in which the boarding type mobile body 100 maintains a stopped state at the stopping position. Actions include actions that involve movement and actions that do not involve movement, and "waiting" is an action that does not involve movement. "Shopping" is an action in which the boarding type mobile body of the user U (hereinafter, the own machine) goes shopping. "Receiving shopping" is an action in which another boarding type mobile body 100 (hereinafter, the other machine) within the amusement facility P, which is different from the own machine, performs shopping on behalf of the own machine and receives the items obtained from the shopping performed by the other machine.

In the execution list shown in FIG. 10, the execution contents for the same time period are specified as one if the remaining charge of the battery 135 in the boarding type mobile body 100 is the same, but different execution contents may be set for the same non-use time. In this case, the boarding type mobile body 100 executes one of the different execution contents, but the method of determining the execution content is appropriate. In this case, the execution content of the boarding type mobile body 100 may be determined, for example, based on the specification of the user U, or based on the stopping position of the boarding type mobile body 100 (the position where the user U gets off the boarding type mobile body 100).

The mobile unit management unit 421 recognizes the positions of the multiple boarding type mobile bodies 100 within the amusement facility P based on the vehicle position signals transmitted by the multiple boarding type mobile bodies 100. The mobile unit management unit 421 refers to the recognized positions of the multiple boarding type mobile bodies 100 and a map of the amusement facility P, and generates a movement plan for moving the boarding type mobile bodies 100 to an area with a smaller number of boarding type mobile bodies 100. The mobile unit management unit 421 generates a movement signal that achieves the movement plan, and outputs it to the server communication device 410. The mobile unit management unit 421 manages the multiple types of boarding type mobile bodies 100 by type.

When the server communication device 410 receives a reservation request signal transmitted by the terminal device 200, the mobile object management unit 421 executes a reservation of the boarding type mobile object 100 for the user U of the terminal device 200 that transmitted the reservation request signal. The mobile object management unit 421 updates the reservation management list 451 stored in the memory unit 450 in association with the reservation of the boarding type mobile object 100. When the server communication device 410 receives a reservation request signal, the mobile object management unit 421 selects and determines the boarding type mobile object 100 to be lent to the user U from among the available boarding type mobile objects 100. The mobile object management unit 421 outputs a reservation signal to the server communication device 410 to be transmitted to the user U of the terminal device 200 that transmitted the reservation request signal and the determined boarding type mobile object 100.

When the server communication device 410 receives a matching signal transmitted by the boarding type mobile body 100, the mobile body management unit 421 acquires information that the boarding type mobile body 100 having the mobile body ID indicated by the matching signal has been rented to the user U having the user ID indicated by the matching signal. The mobile body management unit 421 updates the rental management list 452 stored in the memory unit 450 based on the information acquired here.

When the server communication device 410 receives a dispatch request signal transmitted by the terminal device 200, the dispatch management unit 422 generates a dispatch signal to move a boarding type mobile body 100 for which no usage rights have been set to the location of the terminal device 200 that transmitted the dispatch request signal. The dispatch management unit 422, for example, designates a boarding type mobile body 100 in the vicinity of the terminal device 200 that transmitted the dispatch request signal as a dispatch target. The dispatch management unit 422 outputs the generated dispatch signal to the server communication device 410.

The reception unit 423 receives a reservation request signal transmitted by the terminal device 200 and received by the server communication device 410. The reception unit 423 stores the contents of each item included in the reservation request signal in the reservation management list 451 of the storage unit 450 shown in FIG. 8. The reception unit 423 updates the reservation management list 451 by storing the contents of each item included in the reservation request signal in the reservation management list 451.

The estimation unit 424 estimates the unused time during which the first user will not be using the boarding type mobile body 100 based on information indicated by the vehicle position signal and the interruption signal output by the server communication device 410. Information for estimating the unused time includes, for example, the disembarking location and disembarking time of user U based on the vehicle position signal and the interruption signal, the facility B within the facility near the disembarking location, and the composition of the people accompanying user U. The estimation unit 424 outputs a unused time signal indicating the estimated unused time to the server communication device 410.

The determination unit 425 determines the operation of the boarding type mobile body 100 based on the non-use time estimated by the estimation unit 424 and the remaining charge signal transmitted by the boarding type mobile body 100. The determination unit 425, for example, refers to the execution list 453 shown in FIG. 10 for the non-use time estimated by the estimation unit 424. The determination unit 425 determines the execution content determined by referring to the non-use time as the operation to be executed by the boarding type mobile body 100. The determination unit 425 outputs an execution signal indicating the determined execution content to the server communication device 410.

The lending determination unit 426 determines whether or not the boarding type mobile body 100 can be lent to the second user based on the reservation of the second user accepted by the acceptance unit 423 and the unused time and permitted lending time of the boarding type mobile body 100 of the first user estimated by the estimation unit 424. The lending determination unit 426 determines that the boarding type mobile body 100 can be lent to the second user, for example, when the time from the start of use by the second user to the elapse of the usage time falls within the unused time of the boarding type mobile body 100 of the first user. The lending determination unit 426 prohibits the determination that the boarding type mobile body 100 can be lent to the second user during the lending waiting time after the first user dismounts from the boarding type mobile body 100 when the boarding type mobile body 100 is not in use. The lending waiting time may be determined arbitrarily, and may be, for example, between about 10 seconds and 30 seconds, or between about 1 minute and 5 minutes.

When the lending determination unit 426 determines that the first user can use another boarding type mobile body 100 after the non-use time has elapsed, it determines that the boarding type mobile body 100 can be lent to a second user. The lending determination unit 426 outputs a lending availability signal to the server communication device 410 indicating that the lending available boarding type mobile body is available for lending to the first user of the boarding type mobile body that has been determined to be available for lending to a second user (hereinafter, a lending available boarding type mobile body).

The lending determination unit 426 determines whether or not to lend the lendable boarding type mobile body to the second user. For example, when there are multiple lendable boarding type mobile bodies, the lending determination unit 426 determines that one of them is to be lent to the second user. The lending determination unit 426 outputs a lending signal to the server communication device 410 to the first user of the boarding type mobile body to be lent to the second user (hereinafter, the lending boarding type mobile body), indicating that the lending boarding type mobile body will be lent to a second user during a time when the lending boarding type mobile body is not in use.

The rental determination unit 426 determines whether the second user's usage mode is a test ride or not, and if it is determined that it is a test ride, imposes restrictions on the range of movement of the boarding type mobile body 100 to be rented out. In this case, the rental determination unit 426 generates a rental availability signal adding that there is a restriction on the range of movement of the boarding type mobile body 100. If the boarding type mobile body 100 is a test ride, it is not assumed that extensive movement will be performed, so a restriction is imposed on the range of movement.

The preparation control unit 427 starts preparation for the user U to use the boarding type mobile body 100 when the user U performs a predetermined action, for example, approaches the boarding type mobile body 100 or a parking area (parking area) where the boarding type mobile body 100 is parked. The preparation control unit 427 determines whether the distance between the user U and the boarding type mobile body 100 is equal to or less than a predetermined value, for example, based on the vehicle position signal transmitted by the boarding type mobile body 100 and the user position signal transmitted by the terminal device 200. The predetermined action may be an action other than the action of the user U approaching the boarding type mobile body 100. For example, the information may be information indicating that the user U will start the attraction when the user U stops the boarding type mobile body 100 near an attraction and gets back on the boarding type mobile body 100 after the attraction is over. The information indicating that the user U will start the attraction may be, for example, information indicating that the user U holds a two-dimensional code such as a QR code (registered trademark) over a reader installed at the entrance when entering the attraction.

When the preparation control unit 427 determines that the distance between the user U and the boarding type mobile body 100 is equal to or less than a predetermined value, it outputs a preparation start signal to the server communication device 410 to cause the boarding type mobile body 100 to start preparing for use by the user U. The preparation for allowing the user U to use the boarding type mobile body 100 may be any preparation, for example, the boarding type mobile body 100 may be warmed up, or a lamp provided in the alarm device 115 may be turned on to make the boarding type mobile body 100 easier for the user U to understand.

The granting unit 428 grants an incentive to the first user when the lending determination unit 426 determines that the boarding type mobile body 100 can be lent to the second user. The granting unit 428 grants an additional incentive to the first user when the boarding type mobile body 100 that can be lent is lent to the second user. When granting the incentive, incentive, and additional incentive to the first user, the granting unit 428 outputs a grant signal to the server communication device 410.

The incentive and additional incentive may be of any content. For example, the incentive and additional incentive may be a preferential use of a preferred boarding type vehicle 100, or a discount on the rental fee for the boarding type vehicle 100. The incentive and additional incentive may be the same or different in the degree to which they are advantageous to the user U, for example, the degree to which the fee is discounted. The additional incentive may be more advantageous or less advantageous to the user U than the incentive.

The server communication device 410 transmits the movement signal output by the mobile unit management unit 421 to the boarding type mobile unit 100. The server communication device 410 transmits the reservation signal output by the mobile unit management unit 421 to the boarding type mobile unit 100 and the terminal device 200. The server communication device 410 transmits the dispatch signal output by the dispatch management unit 422 to the boarding type mobile unit 100 designated by the dispatch management unit 422 as the dispatch target. The server communication device 410 transmits the unused time signal, the rentable signal, the rent signal, and the grant signal output by the estimation unit 424, the lending determination unit 426, and the granting unit 428 to the terminal device 200 of the first user.

The server communication device 410 transmits the lending available signal and lending signal output by the lending determination unit 426 to the terminal device 200 of the first user. The server communication device 410 transmits the lending signal, execution signal, and preparation start signal output by the decision unit 425, lending determination unit 426, and preparation control unit 427 to the boarding type mobile body 100 of the first user. When transmitting a lending signal to the boarding type mobile body 100, the server communication device 410 also transmits a reservation signal.

Next, the control procedure of the boarding type mobile body 100 by the control device 150 will be described. FIG. 11 is a flowchart showing an example of processing by the control device 150. The control device 150 starts the processing shown in FIG. 11 when it receives a usage right setting request signal transmitted to the communication device 120 by the terminal device 200. Before the control device 150 receives the usage right setting request signal and the user U has not been set with the usage right, the boarding type mobile body 100 is stored in the parking pool PP or traveling (self-propelled) within the amusement facility P. When the control device 150 receives the usage right setting request signal, the boarding type mobile body 100 stops even if it was traveling.

When the communication device 120 receives the usage right setting request signal, the authentication unit 161 matches the user U with the boarding type mobile body 100 by matching the user ID added to the usage right setting request signal with the mobile body ID stored in the memory unit (S101), and generates a matching signal. The authentication unit 161 outputs the generated matching signal to the communication device 120, and the communication device 120 transmits the matching signal to the management server 400 (S103).

The authentication unit 161 matches the user U with the boarding type mobile body 100, thereby granting the user U the right to use the boarding type mobile body 100 (S105). After the right to use is granted, the user U boards the boarding type mobile body 100, allowing the user U to operate (drive) the boarding type mobile body 100.

Then, the determination unit 171 determines whether the user U is seated in the seat 113 (S107). When it is determined that the user U is seated in the seat 113, the command generation unit 170 executes boarding control using the center of gravity estimation unit 174 and the balance control unit 175 (S109). By executing the driving control, the user U boarding the boarding type vehicle 100 can drive the boarding type vehicle 100 according to his or her own will.

If it is determined that the user U is not seated in the seat 113, the command generation unit 170 generates a usage interruption signal and causes the communication device 120 to transmit the usage interruption signal to the management server 400 (S111). Next, the release unit 162 starts measuring the time after the user U leaves the boarding type vehicle 100, and executes dismounting control using the detection unit 172 and the generation unit 173 (S113). Dismounting control will be described further below.

The release unit 162 then determines whether the usage rights have been released (S115). If the release unit 162 determines that the usage rights have not been released, it determines whether the release condition has been met (S117). If the release unit 162 determines that the release condition has not been met, it returns the process to step S107. If the release unit 162 determines that the release condition has been met, it releases the usage rights set for user U (S119). In this way, the control device 150 ends the process shown in FIG. 11. If the release unit 162 determines in step S115 that the usage rights have been released, the control device 150 also ends the process shown in FIG. 11.

Next, the disembarking control in step S113 will be described. FIG. 12 is a flowchart showing an example of the disembarking control process. If the determination unit 171 determines in step S107 that the user is not seated, the generation unit 173 determines whether or not the communication device 120 has received an execution signal transmitted by the management server 400 (S201). If it is determined that the communication device 120 has not received the execution signal transmitted by the management server 400, the generation unit 173 advances the process to step S207.

When it is determined that the communication device 120 has received an execution signal transmitted by the management server 400, the generation unit 173 determines whether the received execution signal indicates standby (S203). When it is determined that the received execution signal indicates standby, the generation unit 173 generates an action command corresponding to the execution signal, and generates a control command based on the generated action command (S205). In this way, the control device 150 ends the process shown in FIG. 12.

When it is determined that the communication device 120 has not received the execution signal transmitted by the management server 400, or when it is determined that the received execution signal indicates waiting, the generation unit 173 determines whether or not the communication device 120 has received the rental signal transmitted by the management server 400 (S207). When it is determined that the communication device 120 has received the rental signal transmitted by the management server 400, the generation unit 173 executes a process of renting out the boarding type mobile body 100 to a second user in response to the reservation signal transmitted together with the rental signal (S209). In this way, the control device 150 ends the process shown in FIG. 12.

If it is determined that the communication device 120 has not received the rental signal transmitted by the management server 400, the detection unit 172 determines whether or not there is an object approaching the boarding type mobile body 100 based on the peripheral object signal transmitted by the peripheral sensor 142 (S211). If it is determined that there is no object approaching the boarding type mobile body 100, the control device 150 ends the process shown in FIG. 12.

When it is determined that an object is approaching the boarding type mobile body 100, the detection unit 172 determines whether the approaching object is the user U or not (S213). The determination of whether the approaching object is the user U or not may be performed in any manner. For example, the detection unit 172 determines whether the approaching object is the user U or not based on an identity verification request signal including a user ID that is transmitted by the terminal device 200 of the user U and received by the communication device 120. The detection unit 172 may determine whether the approaching object is the user U or not based on an image of the user U, a physical feature of the user U such as a fingerprint, or by the user touching the aircraft 110. When it is determined that the approaching object is not the user, the detection unit 172 detects the intention of another person to use the boarding type mobile body 100 (S215).

Then, the detection unit 172 determines whether or not the communication device 120 has received an other person request signal transmitted by the terminal device 200 possessed by the other person (S217). If the detection unit 172 determines that the communication device 120 has not received an other person request signal, the process proceeds to step S225. If the detection unit 172 determines that the communication device 120 has received an other person request signal, the release unit 162 determines whether or not the release condition is satisfied (S219). If the release unit 162 determines that the release condition is satisfied, the adjustment unit 163 releases the usage rights of the user U (S221). Next, the adjustment unit 163 sets the usage rights to the other person (S223), and the control device 150 ends the process shown in FIG. 12.

If the release unit 162 determines that the release condition is not satisfied, the generation unit 173 generates a control signal and outputs it to the motor control unit 180 and the alarm control unit 190 (S225). The motor control unit 180, to which the generation unit 173 has output the control signal, outputs a control command to the motor of the omnidirectional wheel 112 to cause the boarding type vehicle 100 to move away. The motor of the omnidirectional wheel 112, to which the control command has been output by the motor control unit 180, causes the boarding type vehicle 100 to move away (S227).

The alarm control unit 190, which has received the control signal from the generation unit 173, outputs a control command to the alarm device 115 to turn on and blink the lamp of the alarm device 115 and to output an alarm sound from the speaker. The alarm device 115, which has received the control command from the alarm control unit 190, outputs an alarm to turn on and blink the lamp and to output an alarm sound from the speaker (S229).

For example, when multiple boarding type mobile bodies 100 are parked in the same area, it is assumed that the user U or other people may approach a boarding type mobile body 100 different from the boarding type mobile body 100 that the user U has been using. Under such circumstances, for example, other people may approach the boarding type mobile body 100 used by the user U, mistakenly thinking that it is the boarding type mobile body 100 that the user U has been using. In this case, the control device 150 detects the intention of other people to use the boarding type mobile body 100 used by the user U. Here, if a request signal from other people has not been received, or if a request signal from other people has been received but the release condition is not met, the right to use is not set for other people, and there is no need for other people to approach the boarding type mobile body 100. For this reason, the control device 150 moves the boarding type mobile body 100 away from other people and causes the alarm device 115 to perform an alarm operation. After that, the control device 150 ends the processing shown in FIG. 12.

If it is determined in step S213 that the object approaching the boarding type mobile body 100 is the user U, the generation unit 173 determines whether or not the communication device 120 has received a preparation start signal transmitted by the management server 400 (S231). If the generation unit 173 determines that the communication device 120 has not received the preparation start signal transmitted by the management server 400, the control device 150 ends the processing shown in FIG. 12.

When it is determined that the communication device 120 has received the preparation start signal transmitted by the management server 400, the generation unit 173 generates an action command based on the preparation start signal, outputs a control command, and starts preparation for use (S233). Next, the communication device 120 transmits a vehicle position signal indicating the position of the boarding type mobile body 100 detected by the vehicle position detection device 130 to the terminal device 200 (S235). The terminal device 200 that has received the vehicle position signal, for example, determines that the boarding type mobile body 100 that stops at a position based on the vehicle position signal is a boarding type mobile body that the user U has a use circle, and performs a decoration display using, for example, an AR display, in accordance with the boarding type mobile body 100 that stops at a position according to the vehicle position signal on the touch panel 210 of the terminal device 200. By displaying the boarding type mobile body 100 that stops at the position indicated by the vehicle position signal in a decoration display, the user U can easily understand the position of the vehicle. In this way, the control device 150 ends the processing shown in FIG. 12.

Next, the processing of the server control device 420 of the management server 400 will be described. FIG. 13 is a flowchart showing an example of the processing of the server control device 420. The server control device 420 judges whether or not the server communication device 410 has received a reservation request signal transmitted by the terminal device 200 operated by the user U (S301). If it is determined that the server communication device has received a reservation request signal, the reception unit 423 executes a reservation of the boarding type mobile body 100 for the user U of the terminal device 200 that transmitted the reservation request signal, and updates the reservation management list 451 stored in the memory unit 450 (S303). If it is determined that the server communication device has not received a reservation request signal, the server control device 420 skips the processing of step S303.

Then, the vehicle dispatch management unit 422 determines whether the server communication device 410 has received the dispatch request signal transmitted by the terminal device 200 (S305). If it is determined that the server communication device 410 has received the dispatch request signal, the vehicle dispatch management unit 422 generates a dispatch signal to move the boarding type mobile body 100, and the server communication device 410 transmits the signal to the boarding type mobile body 100 designated as the dispatch target (S307). If it is determined that the server communication device 410 has not received the dispatch request signal, the vehicle dispatch management unit 422 skips the processing of step S307.

Then, the mobile object management unit 421 determines whether or not the server communication device 410 has received the matching signal transmitted by the boarding type mobile object 100 (S309). If it is determined that the server communication device has received the matching signal, the mobile object management unit 421 acquires information that the boarding type mobile object 100 has been rented to the user U, and updates the rental management list 452 stored in the memory unit 450 (S311). If it is determined that the server communication device has not received the matching signal, the mobile object management unit 421 skips the processing of step S311.

Next, the estimation unit 424 determines whether the server communication device 410 has received the interruption signal transmitted by the boarding type mobile body 100 (S313). If it is determined that the server communication device 410 has received the interruption signal, the estimation unit 424 estimates the non-use time based on the vehicle position signal received by the server communication device 410 and the information indicated by the interruption signal (S315).

When estimating the unused time, the estimation unit 424, for example, identifies the location where the boarding type mobile body 100 is stopped based on the vehicle position signal. The estimation unit 424 estimates the unused time of the boarding type mobile body 100 based on the identified stopping location of the boarding type mobile body 100. The estimation unit 424 estimates the behavior of the user U based on the identified stopping location of the boarding type mobile body 100, for example, and estimates the unused time from the estimated behavior.

For example, when the boarding type vehicle 100 is parked in a parking area or the like near a popular attraction, the estimation unit 424 estimates that the user U will wait in line for a long time. In this case, the estimation unit 424 estimates the non-use time to be long. For example, when the vehicle is parked in a parking area or the like near a restaurant, the estimation unit 424 estimates that the user will eat at the restaurant. In this case, the estimation unit 424 estimates the time spent eating and drinking at the restaurant to be the non-use time.

For example, if the vehicle stops near a vehicle selling sweets that makes rounds within the amusement facility P, the estimation unit 424 estimates that the user will do some light shopping. In this case, the estimation unit 424 estimates the non-use time to be a short period of time. The estimation unit 424 transmits a non-use time signal indicating the estimated non-use time to the terminal device 200 of the user U using the server communication device 410 (S317). The terminal device 200 reports the non-use time indicated by the transmitted non-use time signal to the user U, for example, by displaying it on the touch panel 210.

Next, the determination unit 425 determines the execution content of the boarding type mobile body 100 based on the non-use time estimated by the estimation unit 424 and the remaining charge signal transmitted by the boarding type mobile body 100 (S319). Here, the procedure for determining the execution content of the boarding type mobile body 100 will be described. FIG. 14 is a flowchart showing an example of the process of determining the execution content in the determination unit 425.

When determining the execution content of the boarding type mobile body 100, the determination unit 425 first refers to the execution list 453 stored in the memory unit 450 (S401). Next, the determination unit 425 determines whether the non-use time estimated by the estimation unit 424 is equal to or less than the first reference time (15 minutes) (S403). If it is determined that the estimated non-use time is equal to or less than the first reference time, the determination unit 425 determines "standby" as the execution content of the boarding type mobile body 100 (S405).

If it is determined that the estimated non-use time is not equal to or less than the first reference time (exceeds 15 minutes), the determination unit 425 acquires the remaining charge of the battery 135 in the boarding type vehicle 100 indicated by the remaining charge signal received by the server communication device 410 (S407). Next, the determination unit 425 determines whether the acquired remaining charge of the battery 135 is equal to or greater than a predetermined amount (S409).

When it is determined that the acquired remaining charge of the battery 135 is equal to or greater than a predetermined amount, the determination unit 425 determines "travel" as the execution content of the boarding type mobile body 100 (S411). The predetermined amount may be set to any value, and may be, for example, a remaining charge amount that ensures a certain degree of remaining charge after traveling to and from a specific spot within the amusement facility P.

If it is determined that the remaining charge is not equal to or greater than the predetermined amount (is less than the predetermined amount), the determination unit 425 determines the execution content according to the non-use time shown in the execution list 453 (S413). For example, if the non-use time exceeds the second reference time (60 minutes), the determination unit 425 determines "shopping" as the execution content. In this way, the determination unit 425 ends the process shown in FIG. 14.

Returning to the flow of FIG. 13, the determination unit 425 transmits an execution signal indicating the determined execution content to the boarding type mobile body 100 using the server communication device 410 (S321). Next, the lending determination unit 426 executes a lending determination for the second user of the boarding type mobile body 100 (S323). Here, the procedure for determining the lending of the boarding type mobile body 100 will be described. FIG. 15 is a flowchart showing an example of the lending determination process in the lending determination unit 426.

The lending determination unit 426 determines whether the lending waiting time has elapsed after the boarding type mobile body 100 has stopped and the first user has dismounted from the boarding type mobile body 100 (S501). If it is determined that the lending waiting time has not elapsed, the lending determination unit 426 prohibits lending of the boarding type mobile body 100 to the second user (S503). By setting the lending waiting time, it is possible to permit the boarding type mobile body 100 to be used again in the event of an unexpected event. An example of an unexpected event is when the first user leaves something behind and goes back to retrieve it. Another example of an unexpected event is when, among a parent and child who are about to use an attraction, the child suddenly becomes reluctant to use the attraction, stops using the attraction, and tries to use the boarding type mobile body 100 again.

When it is determined that the rental waiting time has elapsed, the rental determination unit 426 acquires the non-use time estimated by the estimation unit 424 and the reservation management list 451 stored in the memory unit 450 (S505). The rental determination unit 426 refers to the non-use time and the reservation management list 451 to determine whether the reservation of the second user satisfies a first condition that the second user's use time of the boarding type mobile body 100 is within the non-use time (S507). The determination of whether the first condition is satisfied may take into account the time taken by the second user to borrow and return the boarding type mobile body 100.

The lending judgment unit 426 judges that the first condition is met, for example, if the unused time is four hours (e.g., from 13:00 to 17:00) and the usage time of the second user shown in the reservation management list 451 is two hours (e.g., from 14:00 to 16:00). The lending judgment unit 426 judges that the first condition is not met, for example, if the unused time is three hours from the present and the usage time of the second user shown in the reservation management list 451 is four hours from the present.

If it is determined that the first condition is met, the lending determination unit 426 imposes a time limit on the lending time (S509). For example, if the non-use time is two hours, a time limit of two hours or less, or a predetermined time shorter than two hours, for example, one hour and a half, which is 30 minutes shorter, is imposed on the lending time. The lending determination unit 426 may not impose a time limit. Thereafter, the lending determination unit 426 determines that the boarding type vehicle 100 can be lent (S511).

If it is not determined that the first condition is satisfied, the lending determination unit 426 determines whether or not the second condition is satisfied, that is, the use time of the boarding type mobile body 100 of the second user exceeds the non-use time, but there is another boarding type mobile body 100 that can be provided to the first user after the non-use time has elapsed (S513). For example, even if the boarding type mobile body 100 used by the first user is lent to the second user, if another boarding type mobile body 100 can be lent to the first user after the non-use time has elapsed, there will be no inconvenience in the use of the boarding type mobile body 100 of the first user. Therefore, it is possible to leave the possibility of lending the boarding type mobile body 100 used by the first user to the second user. If it is determined that the second condition is not satisfied, the lending determination unit 426 determines that the boarding type mobile body 100 used by the first user cannot be lent (S515), and ends the processing shown in FIG. 15.

Then, the lending determination unit 426 determines whether or not a specified requirement has been added to the boarding type mobile body 100 that has been lent to the first user (S517). If it is determined that the specified requirement has been added, the lending determination unit 426 determines that the boarding type mobile body 100 to be used by the first user is available for lending (S511). If it is determined that the specified requirement has been added, the lending determination unit 426 determines whether or not there is a boarding type mobile body 100 that satisfies the specified requirement within the amusement facility P in addition to the boarding type mobile body 100 that has been lent to the first user (S519).

If it is determined that there are no other boarding type mobile bodies within the amusement facility P that satisfy the specified requirements, the rental determination unit 426 determines that the boarding type mobile body 100 used by the first user cannot be rented (S513), generates a rental availability signal, and ends the processing shown in FIG. 15. If it is determined that there are other boarding type mobile bodies within the amusement facility P that satisfy the specified requirements, the rental determination unit 426 determines that the boarding type mobile body 100 used by the first user can be rented (S511).

Then, the rental determination unit 426 determines whether the information on the usage mode included in the reservation request signal of the second user is a test drive (S521). If the rental determination unit 426 determines that the information on the usage mode is not a test drive, it ends the processing shown in FIG. 15. If the rental determination unit 426 determines that the information on the usage mode is a test drive, it adds a restriction to the movement range of the rentable boarding type vehicle (S523) and adds a notice that there is a restriction on the movement range to the rental availability signal. In this way, the rental determination unit 426 ends the processing shown in FIG. 15.

Returning to the flow of FIG. 13, the lending determination unit 426 determines whether or not lending is possible based on the processing of step S323 (S325). If it is determined that the boarding type mobile body 100 is available for lending, the lending determination unit 426 transmits a lending availability signal to the terminal devices 200 of the first user and the second user, respectively, using the server communication device 410 (S327). If it is determined that the boarding type mobile body 100 is not available for lending (not available for lending), the lending determination unit 426 skips the processing of steps S327 to S335.

Then, the granting unit 428 determines that the first user's boarding type mobile body is available for rental, and grants an incentive to the first user in association with making the boarding type mobile body a rentable boarding type mobile body. In this case, the granting unit 428 generates a grant signal including information about the incentive to be granted to the first user. The granting unit 428 transmits the generated grant signal to the first user's terminal device 200 using the server communication device 410 (S329).

Then, the lending determination unit 426 determines, for example, whether or not to lend the lendable boarding type mobile body to the second user (S331). If there are multiple lendable boarding type mobile bodies, the lending determination unit 426 determines that one of them is to be lent to the second user, and determines that the other lendable boarding type mobile bodies are not to be lent to the second user.

If it is determined that the lendable mobile object is to be lent to the second user, the lending determination unit 426 generates a lending signal and a reservation signal and transmits them to the terminal devices 200 of the first user and the second user, respectively, using the server communication device 410 (S333). If it is determined that the lendable mobile object is not to be lent to the second user, the lending determination unit 426 skips the processing of steps S333 and S335.

Then, the granting unit 428 determines to lend the first user's boarding type mobile body, and grants an additional incentive to the first user in association with making the boarding type mobile body a lent boarding type mobile body. In this case, the granting unit 428 generates a grant signal including information on the additional incentive to be granted to the first user. The granting unit 428 transmits the generated grant signal to the terminal device 200 of the first user using the server communication device 410 (S335).

The preparation control unit 427 then determines whether the distance between the user U and the boarding type mobile body 100 is less than or equal to a predetermined value (S337). If the preparation control unit 427 determines that the distance between the user U and the boarding type mobile body 100 is not less than or equal to the predetermined value (exceeds the predetermined value), the server control unit 420 ends the processing shown in FIG. 13. If the preparation control unit 427 determines that the distance between the user U and the boarding type mobile body 100 is less than or equal to the predetermined value, the preparation control unit 427 begins preparations for allowing the user U to use the boarding type mobile body 100 (S339). In this way, the server control unit 420 ends the processing shown in FIG. 13.

When the boarding type mobile body 100 of the embodiment determines that the user U has left the boarding type mobile body 100 and detects another person's intention to use the boarding type mobile body 100, the boarding type mobile body 100 executes a predetermined operation based on the setting information set for the user U and the boarding type mobile body 100. Specifically, when the information in which the right of use is set is the setting information, the boarding type mobile body 100 executes a predetermined operation.

For example, when a user U approaches a boarding type mobile body 100 for which a right of use has been set, a vehicle position signal is transmitted to the user U's terminal device 200, and the vehicle position is displayed as a decoration on the touch panel 210 of the terminal device 200. Alternatively, when another person approaches a boarding type mobile body 100 for which a right of use has been set, the boarding type mobile body 100 moves in a direction away from the other person, and makes the other person (user U) recognize that the boarding type mobile body 100 is one for which a right of use has been set by a person other than the other person who output the alarm by the alarm device 115. Therefore, it is possible to prevent misuse of the mobile body by others.

The management server 400 in the mobile object management system 1 of the embodiment estimates the unused time of the boarding type mobile object 100 of the first user, and determines whether or not to lend the boarding type mobile object 100 to the second user based on the estimated unused time. This allows the boarding type mobile object 100 to be effectively utilized during the unused time when the first user is not using the boarding type mobile object 100.

In addition, the management server 400 of the embodiment determines that the boarding type mobile body 100 can be lent to the second user when either a first condition is met, that is, the second user's use time of the boarding type mobile body 100 is within the non-use time, or a second condition is met, that is, the second user's use time of the boarding type mobile body 100 exceeds the non-use time but there is another boarding type mobile body 100 that can be provided to the first user after the non-use time has elapsed. Therefore, the boarding type mobile body can be lent to the second user while making it difficult to interfere with the first user's use.

In addition, when the first condition is met and the boarding type mobile body 100 is lent to the second user, a time limit is imposed. Furthermore, when the first user has been lent the boarding type mobile body 100 with certain requirements attached, the boarding type mobile body 100 cannot be lent to the second user. This makes it even less likely that the first user will be hindered from using the boarding type mobile body 100.

The management server 400 of the embodiment also estimates the on-site facility B used by the first user based on the stopping and location of the boarding type mobile body 100, and estimates the non-use time based on the estimated usage time of on-site facility B or the time spent eating and drinking at on-site facility B. This makes it possible to accurately estimate the non-use time of the boarding type mobile body 100 by the first user.

In addition, the management server 400 of the embodiment provides an incentive to a first user who has made the boarding type mobile body 100 available for rental, and provides an additional incentive to the first user when the boarding type mobile body 100 is permitted to be rented and is then used by a second user. This makes it possible to provide the first user with an incentive to rent the boarding type mobile body to the second user. This allows the boarding type mobile body 100 to be effectively utilized during periods of non-use.

In addition, the management server 400 of the embodiment estimates the unused time according to the location when the user dismounts from the boarding type mobile body 100, and determines the operation of the boarding type mobile body 100 based on the estimated unused time. Therefore, even during the unused time when the first user is not using the boarding type mobile body 100, an operation for utilizing the boarding type mobile body 100 can be determined, so that the boarding type mobile body 100 can be effectively utilized during the unused time.

Furthermore, the management server 400 of the embodiment determines the operation of the boarding type mobile body 100 to be on standby when the unused time is a short period of time that is equal to or shorter than the reference time. This makes it possible to prevent a situation in which the first user is unable to use the boarding type mobile body 100 due to a short unused time. Furthermore, the management server 400 of the embodiment determines the operation of the boarding type mobile body 100 to be an operation based on the execution list when the unused time exceeds the reference time. This makes it possible to determine an operation of the boarding type mobile body 100 that is appropriate for the length of the unused time.

The management server 400 of the embodiment also determines the operation of the boarding type mobile body 100 based on the remaining charge of the driving power of the boarding type mobile body 100. For example, when the remaining charge exceeds a predetermined value, the management server 400 of the embodiment determines the operation of the boarding type mobile body 100 to be to travel around the amusement facility P. In this case, a camera mounted on the boarding type mobile body 100 traveling around the amusement facility P captures images of the amusement facility P, and the captured images are displayed on the terminal device 200 of the user U, thereby providing the user with a simulated experience of traveling around the amusement facility P, thereby increasing the user's satisfaction.

In the embodiment of the mobile object management system 1, the control device 150 of the boarding type mobile object 100 is provided with the authentication processing unit 160 and the command generation unit 170, but some or all of these may be provided in the management server 400. For example, functions corresponding to the determination unit 171, the detection unit 172, and the generation unit 173 may be provided in the server control device 420 of the management server 400. In this case, the boarding type mobile object 100 or the terminal device 200 may transmit necessary electrical signals, such as a seating signal, a surrounding object signal, a request signal, etc., to the server communication device 410 of the management server 400. In addition, some or all of the functions of the server control device 420 may be provided in the control device 150 of the boarding type mobile object 100 or the terminal device 200.

In the above embodiment, it is assumed that the terminal device 200 has an application program (mobile body rental application) running, but the application program only needs to be running at least when the user U receives the rental of the boarding type mobile body 100. It is also preferable that the application program be running when the image of the boarding type mobile body 100 is displayed together with the AR image.

In the above embodiment, the user U is allowed to board and use the boarding type mobile body 100 by setting the usage rights for the user U in the boarding type mobile body 100, but the boarding type mobile body 100 may be allowed to be used by a user seated in the seat 113 without the usage rights being set. In particular, the boarding type mobile body 100 traveling around the amusement facility P may be allowed to be used without the usage rights being set.

In the above embodiment, the lending determination unit 426 determines whether the boarding type mobile body 100 is available for lending, but it may also determine whether the boarding type mobile body 100 is available for lending based on the intention of the first user. For example, when the lending determination unit 426 determines that the boarding type mobile body 100 is available for lending, it may transmit a lending confirmation signal to the terminal device 200 of the first user, and when the terminal device 200 returns a lending permission signal to the lending determination unit 426 due to the operation of the first user, the lending determination unit 426 may determine that the boarding type mobile body 100 is available for lending. The lending confirmation signal is a signal for requesting permission from the first user to lend the boarding type mobile body 100 to the second user. The lending permission signal is a signal indicating that the first user has given permission to lend the boarding type mobile body 100 in response to the lending confirmation signal.

Alternatively, for example, when a pre-rental permission signal is transmitted by the terminal device 200 to the lending determination unit 426 by operation of the first user, the lending determination unit 426 may be able to determine that lending is possible. The pre-rental permission signal is a signal that indicates in advance that the first user will permit lending of the boarding type mobile body 100 when a reservation of the boarding type mobile body 100 is made by the second user. The pre-rental permission signal may be provided to the lending determination unit 426 by means other than transmission by the terminal device 200.

In the above embodiment, the specified information is information on the usage rights set for the user U and the boarding type mobile body 100, but the specified information may be other information, for example, the stopping location where the boarding type mobile body 100 stopped when the user U disembarked. In this case, for example, if the stopping location is a specified location, such as near the on-site facility B, it is assumed that the user U will board the boarding type mobile body 100 again after using the on-site facility B. For this reason, for example, when the generation unit 173 detects the usage location of another person, it may generate an action command that executes an action such as notifying that a user who has already been set with usage rights cannot use the vehicle.

The specified time for determining whether the release condition is satisfied may be varied depending on the location where the boarding type vehicle 100 stops when the user U disembarks. For example, the specified time may be made longer if the on-site facility B is a popular attraction that is expected to take a long time to use, and the specified time may be made shorter if the on-site facility B is a facility where the purpose can be completed in a short time, such as a popcorn store.

In the above embodiment, no time limit is set for the usage rights set for user U, but a time limit may be set. Alternatively, user U may be set with the usage rights to exclusively use a specific boarding type mobile body 100. The usage rights to exclusive use may be set for one specific boarding type mobile body 100, or may be set according to the type of boarding type mobile body 100. For example, in a case where a specific character is depicted on only some of the boarding type mobile bodies 100 among the multiple boarding type mobile bodies 100 in the amusement facility P, the usage rights may be set for the boarding type mobile body 100 on which the specific character is depicted.

In the above embodiment, the terminal device 200 displays the boarding type mobile body 100 and executes AR display or the like to make it easier to find the boarding type mobile body 100 for which usage rights have been set. Furthermore, the terminal device 200 may, for example, display on the touch panel 210 a map of the amusement facility P and the position on the map of the parked boarding type mobile body 100.

The above-described embodiment can be expressed as follows.
A storage device storing a program;
a hardware processor;
The hardware processor executes the program stored in the storage device,
determining that the user has left the boarding type vehicle;
Detecting an intention of a person other than the user to use the boarding type vehicle;
When it is determined that the user has left the boarding type mobile object and the intention of the other person to use the boarding type mobile object is detected, an action command is generated to cause the boarding type mobile object to perform a predetermined operation based on setting information set for at least one of the user or the boarding type mobile object.
The control device for a boarding type moving body is configured as described above.

The above-described embodiment can be expressed as follows.
A storage device storing a program;
a hardware processor;
The hardware processor executes the program stored in the storage device,
Estimating a non-use time during which the first user will not be using the boarding type vehicle;
When there is a reservation from a second user different from the first user, it is determined that the boarding type mobile object can be rented to the second user when either a first condition that the second user's usage time of the boarding type mobile object is within the non-use time or a second condition that the second user's usage time of the boarding type mobile object exceeds the non-use time but there is another boarding type mobile object that can be provided to the first user after the non-use time has elapsed is satisfied.
The management device for a boarding type moving object is configured as described above.

The above-described embodiment can be expressed as follows.
A storage device storing a program;
a hardware processor;
The hardware processor executes the program stored in the storage device,
estimating a non-use time for which the user will not be using the boarding type vehicle according to a location when the user gets off the boarding type vehicle;
determining an operation of the ride-on type vehicle based on the estimated non-use time;
The management device for a boarding type moving object is configured as described above.

The above describes the form for carrying out the present invention using an embodiment, but the present invention is not limited to such an embodiment, and various modifications and substitutions can be made without departing from the spirit of the present invention.

1...mobile object management system 100...boarding type mobile object 110...airframe 111...cover panel 111A...landing legs 112...omnidirectional moving wheels 112A...large diameter wheels 112B...small diameter wheels 112C...turning wheels 113...seat 114...step 115...alarm device 120...communication device 130...vehicle position detection device 135...battery 140...sensor 141...seat sensor 142...periphery sensor 143...acceleration sensor 144...angular velocity sensor 145...remaining charge sensor 150...control device 160...authentication processing unit 161...authentication unit 162...release unit 163...adjustment unit 170...command generation unit 171...determination unit 172...detection unit 173...generation unit 174...center of gravity thrust Determination unit 175...balance control unit 180...motor control unit 190...alarm control unit 200...terminal device 210...touch panel 220...terminal communication unit 230...terminal control unit 240...terminal position detection unit 400...management server 410...server communication device 420...server control device 421...mobile object management unit 422...vehicle dispatch management unit 423...reception unit 424...estimation unit 425...decision unit 426...lending judgment unit 427...preparation control unit 428...granting unit 450...memory unit 451...reservation management list 452...lending management list 453...execution list MT1...first motor MT2...second motor MT3...third motor P...user P-IN...entrance entrance PP...parking pool U...user

Claims (8)

A management system for a boarding type vehicle that controls a boarding type vehicle on which a user boards, comprising:
an estimation unit that estimates a non-use time during which the user will not be using the boarding type vehicle according to a location when the user gets off the boarding type vehicle;
A decision unit that decides an operation of the riding type vehicle based on the estimated non-use time;
and a providing unit that provides the user with an image captured by a camera mounted on the boarding type moving body when the determined motion of the boarding type moving body is a motion of traveling around a predetermined area .
A management system for passenger-type mobile vehicles. the determination unit determines an operation of the riding type moving object to be on standby when the non-use time is equal to or shorter than a reference time.
The management system for a boarding type vehicle according to claim 1 . the determination unit determines, when the non-use time exceeds a reference time, an operation of the riding type moving body based on an execution list that is executable by the riding type moving body for each non-use time.
The management system for a boarding type mobile object according to claim 1 or 2. the determination unit determines the action to be performed by the user's own machine, which is the boarding type moving body used by the user, as well as an action to be performed by another machine, which is another boarding type moving body different from the user's own machine, within the specified area;
The management system for a boarding type mobile object according to claim 3 . The determination unit determines the operation of the riding type moving body further based on a remaining charge of driving power in the riding type moving body.
A management system for a boarding type mobile object according to any one of claims 1 to 4. the determination unit determines, when the remaining charge amount exceeds a predetermined value, the operation of the riding type moving object to be an operation of traveling within a predetermined area.
The management system for a boarding type vehicle according to claim 5 . The computer
estimating a non-use time during which the user will not be using the boarding type vehicle according to a location when the user gets off the boarding type vehicle;
determining an operation of the riding type vehicle based on the estimated non-use time ;
providing the user with an image captured by a camera mounted on the boarding type moving body when the determined motion of the boarding type moving body is a motion of traveling around a predetermined area;
A method for managing a passenger-type mobile object. On the computer,
estimating a non-use time during which the user will not be using the boarding type vehicle according to a location when the user gets off the boarding type vehicle;
determining an operation of the riding type vehicle based on the estimated non-use time ;
When the determined motion of the boarding type moving object is a motion of traveling around a predetermined area, an image captured by a camera mounted on the boarding type moving object is provided to the user.
program.

Images