JP7490709B2 - Mobile object usage management system and mobile object usage management method - Google Patents

Description

The present invention relates to a mobile object usage management system and a mobile object usage management method.

In recent years, efforts to provide access to sustainable transportation systems that take into consideration vulnerable transport participants have been gaining momentum. To achieve this, we are focusing on research and development into sharing to further improve the safety and convenience of transport. For example, Patent Literature 1 discloses a system for providing a vehicle dispatch service that uses a single shared vehicle in response to reservations from multiple users, as an example of a technology for sharing moving objects such as vehicles.

JP 2022-46311 A

In the case of sharing a vehicle, it is important to appropriately allocate opportunities to use the vehicle to each user. For example, if the amount of funds contributed by each user to purchase the vehicle varies from user to user, equally allocating opportunities to use the vehicle to all users may create a sense of unfairness.
In order to solve the above problems, the present application aims to enable fair use of vehicles jointly purchased by multiple users, thereby contributing to the development of a sustainable transportation system.

One aspect for achieving the above-mentioned object is a mobile object usage management system having a management device that manages information on a mobile object used by a plurality of users including a first user and a second user , the management device comprising: a memory unit that stores reservation information specifying a time period during which the user will use the mobile object, and an occupancy upper limit time that sets an upper limit for a time period during which each of the users can use the mobile object; and a reception unit that accepts applications from the users to use the mobile object and generates or updates the reservation information so that a cumulative value of the time during which the users use the mobile object over a predetermined period does not exceed the occupancy upper limit time, the occupancy upper limit time being a time corresponding to an investment amount contributed by each of the users for the purchase of the mobile object, the reservation information including occupancy time information specifying an occupancy time period during which the first user will occupy the mobile object, and when an application is received from the first user not to use the mobile object during the occupancy time period, the management device waits for an application to use the mobile object from a user other than the first user, and when an application is made from the second user to use the mobile object during a time period that overlaps with the occupancy time period, the management device accepts the application from the second user and generates the reservation information without imposing a restriction based on the occupancy upper limit time of the second user.

According to the above configuration, the time that multiple users can occupy a vehicle jointly purchased can be limited in accordance with the amount of investment the users made to purchase the vehicle. This allows the difference in investment amount to be reflected in the vehicle reservation made by users, realizing usage that takes into account fairness between users. This allows users to be provided with a comfortable shared experience, contributing to the development of a sustainable transportation system.

FIG. 1 is an explanatory diagram showing an overview of a management system. Block diagram of the management system. FIG. 4 is a schematic diagram showing an example of information stored in a management device. 4 is a flowchart showing the operation of the management system. FIG. 13 is a diagram showing an example of a reservation screen displayed on a user terminal. 4 is a flowchart showing the operation of the management system. 4 is a flowchart showing the operation of the management system. 4 is a flowchart showing the operation of the management system. 4 is a flowchart showing the operation of the management system.

[1. Overview of the management system]
FIG. 1 is an explanatory diagram showing an overview of a management system 1 according to the present embodiment.
The management system 1 is a system that accepts and manages reservations for use of a mobile object M by multiple users U. The management system 1 corresponds to an example of a mobile object usage management system. There is no limit to the number of users U and the number of mobile objects M that the management system 1 manages. In this embodiment, as an example, a case will be described in which one mobile object M is used by three users U1, U2, and U3, and when there is no need to distinguish between the users U1, U2, and U3, they will be referred to as users U.

The mobile body M is a mobile body that the user U can ride, and is, for example, a four-wheeled automobile, a motorcycle, a bicycle, or a three-wheeled automobile. The mobile body M may be a passenger car or a cargo vehicle, or may be a large vehicle. The mobile body M may also be a ship or an aircraft. FIG. 1 illustrates a motorcycle as an example of the mobile body M. The users U1, U2, and U3 are people who pooled together the purchase funds to purchase the mobile body M, and jointly own the mobile body M.

User U uses user terminal 210. In the example of FIG. 1, user U1 uses user terminal 210A, user U2 uses user terminal 210B, and user U3 uses user terminal 210C. When there is no need to distinguish between user terminals 210A, 210B, and 210C, they are referred to as user terminal 210. User terminal 210 is a portable computer, for example, a mobile device such as a smartphone, or a portable computer known as a handheld computer.

The management system 1 has a management device 100. The management device 100 is a computer, for example a server computer, that manages information related to the use of the mobile body M. The management device 100 accepts a reservation by a user U when the user U intends to exclusively use the mobile body M. For example, as described below, the management device 100 accepts a reservation application from a user terminal 210 used by the user U. When a reservation is accepted by the management device 100, the user U can exclusively use the mobile body M during the reserved time period.

The management device 100 is communicatively connected to the user terminal 210 via a communication network 500. The communication network 500 includes, for example, a cellular communication network, a Wi-Fi (registered trademark) network, Bluetooth (registered trademark), the Internet, a Wide Area Network (WAN), a Local Area Network (LAN), a public line, a provider device, a dedicated line, a wireless base station, and the like. These components may each perform wireless communication directly without going through the communication network 500.

