Mobile body management system and control method for mobile body management system

By detecting idle electric scooters and utilizing the terminal devices of nearby vehicle users, rewards are calculated and provided to encourage users to move idle electric scooters to designated locations. This solves the problem in existing technologies where reducing idle vehicles relies on user judgment, and effectively reduces the number of idle vehicles.

CN116645806BActive Publication Date: 2026-04-24HONDA MOTOR CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
HONDA MOTOR CO LTD
Filing Date
2023-02-03
Publication Date
2026-04-24

AI Technical Summary

Technical Problem

In existing technologies, the reduction in idle vehicles depends on user judgment, which may result in the inability to effectively reduce the number of idle vehicles.

Method used

By detecting idle electric scooters and utilizing the terminal devices of nearby vehicle users, rewards are calculated and provided to encourage users to move idle electric scooters to designated locations, including rest stops or lending stations, and the management and reward calculations are carried out through a server system.

Benefits of technology

This effectively reduced the number of idle electric scooters, increased the utilization rate of idle vehicles, and reduced resource waste.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116645806B_ABST
    Figure CN116645806B_ABST
Patent Text Reader

Abstract

The present application provides a mobile body management system and a control method of the mobile body management system, which can effectively reduce the idle electric scooters. The mobile body management system (1) comprises: a first detection unit (303) configured to detect a rideable electric scooter (2) that has been idle outside a specified place for more than a specified period; a second detection unit (304) configured to detect a vehicle (4) approaching an idle area containing the current position of the electric scooter (2) detected by the first detection unit (303) based on information of the current position of the electric scooter (2) detected by the first detection unit (303); and a calculation unit (307) configured to calculate a reward given to a user (P) of the vehicle (4) detected by the second detection unit (304) in the case that the user (P) of the vehicle (4) detected by the second detection unit (304) moves the electric scooter (2) to the specified place.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to a mobile body management system and a control method for the mobile body management system. Background Technology

[0002] Previously, technologies for reducing idle mobile vehicles were known. For example, Patent Document 1 discloses a navigation system that searches for candidate paths using the routes of rented bicycles detected as idle vehicles and outputs the searched candidate paths.

[0003] Existing technical documents

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2020-016668 Summary of the Invention

[0006] The problem that the invention aims to solve

[0007] In the method described in Patent Document 1, the user of the terminal device can identify the route for utilizing idle vehicles, but the user of the terminal device determines whether to utilize the idle vehicles. Therefore, in the method described in Patent Document 1, the degree to which idle vehicles are reduced depends on the user's judgment, and there is a possibility that the method may not effectively reduce the number of idle vehicles.

[0008] The present invention was made in view of the above circumstances, and its object is to provide a mobile body management system and a control method for the mobile body management system that can effectively reduce the number of idle mobile bodies.

[0009] Methods for solving problems

[0010] One way to achieve the above objective is a mobile vehicle management system comprising: a first detection unit that detects rideable mobile vehicles that have been idle for a specified period or more outside a designated location; a second detection unit that, based on information about the current location of the mobile vehicle detected by the first detection unit, detects vehicles approaching an idle area containing the current location of the mobile vehicle detected by the first detection unit; and a calculation unit that, if a user of the vehicle detected by the second detection unit moves the mobile vehicle to the designated location, calculates a reward to be given to the user of the vehicle detected by the second detection unit.

[0011] Invention Effects

[0012] According to the present invention, the number of idle mobile units can be effectively reduced. Attached Figure Description

[0013] Figure 1 This is a diagram showing an overview of the mobile body management system.

[0014] Figure 2 This is a diagram showing the structure of an electric scooter, vehicle, and terminal device.

[0015] Figure 3 This is a diagram showing the structure of the server device.

[0016] Figure 4 This is a flowchart illustrating the actions of the mobile body management system.

[0017] Figure 5 This is a flowchart illustrating the actions of the first decision-making unit.

[0018] Figure 6 This is a flowchart illustrating the actions of the mobile body management system.

[0019] Explanation of reference numerals in the attached figures

[0020] 1…Mobile entity management system, 2…Electric scooter (mobile entity), 3…Server device, 4, 4A, 4B, 4C…Vehicle, 5…Terminal device, 6…Vehicle battery (second charging device), 23…Mobile entity battery (first charging device), 30…Server processor, 31…Server memory, 32…Server communication unit, 301…Receiving unit, 302…Database processing unit, 303…First detection unit, 304…Second detection unit, 305…First decision unit, 306…Notification unit, 307…Calculation Department, 308…Second Decision Department, 311…Control Procedure, 312…Mobile Body Database, 313…Vehicle, 314…User Database, 315…Loan Station Database, 316…Station Database, 317…Use Request Database, 318…Map Data, AR, AR1, AR2, AR3…Idle Area, KS, KS1, KS2, KS3…Loan Station, NW…Communication Network, P, P1, P2, P3…User, TS, TS1, TS2, TS3…Station, Y…Requester. Detailed Implementation

[0021] [1. Overview of the Mobile Entity Management System]

[0022] Reference Figure 1 The outline of the mobile body management system 1 of this embodiment will be described.

[0023] Figure 1 This is a diagram showing an overview of the mobile body management system 1.

[0024] The mobility management system 1 of this embodiment is a system for managing an electric scooter (Kickboard) 2, which is an example of a mobility vehicle. Specifically, the mobility management system 1 manages the current location of the electric scooter 2, the charge level of the mobility battery 23 that serves as the power source for the electric scooter 2, and so on. The electric scooter 2 is a vehicle that moves by an electric drive motor 24 installed on the scooter. The electric scooter 2 can be a standing or seated type. The electric scooter 2 of this embodiment is a loan vehicle that is lent to a user of the electric scooter 2.

[0025] The mobile battery 23 is equivalent to the "first charging device" of this disclosure.

[0026] The server device 3 of the mobile body management system 1 detects electric scooters 2 that have been idle for a specified period of time outside of designated locations. In the following description, electric scooters 2 that have been idle for a specified period of time outside of designated locations will be referred to as "idle electric scooters" and marked with the reference numeral "2A".

[0027] In this embodiment, the designated locations include the stop station TS and the departure station KS. The designated period is set beforehand through testing or simulation as the period during which the passenger is considered to have disembarked and left the vehicle. The designated period is, for example, 24 hours.

