JP2025004917A - Information processing system, information processing device, information processing method, and program - Google Patents

Abstract

To provide a technology that enables users to properly address problems caused by forces acting on a vehicle.SOLUTION: An information processing system 1 according to one embodiment of the present disclosure includes: a sensor data acquisition unit 141 for acquiring information representing forces acting on a vehicle 10; and a notification unit 304 for notifying a user U of the use of the vehicle 10 when the degree of forces acting on the vehicle 10 is relatively high relative to a first criterion based on the information acquired by the sensor data acquisition unit 141.SELECTED DRAWING: Figure 1

Description

This disclosure relates to information processing systems, etc.

For example, there is known technology that uses information representing the forces acting on a vehicle (e.g., information about the acceleration acting on the vehicle) to detect the occurrence of a vehicle accident and report the occurrence of the accident to the outside (see Patent Document 1).

Patent No. 6653852

Incidentally, problems may arise due to forces acting on a vehicle other than vehicle accidents. For example, when a vehicle goes over a step, depending on the size of the step, the speed, etc., the forces acting on the vehicle may cause potential damage, or fatigue and deterioration that may lead to damage may accumulate. In such cases, the user may not be able to grasp the problem occurring to the vehicle and may not be able to deal with it appropriately.

Therefore, in consideration of the above issues, the objective is to provide technology that allows users to appropriately deal with problems caused by forces acting on the vehicle.

In order to achieve the above object, in one embodiment of the present disclosure,
an acquisition unit that acquires information representing forces acting on a vehicle;
a notification unit that notifies a user about use of the vehicle based on the information acquired by the acquisition unit.
An information processing system is provided.

In another embodiment of the present disclosure,
an acquisition unit that acquires information representing forces acting on a vehicle;
a notification unit that notifies a user about use of the vehicle based on the information acquired by the acquisition unit.
An information processing device is provided.

In still another embodiment of the present disclosure,
an acquisition step in which an information processing device acquires information representing a force acting on the vehicle;
a notification step of the information processing device notifying a user about use of the vehicle based on the information acquired in the acquisition step,
A method for processing information is provided.

In still another embodiment of the present disclosure,
In the information processing device,
acquiring information representative of forces acting on the vehicle;
a notification step of notifying a user about use of the vehicle based on the information acquired in the acquisition step.
The program is provided.

The above-described embodiment allows the user to appropriately deal with problems caused by forces acting on the vehicle.

FIG. 1 illustrates an example of an information processing system. FIG. 2 illustrates an example of a hardware configuration of a server device. FIG. 2 is a functional block diagram illustrating a functional configuration of an example of an information processing system. 10 is a flowchart illustrating a first example of a process for notifying information relating to vehicle use in a server device. 10 is a flowchart illustrating a second example of a process for notifying information relating to vehicle use in a server device. 10 is a flowchart illustrating a third example of a process for notifying information related to vehicle use in a server device. 13 is a flowchart illustrating a fourth example of a process for notifying information relating to vehicle use in a server device. 10 is a flowchart illustrating a fifth example of a process for notifying information relating to vehicle use in a server device. 6 is a flowchart illustrating an example of a process related to renewal of a warranty period of a vehicle in a server device. 10 is a flowchart illustrating an example of a process for updating the rank of insurance premiums for a vehicle in a server device.

The following describes the embodiment with reference to the drawings.

[Configuration of Information Processing System]
The configuration of an information processing system 1 according to this embodiment will be described with reference to FIG.

Figure 1 is a diagram showing an example of an information processing system 1. Figure 2 is a diagram showing an example of the hardware configuration of a server device 30.

As shown in FIG. 1, the information processing system 1 includes a vehicle 10, a mobile terminal 20, and a server device 30.

The information processing system 1 acquires information representing the forces acting on the vehicle 10, and when it detects that a relatively large force has acted on the vehicle 10, it provides information regarding the use of the vehicle 10 to the user U of the vehicle 10 via the mobile terminal 20.

A relatively large force acting on the vehicle 10 means a force that leads to damage or deterioration of the vehicle 10. Specifically, a relatively large force acting on the vehicle 10 means a force that is relatively large with respect to a predetermined standard (hereinafter, "first standard") corresponding to a force that leads to damage or deterioration of the vehicle 10. The first standard is predefined, for example, through computer simulation, experiment, etc., as a lower limit value of the force acting on the vehicle 10 that leads to damage or deterioration of the vehicle 10. A force that is relatively large with respect to the first standard may be a force equal to or greater than the first standard, or may exceed the first standard. The same applies to the second standard, etc., described below. In addition, the relatively large force acting on the vehicle 10 may be limited to a force that is relatively small with respect to a predetermined standard (hereinafter, "second standard") that is greater than the first standard, so as not to include a very large force corresponding to an accident or the like of the vehicle 10. The second standard is predefined, for example, through computer simulation, experiment, etc., as a lower limit value of the force acting on the vehicle 10 in the event of an accident or the like.

The user U of the vehicle 10 includes, for example, the owner of the vehicle 10. The user U of the vehicle 10 may also include the family of the owner of the vehicle 10, etc.

The information on the use of the vehicle 10 includes, for example, information on the possibility of damage or deterioration of the vehicle 10 due to the use of the vehicle 10. The information on the possibility of damage or deterioration of the vehicle 10 due to the use of the vehicle 10 includes, for example, information that specifically describes damage or deterioration progression that may be caused by a relatively large force acting on the vehicle 10 and that hinders the use of the vehicle 10. This allows the user U to understand what problems will occur when a relatively large force is applied to the vehicle 10. The information on the use of the vehicle 10 may also include information on advice on how to use the vehicle 10 so as not to apply a relatively large force to the vehicle 10. The advice on how to use the vehicle 10 includes, for example, advice on how to set the tire pressure of the wheels. This allows the user U to use the vehicle 10 so as to suppress the application of a relatively large force to the vehicle 10. The information on the use of the vehicle 10 may also include information on maintenance associated with the use of the vehicle 10. Information regarding maintenance associated with the use of the vehicle 10 includes, for example, information on maintenance methods for dealing with damage to the vehicle 10 or the progression of deterioration that may occur due to a relatively large force acting on the vehicle 10, and information guiding to maintenance facilities. This allows the user U to understand how to deal with the situation when a relatively large force acts on the vehicle 10.