The mobile body M is equipped with a mobile terminal 270. The mobile terminal 270 is capable of communicating with the management device 100 via the communication network 500. The mobile terminal 270 transmits information about the state of the mobile body M to the management device 100.

[2. Management System Configuration]
Fig. 2 is a block diagram of the management system 1, and shows the functional configuration of a management device 100, a user terminal 210, and a mobile terminal 270 that constitute the management system 1. Fig. 3 is a schematic diagram showing an example of information stored in the management device 100.

The management device 100 includes a processor 10, a storage unit 20, and a communication unit 30. The processor 10 is an information processing device such as a CPU (Central Processing Unit) or a microcontroller. The storage unit 20 stores programs executed by the processor 10 and data processed by the processor 10. Examples of the storage unit 20 include non-volatile storage devices configured using semiconductor memory devices such as flash memory, magnetic storage devices, optical storage devices, etc. The storage unit 20 may also include a volatile storage area configured using a semiconductor memory device, and the volatile storage area may form a work area for the processor 10. If the processor 10 is configured as an integrated device that integrates a volatile memory, the storage unit 20 is configured as a non-volatile storage device.

The memory unit 20 stores a control program 21, mobile object information 22, user information 23, reservation information 24, history information 25, and maintenance reference information 26. The control program 21 is a program executed by the processor 10 to control the management device 100.

3, the mobile unit information 22 includes a mobile unit ID (IDentifier) and maintenance information. The mobile unit ID is identification information for identifying the mobile unit M. The mobile unit ID is unique information assigned to each individual mobile unit M, and is information that can identify each individual mobile unit M. The mobile unit ID is, for example, a number assigned by the manufacturer of the mobile unit M, a number assigned to the mobile unit M based on laws and regulations, or a number assigned to the mobile unit M by the management system 1. The maintenance information is information related to the maintenance of the mobile unit M. The maintenance of the mobile unit M refers to work required to maintain the mobile unit M in an operable state. For example, the maintenance of the mobile unit M may include inspection of the mobile unit M required by laws and regulations, replacement of consumable parts equipped in the mobile unit M, adjustment of parts equipped in the mobile unit M, etc. When the mobile unit M has an internal combustion engine, the maintenance of the mobile unit M includes, for example, refueling, and refilling or replacing lubricating oil or hydraulic oil of the internal combustion engine. When the mobile body M has a battery as a driving source, the maintenance of the mobile body M includes, for example, charging or replacing the battery of the mobile body M. The maintenance information is information for determining the necessity of maintenance of the mobile body M and the timing to perform the maintenance. For example, the maintenance information includes one or more of the travel distance of the mobile body M, the remaining amount of fuel of the mobile body M, the remaining capacity of the battery of the mobile body M, etc.

The user information 23 includes a mobile object ID, a user ID, investment information, an occupancy limit time, and a maintenance history. The mobile object ID is as described above. The user ID is unique information assigned to the user U, and is information that can identify each user U. The user ID may be a number assigned to the user U by the management system 1, or a number assigned to the user U based on laws and regulations, such as a driver's license number. The user information 23 is stored in the storage unit 20 in association with the mobile object ID and the user ID. For example, if one user U1 owns multiple mobile objects M, the user information 23 corresponding to each mobile object M owned by the user U1 is stored in the storage unit 20 in association with the user U1.

The investment information is information related to the amount invested by user U when user U purchased mobile unit M. For example, if user U1 jointly purchases mobile unit M with users U2 and U3, user information 23 corresponding to user U1 includes information related to the amount invested by user U1 when purchasing mobile unit M. The investment information is, for example, information indicating the proportion of the investment amount made by user U1 to the total purchase price of mobile unit M, or information indicating the purchase price of mobile unit M and the investment amount made by user U1.

The occupancy upper limit time is information indicating the upper limit of the time that user U occupies mobile unit M. The occupancy upper limit time is the upper limit of the accumulated value of the time that user U occupies mobile unit M in a specified period. For example, the occupancy upper limit time of user U1 is the upper limit of the accumulated value of the time that user U1 uses mobile unit M in one month. User U1 can use mobile unit M as long as the usage time of mobile unit M in one month does not exceed user U1's occupancy upper limit time. The same applies to user U2 and user U3. The specified period is not limited to one month. For example, the occupancy upper limit time may be the upper limit of the time that user U1 can use mobile unit M in one week, one year, or other unit.

Here, occupying a moving body M can be rephrased as using the moving body M. When the moving body M is capable of carrying multiple people, the user U who occupies the moving body M is the user U who drives or operates the moving body M.

