Mobile object management device, mobile object management method, and program

Abstract

To provide a mobile body management device, a method for managing a mobile body, and a program that can more appropriately detect a person who pretends to be a legitimate user of the mobile body and uses the mobile body.SOLUTION: A mobile body management device according to an embodiment includes: a management unit for managing a boarding-type mobile body for a user to board and a terminal device of the user who boards the boarding-type mobile body in relation to each other; an operation instruction unit for causing the boarding-type mobile body to execute a predetermined operation on the basis of an instruction from the user to the boarding-type mobile body; and a determination unit for determining whether the user is a legitimate user on the basis of the skill level of the user according to the operation of the boarding-type mobile body the user is boarding.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a mobile body management device, a mobile body management method, and a program.

Background Art

[0002] Conventionally, there is a theft detection system that reports to a reporting center or the like when theft of a mobile body is detected (see, for example, Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, it has not been possible to appropriately detect the use of a mobile body by a person (other than a legitimate user) who pretends to be a legitimate user.

[0005] Aspects of the present invention have been made in consideration of such circumstances, and an object is to provide a mobile body management device, a mobile body management method, and a program that can more appropriately detect the use of a mobile body by a person who pretends to be a legitimate user.

Means for Solving the Problems

[0006] The mobile body management device, the mobile body management method, and the program according to this invention employ the following configuration. (1) A mobile device management device according to one aspect of the present invention comprises: a management unit that manages a rideable mobile device on which a user is riding and a terminal device of the user riding on the rideable mobile device in association with each other; an operation command unit that causes the rideable mobile device to perform a predetermined operation based on instructions from the user to the rideable mobile device; and a determination unit that determines whether the user is a legitimate user based on the user's level of proficiency in accordance with the operation of the rideable mobile device on which the user is riding.

[0007] (2): A mobile device management device according to another aspect of the present invention is a mobile device management device comprising: a management unit that manages a rideable mobile device on which a user is riding and a terminal device of the user riding in the rideable mobile device in association with each other; an operation command unit that causes the rideable mobile device to perform a predetermined operation based on instructions from the user to the rideable mobile device; and a determination unit that determines whether the user is a legitimate user based on characteristic information of the user's operation while riding in the rideable mobile device.

[0008] (3) In the embodiment of (1) or (2) above, the management unit restricts the control contents of the rideable mobile device that can be executed by the user using the rideable mobile device if the determination unit determines that the user is not a legitimate user.

[0009] (4) In the embodiment of (3) above, if the determination unit determines that the user is not a legitimate user, the management unit reduces the control contents of the rideable mobile body to less than the control contents that a legitimate user can execute, or stops the rideable mobile body.

[0010] (5) In any one of the embodiments of (1) to (4) above, the management unit instructs the operation command unit to move the rideable mobile body to a predetermined location if the determination unit determines that the user is not a legitimate user.

[0011] (6): In any one embodiment of (1) to (5) above, the management unit releases the restrictions on the control content of the rideable mobile body if, after the determination unit has determined that the user is not a legitimate user, the user is determined to be a legitimate user through a re-determination.

[0012] (7) In the embodiment of (1) above, the level of proficiency is determined based on the user's past usage history of the ride-on vehicle or the actions taken by the user during a predetermined time period after boarding the ride-on vehicle.

[0013] (8) In the embodiment of (2) above, the characteristic information of the operation is determined based on the user's past usage history of the rideable vehicle or the content of actions taken by the user during a predetermined time period after boarding the rideable vehicle.

[0014] (9): In any one embodiment of (1) to (8) above, the operation command unit causes the rideable mobile body to perform a predetermined action in response to the event via the user's terminal device, based on the location information of the rideable mobile body and information regarding an event to be carried out within a predetermined area, and the management unit restricts the user's participation in the event if the determination unit determines that the user is not a legitimate user.

[0015] (10): In any one embodiment of (1) to (9) above, if the determination unit determines that the user is not a legitimate user, information indicating that the user is not a legitimate user is notified to the terminal device and / or the passenger-type mobile vehicle.

[0016] (11): In any one of the embodiments of (1) to (10) above, if the determination unit determines that the user is not a legitimate user and the illegitimate user can be identified, the management unit imposes a predetermined penalty on the illegitimate user and / or the legitimate user.

[0017] (12): A mobile vehicle management method according to one aspect of the present invention is a mobile vehicle management method in which a computer manages a rideable mobile vehicle on which a user is riding and a terminal device of the user riding on the rideable mobile vehicle in association with each other, causes the rideable mobile vehicle to perform a predetermined operation based on instructions from the user to the rideable mobile vehicle, and determines whether the user is a legitimate user based on the user's level of proficiency in the operation of the rideable mobile vehicle on which the user is riding.

[0018] (13): A mobile vehicle management method according to another aspect of the present invention is a mobile vehicle management method in which a computer manages a passenger vehicle on which a user is riding and a terminal device of the user riding in the passenger vehicle, causes the passenger vehicle to perform a predetermined operation based on instructions from the user to the passenger vehicle, and determines whether the user is a legitimate user based on characteristic information of the user's operation while riding in the passenger vehicle.

[0019] (14): A program according to one aspect of the present invention causes a computer to manage a rideable mobile vehicle in which a user is riding and a terminal device of the user riding in the rideable mobile vehicle in association with each other, causes the rideable mobile vehicle to perform predetermined operations based on instructions from the user to the rideable mobile vehicle, and determines whether the user is a legitimate user based on the user's level of proficiency in the operation of the rideable mobile vehicle in which the user is riding.

[0020] (15): A program according to another aspect of the present invention is a program that causes a computer to manage a passenger vehicle in which a user is riding and a terminal device of the user riding in the passenger vehicle in association with each other, causes the passenger vehicle to perform a predetermined operation based on instructions from the user to the passenger vehicle, and determines whether the user is a legitimate user based on characteristic information of the user's operation while riding in the passenger vehicle. [Effects of the Invention]

[0021] According to the aspects (1) to (15) above, it is possible to more appropriately detect the use of the moving body by an outsider who has masqueraded as a legitimate user.

Brief Description of the Drawings

[0022] [Figure 1] It is a configuration diagram showing an example of the moving body management system 1 according to the embodiment. [Figure 2] It is a diagram for explaining the content of the user information 181. [Figure 3] It is a diagram for explaining the content of the event information 182. [Figure 4] It is a diagram showing an example of the functional configuration of the management unit 140. [Figure 5] It is a diagram for explaining the content of the control content change information 183. [Figure 6] It is a diagram showing an example of the content of the usage history information 184. [Figure 7] It is a diagram for explaining the content of the operation information 185. [Figure 8] It is a configuration diagram showing an example of the terminal device 200 of the embodiment. [Figure 9] It is a perspective view showing the appearance of the on-vehicle moving body 300 of the embodiment. [Figure 10] It is a perspective view of the omnidirectional moving wheel 312. [Figure 11] It is a diagram for explaining the details of the operation of the omnidirectional moving wheel 312 of the on-vehicle moving body 300. [Figure 12] It is a configuration diagram showing an example of the on-vehicle moving body 300 of the embodiment. [Figure 13] It is a sequence diagram showing an example of the process to be executed by the moving body management system 1. [Figure 14] It is a diagram showing a specific example of the moving body management of the on-vehicle moving body 300. [Figure 15] It is a diagram showing an example of the image IM10 provided to the user U who participated in the event. [Figure 16] It is a diagram showing an example of the image IM20 for notifying the impersonation determination result. [Modes for carrying out the invention]

[0023] The following describes embodiments of the mobile object management device, mobile object management method, and program of the present invention with reference to the drawings. In the following description, a mobile object management system including a rideable mobile object that carries a user and moves within a predetermined area will be described as an example. The predetermined area is, for example, the area of ​​a facility having a predetermined size, such as a theme park, leisure land, amusement park, zoo, aquarium, or shopping mall. Alternatively, the predetermined area may be an area within a range specified by location information such as latitude and longitude.

[0024] [System Configuration] Figure 1 is a configuration diagram showing an example of a mobile vehicle management system 1 according to an embodiment. The mobile vehicle management system 1 includes, for example, a mobile vehicle management server 100, terminal devices 200-1 to 200-n for a plurality of users U1 to Un (where n is 2 or more), and passenger-type mobile vehicles 300-1 to 300-n on which each of the users U1 to Un rides. Hereinafter, unless each of the users U1 to Un is described separately, they will simply be referred to as "user U". Similarly, the terminal devices 200-1 to 200-n and the passenger-type mobile vehicles 300-1 to 300-n will be referred to as "terminal device 200" and "passenger-type mobile vehicle 300" respectively. The mobile vehicle management server 100 and the terminal devices 200 can communicate with each other, for example, via a network NW. The network NW includes, for example, the Internet, WAN (Wide Area Network), LAN (Local Area Network), telephone lines, public lines, dedicated lines, provider equipment, wireless base stations, etc. The mobile device management server 100 is an example of a "mobile device management device." Furthermore, the terminal device 200 and the passenger mobile device 300 can communicate with each other based on, for example, Wi-Fi®, Bluetooth®, or other short-range wireless communication standards. The passenger mobile device 300 may also communicate with the mobile device management server 100 via a network NW.

[0025] The mobile device management server 100 manages users U who use the passenger mobile device 300 and controls the operation of the passenger mobile device 300. The mobile device management server 100 also manages the passenger mobile device 300 in association with the terminal device 200 of user U. Furthermore, the mobile device management server 100 detects use by others who are impersonating legitimate users of the passenger mobile device 300 and imposes restrictions on the use of detected others (restrictions on the operation of the passenger mobile device 300). A legitimate user is, for example, a user associated with a terminal device 200 that communicates with the passenger mobile device 300 and who has been authorized by the mobile device management server 100 to use the passenger mobile device 300.

[0026] The terminal device 200 is, for example, a portable device that user U can carry while boarding the rideable mobile vehicle 300, and specifically, is a smartphone or tablet device. Alternatively, the terminal device 200 may be a wearable device worn by user U. The terminal device 200 is a terminal device owned by user U.

[0027] The rideable mobile device 300 is a mobile device that carries user U and moves within a predetermined area. The rideable mobile device 300 is, for example, a device provided (lent) by the service provider in the mobile device management system 1 for user U to move within a predetermined area. For example, the rideable mobile device 300 is a vehicle, micromobility, robot, etc., that can move with user U seated on a seat or standing on steps. The rideable mobile device 300 moves within a predetermined area with user U on board or performs predetermined actions based on operation commands based on user U's operation or operation commands from the mobile device management server 100. Predetermined actions include, for example, music output in connection with an event held in the predetermined area or actions that match the actions of objects related to the event (e.g., movement or rotation). Predetermined actions may also include actions that output sound from an audio output unit provided on the rideable mobile device 300 or actions that illuminate a light-emitting unit provided on the rideable mobile device 300. The rideable mobile device 300 may guide the user U to perform a predetermined action based on the user U's actions, or it may output information (e.g., voice) to prompt the user U to take action, or it may perform a predetermined action regardless of the user U's actions.

[0028] Events include, for example, parades that march along a predetermined route within a predetermined area at a predetermined time, and shows (for example, theatrical performances, concerts, etc.) held at a specific location within a predetermined area at a predetermined time. Events may also include, for example, events (group events) that occur when a predetermined number of rideable mobile vehicles 300 gather within a specific range within a predetermined area. Objects related to the event include, for example, people participating in the event (mascot characters, musicians, dancers, dolls, and other cast members) and mobile vehicles (parade cars, drones), etc. User U can use the rideable mobile vehicle 300 within the predetermined area by, for example, registering with the mobile vehicle management server 100 via a terminal device 200. The details of the mobile vehicle management server 100, terminal device 200, and rideable mobile vehicle 300 will be described below. Furthermore, the following description assumes that the predetermined area is a theme park.

[0029] [Mobile device management server] The mobile device management server 100 shown in Figure 1 includes, for example, a communication unit 110, a registration unit 120, an acquisition unit 130, a management unit 140, a determination unit 150, an operation selection unit 160, an operation command unit 170, and a storage unit 180. The registration unit 120, acquisition unit 130, management unit 140, determination unit 150, operation selection unit 160, and operation command unit 170 are implemented, for example, by a hardware processor such as a CPU (Central Processing Unit) executing a program (software). Furthermore, some or all of these components may be implemented by hardware (including circuitry) such as LSI (Large Scale Integration), ASIC (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), and GPU (Graphics Processing Unit), or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD (Hard Disk Drive) or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium), and installed on the storage device of the mobile device management server 100 when the storage medium is mounted on a drive device or the like. The mobile device management server 100 may, for example, function as a cloud server that communicates with terminal devices 200 via a network NW and sends and receives various data.

