Vehicle-service development support device, service provision device, vehicle-service development support method, and vehicle-service development support program

Abstract

This vehicle-service development support device comprises: an acquisition unit that acquires data on a vehicle; a plurality of detection units that, on the basis of the data acquired by the acquisition unit, perform detection processing for detecting a plurality of states of a passenger of the vehicle, the plurality of detection units providing notification about an event on the basis of the detection result in the detection processing; and an output unit that performs selection processing for selecting one or more of the detection units from among the plurality of detection units and outputs information about the event on the basis of the detection result of the selected detection unit.

Description

Vehicle service development support device, service providing device, vehicle service development support method, and vehicle service development support program

[0001] This application claims priority based on Japanese Patent Application No. 2024-29518, filed February 29, 2024, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Patent Literature 1 (JP 2014-534487 A) discloses the following system: That is, the system is for providing an infrastructure platform in a smart space environment that facilitates quick and easy development, deployment, and management of sensor-driven applications, and includes: (a) a set of infrastructure services integrated into the infrastructure platform configured to acquire, store, and analyze sensor data received from multiple sensor devices; (b) a plurality of application program interfaces (APIs), programming language-specific libraries, and software development kits (SDKs) provided to application developers who use the infrastructure services for development, testing, deployment, and management of multiple sensor-based applications; (c) a presentation module including a plurality of web-based portals configured to monitor, manage, and control the infrastructure services, developed applications, and software and hardware infrastructure; and (d) a set of infrastructure applications configured to transmit the sensor data to the platform or receive the sensor data from the platform.

[0003] Special Publication No. 2014-534487

[0004] The vehicle service development support device disclosed herein includes an acquisition unit that acquires data related to a vehicle, and a plurality of detection units that perform detection processing to detect a plurality of states related to occupants of the vehicle based on the data acquired by the acquisition unit, the plurality of detection units providing notification regarding an event based on the detection results of the detection processing, and an output unit that performs selection processing to select one or more detection units from the plurality of detection units and outputs information indicating the occurrence of the event based on the detection results of the selected detection units.

[0005] One aspect of the present disclosure can be realized not only as a vehicle service development support device equipped with such a characteristic processing unit, but also as a semiconductor integrated circuit that realizes part or all of the vehicle service development support device, or as a system that includes the vehicle service development support device.

[0006] FIG. 1 is a diagram illustrating an example of the configuration of a vehicle service development support system according to an embodiment of the present disclosure. FIG. 2 is a diagram illustrating an example of the configuration of an in-vehicle device according to an embodiment of the present disclosure. FIG. 3 is a diagram illustrating an example of the configuration of a server according to an embodiment of the present disclosure. FIG. 4 is a diagram illustrating an example of the configuration of a fleet management device according to an embodiment of the present disclosure. FIG. 5 is a diagram illustrating an example of an event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 6 is a diagram illustrating another example of the event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 7 is a diagram illustrating an example of an event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 8 is a diagram illustrating another example of the event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 9 is a diagram illustrating another example of the event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 10 is a diagram illustrating another example of the event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 11 is a diagram illustrating another example of the event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 12 is a diagram illustrating another example of the event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 13 is a diagram showing another example of an event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 14 is a diagram showing another example of an event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 15 is a diagram showing another example of an event selection screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 16 is a diagram showing another example of an event details screen displayed in the fleet management device according to an embodiment of the present disclosure. FIG. 17 is a flowchart defining an example of an operation procedure when a server according to an embodiment of the present disclosure performs detection processing. FIG. 18 is a flowchart defining an example of an operation procedure when a server according to an embodiment of the present disclosure performs selection processing. FIG. 19 is a diagram showing a processing sequence of an on-board device, a server, and a fleet management device in a vehicle service development support system according to an embodiment of the present disclosure.

[0007] 2. Description of the Related Art Conventionally, systems have been developed that include a management device that collects vehicle data related to a vehicle from the vehicle.

[0008] [Problem to be Solved by the Present Disclosure] In recent years, users such as business operators who manage vehicle operations have been required to provide passenger-related services such as understanding the state of passengers, such as fatigue level, while the vehicle is traveling in real time, visualizing the state, and formulating operation plans based on the state. When a user develops such a service using vehicle data collected from the vehicle, it takes time to format the vehicle data and develop the necessary functions.

[0009] The present disclosure has been made to solve the above-mentioned problems, and its purpose is to provide a vehicle service development support device, a service providing device, a vehicle service development support method, and a vehicle service development support program that can easily provide services related to vehicle occupants.

[0010] Effect of the Present Disclosure According to the present disclosure, services related to vehicle passengers can be easily provided.

[0011] [Description of Embodiments of the Present Disclosure] First, the contents of the embodiments of the present disclosure will be listed and described. (1) A vehicle service development support device according to an embodiment of the present disclosure includes an acquisition unit that acquires data related to a vehicle, a plurality of detection units that perform detection processing to detect each of a plurality of states related to an occupant of the vehicle based on the data acquired by the acquisition unit, the plurality of detection units that perform notification related to an event based on detection results of the detection processing, and an output unit that performs selection processing to select one or more of the detection units from the plurality of detection units and output information related to the event based on the detection results of the selected detection units.

[0012] With this configuration, it is possible to output information about an event corresponding to a detection unit selected from a plurality of detection units that provide event-related notifications, eliminating the need for the user to perform tasks such as processing vehicle-related data in order to provide passenger-related services, and allowing the vehicle service development support device to provide desired services according to the selection of a detection unit, thereby easily providing services related to vehicle passengers.

[0013] (2) In the above (1), the vehicle service development support device may further include a reception unit that receives a selection operation to select one or more detection units from the plurality of detection units, and the output unit may perform the selection process in accordance with the selection operation received by the reception unit.

[0014] With this configuration, it is possible to output information about an event desired by the user, for example.

[0015] (3) In (1) or (2) above, the acquisition unit may acquire the data over multiple days, and at least one of the multiple detection units may perform the detection process based on the data over multiple days acquired by the acquisition unit.

[0016] This configuration makes it possible to detect the status of a passenger over multiple days, thereby obtaining more diverse detection results.

[0017] (4) In the above (3), the plurality of detection units may include a detection unit that notifies an evaluation result regarding a driving state of the occupant in the vehicle as the event.

[0018] With this configuration, the user can check an evaluation of the passenger's driving based on the detection results of the passenger's condition over multiple days, and can therefore determine, for example, the riskiness of the passenger's driving.

[0019] (5) In any of (1) to (4) above, the plurality of detection units may include at least one of a detection unit that notifies an evaluation result regarding the driving posture of the occupant as the event, a detection unit that notifies an evaluation result regarding the fatigue level of the occupant while driving the vehicle as the event, and a detection unit that notifies an evaluation result regarding the danger of driving by the occupant as the event.

[0020] For example, when evaluating the driving state of a passenger, such as evaluating the driving posture of the passenger, evaluating the passenger's fatigue level while driving, and evaluating the risk of driving by the passenger, expertise and academic knowledge are required. As described above, by providing various detection units that detect the driving state of a passenger based on data related to the vehicle and perform an evaluation of the driving state, users can develop specialized services without requiring the users to have the expertise and academic knowledge to perform the evaluation.

[0021] (6) In any one of (1) to (5) above, the output unit may further output the detection result corresponding to the event notified by the selected detection unit.

[0022] With this configuration, for example, it is possible to grasp in more detail the condition of the passenger that caused the event to occur.

[0023] (7) In the above (6), the vehicle service development support device may further include a reception unit that receives a specification operation that specifies conditions for the range of the data to be used in the detection process, and the output unit may further output the detection result based on the data that satisfies the conditions specified in the specification operation received by the reception unit.

[0024] With this configuration, it is possible to output detection results based on data within a range that meets the user's needs, for example, thereby obtaining information that is useful for service development.

[0025] (8) In the above (6) or (7), the acquisition unit may acquire the data in a time series, and each of the detection units may perform the detection process based on the time series data acquired by the acquisition unit, and the output unit may further output information indicating the time series change of the detection result corresponding to the event notified by the selected detection unit.