The occupancy upper limit time is determined to be a time corresponding to the investment amount invested by the user U to purchase the mobile unit M. For example, when three users U1, U2, and U3 jointly purchase the mobile unit M, the occupancy upper limit time of the users U1, U2, and U3 is determined to be the same ratio as the investment amount of the users U1, U2, and U3. In this case, the total of the occupancy upper limit time of all the users U who jointly purchased the mobile unit M does not need to be a time corresponding to the entire predetermined period.
The ratio of the occupancy upper limit time may not be equal to the ratio of the investment amount of the user U. For example, the occupancy upper limit time may be a length obtained by dividing a time corresponding to the ratio of the investment amount of the user U into one-hour or five-hour units.

User information 23 necessarily includes the maximum occupancy time, but may not include the investment information. For example, if the maximum occupancy time reflects the percentage of the investment amount, the percentage of the maximum occupancy time and the content of the investment information are similar or identical, so the investment information can be omitted.

The maintenance history indicates the history of when user U was selected as a candidate for the person who will perform maintenance on moving body M. As described below, when user U1 is selected in the process of selecting candidates for the person who will perform maintenance on moving body M, information regarding the timing of the maintenance and the content of the maintenance is added to user information 23 of user U1.

The reservation information 24 is information regarding a reservation for use of the mobile body M, and is generated when a user U makes a reservation for use of the mobile body M. The reservation information 24 includes a reservation ID, a mobile body ID, a user ID, and use time information.
The reservation ID is identification information given to one piece of reservation information 24. The reservation information 24 is generated each time one user U makes a reservation. The usage time information is information indicating the time when the use of the mobile object M is reserved. The usage time information includes, for example, the date and time when the use of the mobile object M starts and the date and time when the use ends.

The history information 25 includes, for example, a reservation ID and a usage result. The usage result is information regarding the result of using the mobile object M based on the reservation information 24. Specifically, the usage result includes information regarding the state of the mobile object M after it has been used, and can be the same as the maintenance information.

The maintenance reference information 26 includes information related to the maintenance of the mobile unit M. Specifically, it includes information indicating locations where maintenance of the mobile unit M can be performed. These locations are, for example, gas stations, charging stations, repair shops, etc. The maintenance reference information 26 also includes information that serves as a criterion for determining when maintenance of the mobile unit M is necessary. For example, the maintenance reference information 26 includes information that associates the remaining amount of fuel or remaining capacity of the battery of the mobile unit M with the time and/or distance that the mobile unit M can travel.

2, the communication unit 30 is a communication device connected to the communication network 500. The communication unit 30 includes, for example, a connector to which an Ethernet (registered trademark) cable is connected, and a communication interface circuit that transmits and receives signals through the cable. The communication unit 30 may be a communication device that includes an antenna and an RF (Radio Frequency) circuit and performs wireless data communication.
The communication unit 30 performs data communication between the user terminal 210 and the mobile terminal 270 through the communication network 500 under the control of the processor 10 .

The processor 10 executes the control program 21 to realize the functions of the management device 100. The functional units configured by the processor 10 are an information acquisition unit 11, a reservation reception unit 12, and a maintenance management unit 13. Each of these functional units is realized by the processor 10 executing the control program 21 through the cooperation of software and hardware.

The information acquisition unit 11 acquires information from the user terminal 210 and the mobile terminal 270 .
The reservation acceptance unit 12 accepts reservation applications for use of the mobile body M and accepts reservation cancellation applications based on information acquired by the information acquisition unit 11 from the user terminal 210. The reservation acceptance unit 12 notifies the user terminal 210 of the date and time when use of the mobile body M is reserved, and notifies the user U of the reservation of the mobile body M. In addition, after the mobile body M is used based on the reservation, the reservation acceptance unit 12 acquires maintenance information for the mobile body M and updates the mobile body information 22. The reservation acceptance unit 12 corresponds to an example of a acceptance unit.

The maintenance management unit 13 identifies the timing for performing maintenance on the mobile body M based on the mobile body information 22. The maintenance management unit 13 selects a candidate user U who will perform maintenance on the mobile body M, and requests the selected user U to perform the maintenance.

The user terminal 210 has a processor 211 , a memory unit 212 , a communication unit 213 , a touch panel 214 , a camera 215 , and a GNSS 216 .
The processor 211 is an information processing device such as a CPU or a microcontroller. The storage unit 212 may be a non-volatile storage device configured using a semiconductor memory device such as a flash memory. The storage unit 212 may have a volatile storage area and may be configured to form a work area for the processor 211. The storage unit 212 stores programs executed by the processor 211 and data processed by the processor 211.
The processor 211 executes a program stored in the storage unit 212 and controls the user terminal 210 .

The communication unit 213 is a communication device that includes an antenna, an RF circuit, etc., and performs wireless data communication via a mobile communication line. The communication unit 213 connects to the communication network 500, and performs data communication with the management device 100 according to the control of the processor 211.

The touch panel 214 displays various images under the control of the processor 211. The touch panel 214 detects touch operations on the touch panel 214 and outputs operation data indicating the detected operations to the processor 211.