[0030] The memory unit 180 may be implemented using the various storage devices mentioned above, or an SSD (Solid State Drive), EEPROM (Electrically Erasable Programmable Read Only Memory), ROM (Read Only Memory), or RAM (Random Access Memory). The memory unit 180 stores, for example, user information 181, event information 182, control content change information 183, usage history information 184, operation information 185, programs, and various other information. The memory unit 180 may also store map information of the theme park. Details of user information 181, event information 182, control content change information 183, usage history information 184, and operation information 185 will be described later.

[0031] The communication unit 110 communicates with the terminal device 200 and other external devices via the network NW.

[0032] The registration unit 120 registers information about user U who uses the mobile device management system 1. Specifically, the registration unit 120 receives information about user U from the terminal device 200 and stores the received information in the user information 181 of the storage unit 180.

[0033] Figure 2 is a diagram illustrating the contents of user information 181. User information 181 is information that associates authentication information used to authenticate user U when using the mobile device management system 1, such as address, name, age, gender, terminal information, mobile device information, proficiency level, and operational characteristic information. Authentication information includes, for example, identification information (e.g., user ID) and password to identify user U. Authentication information may also include biometric authentication information such as fingerprint information and iris information. Terminal information includes, for example, identification information (e.g., terminal ID) to identify the terminal device 200 that user U possesses within the theme park, as well as telephone number, email address, etc. Mobile device information includes, for example, identification information (e.g., mobile device ID) to identify the mobile device 300 that is communicating with user U's terminal device 200 using a short-range wireless communication method such as Bluetooth. The mobile device management server 100 communicates with terminal devices 200 based on terminal information, identifies the rideable mobile device 300 based on rideable mobile device information, and generates individual operation commands. Proficiency is, for example, an index value that quantitatively represents how familiar user U is with using (operating) the rideable mobile device 300. Operational characteristic information is, for example, characteristic information of user U regarding the operation of the rideable mobile device 300, and includes information about user U's habits regarding how weight is distributed (how the center of gravity is shifted), how the brakes are applied, how acceleration and deceleration are performed, and the trajectory when driving around curves. Proficiency and operational characteristic information are managed by the management unit 140, which will be described later. In addition, user information 181 may also include information such as the terminal information and rideable mobile device information of related users (for example, parent and child or friend). In addition, user information 181 may store the level of eligibility to participate in events, which will be described later, instead of (or in addition to) proficiency.

[0034] For example, when the registration unit 120 receives a user registration request from the terminal device 200, it generates an image for inputting various information contained in the user information 181, displays it on the terminal device 200 that received the request, and acquires the user information input from the terminal device 200 and registers it in the user information 181.

[0035] Furthermore, the registration unit 120 may authenticate user U who will use the services of the mobile device management system 1 based on the registered user information 181. In this case, the registration unit 120 authenticates user U, for example, when it receives a service usage request from the terminal device 200. For example, when the registration unit 120 receives a usage request, it generates an authentication image into which authentication information such as a user ID and password is entered, displays the generated image on the requesting terminal device 200, and uses the displayed image to refer to the authentication information in the user information 181 based on the input authentication information, and determines whether or not to allow the use of the service depending on whether or not authentication information matching the input authentication information is stored therein. For example, if the user information 181 contains authentication information matching the input authentication information, the registration unit 120 allows the user to use the service as a legitimate user, and if no matching information is included, it either rejects the use of the service or performs a process to require new registration.

[0036] The acquisition unit 130 acquires information about the rideable mobile vehicle 300 on which user U is riding. For example, when terminal device 200 is communicating with rideable mobile vehicle 300 using a short-range communication method such as Bluetooth, the acquisition unit 130 acquires identification information of the rideable mobile vehicle 300 being communicated with (e.g., mobile vehicle ID), identification information of terminal device 200 (e.g., terminal ID), and user ID from terminal device 200. Then, based on the user ID, the acquisition unit 130 refers to the user ID in user information 181, stores the terminal ID in the terminal information associated with the matching user ID, and stores the mobile vehicle ID in the rideable mobile vehicle information. By repeatedly performing the above process at predetermined timings (e.g., predetermined cycles), the mobile vehicle management server 100 can manage the usage status of the rideable mobile vehicle 300.

[0037] Furthermore, the acquisition unit 130 acquires information about events held within the theme park. For example, the acquisition unit 130 acquires event information 182, which has been previously stored in the storage unit 180, as information about the event.

[0038] Figure 3 is a diagram illustrating the contents of event information 182. Event information 182 is information that associates, for example, an event ID with event details, location / route information, implementation time, and participation conditions. The event ID is identification information for identifying an event held within the theme park. Event details include, for example, the event title, type (parade, show), number of cast members, music, and participating cast members. Location / route information includes, for example, information about the location within the theme park where the event is held and the route the parade will take. In addition, at least one of the event details and location / route information may include information about music and lights output in connection with the event, and the movement of objects related to the event (what kind of movement occurs at what point). Implementation time includes information about the time of day, day of the week, and period during which the event is held. Participation conditions are, for example, information about the conditions under which a user U using a rideable mobile device 300 can participate in the event. For example, participation conditions may include the user's participation level and the number of participants allowed according to that level. Furthermore, the participation requirements may include the minimum participation level required to dance with a specific character participating in the event, as well as the maximum number of participants. The participation requirements may also be changed for specific periods (e.g., Christmas or a user's birthday) or seasons (summer, winter). Each piece of information included in the event information 182 may be obtained, for example, from an external device connected to the network NW, or it may be directly entered by the server administrator from the mobile device management server 100.

[0039] Furthermore, the acquisition unit 130 acquires location information of a terminal device 200 belonging to a user U who is aboard the rideable mobile vehicle 300 (in other words, a terminal device 200 that is communicating with the rideable mobile vehicle 300 using a short-range wireless communication method), and acquires the acquired location information as the location information of the rideable mobile vehicle 300. The acquisition unit 130 repeatedly acquires the location information at predetermined intervals while the terminal device 200 and the rideable mobile vehicle 300 are communicating.

[0040] The management unit 140 manages the entire mobile object management process in the mobile object management system 1. Figure 4 shows an example of the functional configuration of the management unit 140. The management unit 140 includes, for example, a user management unit 141, an event management unit 142, a participant management unit 143, and an incentive management unit 144.

[0041] The user management unit 141 manages the association between the rideable mobile vehicle 300 and the terminal device 200 of user U who is riding in the rideable mobile vehicle 300, for example, based on user information 181. The user management unit 141 also manages the usage status of the rideable mobile vehicle 300 for each user U (for example, which rideable mobile vehicle 300 user U is currently riding in) based on user information 181. The user management unit 141 also manages the location of the rideable mobile vehicle 300 within the theme park based on the information acquired by the acquisition unit 130. Furthermore, if certain users (for example, parent and child or friends) are associated with each other in user information 181, the user management unit 141 may also manage the location information of each other's terminal devices 200 and rideable mobile vehicle 300.

[0042] Furthermore, the user management unit 141 manages the user U's proficiency in driving the rideable mobile vehicle 300 (hereinafter referred to as "user U's proficiency"). Proficiency is determined, for example, based on the number of rotations of the rideable mobile vehicle 300 in a predetermined time period operated by the user, the distance from a predetermined speed to a complete stop (sudden stop), and whether or not predetermined driving maneuvers (for example, straight-line driving or figure-eight driving). Proficiency may also be set, for example, based on the degree of wobbling of the rideable mobile vehicle 300 operated by the user and the frequency of input operations during turns (for example, the number of corrections made when leaning the body to turn at a certain curvature, if the vehicle turns more or less than expected). The degree of wobbling and the frequency of input operations during turns are obtained, for example, based on the detection results of an attitude angle sensor provided on the rideable mobile vehicle 300. Furthermore, regarding the degree of wobbling and the acquisition of proficiency, for example, the technology described in Japanese Patent Publication No. 2011-68216 filed by the present applicant may be used. In addition, the user management unit 141 may determine the proficiency of user U by comparing the operation content of the rideable mobile body 300, such as how to shift the center of gravity, how to apply the brakes, how to accelerate and decelerate, and the trajectory when traveling around curves, with predetermined operation content for each proficiency level (operation level at which operation is judged to be possible).

[0043] For example, the user management unit 141 retrieves the past usage history of user U's rideable mobile device 300 from the usage history information 184 stored in the memory unit 180, and determines user U's proficiency level based on the operation content included in the retrieved usage history and the operation content for each predetermined proficiency level. In this case, the proficiency level is determined by the user's operation level at the time of event participation (determined by the operation content of the rideable mobile device 300).