Vehicle 10 is a vehicle capable of traveling on roads. Vehicle 10 may be, for example, a light vehicle without a motor, such as a bicycle, or a vehicle with a motor. Motorized vehicles include, for example, automobiles with three or more wheels including wheels spaced apart to a certain extent in the width direction, automobiles with two wheels (motorcycles), regular motorized bicycles, and specific small mopeds.

The vehicle 10 included in the information processing system 1 may be one or multiple.

The vehicle 10 includes a sensor 12, an information processing device 14, and a communication device 16.

The sensor 12 acquires information about the forces acting on the vehicle 10. The sensor 12 is, for example, a three-axis acceleration sensor. The sensor 12 may also be a force sensor, a strain gauge, or the like. The output of the sensor 12 is input to the information processing device 14 via a one-to-one communication line, a local network (LAN: Local Area Network), or a short-distance communication line. The short-distance communication line is, for example, a communication line based on a communication standard such as WiFi or Bluetooth (registered trademark).

The information processing device 14 performs a predetermined process based on the output of the sensor 12. For example, the information processing device 14 determines whether the force acting on the vehicle 10 corresponds to a relatively large force, i.e., whether the force is large relative to the first criterion described above, based on the output of the sensor 12.

The functions of the information processing device 14 are realized by any hardware or a combination of any hardware and software. For example, the information processing device 14 is mainly composed of a computer including a CPU (Central Processing Unit), a memory device, an auxiliary storage device, and an interface device. The memory device is, for example, a static random access memory (SRAM). The auxiliary storage device is, for example, an electrically erasable programmable read only memory (EEPROM) or a flash memory. The interface device includes, for example, a communication interface for communicating with other devices of the vehicle 10, such as the sensor 12 and the communication device 16. The interface device may also include an external interface for connecting to an external recording medium and reading data from the external recording medium or reading data to the external recording medium. This allows the information processing device 14 to install data and programs used for various processes in the auxiliary storage device through the external interface.

The communication device 16 communicates with the mobile terminal 20. The communication device 16 is, for example, a short-range communication module based on a communication standard such as Wi-Fi or Bluetooth.

The functions of the communication device 16 may be integrated into the information processing device 14 as one of the interface devices built into the information processing device 14. The functions of the sensor 12 and the information processing device 14 may be transferred to the mobile terminal 20. For example, information representing the force acting on the vehicle 10, i.e., information representing the acceleration acting on the vehicle 10, may be acquired by an acceleration sensor built into the mobile terminal 20, and the functions of the information processing device 14 may be realized by a CPU or the like of the mobile terminal 20, which will be described later. In this case, the communication device 16 may be omitted.

The mobile terminal 20 is a portable user terminal carried by a user U of the vehicle 10. The mobile terminal 20 is, for example, a smartphone or a tablet terminal. The mobile terminal 20 may also be a laptop-type personal computer (PC).

The functions of the mobile terminal 20 are realized by any hardware or any combination of hardware and software. For example, the hardware configuration of the mobile terminal 20 is the same as that of the server device 30 described below. Specifically, like the server device 30, the mobile terminal 20 may be configured around a computer including an external interface, an auxiliary storage device, a memory device, a CPU, a high-speed arithmetic unit, a communication interface, and an output device. Therefore, FIG. 2 is used as the hardware configuration of the mobile terminal 20, and a detailed description of the hardware configuration of the mobile terminal 20 is omitted.

The server device 30 is connected to the mobile terminal 20 so as to be able to communicate with the mobile terminal 20. The server device 30 may be, for example, an on-premise server, a cloud server, or an edge server.

For example, when the server device 30 determines that a relatively large force has acted on the vehicle 10 based on information received from the mobile terminal 20, the server device 30 transmits information regarding the use of the vehicle 10 to the mobile terminal 20. As a result, the mobile terminal 20 can notify the user of information regarding the use of the vehicle 10 through its own display device, triggered by the act of a relatively large force on the vehicle 10.

The server device 30 may also perform processing related to determining (updating) the insurance premium and warranty period of the vehicle 10 depending on the number of occurrences or frequency of occurrence of an event in which a relatively large force acts on the vehicle 10.

The functions of the server device 30 may be realized by any hardware, or any combination of hardware and software. For example, as shown in FIG. 2, the server device 30 includes an external interface 31, an auxiliary storage device 32, a memory device 33, a CPU 34, a high-speed calculation device 35, a communication interface 36, an input device 37, and an output device 38. The external interface 31, the auxiliary storage device 32, the memory device 33, the CPU 34, the high-speed calculation device 35, the communication interface 36, the input device 37, and the output device 38 are connected by a bus BS.

The external interface 31 functions as an interface for reading data from and writing data to the recording medium 31A. The recording medium 31A includes, for example, general-purpose recording media such as flexible disks, CDs (Compact Discs), DVDs (Digital Versatile Discs), BDs (Blu-ray (registered trademark) Discs), SD memory cards, and USB memories. This allows the server device 30 to read various data used in processing through the recording medium 31A, store the data in the auxiliary storage device 32, and install programs that realize various functions.

The auxiliary storage device 32 stores various installed programs as well as files and data required for various processes. Examples of the auxiliary storage device 32 include a hard disk drive (HDD), a solid state disk (SSD), an EEPROM, and a flash memory.

When an instruction to start a program is received, the memory device 33 reads the program from the auxiliary storage device 32 and stores it. The memory device 33 includes, for example, a dynamic random access memory (DRAM) or an SRAM.

The CPU 34 executes various programs loaded from the auxiliary storage device 32 to the memory device 33, and realizes various functions related to the server device 30 according to the programs.