The camera 215 takes pictures under the control of the processor 211 and outputs the taken images to the processor 211 .
A Global Navigation Satellite System (GNSS) 216 detects the position of the user terminal 210 under the control of the processor 211 .

The user terminal 210 transmits a reservation request or a reservation cancellation request to the management device 100 in accordance with the user U's operation on the touch panel 214. The user terminal 210 also receives a notification transmitted by the management device 100 and executes a notification to the user U. The notification executed by the user terminal 210 is, for example, displaying a notification message on the touch panel 214. If the user terminal 210 has a speaker, the user terminal 210 may execute the notification by outputting voice or sound.

The mobile terminal 270 includes a control unit 271 and a communication unit 272. The control unit 271 has a processor that controls the mobile terminal 270. The communication unit 272 is a communication device that includes an antenna, an RF circuit, etc., and performs wireless data communication through a mobile communication line. The communication unit 272 connects to the communication network 500, and performs data communication with the management device 100 according to the control of the control unit 271. The mobile terminal 270 may be a device incorporated in a control device that controls the operation of the mobile body M, or may be a device that is detachably attached to the mobile body M. For example, the mobile terminal 270 may be a smartphone attached to the mobile body M.

3. Operation of the Management System
Fig. 4 is a flowchart showing the operation of the management system 1. Step SA11 in Fig. 4 shows the operation of the user terminal 210, and steps SB11 to SB19 show the operation of the management device 100. In detail, step SA11 is executed by the processor 211, and SB11 to SB19 are executed by the reservation receiving unit 12.

The user terminal 210 transmits a reservation request to the management device 100 (step SA11). The information transmitted by the user terminal 210 in step SA11 includes, for example, the user ID of the user U, the mobile object ID of the mobile object M, and the start and end dates and times of use of the mobile object M.

The management device 100 acquires the reservation request sent by the user terminal 210 (step SB11). The management device 100 references the user information 23 based on the user ID included in the reservation request and acquires the occupancy limit time (step SB12). The management device 100 acquires the reservation information 24 of the user U who made the reservation request (step SB13). That is, the management device 100 acquires the reservation information 24 corresponding to the user ID included in the reservation request from the storage unit 20.

When the management device 100 receives a reservation request, it determines whether the occupancy upper limit time will be exceeded (step SB14). For example, in step SB14, the management device 100 calculates the total usage time information included in the reservation information 24 acquired in step SB13. Furthermore, the management device 100 calculates the length of the requested reservation time based on the usage start date and time and usage end date and time of the reservation request acquired in step SB11. The management device 100 determines whether the sum of the usage time information included in the reservation information 24 and the length of the requested reservation time for a specified period of time exceeds the occupancy upper limit time.

If it is determined that the occupancy upper limit time will not be exceeded (step SB14; NO), the management device 100 decides to accept the reservation request (step SB15). The management device 100 generates reservation information 24 based on the contents of the reservation request acquired in step SB11, and stores it in the memory unit 20 (step SB16). The management device 100 transmits a notification that the reservation request has been accepted to the user terminal 210 (step SB17), and ends this process. Here, the user terminal 210 may execute a notification to the user U in response to receiving the notification that the reservation request has been accepted from the management device 100.

If it is determined that the occupancy upper limit time will be exceeded (step SB14; YES), the management device 100 decides to reject the reservation request (step SB18). The management device 100 transmits a notification to the user terminal 210 that the reservation request is not possible (step SB19), and ends this process. Here, in response to receiving the notification that the reservation request is not possible from the management device 100, the user terminal 210 may execute a notification to the user U.

FIG. 5 is a diagram showing an example of the reservation screen 301 displayed on the user terminal 210. As shown in FIG.
The user U can access the management device 100 by operating the user terminal 210, and can display a reservation screen 301 on the touch panel 214. The reservation screen 301 displays, for example, the reservation status of the mobile object M for several days including the time of access by the user terminal 210, in association with the date and time period. The reservation screen 301 may display an icon or character string indicating the user U who has made a reservation for the mobile object M.

Reservations for the use of the mobile unit M may be made by the user U by executing the operation of FIG. 4, or may be set in advance in the management device 100. Specifically, reservations may be set for specific periods in association with each of the users U1, U2, and U3. For example, these reservations are reservations that specify a specific day of the year, a specific date of the month, or a specific day of the week of the week. These reservations are automatically set for the specified date or day of the week in all years, months, or weeks without the user U's operation. For this reservation, a time period may be specified in addition to the date or day of the week. For example, if a reservation is set for the user U1 to use the mobile unit M from 9:00 a.m. to 12:00 p.m. on Monday, the reservation for the user U1 is set from 9:00 a.m. to 12:00 p.m. every Monday, even if the user U1 does not operate the user terminal 210A to make the reservation. In this way, the management system 1 allows reservations that do not require operation by the user terminal 210, and the time period in which this reservation is set corresponds to an example of an occupied time period. Furthermore, the reservation information 24 related to this type of reservation corresponds to an example of occupied time information.