[0026] With this configuration, it is possible to output the time change in the detection results of the passenger's condition over a period desired by the user, for example, thereby obtaining information that is useful for service development.

[0027] (9) A service providing device according to an embodiment of the present disclosure includes a communication unit that receives information regarding the event from the vehicle service development support device described in any one of (1) to (8) above, and a processing unit that performs processing to provide a service related to the passenger based on the information regarding the event received by the communication unit.

[0028] With this configuration, it is possible to output information about an event corresponding to a detection unit selected from a plurality of detection units that provide event-related notifications, eliminating the need for the user to perform tasks such as processing vehicle-related data in order to provide passenger-related services, and allowing the vehicle service development support device to provide desired services according to the selection of a detection unit, thereby easily providing services related to vehicle passengers.

[0029] (10) A vehicle service development support method according to an embodiment of the present disclosure is a vehicle service development support method in a vehicle service development support device, which includes a step of acquiring data related to a vehicle, wherein the vehicle service development support device has a plurality of detection units that perform detection processing to detect a plurality of states related to occupants of the vehicle based on the acquired data, and the plurality of detection units that provide notification regarding an event based on the detection results of the detection processing, and the vehicle service development support method further includes a step of performing a selection processing to select one or more detection units from the plurality of detection units, and outputting information related to the event based on the detection results of the selected detection units.

[0030] This method makes it possible to output information about an event corresponding to a detection unit selected from a plurality of detection units that provide event-related notifications, thereby eliminating the need for the user to perform tasks such as processing vehicle-related data in order to provide passenger-related services, and enabling the vehicle service development support device to provide desired services in accordance with the selection of a detection unit, thereby making it possible to easily provide services related to vehicle passengers.

[0031] (11) A vehicle service development support program according to an embodiment of the present disclosure is a vehicle service development support program used in a vehicle service development support device, and is a program for causing a computer to function as an acquisition unit that acquires data related to a vehicle, a plurality of detection units that perform detection processing to detect a plurality of states related to the vehicle's occupants based on the data acquired by the acquisition unit, the plurality of detection units that provide notifications related to events based on the detection results of the detection processing, and an output unit that performs selection processing to select one or more detection units from the plurality of detection units and output information related to the event based on the detection results of the selected detection units.

[0032] With this configuration, it is possible to output information about an event corresponding to a detection unit selected from a plurality of detection units that provide event-related notifications, eliminating the need for the user to perform tasks such as processing vehicle-related data in order to provide passenger-related services, and allowing the vehicle service development support device to provide desired services according to the selection of a detection unit, thereby easily providing services related to vehicle passengers.

[0033] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be combined in any manner.

[0034] [Vehicle Service Development Support System] Fig. 1 is a diagram illustrating an example of the configuration of a vehicle service development support system according to an embodiment of the present disclosure. Referring to Fig. 1, the vehicle service development support system 501 includes a server 101, one or more on-board devices 201, and an operation management device 301. The server 101 and the on-board devices 201 can transmit and receive information via an external network 151 such as the Internet, for example. The on-board device 201 is mounted on a vehicle 1. The server 101 is an example of a vehicle service development support device. The operation management device 301 is an example of a service providing device.

[0035] The server 101 and the traffic management device 301 are used, for example, by a business operator or an individual. The users of the server 101 and the traffic management device 301 may be the same or different. The server 101 and the traffic management device 301 can transmit and receive information via, for example, an external network 151. For example, if the user of the server 101 and the traffic management device 301 is the same, the output contents of the traffic management device 301, which will be described later, may be notified from the traffic management device 301 to the business operator that manages the operation of the vehicle 1.

[0036] [On-Vehicle Device] Fig. 2 is a diagram illustrating an example of the configuration of an on-vehicle device according to an embodiment of the present disclosure. Referring to Fig. 2, the on-vehicle device 201 is connected to a plurality of on-vehicle devices 61 via, for example, a communication bus 51. The communication bus 51 is, for example, a CAN (Controller Area Network) bus that complies with the CAN standard.

[0037] The in-vehicle devices 61 include an in-vehicle ECU (Electronic Control Unit), a sensor, a navigation device, a human-machine interface, a camera, and the like.

[0038] 2, the in-vehicle device 201 is connected to in-vehicle devices 61A and 61B, which are in-vehicle devices 61, via a communication bus 51A, which is the communication bus 51. The in-vehicle device 201 is also connected to in-vehicle devices 61C and 61D, which are in-vehicle devices 61, via a communication bus 51B, which is the communication bus 51.

[0039] The in-vehicle device 201 and the in-vehicle equipment 61 exchange information using, for example, a CAN frame that conforms to the CAN standard.

[0040] For example, each in-vehicle device 61 transmits to the in-vehicle device 201 a CAN frame including various information described below, such as information to assist the automatic driving performed by the vehicle 1 and information used for entertainment, and a CAN-ID (Identifier) ​​indicating the type of data, etc.

[0041] In the example shown in Fig. 2, the in-vehicle device 61A is an accelerator sensor. The in-vehicle device 61B is a brake sensor. The in-vehicle device 61C is a vehicle speed sensor. The in-vehicle device 61D is a Global Navigation Satellite Systems (GNSS) receiver. Hereinafter, the in-vehicle devices 61A, 61B, 61C, and 61D will also be referred to as the accelerator sensor 61A, the brake sensor 61C, the vehicle speed sensor 61C, and the GNSS receiver 61D, respectively.

[0042] The accelerator sensor 61A measures the accelerator opening of the vehicle 1 (hereinafter also referred to as "accelerator opening"), for example, periodically, and transmits accelerator information indicating the measurement result and the measurement date and time ta to the in-vehicle device 201.

[0043] The brake sensor 61B measures the brake opening of the vehicle 1 (hereinafter also referred to as "brake opening"), for example, periodically, and transmits brake information indicating the measurement result and the measurement date and time tb to the in-vehicle device 201.

[0044] The vehicle speed sensor 61C measures the speed of the vehicle 1, for example, periodically, and transmits to the in-vehicle device 201 vehicle speed information indicating the measurement result and the measurement date and time tc.

[0045] The GNSS receiver 61D receives GNSS signals, for example, periodically, from one or more satellites, and, based on the received GNSS signals, detects the position of the vehicle 1. The position of the vehicle 1 is indicated by, for example, latitude and longitude.

[0046] The GNSS receiver 61D, for example, periodically transmits the detection result of the position of the vehicle 1 and position information indicating the date and time td when the position was detected to the in-vehicle device 201. Here, the GNSS receiver 61D detects the position of the vehicle 1 at the same timing as the vehicle speed sensor 61C, for example, and transmits the position information to the in-vehicle device 201.

[0047] The in-vehicle device 201 includes an in-vehicle communication unit 11, a pressure information acquisition unit 12, a biological information acquisition unit 13, an external communication unit 14, and a storage unit 15. Some or all of the in-vehicle communication unit 11, the pressure information acquisition unit 12, the biological information acquisition unit 13, and the external communication unit 14 are realized by, for example, a processing circuit including one or more processors. The storage unit 15 is, for example, a non-volatile memory included in the processing circuit.

[0048] (In-vehicle communication unit) The in-vehicle communication unit 11 acquires accelerator information, brake information, vehicle speed information, and position information. More specifically, for example, when the in-vehicle communication unit 11 receives accelerator information from the accelerator sensor 61A, the in-vehicle communication unit 11 stores the received accelerator information in the storage unit 15.

[0049] Furthermore, for example, when the in-vehicle communication unit 11 receives braking information from the brake sensor 61B, the in-vehicle communication unit 11 stores the received braking information in the storage unit 15 .

[0050] Furthermore, for example, when the in-vehicle communication unit 11 receives vehicle speed information from the vehicle speed sensor 61C, the in-vehicle communication unit 11 stores the received vehicle speed information in the storage unit 15 .

[0051] Furthermore, for example, when the in-vehicle communication unit 11 receives position information from the GNSS receiver 61D, the in-vehicle communication unit 11 stores the received position information in the storage unit 15 .