[0044] Furthermore, the user management unit 141 may acquire the actions performed by user U during a predetermined time period after boarding the rideable mobile device 300, and determine the proficiency level based on the acquired actions. Alternatively, the user management unit 141 may instruct user U to perform predetermined actions (e.g., acceleration, deceleration, cornering) while boarding the rideable mobile device 300, and determine the proficiency level based on those actions. In this case, the proficiency level is determined by the user's current operating level.

[0045] Furthermore, the user management unit 141 may adjust the proficiency level according to the number of times and duration of use of the rideable mobile device 300 by user U. For example, the user management unit 141 increases the proficiency value as the number of times or duration of use increases. Note that the number of times and duration of use may be replaced (or added) with the number of times or duration of participation in events.

[0046] Furthermore, the user management unit 141 refers to the control content change information 183 stored in the memory unit 180 and changes the control content of the rideable mobile vehicle 300 permitted to user U according to the user U's proficiency level. Figure 5 is a diagram illustrating the contents of the control content change information 183. The control content change information 183 is, for example, information that associates control content with proficiency level. In the example in Figure 5, the higher the proficiency value, the more control content (driving content) of the rideable mobile vehicle 300 permitted to user U, or the more restrictions on operation content are removed. For example, a user with a proficiency level of 1 is permitted only to drive slowly and stop, while a user with a proficiency level of 2 is permitted to drive slowly, stop, and rotate slowly. In this way, by determining the control content of the rideable mobile vehicle 300 for user U according to the user U's proficiency level, the rideable mobile vehicle 300 can be used more safely by the user.

[0047] Furthermore, the user management unit 141 may acquire characteristic information about user U's operations instead of (or in addition to) proficiency, and determine the control content permitted to user U based on the acquired characteristic information about user U's operations. The characteristic information about operations may be acquired from the usage history information 184 stored in the storage unit 180, from the content of actions taken by user U for a predetermined time after starting to board the rideable mobile vehicle 300, or by instructing user U to perform a predetermined action when boarding the rideable mobile vehicle 300. The user management unit 141 may also determine proficiency based on the characteristic information about user U's operations. The user management unit 141 stores the updated information in the user information 181 each time the proficiency level or characteristic information of user U is updated.

[0048] Furthermore, the user management unit 141 may change the control content (operation content of the rideable mobile vehicle 300) permitted to user U based on the determination result by the determination unit 150, which will be described later. For example, if the determination unit 150 determines that the user riding in the rideable mobile vehicle 300 is not a legitimate user, the user management unit 141 will restrict the control content of the rideable mobile vehicle 300 that the user using the rideable mobile vehicle 300 can execute. Restricting the control content may include, for example, making the control content of the rideable mobile vehicle 300 less than the control content that a legitimate user can execute, or stopping the rideable mobile vehicle 300. Also, if the determination unit 150 determines that the user is not a legitimate user, the user management unit 141 may release the restriction on the control content of the rideable mobile vehicle 300 if the determination unit 150 determines that the user is a legitimate user after a re-determination. Furthermore, if the determination unit 150 determines that the user is not a legitimate user, the user management unit 141 may instruct the operation command unit 170 to move the rideable mobile vehicle 300 to a predetermined location such as a management facility.

[0049] The event management unit 142 manages the event schedule based on the event information 182 stored in the memory unit 180. The event management unit 142 also refers to the event information 182 to obtain information about events to be held within a predetermined time from the present moment, and transmits the content of the obtained events and information about the route and location where the events will be executed to the terminal device 200 to notify user U. The event management unit 142 also determines the content of the events to notify user U according to user U's level of event participation, which is determined by the usage status of user U's rideable mobile device 300. Usage status includes, for example, at least one of the number of times user U has used the rideable mobile device 300 and the usage time. In addition to the number of times and usage time, the usage status may also include information about user U's proficiency with the rideable mobile device 300. The participation level may be set, for example, based on user U's proficiency and operational characteristic information, or instead of (or in addition to) proficiency and operational characteristic information, it may be set according to the number of times or duration of participation in events.

[0050] The participation management unit 143 manages whether user U can participate in an event, for example, based on the usage status of the user's rideable vehicle 300. For example, the participation management unit 143 prevents user U who does not meet the event participation requirements from participating in that event, prevents user U from participating in events that exceed their participation level, and restricts participation in events that user U was previously eligible to participate in based on the time elapsed since the last event participation and / or the time elapsed since the last rideable vehicle 300. In addition, the participation management unit 143 manages, for example, not to send event announcements or inquiries about event participation to user U who is below the participation level set in the event participation requirements.

[0051] Furthermore, the participant management unit 143 manages the users U who participate in each event based on the information stored in the event information 182, and manages the details of each user U's participation (for example, their position in a parade or their performance actions). In addition, the participant management unit 143 adjusts the number of participating users so that it is less than or equal to the number of participants if the number of users wishing to participate exceeds the number of participants, based on factors such as lottery or priority, if the number of users wishing to participate exceeds the number of participants. Furthermore, after a user U participates in an event, the participant management unit 143 updates the number of times and usage time of the user U's rideable mobile device 300, and updates the participation level according to the number of times and usage time. The participant management unit 143 stores the above information as usage history information 184 in the storage unit 180.

[0052] Figure 6 shows an example of the contents of the usage history information 184. The usage history information 184 is information that associates, for example, the number of uses, usage time, participation level, and executable performance actions with the user ID. The number of uses is the number of times the rideable mobile device 300 has been used. For example, when the rideable mobile device 300 moves a predetermined distance or more while the user U's terminal device 200 and the rideable mobile device 300 are connected via short-range communication, the number of uses is counted as 1. The number of uses may also be the number of times the user U participated in an event while riding the rideable mobile device 300 (number of participations). Alternatively, the number of uses may be the number of participations for each event. The usage time is the time spent riding the rideable mobile device 300. For example, the time when the user U's terminal device 200 and the rideable mobile device 300 are connected via short-range communication is considered the time spent riding the rideable mobile device 300. The usage time may also be the time the user U participated in an event while riding the rideable mobile device 300 (participation time). Furthermore, the usage time may be the time spent participating in each event, or it may be date and time information (e.g., year, month, and day, start time of use, end time of use). The participation level is the level at which participation in an event becomes possible, which is determined, for example, by at least one of the number of uses and the usage time. The executable performance actions are performance actions that can be performed during an event, which are set according to the participation level. Performance actions include, for example, outputting light or sound, following event characters, rotating, and coordinating with surrounding characters or other mobile objects. Performance actions may also include information about the events in which participation has become possible, as well as information about the user's position when participating in a parade or show, and information about the character the user is playing. In addition to the above information, the usage history information 184 may also include information about the operations performed by user U on the rideable mobile object 300 (e.g., number of rotations in a predetermined time, sudden braking, straight-line driving, figure-eight driving, degree of wobbling, frequency of input operations during turns, etc.), proficiency level, and operation characteristic information.

[0053] The participation management unit 143 increases the participation level as the number of uses increases or the usage time increases. The participation management unit 143 may also increase the participation level if the number of uses exceeds the first threshold and the usage time exceeds the second threshold. In this case, the participation management unit 143 increases the first and second thresholds as the level increases. The participation management unit 143 also determines the performance actions that can be performed by the user U's rideable mobile body 300 according to the set participation level and stores and manages them in the usage history information 184. For example, the participation management unit 143 allows for a greater variety of performance actions or enables performance actions with faster rotation or movement speeds as the participation level increases. For example, since the event information 182 includes the participation level as a condition for participation in each event, as the user U's participation level increases, the number of events that user U can participate in increases, and the number of performance actions that can be performed by the rideable mobile body 300 increases. Therefore, by leveling up, user U can participate in desired events and perform desired actions, which further increases their motivation to participate in events.

[0054] Furthermore, the participation management unit 143 may restrict user U's participation in events that user U was previously able to participate in, based on at least one of the elapsed time since user U last participated in an event (hereinafter referred to as the first elapsed time) and the elapsed time since user U last boarded the rideable mobile device 300 (hereinafter referred to as the second elapsed time). In this case, the participation management unit 143 may, for example, derive the first and second elapsed times from the usage time (last usage end time) included in the usage history information 184, and restrict user U from participating in events that user U was previously able to participate in by lowering the level of user U's participation as the first and / or second elapsed times become longer. In addition, the participation management unit 143 may restrict user U from participating in the event with event ID "E001" that user U was previously able to participate in if the first elapsed time is longer than a predetermined time, or restrict user U from participating in the events with event IDs "E002" to "E003" that user U was previously able to participate in if the second elapsed time is longer than a predetermined time. Furthermore, the participation management unit 143 may increase the first and second thresholds mentioned above as the first and / or second elapsed time increases, making it more difficult to raise the level, and adjusting so that the number of uses and usage time required to raise the level increase (lengthen). In addition, the participation management unit 143 may adjust the proficiency level of user U according to the results of the adjustment of the participation level as described above. For example, the participation management unit 143 may lower the proficiency level if user U has had a predetermined gap (interval) since boarding the rideable mobile device 300.

[0055] In this way, if user U has had a gap in their participation in events or riding the rideable mobile device 300, the safety of user U can be further improved by restricting the events they can participate in and the operations of the rideable mobile device 300 until they become accustomed to riding the rideable mobile device 300 (until they regain their sense of it). Furthermore, because user U will be more motivated to participate in events and ride the rideable mobile device 300 without being subject to the aforementioned restrictions, the utilization rate of the rideable mobile device 300 can be improved.

[0056] Furthermore, the participation management unit 143 may update the user U's proficiency level based on the operation details of the rideable mobile device 300 included in the usage history information 184, or set participation levels that include proficiency in addition to the number of uses and usage time mentioned above. The participation management unit 143 may also notify user U by sending information regarding the participation level for each user U, as well as information to raise the level or prevent the level from dropping, to user U's terminal device 200.

[0057] The incentive management unit 144 manages incentives to be given to service providers, such as providers of the rideable mobile vehicles 300 lent to user U and event planners. In this case, incentives are, for example, equivalent to service usage fees. Service usage fees may be collected from theme park admission fees, or collected via user U's terminal device 200 when using the rideable mobile vehicle or participating in an event. The incentive management unit 144 may also manage incentives given to user U who participate in an event. In this case, incentives may be, for example, preferential use of a preferred rideable mobile vehicle 300, discounts on rental fees for rideable mobile vehicles 300, or the awarding of reward points.

[0058] Furthermore, if the Incentive Management Unit 144 can identify another person who has used the passenger vehicle 300 by impersonating a legitimate user, it may impose a prescribed penalty on that person, such as requiring them to pay a fine, prohibiting them from using the passenger vehicle 300 for a prescribed period, or preventing them from participating in an event. This can deter the subletting of the passenger vehicle 300. In addition, the prescribed penalty may be imposed not only on (or on behalf of) the aforementioned other person, but also on the legitimate user whose passenger vehicle 300 has been used by another person. This allows for the imposition of a penalty on a legitimate user who intentionally engages in subletting, and also makes the legitimate user aware of the situation even if they have been unintentionally impersonated.

