Information processing methods, programs, and systems

The information processing method addresses the challenge of managing shared vehicle usage by accurately tracking key exchange times and generating analytical reports, enhancing management efficiency and driving quality.

JP7953849B2Active Publication Date: 2026-11-19SMARTDRIVE INC
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
JP2022127053
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2022-08-09
Publication Date
2026-11-19
Estimated Expiration
2042-08-09

AI Technical Summary

Technical Problem

Existing technologies fail to efficiently manage the usage time of shared vehicles by specifying the mobile object usage time of a driver, leading to inaccuracies in vehicle management.

Method used

An information processing method that includes acquiring travel information in a time series, identifying key receipt and return times, and generating analytical information based on this data to efficiently manage vehicle usage.

Benefits of technology

Enables efficient management of shared vehicles by accurately dividing usage time and generating analytical reports on driver performance, improving management efficiency and driving quality.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007953849000001
    Figure 0007953849000001
  • Figure 0007953849000002
    Figure 0007953849000002
  • Figure 0007953849000003
    Figure 0007953849000003
Patent Text Reader

Abstract

To provide information processing technology for efficiently managing a mobile object in the case of using a share vehicle.SOLUTION: An information processing method comprises the steps of: acquiring pieces of travel information regarding a mobile object in a time series manner; specifying receiving time of a key of the mobile object; specifying return time of the key; specifying the travel information in a use period to be specified by the receiving time and the return time among the pieces of travel information acquired in the time series manner; and generating analysis information regarding an operation of the mobile object on the basis of the specified travel information.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present invention relates to an information processing technique for improving the efficiency of mobile object management.

BACKGROUND ART

[0002] There is a social demand to improve the efficiency of management of mobile objects and drivers of the mobile objects, such as in fleet management for managing a plurality of mobile objects, and further to improve driving quality by drivers through the management. For example, Patent Document 1 discloses an operation management device for managing the operation status of vehicles. Furthermore, for example, Patent Document 2 discloses a method and system for sharing vehicles between fleets, which discloses that a vehicle sharing entity is permitted to use a part of the vehicles on weekends when the vehicles of a vehicle rental company are idle, and the like. Furthermore, for example, in Patent Document 3, in a sharing service for sharing vehicles, it is disclosed that the start and end of the usage time are specified by reading user identification information from the user's IC card in order to simplify the settlement of usage fees.

PRIOR ART DOCUMENTS

PATENT DOCUMENTS

[0003]

PATENT DOCUMENT 1

PATENT DOCUMENT 2

PATENT DOCUMENT 3

SUMMARY OF THE INVENTION

PROBLEMS TO BE SOLVED BY THE INVENTION

[0004] However, for example, in the case of performing vehicle management including vehicles that are targets of sharing services, none of these conventional techniques discloses or suggests appropriately and easily specifying the mobile object usage time of a driver to be managed.

[0005] The present invention aims to efficiently manage mobile vehicles when using shared vehicles. [Means for solving the problem]

[0006] According to one aspect of the present invention, the information processing method includes acquiring travel information relating to a mobile body in a time series, identifying the time of receipt of the key for the mobile body, identifying the time of return of the key, identifying travel information from the time series acquired travel information during the usage period specified by the receipt time and the return time, and generating analytical information relating to the operation of the mobile body based on the identified travel information. [Effects of the Invention]

[0007] According to the information processing method of the present invention, when using a shared vehicle, the management of the vehicle can be carried out efficiently. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows an example of the system configuration of a vehicle management system. [Figure 2] This figure shows an example of the functional configuration of server 10. [Figure 3] This is a block diagram illustrating a schematic configuration example of the driving information acquisition device 20. [Figure 4] This is a schematic diagram illustrating the data communication method between the driving information acquisition device 20 and the server 10. [Figure 5] This figure shows an example of the functional configuration of the information processing device 30. [Figure 6] This figure shows an example of the functional configuration of the information processing terminal 40. [Figure 7] This is a conceptual diagram illustrating how the driver D1 in the first embodiment divides the usage time of the mobile body 1. [Figure 8]This is a flowchart of mobile object usage time allocation processing performed by the server 10 in the first embodiment. [Figure 9] This is an output example of processing that shows the positions of a plurality of mobile objects including the mobile object 1 on a map, which is an example of analysis output processing in the first embodiment. [Figure 10] This is a flowchart of mobile object position plotting processing on a map, which is an example of analysis output processing in the first embodiment. [Figure 11] This is an example of report information created in step S1013 in the first embodiment. [Figure 12] This is a diagram showing an example of the system configuration of a vehicle management system in modification 1. [Mode for Carrying Out the Invention]

[0009] Hereinafter, an example of the mode for carrying out the present invention will be described with reference to the drawings. In the description of the drawings, the same reference numerals are assigned to the same elements, and duplicate descriptions may be omitted. In addition, the components described in these embodiments are merely examples, and are not intended to limit the scope of the present invention thereto.

[0010] [Embodiment] Hereinafter, an embodiment for realizing the information processing technology of the present invention will be described. The content described in the present embodiment is applicable to any of the other respective examples and respective modifications.

[0011] In the following, for example, an example will be described in which a business operator that operates vehicles manages mobile objects that are shared vehicles. Note that the shared vehicles are operated not only by drivers associated with the business operator but also by other drivers not associated with the business operator.