The function of the user terminal 210 to display the reservation screen 301, to make a reservation request, and to make a reservation cancellation request (described later) can be implemented in the user terminal 210, for example, as an application program (hereinafter referred to as an app) for a smartphone or tablet computer. In this case, the management device 100 can be configured as a web server that transmits and receives data to and from the app implemented in the user terminal 210. With the reservation screen 301 displayed on the user terminal 210, the user U can make a new reservation request or cancel a reservation.

Figure 6 is a flowchart showing the operation of the management system 1. Steps SA21 to SA23 in Figure 6 show the operation of the user terminal 210 and are executed by the processor 211. Steps SB21 to SB26 show the operation of the management device 100 and are executed by the reservation reception unit 12. Step SC21 shows the operation of the mobile terminal 270 and is executed by the control unit 271.

The management device 100 judges whether the current time is a predetermined time before the reservation date and time based on the usage time information included in the reservation information 24 stored in the storage unit 20 (step SB21). If the time has not reached the time before the reservation date and time (step SB21; NO), the management device 100 waits in step SB21. If it is judged that the time has reached the time before the reservation date and time (step SB21; YES), the management device 100 transmits a notification of the reservation date and time to the user terminal 210 (step SB22). In step SB22, the management device 100 can specify the user terminal 210 to which the notification is to be sent based on the user ID included in the reservation information 24 referenced in step SB21. For example, when the time reaches a predetermined time before the reservation date and time, i.e., the use start date and time, for a reservation for user U1 to use the mobile unit M, the management device 100 transmits a notification to the user terminal 210A used by user U1.

In response to receiving the reservation date and time notification from the management device 100, the user terminal 210 notifies the user U (step SA21). Thereafter, when the user U starts using the mobile object M, the user U operates the user terminal 210 to input that he or she has started using the mobile object M. In response to the input from the user U, the user terminal 210 notifies the management device 100 that he or she has started using the mobile object M (step SA22).

When the management device 100 receives a notification of the start of use from the user terminal 210, it accepts the start of use of the moving object M (step SB23).
When the user U finishes using the mobile object M, the user U operates the user terminal 210 to input information indicating that he or she has finished using the mobile object M. In response to the input by the user U, the user terminal 210 notifies the management device 100 of the end of use of the mobile object M (step SA23).
When the management device 100 receives the notification of the end of use from the user terminal 210, it accepts the end of use of the moving object M (step SB24).

The management device 100 requests the mobile terminal 270 to transmit information (step SB25). The information requested in step SB25 corresponds to the maintenance information described above. Specifically, the information includes the travel distance of the mobile unit M, the remaining amount of fuel in the mobile unit M, the remaining capacity of the battery of the mobile unit M, etc.

In response to receiving the request from the management device 100, the mobile terminal 270 transmits information about the moving object M to the management device 100 (step SC21).
The management device 100 generates usage results of the mobile object M based on the information transmitted by the mobile terminal 270, and generates the history information 25 (step SB26).

The operation of FIG. 6 causes the actual use of the mobile unit M reserved by the user U, and generates a history of the use of the mobile unit M.
In addition, in step SB25, the management device 100 may request the user terminal 210 to transmit the maintenance information. In this case, the user U who has used the moving object M may input information about the moving object M to the user terminal 210 and cause the user terminal 210 to transmit the information to the management device 100.

Figures 7 and 8 are flowcharts showing the operation of the management system 1. Step SA31 in Figure 7 shows the operation of the user terminal 210, and is executed by the processor 211. Steps SB31 to SB35 and steps SB41 to SB48 show the operation of the management device 100, and are executed by the reservation reception unit 12.

The user terminal 210 transmits a reservation cancellation request to the management device 100 based on an operation of the user U on the touch panel 214 (step SA31).
The management device 100 identifies the reservation information 24 corresponding to the reservation cancellation request received from the user terminal 210 from among the reservation information 24 stored in the storage unit 20 (step SB31). The management device 100 executes a process to cancel the reservation related to the identified reservation information 24 (step SB32). The reservation cancellation process of step SB32 includes, for example, a process to invalidate the reservation information 24 or a process to erase the reservation information 24.
The management device 100 notifies the user terminal 210 that the reservation has been cancelled (step SB33). In response to receiving the notice from the management device 100, the user terminal 210 may notify the user U.

Here, the management device 100 determines whether the canceled reservation is a reservation for an exclusive time period (step SB34). If the canceled reservation is not a reservation for an exclusive time period (step SB34; NO), the management device 100 ends this process.

If the canceled reservation is for an exclusive time slot (step SB34; YES), the management device 100 executes a re-reservation acceptance process (step SB35). The re-reservation acceptance process is a process of accepting a reservation from another user U for the time slot in which the reservation set for the exclusive time slot was canceled. As described above, the management system 1 can set exclusive time slots corresponding to some or all users U for the use of the mobile object M. Since the exclusive time slot is automatically reserved on a specified day of the week or date, for example, it is possible that a user U who plans to use the mobile object M during the exclusive time slot does not use the mobile object M. In such a case, in order to effectively use the mobile object M, the management system 1 cancels the reservation for the exclusive time slot and allows the other user U to use the mobile object M.