[0059] For example, if the determination unit 150 determines that a user using the rideable mobile device 300 is not a legitimate user, the incentive management unit 144 acquires one or more terminal devices 200 that are located within a predetermined distance from the rideable mobile device 300 and move in conjunction with the movement of the rideable mobile device 300. Then, if one of the acquired terminal devices 200 is the terminal device of a legitimate user, the incentive management unit 144 identifies the other terminal devices as terminal devices of illegitimate users and compares the information of those terminal devices with the terminal information in the user information 181 to identify the illegitimate user.

[0060] The determination unit 150 determines whether the user using the rideable mobile device 300 is a legitimate user. For example, a user who has not reached the participation level required to participate in an event (hereinafter referred to as "another person") may borrow (or steal) a legitimate user's terminal device 200 or rideable mobile device 300 in order to participate in the event. In this case, because the other person has not reached the participation level required to participate in the event, they may not be able to perform appropriate driving operations according to the event, and some kind of trouble or accident may occur, such as colliding with the rideable mobile device 300 or other objects in the vicinity or tipping over.

[0061] Therefore, the determination unit 150 determines the level of proficiency based on, for example, the degree of swaying and the operation content (for example, the movement and stability of the rideable mobile 300) during a predetermined time at the start of the ride of the currently using user, and compares the determined level of proficiency with the level of proficiency of a legitimate user obtained from user information 181 to determine whether the currently using user is a legitimate user (whether someone else is impersonating a legitimate user). For example, the determination unit 150 determines whether the currently using user is able to perform the control content corresponding to the level of proficiency obtained from user information 181. For example, if the level of proficiency of a legitimate user is 4, the determination unit 150 obtains the result when the currently using user performs a rotation operation, whether or not the rotation operation is possible, and the degree of swaying during the rotation operation, and if the obtained content does not meet the pre-set proficiency level "4", it determines that the user is not a legitimate user (someone else is impersonating a legitimate user). Furthermore, if the acquired data meets the proficiency level "4" criteria, it will be determined that the data is being used by a legitimate user.

[0062] Alternatively, the determination unit 150 may, instead of (or in addition to) proficiency, compare the characteristic information of legitimate user operations stored in user information 181 with the characteristic information of operations obtained from the actual operations of the currently using user to determine whether the currently using user is a legitimate user (whether or not they are another person). In this case, the determination unit 150 determines that the currently using user is not a legitimate user if the difference between the characteristic information of the currently using user and the characteristic information of a legitimate user is greater than or equal to a threshold, and determines that the user is a legitimate user if the difference is less than a predetermined threshold.

[0063] If the determination unit 150 determines that the currently using the system is a legitimate user, it allows the user to participate in events according to their proficiency level (or level of participation). If the determination unit 150 determines that the currently using the system is not a legitimate user (i.e., someone impersonating a legitimate user), it instructs the management unit 140 to implement controls such as restricting the use of the rideable mobile device 300.

[0064] For example, if the user management unit 141 of the management unit 140 determines that the user is not a legitimate user, it outputs command information to the operation command unit 170 to restrict the actions that the rideable mobile device 300 can perform or to stop the rideable mobile device 300. Restricting the actions means, for example, restricting the rideable mobile device 300 to perform only basic actions (for example, the control actions when the proficiency level is 1 as shown in the control action change information 183 (beginner mode)) or limiting the actions to fewer actions than a legitimate user can perform.

[0065] Furthermore, if the determination unit 150 determines that the user is not a legitimate user, the user management unit 141 may output command information to the operation command unit 170 to move (escort) the rideable mobile body 300 to a designated location such as a management facility. In addition, if the determination unit 150 determines that the user is not a legitimate user, the user management unit 141 may restrict participation in events. In this case, the user management unit 141 controls the system so that a legitimate user is unable to participate in an event they wish to attend.

[0066] In this way, based on the judgment results from the judgment unit 150, it is possible to detect with high accuracy others who are impersonating legitimate users, thereby suppressing the possibility of any trouble or accident occurring during the event. Furthermore, by properly managing the use by legitimate user U, it is possible to further improve user U's willingness to participate in the event (willingness to use the rideable mobile device 300).

[0067] Furthermore, if the determination unit 150 determines that a user is not a legitimate user, the user management unit 141 may notify the terminal device 200 communicating with the passenger mobile vehicle 300 and / or the passenger mobile vehicle 300 of information indicating that the user has been determined not to be a legitimate user. This allows the user riding in the passenger mobile vehicle 300 to understand that the operation of the passenger mobile vehicle 300 is restricted because the user has been determined not to be a legitimate user. In addition, if the user management unit 141 determines that a user is not a legitimate user, it may also report the location information of the passenger mobile vehicle 300 to a management center or the like.

[0068] The operation selection unit 160 selects the content of a predetermined operation to be performed by the rideable mobile device 300 based on the location information of the rideable mobile device 300 located within the theme park and information regarding events held within the theme park. For example, the operation selection unit 160 refers to user information 181 and event information 182 stored in the storage unit 180 and selects an operation to be performed by the rideable mobile device 300 for each user U based on the distance between the location where the event is held (including locations along the route) and the rideable mobile device 300, the duration of the event, the participation level of user U participating in the event, and the participation content specified by user U.

[0069] For example, if an event is taking place and the distance between the event location and the rideable mobile vehicle 300 on which user U is riding is within a predetermined distance, the motion selection unit 160 selects a predetermined motion corresponding to the event-specific performance to be performed by the rideable mobile vehicle 300. Alternatively, the motion selection unit 160 may select a predetermined motion to be performed by the rideable mobile vehicle 300 based on the distance between the event-related object and the rideable mobile vehicle 300, provided that the distance between the object and the rideable mobile vehicle 300 is within a predetermined distance. Furthermore, the motion selection unit 160 may select a motion for each of the rideable mobile vehicles 300 located within a specific range, depending on the number of rideable mobile vehicles 300 located within that specific range below the theme park area. The specific range includes, for example, predetermined zones such as adventure areas and park areas within the theme park, or ranges within a predetermined distance centered on the event-related object. The motion selection unit 160 may also select a predetermined motion to be performed based on a combination of several of the above-mentioned conditions for selecting motions.

[0070] When specifically selecting the content of a predetermined operation, the operation selection unit 160 refers to the event ID of the operation information 185 based on the event ID of the target event that satisfies the conditions among the event information 182, and determines the specific content of the predetermined operation to be performed by the target rideable mobile body 300 based on the information associated with the matching event ID.

[0071] Figure 7 is a diagram illustrating the contents of the operation information 185. The contents of the operation information include, for example, music, light emission, or performance actions that are synchronized with the movement of objects related to the event. Operation information 185 is, for example, information that associates the event ID with performance action content and adjustment information. The performance action content includes the operation content of the rideable mobile body 300. The performance action content may be set for each participation level set for each event. In the example in Figure 7, when the event ID is "E001" and the participation level is 20 or higher, the performance actions shown include rotating the rideable mobile body 300 in sync with the music emitted during the event, and when the event ID is "E002", sound is emitted and light emission is performed.

[0072] Adjustment information is, for example, information used to adjust a part of an action set in the operation content according to information about the user U and the surrounding environment. Information about the user U is information obtained from user information 181 (e.g., age, gender). Information about the surrounding environment is information obtained from event information 182 (e.g., location / route information, time of implementation). In the example in Figure 7, the adjustment information shows that the rotation speed is reduced if the user is under 12 years old, the light-emitting part is blinked if the time of day is daytime (e.g., 10:00 to 17:59), and the light intensity of the light-emitting part is increased if the time of day is nighttime (18:00 to 21:00). Note that the performance operation content and adjustment information are not limited to the example in Figure 7. Furthermore, for various events, performance operations such as the movement (rotation, etc.), sound output, and light emission of the rideable mobile body 300, or a combination of all of these, may be set.

[0073] The operation command unit 170 generates an event operation command for the target rideable mobile body 300 based on the operation content determined (selected) by the operation selection unit 160. For example, the operation command unit 170 generates an operation command to cause a rideable mobile body 300, which is on which user U participating in the event is riding, and which is within a predetermined distance from the event location at the time the event is being held, to perform a predetermined event operation. The operation command unit 170 may also adjust the content of the event operation (including the degree of the operation) based on adjustment information, or it may adjust the content of the event operation based on the settings (adjustment information) of user U obtained from the terminal device 200.

[0074] The operation command unit 170 acquires terminal information of the terminal device 200 of user U who is riding the target rideable mobile vehicle 300, based on the terminal information of user information 181, and transmits a generated or adjusted operation command to the terminal device 200 based on the acquired terminal information. In addition to (or instead of) the operation command, the operation command unit 170 may also transmit area (theme park) map information, etc., to the terminal device 200.

[0075] Furthermore, if the user currently using the rideable mobile device 300 is not a legitimate user (i.e., someone is impersonating a legitimate user), the operation command unit 170 controls the rideable mobile device 300 based on an operation command from the user management unit 141, restricting its operation or causing it to move to a designated location such as a management facility.

[0076] [Terminal device] Next, the configuration of the terminal device 200 will be described. Figure 8 is a configuration diagram showing an example of the terminal device 200 of the embodiment. The terminal device 200 includes, for example, a terminal-side communication unit 210, an input unit 220, an output unit 230, a location information acquisition unit 240, an application execution unit 250, an output control unit 260, and a terminal-side storage unit 270. The location information acquisition unit 240, the application execution unit 250, and the output control unit 260 are realized, for example, by a hardware processor such as a CPU executing a program (software). Furthermore, some or all of these components may be realized by hardware (including circuitry) such as LSIs, ASICs, FPGAs, and GPUs, or by the cooperation of software and hardware. The program may be stored in advance on a storage device such as an HDD or flash memory (a storage device equipped with a non-transient storage medium), or it may be stored on a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed on the storage device of the terminal device 200 when the storage medium is inserted into a drive device or card slot.

[0077] The terminal-side storage unit 270 may be implemented using the various storage devices described above, or by EEPROM, ROM, RAM, etc. For example, the terminal-side storage unit 270 stores the mobile device management application 272, programs, and various other information. The terminal-side storage unit 270 may also store user information such as terminal ID and user ID, or map information obtained from the mobile device management server 100, etc.

[0078] The terminal-side communication unit 210 communicates with the mobile management server 100, the passenger mobile unit 300, and other external devices, for example, using a network NW. The terminal-side communication unit 210 may also have a short-range communication function that performs wireless communication based on Wi-Fi, Bluetooth, DSRC (Dedicated Short Range Communication), or other communication standards, or performs near-field communication (NFC) with the passenger mobile unit 300.