[0012] Figure 1 is a diagram showing an example of the system configuration of the vehicle management system in the present embodiment. The system is configured to include a server 10, a travel information acquisition device 20, an information processing device 30, an information processing terminal 40, and the like, and is a mechanism in which these devices cooperate to execute processing. In the vehicle management system according to the present embodiment, for example, the server 10, the travel information acquisition device 20 provided in the mobile object 1, the information processing device 30 held by the driver D1 associated with (e.g., being an employee of) the operator A1, and the information processing terminal 40 capable of viewing report information that is a result of analyzing travel information by the server 10 are communicably connected via a network NW (e.g., the Internet).

[0013] Note that, as shown in FIG. 1, the mobile object 1 is shared with other users, and is driven not only by the driver D1 but also by the driver D2. The driver D2 may or may not be associated with the operator A1 in the same manner as the driver D1. That is, in the present embodiment, although the main purpose is to collect travel information related to the driving of the mobile object 1 by the driver D1, travel information related to the driving of the mobile object 1 by the driver D2 may also be collected in a manner separated from the travel information of the driver D1, and when the driver D2 is also associated with the operator A1, the collected travel information by the driver D2 may be analyzed, while when the driver D2 is not associated with the operator A1 (e.g., when the driver D2 is associated with an enterprise different from the operator A1), the travel information does not need to be analyzed. Further, in the vehicle management system according to the present embodiment, a plurality of servers 10 may be connected.

[0014] In the present embodiment, the mobile object 1 is at least part of the target of travel information analysis, and is, for example, an automobile used for business purposes, but is not particularly limited to an automobile, and any mobile object (including motorcycles, trucks, bicycles, and the like) is applicable. The mobile object 1 is provided with a travel information acquisition device 20 to be described later.

[0015] Server 10 has, for example, a function to separate driving information for each driver. Server 10 also has a function to generate report information based on the driving information accumulated for each driver and output it via the network.

[0016] Figure 2 shows an example of the functional configuration of server 10. Server 10 can be configured, for example, as a single server, or as a distributed server composed of separate servers for each function. Server 10 can also be configured as a distributed virtual server created in a cloud environment, known as a cloud server. As shown in Figure 2, server 10 is configured to include, for example, a communication unit 110, a storage unit 120, a processing unit 130, a clock unit 140, and so on.

[0017] The communication unit 110 is a communication device for sending and receiving information used within the server 10 to and from external devices via a network. Various communication methods can be applied to the communication unit 110, including wired connection via a cable compliant with a predetermined communication standard such as Ethernet or USB (Universal Serial Bus), wireless connection using wireless communication technology compliant with a predetermined communication standard such as Wi-Fi (registered trademark) or 5G (fifth-generation mobile communication system), and connection using short-range wireless communication such as Bluetooth (registered trademark).

[0018] The storage unit 120 is a storage device comprising volatile or non-volatile memory such as ROM, EEPROM, flash memory, RAM, or a hard disk drive. The storage unit 120 stores, for example, various programs such as programs corresponding to each process performed in this embodiment and system programs, as well as driving information received from the driving information acquisition device 20 and the processing results of various programs.

[0019] The processing unit 130 is a processing unit that comprehensively controls each part of the server 10 according to various programs such as system programs stored in the memory unit 120 and performs various processing related to information processing. It is composed of processors such as CPUs, GPUs, and DSPs, and integrated circuits such as ASICs.

[0020] The clock unit 140 is the built-in clock of the server 10 and outputs time information (timing information) acquired based on a clock using, for example, a crystal oscillator. The clock unit 140 may also acquire time information via the communication unit 110 and the network NW in accordance with standards such as NITZ (Network Identity and Time Zone).

[0021] The driving information acquisition device 20 has the function of acquiring driving information for a mobile body 1 equipped with the driving information acquisition device 20. The driving information acquisition device 20 also has the function of transmitting the collected driving information to the server 10 via a network NW. For example, the driving information acquisition device 20 can be inserted into a socket on the mobile body 1 (for example, a cigarette lighter socket, an electrical supply socket, or a connection socket) and fixed inside the vehicle. The electrical supply socket or connection socket is, for example, a socket that supports USB (Universal Serial Bus). Of course, the driving information acquisition device 20 is not limited to such devices, and may be a dashcam or any other IoT device, and as long as they provide the components of the driving information acquisition device 20, either individually or in combination, they may be installed in the vehicle in any manner.

[0022] Figure 3 is a block diagram illustrating a schematic configuration example of the driving information acquisition device 20. As shown in Figure 2, the driving information acquisition device 20 is configured to include, for example, a control unit 210, a storage unit 220, a communication unit 230, a position information acquisition unit 240, a speed information acquisition unit 250, and an acceleration information acquisition unit 260.

[0023] The control unit 210 implements each function of the driving information acquisition device 20 by executing a predetermined program (for example, a program stored in the memory unit 220). For example, it performs control to associate time information corresponding to the acquisition time with the position information acquired by the position information acquisition unit 240, the speed information acquired by the speed information acquisition unit 250, and the acceleration information acquired by the acceleration information acquisition unit 260, and transmits this information to an external device, such as a server 10, via the communication unit 230.

[0024] The storage unit 220 includes, for example, an HDD (Hard Disk Drive), SSD (Solid State Drive), EEPROM (Electrically Erasable Programmable Read-Only Memory), ROM (Read-Only Memory), RAM (Random Access Memory), etc., and stores control programs processed by the control unit 210, as well as various data, such as position information acquired by the position information acquisition unit 240, speed information acquired by the speed information acquisition unit 250, and acceleration information acquired by the acceleration information acquisition unit 260. Note that the storage unit 220 is not limited to one built into the driving information acquisition device 20, but may also be an external storage device connected via a digital input / output port such as USB (Universal Serial Bus).