[0028] The stop station TS is a place where the electric scooter 2 can stop. In this embodiment, the stop station TS has an upper limit on the number of electric scooters 2 that can stop. In addition, the stop station TS can also be a place where the mobile battery 23 of the electric scooter 2 can be charged.

[0029] The rental station KS is where electric scooter 2 is rented out. At the rental station KS, the battery 23 of the electric scooter 2 can be charged.

[0030] If the server device 3 detects an idle electric scooter 2A, it detects vehicles 4 that are close to the idle area AR containing the current position of the detected idle electric scooter 2A. The idle area AR is, for example, a circular area with a radius of 10m centered on the current position of the idle electric scooter 2A. However, the shape and size of the idle area AR are not limited to this. The vehicle 4 detected by the server device 3 has a vehicle battery 6 capable of charging the mobile battery 23 of the electric scooter 2. In this embodiment, the vehicle battery 6 is a battery that has been lent to the user P of the vehicle 4.

[0031] The vehicle battery 6 is equivalent to the "second charging device" of this disclosure.

[0032] Furthermore, in this embodiment, a four-wheeled private car is exemplified as vehicle 4, but vehicle 4 is not limited to a private car; it could also be a taxi, a vehicle used by delivery personnel, or a bus. Additionally, the number of wheels on vehicle 4 is not limited to four.

[0033] If server device 3 detects a vehicle 4 approaching an idle area AR, it sends notification information J1 to the terminal device 5 used by the user P of the detected vehicle 4. Notification information J1 contains information about the location to which the idle electric scooter 2A should be moved. Terminal device 5 is, for example, a smartphone with an application related to the electric scooter 2 installed. Hereinafter, this application will be simply referred to as the "application" and marked with the reference numeral "511". Terminal device 5 receives notification information J1 through the functions of application 511 and notifies the user of the location, etc., based on notification information J1.

[0034] When server device 3 detects that user P, whose vehicle 4 is approaching an idle area AR, moves the idle electric scooter 2 to a mobile location, server device 3 calculates a reward for user P. Then, server device 3 awards the calculated reward to user P. In this embodiment, money is exemplified as a reward, but the reward is not limited to money; for example, it could be a coupon, etc.

[0035] exist Figure 1 The image shows three vehicles: 4A, 4B, and 4C. Figure 1 The image shows a scenario where, on the path leading to destination D1, user P1 of vehicle 4A moves an idle electric scooter 2A, located in the idle area AR1, to stop TS1. Additionally, in... Figure 1 The image shows a scenario where, on the path leading to destination D2, user P2 of vehicle 4B moves an idle electric scooter 2A, located in the idle area AR2, to the rental station KS1. Additionally, in... Figure 1 The image shows a scenario where, on the road leading to destination D3, user P3 of vehicle 4C moves an idle electric scooter 2A located in the idle area AR3 to the nearest stop TS3 to the requester Y who made the request to use the electric scooter 2A. Figure 1 In this process, rewards are given to users P1, P2, and P3 respectively. Furthermore, requester Y requests the use of electric scooter 2 via a requester terminal 7, such as a smartphone. An application for making the usage request is installed on the requester terminal 7.

[0036] The mobile body management system 1 includes an electric scooter 2, a vehicle 4, and a terminal device 5.

[0037] Figure 2 This is a diagram showing the structure of the electric scooter 2, the vehicle 4, and the terminal device 5.

[0038] [2. Structure of an electric scooter]

[0039] First, the structure of the electric scooter 2 will be explained.

[0040] The electric scooter 2 includes a mobile control device 20, a mobile communication unit 21, a mobile GNSS (Global Navigation Satellite System) 22, a mobile battery 23, and a drive motor 24.

[0041] The mobile control device 20 includes a mobile processor 200 and a mobile memory 210, controlling various parts of the electric scooter 2. The mobile processor 200 is a processor such as a CPU (Central Processing Unit). The mobile processor 200 functions as a mobile communication control unit 201 by reading and executing the control program 211 stored in the mobile memory 210. The mobile memory 210 is a memory that stores programs and data. The mobile memory 210 stores the control program 211 and the data processed by the mobile processor 200. The mobile memory 210 has a non-volatile storage area. Alternatively, the mobile memory 210 may also have a volatile storage area, constituting the working area of ​​the mobile processor 200.

[0042] The mobile control device 20 is connected to the mobile communication unit 21, the mobile GNSS 22, the mobile battery 23, and the drive motor 24. Furthermore, the mobile control device 20 can also be connected to other devices.

[0043] The mobile communication unit 21 includes wireless communication hardware such as an antenna and wireless communication circuitry. The mobile communication unit 21 communicates with a server device 3 connected to the communication network NW via the communication network NW. The communication network NW can be any data communication network, such as a wide area communication network that includes a public line network.

[0044] The mobile GNSS 22 locates the current position of the electric scooter 2. The mobile GNSS 22 outputs the located current position information to the mobile control device 20.

[0045] The mobile battery 23 is a rechargeable battery. The mobile battery 23 supplies power to various parts of the electric scooter 2. The mobile battery 23 outputs charge level information to the mobile control device 20.

[0046] The drive motor 24 is powered by the mobile body battery 23. The drive motor 24 rotates the wheels of the electric scooter 2 under the control of the mobile body control device 20.

[0047] As described above, the mobile unit processor 200 functions as the mobile unit communication control unit 201.

[0048] The mobile communication control unit 201 communicates with the server device 3 via the mobile communication unit 21. The mobile communication control unit 201 generates first upload information J2 at predetermined intervals and sends the generated first upload information J2 to the server device 3. The first upload information J2 includes a mobile entity ID (identification information for the electric scooter 2), information about the current location of the electric scooter 2 as determined by the mobile entity GPS 22, and information about the charge level of the mobile entity battery 23. Furthermore, the mobile entity ID is pre-stored in the mobile entity memory 210.

[0049] [3. Vehicle Structure]

[0050] Next, the structure of vehicle 4 will be explained.