[0052] Note that the in-vehicle device 201 and the in-vehicle equipment 61 may be configured to perform communication in accordance with a communication protocol such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media Oriented System Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extension Peripheral Interface) (registered trademark), instead of or in addition to communication in accordance with the CAN standard.

[0053] (Pressure Information Acquisition Unit) The pressure information acquisition unit 12 acquires pressure information indicating the pressure applied by a passenger to the seat surface of the seat of the vehicle 1. In this embodiment, for example, the pressure information acquisition unit 12 acquires, as pressure information, information indicating the pressure applied by the driver to the seat surface of the driver's seat of the vehicle 1 (hereinafter also referred to as "seat pressure P").

[0054] More specifically, for example, a plurality of pressure sensors 62 are provided on the seat surface of the driver's seat of the vehicle 1 .

[0055] The in-vehicle device 201 performs wireless communication with each pressure sensor 62 according to a standard such as Bluetooth.

[0056] Each pressure sensor 62 transmits pressure information indicating the measurement result, the measurement date and time te, and its own ID (Identifier) ​​(hereinafter also referred to as "sensor ID") to the in-vehicle device 201. Each pressure sensor 62 measures the pressure and transmits the pressure information, for example, periodically. Here, each pressure sensor 62 measures the seat pressure P at the same measurement date and time te, for example, and transmits the pressure information to the in-vehicle device 201 at the same transmission date and time. Each pressure sensor 62 measures the seat pressure P and transmits the pressure information, for example, every minute.

[0057] In the in-vehicle device 201 , when the pressure information acquisition unit 12 receives pressure information from each pressure sensor 62 , the pressure information acquisition unit 12 stores the received multiple pieces of pressure information in the storage unit 15 .

[0058] (Biometric Information Acquisition Unit) The biometric information acquisition unit 13 acquires biometric information of an occupant of the vehicle 1. The biometric information includes the occupant's body temperature, heart rate, pulse rate, etc. In the present embodiment, for example, the biometric information acquisition unit 13 acquires biometric information of the driver of the vehicle 1.

[0059] More specifically, for example, the biometric information acquisition unit 13 performs wireless communication with a vital sensor 63 worn by the driver in accordance with a standard such as Bluetooth.

[0060] The vital sensor 63 is a sensor that detects the driver's biological information. Specifically, the vital sensor 63 is, for example, a wearable terminal such as a smart watch. In the present embodiment, for example, the vital sensor 63 measures the body temperature of the vehicle 1. The vital sensor 63 then transmits biological information indicating the measurement value and the measurement date and time tf to the in-vehicle device 201. The vital sensor 63 measures the body temperature and transmits the biological information, for example, periodically.

[0061] In the in-vehicle device 201 , when the biological information acquisition unit 13 receives the biological information from the vital sensor 63 , the biological information acquisition unit 13 stores the received biological information in the storage unit 15 .

[0062] (External communication unit) The external communication unit 14 performs a transmission process of transmitting the accelerator information, brake information, and vehicle speed information acquired by the internal communication unit 11, the pressure information acquired by the pressure information acquisition unit 12, and the biometric information acquired by the biometric information acquisition unit 13 to the server 101.

[0063] More specifically, the exterior-vehicle communication unit 14 communicates with the server 101 via the external network 151 by wirelessly communicating with a device such as a wireless base station device (not shown) in accordance with a communication method such as Wi-Fi (registered trademark), LTE (Long Term Evolution) (registered trademark), or 5G. Note that the exterior-vehicle communication unit 14 is not limited to a configuration in which it communicates with the server 101 via the wireless base station device and the external network 151, and may be configured to communicate with the server 101 via a wired line. Furthermore, the exterior-vehicle communication unit 14 may be configured to communicate with the server 101 further via another in-vehicle device.

[0064] For example, the storage unit 15 stores driver identification information (hereinafter also referred to as "driver ID") for identifying the driver of the vehicle 1. The driver ID is an ID unique to each driver.

[0065] For example, when processing timing T1 of the transmission process arrives, exterior communication unit 14 creates a vehicle data group including at least one of accelerator information, brake information, vehicle speed information, position information, pressure information, and biological information stored in storage unit 15. Then, exterior communication unit 14 includes the driver ID in the created vehicle data group and transmits it to server 101. The cycle of processing timing T1 is, for example, 10 minutes.

[0066] [Server] Fig. 3 is a diagram illustrating an example of a server configuration according to an embodiment of the present disclosure. Referring to Fig. 3, the server 101 includes a communication unit 31, a plurality of event detection units 32, a physical condition detection unit 33, an output unit 34, and a storage unit 35. Some or all of the communication unit 31, the plurality of event detection units 32, the physical condition detection unit 33, and the output unit 34 are implemented, for example, by a processing circuit including one or more processors. The storage unit 35 is, for example, a non-volatile memory included in the processing circuit. The communication unit 31 is an example of an acquisition unit and an example of a reception unit.

[0067] (Communication Unit) The communication unit 31 acquires vehicle data related to the vehicle 1. More specifically, for example, the communication unit 31 acquires time-series vehicle data.

[0068] The communication unit 31 acquires accelerator information, brake information, vehicle speed information, pressure information, and biological information contained in the vehicle data group transmitted from the in-vehicle device 201 as time-series vehicle data.

[0069] For example, every time the communication unit 31 receives a group of vehicle data from the in-vehicle device 201 via the external network 151, the communication unit 31 stores the received group of vehicle data in the storage unit 35, for example, for each driver ID.

[0070] (Detection Unit) The plurality of event detection units 32 perform detection processing to detect a plurality of states related to the occupants of the vehicle 1, based on the vehicle data acquired by the communication unit 31. Below, an example will be described in which each event detection unit 32 detects a state related to the driver of the vehicle 1 in the detection processing.

[0071] For example, each event detection unit 32 performs detection processing based on time-series vehicle data acquired by the communication unit 31 .

[0072] In the example shown in FIG. 3, the server 101 includes a plurality of event detection units 32, namely, event detection units 32A, 32B, and 32C.

[0073] For example, when processing timing T2, for example, a predetermined time in a day, arrives, each event detection unit 32 acquires multiple groups of vehicle data that were created by the in-vehicle device 201 for each processing timing T1 during the period from 24 hours before processing timing T2 to processing timing T2 and that were stored in the memory unit 35 by the communication unit 31.

[0074] <Detection Process D1> The event detection unit 32A performs a detection process D1 related to the driver's driving posture based on the pressure information acquired by the communication unit 31.

[0075] More specifically, for example, when the event detection unit 32A acquires multiple vehicle data groups for a certain day from the memory unit 35, it performs detection processing D1 for each vehicle data group using multiple pieces of pressure information contained in the vehicle data group.

[0076] Specifically, for example, the event detection unit 32A calculates the driver's center of gravity position at the measurement date and time te based on multiple pressure information items included in a single vehicle data group that have the same measurement date and time te.

[0077] For example, the storage unit 35 stores a sensor position list indicating the correspondence between the sensor ID of the pressure sensor 62 shown in FIG. 2 and the position of the pressure sensor 62 on the seat surface of the driver's seat.

[0078] The event detection unit 32A refers to the sensor position list in the storage unit 15 to identify the position of the pressure sensor 62 corresponding to the sensor ID indicated by each piece of pressure information at a certain measurement date and time te.

[0079] Then, based on the measurement value indicated by each piece of pressure information and the position of each identified pressure sensor 62, the event detection unit 32A calculates the position of the center of gravity of the driver on the seat at the corresponding measurement date and time te.

[0080] For example, the storage unit 35 stores a reference position G of the center of gravity. The reference position G indicates the center of gravity position in an ideal driving posture, for example.

[0081] After calculating the center-of-gravity position at a certain measurement date and time te, the event detection unit 32A calculates the amount of change from the center-of-gravity position in the ideal driving posture (hereinafter also referred to as "posture change amount") by comparing the calculated center-of-gravity position with the reference position G. Then, the event detection unit 32A detects the driver's driving posture based on the calculated posture change amount.