[0025] The communication unit 230 is a module that connects to a public network NW such as the Internet using, for example, mobile communication such as LTE (Long Term Evolution), 3G, 4G, 5G, or narrowband communication such as DSRC (Dedicated Short Range Communication), and is capable of data communication with various devices such as the server 10 connected to the same network NW. For example, the driving information acquisition device 20 transmits data to the server 10 via the communication unit 230.

[0026] The position information acquisition unit 240 acquires position information (e.g., latitude and longitude information) of the driving information acquisition device 20 in a time series based on radio waves arriving from, for example, GNSS satellites (e.g., GPS satellites). Preferably, this position information is acquired at predetermined time intervals (e.g., every second). That is, the position information of the mobile body 1 equipped with the driving information acquisition device 20 can be acquired. The acquired position information is linked to the time (current time) at which the position information was acquired and stored in the storage unit 220. Here, the location information acquisition unit 240 may acquire location information via GPS and also acquire accuracy values ​​indicating the accuracy of that location information (for example, location accuracy of 5m, 10m, 100m, DOP value, etc.). In this case, the acquired location information and accuracy values ​​are linked to the current time and stored in the storage unit 220.

[0027] The method of acquiring location information by the location information acquisition unit 240 is not limited to the above, and any location information acquisition method may be applied. For example, the location information acquisition unit 240 may acquire the location information of the driving information acquisition device 20 by receiving radio waves containing location information specific to the roadside unit, which are emitted by a roadside unit installed on the side of the road, when the mobile body 1 equipped with the driving information acquisition device 20 approaches.

[0028] The speed information acquisition unit 250 periodically acquires the travel speed of the mobile body 1 and supplies the travel speed to the control unit 210. The speed acquisition unit 250 may have any configuration, but for example, it may calculate speed information based on position information acquired by the position information acquisition unit 240. In this case, the speed information acquisition unit 250 may not be provided. Alternatively, it may acquire vehicle speed pulse information acquired by a vehicle speed pulse acquisition unit (not shown) mounted on the mobile body 1 and calculate the speed of the mobile body 1 based on that vehicle speed pulse information.

[0029] The acceleration information acquisition unit 260 acquires the acceleration of the vehicle, and is configured to acquire acceleration using, for example, a piezoelectric acceleration sensor. Alternatively, the acceleration of the vehicle may be calculated based on the velocity information acquired from the position information acquired by the position information acquisition unit 240, in which case the acceleration information acquisition unit 260 may not be necessary.

[0030] Figure 4 is a schematic diagram showing the mode of data communication between the driving information acquisition device 20 and the server 10. As shown in Figure 4, the driving information acquisition device 20 is connected to the server 10 either via a mobile terminal T or directly. Furthermore, the driving information acquisition device 20 is not limited to being installed on the mobile body 1, but may also be a device held by the passenger of the mobile body 1, such as a smartphone. In this case, for example, the functions of the driving information acquisition device 20 may be included in the information processing device 30 described later.

[0031] The information processing device 30 has, for example, a virtual key function that enables the use of the mobile device 1. In this case, the virtual key function is realized, for example, through an application provided in a service that shares the mobile device 1. The information processing device 30 also has a function to record the time of transfer of the virtual key related to the mobile device 1 and send it to the server 10, and a function to display the results of analysis of the mobile device 1's driving information.

[0032] Figure 5 shows an example of the functional configuration of the information processing device 30. As shown in Figure 5, the information processing device 30 is configured to include, for example, a processing unit 310, a storage unit 320, a first communication unit 330, a display unit 340, an audio output unit 350, an operation unit 360, a second communication unit 370, a clock unit 380, and the like.

[0033] The processing unit 310 is a processing unit that comprehensively controls each part of the information processing device 30 according to various programs such as system programs stored in the memory unit 320, and performs various processing related to information processing. It is composed of a processor such as a CPU, GPU, or DSP, and an integrated circuit such as an ASIC.

[0034] The storage unit 320, like the storage unit 220, is a storage device configured with volatile or non-volatile memory such as ROM, EEPROM, flash memory, RAM, or a hard disk drive. The storage unit 320 stores, for example, various programs such as programs corresponding to each process performed in this embodiment and system programs, as well as information received from the server 10 and the results of processing by various programs.

[0035] The first communication unit 330 is a communication device for sending and receiving information used within the information processing device 30 to and from external devices via a network NW. Since the configuration of the communication unit 330 can be similar to that of the communication unit 210, a detailed explanation is omitted.

[0036] The display unit 340 is a display device configured with an LCD (Liquid Crystal Display) or an OLED (Organic Electro-luminescence Display), and performs various displays based on the display signals output from the processing unit 310. For example, the display unit 340 displays information related to the virtual key function corresponding to the mobile body 1 (such as whether the virtual key is available or unavailable), and various information generated based on the movement information of the mobile body 1.

[0037] The sound output unit 350 is a sound output device that includes a D / A converter, a speaker, etc., and performs various sound outputs based on the sound output signal output from the processing unit 310. For example, when dangerous driving is detected based on driving information acquired by the driving information acquisition device 20, the sound output unit 350 will notify the driver of any information in voice or by beep when necessary.

[0038] The operation unit 360 is configured to have input devices such as a keyboard and mouse for the user to perform various operations on the information processing device 30. Operation signals corresponding to user operations are output from the operation unit 360 to the processing unit 310. For example, the operation unit 360 receives information input by the user in accordance with the information displayed on the display unit 340.