[0051] Vehicle 4 is equipped with a vehicle control device 40, a TCU (Telematics Control Unit) 41, a vehicle communication unit 42, a vehicle GNSS (Global Navigation Satellite System) 43, a vehicle touch panel 44, and a vehicle status sensor 45.

[0052] The vehicle control device 40 includes a vehicle processor 400 and a vehicle memory 410, controlling various parts of the vehicle 4. The vehicle processor 400 is a processor such as a CPU. The vehicle processor 400 functions as the first vehicle communication control unit 401 and the second vehicle communication control unit 402 by reading and executing the control program 411 stored in the vehicle memory 410. The vehicle memory 410 is a memory that stores programs and data. The vehicle memory 410 stores the control program 411 and the data processed by the vehicle processor 400. The vehicle memory 410 has a non-volatile storage area. Alternatively, the vehicle memory 410 may also have a volatile storage area, constituting the working area of ​​the vehicle processor 400.

[0053] The TCU 41, vehicle communication unit 42, vehicle GNSS 43, vehicle touch panel 44, and vehicle status sensor 45 are connected to the vehicle control unit 40. Furthermore, the vehicle control unit 40 can also be connected to other devices.

[0054] The vehicle communication unit 42 includes communication circuits and other communication devices. The vehicle communication unit 42 communicates with smartphones or other devices used by passengers in the vehicle 4. The communication standard of the vehicle communication unit 42 can be either a wireless communication standard or a wired communication standard.

[0055] The vehicle GNSS 43 determines the current position of the vehicle 4. If the vehicle 4 is equipped with a car navigation system (not shown), the vehicle GNSS 43 can utilize the GPS (Global Positioning System) unit of the car navigation system. The vehicle GNSS 43 outputs the positioning result to the vehicle control unit 40.

[0056] The vehicle touch panel 44 is a touch panel. The vehicle touch panel 44 displays various information according to the control of the vehicle control unit 40. In addition, the vehicle touch panel 44 outputs signals corresponding to touch operations to the vehicle control unit 40.

[0057] The vehicle status sensor 45 includes, for example, a triaxial acceleration sensor, a yaw rate sensor, and a speed sensor. The vehicle status sensor 45 outputs detection values ​​to the vehicle control unit 40 at predetermined intervals.

[0058] As described above, the vehicle processor 400 functions as both the first vehicle communication control unit 401 and the second vehicle communication control unit 402.

[0059] The first vehicle communication control unit 401 communicates with the server device 3 via the TCU 41. The first vehicle communication control unit 401 generates second upload information J3 at predetermined intervals and sends the generated second upload information J3 to the server device 3. The second upload information J3 includes the vehicle ID (as identification information of the vehicle 4), the current location determined by the vehicle's GNSS 43, the vehicle 4's direction of travel, and the vehicle 4's destination information. The vehicle ID is pre-stored in the vehicle memory 410. When generating the second upload information J3, the first vehicle communication control unit 401 determines the vehicle 4's direction of travel based on the current location determined by the vehicle's GNSS 43 and the detection values ​​from the vehicle status sensor 45. Furthermore, the first vehicle communication control unit 401 includes destination information input via the vehicle touch panel 44, etc., in the second upload information J3.

[0060] The second vehicle communication control unit 402 communicates with the device connected to the vehicle communication unit 42 via the vehicle communication unit 42.

[0061] [4. Structure of the terminal device]

[0062] Next, the structure of terminal device 5 will be described.

[0063] The terminal device 5 includes a terminal control device 50, a terminal communication unit 51, and a terminal touch panel 52.

[0064] The terminal control device 50 includes a terminal processor 500 and a terminal memory 510, and controls various parts of the terminal device 5. The terminal processor 500 is a processor such as a CPU. The terminal processor 500 functions as an application execution unit 501 by reading and executing the application 511 stored in the terminal memory 510. The terminal memory 510 is a memory that stores programs and data. The terminal memory 510 stores the application 511, programs other than the application 511, and data processed by the terminal processor 500. The terminal memory 510 has a non-volatile storage area. Alternatively, the terminal memory 510 may also have a volatile storage area, constituting the working area of ​​the terminal processor 500.

[0065] The terminal control device 50 is connected to the terminal communication unit 51 and the terminal touch panel 52. Furthermore, the terminal control device 50 can also be connected to other devices.

[0066] The terminal communication unit 51 includes communication hardware such as an antenna and a wireless communication circuit. In this embodiment, the terminal communication unit 51 communicates with the server device 3 via a communication network NW.

[0067] The terminal touch panel 52 is a touch panel. The terminal touch panel 52 displays various information under the control of the terminal control device 50. In addition, the terminal touch panel 52 outputs signals corresponding to touch operations to the terminal control device 50.

[0068] As described above, the terminal processor 500 functions as the application execution unit 501.

[0069] Application execution unit 501 communicates with server device 3 via terminal communication unit 51. Application execution unit 501 causes terminal touch panel 52 to display various information related to electric scooter 2. Application execution unit 501 accepts various inputs via terminal touch panel 52. Application execution unit 501 receives notification information J1 from server device 3. If application execution unit 501 receives input indicating that the movement of electric scooter 2 has been completed, it sends movement completion information J4, indicating the completion of the movement of electric scooter 2, to server device 3. The movement completion information J4 includes a user ID, which serves as identification information for user P. The user ID is pre-stored in terminal memory 510.

[0070] [5. Structure of the server device]

[0071] The mobile body management system 1 has a server device 3.

[0072] Figure 3 This is a diagram showing the structure of server device 3.

[0073] The server device 3 includes a server processor 30, which serves as a processor such as a CPU; a server memory 31, which serves as a memory for storing programs and data; and a server communication unit 32.

[0074] The server processor 30 functions as a receiving unit 301, a database processing unit 302, a first detection unit 303, a second detection unit 304, a first decision unit 305, a notification unit 306, a calculation unit 307, and a second decision unit 308 by reading and executing the control program 311 stored in the server memory 31.

[0075] Server memory 31 stores programs executed by server processor 30 and data processed by server processor 30. Server memory 31 stores control programs 311, a mobile entity database (DB), 312, a vehicle database, 313, a user database, 314, a lending station database, 315, a stop station database, 316, a usage request database, 317, map data, 318, and various other data executed by server processor 30. Server memory 31 has non-volatile storage areas. Alternatively, server memory 31 may also have volatile storage areas, constituting the working area of ​​server processor 30.