In FIG. 8, the management device 100 starts accepting reservation requests for the time period in which the reservation was canceled (step SB41). After step SB41, the management device 100 waits to receive a reservation request from the user terminal 210.

The management device 100 waits until it receives a reservation request from at least one user terminal 210 (step SB42). If a reservation request is received (step SB42; YES), the management device 100 determines whether reservation requests have been made by multiple users U (step SB43).

When a reservation request is made by one user U (step SB43; NO), the management device 100 generates reservation information 24 based on the reservation request (step SB44) and notifies the user terminal 210 that a reservation has been made (step SB45).

When multiple users U make reservation requests (step SB43; YES), the management device 100 judges the priority of the users U who made the reservation requests (step SB46). The management device 100 judges the priority of the users U based on the proportion of the purchase amount contributed by the users U. Specifically, the priority of the user U with the largest proportion of the investment amount indicated by the investment information in the user information 23 or the user U with the longest occupancy limit time is set higher than that of the other users U. When there are three or more target users U, the priority is judged in descending order of the largest proportion of the investment amount indicated by the investment information or the longest occupancy limit time. In this case, the higher the proportion of the investment amount, the higher the priority of the user U.

The management device 100 accepts the reservation request from the user U whose priority was determined in step SB47 (step SB47). The management device 100 notifies the user terminal 210 used by the user U whose reservation request was not accepted that the reservation request was not accepted (step SB48), and proceeds to step SB44.

In step SB44 of FIG. 8, the management device 100 does not determine whether the upper occupancy time limit of the user U accepting the reservation is exceeded. In other words, when a reservation for an occupied time period is cancelled and a reservation for a mobile unit M for the cancelled occupied time period is accepted, the management device 100 does not impose a restriction based on the upper occupancy time limit. This makes it easier for other users U to use the mobile unit M when a reservation for an occupied time period corresponding to user U is cancelled, allowing the mobile unit M to be used effectively.

Figure 9 is a flowchart showing the operation of the management system 1, and shows the operation of the management device 100. Steps SB51 to SB60 are executed by the maintenance management unit 13.

The management device 100 acquires maintenance information from the mobile object information 22 (step SB51). The management device 100 acquires reservation information 24 (step SB52) and determines the timing of maintenance execution based on the maintenance information and the reservation information 24 (step SB53). In step SB53, the management device 100 calculates, for example, the time and/or travel distance that the mobile object M can be used before maintenance is executed based on the maintenance information. Here, in the process of calculating the time and/or distance, the management device 100 may refer to the maintenance reference information 26. The management device 100 identifies a reservation that cannot be executed without maintenance based on the calculated time and/or travel distance and the reservation information 24. The management device 100 determines the timing of maintenance execution to be before the identified reservation.

As an example, assume that the storage unit 20 stores reservation information 24 for a first reservation using a mobile object M, and reservation information 24 for a second reservation to be made following the first reservation. In this example, assume that the first reservation can be made without maintenance, but that maintenance becomes necessary while the second reservation is in use. In this case, since the second reservation cannot be completed without maintenance, for example, while the mobile object M is in use, it may become impossible for the mobile object M to travel. In this example, the management device 100 determines the timing for performing maintenance to be before the second reservation is made. More specifically, the timing for performing maintenance is determined to be between the start of the first reservation and the start of the second reservation.

The management device 100 waits until the timing to perform maintenance arrives (step SB54). When the timing to perform maintenance arrives (step SB54; YES), the management device 100 acquires location information of the user U who is using the mobile object M (step SB55). In step SB55, the management device 100, for example, requests each user terminal 210 to transmit location information, and acquires the location information transmitted by the user terminal 210 in response to this request.

The management device 100 refers to the maintenance reference information 26, identifies a location where maintenance of the mobile unit M can be performed, and selects a user U close to the identified location (step SB56). Here, the management device 100 refers to the user information 23 of the user U selected in step SB56 (step SB57) and determines whether the user U is a candidate for the previous maintenance (step SB58). In other words, the management device 100 determines whether the user U selected in step SB56 is the user U selected for the maintenance performed previously.

If the selected user U is a candidate for the previous maintenance (step S58; YES), the management device 100 removes the user U selected in step SB56 from the candidates (step SB59) and returns to step SB56. If the selected user U is not a candidate for the previous maintenance (step S58; NO), the management device 100 transmits information requesting the performance of maintenance to the user terminal 210 used by the user U selected in step SB56 (step SB60). Having received this information, the user terminal 210 may notify the user U of the request to perform maintenance.

4. Other embodiments
The above embodiment shows a specific example to which the present invention is applied, and does not limit the form to which the invention is applied.