[0082] For example, the event detection unit 32A determines whether the driver's driving posture is "forward leaning," "slightly forward leaning," "ideal," "slightly backward leaning," or "backward leaning," depending on the calculated posture change amount.

[0083] For example, if the value of the posture change amount is "zero," the event detection unit 32A determines that the driver's driving posture is "ideal." If the value of the posture change amount is "+1," the event detection unit 32A determines that the driver's driving posture is "slightly leaning forward." If the value of the posture change amount is "+2" or greater, the event detection unit 32A determines that the driver's driving posture is "leaning forward." If the value of the posture change amount is "-1," the event detection unit 32A determines that the driver's driving posture is "slightly leaning backward." If the value of the posture change amount is "-2" or greater, the event detection unit 32A determines that the driver's driving posture is "leaning backward."

[0084] Then, the event detection unit 32A stores in the storage unit 35 detection result information K1 indicating the calculated posture change amount, the driving posture corresponding to the posture change amount, the measurement date and time te, and the driver ID.

[0085] <Detection process D2> The event detection unit 32B performs detection process D2 regarding the number of times the driver has shifted in his / her seat, i.e., the driver's seat (hereinafter also referred to as the "number of times of shifting"), based on the pressure information acquired by the communication unit 31.

[0086] More specifically, for example, when the event detection unit 32B acquires multiple vehicle data groups for a certain day from the memory unit 35, it performs detection processing D2 for each vehicle data group using multiple pieces of pressure information contained in the vehicle data group.

[0087] Specifically, for example, the event detection unit 32B calculates the number of times the driver shifts their seat per minute at a certain measurement date and time te for each driver ID based on multiple pressure information included in a single vehicle data group that have the same measurement date and time te.

[0088] Then, the event detection unit 32B stores in the storage unit 35 detection result information K2 indicating the calculation result of the number of times the driver has adjusted his / her seat, the measurement date and time te corresponding to the calculation result, and the driver ID.

[0089] <Detection Process D3> The event detection unit 32C performs a detection process D3 relating to the riskiness of the driver's driving based on the accelerator information, brake information, and vehicle speed information acquired by the communication unit 31 over multiple days.

[0090] More specifically, for example, the event detection unit 32C performs the detection process D3 for each driver ID using a group of multiple vehicle data for a certain day acquired from the storage unit 35.

[0091] Specifically, for example, when the event detection unit 32C acquires multiple vehicle data groups for a certain day from the memory unit 35, it counts the number N1 of vehicle data groups among the multiple vehicle data groups that include accelerator information indicating an accelerator opening degree that is greater than or equal to a predetermined threshold value Th1 for each driver ID.

[0092] Also, for example, when the event detection unit 32C acquires multiple vehicle data groups for a certain day from the memory unit 35, it counts, for each driver ID, the number N2 of vehicle data groups that include brake information indicating a brake opening degree that is greater than or equal to a predetermined threshold value Th2 among the multiple vehicle data groups.

[0093] For example, the storage unit 35 stores a road table that indicates the correspondence between position coordinates indicating the location of a road and speed limits.

[0094] When the event detection unit 32C acquires multiple vehicle data groups for a certain day from the memory unit 35, it refers to the road table in the memory unit 35 and, for each acquired vehicle data group, checks the speed limit (hereinafter also referred to as the "corresponding speed limit") corresponding to the position of vehicle 1 indicated by the location information included in that vehicle data group.

[0095] Then, the event detection unit 32C counts, for each driver ID, the number N3 of vehicle data groups that include vehicle speed information indicating a vehicle speed greater than the corresponding speed limit, among the multiple vehicle data groups for a certain day obtained from the memory unit 35.

[0096] The event detection unit 32C stores in the memory unit 35 detection result information K3 indicating the counted numbers N1, N2, and N3, the date on which the detection process D3 was performed, and the driver ID included in the vehicle data group corresponding to the numbers N1, N2, and N3.

[0097] (Physical condition detection unit) For example, the physical condition detection unit 33 performs a detection process D4 to detect the physical condition of a passenger in the vehicle 1 based on the biological information acquired by the communication unit 31. Below, an example will be described in which the physical condition detection unit 33 detects the physical condition of the driver of the vehicle 1 in the detection process D4.

[0098] More specifically, for example, when processing timing T2 arrives, the physical condition detection unit 33, like the event detection unit 32, acquires from the storage unit 35 a plurality of vehicle data groups that have been created by the in-vehicle device 201 for each processing timing T1 during the period from 24 hours before processing timing T2 to processing timing T2 and that have been stored in the storage unit 35 by the communication unit 31. Then, the physical condition detection unit 33 performs detection process D4 for each driver ID using the plurality of vehicle data groups.

[0099] Specifically, for example, when the physical condition detection unit 33 acquires multiple vehicle data groups for a certain day from the memory unit 35, it counts the number N4 of vehicle data groups among the multiple vehicle data groups that contain biological information indicating a body temperature that is equal to or higher than a predetermined threshold Th4 for each driver ID.

[0100] For example, the physical condition detection unit 33 determines whether the driver's physical condition is "good," "fairly good," "average," "fairly poor," or "poor" depending on the value of the counted number N4.

[0101] Then, the physical condition detection unit 33 stores in the storage unit 35 detection result information K4 indicating the identified physical condition, the date on which the detection process D4 was performed, and the driver ID corresponding to the number N4.

[0102] (Event Information) Each event detection unit 32 provides notification regarding an event based on the detection result in the detection process.

[0103] For example, each event detection unit 32 notifies, as an event, the result of evaluation regarding the driving state of the occupant of the vehicle 1. More specifically, for example, event detection unit 32A notifies, as event L1, the result of evaluation regarding the driving posture of the occupant. Event detection unit 32B notifies, as event L2, the result of evaluation regarding the fatigue level of the occupant while driving the vehicle 1. Event detection unit 32C notifies, as event L3, the result of evaluation regarding the risk of driving by the occupant.

[0104] Specifically, for example, event L1 is the detection result of the driver's driving posture in detection process D1 by event detection unit 32A, event L2 is the detection result of the number of times the driver shifts his / her seat in detection process D2 by event detection unit 32B, and event L3 is the detection result of the risk of the driver's driving in detection process D3 by event detection unit 31C.

[0105] For example, the fleet management device 301 transmits request information requesting event information related to an event to the server 101 in accordance with an operation by a user.

[0106] In the server 101, when the communication unit 31 receives request information from the traffic management device 301, it creates screen information M1 that indicates the types of events L1, L2, and L3 that correspond to the detection result information K1, K2, and K3, respectively, stored in the storage unit 35. Then, the communication unit 31 transmits the created screen information M1 to the traffic management device 301.

[0107] 4 is a diagram illustrating an example of a configuration of a traffic management device according to an embodiment of the present disclosure. Referring to FIG. 4, traffic management device 301 includes a communication unit 41 and a processing unit 42. One or both of communication unit 31 and processing unit 42 are realized, for example, by a processing circuit including one or more processors.

[0108] Referring to FIG. 4, for example, communication unit 41 receives event information relating to an event from server 101.

[0109] Specifically, for example, the communication unit 41 receives, as event information, screen information M1 transmitted from the server 101. Upon receiving the screen information M1 from the server 101, the communication unit 41 outputs the received screen information M1 to the processing unit 42.

[0110] For example, the processing unit 42 performs processing to provide services related to the passengers of the vehicle 1 based on the screen information M1 received by the communication unit 41 .

[0111] Specifically, for example, when the processing unit 42 receives screen information M1 from the communication unit 41, it draws an event selection screen G1 on a web browser displayed on the display unit of its own operation management device 301 based on the screen information M1.

[0112] FIG. 5 is a diagram illustrating an example of an event selection screen displayed on the traffic management device according to the embodiment of the present disclosure.

[0113] 5, the event selection screen G1 includes areas A1, A2, and A3. In area A1, events based on the detection results of the detection processes performed by the event detection units 32 in the server 101 are displayed.

[0114] In the example shown in Figure 5, in area A1, "Posture monitoring" indicating event L1 corresponding to event detection unit 32A shown in Figure 3, "Sitting back detection" indicating event L2 corresponding to event detection unit 32B, and "Dangerous characteristic detection" indicating event L3 corresponding to event detection unit 32C are displayed.

