Information processing apparatus and information processing system
The information processing system addresses the issue of varying charging costs by calculating fair compensation for rescuers, enhancing motivation and efficiency in resolving electric vehicle power shortages.
Patent Information
- Application Number
- JP2023080352
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-15
- Publication Date
- 2024-11-27
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing systems for rescuing electric vehicles facing power shortages do not account for varying charging costs, leading to potential financial losses for rescuers and reduced motivation.
An information processing system that calculates appropriate compensation for rescuers based on charging cost information, equipment availability, and travel expenses, identifying suitable rescue vehicles and requesting their assistance.
Ensures fair compensation for rescuers, motivating them to assist promptly and effectively, thereby reducing financial burdens and increasing the likelihood of successful rescues.
Smart Images

Figure 2024164687000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to the technical field of an information processing device and an information processing system for solving a problem that occurs in a vehicle. [Background technology]
[0002] Electric vehicles, which can run without using fuel such as gasoline, are becoming more and more popular. Electric vehicles run on electricity stored in an on-board battery, but since charging facilities for on-board batteries are less common than gas stations, they are prone to problems due to running out of power.
[0003] The following Patent Document 1 describes an invention in which a request for rescue is made to vehicles capable of rescuing a vehicle that has run out of power, and a reward is offered to the rescuer. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2022-139845 A Summary of the Invention [Problem to be solved by the invention]
[0005] Incidentally, the cost of charging the on-board battery of an electric vehicle varies more than the cost of purchasing gasoline.
[0006] For example, the electricity rate may be different depending on whether the vehicle battery is charged at night or during the day. Also, the cost of charging may be different depending on whether the battery is normally charged or quickly charged.
[0007] However, the invention described in Patent Document 1 above does not take such charging costs into consideration, which may result in rescuers incurring losses when rescuing a troubled vehicle, which may discourage rescuers from providing rescue services.
[0008] The present invention has been made in consideration of the above circumstances, and has an object to provide an appropriate reward to rescuers. [Means for solving the problem]
[0009] An information processing device according to one embodiment of the present invention comprises one or more processors and a storage medium on which a program executed by the one or more processors is stored, the program including one or more instructions that cause the one or more processors to execute the following processes: acquiring charging cost information related to charging an onboard battery of an information acquisition target vehicle; receiving a rescue request from a troubled vehicle in which a trouble has occurred; extracting vehicles from the information acquisition target vehicles that can resolve the trouble based on rescue details related to resolving the trouble and the remaining battery charge of the onboard battery of the information acquisition target vehicle as rescue candidate vehicles; calculating a reward for each rescue candidate vehicle based on the rescue details and the charging cost information; presenting the rescue candidate vehicles and the reward to a user of the troubled vehicle; identifying a vehicle from the rescue candidate vehicles selected by the user of the troubled vehicle as a rescue vehicle; and notifying the user of the rescue vehicle of a rescue request. Effect of the Invention
[0010] According to the present invention, it is possible to provide an appropriate reward to a rescuer. [Brief description of the drawings]
[0011] [Figure 1] FIG. 1 illustrates an example of a configuration of an information processing system. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of an information processing device. [Diagram 3] FIG. 2 is a diagram showing a hardware configuration of a vehicle 2. [Figure 4] FIG. 2 is a diagram illustrating a functional configuration of a server device. [Diagram 5] FIG. 2 is a diagram illustrating a functional configuration of a vehicle. [Figure 6] 6 is a flowchart illustrating an example of a process executed by a server device to collect information about a vehicle. [Figure 7] 6 is a flowchart illustrating an example of a process executed by a vehicle to transmit information about the vehicle to a server device. [Figure 8] 10 is a flowchart showing an example of a series of processes following FIG. 9, which are executed by the server device to resolve a problem that has occurred in a vehicle having the problem. [Figure 9] 9 is a flow chart showing an example of a series of processes continued from FIG. 8 and executed by the server device to resolve a problem that has occurred in a vehicle in trouble. [Figure 10] 12 is a flowchart showing an example of a series of processes following FIG. 11 and executed by the vehicle to resolve a trouble that has occurred in the troubled vehicle. [Figure 11] 11 is a flowchart showing an example of a series of processes continued from FIG. 10 and executed by the vehicle to resolve a trouble that has occurred in the troubled vehicle. [Figure 12] FIG. 13 is a diagram illustrating a modified example of the configuration of the information processing system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0012] <1. Information processing system configuration> An information processing system S in one embodiment of the present invention is configured to include a server device 1 and one or more vehicles 2 (see FIG. 1).
[0013] The information processing system S is a system for solving a problem that has occurred in a vehicle 2. Specifically, the information processing system S receives a notification from a troubled vehicle 2T, which is a vehicle 2 in which a problem has occurred, and extracts candidates for vehicles 2 that can help solve the problem as rescue candidate vehicles 2P. Then, the information processing system S calculates and presents a reward according to the charging cost of the on-board battery installed in the rescue candidate vehicle 2P.
[0014] In the following explanation, since an electric vehicle is used as an example, terms such as "charging cost" and "electricity cost" are used, but this is merely an example. The vehicle 2 may be a vehicle 2 equipped with an internal combustion engine such as a gasoline vehicle or a diesel vehicle, or a fuel cell vehicle that runs on hydrogen or the like. In that case, this configuration can be applied by replacing "charging cost" with "fuel cost" or the like and "electricity cost" with "fuel consumption" or the like.
[0015] In addition, the information processing system S identifies a vehicle selected by the user of the troubled vehicle 2T from among the rescue candidate vehicles 2P as a rescue vehicle 2R, and transmits a rescue request to the rescue vehicle 2R.
[0016] The server device 1 and the vehicle 2 are capable of communicating with each other via a communication network N.
[0017] <2. Server device configuration> An example of the configuration of the server device 1 is shown in FIG. The server device 1 is configured with a CPU (Central Processing Unit) 31, a ROM (Read Only Memory) 32, a RAM (Random Access Memory) 33, a bus 34, an input / output interface 35, an input section 36, an output section 37, a memory section 38, a communication section 39, a media drive 40, etc.
[0018] The CPU 31 executes various processes according to a program stored in the ROM 32 or a program loaded from the storage unit 38 into the RAM 33. The RAM 33 also stores data and the like necessary for the CPU 31 to execute various processes, as appropriate.
[0019] The CPU 31, the ROM 32, and the RAM 33 are connected to one another via a bus 34. In addition, an input / output interface 35 is also connected to the bus 34.
[0020] To the input / output interface 35, an input unit 36, an output unit 37, a storage unit 38, a communication unit 39, and a media drive 40 are connected. The input unit 36 is composed of a keyboard, a mouse, a touch panel, a microphone, and the like. The output unit 37 is composed of a display such as an LCD (Liquid Crystal Display) or an organic EL (Electro Luminescence) panel, a speaker, and the like.
[0021] The storage unit 38 is configured with an HDD (Hard Disk Drive), a flash memory device, etc. The storage unit 38 stores information on each vehicle 2 for rescuing a troubled vehicle 2T.
[0022] The communication unit 39 performs communication processing and communication between devices via a communication network. Removable media 41 such as a semiconductor memory, a magnetic disk, an optical disk, or a magneto-optical disk is loaded into the media drive 40 as required, and information is written to and read from the removable media 41 .
[0023] In the server device 1, data and programs are uploaded and downloaded through communication by the communication unit 39. In addition, data and programs can be transferred via a removable medium 41. The CPU 31 performs processing operations based on various programs, whereby the server device 1 executes necessary information processing and communication.
[0024] <3. Vehicle configuration> An example configuration of the vehicle 2 is shown in FIG. The vehicle 2 includes a control device 61 , an on-board battery 62 , a PCU (Power Control Unit) 63 , a motor 64 , an operation unit 65 , a display unit 66 , and a connector unit 67 .
[0025] Note that FIG. 3 shows only a portion of the configuration of the vehicle 2, and the vehicle 2 is appropriately equipped with a map locator, various sensors for driving, communication devices, etc., which are not shown.
[0026] The control device 61 is configured with a CPU, a memory, etc., and performs overall control of the vehicle 2. The control device 61 may be provided as a single unit, or may be configured with multiple ECUs (Electronic Control Units). The multiple ECUs may include various types of ECUs, such as a battery control ECU that performs charging control of the in-vehicle battery 62, a display control ECU that performs display control of a display device (including meters, etc.) provided in the vehicle 2, an airbag control ECU, and an air conditioning control ECU.
[0027] The control device 61 realizes various functions by executing various programs stored in a memory or the like. The functions of the control device 61 will be described later.
[0028] The on-board battery 62 is a high-voltage battery used for driving the vehicle 2. The on-board battery 62 supplies power used for driving the wheels, power used for operating an air conditioner of the vehicle 2, and power used for operating other devices. Fig. 3 shows the power supply from the on-board battery 62 used for driving the wheels and the power supply to the display unit 66, and does not show the power supply used for operating each of the other units.
[0029] The vehicle-mounted battery 62 is charged based on the DC voltage supplied from the PCU 63 . An on-board battery 62 supplies a power supply voltage to the PCU 63 for driving the motor 64 .
[0030] The PCU 63 is configured to include an inverter, a DC / DC converter, and the like for driving the motor 64 . The PCU 63 generates an AC current for driving the motor 64 based on the supplied power supply voltage, and supplies the AC current to the motor 64. The PCU 63 controls the torque of the motor 64 by controlling the AC current. The PCU 63 may also be provided with a regenerative braking function to optimize energy efficiency by utilizing regenerative energy.
[0031] The motor 64 is configured as a motor generator having a power generating function, and drives the wheels based on the supplied alternating current.
[0032] The operation unit 65 includes, for example, various types of buttons, levers, and other operators arranged in front of the driver's seat of the vehicle 2. In addition, the operation unit 65 may include an MFD (Multi Function Display) having a touch panel function, a display unit of a navigation device, and the like.
[0033] The user of the troubled vehicle 2T can operate the operation unit 65 to notify the server device 1 that the troubled vehicle 2T is the vehicle in trouble and to request rescue. Furthermore, the user of the troubled vehicle 2T can operate the operation unit 65 to select one vehicle from the rescue candidate vehicles 2P presented by the server device 1 and notify the server device 1 of the selection.
[0034] Furthermore, the user of the rescue vehicle 2R selected from the rescue candidate vehicles 2P can operate the operation unit 65 to select whether or not to accept the rescue request from the server device 1.
[0035] The display unit 66 comprehensively represents, for example, an MFD installed in front of the driver and other display devices for presenting information to the driver. The display unit 66 displays information based on detection signals detected by various sensors provided in the vehicle 2. The display unit 66 appropriately displays various information such as the total distance traveled by the vehicle, the outside temperature, and the instantaneous fuel consumption. Furthermore, the display unit 66 is capable of displaying map information, extracted route information, and the like.
[0036] On the display unit 66 of the troubled vehicle 2T, for example, a menu display for requesting rescue and a display presenting rescue candidate vehicles 2P provided by the server device 1 are displayed.
[0037] Further, the display unit 66 of the rescue vehicle 2R displays a message for selecting whether or not to accept the rescue request.
[0038] The connector unit 67 has a structure into which a charging plug provided in charging equipment installed in each home or at a charging station can be inserted. The connector unit 67 outputs AC voltage supplied via the inserted charging plug to the PCU 63. The PCU 63 is provided with an AC / DC converter and supplies the converted DC voltage to the vehicle-mounted battery 62, thereby charging the vehicle-mounted battery 62.
[0039] <4. Functional configuration> <4-1. Functional configuration of server device>
[0040] The CPU 31 of the server device 1 executes programs to realize various functions. An example of the functions of the CPU 31 in this embodiment is shown in FIG.
[0041] The CPU 31 includes an information acquisition function F1, a rescue request reception function F2, a search processing function F3, a reward calculation function F4, a rescue candidate vehicle presentation function F5, and a rescue request notification function F6.
[0042] The information acquisition function F1 acquires information from the vehicles 2 under its control and updates the information, for example, periodically. The information acquired from the vehicle 2 by the information acquisition function F1 includes, for example, the current location information of the vehicle 2, information on the remaining battery charge of the on-board battery 62 equipped in the vehicle 2, and charging cost information regarding the electricity stored in the on-board battery 62.
[0043] The charging cost information is information indicating, for example, the cost required to accumulate 1 kWh of charging amount, and the like, and is information acquired by the vehicle 2.
[0044] Furthermore, the information acquisition function F1 may acquire rescue records and the like for the vehicle 2. The rescue record information includes date and time information when rescue was performed, and is used to determine whether or not to request rescue depending on the time when a problem occurred in another vehicle 2.
[0045] The rescue request receiving function F2 is a function that receives a rescue request issued from a troubled vehicle 2T in which a problem has occurred. The rescue request reception function F2 performs processes such as identifying the troubled vehicle 2T based on information received from the troubled vehicle 2T, identifying the current location of the troubled vehicle 2T, identifying the details of the trouble (rescue details), and identifying the equipment needed to resolve the trouble.
[0046] The equipment necessary to resolve the trouble includes cables that enable the on-board battery 62 of the troubled vehicle 2T to be charged from the on-board battery 62 of another vehicle 2 if the troubled vehicle 2T is a vehicle that has run out of power, and towing equipment to remove the troubled vehicle 2T from mud if the troubled vehicle 2T is a stuck vehicle that cannot move due to mud or the like.
[0047] The search processing function F3 realizes a process of extracting other vehicles 2 suitable for rescuing the troubled vehicle 2T, i.e., rescue candidate vehicles 2P, in response to the rescue request reception function F2 receiving a rescue request. The search processing function F3 extracts the rescue candidate vehicles 2P based on, for example, information on tools required to resolve the trouble and information on the travel distance to the position of the troubled vehicle 2T.
[0048] The search processing function F3 uses location information of the troubled vehicle 2T and other vehicles 2, information on equipment required to resolve the trouble (hereinafter simply referred to as ``equipment information''), and charging cost information as extraction conditions for extracting rescue candidate vehicles 2P from other vehicles 2.
[0049] For example, the search processing function F3 extracts a vehicle 2 that is close to the troubled vehicle 2T, is equipped with the tools necessary to solve the trouble, and has low charging costs as a rescue candidate vehicle 2P.
[0050] The search processing function F3 may use information on the time required to merge with the troubled vehicle 2T instead of the distance information. That is, the search processing function F3 may preferentially extract, as a rescue candidate vehicle 2P, other vehicles 2 that are farther away but likely to merge smoothly, rather than other vehicles 2 that are close but likely to get caught in traffic.
[0051] The reward calculation function F4 realizes a process of calculating a reward to be paid to a rescuer who rescues a troubled vehicle 2T. When there are multiple rescue candidate vehicles 2P extracted by the search processing function F3, the reward calculation function F4 calculates a reward (payment amount) for each rescue candidate vehicle 2P.
[0052] The remuneration calculated by the remuneration calculation function F4 includes, for example, necessary expenses, which are the costs incurred in the rescue, and a rescue fee, which is an incentive paid for the rescue act.
[0053] The necessary expenses include a travel expense, which is an expense required for the rescue candidate vehicle 2P to join the current location of the troubled vehicle 2T, and a rescue expense for getting the troubled vehicle 2T out of its current trouble.
[0054] The travel cost is calculated based on the travel power consumption and charging cost calculated according to the travel distance and the electricity cost. If a toll road is used for merging, the toll fee is also included in the travel cost. Furthermore, the travel cost may include not only the one-way cost required for the rescue candidate vehicle 2P to merge with the current location of the troubled vehicle 2T, but also the round-trip cost for the rescue candidate vehicle 2P to return to its original position.
[0055] The rescue cost also includes a battery usage fee calculated based on the power consumed by the on-board battery 62 of the rescue candidate vehicle 2P to charge the on-board battery 62 of the troubled vehicle 2T when the troubled vehicle 2T is out of power, and the charging cost. The battery usage fee is calculated by multiplying the charging cost (charging cost) by the power consumption. In addition, if the troubled vehicle 2T is a stuck vehicle, the rescue cost also includes the cost of multiplying the power consumed in towing the troubled vehicle 2T out of the mud by the power receiving cost. In addition, if tools are used in the rescue, the rescue cost may further include the cost of using the tools, etc.
[0056] By paying the necessary expenses plus the compensation for rescue as compensation, rescuers' motivation to rescue can be stimulated.
[0057] The rescue candidate vehicle presenting function F5 realizes a process of presenting rescue candidate vehicles 2P to the user of the troubled vehicle 2T.
[0058] The rescue request notification function F6 realizes a process of identifying a vehicle 2 selected from the rescue candidate vehicles 2P by the user of the troubled vehicle 2T as a rescue vehicle 2R and notifying the rescue vehicle 2R of a rescue request. The rescue request notification function F6 may also receive information from the rescue vehicle 2R that made the rescue request as to whether the rescue request has been accepted. If the rescue request has not been accepted, the rescue request notification function F6 may cause the candidate vehicle presentation function F5 to execute a process of having the user of the troubled vehicle 2T select another rescue vehicle 2R, or may cause the rescue search processing function F3 to execute a process of re-searching for rescue candidate vehicles 2P.
[0059] <4-2. Vehicle Functional Configuration> The control device 61 of the vehicle 2 executes programs to realize various functions. An example of the functions of the control device 61 in this embodiment is shown in FIG.
[0060] The control device 61 of the vehicle 2 includes an information transmission function F11, a rescue request transmission function F12, a rescue candidate vehicle presentation function F13, a selection result transmission function F14, a rescue request reception function F15, and an acceptance result notification function F16.
[0061] The information transmission function F11 is a function corresponding to the information acquisition function F1 on the server device 1 side, and transmits information such as the current location information of the vehicle 2, information on the remaining battery charge of the on-board battery 62 equipped in the vehicle 2, and charging cost information regarding the power stored in the on-board battery 62 in response to a request from the server device 1. The charging cost information to be sent to the server device 1 may be, for example, input by the user of the vehicle 2, or may be obtained by the vehicle 2 communicating with the charging station equipment when charging the on-board battery 62 at the charging station, or by the server terminal and the vehicle 2 communicating via the charging station equipment. In addition, when charging the in-vehicle battery 62 using a charging outlet installed at home, charging cost information may be obtained by communication with a server terminal of an electric power company that has a contract with the vehicle 2, or the charging cost information may be obtained by estimating the charging cost information based on information about the time period during which charging was performed.
[0062] When charging the vehicle battery 62 of the vehicle 2, the information transmission function F11 transmits the charging mode of the vehicle battery 62 or the charging cost of the vehicle battery 62 to the server device 1 even without a request from the server device 1. This allows the server device 1 to keep the charging cost information of the vehicle 2 up to date.
[0063] The rescue request transmission function F12 realizes a process of transmitting a rescue request to the server device 1 in response to a user operation when the vehicle 2 becomes a troubled vehicle 2T, for example, when the vehicle 2 runs out of power or gets stuck in mud.
[0064] The rescue candidate vehicle presenting function F13 realizes a process of presenting to the user rescue candidate vehicles 2P transmitted from the server device 1 after the rescue request is transmitted to the server device 1 by the rescue request transmitting function F12.
[0065] The selection result transmission function F14 realizes a process of transmitting to the server device 1 the user's selection result of the rescue candidate vehicles 2P presented by the rescue candidate vehicle presentation function F13.
[0066] The rescue request receiving function F15 realizes processing for receiving a rescue request sent from the server device 1 in response to a user of a troubled vehicle 2T other than the own vehicle being selected as the rescue vehicle 2R to rescue the troubled vehicle 2T.
[0067] The rescue request receiving function F15 not only notifies the user that a rescue request has been received from the server device 1, but also presents to the user the current location of the troubled vehicle 2T to be rescued, the driving time required to reach the location, the remuneration to be paid, information on tools required for rescue, etc. Note that necessary expenses and the compensation for rescue may be further presented as the breakdown of the remuneration to be paid.
[0068] The acceptance result notifying function F16 realizes a process of notifying the server device 1 of the selection result of whether or not to accept the request made by the user in response to the information presented to the user by the rescue request receiving function F15 as the acceptance result.
[0069] In addition, if there is no user near the vehicle 2 that received the rescue request and no user operation is performed within a certain period of time after receiving the rescue request, the acceptance result notification function F16 may automatically notify the server device 1 of the acceptance result indicating that the rescue request is not accepted.
[0070] <5. Processing flow> An example of the processing executed by the server device 1 and the vehicle 2 will be described with reference to the attached drawings.
[0071] <5-1. Processing for collecting information> First, an example of a process that is periodically executed by the server device 1 to collect information about the vehicle 2 is shown in FIG.
[0072] In step S101, the CPU 31 of the server device 1 selects one vehicle 2. This process is to select one vehicle 2 owned by a user who has indicated a willingness to rescue the vehicle 2 in the event of trouble, and is, for example, a process to select the vehicle 2 of a user who uses the service provided by the server device 1. The vehicle 2 selected here is set as the vehicle 2 to be processed in the subsequent processes.
[0073] In step S102, the CPU 31 first sets OFF the rescue possible flag for the processing target vehicle 2. The rescue possible flag is a flag for identifying a vehicle 2 capable of rescuing another vehicle, and is set ON when it is determined in the subsequent processing that the processing target vehicle 2 can become a rescue vehicle 2R.
[0074] In step S103, the CPU 31 determines whether the vehicle 2 to be processed is in operation. Here, a vehicle 2 in operation is a vehicle 2 for which information transmission is permitted. For example, a vehicle 2 with the ignition turned on, a vehicle 2 being charged, a vehicle 2 being driven, etc., are examples of a vehicle 2 in operation.
[0075] On the other hand, a vehicle 2 that is not in a charging state and not running is regarded as a vehicle 2 for which information transmission is not permitted in order to avoid power consumption due to information transmission processing.
[0076] If it is determined that the vehicle 2 to be processed is not in operation, the CPU 31 ends the series of processes shown in FIG. 6 without executing the processes in and after step S104. The CPU 31 repeatedly executes the series of processes shown in Fig. 6. Specifically, the CPU 31 executes the process of step S101 again to select another vehicle 2 as the vehicle 2 to be processed, and executes the processes from step S102 onwards.
[0077] If it is determined in step S103 that the vehicle 2 to be processed is in operation, the CPU 31 transmits an information transmission request to the vehicle 2 to be processed in step S104. In response to this, the CPU 31 receives information from the vehicle 2 to be processed in step S105.
[0078] The information that the server device 1 receives from the vehicle 2 to be processed in steps S104 and S105 includes, for example, information on the remaining battery charge, the charging cost information described above, and information for identifying the vehicle 2 to be processed, such as the chassis number and VIN (Vehicle Identification Number).
[0079] In step S106, the CPU 31 registers (stores) electricity cost information and the like for the vehicle 2 being processed. The information registered here includes not only electricity cost information but also information indicating charging cost information for charging 1 kWh (kilowatt hour), remaining battery charge, and chassis number, and is the information received in step S105.
[0080] In step S107, the CPU 31 determines whether or not the remaining battery charge of the target vehicle 2 is equal to or greater than a certain level. Since a vehicle 2 whose remaining battery charge is not equal to or greater than a certain level is not suitable as a rescue candidate, the CPU 31 leaves the rescue possibility flag for the target vehicle 2 set to OFF and ends the series of processes shown in FIG.
[0081] On the other hand, if it is determined in step S107 that the remaining battery charge is equal to or greater than a certain level, the CPU 31 determines in step S108 whether vehicle rescue equipment, which is the equipment necessary for resolving the trouble, such as the above-mentioned cables and towing equipment, is installed in the vehicle.
[0082] The information on whether or not the vehicle rescue equipment is mounted on the vehicle is, for example, information received from the vehicle 2 that is the processing target in the reception process of step S105.
[0083] If it is determined that no vehicle rescue equipment is installed on the vehicle, the CPU 31 leaves the rescue possibility flag for the vehicle 2 being processed set to OFF, and ends the series of processes shown in FIG.
[0084] Note that the vehicle 2 to be processed for which the determination in step S108 is No has a remaining battery charge sufficient for rescue, and therefore may be set with a different flag as a reserve vehicle. For example, if the troubled vehicle 2T itself is equipped with the necessary vehicle rescue equipment, the rescue vehicle 2R does not need to have the vehicle rescue equipment on board. In that case, the rescue candidate vehicle 2P or the rescue vehicle 2R may be selected from the vehicles 2 serving as substitute vehicles.
[0085] If it is determined in step S108 that vehicle rescue equipment is installed in the vehicle, the CPU 31 sets the rescue possibility flag for the vehicle 2 to be processed to ON in step S109. As a result, the vehicle 2 to be processed has the possibility of being selected as a rescue candidate vehicle 2P.
[0086] In addition, a rescue possibility flag may be set for each vehicle rescue equipment. For example, for a vehicle 2 that has cables on board but no towing equipment on board, the rescue possibility flag for the cables or the vehicle that has run out of power is set to ON, and the rescue possibility flag for the towing equipment or the stuck vehicle is set to OFF.
[0087] After completing the process of step S109, the CPU 31 executes the process of step S101 again, and selects another vehicle 2 as the vehicle 2 to be processed.
[0088] FIG. 7 shows an example of a process that is executed by the control device 61 of the vehicle 2 in response to the CPU 31 of the server device 1 executing the process shown in FIG.
[0089] In step S201, the control device 61 determines whether or not the information transmission request transmitted from the server device 1 in step S104 in Fig. 6 has been received. If it is determined that the information transmission request has not been received, the control device 61 ends the series of processes shown in Fig. 7.
[0090] On the other hand, if it is determined in step S201 that an information transmission request has been received, the control device 61 acquires charging information in step S202. The acquired charging information here includes information on the remaining battery capacity and charging cost information.
[0091] Next, the control device 61 transmits information to the server device 1 in step S203, and ends the series of processes shown in FIG. The information transmitted in step S203 includes information for identifying the vehicle 2, such as the chassis number and VIN, in addition to the information acquired in step S202.
[0092] <5-2. Processing to resolve the problem> An example of a process executed by the CPU 31 of the server device 1 to resolve a problem occurring in the troubled vehicle 2T will be described with reference to Fig. 8 and Fig. 9. Note that connectors Cn1, Cn2, Cn3, and Cn4 in the figure indicate process connections.
[0093] The CPU 31 determines whether or not there is a troubled vehicle 2T in step S121 of Fig. 8. If there is no troubled vehicle 2T, the CPU 31 repeatedly executes the process of step S121.
[0094] Incidentally, instead of performing the determination process of step S121 shown in FIG. 8, the process of step S122 and the following steps may be executed in response to reception of a notice of the occurrence of trouble from the troubled vehicle 2T as a trigger.
[0095] When it is determined that a troubled vehicle 2T exists, the CPU 31 searches for vehicles 2 located around the troubled vehicle 2T in step S122. In this process, for example, vehicles 2 that exist closer than a predetermined distance from the troubled vehicle 2T may be searched for as nearby vehicles, or vehicles 2 that arrive at the current location of the troubled vehicle 2T within a predetermined time may be searched for as nearby vehicles.
[0096] Furthermore, if there is vehicle rescue equipment necessary to resolve the trouble of the troubled vehicle 2T, the search process of step S122 is executed with the additional condition that the target equipment is already installed in the vehicle.
[0097] In addition, when information indicating that the target equipment is installed in the troubled vehicle 2T itself is received from the troubled vehicle 2T, the search process of step S122 may be executed without the above-mentioned additional condition.
[0098] In step S123, the CPU 31 determines whether or not a vehicle whose rescue possible flag is set to ON is present among the vehicles 2 extracted by the search process. Here, the vehicle 2 extracted by the search process and whose rescue possible flag is set to ON is referred to as a "corresponding vehicle."
[0099] If it is determined in step S123 that no corresponding vehicle is present, the CPU 31 proceeds to further search processing in step S126, which will be described in detail later.
[0100] On the other hand, if it is determined in step S123 that a corresponding vehicle exists, the CPU 31 determines in step S124 whether or not each corresponding vehicle is in operation.
[0101] If it is determined in step S124 that there is no corresponding vehicle in operation, the CPU 31 proceeds to a search process in step S126.
[0102] On the other hand, if it is determined in step S124 that a corresponding vehicle in operation exists, the CPU 31 determines in step S125 whether or not a corresponding vehicle whose remaining battery charge is equal to or greater than the required remaining battery charge exists.
[0103] If it is determined in step S125 that there is no corresponding vehicle whose remaining battery charge is equal to or greater than the required remaining battery charge, the CPU 31 proceeds to a search process in step S126.
[0104] On the other hand, if it is determined in step S125 that a relevant vehicle exists whose remaining battery charge is equal to or greater than the required remaining battery charge, the processing from step S131 onwards is executed to set the relevant vehicle as a rescue candidate vehicle 2P and perform various processes.
[0105] The process of step S125 may be executed as a cut-off process before extracting vehicles in steps S123 and S124. For example, after the cut-off process based on the remaining battery power is executed in step S125, the rescue possibility flag may be checked in step S123, and it may be checked in step S124 whether the vehicle is in operation.
[0106] In this way, the processes of steps S123, S124, and S125 can be executed in any order.
[0107] Here, the above-mentioned additional search process will be described.
[0108] If the determination is No in the processes of steps S123, S124, and S125, it means that there is no vehicle 2 that should be preferentially selected as a rescue candidate vehicle 2P in the vicinity of the troubled vehicle 2T.
[0109] In this case, the CPU 31 proceeds to step S126, and performs a search of all vehicles 2 as the search targets, as an additional search process. In this process, for example, a search process is performed without narrowing down the search results based on the position information of the vehicles 2. That is, the rescue possibility flag is determined for each vehicle 2, and vehicles 2 with the flag set to ON are extracted.
[0110] For the vehicles 2 extracted in step S126, the CPU 31 determines in step S127 whether or not there is a vehicle 2 whose rescue possible flag is ON, determines in step S128 whether or not the vehicle 2 is in operation, and determines in step S129 whether or not there is a vehicle 2 whose remaining battery charge is equal to or greater than the required battery charge.
[0111] The process of step S127 is the same as the process of step S123 except for the vehicle 2 that is the processing target. The process of step S128 is the same as the process of step S124 except for the vehicle 2 that is the processing target. The process of step S129 is the same as the process of step S125 except for the vehicle 2 that is the processing target.
[0112] If the determination is No in any of the processes of steps S127, S128, and S129, the CPU 31 returns to the process of step S126 again. Since the vehicles 2 extracted by the search process of step S126 change over time, the CPU 31 may execute the process of step S126 after a certain period of time has elapsed.
[0113] On the other hand, if the judgment is Yes in all of steps S127, S128, and S129, the CPU 31 calculates the required time for the target vehicle 2 for which the judgment is Yes in all of the steps in step S130, and then proceeds to the processing of step S131, where the target vehicle 2 is set as a rescue candidate vehicle 2P and various processing is performed.
[0114] The process of step S130 is a process of calculating the time required for the target vehicle 2 to move to the troubled vehicle 2T in a state in which it can be rescued. For example, when the remaining battery charge is less than the required remaining battery charge, the required time is calculated by adding the charging time required to secure the required remaining battery charge and the travel time.
[0115] In addition, if the user of vehicle 2 is away from vehicle 2, the required time is calculated by adding the time it takes for the user to go and pick up vehicle 2 and the travel time in vehicle 2.
[0116] In step S131, the CPU 31 sets the rescue candidate vehicle flag to ON for the vehicle 2 determined as Yes in each determination process. As a result, the CPU 31 treats the target vehicle as a rescue candidate vehicle 2P in the subsequent processes. Note that there may be one or more rescue candidate vehicles 2P.
[0117] In step S132, the CPU 31 calculates the travel cost for each rescue candidate vehicle 2P. As described above, the travel cost is calculated by taking into account the power consumption for travel, charging costs, tolls, and the like.
[0118] In step S133, the CPU 31 calculates the rescue cost for each rescue candidate vehicle 2P. As described above, the rescue cost is calculated by taking into account the battery usage fee, the equipment usage fee, and the like.
[0119] In step S134, the CPU 31 calculates a rescue fee for each rescue candidate vehicle 2P. The rescue fee may be a fixed amount, or may be calculated by multiplying the travel cost or rescue cost by a fixed rate. The rescue fee may also be calculated after weighting according to the travel distance or the time spent on rescue work.
[0120] In step S135, the CPU 31 calculates the payment amount for each rescue candidate vehicle 2P. The payment amount is the total payment amount including the travel cost, rescue cost, and rescue compensation.
[0121] After the process of step S135, the CPU 31 transmits information about the rescue candidate vehicle 2P to the troubled vehicle 2T in step S136 of FIG.
[0122] In step S137, the CPU 31 determines whether or not a selection result has been received from the troubled vehicle 2T. The selection result is information that identifies one rescue candidate vehicle 2P selected by the user of the troubled vehicle 2T from one or more rescue candidate vehicles 2P presented to the user.
[0123] The selection result may be information indicating that one rescue candidate vehicle 2P has been selected, or may be information indicating that none of the presented rescue candidate vehicles 2P has been selected.
[0124] If it is determined in step S137 that the selection result has not been received, the CPU 31 repeats the process of step S137.
[0125] On the other hand, if it is determined in step S137 that a selection result has been received, the CPU 31 determines in step S138 whether or not the received selection result is a selection of one rescue candidate vehicle 2P.
[0126] If it is determined that the selection result does not indicate that one rescue candidate vehicle 2P has been selected, but rather that, for example, all of the rescue candidate vehicles 2P have not been selected, the CPU 31 returns to the search process of step S122 in FIG. 8 and performs processing to extract a new rescue candidate vehicle 2P.
[0127] On the other hand, if it is determined that a selection result indicating that one rescue candidate vehicle 2P has been selected has been received, the CPU 31 determines the rescue candidate vehicle 2P as the rescue vehicle 2R in step S139.
[0128] In step S140, the CPU 31 transmits a rescue request to the rescue vehicle 2R.
[0129] In the rescue vehicle 2R that has received the rescue request, the user selects whether or not to accept the rescue request. Then, the rescue vehicle 2R transmits the user's selection result to the server device 1 as an acceptance result. Moreover, if the user does not perform a selection operation within a predetermined time, an acceptance result that assumes that the user has selected not to accept the rescue request is transmitted from the rescue vehicle 2R to the server device 1.
[0130] In step S141, the CPU 31 checks whether or not an acceptance result has been received. The CPU 31 repeats the process of step S141 until an acceptance result is received.
[0131] When it is determined that the acceptance result has been received, the CPU 31 determines in step S142 whether the rescue request has been accepted. When it is determined that the rescue request has been accepted, the CPU 31 notifies the troubled vehicle 2T in step S143 that the rescue vehicle 2R has been selected. In this notification process, the time required for the rescue vehicle 2R to join the troubled vehicle 2T, the total payment amount including necessary expenses and the rescue fee, etc. are presented again.
[0132] On the other hand, if it is determined in step S142 that the user of the rescue vehicle 2R has not accepted the rescue request, the CPU 31 determines in step S144 whether or not there is another rescue candidate vehicle 2P. For example, when multiple rescue candidate vehicles 2P are presented to the user of the troubled vehicle 2T and an unselected rescue candidate vehicle 2P exists among the multiple rescue candidate vehicles 2P, the CPU 31 determines in step S144 that other rescue candidate vehicles 2P exist.
[0133] If it is determined that there is another rescue candidate vehicle 2P, in step S145, the CPU 31 sends to the troubled vehicle 2T information indicating that the rescue request has not been accepted, which is the acceptance result from the rescue candidate vehicle 2P selected by the user, and also sends to the troubled vehicle 2T a notification requesting it to select another rescue candidate vehicle 2P from the rescue candidate vehicles 2P that have already been presented.
[0134] On the other hand, if it is determined in step S144 that there is no other rescue candidate vehicle 2P, the CPU 31 returns to the search process of step S122 in FIG. 8, and performs a process for extracting a new rescue candidate vehicle 2P.
[0135] After completing the process of step S143 or step S145, the CPU 31 ends the process for the troubled vehicle 2T. Then, the CPU 31 returns to the process of step S121 in FIG. 8 to determine whether or not there is another troubled vehicle 2T.
[0136] 10 and 11 show an example of the processing executed by the control device 61 of the troubled vehicle 2T and the rescue candidate vehicle 2P in response to the processing shown in FIGS. Connectors Cn5 and Cn6 in the figure indicate connections for processing.
[0137] In step S221, the control device 61 determines whether or not a condition for transmitting a rescue request is satisfied. For example, when the user of the vehicle 2 performs an operation for making a rescue request, the control device 61 determines that the condition for transmitting a rescue request is satisfied. Alternatively, when the vehicle 2 runs out of power and there is no charging station nearby, it may be determined that the condition for automatically transmitting a rescue request is met.
[0138] If it is determined that the rescue request transmission condition is not met, the control device 61 proceeds to the process of FIG. 11 without executing the remaining process shown in FIG.
[0139] When it is determined that the rescue request transmission condition is met, the control device 61 transmits a rescue request to the server device 1 in step S222. Note that, at the time of executing the process of step S222, the vehicle 2 is treated as a troubled vehicle 2T by the server device 1.
[0140] In step S223, the control device 61 determines whether or not the information on the rescue candidate vehicle 2P has been received from the server device 1. If it is determined that the information on the rescue candidate vehicle 2P has not been received, the control device 61 repeats the process of step S223.
[0141] On the other hand, if it is determined in step S223 that the information on the rescue candidate vehicle 2P has been received, the control device 61 presents the rescue candidate vehicle 2P to the user of the troubled vehicle 2T in step S224.
[0142] In step S225, the control device 61 determines whether or not an operation to select one vehicle 2 from the rescue candidate vehicles 2P has been detected. The control device 61 repeats the process of step S225 until the operation is detected.
[0143] If it is determined in step S225 that a selection operation has been detected, the control device 61 transmits the selection result in step S226. In addition, if a user selection operation is not detected for a predetermined period of time in the processing of step S225, the control device 61 may transmit to the server device 1 as a selection result that all of the presented rescue candidate vehicles 2P were not selected in step S226.
[0144] In step S227, the control device 61 performs a branching process depending on whether or not the user of the troubled vehicle 2T has selected one of the rescue candidate vehicles 2P. For example, if the process of step S226 is executed without selecting a rescue candidate vehicle 2P, the control device 61 determines in step S227 that no rescue candidate vehicle 2P has been selected, and returns to the process of step S223. As a result, the control device 61 receives the information on the rescue candidate vehicle 2P again from the server device 1 in step S223.
[0145] On the other hand, when the process of step S226 is executed by selecting one rescue candidate vehicle 2P, the control device 61 proceeds to step S228 and determines whether or not information indicating whether or not the user of the selected rescue candidate vehicle 2P has accepted the rescue request has been received from the server device 1. The control device 61 repeats the process of step S228 until the control device 61 receives the information.
[0146] When it is determined that an acceptance result indicating whether the rescue request has been accepted or not has been received from the server device 1, the control device 61 presents the acceptance result to the user of the troubled vehicle 2T in step S229.
[0147] Next, in step S230, the control device 61 performs a branching process depending on whether the rescue request has been accepted or not. If it is determined that the rescue request has not been accepted, the control device 61 further determines in step S231 whether or not there is an unselected rescue candidate vehicle 2P.
[0148] If it is determined that there is an unselected rescue candidate vehicle 2P, the control device 61 returns to step S224 and again presents information about the rescue candidate vehicle 2P to the user of the troubled vehicle 2T.
[0149] On the other hand, if it is determined that all of the presented rescue candidate vehicles 2P have been selected, that is, if it is determined that rescue requests have been sent from the server device 1 for all of the presented rescue candidate vehicles 2P, the control device 61 returns to step S223 and waits until it receives information about a new rescue candidate vehicle 2P.
[0150] If it is determined in step S230 that the rescue request has been accepted, the control device 61 determines "Yes" in step S230, and proceeds to step S232 in FIG. The processes following step S232 are executed when the vehicle 2 determines whether or not a rescue request has been received. However, it is highly likely that the troubled vehicle 2T for which the determination in step S221 is Yes will not be able to respond to the rescue request. Therefore, after completing the process of step S230, the control device 61 may be configured not to execute the series of processes shown in FIG. 11 until the trouble with the host vehicle is resolved.
[0151] The control device 61 determines whether or not a rescue request has been received in step S232 of Fig. 11. When the host vehicle is selected as a rescue candidate vehicle 2P by the troubled vehicle 2T that is determined as another vehicle 2, a rescue request is transmitted from the server device 1.
[0152] If it is determined that a rescue request has not been received, the control device 61 returns to step S221 in FIG. 10 without executing the series of processes in FIG.
[0153] On the other hand, when it is determined that a rescue request has been received, the control device 61 presents the rescue request to the user of the host vehicle as the rescue candidate vehicle 2P in step S233. In this presentation process, an operator for accepting or not accepting the rescue request may be presented together with a notification indicating that the rescue request has been received.
[0154] In step S234, the control device 61 determines whether or not an operation for selecting whether or not to accept the rescue request has been detected. The control device 61 repeats the process of step S234 until the operation is detected.
[0155] When it is determined in step S234 that an operation for selecting whether or not to accept the rescue request has been detected, the control device 61 transmits the result of the selection to the server device 1 in step S235.
[0156] If no selection operation is detected for a predetermined period of time in step S234, the control device 61 may transmit to the server device 1 in step S235 a selection result indicating that the rescue request is not accepted.
[0157] <6. Variations> In the above-described example, a configuration has been shown in which the server device 1 and the control device 61 provided in the vehicle 2 cooperate with each other to realize a predetermined function. The application of the present technology is not limited to this, and may be realized by cooperation between the server device 1 and a user terminal device 100 such as a smartphone carried by a user of the vehicle 2 (see FIG. 12).
[0158] The configuration of the user terminal device 100 is as shown in FIG. 2, so a duplicated description will be avoided.
[0159] The CPU 31 of the user terminal device 100 executes a program to realize the functions shown in FIG.
[0160] The CPU 31 of the user terminal device 100, as an information transmission function F11, transmits information on the current location of the vehicle 2, information on the remaining battery charge of the on-board battery 62 provided in the vehicle 2, charging cost information on the power stored in the on-board battery 62, and the like.
[0161] At this time, the current location information may be obtained as substitute information for the current location of the user terminal device 100 and transmitted to the server device 1. In addition, the remaining battery charge and charging cost information of the vehicle 2's on-board battery 62 are obtained by the user inputting the information into the user terminal device 100 or by communication between the user terminal device 100 and the vehicle 2, and then transmitted to the server device 1. The charging cost information may be acquired by the user terminal device 100 from a server terminal of a power company.
[0162] The CPU 31 of the user terminal device 100 detects a user operation for notifying the server device 1 of a trouble and transmits a rescue request to the server device 1 as a rescue request transmission function F12.
[0163] The CPU 31 of the user terminal device 100 performs a process of presenting the rescue candidate vehicles 2P transmitted from the server device 1 to the user as a rescue candidate vehicle presenting function F13.
[0164] The CPU 31 of the user terminal device 100 transmits, as a selection result transmission function F14, to the server device 1 based on the user's selection operation on the rescue candidate vehicles 2P presented to the user.
[0165] The CPU 31 of the user terminal device 100 receives, as a rescue request receiving function F15, from the server device 1 a rescue request for a troubled vehicle 2T other than the user's own vehicle.
[0166] The CPU 31 of the user terminal device 100 notifies the server device 1 of the result of the user's operation in response to the rescue request as the acceptance result, as an acceptance result, using an acceptance result notification function F16.
[0167] In this way, by using the CPU 31 of the user terminal device 100, the various processes described above can be realized without relying on the control device 61 of the vehicle 2.
[0168] The necessary expenses described in the above example may exceed the expected amount. For example, if the planned driving route cannot be traveled and a detour is required, the travel expenses and tolls may differ from the expected amount. To deal with such a case, the server device 1 may notify each user that the necessary expenses are merely estimates. Also, when the estimated necessary expenses are changed, the server device 1 may notify each user of the new information each time.
[0169] Furthermore, if the travel route is changed, the travel time may increase. Therefore, the compensation for rescue may be changed in accordance with changes in necessary expenses. In this case, it is preferable to present the changed payment amount to the user as appropriate.
[0170] <7. Summary> The information processing device as the server device 1 described above includes one or more processors (e.g., CPU 31) and a storage medium (e.g., ROM 32, RAM 33, memory unit 38, removable media 41, etc.) in which a program executed by the one or more processors is stored, and the program includes one or more instructions, which cause the one or more processors to execute the following processes: That is, the one or more instructions cause one or more processors (e.g., CPU 31) to perform the following operations: acquiring charging cost information related to charging the on-board battery 62 of an information acquisition target vehicle (vehicle 2) (steps S104, S105); receiving a rescue request from a troubled vehicle 2T in which a trouble has occurred (step S121); and extracting a vehicle capable of solving the trouble from among the information acquisition target vehicles as a rescue candidate vehicle 2P based on the rescue content related to solving the trouble and the remaining battery charge of the on-board battery 62 of the information acquisition target vehicle (steps S122, S126). The system executes the following processes: calculating a reward (at least a rescue fee) for each rescue candidate vehicle 2P based on the rescue details and charging cost information (steps S132, S133, S134, S135); presenting the rescue candidate vehicle 2P and the reward to the user of the troubled vehicle 2T (step S136); identifying a vehicle 2 (rescue candidate vehicle 2P) selected by the user of the troubled vehicle 2T from among the rescue candidate vehicles 2P as a rescue vehicle 2R (step S139); and notifying the user of the rescue vehicle 2R of a rescue request (step S140). The cost of charging the vehicle battery 62 installed in an EV or HEV varies depending on the charging method. In an information processing device having this configuration, it is possible to calculate an appropriate remuneration by using the charging cost information. This allows a rescue request that is highly appealing to users who are willing to help, and therefore allows for early resolution of the occurring trouble. In addition, by calculating an appropriate reward, the burden on rescuers can be reduced and their motivation to rescue can be increased. Furthermore, since the compensation is presented in advance and both parties are in agreement before a rescue request is made, financial disputes can be avoided. In addition, by increasing the opportunities for ordinary people to be involved in rescue operations, specialized rescue companies will be more available, which will shorten the time it takes to resolve problems that can only be solved by specialized rescue companies. In addition, the information processing device may be provided with a mechanism for automatically paying an appropriate reward from the user of the troubled vehicle 2T to the user of the rescue vehicle 2R. This can avoid troubles at the time of reward payment and further stimulate motivation for rescue. In the above examples, EVs and HEVs are given as examples, but the present invention can be applied to vehicles 2 having internal combustion engines such as gasoline-powered vehicles and fuel cell vehicles. In this case, the travel cost may be calculated as the cost required to travel 1 km, for example.
[0171] In the information processing device as the server device 1 described above, the rescue content may include information on tools required for rescue and information on the travel distance from the position of the information acquisition target vehicle to the position of the troubled vehicle 2T. For example, when a vehicle needs to be towed to resolve a problem, a rescue candidate vehicle 2P is extracted from the vehicles 2 equipped with a towing tool. Therefore, the rescue vehicle 2R selected from the rescue candidate vehicles 2P will also be equipped with the equipment necessary to resolve the trouble, which will prevent a wasted trip to the location of the troubled vehicle 2T but unable to resolve the trouble. In addition, by including travel distance information in the rescue details, the possibility that a vehicle that needs to travel a long distance will be extracted as a rescue candidate vehicle 2P is reduced, which prevents the time required to resolve the problem from becoming too long.
[0172] In the information processing device as the above-mentioned server device 1, one or more instructions may cause one or more processors (e.g., CPU 31) to re-execute the process (step S126) of relaxing the extraction conditions used for extraction if no extracted rescue candidate vehicles 2P exist. For example, the extraction condition may be such that the threshold for the remaining battery charge is relaxed, or vehicles that are further away from the troubled vehicle 2T are extracted. In addition, vehicles that are expected to arrive at the location of the troubled vehicle 2T late may also be extracted. This can improve the possibility of resolving the trouble in the troubled vehicle 2T.
[0173] In the information processing device as the server device 1 described above, one or more instructions may cause one or more processors (for example, the CPU 31) to execute a cut-off process based on the remaining battery power and then execute extraction of rescue candidate vehicles 2P. If it is determined for all of the information acquisition target vehicles whether or not they should be selected as rescue candidate vehicles 2P, the processing time and processing load will increase. With this configuration, by first executing the cut-off process according to the remaining battery charge, it is possible to reduce the processing load and processing time related to the extraction determination.
[0174] The above-mentioned information processing system S is an information processing system S including a first information processing device (server device 1) on the server side and a second information processing device (vehicle 2 or user terminal device 100) linked to a vehicle, and the first information processing device includes one or more first processors (e.g., CPU 31 of the server device 1) and a first storage medium (e.g., ROM 32, RAM 33, memory unit 38, removable media 41, etc. in the server device 1) in which a first program executed by the one or more first processors is stored, and the first program includes one or more first instructions, and the one or more first instructions cause the one or more first processors to execute the following processes. That is, the one or more instructions cause one or more processors (e.g., the CPU 31 of the server device 1) to perform a process of acquiring charging cost information related to charging the on-board battery 62 of the information acquisition target vehicle (vehicle 2) from the second information processing device (steps S104 and S105), a process of receiving a rescue request from a troubled vehicle 2T in which a trouble has occurred (step S121), and a process of extracting a vehicle capable of solving the trouble from among the information acquisition target vehicles as a rescue candidate vehicle 2P based on the rescue content related to solving the trouble and the remaining battery charge of the on-board battery 62 of the information acquisition target vehicle (step The control unit 10 executes the following steps: S122, S126), a process for calculating a reward (at least a rescue fee) for each rescue candidate vehicle 2P based on the rescue content and charging cost information (steps S132, S133, S134, S135), a process for presenting the rescue candidate vehicle 2P and the reward to the user of the troubled vehicle 2T (step S136), a process for identifying a vehicle 2 (rescue candidate vehicle 2P) selected by the user of the troubled vehicle 2T from among the rescue candidate vehicles 2P as a rescue vehicle 2R (step S139), and a process for notifying the user of the rescue vehicle 2R of a rescue request (step S140). Furthermore, the second information processing device (vehicle 2 or user terminal device 100) includes one or more second processors (e.g., the control device 61 of the vehicle 2 or the CPU 31 of the user terminal device 100) and a second storage medium (e.g., the memory of the control device 61 of the vehicle 2 or the ROM 32, RAM 33, memory unit 38, removable media 41, etc. of the user terminal device 100) in which a second program executed by the one or more second processors is stored, and the second program includes one or more second instructions, and the one or more second instructions cause the one or more second processors to execute the following processes. That is, the one or more second instructions cause one or more second processors (e.g., the control device 61 of the vehicle 2 or the CPU 31 of the user terminal device 100) to execute the following processes: a process of transmitting charging cost information related to the charging of the on-board battery 62 of the linked vehicle 2 to the first information processing device (server device 1) (step S203); a process of determining whether or not a trouble has occurred in the linked vehicle 2 (step S221); a process of notifying the first information processing device of the occurrence of trouble if it is determined that a trouble has occurred (step S222); a process of displaying the rescue candidate vehicles 2P and rewards extracted in the first information processing device (step S224); a process of transmitting information identifying a vehicle selected from the rescue candidate vehicles 2P to the first information processing device (step S226); a process of receiving a rescue request from the first information processing device (step S232); and a process of displaying in response to the reception of the rescue request (step S233). Such an information processing system S can also provide the various functions and effects described above.
[0175] The above-described embodiments and modifications can be combined as appropriate. [Explanation of symbols]
[0176] 1. Server device (information processing device) 2 Vehicles 2P Rescue candidate vehicle 2R Rescue vehicle 2T Troubled vehicle 62 Vehicle Battery S Information Processing System
Claims
1. one or more processors; A storage medium storing a program executed by the one or more processors, The program includes one or more instructions, The one or more instructions may be for the one or more processors to: A process of acquiring charging cost information relating to charging an on-board battery of an information acquisition target vehicle; A process of receiving a rescue request from a troubled vehicle; A process of extracting vehicles capable of solving the trouble from among the information acquisition target vehicles as rescue candidate vehicles based on rescue details related to solving the trouble and the remaining battery charge of the on-board battery of the information acquisition target vehicle; calculating a reward for each of the rescue candidate vehicles based on the rescue content and the charging cost information; A process of presenting the rescue candidate vehicle and the reward to a user of the troubled vehicle; A process of identifying a vehicle selected by a user of the troubled vehicle as a rescue vehicle from among the rescue candidate vehicles; and notifying a user of the rescue vehicle of a rescue request. Information processing device.
2. The rescue details include information on tools required for rescue and information on a travel distance from the location of the information acquisition target vehicle to the location of the troubled vehicle. The information processing device according to claim 1 .
3. The one or more instructions may be for the one or more processors to: When the extracted rescue candidate vehicle is not present, the extraction condition used for the extraction is relaxed and the extraction process is executed again. The information processing device according to claim 2 .
4. The one or more instructions may be for the one or more processors to: After the cut-off process based on the remaining battery power is performed, the rescue candidate vehicle is extracted.
4. The information processing device according to claim 1.
5. An information processing system including a first information processing device on a server side and a second information processing device associated with a vehicle, The first information processing device, one or more first processors; a first storage medium storing a first program executed by the one or more first processors; the first program includes one or more first instructions; The one or more first instructions may be for the one or more first processors to: A process of acquiring charging cost information related to charging an on-board battery of an information acquisition target vehicle from the second information processing device; A process of receiving a rescue request from a troubled vehicle; A process of extracting vehicles capable of solving the trouble from among the information acquisition target vehicles as rescue candidate vehicles based on rescue details related to solving the trouble and the remaining battery charge of the on-board battery of the information acquisition target vehicle; calculating a reward for each of the rescue candidate vehicles based on the rescue content and the charging cost information; A process of presenting the rescue candidate vehicle and the reward to a user of the troubled vehicle; A process of identifying a vehicle selected by a user of the troubled vehicle as a rescue vehicle from among the rescue candidate vehicles; and notifying a user of the rescue vehicle of a rescue request. The second information processing device is one or more second processors; a second storage medium storing a second program executed by the one or more second processors; the second program includes one or more second instructions; The one or more second instructions may be for the one or more second processors to: A process of transmitting the charging cost information related to charging an on-board battery of the linked vehicle to the first information processing device; A process for determining whether or not a trouble has occurred in the linked vehicle; a process of notifying the first information processing device of the occurrence of the trouble when the trouble is determined to have occurred; a process of displaying the extracted rescue candidate vehicles and the reward in the first information processing device; a process of transmitting information identifying a vehicle selected from the rescue candidate vehicles to the first information processing device; receiving the rescue request from the first information processing device; and executing a process of displaying the rescue request in response to the reception of the rescue request. Information processing system.
Citation Information
Patent Citations
Vehicle rescue system
JP2022139845A
