Vehicle service development support device, service provision device, vehicle service development support method, and vehicle service development support procedure
By acquiring vehicle data to detect passenger status and output relevant event information, the problem of long vehicle data formation and function development time is solved, thus simplifying the development of passenger services.
Patent Information
- Application Number
- CN202580014898.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-02-29
- Filing Date
- 2025-02-20
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, the formation and functional development of vehicle data take time, making it difficult for users to monitor the status of vehicle occupants in real time and provide related services.
A vehicle service development support device is provided, which acquires vehicle data, performs passenger status detection, and outputs relevant event information, thereby simplifying the service development process.
It enables the development of simplified services for vehicle passengers, allowing users to provide passenger-related services without requiring specialized knowledge.
Smart Images

Figure CN123125631A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to a vehicle service development support device, a service provision device, a vehicle service development support method, and a vehicle service development support procedure.
[0002] This application claims priority based on Japanese Application No. 2024-29518, filed on February 29, 2024, the entire contents of which are incorporated herein by reference. Background Technology
[0003] Patent Document 1 (Japanese Patent Publication No. 2014-534487) discloses a system that provides a foundational platform for a smart space environment, facilitating the rapid and easy development, deployment, and management of sensor-driven applications. This system includes: (a) a set of basic services integrated into the foundational platform, configured to acquire, store, and analyze sensor data received from multiple sensor devices; (b) multiple application programming interfaces (APIs), programming language libraries, and software development kits (SDKs) provided to application developers utilizing the basic services for the development, testing, deployment, and management of multiple sensor-based applications; (c) a demonstration module including multiple web-based portals configured to monitor, manage, and control the basic services, the developed applications, and the software and hardware infrastructure; and (d) a set of basic applications configured to send the sensor data to or receive the sensor data from the platform.
[0004] Existing technical documents Patent documents Patent Document 1: Japanese Patent Publication No. 2014-534487 Summary of the Invention
[0005] The vehicle service development support apparatus disclosed herein includes: an acquisition unit for acquiring vehicle-related data; multiple detection units for performing detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle, the multiple detection units for issuing event-related notifications based on the detection results of the detection processing; and an output unit for performing selection processing to select one or more of the multiple detection units and outputting information indicating the occurrence of the event based on the detection results of the selected detection units.
[0006] One solution disclosed herein can be implemented not only as a vehicle service development support device with such a characteristic processing unit, but also as a semiconductor integrated circuit that implements part or all of the vehicle service development support device, or as a system including the vehicle service development support device. Attached Figure Description
[0007] Figure 1 This is a diagram illustrating an example of the configuration of a vehicle service development support system according to an embodiment of the present disclosure.
[0008] Figure 2 This is a diagram illustrating an example of the configuration of a vehicle-mounted device according to an embodiment of the present disclosure.
[0009] Figure 3 This is a diagram illustrating an example of the configuration of a server according to an embodiment of the present disclosure.
[0010] Figure 4 This is a diagram illustrating an example of the configuration of an operation management device according to an embodiment of the present disclosure.
[0011] Figure 5 This is a diagram showing an example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0012] Figure 6 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0013] Figure 7 This is a diagram showing an example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0014] Figure 8 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0015] Figure 9 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0016] Figure 10 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0017] Figure 11 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0018] Figure 12 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0019] Figure 13 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0020] Figure 14 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0021] Figure 15 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0022] Figure 16 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0023] Figure 17 This is a flowchart illustrating an example of the operation process of a server performing detection processing according to an embodiment of the present disclosure.
[0024] Figure 18 This is a flowchart illustrating an example of the operation process when a server performs selection processing according to an embodiment of this disclosure.
[0025] Figure 19 This is a diagram illustrating the processing sequence of the vehicle-mounted device, server, and operation management device in a vehicle service development support system according to an embodiment of the present disclosure. Detailed Implementation
[0026] Previously, a system was developed that included a management device for collecting vehicle data related to the vehicle.
[0027] [The problem this disclosure aims to solve] In recent years, users such as operators who manage vehicle operations have demanded real-time monitoring of passenger conditions, such as fatigue levels, during vehicle operation, making these conditions visible, and providing passenger-related services such as operation planning based on these conditions. When users develop services using vehicle data collected from vehicles, the formation of the vehicle data and the development of the required functionalities take time.
[0028] This disclosure was 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 passengers.
[0029] [Effects of this disclosure] According to this disclosure, services related to vehicle passengers can be easily provided.
[0030] [Description of embodiments of this disclosure] First, the contents of the embodiments of this disclosure will be listed for explanation.
[0031] (1) The vehicle service development support apparatus according to the embodiments of the present disclosure includes: an acquisition unit for acquiring vehicle-related data; a plurality of detection units for performing detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle, the plurality of detection units for performing event-related notifications based on the detection results of the detection processing; and an output unit for performing selection processing to select one or more of the plurality of detection units and outputting event-related information based on the detection results of the selected detection units.
[0032] With this configuration, event-related information corresponding to the selected detection unit from among multiple detection units that issue event-related notifications can be output. Therefore, users do not need to perform tasks such as processing vehicle-related data for providing passenger-related services, and can receive the desired service corresponding to the selection result of the detection unit in the vehicle service development support device. Thus, passenger-related services for the vehicle can be provided simply.
[0033] (2) In (1) above, the vehicle service development support device may also include a receiving unit, which accepts a selection operation of selecting one or more of the multiple detection units, and the output unit performs the selection processing according to the selection operation accepted by the receiving unit.
[0034] With such a configuration, information related to the events the user expects can be output.
[0035] (3) In (1) or (2) above, the acquisition unit may acquire the data over several days, and at least one of the plurality of detection units may perform the detection processing based on the data over several days acquired by the acquisition unit.
[0036] This configuration allows for the monitoring of passenger-related conditions over multiple days, resulting in a wider range of test results.
[0037] (4) In (3) above, the plurality of detection units may include the detection unit that notifies the event of the evaluation result related to the driving state of the passenger in the vehicle.
[0038] With this configuration, users can confirm the evaluation of driving performed by the passenger based on the detection results of the passenger's condition over several days, and thus, for example, can judge the danger of driving performed by the passenger.
[0039] (5) In any of (1) to (4) above, the plurality of detection units may include at least one of the detection unit that notifies the event of the evaluation result related to the driver’s driving posture, the detection unit that notifies the event of the evaluation result related to the fatigue level of the driver while driving the vehicle, and the detection unit that notifies the event of the evaluation result related to the danger of driving by the driver.
[0040] For example, evaluations related to a passenger's driving condition, such as assessments related to the passenger's driving posture, the passenger's fatigue level while driving, and the hazard of driving by the passenger, require professional and academic insights. As described above, by configuring various detection units that can detect and evaluate a passenger's driving condition based on vehicle-related data, users can develop professional services without requiring professional and academic insights from the user to perform such evaluations.
[0041] (6) In any of (1) to (5) above, the output unit may also output the detection result corresponding to the event notified by the selected detection unit.
[0042] Such a structure allows for a more detailed understanding of the state of passengers who become factors in the occurrence of an event.
[0043] (7) In (6) above, the vehicle service development support device may also include a receiving unit that accepts a specified operation that specifies the conditions for the range of data used in the detection process, and the output unit outputs the detection result based on the data that satisfies the conditions specified in the specified operation accepted by the receiving unit.
[0044] With such a configuration, for example, detection results can be output based on data within a range that corresponds to the user's expectations, thus providing more useful information for service development.
[0045] (8) In (6) or (7) above, the acquisition unit may acquire the time series data, each detection unit may perform the detection processing based on the time series data acquired by the acquisition unit, and the output unit may also output information representing the time series change of the detection result corresponding to the event notified by the selected detection unit.
[0046] With such a configuration, for example, it is possible to output the temporal changes in the detection results of the rider's status during the period expected by the user, thus obtaining more useful information for service development.
[0047] (9) The service providing apparatus according to the present disclosure includes: a communication unit that receives information related to the event from the vehicle service development support apparatus of any one of (1) to (8) above; and a processing unit that performs processing for providing services related to the passenger based on the information related to the event received through the communication unit.
[0048] With this configuration, event-related information corresponding to the selected detection unit from among multiple detection units that issue event-related notifications can be output. Therefore, users do not need to perform tasks such as processing vehicle-related data for providing passenger-related services, and can receive the desired service corresponding to the selection result of the detection unit in the vehicle service development support device. Thus, passenger-related services for the vehicle can be provided simply.
[0049] (10) The vehicle service development support method of the present disclosure is a vehicle service development support method in a vehicle service development support device. The vehicle service development support method includes the step of acquiring vehicle-related data. The vehicle service development support device has multiple detection units. The multiple detection units perform detection processing based on the acquired data to detect multiple states related to the occupants of the vehicle. The multiple detection units make event-related notifications based on the detection results in the detection processing. The vehicle service development support method further includes the following steps: performing a selection process to select one or more of the multiple detection units, and outputting event-related information based on the detection results of the selected detection units.
[0050] This method outputs event-related information corresponding to the detection unit selected from multiple detection units that issue event-related notifications. Therefore, users do not need to perform tasks such as processing vehicle-related data for providing passenger-related services; they can receive the desired service corresponding to the selection result of the detection unit in the vehicle service development support device. Thus, passenger-related services for the vehicle can be provided simply.
[0051] (11) The vehicle service development support program of the present disclosure is a vehicle service development support program used in a vehicle service development support device. The vehicle service development support program enables a computer to function as an acquisition unit, multiple detection units, and an output unit. The acquisition unit acquires vehicle-related data, the multiple detection units perform detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle, the multiple detection units perform event-related notifications based on the detection results in the detection processing, and the output unit performs selection processing to select one or more of the multiple detection units and outputs event-related information based on the detection results of the selected detection units.
[0052] With this configuration, event-related information corresponding to the selected detection unit from among multiple detection units that issue event-related notifications can be output. Therefore, users do not need to perform tasks such as processing vehicle-related data for providing passenger-related services, and can receive the desired service corresponding to the selection result of the detection unit in the vehicle service development support device. Thus, passenger-related services for the vehicle can be provided simply.
[0053] Hereinafter, embodiments of the present disclosure will be described using the accompanying drawings. It should be noted that the same or equivalent parts in the drawings will be labeled with the same reference numerals, and their description will not be repeated. Furthermore, at least some of the embodiments described below may be arbitrarily combined.
[0054] [Vehicle Service Development Support System] Figure 1 This is a diagram illustrating an example of the configuration of a vehicle service development support system according to an embodiment of this disclosure. (Refer to...) Figure 1 The vehicle service development support system 501 includes a server 101, one or more vehicle-mounted devices 201, and an operation management device 301. The server 101 and the vehicle-mounted devices 201 can exchange information via an external network 151, such as the Internet. The vehicle-mounted devices 201 are 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 provisioning device.
[0055] Server 101 and operation management device 301 may be used by an operator or an individual. The users of server 101 and operation management device 301 may be the same or different. Server 101 and operation management device 301 may send and receive information via external network 151, for example. For example, if the users of server 101 and operation management device 301 are the same, the configuration may be as follows: the output content of operation management device 301 (described later) is notified from operation management device 301 to the operator who manages the operation of vehicle 1.
[0056] [Vehicle-mounted device] Figure 2 This is a diagram illustrating an example of the configuration of a vehicle-mounted device according to an embodiment of the present disclosure. (Refer to...) Figure 2 The vehicle-mounted device 201 is connected to multiple vehicle-mounted devices 61, for example, via a communication bus 51. The communication bus 51 is, for example, a CAN bus that conforms to the CAN (Controller Area Network) standard.
[0057] The vehicle-mounted equipment 61 includes vehicle-mounted ECUs (Electronic Control Units), sensors, navigation devices, human-machine interfaces, and cameras, etc.
[0058] exist Figure 2 In the example shown, the vehicle-mounted device 201 is connected to vehicle-mounted devices 61A and 61B, which are vehicle-mounted devices 61, via communication bus 51A, which is communication bus 51. In addition, the vehicle-mounted device 201 is connected to vehicle-mounted devices 61C and 61D, which are vehicle-mounted devices 61, via communication bus 51B, which is communication bus 51.
[0059] Vehicle-mounted device 201 and vehicle-mounted equipment 61 exchange information, for example, using CAN frames that conform to the CAN standard.
[0060] For example, each vehicle-mounted device 61 sends a CAN frame to the vehicle-mounted device 201 containing various information, such as information for assisting autonomous driving performed by the vehicle 1 and information for entertainment, as well as a CAN-ID (Identifier) indicating the type of data.
[0061] exist Figure 2In the example shown, vehicle-mounted device 61A is an accelerometer sensor. Vehicle-mounted device 61B is a brake sensor. Vehicle-mounted device 61C is a vehicle speed sensor. Vehicle-mounted device 61D is a GNSS (Global Navigation Satellite Systems) receiver. Hereinafter, vehicle-mounted devices 61A, 61B, 61C, and 61D will also be referred to as accelerometer sensor 61A, brake sensor 61C, vehicle speed sensor 61C, and GNSS receiver 61D, respectively.
[0062] Accelerator sensor 61A periodically measures the accelerator opening of vehicle 1 (hereinafter also referred to as "accelerator opening") and sends accelerator information indicating the measurement results and the measurement date and time ta to onboard device 201.
[0063] Brake sensor 61B periodically measures the opening degree of the brakes of vehicle 1 (hereinafter also referred to as "brake opening") and sends brake information indicating the measurement results and the measurement date and time tb to onboard device 201.
[0064] The vehicle speed sensor 61C periodically measures the speed of vehicle 1 and sends speed information, including the measurement result, measurement date, and time tc, to the on-board unit 201.
[0065] The GNSS receiver 61D receives GNSS signals from one or more satellites, for example, periodically, and performs position detection of vehicle 1 based on the received GNSS signals. The position of vehicle 1 is represented, for example, by latitude and longitude.
[0066] The GNSS receiver 61D periodically sends, for example, detection results indicating the position of vehicle 1, along with the date and time td of the detected position, to the vehicle-mounted device 201. Here, the GNSS receiver 61D, for example, performs position detection of vehicle 1 at the same timing as the vehicle speed sensor 61C and sends the position information to the vehicle-mounted device 201.
[0067] The vehicle-mounted 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. Part 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 implemented, for example, by a processing circuit including one or more processors. The storage unit 15 is, for example, a non-volatile memory included in the aforementioned processing circuit.
[0068] (In-vehicle communication unit) The in-vehicle communication unit 11 acquires accelerometer information, brake information, vehicle speed information, and position information. More specifically, for example, when accelerometer information is received from the accelerometer sensor 61A, the in-vehicle communication unit 11 saves the received accelerometer information in the storage unit 15.
[0069] In addition, for example, when brake information is received from brake sensor 61B, the in-vehicle communication unit 11 saves the received brake information in the storage unit 15.
[0070] In addition, for example, when vehicle speed information is received from vehicle speed sensor 61C, the in-vehicle communication unit 11 saves the received vehicle speed information in storage unit 15.
[0071] In addition, for example, when location information is received from GNSS receiver 61D, the in-vehicle communication unit 11 saves the received location information in the storage unit 15.
[0072] It should be noted that the vehicle-mounted device 201 and the vehicle-mounted equipment 61 may also be configured as follows: instead of communication following the CAN standard, or in addition to such communication, to perform communication following communication protocols such as CAN FD (CAN with Flexible Data Rate), Ethernet (registered trademark), FlexRay (registered trademark), MOST (Media OritendSystem Transport) (registered trademark), LIN (Local Interconnect Network), and CXPI (Clock Extention Peripheral Interface) (registered trademark).
[0073] (Pressure Information Acquisition Department) The pressure information acquisition unit 12 acquires pressure information representing the pressure exerted by the passenger on the seat surface of the vehicle 1. In this embodiment, for example, the pressure information acquisition unit 12 acquires information representing the pressure exerted by the driver on the driver's seat surface of the vehicle 1 (hereinafter also referred to as "seat pressure P") as pressure information.
[0074] More specifically, for example, multiple pressure sensors 62 are provided on the driver's seat of vehicle 1.
[0075] The vehicle-mounted device 201 communicates wirelessly with each pressure sensor 62, for example, according to standards such as Bluetooth.
[0076] Each pressure sensor 62 sends pressure information to the vehicle-mounted device 201, indicating the measurement result, measurement date and time te, and its own ID (identifier) (hereinafter also referred to as "sensor ID"). Each pressure sensor 62 performs pressure measurements and sends pressure information periodically, for example. Here, each pressure sensor 62 measures the seat pressure P on the same measurement date and time te, and sends the pressure information to the vehicle-mounted device 201 on the same sending date and time. Each pressure sensor 62 performs seat pressure P measurements and sends pressure information every minute, for example.
[0077] In the vehicle-mounted device 201, when pressure information is received from each pressure sensor 62, the pressure information acquisition unit 12 stores the received pressure information in the storage unit 15.
[0078] (Biobiotechnology Information Acquisition Department) The biometric information acquisition unit 13 acquires the biometric information of the occupants of vehicle 1. This biometric information includes the occupants' body temperature, heart rate, and pulse rate. In this embodiment, for example, the biometric information acquisition unit 13 acquires the biometric information of the driver of vehicle 1.
[0079] More specifically, for example, the biometric information acquisition unit 13 communicates wirelessly with the vital signs sensor 63 worn by the driver according to standards such as Bluetooth.
[0080] The vital signs sensor 63 is a sensor that detects the driver's biological information. Specifically, the vital signs sensor 63 may be a wearable device such as a smartwatch. In this embodiment, for example, the vital signs sensor 63 measures the body temperature of the driver in vehicle 1. Furthermore, the vital signs sensor 63 sends biological information, representing the measured value and the date and time tf of the measurement, to the on-board unit 201. The vital signs sensor 63 performs body temperature measurement and sends biological information periodically, for example.
[0081] In the vehicle-mounted device 201, when biological information is received from the vital signs sensor 63, the biological information acquisition unit 13 saves the received biological information in the storage unit 15.
[0082] (External Communication Department) The external communication unit 14 performs transmission processing to send to the server 101 the accelerator information, brake information and vehicle speed information obtained through the internal communication unit 11, the pressure information obtained through the pressure information acquisition unit 12, and the biological information obtained through the biological information acquisition unit 13.
[0083] More specifically, the external communication unit 14 wirelessly communicates with devices such as a wireless base station (not shown) using communication methods such as WiFi (registered trademark), LTE (Long Term Evolution) (registered trademark), or 5G (5th Generation), thereby communicating with the server 101 via the external network 151. It should be noted that the external communication unit 14 is not limited to a configuration where it communicates with the server 101 via a wireless base station and the external network 151; it can also be configured to communicate with the server 101 via a wired line. Furthermore, the external communication unit 14 may also be configured to communicate with the server 101 via other in-vehicle devices.
[0084] For example, the storage unit 15 stores driver identification information (hereinafter also referred to as "driver ID") used to identify the driver of vehicle 1. The driver ID is a unique ID for each driver.
[0085] For example, when the processing time T1 arrives, the external communication unit 14 generates a vehicle data set containing at least one of the following stored in the storage unit 15: accelerator information, brake information, vehicle speed information, position information, pressure information, and biological information. Furthermore, the external communication unit 14 sends the generated vehicle data set, including the driver ID, to the server 101. The period of the processing time T1 is, for example, 10 minutes.
[0086] [server] Figure 3 This is a diagram illustrating an example of the configuration of a server according to an embodiment of this disclosure. (Refer to...) Figure 3 The server 101 includes a communication unit 31, a multiple event detection unit 32, a health status detection unit 33, an output unit 34, and a storage unit 35. Some or all of the communication unit 31, the multiple event detection unit 32, the health status 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 aforementioned processing circuit. The communication unit 31 is an example of an acquisition unit and also an example of a receiving unit.
[0087] (Ministry of Communications) The communication unit 31 acquires vehicle data related to vehicle 1. More specifically, for example, the communication unit 31 acquires time-series vehicle data.
[0088] The communication unit 31 acquires accelerator information, brake information, vehicle speed information, pressure information, and biological information contained in the vehicle data set sent from the vehicle-mounted device 201 as time-series vehicle data.
[0089] For example, whenever the communication unit 31 receives a vehicle data set from the vehicle-mounted device 201 via the external network 151, the communication unit 31 saves the received vehicle data set, for example, according to each driver ID, in the storage unit 35.
[0090] (Testing Department) Multiple event detection units 32 perform detection processing based on vehicle data acquired through the communication unit 31 to detect multiple states related to the occupants of vehicle 1. Hereinafter, examples of each event detection unit 32 detecting states related to the driver of vehicle 1 during the detection processing will be described.
[0091] For example, each event detection unit 32 performs detection processing based on the time-series vehicle data obtained through the communication unit 31.
[0092] exist Figure 3 In the example shown, server 101 has multiple event detection units 32A, 32B, and 32C, which are event detection units 32.
[0093] For example, when processing time T2 arrives, such as a predetermined time within a day, each event detection unit 32 acquires multiple vehicle data sets generated by the vehicle-mounted device 201 at each processing time T1 during the period from 24 hours before processing time T2 to processing time T2 and stored in the storage unit 35 by the communication unit 31.
[0094] <Detection and Processing D1> The event detection unit 32A performs detection processing D1 related to the driver's driving posture based on the pressure information obtained through the communication unit 31.
[0095] More specifically, for example, when multiple vehicle data sets for a certain day are obtained from the storage unit 35, the event detection unit 32A uses the multiple pressure information contained in each vehicle data set to perform detection processing D1.
[0096] Specifically, for example, the event detection unit 32A calculates the driver's center of gravity position on the measurement date and time te based on multiple pressure information contained in a vehicle data set that have the same measurement date and time te.
[0097] For example, storage unit 35 stores representations Figure 2 A list of sensor locations showing the correspondence between the sensor ID of pressure sensor 62 and the location of pressure sensor 62 in the driver's seat.
[0098] The event detection unit 32A determines the position of the pressure sensor 62 corresponding to the sensor ID represented by the pressure information by referring to the sensor position list in the storage unit 15 for each pressure information under a certain measurement date and time te.
[0099] Then, the event detection unit 32A calculates the driver's center of gravity position on the seat surface at the corresponding measurement date and time te based on the measured values represented by each pressure information and the determined position of each pressure sensor 62.
[0100] For example, the storage unit 35 stores a reference position G for the center of gravity. The reference position G, for example, represents the center of gravity position under an ideal driving posture.
[0101] When the center of gravity position is calculated for a certain measurement date and time te, the event detection unit 32A calculates the change in the center of gravity position relative to the ideal driving posture (hereinafter also referred to as "posture change") 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.
[0102] For example, the event detection unit 32A determines the driver's driving posture as "leaning forward", "slightly leaning forward", "ideal", "slightly leaning back" or "leaning back" based on the calculated change in posture.
[0103] For example, when the value of the posture change is "0", the event detection unit 32A determines that the driver's driving posture is "ideal". Furthermore, when the value of the posture change is "+1", the event detection unit 32A determines that the driver's driving posture is "slightly forward-leaning". Furthermore, when the value of the posture change is greater than or equal to "+2", the event detection unit 32A determines that the driver's driving posture is "forward-leaning". Furthermore, when the value of the posture change is "-1", the event detection unit 32A determines that the driver's driving posture is "slightly backward-leaning". Furthermore, when the value of the posture change is greater than or equal to "-2", the event detection unit 32A determines that the driver's driving posture is "backward-leaning".
[0104] Then, the event detection unit 32A saves the detection result information K1, which represents the calculated posture change amount, the driving posture corresponding to the posture change amount, the measurement date and time te, and the driver ID, in the storage unit 35.
[0105] <Detection and Processing D2> The event detection unit 32B performs detection processing D2 related to the number of times the driver has adjusted his / her posture in the seat (hereinafter also referred to as "posture adjustment number") based on the pressure information obtained through the communication unit 31.
[0106] More specifically, for example, when multiple vehicle data sets for a certain day are obtained from the storage unit 35, the event detection unit 32B uses the multiple pressure information contained in each vehicle data set to perform detection processing D2.
[0107] Specifically, for example, the event detection unit 32B calculates the number of posture adjustments per minute for each driver ID based on multiple pressure information that have the same measurement date and time te among multiple pressure information contained in a vehicle data set.
[0108] Then, the event detection unit 32B saves the calculation result representing the number of times the sitting posture was adjusted, as well as the detection result information K2 of the measurement date and time te and driver ID corresponding to the calculation result in the storage unit 35.
[0109] <Detection and Processing D3> The event detection unit 32C performs detection processing D3 related to the danger of the driver's driving based on the accelerator information, brake information and vehicle speed information obtained through the communication unit 31 over several days.
[0110] More specifically, for example, the event detection unit 32C uses multiple vehicle data sets from a certain day obtained from the storage unit 35 to perform detection processing D3 by each driver ID.
[0111] Specifically, for example, when multiple vehicle data sets for a certain day are obtained from the storage unit 35, the event detection unit 32C counts the number N1 of the multiple vehicle data sets containing accelerator information representing an accelerator opening greater than or equal to a predetermined threshold Th1, according to each driver ID.
[0112] Furthermore, for example, when multiple vehicle data sets for a certain day are obtained from the storage unit 35, the event detection unit 32C counts the number N2 of vehicle data sets containing brake information indicating a brake opening degree greater than or equal to a predetermined threshold Th2, according to each driver ID.
[0113] For example, the storage unit 35 stores a road table that shows the correspondence between the location coordinates of the indicated road and the speed limit.
[0114] When multiple vehicle data sets for a certain day are obtained from the storage unit 35, the event detection unit 32C determines the speed limit (hereinafter also referred to as "corresponding speed limit") corresponding to the position of vehicle 1 represented by the location information contained in the vehicle data set for each obtained vehicle data set by referring to the road table in the storage unit 35.
[0115] Then, the event detection unit 32C counts the number N3 of vehicle data groups that contain vehicle speed information indicating a speed greater than the corresponding speed limit from multiple vehicle data groups obtained from the storage unit 35 for a certain day, according to each driver ID.
[0116] The event detection unit 32C stores the detection result information K3 in the storage unit 35, which represents the number N1, number N2, number N3 obtained by counting, the date of detection processing D3, and the driver ID contained in the vehicle data group corresponding to the number N1, number N2, number N3.
[0117] (Physical Condition Testing Department) For example, the physical condition detection unit 33 performs detection processing D4 to detect the physical condition of the occupants of vehicle 1 based on the biological information obtained through the communication unit 31. Hereinafter, an example of the physical condition detection unit 33 detecting the physical condition of the driver of vehicle 1 in detection processing D4 will be described.
[0118] More specifically, for example, when processing time T2 arrives, similarly to event detection unit 32, physical condition detection unit 33 retrieves from storage unit 35 multiple vehicle data sets generated by vehicle device 201 at each processing time T1 and stored in storage unit 35 by communication unit 31 during the period from 24 hours before processing time T2 to processing time T2. Then, physical condition detection unit 33 uses these multiple vehicle data sets to perform detection processing D4 for each driver ID.
[0119] Specifically, for example, when multiple vehicle data sets for a certain day are obtained from the storage unit 35, the physical condition detection unit 33 counts the number N4 of vehicle data sets containing biological information representing a body temperature greater than or equal to a predetermined threshold Th4 in each of the multiple vehicle data sets according to each driver ID.
[0120] For example, the physical condition detection unit 33 determines whether the driver's physical condition is "good", "slightly better", "average", "slightly worse" or "poor" based on the value of the number N4 obtained by counting.
[0121] Then, the physical condition detection unit 33 saves the detection result information K4, which indicates the determined physical condition, the date of the detection process D4, and the driver ID corresponding to the quantity N4, in the storage unit 35.
[0122] (Event Information) Each event detection unit 32 issues event-related notifications based on the detection results of the detection processing.
[0123] For example, each event detection unit 32 notifies the driver of the vehicle 1 of the evaluation results related to the occupant's driving status as an event. More specifically, event detection unit 32A notifies the driver of the occupant's driving posture as event L1. Event detection unit 32B notifies the driver of the vehicle 1 of the evaluation results related to the occupant's fatigue level while driving as event L2. Event detection unit 32C notifies the driver of the vehicle 1 of the evaluation results related to the danger of driving by the occupant as event L3.
[0124] Specifically, for example, event L1 is the detection result of the driver's driving posture in detection process D1 performed by event detection unit 32A. Event L2 is the detection result of the number of times the driver adjusts their seating position in detection process D2 performed by event detection unit 32B. Event L3 is the detection result of the hazard of the driver's driving in detection process D3 performed by event detection unit 31C.
[0125] For example, the operation management device 301 sends a request for event information related to the event to the server 101 according to the operation performed by the user.
[0126] In server 101, when a request message is received from operation management device 301, communication unit 31 generates screen information M1 indicating the type of event L1, event L2, and event L3 corresponding to detection result information K1, detection result information K2, and detection result information K3 stored in storage unit 35, respectively. Then, communication unit 31 sends the generated screen information M1 to operation management device 301.
[0127] Figure 4 This is a diagram illustrating an example of the configuration of an operation management device according to an embodiment of the present disclosure. (Refer to...) Figure 4 The operation management device 301 includes a communication unit 41 and a processing unit 42. One or both of the communication unit 31 and the processing unit 42 are implemented, for example, by a processing circuit including one or more processors.
[0128] Reference Figure 4 For example, the communication unit 41 receives event information related to the event from the server 101.
[0129] Specifically, for example, the communication unit 41 receives screen information M1 sent from the server 101 as event information. When the screen information M1 is received from the server 101, the communication unit 41 outputs the received screen information M1 to the processing unit 42.
[0130] 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 through the communication unit 41.
[0131] Specifically, for example, when the screen information M1 is received from the communication unit 41, the processing unit 42 draws the event selection screen G1 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M1.
[0132] Figure 5 This is a diagram showing an example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure.
[0133] Reference Figure 5 The event selection screen G1 includes areas A1, A2, and A3. Area A1 displays events based on the detection results performed by the event detection units 32 in server 101.
[0134] exist Figure 5 In the example shown, area A1 displays the representation of... Figure 3 The event detection unit 32A is shown as "posture monitoring" for event L1, the event detection unit 32B is shown as "sitting posture adjustment detection" for event L2, and the event detection unit 32C is shown as "hazardous characteristic detection" for event L3.
[0135] Area A1 contains checkboxes Ch1, Ch2, and Ch3, which correspond to “Posture Monitoring”, “Sitting Posture Adjustment Detection”, and “Hazardous Characteristic Detection”, respectively.
[0136] For example, area A2 displays the name of the data to be compared with the vehicle data (hereinafter also referred to as "comparison object data") or the display conditions of the detection results corresponding to each event detection unit 32. Area A3 displays the name of the vehicle data acquired by server 101.
[0137] exist Figure 5 In the example shown, the name of the comparison data displayed in area A2 is "Physical Condition," representing the driver's biological information. Furthermore, the display condition for the test results shown in area A2 is "Year," indicating that the test results are displayed monthly.
[0138] Area A2 contains checkboxes Ch4 and Ch5, which correspond to "physical condition" and "years of life," respectively.
[0139] It should be noted that in area A2, as a condition for displaying the test results, in addition to "years" which indicates that the test results are displayed monthly, "driving area" which indicates the driving area of vehicle 1 can also be displayed instead of "years".
[0140] In addition, Figure 5In the example shown, the names of the vehicle data displayed in area A3 are "seat pressure" for pressure information, "accelerator opening" for accelerator information, "brake opening" for brake information, "vehicle speed" for vehicle speed information, and "body condition" for biological information.
[0141] Area A3 contains checkboxes Ch6, Ch7, Ch8, Ch9, and Ch10, which correspond to “seat pressure”, “accelerator opening”, “brake opening”, “vehicle speed”, and “physical condition”, respectively.
[0142] For example, the event selection screen G1 also includes an input field B1 for the driver ID, an input field B2 for the start date and time of the event retrieval period, and an input field B3 for the end date and time of the event retrieval period.
[0143] (Select processing) Refer again Figure 3 For example, the communication unit 31 accepts a selection operation of choosing one or more event detection units 32 from a plurality of event detection units 32.
[0144] More specifically, for example, the communication unit 31 acquires operation information indicating the user's operation on the event selection screen G1 displayed on the operation management device 301.
[0145] Figure 6 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure. Figure 6 The event selection screen G1 is shown in the following situation: The user enters any value into input fields B1, B2, and B3, and clicks checkbox Ch1.
[0146] Reference Figure 6 For example, suppose a user enters "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 clicks checkbox Ch1. In this case, the operation management device 301 sends operation information C1 indicating these operations to the server 101.
[0147] In server 101, when operation information C1 is received from operation management device 301, communication unit 31 outputs operation information C1 to output unit 34.
[0148] The output unit 34 performs a selection process to select one or more event detection units 32 from a 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.
[0149] More specifically, for example, the output unit 34 performs selection processing according to the selection operation handled by the communication unit 31.
[0150] Specifically, for example, when operation information C1 is received from communication unit 31, output unit 34, based on operation information C1, retrieves detection result information K1 (hereinafter also referred to as "selection detection information K11") from storage unit 35, which represents the detection result of "posture monitoring" selected by the user, i.e., event detection unit 32A, from multiple detection result information stored in storage unit 35. This detection result is the detection result corresponding to the driver with driver ID "aaa123" within the period P1 from 10:00 on September 9, 2023 to 10:10 on September 9, 2023, as input by the user.
[0151] For example, in addition to outputting the event information mentioned above, the output unit 34 also outputs the detection result corresponding to the event notified by the selected event detection unit 32.
[0152] Specifically, for example, when selection detection information K11 is obtained from storage unit 35, output unit 34 uses the obtained selection detection information K11 to generate screen information M2 representing event details screen G21. Then, output unit 34 sends the generated screen information M2 to operation management device 301 via communication unit 31.
[0153] When the screen information M2 is received from the server 101 via the communication unit 41, the processing unit 42 in the operation management device 301 draws the event details screen G21 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M2.
[0154] Figure 7 This is a diagram showing an example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0155] Reference Figure 7 This shows the posture state of the driver with driver ID "aaa123" every minute during period P1.
[0156] exist Figure 7In the example shown, between 10:00 and 10:04 during period P1, the driver's driving posture is "ideal". Between 10:05 and 10:07 during period P1, the driver's driving posture is "slightly leaning back". Between 10:08 and 10:10 during period P1, the driver's driving posture is "leaning forward".
[0157] Figure 8 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure. Figure 8 The event selection screen G1 is shown in the following situation: The user enters any value into input fields B1, B2, and B3, and clicks checkbox Ch2.
[0158] Reference Figure 8 For example, suppose a user enters "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 clicks checkbox Ch2. In this case, the operation management device 301 sends operation information C2 indicating these operations to the server 101.
[0159] In server 101, when operation information C2 is received from operation management device 301, communication unit 31 outputs operation information C2 to output unit 34.
[0160] For example, when operation information C2 is received from communication unit 31, output unit 34 retrieves detection result information K2 (hereinafter also referred to as "selection detection information K12") from storage unit 35, which represents the detection result of the "sitting posture adjustment detection" selected by the user, i.e., the detection result of event detection unit 32B, from among the multiple detection result information stored in storage unit 35. This detection result is the detection result corresponding to the driver with driver ID "aaa123" during the period P1 input by the user.
[0161] For example, when selection detection information K12 is obtained from storage unit 35, output unit 34 uses selection detection information K12 to generate screen information M3 representing event details screen G22. Then, output unit 34 sends the generated screen information M3 to operation management device 301 via communication unit 31.
[0162] When the screen information M3 is received from the server 101 via the communication unit 41, the processing unit 42 in the operation management device 301 draws the event details screen G22 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M3.
[0163] Figure 9 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0164] Reference Figure 9 The event details screen G22 shows the number of times the driver with driver ID "aaa123" adjusted their seating position per minute during period P1.
[0165] exist Figure 9 In the example shown, the number of posture adjustments during the period from 10:00 to 10:06 in P1 is "0". The number of posture adjustments during the period from 10:07 in P1 is "1". The number of posture adjustments during the period from 10:08 to 10:10 in P1 is "0".
[0166] Figure 10 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure. Figure 10 The event selection screen G1 is shown in the following situation: The user enters any value into input fields B1, B2, and B3, and clicks checkboxes Ch1 and Ch2.
[0167] Reference Figure 10 Suppose a user enters "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, and clicks checkboxes Ch1 and Ch2. In this case, the operation management device 301 sends operation information C3 indicating these operations to the server 101.
[0168] In server 101, when operation information C3 is received from operation management device 301, communication unit 31 outputs operation information C3 to output unit 34.
[0169] For example, when the operation information C3 is received from the communication unit 31, the output unit 34 obtains the selected detection information K11 and selected detection information K12 from the multiple detection result information stored in the storage unit 35 based on the operation information C3.
[0170] For example, when selection detection information K11 and selection detection information K12 are obtained from the storage unit 35, the output unit 34 uses the selection detection information K11 and selection detection information K12 to generate screen information M4 representing the event details screen G23. Then, the output unit 34 sends the generated screen information M4 to the operation management device 301 via the communication unit 31.
[0171] When the screen information M4 is received from the server 101 via the communication unit 41, the processing unit 42 in the operation management device 301 draws the event details screen G23 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M4.
[0172] Figure 11 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0173] Reference Figure 11 The event details screen G23 shows the number of times the driver with driver ID "aaa123" adjusted their driving posture and seating position per minute during the period P1.
[0174] exist Figure 11 In the example shown, the driver's driving posture during period P1 is the same as... Figure 7 The driving posture shown in the event details screen of G21 is the same. Furthermore, in Figure 11 In the example shown, the number of times the driver adjusts their seating position during period P1 is related to... Figure 9 The number of posture adjustments shown in the event details screen G22 is the same.
[0175] Figure 12 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure. Figure 12 This shows another example of the event details screen G23.
[0176] Reference Figure 12 The event details screen G23 displays a graph showing the amount of posture changes and the number of seating adjustments made by the driver during period P1. In this graph, the horizontal axis represents the date and time, the left vertical axis represents the amount of posture changes, and the right vertical axis represents the number of seating adjustments.
[0177] exist Figure 12 In the example shown, the graph Q1 representing the change in posture is displayed as a line graph, for example. The change in posture between 10:00 and 10:04 during period P1 is “0”. The change in posture between 10:05 and 10:07 is “-1”. The change in posture between 10:08 and 10:10 is “2”.
[0178] In addition, Figure 12 In the example shown, the chart Q2, which represents the number of posture adjustments, is displayed as a bar chart, for example. Figure 12 The number of times the sitting posture was adjusted as shown Figure 9 The number of posture adjustments shown in the event details screen G22 is the same.
[0179] For example, the Communications Department 31 accepts the specified operation for specifying the conditions of the range of vehicle data used in the detection process.
[0180] More specifically, for example, the Ministry of Communications accepted the case in Section 31. Figure 5 The event selection screen G1, area A2, displays the detection result display condition "over the years" and performs the specified operation, namely, accepting the user's click on checkbox Ch5.
[0181] Figure 13 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure. Figure 13 The event selection screen G1 is shown in the following situation: The user enters any value into input fields B1, B2, and B3 and clicks checkboxes Ch3, Ch5, Ch7, and Ch9.
[0182] Reference Figure 13 For example, suppose a user enters "aaa123", "2022 / 9", and "2023 / 5" into input fields B1, B2, and B3 of the event selection screen G1, and clicks checkboxes Ch3, Ch5, Ch7, and Ch9 respectively. In this case, the operation management device 301 sends operation information C4 indicating these operations to the server 101.
[0183] In server 101, when operation information C4 is received from operation management device 301, communication unit 31 outputs operation information C4 to output unit 34.
[0184] For example, the output unit 34 also outputs the detection results based on vehicle data that meet the conditions specified in the designated operation handled by the communication unit 31.
[0185] More specifically, for example, when operation information C4 is received from communication unit 31, output unit 34, based on operation information C4, retrieves from storage unit 35 multiple detection result information K3 (hereinafter also referred to as "multiple selection detection information K13") representing the detection result of the "hazardous characteristic detection" i.e., event detection unit 32C selected by the user, from multiple detection result information stored in storage unit 35. This detection result is the detection result corresponding to the driver with driver ID "aaa123" during the period from September 2022 to May 2023, as input by the user.
[0186] Then, the output unit 34 uses the acquired multiple selection detection information K13 to calculate the total value of the accelerator information and vehicle speed information selected by the user each month, that is, the total value S1 of the above-mentioned quantity N1 and quantity N3.
[0187] When the total value S1 for each month is calculated, the output unit 34 generates screen information M5 representing the calculation result. Then, the output unit 34 sends the generated screen information M5 to the operation management device 301 via the communication unit 31.
[0188] When the screen information M5 is received from the server 101 via the communication unit 41, the processing unit 42 in the operation management device 301 draws the event details screen G24 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M5.
[0189] Figure 14 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0190] Reference Figure 14 The event details screen G24 displays a chart showing the total value S1 for each month from September 2022 to May 2023. In this chart, the horizontal axis represents the year and month, and the vertical axis represents the total value S1.
[0191] exist Figure 14 In the example shown, the total value S1 for September 2022, October 2022, November 2022, December 2022, January 2023, February 2023, March 2023, April 2023, and May 2023 are “3”, “2”, “1”, “4”, “3”, “4”, “6”, “10”, and “12”, respectively.
[0192] Figure 15 This is a diagram showing another example of an event selection screen displayed in an operation management device according to an embodiment of this disclosure. Figure 15 The event selection screen G1 is shown in the following situation: The user enters any value into input fields B1, B2, and B3 and clicks checkboxes Ch3, Ch4, Ch7, Ch8, Ch9, and Ch10.
[0193] Reference Figure 15 For example, suppose a user enters "aaa123", "2023 / 9 / 1", and "2023 / 9 / 9" into input fields B1, B2, and B3 of the event selection screen G1, respectively, and clicks checkboxes Ch3, Ch4, Ch7, Ch8, Ch9, and Ch10. In this case, the operation management device 301 sends operation information C5 indicating these operations to the server 101.
[0194] In server 101, when operation information C5 is received from operation management device 301, communication unit 31 outputs operation information C5 to output unit 34.
[0195] For example, when the communication unit 31 receives the operation information C5, the output unit 34, based on the operation information C4, retrieves from the storage unit 35 multiple detection result information K3 (hereinafter also referred to as "multiple selection detection information K23") which represents the detection result of the "hazardous characteristic detection" i.e., the event detection unit 32C selected by the user, from the multiple detection result information stored in the storage unit 35. The detection result is the detection result corresponding to the driver with driver ID "aaa123" within the period P2 from September 1, 2022 to September 9, 2023, as input by the user.
[0196] Then, the output unit 34 uses the acquired multiple selection detection information K23 to calculate the total value of the accelerator information, brake information and vehicle speed information selected by the user each day, namely the total value S2 of the above-mentioned quantities N1, N2 and N3.
[0197] Furthermore, for example, based on the operation information C5 received from the communication unit 31, the output unit 34 retrieves from the storage unit 35 multiple detection result information K4 (hereinafter also referred to as "multiple selection detection information K14") which represents the "physical condition" selected by the user, i.e., the detection result of the physical condition detection unit 33, from the multiple detection result information stored in the storage unit 35. This detection result is the detection result corresponding to the driver with driver ID "aaa123" during the period P2.
[0198] Then, the output unit 34 generates screen information M6, which includes the calculation result of the daily total value S2 within period P2 and the detection result represented by each selected detection information K14. Then, the output unit 34 sends the generated screen information M6 to the operation management device 301 via the communication unit 31.
[0199] When the screen information M6 is received from the server 101 via the communication unit 41, the processing unit 42 in the operation management device 301 draws the event details screen G25 on the web browser displayed on the display unit of its own operation management device 301 based on the screen information M6.
[0200] Figure 16 This is a diagram showing another example of an event details screen displayed in the operation management device according to an embodiment of this disclosure.
[0201] Reference Figure 16The event details screen G25 displays a chart showing the driver's physical condition during period P3 and the daily total S2. In this chart, the horizontal axis represents the date, the left vertical axis represents the driver's physical condition, and the right vertical axis represents the total S2.
[0202] exist Figure 16 In the example shown, chart Q3, representing the driver's physical condition during period P2, is displayed as a line graph, for example. The driver's physical condition during period P2, from September 1st to September 3rd, is "good." The driver's physical condition on September 4th is "average." The driver's physical condition on September 5th is "poor." The driver's physical condition between September 6th and September 9th is "good."
[0203] In addition, Figure 16 In the example shown, the chart Q4, which represents the daily total S2 within period P2, is displayed as a bar chart, for example. The total S2 for September 1, 2, 3, 4, 5, 6, 7, 8, and 9, 2023, are “0”, “0”, “1”, “3”, “6”, “0”, “0”, “1”, and “0”, respectively.
[0204] [Action Flow] Next, the operation flow of the server 101 in the vehicle service development support system 501 of the present disclosure will be described using the accompanying drawings.
[0205] Figure 17 This is a flowchart illustrating an example of the operation process of a server performing detection processing according to an embodiment of the present disclosure.
[0206] Reference Figure 17 First, before processing the arrival of time T2 (in step S102, "No"), the server 101 saves the vehicle data groups received from each vehicle-mounted device 201 to the storage unit 35 (step S101).
[0207] Next, when processing time T2 arrives ("Yes" in step S102), server 101 uses multiple vehicle data sets generated by vehicle device 201 and stored in storage unit 35 at each processing time T1 during the period from 24 hours before processing time T2 to processing time T2, and performs detection processing D1, detection processing D2, detection processing D3, and detection processing D4 at each driver ID (step S103).
[0208] Then, server 101 waits for the next processing time T2 to arrive (which is "No" in step S102).
[0209] Figure 18This is a flowchart illustrating an example of the operation process when a server performs selection processing according to an embodiment of this disclosure.
[0210] Reference Figure 18 First, server 101 waits for the notification of the request information from the operation management device 301 (in step S201, this is "No").
[0211] Furthermore, when a request message is received from the operation management device 301 ("Yes" in step S201), the server 101 generates screen information M1 indicating the type of the event. For example, as described above, the server 101 generates screen information M1 indicating the type of event L1, event L2, and event L3 corresponding to the detection results of detection processes D1, D2, and D3, respectively (step S202).
[0212] Next, the server 101 sends the generated screen information M1 to the operation management device 301 (step S203).
[0213] Next, server 101 waits for the receipt of operation information indicating the user's operation on the event selection screen displayed in the operation management device 301 ("No" in step S204) and the arrival of processing time T2 ("No" in step S205).
[0214] Furthermore, in server 101, when operation information is received from operation management device 301 via communication unit 31 ("Yes" in step S204), output unit 34 performs selection processing to select one or more event detection units 32 from multiple event detection units 32 according to the selection operation performed by the user as indicated by the operation information. For example, as described above, output unit 34 retrieves detection result information indicating the detection result of the event detection unit 32 selected by the user from multiple detection result information stored in storage unit 35. Here, it is assumed that server 101 receives information indicating... Figure 6 The operation information C1 of the user's operation on the event selection screen G1 is shown, and the selection detection information K11 is obtained from the storage unit 35 based on the operation information C1 (step S206).
[0215] Next, the server 101 uses the selection detection information K11 obtained from the storage unit 35 to generate screen information M2 representing the event details screen G2 (step S207).
[0216] Next, the server 101 sends the generated screen information M2 to the operation management device 301 (step S208) and waits to receive new operation information from the operation management device 301 (no in step S204).
[0217] Furthermore, when the processing time T2 arrives (yes in step S205), the server 101 updates the screen information M1, sends the updated screen information M1 to the operation management device 301 (step S209), and waits for the receipt of new operation information from the operation management device 301 (no in step S204).
[0218] Figure 19 This is a diagram illustrating the processing sequence of the vehicle-mounted device, server, and operation management device in a vehicle service development support system according to an embodiment of the present disclosure.
[0219] Reference Figure 19 First, when the processing time T1 arrives, the vehicle device 201 generates a vehicle data set containing at least one of the following stored in the storage unit 15: accelerator information, brake information, vehicle speed information, position information, pressure information, and biological information (step S301).
[0220] Next, the vehicle-mounted device 201 performs the transmission process of sending the generated vehicle data set to the server 101 (step S302).
[0221] Next, the server 101 saves the vehicle data set received from the vehicle-mounted device 201 in the storage unit 35 (step S303).
[0222] Next, when processing time T2 arrives, server 101 uses multiple vehicle data sets generated by vehicle device 201 and stored in storage unit 35 during the period from 24 hours before processing time T2 to processing time T2, and performs detection processing D1, detection processing D2, detection processing D3, and detection processing D4 according to each driver ID (step S304).
[0223] Next, the operation management device 301 sends a request message for the notification of the request event to the server 101 (step S305).
[0224] Next, server 101 generates screen information M1 representing the types of events L1, L2, and L3 corresponding to the detection results of detection processing D1, detection processing D2, and detection processing D3, respectively (step S306).
[0225] Next, the server 101 sends the generated screen information M1 to the operation management device 301 (step S307).
[0226] Next, when the screen information M1 is received from the server 101, the operation management device 301 draws the event selection screen G1 on the web browser displayed on its own display unit based on the screen information M1 (step S308).
[0227] Next, the operation management device 301 sends operation information indicating the user's operation on the event selection screen G1 to the server 101. Here, it is assumed that the operation management device 301 sends operation information indicating... Figure 6 The operation information C1 shown is the user's operation on the event selection screen G1 (step S309).
[0228] Next, in server 101, when operation information C1 is received from operation management device 301 via communication unit 31, output unit 34 performs selection processing to select one or more event detection units 32 from a plurality of event detection units 32 according to the selection operation performed by the user as indicated by operation information C1. For example, as described above, output unit 34 obtains selection detection information K11 from storage unit 35 based on operation information C1 (step S310).
[0229] Next, the server 101 uses the selection detection information K11 obtained from the storage unit 35 to generate screen information M2 representing the event details screen G2 (step S311).
[0230] Next, the server 101 sends the generated screen information M2 to the operation management device 301 (step S312).
[0231] Next, when the screen information M2 is received from the server 101, the operation management device 301 draws the event details screen G21 on the web browser displayed on its own display unit based on the screen information M2 (step S313).
[0232] It should be noted that in the vehicle service development support system 501 of the present disclosure, the server 101 is configured to send screen information M1 representing the events corresponding to the detection results of each event detection unit 32 to the operation management device 301 as event information, but it is not limited to this. Alternatively, the server 101 may be configured to send screen information representing the types of events that have occurred in the events corresponding to each event detection unit 32 to the operation management device 301 as event information.
[0233] Furthermore, in the server 101 of the embodiments of this disclosure, each event detection unit 32 is configured to detect driver-related states during detection processing that detects states related to the occupants of the vehicle 1, but this is not a limitation. Alternatively, at least one of the multiple event detection units 32 may be configured to detect states related to passengers, either in place of driver-related states or in addition to driver-related states, during detection processing.
[0234] Furthermore, the physical condition detection unit 33 is configured to detect the driver's physical condition in the detection process D4, which detects the physical condition of the occupants of vehicle 1, but it is not limited to this. Alternatively, the physical condition detection unit 33 may be configured to detect the physical condition of the passengers in the detection process D4, either in place of the driver's physical condition or in addition to the driver's physical condition.
[0235] Furthermore, in the vehicle service development support system 501 of the embodiments of this disclosure, the server 101 is configured to accept selection operations of selecting one or more event detection units 32 from a plurality of event detection units 32, and perform selection processing according to the selection operations, but is not limited thereto. Alternatively, the server 101 may be configured to select one or more event detection units 32 from a plurality of event detection units 32 in a predetermined order.
[0236] Furthermore, in the server 101 of the embodiments of this disclosure, the event detection unit 32C is configured to perform detection processing D3 based on accelerator information, brake information, and vehicle speed information accumulated over multiple days, but it is not limited to this. Alternatively, the event detection unit 32C may be configured to perform detection processing D3 based on accelerator information, brake information, and vehicle speed information accumulated over a single day.
[0237] Furthermore, in the server 101 of the embodiments of this disclosure, the multiple event detection units 32 are configured to notify the passenger of evaluation results related to the passenger's driving status as events, but this is not a limitation. Alternatively, some or all of the multiple event detection units 32 may be configured to notify the passenger of other evaluation results related to the passenger that are different from the evaluation results of the driving status.
[0238] Furthermore, the server 101 in this embodiment of the present disclosure is configured to include an event detection unit 32A, an event detection unit 32B, and an event detection unit 32C. The event detection unit 32A notifies the user of an evaluation result related to the passenger's driving posture as event L1, the event detection unit 32B notifies the user of an evaluation result related to the passenger's fatigue level as event L2, and the event detection unit 32C notifies the user of an evaluation result related to the danger of driving by the passenger as event L3, but is not limited to this. Alternatively, the server 101 may be configured to include other event detection units besides the event detection units 32A, 32B, and 32C, which notify the user of evaluation results related to driving conditions other than the passenger's driving posture, passenger fatigue level, and driving danger as events. Alternatively, the server 101 may be configured to include these other event detection units in place of some or all of the event detection units 32A, 32B, and 32C.
[0239] Furthermore, in the vehicle service development support system 501 of this disclosure, the server 101 is configured to also output the detection result corresponding to the event notified by the selected event detection unit 32, but this is not a limitation. Alternatively, the server 101 may not output the detection result.
[0240] Furthermore, in the vehicle service development support system 501 of this disclosure, the server 101 is configured to accept a specified operation that specifies the conditions for the range of vehicle data used in the detection process, and also output a detection result based on the vehicle data that satisfies the conditions specified in the specified operation, but this is not a limitation. Alternatively, the server 101 may be configured not to have the function of accepting the specified operation.
[0241] Furthermore, in the vehicle service development support system 501 of this disclosure, the server 101 is configured to output information representing the time-series changes of the detection results corresponding to the events notified by the selected event detection unit 32, but this is not a limitation. Alternatively, the server 101 may be configured to output the detection results without establishing a correspondence with the measurement date and time.
[0242] Furthermore, some or all of the functions of the server 101 in the embodiments of this disclosure can also be provided through cloud computing. That is, the server 101 in the embodiments of this disclosure can also be a cloud server composed of multiple servers.
[0243] It should be considered that the above embodiments are exemplary in all respects and not restrictive. The scope of the invention is not shown by the foregoing description but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims.
[0244] The processes (functions) in the above-described embodiments are implemented by a processing circuit including one or more processors. Alternatively, the processing circuit may be composed of an integrated circuit consisting of one or more processors combined with one or more memories, various analog circuits, and various digital circuits. The one or more memories store programs (instructions) that cause the one or more processors to execute the processes. The one or more processors may execute the processes according to the programs read from the one or more memories, or they may execute the processes according to logic circuits pre-designed to execute the processes. The processors may be various processors suitable for computer control, such as CPUs (Central Processing Units), GPUs (Graphics Processing Units), DSPs (Digital Signal Processors), FPGAs (Field Programmable Gate Arrays), and ASICs (Application Specific Integrated Circuits). It should be noted that multiple physically separate processors may also cooperate to execute the processes. For example, the processors of each of several physically separate computers may collaborate via networks such as LANs (Local Area Networks), WANs (Wide Area Networks), and the Internet to execute the aforementioned processes. The programs may be installed in the memory from external server devices via these networks, or they may be stored on recording media such as CD-ROMs (Compact Disc Read Only Memory), DVD-ROMs (Digital Versatile Disk Read Only Memory), and semiconductor memory, and then installed in the memory from these recording media.
[0245] The above description includes the following features.
[0246] [Appendix 1] A vehicle service development support apparatus includes: an acquisition unit for acquiring vehicle-related data; multiple detection units for performing detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle, the multiple detection units distributing event-related notifications based on the detection results of the detection processing; and an output unit for performing selection processing to select one or more of the multiple detection units and outputting event-related information based on the detection results of the selected detection units, wherein the multiple detection units include: a first detection unit for performing detection processing related to the occupant's driving posture; a second detection unit for performing detection processing related to the number of times the occupant adjusts their seating posture; and a third detection unit for performing detection processing related to the occupant's driving state.
[0247] Explanation of reference numerals in the attached figures 1: Vehicle; 11: In-vehicle communication unit; 12: Seat pressure information acquisition unit; 13: Biological information acquisition unit; 14: External communication unit; 15, 34: Storage unit; 21: Pressure sensor; 31: Communication unit; 32, 32A, 32B, 32C: Event detection unit; 33: Body condition detection unit; 34: Output unit; 51, 51A, 51B: Communication bus; 61, 61A, 61B, 61C, 61D: On-board equipment; 62: Pressure sensor; 63: Vital signs sensor; 101: Server; 151: External network; 201: On-board device; 301: Operation management device; 501: Vehicle service development support system.
Claims
1. A vehicle service development support device, comprising: The acquisition department acquires vehicle-related data; Multiple detection units perform detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle. The multiple detection units then issue event-related notifications based on the detection results of the detection processing. The output unit performs a selection process to select one or more of the multiple detection units, and outputs information related to the event based on the detection results of the selected detection units.
2. The vehicle service development support device according to claim 1, wherein, The vehicle service development support device also includes a receiving unit, which accepts selection operations for choosing one or more of the plurality of testing units. The output unit performs the selection process according to the selection operation received by the receiving unit.
3. The vehicle service development support device according to claim 1 or 2, wherein, The acquisition unit acquires the data accumulated over several days. At least one of the plurality of detection units performs the detection processing based on the data acquired by the acquisition unit over several days.
4. The vehicle service development support device according to claim 3, wherein, The plurality of detection units includes the detection unit that notifies the event of an evaluation result related to the driving status of the occupant in the vehicle.
5. The vehicle service development support device according to any one of claims 1 to 4, wherein, The plurality of detection units include at least one of the following: the detection unit that notifies the event of an evaluation result related to the driver's driving posture; the detection unit that notifies the event of an evaluation result related to the driver's fatigue level while driving the vehicle; and the detection unit that notifies the event of an evaluation result related to the danger of driving by the driver.
6. The vehicle service development support device according to any one of claims 1 to 5, wherein, The output unit also outputs the detection result corresponding to the event notified by the selected detection unit.
7. The vehicle service development support device according to claim 6, wherein, The vehicle service development support device also includes a receiving unit, which accepts specified operations that define the conditions for the range of data used in the detection process. The output unit also outputs the detection result based on the data that satisfies the conditions specified in the designated operation accepted by the receiving unit.
8. The vehicle service development support device according to claim 6 or 7, wherein, The acquisition unit acquires the time series data. Each of the detection units performs the detection processing based on the time-series data acquired by the acquisition unit. The output unit also outputs information representing the time-series change of the detection result corresponding to the event notified by the selected detection unit.
9. A service providing device, comprising: The communications unit receives information related to the event from the vehicle service development support device as described in any one of claims 1 to 8; and The processing unit performs processing based on information related to the event received through the communication unit to provide services related to the passenger.
10. A vehicle service development support method, which is a vehicle service development support method in a vehicle service development support device, wherein, The vehicle service development support method includes the step of acquiring vehicle-related data. The vehicle service development support device includes multiple detection units. These detection units perform detection processing based on the acquired data to detect multiple states related to the vehicle's occupants. Based on the detection results, the multiple detection units issue event-related notifications. The vehicle service development support method also includes the following steps: A selection process is performed to select one or more of the plurality of detection units, and information related to the event is output based on the detection results of the selected detection units.
11. A vehicle service development support program, which is used in a vehicle service development support device, wherein, The vehicle service development support program enables a computer to function as an acquisition unit, multiple detection units, and an output unit. The acquisition unit acquires vehicle-related data, the multiple detection units perform detection processing based on the data acquired by the acquisition unit to detect multiple states related to the occupants of the vehicle, the multiple detection units send event-related notifications based on the detection results of the detection processing, and the output unit performs selection processing to select one or more of the multiple detection units and outputs event-related information based on the detection results of the selected detection units.
Citation Information
Patent Citations
Computational platform for developing and deploying sensor database applications and services
JP2014534487A
Game machine
JP2024029518A