[0115] Area A1 includes check boxes Ch1, Ch2, and Ch3 corresponding to "posture monitoring," "seat adjustment detection," and "dangerous characteristic detection," respectively.

[0116] For example, area A2 displays the name of data to be compared with the vehicle data (hereinafter also referred to as "comparison data") or the display conditions for the detection results corresponding to each event detection unit 32. Area A3 displays the name of the vehicle data acquired by the server 101.

[0117] 5, the name of the comparison data displayed in area A2 is "Physical Condition," which indicates the driver's biological information. The display condition of the detection results displayed in area A2 is "Aging," which indicates that the detection results are to be displayed monthly.

[0118] Area A2 includes check boxes Ch4 and Ch5 corresponding to "physical condition" and "aging," respectively.

[0119] In addition, in area A2, as a display condition for the detection results, in addition to or instead of "Age", which indicates that the detection results are displayed monthly, "Driving Area", which indicates that the driving area of ​​vehicle 1 is displayed, may be displayed.

[0120] In the example shown in Figure 5, the names of the vehicle data displayed in area A3 are "seat pressure" indicating pressure information, "accelerator opening" indicating accelerator information, "brake opening" indicating brake information, "vehicle speed" indicating vehicle speed information, and "physical condition" indicating biometric information.

[0121] Area A3 includes check boxes Ch6, Ch7, Ch8, Ch9, and Ch10 corresponding to "seat pressure," "accelerator opening," "brake opening," "vehicle speed," and "physical condition," respectively.

[0122] For example, the event selection screen G1 further includes an input field B1 for a driver ID, an input field B2 for the start date and time of the event search period, and an input field B3 for the end date and time of the event search period.

[0123] (Selection Process) Referring back to FIG. 3, for example, the communication unit 31 accepts a selection operation for selecting one or more event detection units 32 from the plurality of event detection units 32 .

[0124] More specifically, for example, the communication unit 31 acquires operation information indicating an operation by a user on the event selection screen G1 displayed on the fleet management device 301 .

[0125] 6 is a diagram illustrating another example of an event selection screen G1 displayed in the traffic management device according to an embodiment of the present disclosure, in which a user inputs values ​​into the input fields B1, B2, and B3 and clicks the check box Ch1.

[0126] 6 , for example, suppose that a user inputs “aaa123,” “2023 / 9 / 9 10:00,” and “2023 / 9 / 9 10:10” into input fields B1, B2, and B3 of event selection screen G1, respectively, and also clicks check box Ch1. In this case, traffic management device 301 transmits operation information C1 indicating these operations to server 101.

[0127] In the server 101 , when the communication unit 31 receives the operation information C1 from the traffic management device 301 , the communication unit 31 outputs the operation information C1 to the output unit 34 .

[0128] The output unit 34 performs a selection process to select one or more event detection units 32 from the plurality of event detection units 32. Then, the output unit 34 outputs event information based on the detection results of the selected event detection units 32.

[0129] More specifically, for example, the output unit 34 performs a selection process in accordance with a selection operation received by the communication unit 31 .

[0130] Specifically, for example, when the output unit 34 receives operation information C1 from the communication unit 31, it acquires from the memory unit 35, based on the operation information C1, detection result information K1 (hereinafter also referred to as "selected detection information K11") indicating the "posture monitoring" selected by the user from among the multiple detection result information stored in the memory unit 35, i.e., the detection result of the event detection unit 32A, which corresponds to the driver with driver ID "aaa123" during the period P1 from 10:00 on September 9, 2023 to 10:10 on September 9, 2023, as input by the user.

[0131] For example, in addition to the event information, the output unit 34 also outputs a detection result corresponding to the event notified by the selected event detection unit 32 .

[0132] Specifically, for example, when the output unit 34 acquires the selection detection information K11 from the storage unit 35, the output unit 34 creates screen information M2 that shows the event details screen G21 using the acquired selection detection information K11. Then, the output unit 34 transmits the created screen information M2 to the fleet management device 301 via the communication unit 31.

[0133] When the processing unit 42 in the operation management device 301 receives the screen information M2 from the server 101 via the communication unit 41, it draws an event details screen G21, for example, on a web browser displayed on the display unit of its own operation management device 301 based on the screen information M2.

[0134] FIG. 7 is a diagram illustrating an example of an event details screen displayed on the traffic management device according to the embodiment of the present disclosure.

[0135] Referring to FIG. 7, the posture state of the driver with driver ID "aaa123" is shown for each minute during period P1.

[0136] In the example shown in Figure 7, the driver's driving posture is "ideal" from 10:00 to 10:04 in period P1. The driver's driving posture is "slightly leaning backward" from 10:05 to 10:07 in period P1. The driver's driving posture is "leaning forward" from 10:08 to 10:10 in period P1.

[0137] 8 is a diagram illustrating another example of an event selection screen G1 displayed in the traffic management device according to an embodiment of the present disclosure, in which a user inputs values ​​into the input fields B1, B2, and B3 and clicks the check box Ch2.

[0138] 8 , for example, suppose that the user inputs “aaa123,” “2023 / 9 / 9 10:00,” and “2023 / 9 / 9 10:10” into input fields B1, B2, and B3 of the event selection screen G1, respectively, and also clicks check box Ch2. In this case, the traffic management device 301 transmits operation information C2 indicating these operations to the server 101.

[0139] In the server 101 , when the communication unit 31 receives the operation information C2 from the traffic management device 301 , the communication unit 31 outputs the operation information C2 to the output unit 34 .

[0140] For example, when the output unit 34 receives operation information C2 from the communication unit 31, it acquires, based on the operation information C2, from the memory unit 35 detection result information K2 (hereinafter also referred to as "selected detection information K12") indicating the "seat adjustment detection" selected by the user from among the multiple detection result information stored in the memory unit 35, i.e., the detection result of the event detection unit 32B, which corresponds to the driver with driver ID "aaa123" during the period P1 input by the user.

[0141] For example, when the output unit 34 acquires the selection detection information K12 from the storage unit 35, the output unit 34 uses the selection detection information K12 to create screen information M3 that shows the event details screen G22. Then, the output unit 34 transmits the created screen information M3 to the operation management device 301 via the communication unit 31.

[0142] When the processing unit 42 in the operation management device 301 receives screen information M3 from the server 101 via the communication unit 41, it draws an event details screen G22, for example, on a web browser displayed on the display unit of its own operation management device 301, based on the screen information M3.

[0143] FIG. 9 is a diagram illustrating another example of an event details screen displayed on the traffic management device according to the embodiment of the present disclosure.

[0144] Referring to FIG. 9, the event details screen G22 shows the number of times the driver with the driver ID "aaa123" changed his / her seat for each minute during the period P1.

[0145] In the example shown in Figure 9, the number of times a person changed their seat during the period P1 from 10:00 to 10:06 is "zero." The number of times a person changed their seat during the period P1 from 10:07 is "1." The number of times a person changed their seat during the period P1 from 10:08 to 10:10 is "zero."

[0146] 10 is a diagram illustrating another example of an event selection screen G1 displayed in the traffic management device according to an embodiment of the present disclosure, in which a user inputs values ​​into the input fields B1, B2, and B3 and clicks the check boxes Ch1 and Ch2.

[0147] 10 , assume that the user inputs "aaa123," "2023 / 9 / 9 10:00," and "2023 / 9 / 9 10:10" into input fields B1, B2, and B3 of the event selection screen G1, respectively, and also clicks check boxes Ch1 and Ch2. In this case, the traffic management device 301 transmits operation information C3 indicating these operations to the server 101.

[0148] In the server 101 , when the communication unit 31 receives the operation information C3 from the traffic management device 301 , the communication unit 31 outputs the operation information C3 to the output unit 34 .

[0149] For example, when the output unit 34 receives operation information C3 from the communication unit 31, it acquires selected detection information K11 and K12 from the memory unit 35 based on the operation information C3 from among the multiple detection result information stored in the memory unit 35.