[0076] The mobile entity database 312 stores records containing information about each electric scooter 2. The information contained in a record for the electric scooter 2 includes the mobile entity ID, the current location information of the electric scooter 2, the charge level information of the mobile entity battery 23, and information on the stationary period as a period of inertia.

[0077] The vehicle database 313 stores records containing information about each vehicle 4. The information for each vehicle 4 in a record includes the vehicle ID, the vehicle 4's current location, the vehicle 4's direction of travel, the vehicle 4's destination, and the user ID. Furthermore, a pre-defined mapping between vehicle IDs and user IDs is established appropriately.

[0078] User database 314 stores records containing information about each user P. The information for user P in a record includes the user ID, communication information for communicating with the terminal device 5 used by user P, and reward information.

[0079] The lending station database 315 stores records containing information about each lending station (KS). The information for a lending station KS in a record includes the name of the lending station KS, the cumulative number of loans as a cumulative value, and the location information of the lending station KS. If the number of loans increases in the corresponding lending station KS, the information of the lending station KS is updated accordingly.

[0080] The stop database 316 stores records containing information about each stop TS. The information for a stop TS in a record includes the name of the stop TS, the number of available electric scooters 2 that can be stopped, and the location of the stop TS. The information for a stop TS is updated appropriately when the number of available scooters changes.

[0081] Using the request database 317, for each use request of the electric scooter 2, a record is stored containing the current location information of the requester Y.

[0082] Map data 318 stores road map information, facility information for various facilities, and data used for map matching. Road map information consists of a road network represented by lines on the map, including information related to the links that divide roads into multiple sections using intersections, forks, etc., as nodes, and define the sections between nodes as links. Facility information indicates the location and name of facilities.

[0083] The server communication unit 32 is equipped with communication hardware such as communication circuits. The server communication unit 32 communicates with the electric scooter 2, the vehicle 4, the terminal device 5, and the requester terminal 7 via the communication network NW.

[0084] As described above, the server processor 30 functions as a receiving unit 301, a database processing unit 302, a first detection unit 303, a second detection unit 304, a first decision unit 305, a notification unit 306, a calculation unit 307, and a second decision unit 308.

[0085] The receiving unit 301 communicates with the electric scooter 2, the vehicle 4, and the terminal device 5 via the server communication unit 32. The receiving unit 301 receives first upload information J2 from the electric scooter 2. The receiving unit 301 receives second upload information J3 from the vehicle 4. The receiving unit 301 receives movement completion information J4 from the terminal device 5. The receiving unit 301 receives usage request information indicating a usage request for the electric scooter 2 from the requester terminal 7. The usage request information includes the current location information of the requester terminal 7, representing the current location of the requester Y.

[0086] The database processing unit 302 updates the various databases stored in the server storage 31.

[0087] Upon receiving the first upload information J2 at the receiving unit 301, the database processing unit 302 updates the mobile entity database 312. The database processing unit 302 uses the record containing the mobile entity ID included in the received first upload information J2 as the update target. If the current location information included in the first upload information J2 differs from the current location information of the update target record, the database processing unit 302 updates the current location information of the update target record to the current location information included in the first upload information J2. If the current location information included in the first upload information J2 matches the current location information of the update target record, the database processing unit 302 calculates the period from the date and time the current location information was last updated to the present date and time as a stationary period, and updates the stationary period information of the update target record to the calculated stationary period.

[0088] Upon receiving the second uploaded information J3, the receiving unit 301 updates the vehicle database 313. The database processing unit 302 takes the record containing the vehicle ID included in the second uploaded information J3 as the update target. The database processing unit 302 updates the current location information, travel direction information, and destination information of the update target record with the information included in the second uploaded information J3.

[0089] When the calculation unit 307 (described later) outputs reward information associated with a user ID, the database processing unit 302 updates the reward information contained in records with the same user ID as the user ID output by the calculation unit 307 to include the reward information calculated by the calculation unit 307. In this way, the database processing unit 302 functions as a reward-giving unit that provides the reward calculated by the calculation unit 307.

[0090] When the receiving unit 301 receives a usage request information from the requester terminal 7, the database processing unit 302 stores a record containing the current location information of the requester Y in the usage request database 317. The database processing unit 302 stores the current location information contained in the usage request information as a record in the usage request database 317.

[0091] The first inspection unit 303 inspects the idle electric scooter 2. Specifically, the first inspection unit 303 inspects the idle electric scooter 2A by referring to the mobile body database 312, the lending station database 315, and the rest station database 316, and by determining from the mobile body database 312 the records indicating the current location outside the designated location and the period of inactivity being more than the designated period.

[0092] The second detection unit 304 detects vehicles 4 approaching the idle area AR, which includes the current position of the idle electric scooter 2A detected by the first detection unit 303. A vehicle 4 approaching the idle area AR is defined as a vehicle 4 whose separation distance from the idle area AR is less than a predetermined distance (e.g., 1 km) and whose direction of travel is towards the idle area AR. The second detection unit 304 refers to the moving body database 312 and map data 318 to identify the position and size of the idle area AR, including the current position of the idle electric scooter 2A detected by the first detection unit 303. Next, the second detection unit 304 refers to the vehicle database 313 to detect vehicles 4 whose separation distance from the identified idle area AR is less than the predetermined distance and whose direction of travel is towards the identified idle area AR. Specifically, the second detection unit 304 determines from the vehicle database 313 records indicating the current position of the identified idle area AR whose separation distance is less than the predetermined distance and whose direction of travel is towards the identified idle area AR.

[0093] The first decision unit 305 determines from a plurality of designated locations the moving location to which the electric scooter 2 detected by the first detection unit 303 will move. If the first decision unit 305 determines the moving location, it outputs the determined moving location information to the notification unit 306. The operation of the first decision unit 305 will be described later.

[0094] The notification unit 306 notifies the user P of vehicle 4, which is detected by the second detection unit 304, of the location of movement determined by the first decision unit 305. Specifically, the notification unit 306, referring to the vehicle database 313 and the user database 314, sends notification information J1 to the terminal device 5 used by the user P of vehicle 4, which is detected by the second detection unit 304. The notification information J1 sent by the notification unit 306 contains information about the location of movement determined by the first decision unit 305.