[0079] The input unit 220 accepts user U input, for example, through the operation of various keys or buttons. The input unit 220 may also be equipped with a motion sensor to detect the operation of the terminal device 200, and may accept user U input based on the operation of the terminal device itself detected by the motion sensor (for example, user U shaking or rotating the terminal device 200). The input unit 220 may also be equipped with an audio input unit such as a microphone, and may accept user U input by inputting user U's voice or ambient sounds around the terminal device 200 via the audio input unit and analyzing the input sounds. The output unit 230 outputs information to user U. The output unit 230 is, for example, a display (display unit) or a speaker (audio output unit). The display is, for example, an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) display. The input unit 220 may be configured integrally with the display as a touch panel. The display displays various information in the embodiment under the control of the output control unit 260. The speaker outputs a predetermined sound (voice, music, warning sound, sound effect, etc.) under the control of, for example, the output control unit 260.

[0080] The location information acquisition unit 240 acquires location information of the terminal device 200, for example, using a built-in GPS (Global Positioning System) device (not shown). The location information includes, for example, latitude and longitude.

[0081] The application execution unit 250 is realized by executing the mobile device management application 272 stored in the terminal-side storage unit 270. The mobile device management application 272 is, for example, downloaded from an external device via a network NW and installed on the terminal device 200. The mobile device management application 272 is an application program that controls the output control unit 260 to cause the user U to output images provided by the mobile device management server 100 to the display, or to output audio corresponding to information provided by the mobile device management server 100 from the speaker.

[0082] The application execution unit 250 transmits information input by the input unit 220 and information stored in the terminal-side storage unit 270 to the mobile device management server 100 and the passenger mobile device 300 via the terminal-side communication unit 210. The information input by the input unit 220 includes, for example, information related to the registration and authentication of user U, and information on the adjustment of user U's actions when the passenger mobile device 300 operates in response to an event. The application execution unit 250 also transmits information obtained from the mobile device management server 100, location information of the terminal device 200, map information, etc., to the passenger mobile device 300 on which user U is riding, and transmits information obtained from the passenger mobile device 300 to the mobile device management server 100 along with the user ID and location information. Furthermore, if the mobile device management server 100 determines that the user currently using the passenger mobile device 300 is not a legitimate user (i.e., that the user is someone impersonating a legitimate user), the application execution unit 250 will output information to the output unit 230 indicating this fact, or will perform controls to restrict the operation of the passenger mobile device 300.

[0083] The output control unit 260 controls the content and display manner of the image to be displayed on the display of the output unit 230, as well as the content and output manner of the audio to be output to the speaker, under the control of the application execution unit 250.

[0084] [Piloted vehicle] Next, the rideable mobile vehicle 300 will be described. Figure 9 is a perspective view showing the external appearance of the rideable mobile vehicle 300 according to the embodiment. In Figure 9, the width direction of the rideable mobile vehicle 300 is called the x direction, the front-rear direction is called the y direction, and the up-down direction is called the z direction. The forward direction of the rideable mobile vehicle 300 is the positive direction of the y axis, and the rear direction is the negative direction of the y axis. The rideable mobile vehicle 300 shown in Figure 9 comprises, for example, a base body 310, omnidirectional wheels 312, a seat 313, and a step 314. The base body 310 is covered internally with, for example, a resin cover panel. The internal configuration of the base body 310 will be described later.

[0085] Figure 10 is a perspective view of the omnidirectional wheel 312. The omnidirectional wheel 312 comprises a large-diameter wheel 312A, a small-diameter wheel 312B, a swivel wheel 312C, a first motor MT1, a second motor MT2, and a third motor MT3. The large-diameter wheel 312A is a wheel that can rotate around the x-axis. The large-diameter wheel 312A is rotated by the first motor MT1.

[0086] The small-diameter wheel 312B is a wheel that can rotate around an axis perpendicular to the radial straight line in the widthwise central cross-section of the large-diameter wheel 312A. The omnidirectional wheel 312 is equipped with multiple small-diameter wheels 312B. The multiple small-diameter wheels 312B are arranged at approximately equal intervals from each other along the circumferential direction of the large-diameter wheel 312A. Some or all of the multiple small-diameter wheels 312B are rotated by, for example, a second motor MT2.

[0087] The swivel wheel 312C is a wheel that can rotate around the y-axis. The swivel wheel 312C has a smaller diameter than the large-diameter wheel 312A. The swivel wheel 312C is rotated by the third motor MT3. The omnidirectional movement wheel 312 moves the rideable mobile body 300 by rotating at least one of the large-diameter wheel 312A, the small-diameter wheel 312B, or the swivel wheel 312C. Details of the operation of the omnidirectional movement wheel 312 will be described later.

[0088] Returning to Figure 9, the seat 313 is mounted above the base 310. The seat 313 is the component on which the user U, who boards the rideable mobile unit 300, sits. The step 314 is mounted on the lower front of the base 310. The step 314 is the component on which the user U rests their legs. The seat 313 and step 314 are adjustable in width and height.

[0089] Furthermore, the rideable mobile unit 300 may be equipped with light-emitting parts 316 such as lamps, and speakers 317 that output sound. The light-emitting parts 316 can light up or flash in one or more predetermined colors. The speaker 317 outputs predetermined sounds (voices, music, warning sounds, sound effects, etc.). Note that the light-emitting parts 316 and speakers 317 can each be attached to any location on the rideable mobile unit 300, and are not limited to the mounting positions shown in Figure 9.

[0090] Next, the operation of the omnidirectional wheels 312 of the rideable mobile body 300 will be described in detail. Figure 11 is a diagram illustrating the operation of the omnidirectional wheels 312 of the rideable mobile body 300 in detail. The omnidirectional wheels 312 are wheels that enable the rideable mobile body 300 to immediately move in any direction (all 360 degrees) from its current position without performing any preparatory movements such as turning. The omnidirectional wheels 312 include, for example, a large-diameter wheel 312A as the front wheel and a turning wheel 312C as the rear wheel, and multiple small-diameter wheels 312B are provided on the contact area (radial edge portion) of the large-diameter front wheel 312A.

[0091] The large-diameter wheel 312A is primarily used for straight-line movement in the forward and backward directions. The small-diameter wheel 312B rotates around the rotational direction (circumferential direction) of the large-diameter wheel 312A as its axis, primarily enabling lateral movement in place. On the other hand, the rear turning wheel 312C has a smaller diameter than the large-diameter wheel 312A and rotates around an axis perpendicular to the rotational axis of the large-diameter wheel 312A, primarily enabling turning movement.

[0092] The omnidirectional wheels 312 are equipped with motors MT1 to MT3 that can independently control the rotation of the large-diameter wheels 312A, small-diameter wheels 312B, and swivel wheels 312C, respectively. With this configuration, the omnidirectional wheels 312 can move not only in various directions, such as directly to the side or diagonally, but also in agile movements such as turning and turning in place, by utilizing the difference in lateral movement speed between the front and rear wheels, in addition to forward and backward movement.

[0093] Here, the forward direction of the rideable mobile body 300 is the positive direction of the y-axis (+y-axis direction) in Figure 9, and the backward direction is the negative direction of the y-axis (-y-axis direction). For example, as shown in the operation example M1 (forward / reverse) in Figure 9, the omnidirectional mobile wheel 312 moves forward by rotating the large-diameter wheel 312A in the direction of arrow A1, and moves backward by rotating it in the direction of arrow A2.

[0094] Furthermore, as shown in the operation example M2 (left-right movement) in Figure 11, the omnidirectional wheel 312 can move to the left in place without changing direction by rotating the small-diameter wheel 312B in the direction of arrow A3. In this case, the swivel wheel 312C may be configured to rotate naturally in the direction of arrow A4 in response to the left-right movement, or it may be controlled to rotate in the direction of arrow A4 in accordance with the amount of rotation of the small-diameter wheel 312B. Also, the omnidirectional wheel 312 can move to the right in place without changing direction by rotating the small-diameter wheel 312B in the opposite direction to arrow A3. Here, the left direction corresponds to the positive x-axis direction (+x-axis direction) in Figure 9, and the right direction corresponds to the right direction in Figure 9, which corresponds to the negative x-axis direction (-x-axis direction). The multiple small-diameter wheels 312B may be configured so that all wheels rotate simultaneously, or only the wheels at the contact point with the ground may rotate.

[0095] As shown in the operation example M3 (in-place rotation) in Figure 11, the omnidirectional wheel 312 can rotate in place in the direction of arrow A6 around the contact point P1 of the large-diameter wheel 312A by rotating the swivel wheel 312C in the direction of arrow A5, and can rotate in place in the opposite direction to arrow A6 by rotating it in the opposite direction to arrow A5.

[0096] As shown in the operation example M4 (turning movement) in Figure 11, the omnidirectional wheel 312 can move forward while turning in the direction of arrow A9 by rotating the large-diameter wheel 312A in the direction of arrow A7 and the turning wheel 312C in the direction of arrow A8 (turning movement). In addition, the omnidirectional wheel 312 can move backward while turning in the opposite direction of arrow A9 by rotating the large-diameter wheel 312A in the opposite direction of arrow A7 and rotating the turning wheel 312C in the direction of arrow A8. Furthermore, in this example, the omnidirectional wheel 312 can move forward or backward with the turning center to the right by rotating the turning wheel 312C in the opposite direction of arrow A8.

[0097] The method for realizing the omnidirectional wheels 312 is not limited to the method shown in Figure 11. The omnidirectional wheels 312 may be realized using any existing technology. Furthermore, the rideable mobile body 300 may be equipped with one omnidirectional wheel 312 or with multiple omnidirectional wheels 312. In addition, the rideable mobile body 300 may be equipped with conventional wheels as auxiliary wheels in addition to the omnidirectional wheels 312.

[0098] Next, the functional configuration of the rideable mobile vehicle 300 will be described. Figure 12 is a configuration diagram showing an example of the rideable mobile vehicle 300 according to the embodiment. The rideable mobile vehicle 300 shown in Figure 12 includes, for example, a communication device 320, a sensor 340, and a control device 350. The communication device 320, sensor 340, and control device 350 are provided, for example, within a base 310. In addition to the base 310, the rideable mobile vehicle 300 includes, for example, omnidirectional wheels 312, a seat 313, a step 314, a light-emitting unit 316, and a speaker 317.

[0099] The communication device 320 performs wireless communication based on, for example, Wi-Fi, Bluetooth, DSRC, or other communication standards. The communication device 320 receives electrical signals transmitted by the terminal device 200 and outputs them to the control device 350. The communication device 320 transmits electrical signals output by the control device 350 to the terminal device 200. In place of (or in addition to) the communication device 320, a near-field communication (NFC) function may be provided to perform near-field communication (NFC) with the terminal device 200.