In the above embodiment, an example has been described in which, when a reservation during an occupied time period is cancelled, the operation of FIG. 8 is performed to accept a new reservation, but this is just one example. For example, the management device 100 may be configured to perform the operation of FIG. 7 for a reservation other than the occupied time period and accept a reservation cancellation request. In this case, after accepting the reservation cancellation request, the management device 100 may execute the re-reservation acceptance process of step SB35, and enable the use of the mobile unit M during the time period when the reservation was cancelled. Furthermore, the management device 100 may be configured not to impose a restriction based on the occupancy upper limit time when a reservation other than the occupied time period is cancelled and a new reservation is accepted during the time period when the reservation was cancelled.

Furthermore, the management device 100 is not limited to a single server computer, but may be configured to perform distributed processing using multiple server computers, or may be configured as a cloud server.

Figure 2 is a schematic diagram showing the functional configuration of each device in the management system 1, divided according to the main processing content, in order to facilitate understanding of the present invention, and is not intended to limit the configuration of the devices. For example, in the management device 100, the processing of the components provided in the processor 10 may be executed by one hardware unit or by multiple hardware units. The same applies to the user terminal 210. In addition, each process shown in Figures 4 and 6 to 9 may be executed by one program or by multiple programs.

The control program 21 can also be realized in a state in which the control program 21 is recorded on a portable information recording medium. Examples of information recording media include magnetic recording media such as hard disks, optical recording media such as CDs, and semiconductor storage devices such as USB (Universal Serial Bus) memories and SSDs (Solid State Drives), but other recording media can also be used. The processor 10 can read and execute the control program 21 from the information recording medium.

5. Configurations supported by the above embodiment
The above embodiment supports the following configurations.

(Configuration 1) A mobile object usage management system having a management device for managing information on mobile objects used by a plurality of users, the management device comprising: a memory unit for storing reservation information specifying the time the users will use the mobile object, and an occupancy upper limit time that sets an upper limit for the time each of the users can use the mobile object; and a reception unit for receiving applications for use of the mobile object from the users and generating or updating the reservation information so that the accumulated value of the time the users use the mobile object over a predetermined period of time does not exceed the occupancy upper limit time, the occupancy upper limit time being a time corresponding to the amount of investment each of the users has made to purchase the mobile object.
According to the management system of configuration 1, the time during which a plurality of users can occupy a moving object jointly purchased can be limited according to the amount of money the users invested in purchasing the moving object. This makes it possible to reflect the difference in the amount of investment in the reservations of moving objects made by users, thereby realizing utilization that takes into consideration fairness among users.

(Configuration 2) The reservation information includes occupancy time information specifying an occupied time period during which a first user included in the plurality of users occupies the mobile object, and when the reception unit receives an application from the first user not to use the mobile object during the occupied time period, the reception unit accepts an application from a second user included in the plurality of users to use the mobile object during a time period overlapping with the occupied time period.
According to the management system of configuration 2, a user can use a mobile object periodically by making it possible to reserve an exclusive time period for any one of a plurality of users who jointly purchased the mobile object. Furthermore, when a reservation for the use of the mobile object is cancelled, a new reservation for the time period for which the reservation was cancelled can be accepted, thereby enabling the mobile object to be used effectively.

(Configuration 3) A mobile object usage management system as described in Configuration 2, wherein when the reception unit receives an application from the second user to use the mobile object during a time period that overlaps with the occupancy time period, the reception unit allows the second user to use the mobile object beyond the second user's upper occupancy time limit.
According to the management system of configuration 3, when a reservation for the use of a mobile object is cancelled and a new reservation is accepted, the restriction by the upper limit of occupancy time is relaxed. This increases the degree of freedom for accepting a new reservation when a reservation is cancelled, and allows the mobile object to be used more effectively.

(Configuration 4) A mobile object usage management system as described in configuration 2 or configuration 3, in which the reception unit sets a priority among the users corresponding to the amount of investment each of the users has made to purchase the mobile object, and when the reception unit receives an application for use of the mobile object during a time period overlapping with the occupancy time period from the second user and a third user included in the plurality of users, the reception unit accepts the application for use of the mobile object in accordance with the priority.
According to the management system of configuration 4, even when a reservation for use of a mobile object is canceled and a new reservation is accepted for the time period for which the reservation was canceled, the user's investment amount is reflected, thereby realizing usage that takes into consideration fairness among users.

(Configuration 5) A mobile object usage management system described in any of configurations 1 to 4, wherein the memory unit stores usage history information regarding the history of use of the mobile object in association with the user who used the mobile object, and the management device is equipped with a maintenance management unit that identifies a timing to perform maintenance of the mobile object based on the usage history information and the reservation information, and selects candidate users to perform the maintenance from among multiple users based on the identified timing.
According to the management system of configuration 5, it becomes possible to perform maintenance on the moving object at an appropriate time, so that the moving object can be used efficiently.