[0095] When the calculation unit 307 detects that user P of vehicle 4, detected by the second detection unit 304, moves electric scooter 2, detected by the first detection unit 303, to a location determined by the first decision unit 305, it calculates a reward for user P of vehicle 4. The calculation unit 307 may, for example, calculate the reward in a way that varies depending on the type of location. Alternatively, the calculation unit 307 may calculate the reward in a way that varies depending on the distance the electric scooter 2 is moved. If the calculation unit 307 calculates a reward, it outputs the calculated reward information to the database processing unit 302. When outputting the calculated reward information to the database processing unit 302, the calculation unit 307 associates the user ID of user P, the recipient of the calculated reward, with the calculated reward information.

[0096] The second decision-making unit 308 refers to the mobile body database 312 to determine the location of the newly designated site. The details of the second decision-making unit 308 will be described later.

[0097] Next, the operation of each part of the mobile body management system 1 will be explained.

[0098] [6. Actions of the Mobile Entity Management System]

[0099] First, the actions of the mobile body management system 1 involved in the notification of mobile locations will be explained.

[0100] Figure 4 This is a flowchart illustrating the actions of the mobile body management system 1.

[0101] exist Figure 4 In the flowchart, FA represents the actions of server device 3, and FB represents the actions of terminal device 5.

[0102] As shown in flowchart FA, the first detection unit 303 of the server processor 30 determines whether a trigger for detecting an idle electric scooter 2A has occurred (step SA1). Examples of such triggers include the arrival of a pre-defined period or the updating of the mobile object database 312.

[0103] If the first detection unit 303 determines that no trigger for detecting an idle electric scooter 2A has occurred (step SA1: No), it will perform the determination in step SA1 again.

[0104] On the other hand, when the first detection unit 303 determines that a trigger for detecting an idle electric scooter 2A has occurred (step SA1: Yes), it refers to the mobile body database 312 and detects the idle electric scooter 2A (step SA2).

[0105] The first detection unit 303 determines whether an idle electric scooter 2A can be detected (step SA3).

[0106] If the first detection unit 303 determines that an idle electric scooter 2A cannot be detected (step SA3: No), the server processor 30 ends the process.

[0107] On the other hand, if the first detection unit 303 determines that an idle electric scooter 2A can be detected (step SA3: Yes), the second detection unit 304 refers to the vehicle database 313 and detects the vehicle 4 that is close to the idle area AR (step SA4).

[0108] The second detection unit 304 determines whether a vehicle 4 approaching the idle area AR can be detected (step SA5).

[0109] If the second detection unit 304 determines that it has failed to detect vehicle 4 approaching the idle area AR (step SA5: no), the server processor 30 ends the process.

[0110] On the other hand, if the second detection unit 304 determines that a vehicle 4 approaching the idle area AR can be detected (step SA5: yes), the first decision unit 305 determines the location of movement (step SA6).

[0111] Here, the decision on the location of the first decision section 305 will be described in detail.

[0112] Figure 5 This is a flowchart FC showing the operation of the first decision unit 305.

[0113] The first decision unit 305 refers to the vehicle database 313 and map data 318 to search for a route from the current location of the vehicle 4 detected by the second detection unit 304 to the destination of the vehicle 4 (step SC1).

[0114] Next, the first decision unit 305 refers to the lending station database 315 and the stop station database 316, and determines the lending station KS and stop station TS located within a specified distance (e.g., 500m) from the route searched in step SC1 as candidates for the mobile location (step SC2).

[0115] The first decision unit 305 determines whether a candidate mobile location can be identified in step SC2 (step SC3).

[0116] If the first decision unit 305 determines in step SC2 that no candidate for a moving location can be determined (step SC3: No), it does not decide on a moving location and ends the action of deciding on a moving location.

[0117] On the other hand, if it is determined in step SC2 that a candidate for a mobile location can be identified (step SC3: yes), the first decision unit 305 determines whether the candidate mobile locations identified in step SC2 include multiple lending stations KS (step SC4).

[0118] If the first decision unit 305 determines that multiple lending stations (KS) are included (step SC4: Yes), it refers to the cumulative number of loans recorded in the lending station database 315 and excludes lending stations (KS) with a cumulative number of loans exceeding a certain number) from the candidates for mobile locations (step SC5). The certain number is appropriately determined through prior testing, simulation, etc. The certain number is, for example, 200 units.

[0119] On the other hand, if the first decision unit 305 determines that the candidate mobile locations identified in step SC2 do not include multiple lending stations KS (step SC4: No), it skips the processing in step SC5.

[0120] The first decision unit 305 determines whether the candidate mobile location includes a stop station TS (step SC6).

[0121] If the first decision unit 305 determines that the candidate mobile location includes a stop station TS (step SC6: Yes), it refers to the idle quantity information of the records stored in the stop station database 316 and excludes the stop station TS with zero idle quantity from the candidate mobile location (step SC7).

[0122] On the other hand, if the first decision unit 305 determines that the candidate for mobile location does not include the rest station TS (step SC6: no), it skips step SC7.

[0123] The first decision unit 305 determines whether there are any remaining candidates for mobile locations (step SC8).

[0124] If the first decision unit 305 determines that there are no remaining candidates for the move location (step SC8: No), it does not decide on the move location and ends the action of deciding on the move location.

[0125] On the other hand, if it is determined that there are remaining candidates for mobile locations (step SC8: Yes), the first decision unit 305 determines whether there are multiple remaining candidates for mobile locations (step SC9).

[0126] If the first decision unit 305 determines that there are no more candidates for mobile locations (step SC9: No), it will decide the candidate mobile location as a mobile location (step SC10).

[0127] If the first decision unit 305 determines that there are multiple remaining candidates for the mobile location (step SAC9: Yes), it determines whether there is a lending station KS or a stop station TS located within a specified distance from the location of the requester Y among the candidates for the mobile location (step SC11).

[0128] If the first decision unit 305 determines that there is no lending station KS or rest station TS located within a specified distance from the location of the requester Y (step SC11: No), it will determine the candidate of the mobile location that is closest to the route searched in step SC1 as the mobile location (step SC12).