The high-speed calculation device 35 works in conjunction with the CPU 34 and performs calculation processing at a higher speed than the CPU 34. The high-speed calculation device 35 includes, for example, a GPU (Graphics Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc.

The high-speed calculation device 35 may be omitted depending on the speed of calculation processing required for the server device 30.

The communication interface 36 is used as an interface for connecting to an external device so as to be able to communicate with the device. This allows the server device 30 to communicate with the mobile terminal 20 through the communication interface 36. The server device 30 can also obtain various data and programs used in processing from the external device through the communication interface 36, for example. The communication interface 36 may have multiple types of communication interfaces depending on the communication method between the connected device, etc.

The input device 37 accepts various inputs from the user of the server device 30.

The input device 37 includes, for example, an input device (hereinafter, "operation input device") that accepts mechanical operation input from a user of the server device 30. The operation input device includes, for example, a button, a toggle, a lever, a keyboard, a mouse, a touch panel, a touch pad, etc.

The input device 37 may also include a voice input device capable of receiving voice input from a user of the server device 30. The voice input device includes, for example, a microphone capable of collecting the voice of the user of the server device 30.

The input device 37 may also include a gesture input device capable of receiving gesture input from a user of the server device 30. The gesture input device may include, for example, a camera capable of capturing an image of the user's gesture.

The input device 37 may also include a biometric input device capable of accepting biometric input from a user of the server device 30. The biometric input device includes, for example, a camera capable of acquiring image data containing information about the user's fingerprint or iris.

The output device 38 outputs information to the user of the server device 30.

The output device 38 is, for example, a lighting device or a display device that visually outputs information. The lighting device is, for example, an indicator lamp. The display device is, for example, a liquid crystal display or an organic EL (electroluminescence) display.

In addition, the output device 38 may be a sound output device that outputs auditory information. Examples of the sound output device include a buzzer, an alarm, a speaker, etc.

The functions of the server device 30 may be integrated into the mobile terminal 20. In this case, the server device 30 may be omitted.

[Functional configuration of information processing system]
Next, the functional configuration of the information processing system 1 will be described with reference to FIG.

Figure 3 is a functional block diagram showing an example of the functional configuration of information processing system 1.

As shown in FIG. 3, the information processing device 14 includes, as functional units, a sensor data acquisition unit 141, an event determination unit 142, and a transmission unit 143. These functions are realized, for example, by loading a program installed in an auxiliary storage device into a memory device and executing the program on a CPU.

The sensor data acquisition unit 141 acquires the output data (sensor data) of the sensor 12 at predetermined intervals.

The event determination unit 142 determines whether or not an event has occurred in which a relatively large force acts on the vehicle 10 (hereinafter, simply "event"), based on the sensor data acquired by the sensor data acquisition unit 141. For example, the event determination unit 142 determines that an event has occurred when the force acting on the vehicle 10, measured based on the sensor data, is relatively large with respect to the above-mentioned first criterion. The event determination unit 142 may also determine that an event has occurred when the force acting on the vehicle 10, measured based on the sensor data, is relatively large with respect to the above-mentioned first criterion and relatively small with respect to the above-mentioned second criterion. Hereinafter, the determination of the occurrence of an event may be referred to as "detection of the occurrence of an event."

When the event occurrence is detected by the event determination unit 142, the transmission unit 143 transmits data regarding the occurrence of the event (hereinafter, "event data") to the mobile device 20 via the communication device 16. The event data includes, for example, information indicating the occurrence of the event. The event data may also include sensor data for a predetermined period before and after the occurrence of the event.

The function of the event determination unit 142 may be transferred to the mobile terminal 20 or the server device 30. In this case, the transmission unit 143 transmits the sensor data to the mobile terminal 20. As described above, the functions of the sensor 12 and the information processing device 14 may be transferred to the mobile terminal 20. In this case, the functions of the sensor data acquisition unit 141 and the event determination unit 142 are transferred to the mobile terminal 20, and the function of the transmission unit 143 is omitted.

As shown in FIG. 3, the mobile device 20 includes an event data acquisition unit 201, a transmission unit 202, and a notification unit 203. These functions are realized, for example, by executing a predetermined application program (hereinafter simply "app") installed in an auxiliary storage device on a CPU.

The event data acquisition unit 201 acquires event data from the information processing device 14, which is received via the communication interface.

As described above, when the function of the event determination unit 142 is transferred to the mobile terminal 20 or the server device 30, a sensor data acquisition unit that acquires sensor data received from the vehicle 10 is provided instead of the event data acquisition unit 201.

The transmission unit 202 transmits the event data acquired by the event data acquisition unit 201 to the server device 30.

As described above, when the function of the event determination unit 142 is transferred to the server device 30, the transmission unit 202 transmits the sensor data to the server device 30.

The notification unit 203 notifies the user U of the information received from the server device 30. The notification unit 203 notifies the user U of the information received from the server device 30, for example, in a visual manner using a display device or the like. Furthermore, the notification unit 203 may notify the user U of the information received from the server device 30 in an auditory manner using a sound output device or the like instead of or in addition to a visual manner.

The communication device 16 may be capable of communicating directly with the server device 30, and the transmission unit 143 may transmit the event data to the server device 30 instead of the mobile terminal 20. In this case, the event data acquisition unit 201 and the transmission unit 202 are omitted. In this case, a stationary terminal device (e.g., a desktop PC, etc.) may be adopted instead of the mobile terminal 20, and the stationary terminal device may be equipped with a function equivalent to the notification unit 203.

As shown in FIG. 3, the server device 30 includes an event data acquisition unit 301, a notification determination unit 303, a notification unit 304, a warranty period update unit 305, and an insurance fee update unit 306. These functions are realized, for example, by loading a program installed in the auxiliary storage device 32 into the memory device 33 and executing the program on the CPU 34. The server device 30 also includes an event data storage unit 302. This function is realized, for example, by a storage area defined in the auxiliary storage device 32 or the memory device 33.

The event data acquisition unit 301 acquires event data from the mobile device 20, which is received by the communication interface 36.

As described above, when the event determination unit 142 is transferred to the server device 30, a sensor data acquisition unit that acquires sensor data received from the mobile terminal 20 is provided in place of the event data acquisition unit 301.

The event data storage unit 302 stores the event data acquired by the event data acquisition unit 301 in an accumulated form. This allows the server device 30 to check the history of event data corresponding to the history of event occurrence in the vehicle 10. For example, the event data storage unit 302 has an event data database (hereinafter, for convenience, "event DB (Data Base)") that includes one event of event data acquired by the event data acquisition unit 301 as at least a part of the record data. The record data of the event DB includes, for example, identification information of the vehicle 10 and information on sensor data before and after the event occurrence. The identification information of the vehicle 10 is, for example, a vehicle ID (Identification) or a vehicle number unique to each vehicle 10. The record data of the event DB may also include identification information of a user U that is registered in advance in a form associated with the vehicle 10. The identification information of the user U is a user ID unique to each user U. The record data of the event DB may also include information indicating the type of event corresponding to the event data. For example, the information indicating the type of event in the event DB reflects the result of the event type determination made by the notification determination unit 303 described below. The event type is classified according to the cause of the occurrence of an event in which a relatively large force acts on the vehicle 10. For example, the event types include "insufficient air pressure in the wheels", "excessive air pressure in the wheels", "sudden braking", "sudden acceleration", "abrupt steering", "driving over a large step", etc.

The notification determination unit 303 makes a determination regarding a notification to the user U in response to the detection of the occurrence of an event. For example, the notification determination unit 303 determines whether or not a notification regarding the use of the vehicle 10 is to be sent to the user U in response to the detection of the occurrence of an event. In addition, as described below, when multiple types of events are defined, the notification determination unit 303 may determine (estimate) the type of event as a prerequisite for sending a notification with content that matches the type of event.

The notification unit 304 notifies the user of information regarding the use of the vehicle 10 based on the judgment result of the notification judgment unit 303.

For example, the notification unit 304 transmits a notification signal including information regarding the use of the vehicle 10 to the mobile device 20 through the communication interface 36. Specifically, the notification unit 304 cooperates with an app on the mobile device 20 and transmits the notification signal to the mobile device 20 in the form of a push notification. This allows the notification unit 203 of the mobile device 20 to notify the user U of the information regarding the use of the vehicle 10 received from the server device 30 by a visual method, an auditory method, or the like. Therefore, the server device 30 can provide the user U with information regarding the occurrence of an event on the vehicle 10, i.e., the use of the vehicle 10 associated with the application of a relatively large force to the vehicle 10, through the mobile device 20.

In addition, instead of or in addition to sending a notification signal to a specific mobile terminal 20 of the user U, the notification unit 304 may send information regarding the use of the vehicle 10 to the user U via email or a social networking service (SNS).

The notification unit 304 may also transmit information regarding the use of the vehicle 10 to a maintenance company such as a dealer of the vehicle 10 through the communication interface 36. For example, the notification unit 304 may transmit information regarding the use of the vehicle 10 to a server device or terminal device of the maintenance company through the communication interface 36, or may transmit information regarding the use of the vehicle 10 to an email address of the maintenance company. This allows the maintenance company to provide information regarding the use and maintenance of the vehicle 10 to the user U through a predetermined method, including information regarding the use of the vehicle 10 received from the server device 30. Examples of the predetermined method include telephone, email, and SNS. Therefore, the notification unit 304 can provide information regarding the use of the vehicle 10 to the user U through the maintenance company, including the occurrence of an event of the vehicle 10, i.e., the application of a relatively large force to the vehicle 10.

In addition, instead of the information regarding the use of the vehicle 10, the maintenance company may be sent information indicating the preconditions that led to the notification of that information. This is because the maintenance company can provide information regarding the use of the vehicle 10 based on its own accumulated know-how, etc. The information indicating the preconditions includes event data information.

The warranty period update unit 305 performs processing related to updating the warranty period of the target vehicle 10 based on the event data history of the target vehicle 10 in the event data storage unit 302. For example, the warranty period update unit 305 evaluates the number of times an event occurs and the frequency of occurrence based on the event data history of the target vehicle 10 in the event data storage unit 302, and determines whether or not to extend the warranty period of the target vehicle 10 from the default state depending on the evaluation result. The warranty period update unit 305 transmits the result of the processing related to updating the warranty period to a warranty company such as a vehicle manufacturer through the communication interface 36. For example, the warranty period update unit 305 transmits the result of the processing related to updating the warranty period to a server device of the warranty company through the communication interface 36.

The function of the warranty period update unit 305 may be transferred to a server device of the warranty company. In this case, the event data history of the target vehicle 10 in the event data storage unit 302 is provided to, for example, a server device of the warranty company.

The insurance premium update unit 306 performs processing related to updating the premiums of a specified optional insurance policy that is subscribed to in a manner that specifies the target vehicle 10, based on the event data history of the target vehicle 10 in the event data storage unit 302. For example, at the timing of renewal of the specified optional insurance, the insurance premium update unit 306 evaluates the number of occurrences and frequency of events based on the event data history of the target vehicle 10 in the event data storage unit 302, and updates the insurance premium rank according to the evaluation result. The insurance premium update unit 306 transmits the results of the processing related to updating the insurance premium to the insurance company via the communication interface 36. For example, the insurance premium update unit 306 transmits the results of the processing related to updating the insurance premium to a server device of the insurance company via the communication interface 36.

The function of the insurance premium update unit 306 may be transferred to a server device or the like of the insurance company. In this case, the event data history of the target vehicle 10 in the event data storage unit 302 is provided to, for example, a server device or the like of the insurance company.

[Notification process regarding vehicle use information]
Next, a specific example of a process for notifying information relating to the use of the vehicle 10 in the server device 30 will be described with reference to FIGS.

<First Example>
4 is a flowchart illustrating a first example of a notification process of information related to the use of the vehicle 10 in the server device 30. This flowchart is repeatedly executed for each vehicle 10 included in the information processing system 1 at predetermined processing intervals, for example.

As shown in FIG. 4, in step S102, the notification determination unit 303 checks the event DB in the event data storage unit 302.

When the processing of step S102 is completed, the server device 30 proceeds to step S104.

In step S104, the notification determination unit 303 determines whether an event occurrence has been detected for the target vehicle 10. If new record data including event data for the target vehicle 10 has been registered in the event DB, the notification determination unit 303 determines that an event occurrence has been detected. If an event occurrence has been detected for the target vehicle 10, the notification determination unit 303 proceeds to step S106, otherwise it ends the processing of this flowchart.

In step S106, the notification unit 304 transmits a notification signal including information regarding the use of the vehicle 10 to the mobile terminal 20 of the user U of the target vehicle 10.

When step S106 is completed, the process of this flowchart ends.

In this way, in this example, when the server device 30 detects the occurrence of an event indicating that a relatively large force has been applied to the vehicle 10, it can provide the user U with information regarding the use of the vehicle 10 via the mobile terminal 20. Therefore, the user U can grasp, for example, the specific content of problems such as damage to the vehicle 10 and the progression of deterioration of the vehicle 10 that may occur when a relatively large force is applied to the vehicle 10, and how to deal with these problems. In addition, the user U can grasp, for example, how to use the vehicle 10 so as to prevent a relatively large force from being applied to the vehicle 10. Therefore, the server device 30 can improve the convenience of the user U, and can also improve safety by suppressing the occurrence of damage to the vehicle 10 during use that accompanies continued use of the vehicle 10.

<Second Example>
5 is a flowchart illustrating a second example of a notification process of information related to the use of the vehicle 10 in the server device 30. This flowchart is repeatedly executed for each vehicle 10 included in the information processing system 1 at predetermined processing intervals, for example.

As shown in FIG. 5, steps S202 and S204 are the same as steps S102 and S104 in FIG. 4, so their explanation is omitted.

If the notification determination unit 303 detects that an event has occurred for the target vehicle 10, it proceeds to step S206; otherwise, it ends the processing of this flowchart.

In step S206, the notification determination unit 303 estimates the type of event based on the latest event data of the target vehicle 10.

For example, the notification determination unit 303 estimates the type of event according to the direction of the force acting on the target vehicle 10 and the tendency of the change in the force acting over time. This is because the direction of the force and the tendency of the change in the force over time vary depending on the cause of a relatively large force acting on the vehicle 10. Specifically, the notification determination unit 303 may estimate the type of event by pattern matching between data of the force acting on the vehicle 10 when an event occurs on the target vehicle 10 and reference data of the force acting on the vehicle 10 that is specified for each type of event. In addition, the notification determination unit 303 may estimate the type of event from data of the force acting on the vehicle 10 when an event occurs on the target vehicle 10, for example, by using a learned model to which supervised learning is applied based on a known machine learning technique such as deep learning.

When the processing of step S206 is completed, the server device 30 proceeds to step S208.

In step S208, the notification unit 304 transmits a notification signal including information regarding the use of the vehicle 10 according to the type of event estimated in step S206 to the mobile device 20 via the communication interface 36.

When the processing of step S208 is completed, the server device 30 ends the processing of this flowchart.

In this way, in this example, the server device 30 can vary the content of the information regarding the use of the vehicle 10 depending on the type of event detected, i.e., the cause of the event occurrence. Therefore, the user can more appropriately grasp the specific details of the progress of damage and deterioration of the vehicle 10 and how to deal with it, which may differ depending on the cause of the event occurrence, for example. In addition, the user can more appropriately grasp how to use the vehicle 10 to prevent a relatively large force from acting on the vehicle 10, which may differ depending on the cause of the event occurrence, for example. Therefore, the server device 30 can further improve the convenience of the user U, and can more appropriately suppress the occurrence of damage, etc., during use of the vehicle 10 that accompanies continued use of the vehicle 10, thereby further improving safety.

<Third Example>
6 is a flowchart illustrating a third example of a notification process of information related to the use of the vehicle 10 in the server device 30. This flowchart is repeatedly executed for each vehicle 10 included in the information processing system 1 at predetermined processing intervals, for example.

As shown in FIG. 6, steps S302 and S304 are the same as steps S102 and S104 in FIG. 4, so their explanation is omitted.

If the notification determination unit 303 detects that an event has occurred for the target vehicle 10, it proceeds to step S306; otherwise, it ends the processing of this flowchart.

In step S306, the notification determination unit 303 determines whether the cumulative value FS of the force acting on the target vehicle 10 is equal to or greater than a predetermined threshold value FS_th1, based on the event data history in the event data storage unit 302. The cumulative value FS of the force acting on the target vehicle 10 is the cumulative value of the maximum value of the force acting on the vehicle 10 for each event occurrence from the start of use of the target vehicle 10 to the present. If the cumulative value FS of the force acting on the target vehicle 10 is equal to or greater than the threshold value FS_th1, the notification determination unit 303 proceeds to step S308; otherwise, the notification determination unit 303 ends the processing of this flowchart.

Step S308 is the same as step S106 in FIG. 4, so the explanation is omitted.

When the processing of step S308 is completed, the server device 30 ends the processing of this flowchart.

In this way, in this example, the server device 30 notifies the user of information regarding the use of the vehicle 10 when a relatively large force is applied to the vehicle 10 and the cumulative value of that force is relatively large compared to a predetermined standard. Therefore, the server device 30 can wait until a situation is determined to be high probability of damage or further deterioration of the vehicle 10, and then notify the user of information regarding the use of the vehicle 10. Therefore, the server device 30 can improve the safety of the vehicle 10 by providing the user with information regarding the use of the vehicle 10, while preventing situations in which the user feels annoyed by frequent notifications.

<Fourth Example>
7 is a flowchart illustrating a fourth example of a notification process of information related to the use of the vehicle 10 in the server device 30. This flowchart is repeatedly executed for each vehicle 10 included in the information processing system 1 at predetermined processing intervals, for example.

As shown in FIG. 7, steps S402 and S404 are the same as steps S102 and S104 in FIG. 4, so their explanation is omitted.

If the notification determination unit 303 detects that an event has occurred for the target vehicle 10, it proceeds to step S406; otherwise, it ends the processing of this flowchart.

In step S406, the notification determination unit 303 determines whether the event occurrence frequency FQ for the target vehicle 10 is equal to or greater than a predetermined threshold value FQ_th1 based on the event data history in the event data storage unit 302. The event occurrence frequency FQ is, for example, the number of times an event occurs per predetermined unit period during the entire period from when the vehicle 10 began to be used until the present. The event occurrence frequency may also be the number of times an event occurs per predetermined unit period during the most recent predetermined period. If the event occurrence frequency FQ for the target vehicle 10 is equal to or greater than the threshold value FQ_th1, the notification determination unit 303 proceeds to step S408; otherwise, the notification determination unit 303 ends the processing of this flowchart.

In addition, in step S406, the notification determination unit 303 may determine whether the number of times an event has occurred since the start of use of the vehicle 10 to the present, or the number of times an event has occurred in the most recent specified period, is equal to or greater than a threshold value.

Step S408 is the same as step S106 in FIG. 4, so the explanation is omitted.

When the processing of step S408 is completed, the server device 30 ends the processing of this flowchart.

In this way, in this example, the server device 30 notifies the user of information regarding the use of the vehicle 10 when the frequency or number of occurrences of an event in which a relatively large force acts on the vehicle 10 is relatively high compared to a predetermined standard. Therefore, the server device 30 can wait until a situation in which it is determined that there is a high possibility of damage to or further deterioration of the vehicle 10, and then notify the user of information regarding the use of the vehicle 10. Therefore, the server device 30 can improve the safety of the vehicle 10 by providing the user with information regarding the use of the vehicle 10, while preventing situations in which the user feels annoyed by frequent notifications.

<Fifth Example>
8 is a flowchart illustrating a fifth example of a notification process of information related to the use of the vehicle 10 in the server device 30. This flowchart is repeatedly executed for each vehicle 10 included in the information processing system 1 at predetermined processing intervals, for example.

As shown in FIG. 8, steps S502 and S504 are the same as steps S102 and S104 in FIG. 4, so their explanation is omitted.

If the notification determination unit 303 detects that an event has occurred for the target vehicle 10, it proceeds to step S506; otherwise, it ends the processing of this flowchart.

Step S506 is the same as step S206 in Figure 5, so its explanation is omitted.

When processing of step S506 is completed, the server device 30 proceeds to step S508.

Step S508 is the same as step S406 in FIG. 7, so the explanation is omitted.

If the event occurrence frequency FQ is equal to or greater than the predetermined threshold FQ_th1, the notification determination unit 303 proceeds to step S510; otherwise, it terminates the processing of this flowchart.

In addition, in step S508, the notification determination unit 303 may determine whether the number of events that have occurred since the start of use of the vehicle 10 to the present or the number of events that have occurred in the most recent specified period is equal to or greater than a threshold value.

In step S<b>510 , notification unit 304 transmits to mobile device 20 a notification signal including information regarding the use of vehicle 10 in accordance with the combination of event types included in the event data history in event data storage unit 302 .

In addition, if the types of previously detected events corresponding to the event data history are all the same, the notification unit 304 may send a notification signal including information regarding the use of the vehicle to the mobile terminal 20 according to the type of event, as in step S208 of Figure 5.

In this way, in this example, the server device 30 can vary the content of the information related to the use of the vehicle 10 depending on the type of event in the event occurrence history, i.e., the combination of causes of the event occurrence. Therefore, the user U can more appropriately grasp the specific details of the progress of damage and deterioration of the vehicle 10 and the countermeasures, which may differ depending on the combination of causes of the event occurrence, for example. In addition, the user U can more appropriately grasp the method of using the vehicle 10 to prevent a relatively large force from acting on the vehicle 10, which may differ depending on the type of event in the event occurrence history, i.e., the combination of causes of the event occurrence. Therefore, the server device 30 can further improve the convenience of the user U, and can more appropriately suppress the occurrence of damage, etc., during use of the vehicle 10 due to continued use of the vehicle 10, thereby further improving safety.

[Vehicle warranty renewal process]
Next, a specific example of the process of updating the warranty period of the vehicle 10 in the server device 30 will be described with reference to FIG.

Figure 9 is a flowchart that shows an example of a process for updating the warranty period of the vehicle 10 in the server device 30. This flowchart is executed at a predetermined update timing that is set, for example, within the default warranty period of the target vehicle 10.

As shown in FIG. 9, in step S602, the warranty period update unit 305 checks the event DB in the event data storage unit 302.

When the processing of step S602 is completed, the server device 30 proceeds to step S604.

In step S604, the warranty period update unit 305 determines whether the number of times NT that an event has occurred during the period from the start of use of the target vehicle 10 to the present is equal to or less than a predetermined threshold NT_th1. If the number of times NT that an event has occurred is equal to or less than the threshold NT_th1, the warranty period update unit 305 proceeds to step S606; otherwise, the warranty period update unit 305 ends the processing of this flowchart.

In step S606, the warranty period update unit 305 updates the warranty period by extending the warranty period of the target vehicle 10 from the default value. The extension amount may be a fixed value or a variable value. If it is a variable value, the extension amount is set, for example, so that it is larger as the number of times the event occurs NT is smaller.

When the processing of step S606 is completed, the server device 30 ends the processing of this flowchart.

In addition, the warranty period update unit 305 may update the warranty period by extending the warranty period of the target vehicle 10 from the default value when the event occurrence frequency FQ (the number of occurrences per unit period) is relatively small compared to a predetermined threshold value instead of the number of event occurrences NT. Also, as in the case where the event occurrence frequency NT is adopted, the extension amount of the warranty period may be a constant value or may be a variable value, and if it is a variable value, the extension amount may be set to be larger as the event occurrence frequency FQ is smaller.

In this way, in this example, the warranty period update unit 305 updates the warranty period by extending it from the default value when the number of times NT or the frequency FQ of an event occurrence is relatively small compared to a predetermined standard. This allows the server device 30 to provide an incentive to extend the warranty period for vehicles 10 that are not subjected to a relatively large force many times or at a low frequency.

[Vehicle insurance premium rank update process]
Next, a specific example of the process of updating the insurance premium rank of the vehicle 10 in the server device 30 will be described with reference to FIG.

Figure 10 is a flowchart that shows an example of the process of updating the insurance premium rank of the vehicle 10 in the server device 30. This flowchart is executed, for example, in accordance with the timing of updating the insurance premium of the vehicle 10.

As shown in FIG. 10, in step S702, the insurance premium update unit 306 checks the event DB in the event data storage unit 302.

When the processing of step S702 is completed, the server device 30 proceeds to step S704.

In step S704, the insurance premium update unit 306 determines whether the number of times NT that an event has occurred during the current insurance contract period is equal to or less than a predetermined threshold NT_th2. If the number of times NT that an event has occurred during the current insurance contract period is equal to or less than the threshold NT_th2, the insurance premium update unit 306 proceeds to step S706; otherwise, the insurance premium update unit 306 ends the processing of this flowchart.

In step S706, the insurance premium update unit 306 updates the insurance premium rank of the target vehicle 10 in the direction of decreasing the insurance premium. The change range of the insurance premium rank may be a fixed value or a variable value. If it is a variable value, the change range is set, for example, to be larger as the number of occurrences of the event decreases.

When the processing of step S706 is completed, the server device 30 ends the processing of this flowchart.

In addition, the insurance premium update unit 306 may update the rank of the insurance premium of the target vehicle 10 in the direction of decreasing the insurance premium when the frequency of occurrence of the event FQ (the number of occurrences per unit period) of the event is relatively small compared to a predetermined threshold value, instead of the number of occurrences of the event NT. Also, as in the case where the number of occurrences of the event NT is used, the change range of the insurance premium rank may be a constant value or a variable value, and if it is a variable value, the change range may be set to be larger as the frequency of occurrence of the event FQ is smaller.

In this way, in this example, the insurance premium update unit 306 updates the insurance premium rank in the direction of lowering the insurance premium when the number of times NT or frequency FQ of an event occurrence is relatively small compared to a predetermined standard. This allows the server device 30 to provide an incentive to lower the insurance premium for vehicles 10 that are not subjected to a relatively large force many times or with a low frequency.

[Other embodiments]
Next, another embodiment will be described.

The above-described embodiments may be modified or altered as appropriate.

For example, in the above embodiment, the information processing system 1 notifies the user U of information regarding the use of the vehicle 10, determines the warranty period for the vehicle 10, and determines the insurance premium for the vehicle 10 based on the sensor data, but may perform only some of these functions.

[Action]
Next, the operations of the information processing system, the information processing device, the information processing method, and the program according to the present embodiment will be described.

In this embodiment, the information processing system includes an acquisition unit and a notification unit. The information processing system is, for example, the information processing system 1 described above. The acquisition unit is, for example, the sensor data acquisition unit 141 described above. The notification unit is, for example, the notification unit 203 or the notification unit 304 described above. Specifically, the acquisition unit acquires information representing forces acting on the vehicle. The vehicle is, for example, the vehicle 10 described above. Then, the notification unit notifies the user about the use of the vehicle based on the information acquired by the acquisition unit.

In addition, in this embodiment, the information processing device includes an acquisition unit and a notification unit. The information processing device is, for example, a mobile terminal 20 or a server device 30. The acquisition unit acquires information representing forces acting on the vehicle. The acquisition unit is, for example, a sensor data acquisition unit provided in place of the above-mentioned event data acquisition unit 201 or event data acquisition unit 301. Then, the notification unit notifies the user about the use of the vehicle based on the information acquired by the acquisition unit.

In this embodiment, the information processing method includes an acquisition step and a notification step. Specifically, in the acquisition step, the information processing device acquires information representing forces acting on the vehicle. Then, in the notification step, the information processing device notifies the user about the use of the vehicle based on the information acquired in the acquisition step.

In addition, in this embodiment, the program may cause the information processing device to execute an acquisition step and a notification step.

This allows the information processing system or information processing device (hereinafter referred to as "information processing system, etc.") to grasp the state of the forces acting on the vehicle. Therefore, the information processing system, etc. can appropriately provide notifications regarding the use of the vehicle depending on the occurrence of an event in which a relatively large force is acting on the vehicle that will not immediately render the vehicle unusable, but will lead to damage or further deterioration if the vehicle is continued to be used. Therefore, the information processing system, etc. can support the user in appropriately dealing with problems caused by forces acting on the vehicle.

In addition, in this embodiment, the notification regarding the user's use of the vehicle may include at least one of a notification regarding the possibility of damage or deterioration of the vehicle occurring as the vehicle is used, a notification regarding maintenance associated with the use of the vehicle, and a notification regarding how the vehicle is used.

As a result, the information processing system etc. can notify the user about damage to the vehicle or the progression of deterioration associated with use of the vehicle, which may occur, for example, when a relatively large force is applied to the vehicle. The information processing system can also notify the user about maintenance to address damage to the vehicle or the progression of deterioration, which may occur, for example, when a relatively large force is applied to the vehicle. The information processing system can also notify the user about a method of using the vehicle to suppress the progression of damage to the vehicle or the progression of deterioration, which may occur, for example, when a relatively large force is applied to the vehicle. Therefore, the information processing system can improve the convenience of the user, as well as suppress the progression of damage to the vehicle and deterioration, and improve the safety of the vehicle.

In addition, in this embodiment, the notification unit may notify the user when the degree of force acting on the vehicle is relatively high with respect to a predetermined criterion. The predetermined criterion is, for example, the first criterion described above.

This allows the information processing system, etc., to notify the user about the use of the vehicle when a relatively large force is applied to the vehicle, taking into account the possibility of damage to the vehicle or further deterioration.

In addition, in this embodiment, the notification unit may notify the user depending on the direction or time series change of the force acting on the vehicle.

This allows the information processing system, etc., to notify the user, for example, depending on the cause of a relatively large force acting on the vehicle. This is because the cause of the relatively large force acting on the vehicle can result in differences in the direction or time-series changes of the force acting on the vehicle.

In addition, in this embodiment, the notification unit may vary the content of the notification to the user depending on the direction of the force acting on the vehicle or the trend indicated by the change over time.

This allows the information processing system, etc. to appropriately change the notification to the user depending on the cause of the relatively large force acting on the vehicle. Therefore, the information processing system, etc. can provide an appropriate notification to the user in accordance with the cause of the relatively large force acting on the vehicle. Therefore, the information processing system, etc. can further improve the convenience for the user and can further improve the safety of the vehicle.

In addition, in this embodiment, the information processing system etc. may include an estimation unit. The estimation unit is, for example, the notification determination unit 303 described above. Specifically, the estimation unit may estimate the cause of the force acting on the vehicle based on the direction of the force acting on the vehicle or a trend indicated by a change over time. Then, the notification unit may notify the user based on the estimation result of the estimation unit.

This allows the information processing system, etc. to notify the user depending on the cause of the relatively large force acting on the vehicle.

In addition, in this embodiment, the information processing system or the like may include a detection unit. The detection unit is, for example, the event determination unit 142 described above. Specifically, the detection unit may detect the occurrence of a specified event that indicates a state in which a force acting on the vehicle is relatively large with respect to a specified standard, based on the information acquired by the acquisition unit. Then, the notification unit may notify the user based on the history of the specified event detected by the detection unit.

This allows the information processing system, etc. to notify the user more appropriately depending on the occurrence of an event in which a relatively large force acts on the vehicle.

In addition, in this embodiment, the notification unit may notify the user when a cumulative value representing the degree of force acting on the vehicle for the history of a specified event is relatively high with respect to a specified criterion. The cumulative value is, for example, the above-mentioned cumulative force value FS. The specified criterion is, for example, the above-mentioned threshold value FS_th1.

This allows the information processing system etc. to notify the user when it determines that there is a high possibility of damage to the vehicle or further deterioration due to an accumulation of events in which a relatively large force acts on the vehicle. Therefore, the information processing system etc. can prevent situations in which the user feels annoyed by frequent notifications while ensuring the safety of the vehicle.

In addition, in this embodiment, the notification unit may notify the user when the occurrence frequency of a specified event is relatively high compared to a specified criterion.

This allows the information processing system, etc. to notify the user when it determines that there is a high possibility of damage or deterioration to the vehicle due to a high occurrence rate of events in which a relatively large force acts on the vehicle. Therefore, the information processing system, etc. can prevent situations in which the user feels annoyed by frequent notifications while ensuring the safety of the vehicle.

In addition, in this embodiment, there may be multiple types of specified events. The notification unit may vary the content of the notification to the user depending on the type of the specified event included in the history of the specified events.

This allows the information processing system etc. to provide more appropriate notifications to the user depending on the type of event in which a relatively large force acts on the vehicle.

In addition, in this embodiment, the information processing system or the like may include a processing unit. The processing unit is, for example, the warranty period update unit 305 or the insurance premium update unit 306 described above. Specifically, the processing unit may perform processing to reflect the tendency regarding the degree of force acting on the vehicle in the warranty period or insurance premium of the vehicle based on the information acquired by the acquisition unit.

This allows the information processing system, etc. to take into account, for example, the frequency with which a relatively large force acts on the vehicle. Therefore, the information processing system, etc. can more appropriately determine the vehicle warranty period and insurance premiums by taking into account the actual manner in which the user uses the vehicle.

In addition, in this embodiment, the processing unit may extend the warranty period of the vehicle or reduce the insurance premium if the frequency or number of occurrences of a state in which the degree of force acting on the vehicle is relatively high compared to a predetermined standard is relatively low compared to a predetermined standard.

This allows the information processing system, etc., to provide appropriate incentives for vehicles that are used in a manner that results in a low occurrence or frequency of events in which a relatively large force is applied.

Although the embodiments have been described in detail above, the present disclosure is not limited to such specific embodiments, and various modifications and variations are possible within the scope of the gist of the invention as described in the claims.

Reference Signs List 1 Information processing system 10 Vehicle 12 Sensor 14 Information processing device 16 Communication device 20 Portable terminal 30 Server device 31 External interface 31A Recording medium 32 Auxiliary storage device 33 Memory device 34 CPU
35 High-speed arithmetic unit 36 Communication interface 37 Input device 38 Output device 141 Sensor data acquisition unit 142 Event determination unit 143 Transmission unit 201 Event data acquisition unit 202 Transmission unit 203 Notification unit 301 Event data acquisition unit 302 Event data storage unit 303 Notification determination unit 304 Notification unit 305 Warranty period update unit 306 Insurance fee update unit U User

Claims (15)

an acquisition unit that acquires information representing forces acting on a vehicle;
a notification unit that notifies a user about use of the vehicle based on the information acquired by the acquisition unit.
Information processing system. The notification regarding the use of the vehicle by the user includes at least one of a notification regarding the possibility of damage or deterioration of the vehicle due to the use of the vehicle, a notification regarding maintenance due to the use of the vehicle, and a notification regarding the method of using the vehicle.
The information processing system according to claim 1 . The notification unit notifies the user when a degree of the force acting on the vehicle is relatively high with respect to a predetermined standard.
3. The information processing system according to claim 1 or 2. The notification unit notifies the user in accordance with a change in a direction or a time series of a force acting on the vehicle.
The information processing system according to claim 3 . The notification unit varies the content of the notification to the user depending on a trend represented by a direction or a time-series change of the force acting on the vehicle.
5. The information processing system according to claim 4. an estimation unit that estimates a cause of a force acting on the vehicle based on a tendency represented by a direction or a time-series change of the force acting on the vehicle;
The notification unit notifies a user based on the estimation result of the estimation unit.
6. The information processing system according to claim 5. a detection unit that detects an occurrence of a predetermined event that indicates a state in which a force acting on the vehicle is large relative to a predetermined standard, based on the information acquired by the acquisition unit;
the notification unit notifies the user based on a history of the predetermined event detected by the detection unit.
3. The information processing system according to claim 1 or 2. the notification unit notifies the user when a cumulative value representing a degree of force acting on the vehicle for the history of the predetermined event is relatively high with respect to a predetermined standard.
The information processing system according to claim 7. the notification unit notifies the user when an occurrence frequency of the predetermined event is relatively high with respect to a predetermined criterion.
The information processing system according to claim 7. There are a plurality of types of the predetermined event,
the notification unit varies content of the notification to the user depending on a type of the predetermined event included in the history of the predetermined event.
The information processing system according to claim 7. a processing unit that performs processing to reflect a tendency regarding the degree of force acting on the vehicle in a warranty period or insurance premium of the vehicle based on the information acquired by the acquisition unit,
3. The information processing system according to claim 1 or 2. The processing unit extends a warranty period of the vehicle or reduces an insurance premium when a frequency or number of occurrences of a state in which a degree of force acting on the vehicle is relatively high with respect to a predetermined standard is relatively low with respect to a predetermined standard.
The information processing system according to claim 11. an acquisition unit that acquires information representing forces acting on a vehicle;
a notification unit that notifies a user about use of the vehicle based on the information acquired by the acquisition unit.
Information processing device. an acquisition step in which an information processing device acquires information representing a force acting on the vehicle;
a notification step of the information processing device notifying a user about use of the vehicle based on the information acquired in the acquisition step,
Information processing methods. In the information processing device,
acquiring information representative of forces acting on the vehicle;
a notification step of notifying a user about use of the vehicle based on the information acquired in the acquisition step.
program.

Images