[0150] For example, when the output unit 34 acquires the selected detection information K11 and K12 from the storage unit 35, the output unit 34 creates screen information M4 that shows the event details screen G23 using the selected detection information K11 and K12. Then, the output unit 34 transmits the created screen information M4 to the operation management device 301 via the communication unit 31.

[0151] When the processing unit 42 in the operation management device 301 receives screen information M4 from the server 101 via the communication unit 41, it draws an event details screen G23, for example, on a web browser displayed on the display unit of its own operation management device 301 based on the screen information M4.

[0152] FIG. 11 is a diagram illustrating another example of an event details screen displayed in the traffic management device according to the embodiment of the present disclosure.

[0153] Referring to FIG. 11, the event details screen G23 shows the driving posture and the number of times the driver with driver ID "aaa123" rearranges his / her seat for each minute during the period P1.

[0154] In the example shown in Fig. 11, the driving posture of the driver during period P1 is the same as the driving posture on the event details screen G21 shown in Fig. 7. Also, in the example shown in Fig. 11, the number of times the driver rearranges his / her seat during period P1 is the same as the number of times the driver rearranges his / her seat on the event details screen G22 shown in Fig. 9.

[0155] 12 is a diagram illustrating another example of an event details screen G23 displayed in the traffic management device according to the embodiment of the present disclosure.

[0156] 12, the event details screen G23 displays a graph showing the driver's posture change amount and the number of times the driver adjusted his / her seat during the period P1. In the graph, the horizontal axis represents the date and time, the left vertical axis represents the posture change amount, and the right vertical axis represents the number of times the driver adjusted his / her seat.

[0157] 12, a graph Q1 showing the amount of posture change is displayed, for example, as a line graph. The amount of posture change from 10:00 to 10:04 in period P1 is "zero." The amount of posture change from 10:05 to 10:07 is "-1." The amount of posture change from 10:08 to 10:10 is "2."

[0158] 12, a graph Q2 showing the number of times the user has changed seats is displayed as a bar graph, for example. The number of times the user has changed seats shown in FIG. 12 is the same as the number of times the user has changed seats on the event details screen G22 shown in FIG.

[0159] For example, the communication unit 31 accepts a designation operation that designates the conditions for the range of vehicle data to be used in the detection process.

[0160] More specifically, for example, the communication unit 31 accepts an operation to specify the display condition for the detection results as "Aging", which is displayed in area A2 of the event selection screen G1 shown in Figure 5, i.e., an operation in which the user clicks on check box Ch5.

[0161] 13 is a diagram illustrating another example of an event selection screen displayed in the traffic management device according to an embodiment of the present disclosure. Figure 13 illustrates an event selection screen G1 when a user inputs arbitrary values ​​into input fields B1, B2, and B3 and clicks check boxes Ch3, Ch5, Ch7, and Ch9.

[0162] 13 , for example, suppose that the user inputs “aaa123,” “2022 / 9,” and “2023 / 5” into input fields B1, B2, and B3 of the event selection screen G1, respectively, and also clicks check boxes Ch3, Ch5, Ch7, and Ch9. In this case, the traffic management device 301 transmits operation information C4 indicating these operations to the server 101.

[0163] In the server 101 , when the communication unit 31 receives the operation information C4 from the traffic management device 301 , the communication unit 31 outputs the operation information C4 to the output unit 34 .

[0164] For example, the output unit 34 further outputs the detection result based on the vehicle data that satisfies the condition specified in the specifying operation received by the communication unit 31 .

[0165] More specifically, for example, when the output unit 34 receives operation information C4 from the communication unit 31, it acquires from the memory unit 35, based on the operation information C4, a plurality of detection result information K3 (hereinafter also referred to as "a plurality of selected detection information K13") indicating the "hazardous characteristic detection" selected by the user from among the plurality of detection result information stored in the memory unit 35, i.e., the detection result of the event detection unit 32C, which corresponds to the driver with driver ID "aaa123" for the period from September 2022 to May 2023 input by the user.

[0166] Then, the output unit 34 uses the acquired multiple pieces of selected detection information K13 to calculate the total value of the accelerator information and vehicle speed information selected by the user, i.e., the total value S1 of the above-mentioned numbers N1 and N3, for each month.

[0167] After calculating the monthly total value S1, the output unit 34 generates screen information M5 showing the calculation result. Then, the output unit 34 transmits the generated screen information M5 to the fleet management device 301 via the communication unit 31.

[0168] When the processing unit 42 in the operation management device 301 receives screen information M5 from the server 101 via the communication unit 41, it draws an event details screen G24, for example, on a web browser displayed on the display unit of its own operation management device 301 based on the screen information M5.

[0169] FIG. 14 is a diagram illustrating another example of an event details screen displayed in the traffic management device according to the embodiment of the present disclosure.

[0170] 14, the event details screen G24 displays a graph showing the total value S1 for each month from September 2022 to May 2023. In the graph, the horizontal axis represents the year and month, and the vertical axis represents the total value S1.

[0171] In the example shown in Figure 14, the total values ​​S1 for September, October, November, and December in 2022, and January, February, March, April, and May in 2023 are "3," "2," "1," "4," "3," "4," "6," "10," and "12," respectively.

[0172] 15 is a diagram illustrating another example of an event selection screen G1 displayed in the traffic management device according to an embodiment of the present disclosure, in which a user inputs values ​​into input fields B1, B2, and B3 and clicks check boxes Ch3, Ch4, Ch7, Ch8, Ch9, and Ch10.

[0173] 15 , for example, suppose that the user inputs “aaa123,” “2023 / 9 / 1,” and “2023 / 9 / 9” into input fields B1, B2, and B3 of event selection screen G1, respectively, and also clicks check boxes Ch3, Ch4, Ch7, Ch8, Ch9, and Ch10. In this case, the traffic management device 301 transmits operation information C5 indicating these operations to the server 101.

[0174] In the server 101 , when the communication unit 31 receives the operation information C5 from the traffic management device 301 , the communication unit 31 outputs the operation information C5 to the output unit 34 .

[0175] For example, when the output unit 34 receives operation information C5 from the communication unit 31, it acquires from the memory unit 35, based on the operation information C4, a plurality of detection result information K3 (hereinafter also referred to as "a plurality of selected detection information K23") indicating the "hazardous characteristic detection" selected by the user from the plurality of detection result information stored in the memory unit 35, i.e., the detection result of the event detection unit 32C, which corresponds to the driver with driver ID "aaa123" for the period P2 from September 1, 2022 to September 9, 2023, as input by the user.

[0176] Then, the output unit 34 uses the acquired multiple pieces of selected detection information K23 to calculate the total value of the accelerator information, brake information, and vehicle speed information selected by the user, i.e., the total value S2 of the above-mentioned numbers N1, N2, and N3, for each day.

[0177] Furthermore, for example, based on the operation information C5 received from the communication unit 31, the output unit 34 acquires from the memory unit 35 a plurality of pieces of detection result information K4 (hereinafter also referred to as "a plurality of selected detection information K14") indicating the "physical condition" selected by the user from among the plurality of detection result information stored in the memory unit 35, i.e., the detection results of the physical condition detection unit 33, which correspond to the driver with driver ID "aaa123" during the period P2.

[0178] The output unit 34 then generates screen information M6 including the calculation results of the daily total value S2 for the period P2 and the detection results indicated by each selected detection information K14. The output unit 34 then transmits the generated screen information M6 to the fleet management device 301 via the communication unit 31.

[0179] When the processing unit 42 in the operation management device 301 receives the screen information M6 from the server 101 via the communication unit 41, it draws the event details screen G25, for example, on a web browser displayed on the display unit of its own operation management device 301 based on the screen information M6.

[0180] FIG. 16 is a diagram illustrating another example of an event details screen displayed in the traffic management device according to the embodiment of the present disclosure.

[0181] 16, the event details screen G25 displays a graph showing the driver's physical condition and the daily total value S2 for the period P3. In the graph, the horizontal axis represents the date, the left vertical axis represents the driver's physical condition, and the right vertical axis represents the total value S2.