[0039] The operation unit 360 may have a touch panel (not shown) that is integrated with the display unit 340, and this touch panel may function as an input interface between the user (administrator) and the information processing device 30.

[0040] The second communication unit 370 is a communication device that transmits and receives data with, for example, a key function mounted on the mobile device 1, and can cooperate with an installed application to enable the information processing device 30 to function as a virtual key. Various communication methods can be applied to the second communication unit 370, including wireless connection using wireless communication technology compliant with a predetermined communication standard such as Wi-Fi (registered trademark) or 5G (fifth-generation mobile communication system), and connection using short-range wireless communication such as Bluetooth (registered trademark).

[0041] The clock unit 380 can be configured, for example, in the same way as the clock unit 240 of the server 10.

[0042] Figure 6 shows an example of the functional configuration of the information processing terminal 40. As shown in Figure 6, the information processing terminal 40 is configured to include, for example, a processing unit 410, a storage unit 420, a communication unit 430, a display unit 440, an audio output unit 450, an operation unit 360, and so on. Since each of these functional units can be configured in the same way as the processing unit 310, storage unit 320, first communication unit 330, display unit 340, audio output unit 350, and operation unit 360 of the information processing device 30, a detailed explanation of them will be omitted.

[0043] A network (NW) is a communication network that connects various devices using wired connections, wireless connections, or both.

[0044] [First Embodiment] In the first embodiment, when driver D1 boards and alights from the mobile device 1, a virtual key is exchanged in the information processing device 30, the exchange time is recorded, and transmitted to the server 10. The server 10 then divides the usage time of the mobile device 1 by driver D1 based on the received information regarding the exchange time, and generates and outputs report information based on the driving information identified based on the divided time. The contents described in the first embodiment are applicable to any of the other embodiments and modifications.

[0045] Figure 7 is a conceptual diagram illustrating how the driver D1 in this embodiment divides the usage time of the mobile body 1. In this embodiment, the allocation of usage time for each driver of the mobile device 1 is based on the receipt and return of the key. In the example shown in Figure 7, it is shown how the usage time for each driver of the mobile device 1 is allocated in a situation where driver D2 belonging to company B uses the mobile device 1 first, then driver D1 belonging to company A uses the mobile device 1, and then driver D2 of company B uses the mobile device 1 again.

[0046] As shown in the upper part of Figure 7, the usage time of the mobile unit 1 by each driver is divided based on the time of receiving and returning the key. First, when driver D2 receives the key, driver D2's start time of use is recorded, and when driver D2 returns the key, driver D2's end time of use is recorded. Similarly, when driver D1 receives the returned key, driver D1's start time of use is recorded, and when driver D1 returns the key, driver D1's end time of use is recorded. Server 10 divides the usage time based on the start and end times of each of these drivers.

[0047] For example, as shown in the lower part of Figure 7, if we were to attempt to divide the usage time for each driver based on the reservation time, it is possible that a driver may use the mobile device 1 for longer than the reserved time, which could lead to an inaccurate division of usage time.

[0048] [Mobile device usage time segmentation process] The following describes an example of the processing procedure in this embodiment. Figure 8 is a flowchart of the mobile device usage time sorting process performed by server 10. The flowchart described below is merely an example of the information processing procedure in this embodiment, and other steps may be added, some steps may be deleted, or some steps may be executed in the processing unit of another device.