(Configuration 6) A mobile usage management system as described in Configuration 5, in which when the maintenance management unit selects a fourth user included in the plurality of users as a candidate user, the next time a candidate user is selected, the maintenance management unit selects a user other than the fourth user.
According to the management system of configuration 6, it is possible to prevent the burden of maintenance from being concentrated on a specific user, thereby realizing fairness among users in terms of maintenance as well.

(Configuration 7) A mobile object usage management method for managing information on mobile objects used by multiple users, the method comprising: storing in a management device reservation information specifying the time the users will use the mobile object, and an occupancy limit time that sets an upper limit for the time each user can use the mobile object; receiving an application for use of the mobile object from the user and generating or updating the reservation information so that the cumulative value of the time the users use the mobile object over a specified period of time does not exceed the occupancy limit time; and the occupancy limit time is a time corresponding to the amount of investment each user has made to purchase the mobile object.
According to the management method of configuration 7, the time during which a plurality of users can occupy a moving object jointly purchased can be limited according to the amount of money the users invested in purchasing the moving object. This makes it possible to reflect the difference in the amount of investment in the reservations of moving objects made by users, thereby realizing utilization that takes into consideration fairness among users.

1...Management system (mobile object usage management system), 10...Processor, 11...Information acquisition unit, 12...Reservation reception unit (reception unit), 13...Maintenance management unit, 20...Memory unit, 21...Control program, 22...Mobile object information, 23...User information, 24...Reservation information, 25...History information, 26...Maintenance reference information, 30...Communication unit, 100...Management device, 210, 210A, 210B, 210C...User terminal, 211...Processor, 212...Memory unit, 213...Communication unit, 214...Touch panel, 215...Camera, 216...GNSS, 270...Mobile object terminal, 271...Control unit, 272...Communication unit, 301...Reservation screen, 500...Communication network, M...Mobile object, U, U1, U2, U3...User.

Claims (6)

A management device that manages information on a moving object used by a plurality of users including a first user and a second user ,
The management device includes:
a storage unit that stores reservation information that specifies a time during which the user uses the moving object, and an occupancy upper limit time that determines an upper limit of a time during which each user can use the moving object;
a reception unit that receives an application for use of the mobile object from the user and generates or updates the reservation information so that a cumulative value of a time during which the user uses the mobile object in a predetermined period does not exceed the occupancy upper limit time,
the occupancy upper limit time is a time corresponding to an investment amount contributed by each of the users for the purchase of the mobile object,
The management device includes:
when the reservation information includes occupancy time information specifying an occupancy time period during which the first user occupies the mobile object, and a request not to use the mobile object during the occupancy time period is received from the first user, waiting for a request to use the mobile object from a user other than the first user;
When the second user applies to use the mobile object during a time period that overlaps with the occupancy time period, the mobile object usage management system accepts the application from the second user and generates the reservation information without imposing any restriction based on the second user's upper occupancy time limit. 2. The mobile object usage management system of claim 1, wherein the reservation information includes occupancy time information specifying an occupancy time period during which the first user occupies the mobile object, and when the management device receives a request from the first user not to use the mobile object during the occupancy time period, the management device erases the reservation information corresponding to the request not to use the mobile object and waits for a request to use the mobile object from a user other than the first user . In the reception unit, a priority among the users is set corresponding to an investment amount contributed by each of the users for the purchase of the moving object,
3. The mobile object usage management system according to claim 1, wherein the reception unit accepts applications for use of the mobile object in a time period that overlaps with the occupancy time period from the second user and a third user included in the plurality of users in accordance with the priority. the storage unit stores usage history information relating to a history of use of the mobile object in association with the user who used the mobile object;
The management device includes:
A mobile object usage management system as described in any one of claims 1 to 3, comprising a maintenance management unit that identifies a timing to perform maintenance of the mobile object based on the usage history information and the reservation information, and selects candidate users to perform the maintenance from among the multiple users based on the identified timing. The mobile use management system according to claim 4, wherein when the maintenance management unit selects a fourth user among the plurality of users as the candidate user, the maintenance management unit selects a user other than the fourth user when selecting a candidate user next. A mobile object usage management method for managing information on a mobile object used by a plurality of users including a first user and a second user, comprising :
storing reservation information designating a time for the user to use the mobile object and an occupancy upper limit time defining an upper limit of a time for each user to use the mobile object in a management device;
accepting an application for use of the mobile object from the user and generating or updating the reservation information so that a cumulative value of time during which the user uses the mobile object in a predetermined period does not exceed the occupancy upper limit time;
the occupancy upper limit time is a time corresponding to an investment amount contributed by each of the users for the purchase of the mobile object,
when the reservation information includes occupancy time information specifying an occupancy time period during which the first user occupies the mobile object, and when a request not to use the mobile object during the occupancy time period is received from the first user, waiting for a request to use the mobile object from a user other than the first user;
A mobile object usage management method, in which, when a second user applies to use the mobile object during a time period that overlaps with the occupancy time period, the second user's application is accepted and the reservation information is generated without imposing any restriction based on the second user's upper occupancy time limit.

Images