[0129] On the other hand, if the first decision unit 305 determines that there is a lending station KS or a resting station TS located within a specified distance from the requester Y's location (step SC11: Yes), it determines the lending station KS or the resting station TS located closest to the requester Y's current location as the mobile location (step SC13).

[0130] Return to Figure 4 The flowchart FA describes the process where the first decision unit 305 determines whether a mobile location can be determined (step SA7).

[0131] If the first decision unit 305 determines that the location of the move cannot be determined (step SA7: No), the server processor 30 terminates the process.

[0132] On the other hand, if the first decision unit 305 determines that the location of the move can be determined (step SA7: Yes), the notification unit 306 sends the notification information J1 to the terminal device 5 (step SA8).

[0133] As shown in flowchart FB, the application execution unit 501 of terminal device 5 receives notification information J1 from server device 3 (step SB1).

[0134] Next, the application execution unit 501 sends a notification related to the idle electric scooter 2A based on the received notification information J1 (step SB2).

[0135] In step SB2, for example, the application execution unit 501 displays a notification screen on the terminal touch panel 52 to notify users of information related to the idle electric scooter 2A. This notification screen includes information such as the location of the idle electric scooter 2A and the location of its movement.

[0136] Next, the operation of the mobile body management system 1 when the electric scooter 2 moves to the designated location will be explained.

[0137] Reference Figure 1 This section provides a detailed description of the actions of the mobile body management system 1.

[0138] exist Figure 1 The image shows vehicle 4A heading towards destination D1. Figure 1 In the example, regarding vehicle 4A, in Figure 4 During the operation, rest stations TS1 and TS2 were identified as candidate mobile locations. Figure 1 In the example, the number of idle units at stop TS2 is zero, and the number of idle units at stop TS1 is 1. Therefore, in Figure 1 In the example, as a mobile location, stop TS1 is notified to user P1 of vehicle 4A.

[0139] exist Figure 1 The image shows vehicle 4B heading towards destination D2. Figure 1 In the example, regarding vehicle 4B, in Figure 4 In the process, lending stations KS1 and KS2 were identified as candidate mobile locations. Figure 1 In the example, the cumulative number of loans issued by lending station KS2 is less than the required number, while the cumulative number of loans issued by lending station KS1 is more than the required number. Therefore, in Figure 1 In the example, as a mobile location, taxi stand KS1 is notified to user P2 of vehicle 4B.

[0140] exist Figure 1 The image shows vehicle 4C heading towards destination D3. Figure 1 In the example, regarding vehicle 4C, in Figure 4 In the process, lending station KS3 and dwell station TS3 were identified as candidate mobile locations. Figure 1 In the example, the nearest designated location to requester Y is stop TS3. Therefore, in Figure 1 In the example, as a mobile location, the stop station TS3 is notified to the user P3 of vehicle 4C.

[0141] Figure 6 This is a flowchart illustrating the actions of the mobile body management system 1.

[0142] exist Figure 6 In the flowchart, FD represents the actions of server device 3, and FE represents the actions of terminal device 5.

[0143] If the application execution unit 501 receives input indicating that the electric scooter 2 has completed its movement via the terminal touch panel 52, it sends the movement completion information J4 to the server device 3 (step SE1).

[0144] The receiving unit 301 of the server device 3 receives the motion completion information J4 from the terminal device 5 (step SD1).

[0145] Next, the calculation unit 307 of the server device 3 calculates the reward (step SD2). The calculation unit 307 matches the calculated reward information with the user ID contained in the movement completion information J4 received in step SD1 and outputs it to the database processing unit 302.

[0146] Next, the database processing unit 302 calculates the reward calculated in step SD2 (step SD3).

[0147] [8. The actions of the Second Decision-Making Department]

[0148] Next, the operation of the second decision unit 308 will be explained.

[0149] The second decision section 308 determines whether a trigger has occurred that initiates the determination of the location of a newly established designated location.

[0150] The second decision unit 308 refers to the current location information of each record stored in the mobile body database 312 and the map data 318 to determine a specified area (e.g., a range with a diameter of 1 km) where there are more than a specified number (e.g., 20) of idle electric scooters 2.

[0151] Next, the second decision-making unit 308 determines the location of the newly established designated site within the determined area.

[0152] [9. Other Implementation Methods]

[0153] In other embodiments, when the first detection unit 303 detects multiple idle electric scooters 2A, the second detection unit 304 may also detect each idle electric scooter 2A one by one according to a predetermined priority order. Here, the predetermined priority order is taken as an example of ordering from lowest to highest charge level. In this case, the second detection unit 304 refers to the mobile body database 312 to determine the charge level of each idle electric scooter 2A detected by the first detection unit 303. Then, based on the determined charge level, the second detection unit 304 determines the priority order of the idle electric scooters 2A moving to a designated location. That is, the second detection unit 304 determines the priority order of the idle electric scooters 2A moving to the designated location in a manner where the lower the charge level, the higher the priority. Then, the second detection unit 304 determines the vehicle 4 that moves the idle electric scooters 2A one by one according to the determined priority order.

[0154] The first decision unit 305 in other embodiments can also perform... Figure 5The movement location is determined by different actions. For example, in another embodiment, the first decision unit 305 searches for a route from the current location of vehicle 4 detected by the second detection unit 304 to the destination of vehicle 4, and determines the nearest rental station KS to the searched route, or the nearest stop TS to the searched route with a non-zero number of available units, as the movement location. Alternatively, in another embodiment, the first decision unit 305 searches for a route from the current location of vehicle 4 detected by the second detection unit 304 to the destination of vehicle 4, determines one or more rental stations KS located within a predetermined distance (e.g., 500m) from the searched route, and if multiple rental stations KS are determined, the rental station KS with a cumulative rental number of more than a predetermined number of units is determined as the movement location. Additionally, for example, in other embodiments, the first decision unit 305 searches for a route from the current location of the vehicle 4 detected by the second detection unit 304 to the destination of the vehicle 4, and determines at least one of a rental station KS and a rest station TS located within a predetermined distance (e.g., 500m) from the searched route. From the determined rental station KS or rest station TS, the rental station KS or rest station TS closest to the location of the requester who made the request to use the electric scooter 2 is determined as the mobile location.