[0182] In the example shown in Figure 16, a graph Q3 showing the driver's physical condition during period P2 is displayed, for example, as a line graph. The driver's physical condition is "good" from September 1st to September 3rd during period P2. The driver's physical condition is "normal" on September 4th. The driver's physical condition is "bad" on September 5th. The driver's physical condition is "good" from September 6th to September 9th.

[0183] 16, a graph Q4 showing the daily total value S2 for period P2 is displayed, for example, as a bar graph. The total values ​​S2 for September 1, 2, 3, 4, 5, 6, 7, 8, and 9 in 2023 are "zero," "zero," "1," "3," "6," "zero," "zero," "1," and "zero," respectively.

[0184] [Operation Flow] Next, the operation flow of the server 101 in the vehicle service development support system 501 according to the embodiment of the present disclosure will be described with reference to the drawings.

[0185] FIG. 17 is a flowchart illustrating an example of an operation procedure when the server according to the embodiment of the present disclosure performs the detection process.

[0186] 17, first, the server 101 stores the vehicle data group received from each in-vehicle device 201 in the storage unit 35 (step S101) until processing timing T2 arrives (NO in step S102).

[0187] Next, when processing timing T2 arrives (YES in step S102), the server 101 performs detection processes D1, D2, D3, and D4 for each driver ID using multiple vehicle data groups created by the in-vehicle device 201 for each processing timing T1 during the period from 24 hours before processing timing T2 to processing timing T2 and stored in the memory unit 35 (step S103).

[0188] Then, the server 101 waits for the next processing timing T2 to arrive (NO in step S102).

[0189] FIG. 18 is a flowchart defining an example of an operation procedure when the server according to the embodiment of the present disclosure performs the selection process.

[0190] Referring to FIG. 18, first, server 101 waits for reception of request information requesting notification of an event from fleet management device 301 (NO in step S201).

[0191] Then, when the server 101 receives the request information from the fleet management device 301 (YES in step S201), the server 101 creates screen information M1 indicating the type of event. For example, as described above, the server 101 creates screen information M1 indicating the types of events L1, L2, and L3 corresponding to the detection results of the detection processes D1, D2, and D3, respectively (step S202).

[0192] Next, the server 101 transmits the created screen information M1 to the operation management device 301 (step S203).

[0193] Next, the server 101 waits for reception of operation information indicating a user operation on the event selection screen displayed on the traffic management device 301 (NO in step S204) and for the arrival of processing timing T2 (NO in step S205).

[0194] Then, in the server 101, when the output unit 34 receives operation information from the fleet management device 301 via the communication unit 31 (YES in step S204), the output unit 34 performs a selection process to select one or more event detection units 32 from the multiple event detection units 32 in accordance with the user's selection operation indicated by the operation information. For example, as described above, the output unit 34 acquires, from the storage unit 35, detection result information indicating the detection result of the event detection unit 32 selected by the user from the multiple pieces of detection result information stored in the storage unit 35. Here, it is assumed that the server 101 receives operation information C1 indicating the user's operation on the event selection screen G1 shown in FIG. 6 and acquires selected detection information K11 from the storage unit 35 based on the operation information C1 (step S206).

[0195] Next, the server 101 uses the selection detection information K11 acquired from the storage unit 35 to create screen information M2 that shows the event details screen G2 (step S207).

[0196] Next, the server 101 transmits the created screen information M2 to the traffic management device 301 (step S208), and waits for reception of new operation information from the traffic management device 301 (NO in step S204).

[0197] Furthermore, when the processing timing T2 arrives (YES in step S205), the server 101 updates the screen information M1, transmits the updated screen information M1 to the operation management device 301 (step S209), and waits to receive new operation information from the operation management device 301 (NO in step S204).

[0198] FIG. 19 is a diagram illustrating a processing sequence of the in-vehicle device, the server, and the operation management device in the vehicle service development support system according to the embodiment of the present disclosure.

[0199] Referring to Figure 19, first, when processing timing T1 arrives, the in-vehicle device 201 creates a vehicle data group including at least one of accelerator information, brake information, vehicle speed information, position information, pressure information, and biometric information stored in the memory unit 15 (step S301).

[0200] Next, the in-vehicle device 201 performs a transmission process to transmit the created vehicle data group to the server 101 (step S302).

[0201] Next, the server 101 stores the vehicle data group received from the in-vehicle device 201 in the storage unit 35 (step S303).

[0202] Next, when processing timing T2 arrives, the server 101 performs detection processes D1, D2, D3, and D4 for each driver ID using multiple vehicle data groups created by the in-vehicle device 201 for each processing timing T1 during the period from 24 hours before processing timing T2 to processing timing T2 and stored in the memory unit 35 (step S304).

[0203] Next, the operation management device 301 transmits request information requesting notification of an event to the server 101 (step S305).

[0204] Next, the server 101 creates screen information M1 indicating the types of events L1, L2, and L3 corresponding to the detection results of the detection processes D1, D2, and D3, respectively (step S306).

[0205] Next, the server 101 transmits the created screen information M1 to the operation management device 301 (step S307).

[0206] Next, when the fleet management device 301 receives the screen information M1 from the server 101, it renders an event selection screen G1 on the web browser displayed on its own display unit, for example, based on the screen information M1 (step S308).

[0207] Next, the traffic management device 301 transmits operation information indicating a user operation on the event selection screen G1 to the server 101. Here, it is assumed that the traffic management device 301 transmits operation information C1 indicating a user operation on the event selection screen G1 shown in FIG. 6 (step S309).

[0208] Next, in the server 101, when the output unit 34 receives the operation information C1 from the traffic management device 301 via the communication unit 31, the output unit 34 performs a selection process to select one or more event detection units 32 from the plurality of event detection units 32 in accordance with the user's selection operation indicated by the operation information C1. For example, as described above, the output unit 34 acquires the selected detection information K11 from the storage unit 35 based on the operation information C1 (step S310).

[0209] Next, the server 101 uses the selection detection information K11 acquired from the storage unit 35 to create screen information M2 that shows the event details screen G2 (step S311).

[0210] Next, the server 101 transmits the created screen information M2 to the operation management device 301 (step S312).

[0211] Next, when the fleet management device 301 receives the screen information M2 from the server 101, it renders the event details screen G21, for example, on the web browser displayed on its own display unit, based on the screen information M2 (step S313).

[0212] In the vehicle service development support system 501 according to the embodiment of the present disclosure, the server 101 is configured to transmit screen information M1 indicating an event corresponding to a detection result of each event detection unit 32 to the traffic management device 301 as event information, but this is not limited to this. The server 101 may also be configured to transmit screen information indicating the type of an event that has occurred among the events corresponding to each event detection unit 32 to the traffic management device 301 as event information.

[0213] Furthermore, in the server 101 according to the embodiment of the present disclosure, each event detection unit 32 is configured to detect a state related to the driver in the detection process for detecting a state related to the passengers of the vehicle 1, but this is not limited to this. At least one event detection unit 32 among the plurality of event detection units 32 may be configured to detect a state related to a passenger instead of or in addition to a state related to the driver in the detection process.

[0214] Furthermore, in the detection process D4 for detecting the physical conditions of the passengers of the vehicle 1, the physical condition detection unit 33 is configured to detect the physical condition of the driver, but this is not limited to this. In the detection process D4, the physical condition detection unit 33 may be configured to detect the physical conditions of the passengers instead of or in addition to the driver's physical condition.

[0215] Furthermore, in the vehicle service development support system 501 according to the embodiment of the present disclosure, the server 101 is configured to accept a selection operation for selecting one or more event detection units 32 from the plurality of event detection units 32 and to perform selection processing in accordance with the selection operation, but this is not limiting. The server 101 may also be configured to select one or more event detection units 32 from the plurality of event detection units 32 in a predetermined order.

[0216] Furthermore, in the server 101 according to the embodiment of the present disclosure, the event detection unit 32C is configured to perform the detection process D3 for detecting the driving state of the driver based on accelerator information, brake information, and vehicle speed information over multiple days, but this is not limited to this. For example, the event detection unit 32C may be configured to perform the detection process D3 based on accelerator information, brake information, and vehicle speed information over a single day.