[0100] Sensor 340 includes, for example, a seating sensor 341, an ambient sensor 342, an acceleration sensor 343, and an angular velocity sensor 344. The seating sensor 341 detects whether or not user U (passenger) is seated in seat 313. The seating sensor 341 outputs a seating signal indicating user U's seating status to the control device 350.

[0101] The surrounding sensor 342 is a sensor that detects objects in the vicinity of the rideable mobile body 300. The surrounding sensor 342 also detects, for example, the distance between the detected object and the rideable mobile body 300. The surrounding sensor 342 outputs a surrounding object signal to the control device 350 regarding the detected object and the distance between the detected object and the rideable mobile body 300. The surrounding sensor 342 may be, for example, an ultrasonic sensor using ultrasound as a medium, an optical sensor using light as a medium, or an image sensor that captures an image of the vicinity of the rideable mobile body 300.

[0102] The acceleration sensor 343 is attached to one or more arbitrary locations on the base 310 or the seat 313. The acceleration sensor 343 detects the acceleration acting on the attachment location and outputs it to the control device 350. The angular velocity sensor (gyro sensor) 344 is attached to one or more arbitrary locations on the base 310 or the seat 313. The angular velocity sensor 344 detects the angular velocity acting on the attachment location and outputs it to the control device 350. In addition to the sensors described above, the sensor 340 may also include an attitude angle sensor that detects the attitude angle (tilt) of the rideable mobile body 300.

[0103] The control device 350 controls the operation of the rideable mobile body 300 based on information obtained from the communication device 320 and the sensor 340. The control device 350 includes, for example, an authentication processing unit 360, a command generation unit 370, a motor control unit 380, and an output control unit 390. The authentication processing unit 360 includes, for example, an authentication unit 361 and a release unit 362. The command generation unit 370 includes, for example, a determination unit 371, a detection unit 372, a generation unit 373, a center of gravity estimation unit 374, and a balance control unit 375.

[0104] These components are 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 LSIs, ASICs, FPGAs, and GPUs, or by the cooperation of software and hardware. The program may be stored in advance in a storage device such as an HDD or flash memory (a storage device equipped with a non-transient storage medium) provided in the rideable mobile body 300, or it may be stored in a removable storage medium such as a DVD or CD-ROM (a non-transient storage medium) and installed in the storage device when the storage medium is mounted on a drive device. The storage device may store a mobile body ID assigned to the vehicle, a terminal ID obtained from the terminal device 200, location information, map information, operation commands, etc.

[0105] The authentication unit 361 authenticates user U who is boarding (or is boarding) the rideable mobile vehicle 300. The authentication unit 361 uses Bluetooth or the like to communicate with terminal devices 200 in the vicinity (within a predetermined distance), and obtains information about the terminal device 200 (e.g., terminal ID and user ID) from the terminal device 200 with which communication is first established or the nearest terminal device 200, and sets usage rights for user U who possesses the terminal device 200 based on the obtained information. The authentication unit 361 may also perform the above authentication if, for example, the seating sensor 341 determines that user U is seated in the seat 313. When usage rights are set, the authentication unit 361 is in a state of communication between the terminal device 200 and the rideable mobile vehicle 300. The authentication unit 361 does not communicate with other terminal devices 200 when usage rights are set for one user U (i.e., usage rights cannot be set for multiple users simultaneously).

[0106] The release unit 362 measures the elapsed time after user U has left the rideable mobile vehicle 300. After a predetermined time has elapsed since user U left the rideable mobile vehicle 300, the release unit 362 determines that the release conditions have been met and releases user U's right to use the rideable mobile vehicle 300. The predetermined time may be constant or may vary depending on specific conditions. Specific conditions may include, for example, the parking location of the rideable mobile vehicle 300, the time of day, the number of people who visited a specific area with user U, and relationships such as family and friends. The release conditions may also be other conditions. For example, the release condition may be that user U performs an operation indicating their intention to release the right to use the vehicle, and the release unit 362 receives a signal corresponding to that operation. Furthermore, the release unit 362 compares the operation of the rideable mobile device 300 by user operation after authentication by the authentication unit 361 (hereinafter referred to as "actual operation") with the operation associated with the user U's participation level (hereinafter referred to as "level operation"). If the actual operation does not reach the level operation, the release unit 362 may release the user U's right to use the rideable mobile device 300 or add usage restrictions so that some operations cannot be performed. This can deter others from impersonating user U and using the device due to the transfer or theft of the terminal device 200, and can further improve user U's safety by restricting use if user U has a gap in their ride experience with the rideable mobile device 300.

[0107] The command generation unit 370 generates commands for, for example, operation control and output control for the rideable mobile body 300. The determination unit 371 determines whether or not user U is seated based on the seating signal output by the seating sensor 341. Alternatively, if the determination unit 371 determines that user U is seated on the seat 313 based on the seating signal, and then determines that user U is not seated on the seat 313, it may determine that user U has left the rideable mobile body 300.

[0108] The detection unit 372 detects the user U's operations on the rideable mobile device 300 and information about events (event operation commands) acquired from the terminal device 200. The detection unit 372 may also detect the surrounding conditions of the rideable mobile device 300 as detected by the surrounding sensor 342. Surrounding conditions include, for example, the behavior of other rideable mobile devices 300 in the vicinity, or characters or vehicles participating in a parade, etc.

[0109] The generation unit 373 generates event operation commands for the rideable mobile body 300. For example, based on event operation commands generated by the mobile body management server 100, which are acquired via the terminal device 200, the generation unit 373 generates event operation commands corresponding to events such as parades and shows taking place in the vicinity. The generated event operation commands are, for example, commands to drive the omnidirectional wheels 312 by the motor control unit 380, to light up or flash a predetermined color by the light-emitting unit 316 by the output control unit 390, or to output a predetermined sound from the speaker (sound output unit), according to the operation commands from the mobile body management server 100. The generation unit 373 may also generate operation commands to move the rideable mobile body 300 so as not to come into contact with surrounding objects obtained from the surrounding sensor 342. The generation unit 373 outputs control information based on the generated operation commands (including event operation commands) to the motor control unit 380 and the output control unit 390.

[0110] The center of gravity estimation unit 374 and the balance control unit 375 primarily function when a user U is riding on the rideable mobile device 300. The center of gravity estimation unit 374 estimates the center of gravity of the object, including the user U, base 310, and seat 313, riding on the rideable mobile device 300, based on the outputs of the acceleration sensor 343 and the angular velocity sensor 344.

[0111] The balance control unit 375 generates control information (action commands) that return the position of the center of gravity estimated by the center of gravity estimation unit 374 to the reference position (the position of the center of gravity in a stationary state). For example, if the position of the center of gravity is biased to the right and rearward from the reference position, the balance control unit 375 generates control information that instructs acceleration toward the right and rearward. Also, if the operation (action command) by the user U is to accelerate forward and the position of the center of gravity is behind the reference position, the balance control unit 375 may suppress the acceleration so that the position of the center of gravity is further biased backward by the accelerated forward movement, or it may reverse once to guide the position of the center of gravity forward before starting the accelerated forward movement. The command generation unit 370 outputs the control information (action commands) generated by the balance control unit 375 to the motor control unit 380.

[0112] The motor control unit 380 individually controls each motor attached to the omnidirectional wheels 312 based on the control information output by the command generation unit 370. For example, the motor control unit 380 may perform different controls depending on whether a user U is riding on the rideable mobile body 300, whether user U is riding (seated) on the rideable mobile body 300, or whether user U is not riding on it.

[0113] When a user U is riding in the rideable mobile device 300, this control allows the user U to move the rideable mobile device 300 in the desired direction by changing their own posture to shift their center of gravity in the desired direction. In other words, the rideable mobile device 300 recognizes the user U's shift in center of gravity as a control operation and performs movement actions in accordance with the control operation.

[0114] Based on the control information output by the command generation unit 370, the output control unit 390 causes the light-emitting unit 316 to light up or blink in a predetermined color, or the speaker 317 to output a predetermined sound (voice, music, warning sound, sound effect, etc.).

[0115] The functions performed by the rideable mobile unit 300 are powered by electricity supplied from a battery (not shown) mounted inside. The battery may be charged by a charging device located outside the rideable mobile unit 300, and may be detachable so that it can be replaced with other batteries. The battery can also be charged by electricity regenerated by the motor of the omnidirectional mobile wheels 312.

[0116] [Processing performed by the mobile management system] Next, we will describe the processes performed by the mobile device management system 1. Figure 13 is a sequence diagram showing an example of the processes performed by the mobile device management system 1. For the sake of explanation, the example in Figure 13 uses one mobile device management server 100, a terminal device 200, and a passenger-type mobile device 300. Furthermore, the example in Figure 13 mainly focuses on the process when the passenger-type mobile device 300 participates in an event held within a predetermined area. In addition, in the example in Figure 13, it is assumed that authentication processing is performed between the terminal device 200 and the mobile device management server 100, and that user U of the terminal device 200 has been granted permission to use the services provided by the mobile device management system 1.

[0117] In the example shown in Figure 13, when user U boards the rideable mobile vehicle 300, the terminal device 200 communicates with the rideable mobile vehicle 300 using a short-range communication method such as Bluetooth (step S100), and when permission to use the rideable mobile vehicle 300 is granted (communication is established), it obtains the identification information (mobile vehicle ID) of the rideable mobile vehicle 300 (step S102). Next, the location information acquisition unit 240 of the terminal device 200 acquires the location information of the terminal device 200 (step S104). Next, the terminal device 200 transmits the acquired location information, user ID, terminal ID, and mobile vehicle ID to the mobile vehicle management server 100 (step S106).

[0118] The mobile device management server 100 receives information from the terminal device 200, refers to the user ID in the user information 181, and stores the terminal ID and mobile device ID in the user information 181 in association with the user ID that matches the received user ID, thereby performing user management (step S108). The mobile device management server 100 also manages the location information of the terminal device 200 acquired by the terminal device 200 as the location information of the rideable mobile device 300 (step S110). The processes in steps S104 to S110 may be repeatedly executed at predetermined intervals while the terminal device 200 and the rideable mobile device 300 are connected by short-range communication.