[0155] In the above embodiments, the designated locations are the lending station KS and the rest stop TS. However, the designated location is not limited to the lending station KS and the rest stop TS. The designated location can be either the lending station KS or the rest stop TS. In addition, the designated location can also include other types of locations. For example, the designated location can also include a repair shop that repairs the electric scooter 2. In this case, the mobility control device 20 of the electric scooter 2 performs fault detection on the electric scooter 2, and if a fault is detected, it sends the information to the server device 3. Moreover, if the user P of the vehicle 4 moves the electric scooter 2, which has been reported as having a fault, to the repair shop, the mobility management system 1 will calculate the reward given to the user P to be higher than the reward given if the scooter is moved to the lending station KS or the rest stop TS. In addition, the designated location is not limited to a stationary location; for example, it can also be a movable location such as a vehicle recycling center.

[0156] In the above embodiment, the first decision unit determines a station TS that can accommodate one or more electric scooters 2 as a mobile location. However, the station TS that is determined as a mobile location only needs to accommodate a number of electric scooters 2 that are not zero, and the number of electric scooters 2 that can accommodate is N (N is an integer greater than or equal to 1) or more.

[0157] In the above embodiments, an electric scooter 2 is exemplified as a mobile body of the present disclosure, but the mobile body is not limited to the electric scooter 2. The mobile body of the present disclosure can be used as long as it is rideable and can be moved by the vehicle 4.

[0158] In the above embodiment, the terminal device 5 is configured to send notifications related to the idle electric scooter 2A. However, the vehicle 4 can also send notifications related to the idle electric scooter 2A. In this configuration, the vehicle control device 40 receives notification information J1 from the terminal device 5 via the vehicle communication unit 42 and sends a notification based on the notification information J1. Alternatively, in this configuration, the vehicle control device 40 can also send the movement completion information J4 to the server device 3 via the TCU 41, or via the vehicle communication unit 42 and the terminal device 5.

[0159] The server processor 30, mobile processor 200, vehicle processor 400, and terminal processor 500 can be composed of a single processor or multiple processors. The server processor 30, mobile processor 200, vehicle processor 400, and terminal processor 500 can also be hardware programmed to implement corresponding functional units. That is, the server processor 30, mobile processor 200, vehicle processor 400, and terminal processor 500 can, for example, be composed of ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

[0160] in addition, Figure 2 and Figure 3 The electric scooter 2, server device 3, vehicle 4, and terminal device 5 shown are just one example; the specific installation method is not particularly limited. That is, it is not necessary to install hardware corresponding to each part; of course, it is also possible to configure each part to implement its function by executing a program through a processor. In addition, in the above embodiment, a part of the function implemented by software can be implemented as hardware, or a part of the function implemented by hardware can be implemented by software. Furthermore, the specific structural details of the other parts of the electric scooter 2, server device 3, vehicle 4, and terminal device 5 can also be arbitrarily changed.

[0161] In addition, for example, Figure 4 , Figure 5 as well as Figure 6The steps shown are divided according to the main processing content for ease of understanding, and the present invention is not limited to the method or name of the division of processing units. Depending on the processing content, it can also be divided into more step units. Alternatively, it can be divided in a way that includes more processing within a single step unit. Furthermore, the order of these steps can be appropriately changed without affecting the spirit of the present invention.

[0162] [10. Structure supported by the above embodiments]

[0163] The above implementation supports the following structures.

[0164] (Structure 1) A mobile vehicle management system comprising: a first detection unit that detects rideable mobile vehicles that have been idle for a specified period or more outside a specified location; a second detection unit that detects vehicles approaching an idle area containing the current location of the mobile vehicle detected by the first detection unit, based on information about the current location of the mobile vehicle detected by the first detection unit; and a calculation unit that calculates a reward for the user of the vehicle detected by the second detection unit if the user of the vehicle detected by the second detection unit moves the mobile vehicle to the specified location.

[0165] According to the mobile vehicle management system of Structure 1, when a mobile vehicle that has been idle for a specified period outside a designated location is moved to the designated location, a reward is calculated and given to the user of the vehicle detected by the second detection unit. Therefore, by moving a mobile vehicle that has been idle for a specified period outside a designated location to the designated location, a reward can be given to the user of the vehicle. Thus, the motivation of vehicle users to move idle mobile vehicles to designated locations can be stimulated, and the number of idle mobile vehicles can be effectively reduced.

[0166] (Structure 2) The mobile body management system of Structure 1, wherein the mobile body management system comprises: a first decision unit that determines from a plurality of the specified locations a mobile body detected by the first detection unit shall move to a mobile location; and a notification unit that notifies the user of the vehicle of the mobile location determined by the first decision unit.

[0167] According to the mobile vehicle management system of Structure 2, vehicle users can determine the mobile location to which vehicles that have been idle for a specified period outside of designated locations can be moved, thus increasing the likelihood that vehicle users will move the vehicles to designated locations. Therefore, the number of idle mobile vehicles can be reduced more effectively.

[0168] (Structure 3) The mobile body management system of Structure 2, wherein the first decision unit determines the mobile location based on the destination of the vehicle detected by the second detection unit.

[0169] According to the mobile vehicle management system of Structure 3, vehicle users can move the mobile vehicle to the designated location along the vehicle's path toward the destination. Therefore, it is possible to prevent vehicle users from moving away from their destination in order to move the mobile vehicle, thereby reducing the incentive to move idle mobile vehicles to the designated location.

[0170] (Structure 4) A mobile body management system of Structure 2 or Structure 3, wherein the first decision unit determines a station where N or more mobile bodies can stay as the mobile location, wherein N is an integer of 1 or more.

[0171] According to the mobile body management system of Structure 4, the mobile body is notified of the mobile location that enables the mobile body to move, thus increasing the likelihood that vehicle users can move the mobile body and more effectively reducing the number of idle mobile bodies.

[0172] (Structure 5) A mobile body management system of any one of Structures 2 to 4, wherein the first decision unit determines a lending station where the number of mobile bodies lent out is a predetermined number or more as the mobile location.