[0217] In addition, in the server 101 according to the embodiment of the present disclosure, each of the plurality of event detection units 32 is configured to notify the evaluation result regarding the driving state of the occupant as an event, but this is not limited to this. Some or all of the plurality of event detection units 32 may be configured to notify the evaluation result regarding the occupant, which is different from the evaluation result regarding the driving state, as an event.

[0218] Furthermore, although the server 101 according to the embodiment of the present disclosure is described as including an event detection unit 32A that detects an event L1 that notifies the driver of an evaluation result related to the driver's driving posture, an event detection unit 32B that notifies the driver of an evaluation result related to the driver's fatigue level as an event L2, and an event detection unit 32C that notifies the driver of an evaluation result related to the driver's driving riskiness as an event L3, the present disclosure is not limited to this. In addition to the event detection units 32A, 32B, and 32C, the server 101 may also include another event detection unit that notifies the driver of an evaluation result related to a driving state other than the driver's driving posture, the driver's fatigue level, and the driving riskiness as an event. Alternatively, the server 101 may include the other event detection unit instead of some or all of the event detection units 32A, 32B, and 32C.

[0219] Furthermore, in the vehicle service development support system 501 according to the embodiment of the present disclosure, the server 101 is configured to further output a detection result corresponding to the event notified by the selected event detection unit 32, but this is not limited thereto. The server 101 may also be configured not to output the detection result.

[0220] Furthermore, in the vehicle service development support system 501 according to the embodiment of the present disclosure, the server 101 is configured to accept a designation operation that designates conditions for the range of vehicle data used in the detection process and further output detection results based on vehicle data that satisfy the conditions designated in the designation operation, but this is not limited thereto. The server 101 may also be configured without the function of accepting the designation operation.

[0221] Furthermore, in the vehicle service development support system 501 according to the embodiment of the present disclosure, the server 101 is configured to output information indicating a time-series change in the detection result corresponding to the event notified by the selected event detection unit 32, but this is not limited thereto. The server 101 may also be configured to output the detection result without associating it with the measurement date and time.

[0222] Furthermore, some or all of the functions of the server 101 according to the embodiment of the present disclosure may be provided by cloud computing, i.e., the server 101 according to the embodiment of the present disclosure may be a cloud server configured by a plurality of servers.

[0223] The above-described embodiments should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims.

[0224] Each process (each function) in the above-described embodiments is realized by a processing circuit including one or more processors. The processing circuit may be configured as an integrated circuit or the like that combines one or more memories, various analog circuits, and various digital circuits in addition to the one or more processors. The one or more memories store programs (instructions) that cause the one or more processors to execute each of the processes. The one or more processors may execute each of the processes according to the program read from the one or more memories, or may execute each of the processes according to a logic circuit designed in advance to execute each of the processes. The processor may be any of various processors suitable for computer control, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a DSP (Digital Signal Processor), an FPGA (Field Programmable Gate Array), and an ASIC (Application Specific Integrated Circuit). Note that the physically separated processors may cooperate with each other to execute the processes. For example, the processors installed in the physically separated computers may cooperate with each other via a network such as a LAN (Local Area Network), a WAN (Wide Area Network), or the Internet to execute the processes. The program may be installed into the memory from an external server device or the like via the network, or may be distributed in a state stored on a recording medium such as a CD-ROM (Compact Disc Read Only Memory), a DVD-ROM (Digital Versatile Disc Read Only Memory), or a semiconductor memory, and then installed into the memory from the recording medium.

[0225] The above description includes the features noted below. [Note 1] A vehicle service development support device comprising: an acquisition unit that acquires data related to a vehicle; a plurality of detection units that perform detection processing to detect each of a plurality of states related to an occupant of the vehicle based on the data acquired by the acquisition unit, the plurality of detection units that perform notification related to an event based on detection results of the detection processing; and an output unit that performs selection processing to select one or more of the detection units from the plurality of detection units and output information related to the event based on the detection results of the selected detection units, wherein the plurality of detection units include a first detection unit that performs detection processing related to the driving posture of the occupant, a second detection unit that performs detection processing related to the number of times the occupant shifts in their seat, and a third detection unit that performs detection processing related to the driving state of the occupant.

[0226] REFERENCE SIGNS LIST 1 Vehicle 11 In-vehicle communication unit 12 Seat pressure information acquisition unit 13 Biometric information acquisition unit 14 Exterior communication unit 15, 34 Memory unit 21 Pressure sensor 31 Communication unit 32, 32A, 32B, 32C Event detection unit 33 Physical condition detection unit 34 Output unit 51, 51A, 51B Communication bus 61, 61A, 61B, 61C, 61D In-vehicle equipment 62 Pressure sensor 63 Vital sensor 101 Server 151 External network 201 In-vehicle device 301 Operation management device 501 Vehicle service development support system

Claims

1. A vehicle service development support device comprising: an acquisition unit that acquires data related to a vehicle; a plurality of detection units that perform detection processing to detect a plurality of states related to occupants of the vehicle based on the data acquired by the acquisition unit, the plurality of detection units that notify about an event based on the detection results of the detection processing; and an output unit that performs selection processing to select one or more detection units from the plurality of detection units and output information related to the event based on the detection results of the selected detection units.

2. The vehicle service development support device of claim 1 further includes a reception unit that receives a selection operation to select one or more detection units from the plurality of detection units, and the output unit performs the selection process in accordance with the selection operation received by the reception unit.

3. A vehicle service development support device as described in claim 1 or claim 2, wherein the acquisition unit acquires the data over multiple days, and at least one of the multiple detection units performs the detection processing based on the data over multiple days acquired by the acquisition unit.

4. A vehicle service development support device as described in claim 3, wherein the plurality of detection units includes a detection unit that notifies an evaluation result regarding the driving state of the occupant in the vehicle as the event.

5. A vehicle service development support device as described in any one of claims 1 to 4, wherein the plurality of detection units include at least one of a detection unit that notifies, as the event, an evaluation result regarding the driving posture of the occupant, a detection unit that notifies, as the event, an evaluation result regarding the fatigue level of the occupant while driving the vehicle, and a detection unit that notifies, as the event, an evaluation result regarding the danger of driving by the occupant.

6. A vehicle service development support device according to any one of claims 1 to 5, wherein the output unit further outputs the detection result corresponding to the event notified by the selected detection unit.

7. The vehicle service development support device of claim 6 further includes a reception unit that receives a specification operation that specifies conditions for the range of the data to be used in the detection process, and the output unit further outputs the detection results based on the data that meets the conditions specified in the specification operation received by the reception unit.

8. A vehicle service development support device as described in claim 6 or claim 7, wherein the acquisition unit acquires the time-series data, each of the detection units performs the detection process based on the time-series data acquired by the acquisition unit, and the output unit further outputs information indicating the time-series changes in the detection results corresponding to the event notified by the selected detection unit.

9. A service providing device comprising: a communication unit that receives information regarding the event from a vehicle service development support device described in any one of claims 1 to 8; and a processing unit that performs processing to provide a service related to the passenger based on the information regarding the event received by the communication unit.

10. A vehicle service development support method in a vehicle service development support device, comprising the step of acquiring data related to a vehicle, wherein the vehicle service development support device comprises a plurality of detection units that perform detection processing to detect a plurality of states related to occupants of the vehicle based on the acquired data, and the plurality of detection units that provide notification related to an event based on the detection results of the detection processing, the vehicle service development support method further comprising the step of performing a selection processing to select one or more detection units from the plurality of detection units, and outputting information related to the event based on the detection results of the selected detection units.

11. A vehicle service development support program used in a vehicle service development support device, which causes a computer to function as: an acquisition unit that acquires data related to a vehicle; a plurality of detection units that perform detection processing to detect multiple states related to occupants of the vehicle based on the data acquired by the acquisition unit, the plurality of detection units that notify users of an event based on the detection results of the detection processing; and an output unit that performs selection processing to select one or more detection units from the plurality of detection units and output information related to the event based on the detection results of the selected detection units.

Images