[0049] Furthermore, in this embodiment, as an example rather than an limitation, the key to the mobile body 1 subject to receipt and return is assumed to be a virtual key. Specifically, a virtual key application installed on the information processing device 30 enables the opening and closing of the doors of the mobile body 1 and the starting of the engine, etc., through authentication processing by the server 10 (or a separate authentication server) and data transmission and reception by the communication unit 370. Furthermore, in realizing the virtual key in the information processing device 30, a corresponding virtual key application is installed, and information about the driver to be used (for example, the driver's name, affiliation, etc.) is registered as account information in the server 10 through this virtual key application.

[0050] Furthermore, independently of the mobile body usage time sorting process, the server 10 is assumed to acquire time-series travel information from the mobile body 1 through the travel information acquisition device 20 (S1101). Travel information includes, but is not limited to, acceleration information, speed information, and position information, and is not particularly limited to any information relating to the travel of the mobile body 1. In this embodiment, the acquired travel information is assumed to consist of at least one of the following pieces of information: acceleration information, speed information, and position information. Accordingly, the travel information acquisition device 20 may consist of, for example, at least one of the position information acquisition unit 140, speed information acquisition unit 150, and acceleration information acquisition unit 160.

[0051] First, the server 10 determines, through the information processing device 30, whether a request for permission to use the key has been made (S1001). Whether a request for permission to use the key has been made is determined, for example, by whether an input has been made to the virtual key application in the information processing device 30 through the operation unit 360 indicating a desire to make the key of the mobile device 1 available for use.

[0052] If it is determined that there was no request for permission to use the key (S1001;N), the process returns to step S1001 and makes the same determination again. When it is determined that a request for permission to use the key has been made (S1001; Y), the driver that requested permission to use the key is identified (S1003). Specifically, for example, this is done by referring to the account information of the virtual key application that received the request for permission to use the key.

[0053] Then, the driver is granted the right to use the key, and the time at which the right was granted is obtained from the clock unit 380 and recorded (S1005). The right to use the key is granted only if certain conditions are met (for example, the mobile body 1 is not in use at that time, it is within the period that was reserved in advance, the user who made the reservation has applied for it, etc.). Furthermore, granting key usage rights indicates that, in the information processing device 30 on which the virtual key application for which usage rights was requested is installed, the doors of the mobile unit 1 can be opened and closed and the engine can be started via the second communication unit 370, etc.

[0054] From step S1005 onward, it is possible to recognize which driver is using the mobile body 1, and therefore, an analysis output process is performed based on the time-series acquisition of driving information of the mobile body 1 (S1007). The analysis output process will be described later.

[0055] After step S1007, it is determined whether the right to use the key has been returned (S1009). Whether the right to use the key has been returned is determined by whether, similar to the request for the right to use the key, an input has been made in the virtual key application on the information processing device 30 via the operation unit 360 indicating a desire to return the key of the mobile device 1. Furthermore, the return of the key usage rights makes it impossible to open and close the doors of mobile unit 1 and start the engine, etc., which were previously possible via the second communication unit 370, etc.

[0056] If it is determined in step S1009 that the right to use the key has not been returned (S1009;N), the process returns to step S1007 and continues with the analysis output process. If it is determined that the right to use the key has been returned (S1009; Y), the time when the right to use the key was returned is recorded (S1011).

[0057] After step S1011, report information is created (S1013) based on the travel information of mobile body 1 acquired during the period including the time the key usage rights were granted and the time they were returned (hereinafter referred to as the "specified period"). Note that step S1013 is optional and does not have to be performed. The report information will be described later.

[0058] [Analysis output processing] The analysis output processing performed in step S1007 will be described below. The analysis output processing in this embodiment refers to processing performed based on the driving information acquired for the mobile body 1. Examples include processing that shows the position of the mobile body 1 on a map, as shown in Figures 9 and 10, and processing that shows changes in the driving quality of the mobile body 1. In the analysis output processing, driving information is acquired as it is received and processed accordingly, so it is performed in real time.

[0059] Figure 9 shows an example of the output of an analysis output process, which displays the positions of multiple moving objects, including moving object 1, on a map. This output is displayed, for example, on the display unit 440 of an information processing terminal 40 connected to server 10 via a network NW. As shown in Figure 9, on the map, moving objects are indicated by circular icons, and stationary objects are indicated by square icons. This output is based on the location information included in the driving information acquired at the time of step S1007, and the latest location display for each object is updated as step S1007 is repeated.

[0060] Figure 10 is a flowchart of the process of plotting the position of a moving object on a map, which is an example of the analysis output processing. In the mobile object position plotting process, first, position information included in the latest travel information acquired at the time of execution of step S1007 is extracted (S10071).

[0061] Next, based on the latest predetermined number (e.g., 5) of travel information acquired during step S1007, it is determined whether the mobile body 1 is in motion (S10072). The method for determining whether the mobile body 1 is in motion based on the latest predetermined number of travel information is not particularly limited, but for example, it may be determined based on the magnitude of the difference in position information contained in each of the predetermined number of travel information.

[0062] Then, the moving object 1 is plotted on the map based on the location information extracted in step S10071, in a display manner based on the content determined in step S10072 (S10073). By doing this, it becomes possible to know the current location of each moving object in real time.

[0063] Furthermore, if mobile vehicle 1 is a shared vehicle, the same display as other vehicles will be shown from the time the right to use the key is received until the right to use the key is returned. However, it is preferable that the corresponding icon is not displayed before the right to use the key is received or after the right to use the key is returned. Alternatively, even while driving information is being acquired, the vehicle may stop at the location where the right to use the key was last returned and display an icon indicating the end of the service. In other words, regarding the use of Mobile 1, which is a shared vehicle, by drivers not under management, the server 10 may continue to acquire driving information, but the output will not reflect that usage status.

[0064] [Report Information Creation] In the explanation above, it is stated that report information is created in step S1013, and an example of that report information is described below. Please note that the following description is merely an example of report information, and report information is not limited to this. Report information may include any information generated based on acquired driving data.

[0065] Figure 11 shows an example of report information created in step S1013. The report information shown in Figure 11 is created, for example, in response to a creation request made through the operation unit 460 of the information processing device 40. The created report information is then displayed, for example, on the display unit 440, and its contents are viewed by an administrator or other person who manages multiple mobile bodies, including mobile body 1.

[0066] As shown in Figure 11, the report information is composed of areas, for example, that are described below.

[0067] Area U11 consists of information about the driver for whom the report information is created (hereinafter referred to as the "target driver") (e.g., name and affiliation), and the period for which the report information is created (hereinafter referred to as the "target period"). Here, the target period can be set arbitrarily, and each analysis process is performed and each output is generated based on the driving information corresponding to the set target period. However, since mobile unit 1 is not used by the target driver, driver D1, outside of the specified period, driving information outside of the specified period is not used to create the report information. Therefore, when creating report information for mobile unit 1, if the target period is set to include a period outside of the specified period, each element of the report information will be created with some of the driving information for the target period missing. In this embodiment, the following explanation will be based on the example where the target driver uses only the shared vehicle, Mobile Unit 1, for a specific period and does not use any other vehicles. However, if the target driver uses another vehicle outside of the specific period, the analysis and output will be performed based on the driving information of that other vehicle.

[0068] Area U12 consists of various driving-related scores (e.g., driving score, acceleration score, deceleration score, steering score) calculated based on driving information during the target period for a mobile object driven by the target driver. Here, driving-related scores are, without limitation, examples of scores that quantify the quality of the target driver's driving of the mobile object from various perspectives. Acceleration is an evaluation value of the quality of the forward acceleration of the mobile object, deceleration is an evaluation value of the quality of the backward acceleration of the mobile object, steering is an evaluation value of the quality of the lateral acceleration of mobile object 1, and the driving score is an evaluation value of the quality of all accelerations: acceleration, deceleration, and steering.

[0069] Region U13 is a driving information map generated based on driving information during the target period for a moving object driven by the target driver. A driving information map is, for example, a two-dimensional map of acceleration information included in the acquired driving information based on its direction and magnitude. In this embodiment, the frequency of occurrence of acceleration information is counted for each predetermined category, and a display based on the count value is performed for the region of each category. Note that the display in each category of the acceleration map is not limited to the frequency of occurrence, but may also be based on the probability of occurrence, for example. The generated driving information map may not be a map of acceleration information, but rather a map of speed information. Alternatively, it may be a map of both acceleration information and speed information. In this case, the speed information may be speed information acquired by the speed information acquisition unit 150 in the data processing device 10, or it may be speed information calculated based on position information (for example, a speed state value).

[0070] Area U14 contains timeline information regarding the driver's driving during the specified period. Timeline information summarizes information about each event that occurred while the driver was operating the vehicle. In this embodiment, the start time, event content, event content category, and duration of occurrence are output. By providing timeline information, managers and others can check what tasks the driver performed and what the quality of their driving was. In this case, if the target period is set to include a period outside the specified period, timeline information for the moving object during that period outside the specified period will not be generated. That is, as shown in area U14, timeline information for the period outside the specified period is not displayed, but is shown in gray, and a statement indicating that it is "outside the period for collecting driving information" is included.

[0071] Area U15 is information that maps the trajectory of the vehicle driven by the target driver and the locations where specific driving behaviors were observed onto a map, based on the location information contained in the driving data of the target driver during the target period. By providing such information, managers and others can confirm how the target driver operated the vehicle and what the quality of driving was at each location. Similarly, if the target period is set to include a period outside the specified period, mapping based on the location information of the moving object 1 during that period outside the specified period will not be performed. In other words, it will not be possible to know how the moving object 1 moved during the period outside the specified period.

[0072] Area U16 provides time-series information showing the timing and magnitude of score deductions that affect the calculation of the driving score for vehicles driven by the target driver during the target period. In other words, it displays the extent of score deductions based on output linked to time information. By providing this information, it is possible to understand when and what caused the score to decrease. The time information referred to here may be the time information that is stored in association with the corresponding driving information when it is acquired and stored in the memory unit 220, or the time at the time of output may be acquired from the clock unit 240 and used; the method of acquiring the time information is not particularly limited.

[0073] In the above explanation, a penalty score is derived for each acceleration information according to its direction and magnitude, but the system is not limited to this configuration. At a minimum, an addition or subtraction score is derived according to the content of each driving information, and the final driving score is calculated based on these addition and subtraction scores for each driving information. The bonus / subtraction score may be a positive value if it corresponds to desirable driving information, or it may be 0 or a negative value. In calculating the final driving score, for example, the sum of these bonus / subtraction scores may be added to 70 if the baseline score is 70 points.

[0074] Furthermore, if an addition / deduction score is calculated instead of a deduction score, area U16 may show in chronological order the timing and magnitude of the addition or deduction of points in the score during the target period by the target driver.

[0075] By outputting report information in this way, it is possible to grasp the details of how the target driver operated the vehicle. In this case, the report information is generated and output excluding the period when a driver other than the target driver was driving vehicle 1 (a shared vehicle). Therefore, even when managing shared vehicles, it is possible to generate report information using driving information that appropriately extracts the necessary parts.

[0076] [Example 1] As a variation, the case where the key is a physical key rather than a virtual key will be explained below. The breakdown of usage time is based on the time of key receipt and key return, as in the embodiment described above. In the case of a physical key, which is a variation, the breakdown is performed as follows as an example.

[0077] Figure 12 shows an example of the system configuration of a vehicle management system in a modified example. In the modified example, the system consists of a server 10, a driving information acquisition device 20, an information processing terminal 40, a key box 50, etc., and these devices work together to perform processing. In the modified vehicle management system, for example, a server 10, a driving information acquisition device 20 installed on the mobile unit 1, an information processing terminal 40 capable of viewing report information resulting from the analysis of driving information by the server 10, and a key box 50 that stores the key for the mobile unit 1 and can recognize its removal are all communicated via a network NW (e.g., the Internet).

[0078] The key box 50 is a container for storing and storing physical keys, and is located, for example, near the location where the shared vehicle, mobile unit 1, is normally parked (for example, a parking lot where the shared vehicle is located). The key box 50 is configured to be able to obtain information about the presence or absence of a physical key, or whether the physical key has been retrieved or returned, and to transmit this information to the server 10 via the connected network NW.

[0079] First, similar to S1001, server 10 determines whether a physical key has been removed from key box 50. Whether a physical key has been removed is determined not by any means, but by any means, such as a sensor that detects the presence or absence of a physical key inside key box 50 (for example, a sensor that detects signals from tags attached to the physical key). As an example of other methods, the system may determine whether a physical key has been removed by measuring its weight inside the key box 50. Alternatively, the physical key may be linked to a switch provided in the key box 50, and when the physical key is removed, the switch is activated, sending information that the physical key has been removed to the server 10. The method is not particularly limited.

[0080] Next, similar to step S1003, the driver who extracted the physical key is identified. In the modified example, when identifying the driver, a means is provided to accept input of driver information when opening the key box 50. If appropriate driver information is entered, the key box 50 can be opened and closed, and the driver is identified by sending the entered driver information to the server 10. As an example of other methods, driver D1 may input the identification number written on the physical key taken from key box 50 and its own driver information into an information processing device (not shown) having a similar function to the information processing device 30 in Figure 1, and then transmit the input information to server 10 for identification. The method is not particularly limited.

[0081] The processing from step S1003 onward is the same as in the embodiment described above. Note that, similar to step S1009, determining whether a physical key has been returned can be achieved by the reverse of determining whether a physical key has been retrieved, or by any other arbitrary means.

[0082] [Other variations] In the above description, only the virtual key function was implemented in the information processing device 30, but the information processing device 30 is not limited to the virtual key function. For example, at least one of the display unit 340 and the sound output unit 350 may be used to notify the passenger of the mobile body 1 holding the information processing device 30 of some kind of information. For example, in conjunction with the virtual key function, based on the scheduled time information for receiving and returning the key usage rights, when the time to receive the virtual key approaches (for example, 30 minutes before the scheduled start time), the information processing device 30 may be notified by displaying this information on the display unit 340. The same applies to the return of key usage rights.

[0083] Furthermore, considering that the location where the keys are picked up and returned coincides with the storage location of the vehicle 1, it is also possible to encourage the vehicle 1 to be returned on time by displaying road information near the storage location, such as construction information or traffic congestion information, on the display unit 340 or by providing voice notifications via the sound output unit 350 as the return time approaches while the vehicle 1 is in use. For similar reasons, if the distance between the mobile vehicle 1 and the storage location becomes large and it is considered difficult to return it by the return time (when the time until the return time is less than or equal to the predetermined time, and the distance between the mobile vehicle 1 and the storage location is greater than or equal to the predetermined distance), the system may notify users of this fact by displaying it on the display unit 340 or by providing an audio notification via the sound output unit 350. In this case, the system may also notify the computer of the administrator who manages the shared vehicles via the network NW that it will be difficult to return the vehicle by the return time, or by notifying the computer of the person who has made a reservation to use the mobile vehicle 1 next.

[0084] Furthermore, the administrator may pre-register areas where dangerous driving is likely to occur, based on previously acquired driving information, and when the mobile vehicle 1 approaches such an area, the sound output unit 350 may notify the occupant of the mobile vehicle 1 with a message or beep to remind them to drive carefully. Preferably, such areas are shown in region U15 in Figure 11.

[0085] Furthermore, if the information processing device 30 includes the functions of the driving information acquisition device 20, the information processing device 30 may process the driving information acquired by such functions to determine whether or not dangerous driving has occurred, and if dangerous driving has occurred, it may notify the passengers of the mobile vehicle 1 of this fact through the sound output unit 350 or the like.

[0086] In the above description, it is assumed that a virtual key is realized by installing a virtual key application on the information processing device 30. In this case, the detection of the receipt and return of the virtual key may be performed within the virtual key application, or if detection is performed from outside the virtual key application, it may be done, for example, by releasing the API on the virtual key application side and querying whether the virtual key of the target driver is active (i.e., whether it has been received but has not yet been returned).

[0087] Furthermore, the information processing device 30 may also provide the driver D1 with information related to driving. For example, based on the reservation time of the virtual key, when a predetermined time (e.g., 30 minutes) before the scheduled return time approaches, the display unit 340 may display a message indicating that the return time is approaching, or the voice output unit 350 may output a message indicating that the scheduled return time is approaching. Furthermore, the server 20 may calculate information regarding the driving quality of the mobile unit 1 (for example, a driving score) based on the acquired driving information, receive this calculated driving quality information, and display it on the display unit 340 as appropriate.

[0088] Furthermore, based on the location information acquired by the location information acquisition unit 240 in the driving information acquisition device 20, the distance between the position of the mobile body 1 and a pre-registered return location is calculated and compared with the time until the scheduled return time to determine whether it will be difficult to return the mobile body 1 to the return location at the scheduled return time, and a notification according to the result of that determination may be given via the display unit 340 or the like. For example, if the mobile body 1 is located at a distance that makes it difficult to return it within the time limit when there is a predetermined time (e.g., 30 minutes) until the scheduled return time, the display unit 340 may display a message indicating that it may become difficult to return the mobile body within the time limit when there is another predetermined time (e.g., 15 minutes) before the predetermined time, or a message may be output via the voice output unit 350. Furthermore, as the scheduled return time approaches (for example, 30 minutes or less beforehand), the system may detect whether traffic congestion is occurring near the return location or between the return location and the mobile unit 1. If traffic congestion is present, the system may display this information on the display unit 340 or output a message via the voice output unit 350 to notify the driver that returning the vehicle may become difficult.

[0089] Furthermore, if the information processing device 30 is configured to include a driving information acquisition device 20, the processing unit 310 determines whether dangerous driving has occurred in the mobile body 1 based on the information acquired by the acceleration information acquisition unit 260, etc. If dangerous driving has occurred, the driver is notified by displaying it on the display unit 340 or by outputting a message through the voice output unit 350. In other words, as long as the virtual key is active, even if the vehicle 1 is a shared vehicle, the driver can be notified about whether or not dangerous driving occurred.

[0090] Furthermore, when dividing the usage time of mobile device 1 based on the acquisition and return times of the virtual key, the above explanation states that it is done based on whether a request for the right to use the key was made and whether the right to use the key was returned, but it is not limited to this. For example, when the virtual key function is enabled when the virtual key is in the vicinity of mobile device 1, the usage time of mobile device 1 may be divided based on the detection that the virtual key is in the vicinity of mobile device 1, that is, that communication between the information processing device 30 and mobile device 1 is established, and the detection that the virtual key is not in the vicinity of mobile device 1, that is, that communication between the information processing device 30 and mobile device 1 is interrupted. Of course, the device connected to the information processing device 30 by communication may not be mobile device 1, but rather a virtual key-compatible device installed on mobile device 1. In this way, the usage time of mobile device 1 can be divided without requiring any user interaction regarding key usage rights. Furthermore, there are no particular limitations on how the usage time of mobile unit 1 is divided, and any method can be applied.

[0091] Furthermore, in the above embodiments, various programs and data related to various processes are stored in the storage unit, and the processing unit reads and executes these programs to realize the processes in each embodiment described above. In this case, the storage unit of each device may have recording media (recording media, external storage devices, storage media) such as memory cards (SD cards), CompactFlash® cards, Memory Sticks, USB memory, CD-RWs (optical discs), and MOs (magneto-optical discs), in addition to internal storage devices such as ROM, EEPROM, flash memory, hard disks, and RAM, and the above programs and data may be stored on these recording media.

[0092] Although embodiments and modifications of the present invention have been described in detail above, the scope of the present invention is not limited to the embodiments and modifications described above. Furthermore, the embodiments and modifications described above can be improved and modified in various ways without departing from the spirit of the present invention. In addition, the embodiments and modifications described above can be combined.

[0093] [effect] This invention allows for the proper segmentation of driving information for the desired portion, making it possible to manage even shared vehicles. Therefore, in order to perform proper management, it is possible to utilize shared vehicles without purchasing or maintaining additional vehicles, thereby reducing costs. [Explanation of symbols]

[0094] 1 Mobile Unit 10 servers 20. Driving Information Acquisition Device 30 Information Processing Devices 40 Information Processing Terminals 50 key box

Claims

1. To continuously acquire time-series driving information relating to a mobile body used by multiple users, regardless of the user of the mobile body, Based on the usage rights granting information indicating that the user to whom the usage rights of the key for the mobile device have been granted, the user to whom the usage rights of the key have been granted is identified, and the time of receipt of the key for the mobile device is identified. To identify the time when the aforementioned user returned the key, From the aforementioned time-series acquired driving information, identify the driving information during the usage period of the identified user, which is determined based on the pickup time and the return time. Based on the identified driving information, operational information relating to the operation of the mobile vehicle is generated for the identified user. Information processing methods, including those mentioned above.

2. Based on the acquisition of the aforementioned driving information, the aforementioned operational information will be updated, The information processing method according to claim 1, further comprising:

3. The aforementioned key is a virtual key implemented by an application installed on the information processing device, The time of receipt of the aforementioned key corresponds to the time when the right to use the aforementioned virtual key was granted. The time of return of the aforementioned key corresponds to the time when the right to use the aforementioned virtual key was returned. The information processing method according to claim 1 or 2.

4. The aforementioned key is a virtual key implemented by an application installed on the information processing device, The time of receiving the key corresponds to the time when communication is established between the information processing device and the mobile device or the virtual key device installed on the mobile device. The time of return of the key corresponds to the time when communication between the information processing device and the mobile device or the virtual key device installed on the mobile device is interrupted. The information processing method according to claim 1 or 2.

5. The aforementioned key is a virtual key implemented by an application installed on the information processing device, Releasing the API on the application side, The virtual key is to be determined to be active through the released API, It further includes, The time of receiving the aforementioned key corresponds to the time when the virtual key became active. The return time of the aforementioned key corresponds to the time when the virtual key became inactive. The information processing method according to claim 1 or 2.

6. The aforementioned operational information includes a timeline displaying events related to the mobile object during a predetermined period. During the aforementioned predetermined period, but outside of the usage period, events related to the mobile object will not be displayed. The information processing method according to claim 1 or 2.

7. The aforementioned operational information includes information showing the increase or decrease in the driving score for the mobile unit over a predetermined period in chronological order. During the aforementioned predetermined period, but excluding the aforementioned usage period, the increase or decrease in the driving score for the mobile unit will not be displayed. The information processing method according to claim 1 or 2.

8. On the computer, To continuously acquire time-series driving information regarding a mobile device used by multiple users, regardless of which user of the mobile device is using, Based on the usage rights granting information indicating that the user to whom the usage rights of the key for the mobile device have been granted, the user to whom the usage rights of the key have been granted is identified, and the time of receipt of the key for the mobile device is identified. To identify the time when the aforementioned user returned the key, From the aforementioned time-series acquired driving information, identify the driving information during the usage period of the identified user, which is determined based on the pickup time and the return time. Based on the identified driving information, operational information relating to the operation of the mobile vehicle is generated for the identified user. A program that executes something.

9. An acquisition unit that continuously acquires time-series driving information relating to a mobile body used by multiple users, regardless of which user of the mobile body is used; A user identification unit identifies the user to whom the right to use the key of the mobile body has been granted, based on the right to use the key of the mobile body information. A receipt time identification unit that identifies the time of receipt of the key to the mobile body, A return time identification unit that identifies the time when the key is returned by the identified user, A driving information identification unit identifies driving information during the usage period of the identified user, which is identified based on the time of receipt and the time of return, from among the driving information acquired in the time series. A generation unit generates operational information relating to the operation of the mobile body corresponding to the identified user, based on the identified driving information. An information processing device equipped with the following features.

Citation Information

Patent Citations

  • Rental goods management device and rental fee charging system

    JP2004178523A

  • Vehicle operation management apparatus and vehicle information collecting device

    JP2015038672A

  • Systems and methods for sharing vehicle fleets

    JP2017519270A

  • Information processing system

    JP2019003512A

  • Information processing apparatus, information processing method, and information processing program

    JP2019109814A