[0173] According to the mobile body management system of Structure 5, mobile bodies can be moved to lending stations with a specified number of lending units, thus effectively assisting in the lending of mobile bodies.

[0174] (Structure 6) A mobile body management system of any one of Structures 2 to 5, wherein, when there is a requester who has made a request to use the mobile body, the first decision unit determines the designated location closest to the requester's location as the mobile location.

[0175] According to the mobile body management system of Structure 6, the likelihood of requesters being able to use mobile bodies quickly can be increased, thus improving the convenience for requesters.

[0176] (Structure 7) A mobile body management system of any one of Structures 1 to 6, wherein the mobile body has a first charging device as a driving source, and the second detection unit performs the following processing: when the first detection unit detects multiple mobile bodies, it determines the priority order of the mobile bodies moving to the designated location based on the charging status of the first charging device of the mobile body detected by the first detection unit; and detects the vehicle according to the determined priority order.

[0177] According to the mobile body management system of structure 7, mobile bodies with low charge levels can be prioritized for movement to designated locations. Therefore, mobile bodies with low charge levels and currently idle can be quickly recharged. Furthermore, mobile bodies can be moved to designated locations before they become undetectable due to reduced charge levels. Thus, the number of idle mobile bodies can be effectively reduced.

[0178] (Structure 8) A mobile body management system of any one of Structures 1 to 7, wherein the mobile body has a first charging device as a driving source, and the second detection unit detects the vehicle having a second charging device capable of charging the first charging device.

[0179] According to the mobile body management system of structure 8, the mobile body can be charged when the user of the vehicle moves the mobile body, thus enabling the mobile body that has been moved to the mobile location to become usable.

[0180] (Structure 9) A mobile body management system of any one of Structures 1 to 8, wherein the mobile body management system includes a second decision unit that determines the location of the newly established designated location based on the current location of the mobile body detected by the first detection unit.

[0181] According to the mobile body management system of Structure 9, designated locations can be set up in areas where a large number of mobile bodies have been idle for a specified period of time outside of designated locations, which can more effectively reduce the number of idle mobile bodies.

[0182] (Structure 10) A control method for a mobile vehicle management system, comprising the following steps: detecting a rideable mobile vehicle that has been idle for a specified period or more outside a specified location; detecting vehicles approaching an idle area containing the current location of the detected mobile vehicle based on information about the current location of the detected mobile vehicle; and calculating a reward for the user of the detected vehicle if the user of the detected vehicle moves the mobile vehicle to the specified location.

[0183] The control method of the mobile body management system of structure 10 achieves the same effect as the mobile body management system of structure 1.

Claims

1. A mobile vehicle management system, wherein mobile vehicles and multiple vehicles are connected to a server device via a communication network, wherein, The server device includes: The first inspection department inspects the mobile body that is capable of being used and has been idle for a specified period or more outside of a designated location. The second detection unit detects at least one vehicle from the plurality of vehicles that is close to an idle area containing the current position of the moving body detected by the first detection unit, based on information about the current position of the moving body detected by the first detection unit. The calculation unit calculates a reward to be given to at least one user of the vehicle detected by the second detection unit when the user of the vehicle moves the mobile body to the designated location. The first decision unit determines from among the plurality of defined locations the location to which the moving body detected by the first detection unit will move; as well as The notification department notifies at least one user of the vehicle of the location of the movement determined by the first decision department. The server device receives information from each of the multiple vehicles at predetermined intervals, including information about the current location of the vehicle as determined by the vehicle's global navigation satellite system, and information about the vehicle's destination input by the vehicle's user using the vehicle's touch panel. The first decision unit searches for a route from the vehicle's current location to its destination, received from the vehicle, for at least one of the vehicles detected by the second detection unit, and determines the location of movement based on the searched route.

2. The mobile body management system according to claim 1, wherein, The first decision unit determines the station where N or more of the mobile bodies can stay as the mobile location, where N is an integer greater than or equal to 1.

3. The mobile body management system according to claim 2, wherein, The first decision unit determines a lending station where the number of mobile units lent out is a predetermined number or more as the mobile location.

4. The mobile body management system according to claim 1, wherein, In the event that a requester has made a request to use the mobile device, the first decision unit determines the designated location closest to the requester's location as the mobile location.

5. The mobile body management system according to claim 1, wherein, The mobile body has a first charging device as a driving source. The second detection unit performs the following processing: When the first detection unit detects multiple moving bodies, the priority order of the moving bodies moving to the designated location is determined based on the charging status of the first charging device of the moving bodies detected by the first detection unit. The vehicles are detected according to the determined priority order.

6. The mobile body management system according to claim 1, wherein, The mobile body has a first charging device as a driving source. The second detection unit detects the vehicle equipped with a second charging device capable of charging the first charging device.

7. The mobile body management system according to any one of claims 1 to 6, wherein, The mobile body management system includes a second decision unit that determines the location of the newly established designated location based on the current location of the mobile body detected by the first detection unit.

8. A control method for a mobile body management system, wherein the mobile body management system is a system in which mobile bodies, multiple vehicles, and a server device are connected via a communication network, wherein, The control method of the mobile body management system includes the following steps: The mobile vehicle that is capable of being used has been idle outside a designated location for a specified period of time or more. Based on the information of the current location of the detected moving body, at least one vehicle is detected from the plurality of vehicles that is close to an idle area containing the current location of the detected moving body; If a user of the detected vehicle moves the mobile body to the designated location, a reward is calculated for the user of at least one of the detected vehicles. The location to which the detected moving body will be moved is determined from among the multiple specified locations; The determined location of movement shall be notified to at least one user of the vehicle; The vehicle receives information from each of the multiple vehicles at predetermined intervals regarding the vehicle's current location as determined by its global navigation satellite system, as well as destination information input by the vehicle's user using the vehicle's touch panel. as well as For at least one vehicle detected in the step of detecting at least one of the multiple vehicles, a route from the vehicle's current location to the vehicle's destination, received from the vehicle, is searched, and the location of movement is determined based on the searched route.

Citation Information

Patent Citations

  • Information processing system, information processing program, information processing device, and information processing method

    JP2020016668A

  • Shared bicycle scheduling method and system based on smart lamp pole and smart lamp pole

    CN106952468A

  • KR20200062474A