[0119] Next, the mobile device management server 100 refers to the event information 182, manages the event schedule, and obtains information about events to be held within a predetermined time from the present (for example, the event content, location and route information, implementation time, and information about the participation conditions for user U) (step S112). Next, the mobile device management server 100 transmits the event information (for example, today's event schedule at the theme park) to the terminal device 200 (step S114). In step S114, the mobile device management server 100 may also refer to the usage history information 184 to obtain the participation level for each user U and transmit the event information to user U whose participation level meets the participation conditions.

[0120] The terminal device 200 displays information about events received from the mobile device management server 100 on the output unit 230 (display) (step S116). The terminal device 200 also receives information about events that user U wishes to participate in from the displayed event information and transmits the received information to the mobile device management server 100 (step S118).

[0121] When the mobile device management server 100 receives information about an event to be taken by user U on the terminal device 200, it manages user U's participation in the event (step S120). Here, the mobile device management server 100 performs an impersonation check to determine whether the user currently using the passenger mobile device 300 is a legitimate user (whether it is someone else impersonating a legitimate user) (step S122). If it is determined that the user is legitimate, the process from step S124 onwards is performed. If it is determined that the user is not legitimate, the server takes control measures such as restricting the operation of the passenger mobile device 300, moving it to a designated location such as a management facility, or preventing it from participating in the event.

[0122] If the impersonation detection determines that the currently using user is a legitimate user, the mobile device management server 100 selects the operation of the rideable mobile device 300 that user U is riding in, according to the event that user U is participating in and their participation level (step S124). If the event that user U has chosen to participate in includes multiple different participation options, the mobile device management server 100 may ask user U which option they would like to participate in. The mobile device management server 100 may also ask user U whether or not to perform a performance action according to the user's current participation level, or whether or not to adjust the operation (for example, adjusting the turning speed, limiting the amount of light emitted, or limiting the maximum speed).

[0123] This allows user U to customize the details of the performance actions according to their preferences and surrounding environment, enabling them to enjoy the event more. For example, if there are many people around, user U can adjust the rotation speed or light output to reduce the amount of light, thus enjoying the performance without disturbing others. Conversely, if there are no people around, user U can accelerate the rotation speed or increase the amount of light to fully enjoy a dynamic performance. The above-mentioned adjustment information for the performance actions may be transmitted from the terminal device 200 to the mobile device management server 100, which may then receive the adjusted new event action command and transmit it to the rideable mobile device 300. Alternatively, the terminal device 200 may directly adjust the parameters of the event action command obtained from the mobile device management server 100 and transmit them to the rideable mobile device 300.

[0124] Furthermore, the mobile device management server 100 may refer to the user information 181 and, if the user U on board is a child (for example, 12 years old or younger), adjust the rotation speed during turns compared to when the user is an adult, or cancel the settings for user U. This allows for safer operation for each user U. Therefore, even if user U is a child, parents can rest assured that their child can use the rideable mobile device 300 or participate in events.

[0125] Next, the mobile device management server 100 generates an event operation command to cause the rideable mobile device 300 to perform an operation corresponding to the selected participation level (step S126), and transmits the generated operation command to the terminal device 200 (step S128).

[0126] The terminal device 200 transmits the operation command sent from the mobile device management server 100 to the rideable mobile device 300 (step S130). The rideable mobile device 300 performs an operation in the operation mode and output mode based on the event operation command received from the terminal device 200 (step S132). It transmits the execution result to the terminal device 200 (step S134). The terminal device 200 transmits the execution result transmitted from the rideable mobile device 300 to the mobile device management server 100 (step S136).

[0127] The mobile device management server 100 updates the usage status of the passenger-type mobile device 300, such as the number of times it has been used and the usage time, for each user (step S138). Next, the mobile device management server 100 provides incentives equivalent to rental fees or event participation fees to service providers who have lent out the passenger-type mobile device 300 or planned an event (step S140). The mobile device management server 100 may also provide incentives to users who have participated in the event. This completes the processing of this sequence. Through the above processing, the mobile device management server 100 can manage user U's participation in events and provide events with a more dramatic effect. Note that the impersonation detection described above may be performed in the processing of step S108 or at other times.

[0128] [Specific examples of services provided by mobile management systems] The following describes specific examples of services provided by the mobile device management system 1. Figure 14 is a diagram illustrating a specific example of mobile device management for a rideable mobile device 300. In the example in Figure 14, an event is shown where a parade takes place on a road RD within a theme park, as an example of a service. In the example in Figure 14, objects OB1 to OB3 and users U1 to U4 participate in the parade. Objects OB1 to OB3 are examples of objects related to the event. More specifically, objects OB1 and OB2 are parade cars, and object OB3 is one or more characters. Users U1 to U4 each possess their corresponding terminal devices 200-1 to 200-4 and are riding in rideable mobile devices 300-1 to 300-4. Furthermore, the participation level of users U1 and U2 is such that they meet the participation requirements to perform actions similar to the performance actions of object OB1, and the participation level of users U3 and U4 is such that they meet the participation requirements to perform actions similar to the performance actions of object OB2.

[0129] The management unit 140 of the mobile object management server 100 manages, based on event information 182, which objects pass through which points at what time, and the operation and output modes performed by each object OB1 to OB3. For example, the management unit 140 performs an effect of rotating in a predetermined direction when object OB1, shown in Figure 14, reaches point P11 on road RD, and performs an effect of outputting music when object OB2 reaches point P12 on road RD. In this case, the mobile object management server 100 causes the rideable mobile objects 300-1 to 300-4, located around objects OB1 and OB2, to perform operations and outputs based on the respective operation and output modes of objects OB1 and OB2.

[0130] In the example in Figure 14, when object OB1 in the parade reaches point P11 on road RD and rotates in a predetermined direction, the rideable mobile units 300-1 and 300-2 are also made to rotate in the same direction in conjunction with that movement. Also in the example in Figure 14, when music is played when object OB2 in the parade reaches point P12 on road RD, the same music is played from the speakers 317 of the rideable mobile units 300-3 and 300-4. Furthermore, in the example in Figure 14, when object OB2 illuminates a predetermined color light when it reaches point P12 on road RD, the light-emitting parts 316 of the rideable mobile units 300-3 and 300-4 may also illuminate the same color. Additionally, the mobile unit management server 100 may synchronize the movements of the rideable mobile units 300-3 and 300-4, which are within a predetermined distance from the character of object OB3, with the character's movements (e.g., rotation, forward, backward, stop). This allows users to experience a sense of unity with the parade.

[0131] Furthermore, if a rideable mobile vehicle 300 carrying a user who is not participating in the parade is located within a predetermined distance from objects OB1 to OB3, the mobile vehicle management server 100 may cause the rideable mobile vehicle 300 to perform performance actions corresponding to the movements of objects OB1 to OB3, even if the user is not participating in the parade. In the example in Figure 14, a rideable mobile vehicle 300-5 carrying user U5, who is not participating in the event, is shown rotating in accordance with the rotational movement of object OB1. This allows users who were unable to participate due to participant limits, etc., to experience a sense of unity with the parade.

[0132] Furthermore, the mobile vehicle management server 100 may control the operation of the rideable mobile vehicle 300 so that it stops in front of a fixed camera CAM1 for a predetermined time if a fixed camera CAM1 for photographing event participants is installed at a predetermined position (point P13 in the figure) along the parade route. The fixed camera CAM1 is, for example, a digital camera using a solid-state image sensor such as a CCD (Charge Coupled Device) or CMOS (Complementary Metal Oxide Semiconductor). This ensures that images (still images and videos) of users participating in the parade are reliably captured, and by providing the captured images to the users, a more value-added service can be provided.

[0133] Furthermore, if the mobile device management server 100 manages a relationship between a first user (e.g., a child) participating in the parade and a second user (e.g., a parent) who photographs that user with a camera, it may perform motion control based on the position information of the rideable mobile devices 300 on which the first and second users are riding, such as stopping the first user's rideable mobile device 300 in front of the second user's rideable mobile device, or causing the second user's rideable mobile device 300 to follow the first user's rideable mobile device 300. In the example in Figure 14, the rideable mobile device 300-3 of user U3 and the rideable mobile device 300-6 of user U6 are associated, and the rideable mobile device 300-6 is shown moving in a predetermined interval, following the rideable mobile device 300-3. This allows user U6 to continue photographing user U3's participation in the event with camera CAM2 while following user U3.

[0134] Furthermore, the mobile device management server 100 may provide information regarding the participation results to the user U who participated in the event after the event has ended. Figure 15 shows an example of an image IM10 provided to the user U who participated in the event. Note that the layout and display content of the image IM10 are not limited to the example in Figure 15. The same applies to other images described later. The image IM10 shown in Figure 15 may include, for example, the number of times user U has participated in the event (an example of the number of uses) and the time spent participating (an example of the time spent), the remaining number of uses or time until the next level up, information regarding user U's level, and event information corresponding to the level. The image IM10 may also include information regarding performance actions that have become possible after leveling up (for example, rotation, coordination with other users, etc.).

[0135] The management unit 140 generates an image IM10 containing the information described above and transmits the generated image IM10 to the target user U's terminal device 200 via the network NW. The terminal device 200 receives the image IM10 and displays it on the output unit 230. Alternatively, the mobile device management server 100 may transmit information for generating the image IM10 to the target user's terminal device 200, and the terminal device 200 may generate the image IM10 and output it to the output unit 230. By providing the image IM10 to user U in this way, user U can clearly understand their participation status (usage status of the passenger mobile device 300) and further increase their willingness to participate (willingness to use).

[0136] [Notification content after identity theft detection] Next, we will explain the content of the impersonation notification when the determination unit 150 determines that the user currently using the rideable mobile device 300 is not a legitimate user (i.e., a user impersonating a legitimate user). Figure 16 shows an example of an image IM20 that notifies the result of the impersonation determination. The image IM20 shown in Figure 16 includes, for example, information indicating that the determination result of the determination unit 150 indicates that the user currently using the device is not a legitimate user, and that the operation of the rideable mobile device 300 will be restricted as a result of the above determination, as well as icons IC21 and IC22. Icon IC21 is a GUI (Graphical User Interface) switch that accepts the execution of a re-determination in response to the determination that the user is not a legitimate user. Icon IC22 is a GUI switch that accepts the current user's request to terminate their use of the rideable mobile device 300. If icon IC11 or icon IC12 is selected, the terminal device 200 transmits the received information to the rideable device management server 100.

[0137] For example, if icon IC21 is selected, the mobile device management server 100 performs a predetermined operation to determine the proficiency required for the determination, and then performs a re-determination of impersonation based on the proficiency obtained from the execution result. If the re-determination determines that the user in use is a legitimate user, the management unit 140 of the mobile device management server 100 releases the restrictions on the control content of the rideable mobile device 300 and executes control according to the proficiency level and participation level of the legitimate user. If the re-determination also determines that the user is not a legitimate user, the management unit 140 forcibly restricts the operation content of the rideable mobile device 300. Furthermore, if icon IC22 is selected, the management unit 140 stops the rideable mobile device 300, cancels the operation content applied to the rideable mobile device 300, or cancels the rideable mobile device 300's participation in the event.

[0138] [Differentiation] In the embodiment described above, some or all of the user proficiency and operation characteristic information acquisition process by the management unit 140 of the mobile device management server 100 and the determination process by the determination unit 150 may be performed by the authentication processing unit 360 of the rideable mobile device 300. In this case, operation restrictions of the rideable mobile device 300 according to the determination result are performed, for example, by the command generation unit 370.

[0139] Furthermore, in the services provided by the mobile vehicle management system 1 of this embodiment, users U who are scheduled to participate in an event may be given a lecture in advance on the performance operation of the rideable mobile vehicle, and permission to participate in the event may be granted after the lecture. In addition, the mobile vehicle management system 1 may transmit information regarding the implementation of lectures to improve proficiency to the terminal device 200, notify users who wish to participate in the lecture of the date and time, location and content of the lecture, and manage the user by raising their proficiency level if they pass a practical test after the lecture.

[0140] Furthermore, in the above-described embodiment, the rideable mobile body 300 was made to perform actions and outputs in accordance with the event. In addition, the terminal device 200 may also control actions and outputs in accordance with the event. In this case, the mobile body management server 100 generates event action commands to, for example, activate a vibration function provided in the terminal device 200, output a predetermined sound from a speaker, or illuminate a display, etc., in accordance with the event, and transmits the generated action commands to the terminal device 200. By operating various devices in accordance with the event in this way, the performance effect for the user U can be further improved.

[0141] Furthermore, in the embodiment, if the rideable mobile body 300 is equipped with a position acquisition unit instead of using the position information of the terminal device 200, the mobile body management server 100 may communicate directly with the rideable mobile body 300 without going through the terminal device 200.

[0142] As described above, the mobile device management server (mobile device management device) 100 includes a management unit 140 that manages the relationship between the rideable mobile device 300 on which a user is riding and the user's terminal device riding on the rideable mobile device 300, an operation command unit 170 that causes the rideable mobile device 300 to perform predetermined operations based on instructions from the user to the rideable mobile device 300, and a determination unit 150 that determines whether the user is a legitimate user based on the user's proficiency in the operation of the rideable mobile device 300 on which the user is riding. This makes it possible to more appropriately detect the use of the mobile device by others impersonating legitimate users.

[0143] Furthermore, according to the embodiment described above, the mobile body management server (mobile body management device) 100 includes a management unit 140 that manages the relationship between the rideable mobile body 300 on which a user is riding and the terminal device of the user riding in the rideable mobile body 300, an operation command unit 170 that causes the rideable mobile body 300 to perform a predetermined operation based on instructions from the user to the rideable mobile body 300, and a determination unit 150 that determines whether or not the user is a legitimate user based on characteristic information of the user's operation while riding in the rideable mobile body 300. This makes it possible to more appropriately detect the use of the mobile body by others who are impersonating a legitimate user.

[0144] Furthermore, according to the embodiment, it is possible to prevent unauthorized use of the rideable mobile device 300 by others impersonating legitimate users, based on the user's proficiency level and operational characteristics. This helps to prevent any trouble or accidents from occurring during the event due to others who do not meet the required event participation level participating in the event.

[0145] Furthermore, according to this embodiment, by allowing users riding in the rideable mobile vehicle 300 to participate in the event, it is possible to further entertain users who enjoy events such as parades, as well as fans of the dancers and characters participating in the event. Also, according to this embodiment, by changing the actions that can be performed by the rideable mobile vehicle 300 according to the user's level of participation, for example, the initial effect may only be the illumination of the light-emitting part 316 of the rideable mobile vehicle 300, but it can be changed to an effect that moves in sync with sound or performs actions similar to those of characters, allowing users to experience a variety of performance actions.

[0146] Furthermore, the process for determining impersonation in the above-described embodiment, and the processing based on the determination result, are not limited to ride-on vehicles used when moving within a predetermined area such as a theme park, but may also be applied to ride-on vehicles traveling on public roads or private property, for example. In addition, the ride-on vehicle in the embodiment may be applied not only to rented ride-on vehicles but also to ride-on vehicles owned by individuals. This makes it possible to restrict the operation of the ride-on vehicle or escort the person to a predetermined location based on the determination result if the ride-on vehicle is used by a third party (another person) due to theft or other reasons. Moreover, the vehicle to which the embodiment can be applied is not limited to the ride-on vehicle 300 described above, but may also be a four-wheeled vehicle capable of carrying multiple people, for example. For example, when a four-wheeled vehicle is rented to a user, the method of the embodiment can be used to determine whether a user other than the user who applied for prior registration is driving it, and to manage the four-wheeled vehicle.

[0147] The embodiments described above can be expressed as follows. A storage medium that stores instructions readable by a computer, A processor connected to the storage medium, The processor executes instructions that can be read by the computer, The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in an associated manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on the user's proficiency in the operation of the rideable vehicle on which the user is riding, it is determined whether the user is a legitimate user. Mobile management device.

[0148] Furthermore, the embodiments described above can also be expressed as follows. A storage medium that stores instructions readable by a computer, A processor connected to the storage medium, The processor executes instructions that can be read by the computer, The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in an associated manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on characteristic information of the user's operation while riding in the aforementioned mobile vehicle, it is determined whether the user is a legitimate user. Mobile management device.

[0149] Although embodiments for carrying out the present invention have been described above using examples, the present invention is not limited in any way to these embodiments, and various modifications and substitutions can be made without departing from the spirit of the present invention. [Explanation of symbols]

[0150] 1...Mobile device management system, 100...Mobile device management server, 110...Communication unit, 120...Registration unit, 130...Acquisition unit, 140...Management unit, 141...User management unit, 142...Event management unit, 143...Participation management unit, 144...Incentive management unit, 150...Decision unit, 160...Motion selection unit, 170...Motion command unit, 180...Storage unit, 200...Terminal device, 210...Terminal-side communication unit, 220...Input unit, 230...Output unit, 240...Location information acquisition unit, 250...Application execution unit, 260, 390...Output control unit, 270...Terminal-side storage unit, 300...Riding-type mobile device, 320...Communication device, 340...Sensor, 350...Control device, 360...Authentication processing unit, 370...Command generation unit, 380...Motor control unit

Claims

1. A management unit that manages the relationship between a passenger-type mobile vehicle and the terminal device of the user riding in the passenger-type mobile vehicle, An operation command unit that causes the rideable mobile body to perform a predetermined operation based on instructions from the user to the rideable mobile body, The system includes a determination unit that determines whether the user is a legitimate user based on the user's level of proficiency in response to the operation of the rideable mobile vehicle on which the user is riding, Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the operation command unit causes the rideable mobile body to perform a predetermined action corresponding to the event via the user's terminal device. The management unit, if the determination unit determines that the user is not a legitimate user, restricts the user's participation in the event. Mobile management device.

2. A management unit that manages the relationship between a passenger-type mobile vehicle and the terminal device of the user riding in the passenger-type mobile vehicle, An operation command unit that causes the rideable mobile body to perform a predetermined operation based on instructions from the user to the rideable mobile body, The system includes a determination unit that determines whether the user is a legitimate user based on characteristic information of the user's operation while riding in the aforementioned mobile vehicle, Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the operation command unit causes the rideable mobile body to perform a predetermined action corresponding to the event via the user's terminal device. The management unit, if the determination unit determines that the user is not a legitimate user, restricts the user's participation in the event. Mobile management device.

3. If the determination unit determines that the user is not a legitimate user, the management unit restricts the control contents of the rideable vehicle that can be executed by the user using the rideable vehicle. Mobile object management device according to claim 1 or 2.

4. If the determination unit determines that the user is not a legitimate user, the management unit will either reduce the control content of the rideable mobile device to less than the control content that a legitimate user can execute, or stop the rideable mobile device. The mobile object management device according to claim 3.

5. If the control unit determines that the user is not a legitimate user, it instructs the operation command unit to move the rideable mobile device to a predetermined location. A mobile body management device according to any one of claims 1 to 4.

6. The management unit, after the determination unit has determined that the user is not a legitimate user, and then after a re-determination, determines that the user is a legitimate user, releases the restrictions on the control content of the rideable mobile device. A mobile body management device according to any one of claims 1 to 5.

7. The aforementioned proficiency level is determined based on the user's past usage history of the rideable vehicle or the user's actions during a predetermined period of time after boarding the rideable vehicle. The mobile body management device according to claim 1.

8. The characteristic information of the operation is determined based on the user's past usage history of the rideable vehicle or the actions taken by the user during a predetermined time period after boarding the rideable vehicle. The mobile body management device according to claim 2.

9. If the determination unit determines that the user is not a legitimate user, the management unit shall notify the terminal device and / or the passenger-type mobile vehicle of at least the determination that the user is not a legitimate user. A mobile body management device according to any one of claims 1 to 8.

10. If the determination unit determines that the user is not a legitimate user, and the illegitimate user can be identified, the management unit shall impose a predetermined penalty on the illegitimate user and / or the legitimate user. A mobile body management device according to any one of claims 1 to 9.

11. Computers The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in an associated manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on the user's proficiency level in response to the operation of the rideable vehicle on which the user is riding, it is determined whether the user is a legitimate user or not. Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the user's terminal device is used to cause the rideable mobile body to perform a predetermined action in response to the event. If the user is determined not to be a legitimate user, their participation in the event will be restricted. Mobile object management method.

12. Computers The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in an associated manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on the characteristic information of the user's operation while riding in the aforementioned mobile vehicle, it is determined whether the user is a legitimate user or not. Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the user's terminal device is used to cause the rideable mobile body to perform a predetermined action in response to the event. If the user is determined not to be a legitimate user, their participation in the event will be restricted. Mobile object management method.

13. On the computer, The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in a corresponding manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on the user's proficiency level in response to the operation of the rideable vehicle on which the user is riding, it is determined whether the user is a legitimate user or not. Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the user's terminal device is used to cause the rideable mobile body to perform a predetermined action in response to the event. If the user is determined not to be a legitimate user, their participation in the event may be restricted. program.

14. On the computer, The system manages the passenger vehicle on which the user is riding and the terminal device of the user riding on the passenger vehicle in a corresponding manner. Based on instructions from the user to the rideable mobile body, the rideable mobile body is made to perform a predetermined operation. Based on the characteristic information of the user's operation while riding in the aforementioned mobile vehicle, it is determined whether the user is a legitimate user or not. Based on the location information of the rideable mobile body and information regarding an event taking place within a predetermined area, the user's terminal device is used to cause the rideable mobile body to perform a predetermined action in response to the event. If the user is determined not to be a legitimate user, their participation in the event may be restricted. program.

Images