Terminal, car management system, and setting method

Abstract

To facilitate setting of upload by a manager.SOLUTION: The terminal includes a controller, and the controller is configured to receive an upload setting operation in a group unit to which a driver of the terminal belongs, and collectively perform an upload setting in the group unit according to the setting operation.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present invention relates to a terminal device, a vehicle management system, and a setting method. [Background technology]

[0002] Conventionally, there is an information management device that manages data uploaded from a vehicle. For example, Patent Document 1 discloses a technology for uploading only a portion of data designated by an administrator or the like, with the aim of reducing the amount of data uploaded. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Publication No. 2019-79422 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the conventional technology does not take into consideration how easily an administrator can configure upload settings, and there is room for improvement in terms of making it easier for an administrator to configure upload settings.

[0005] The present invention has been made in view of the above, and has an object to provide a terminal device, a vehicle management system, and a setting method that enable an administrator to easily set up uploads. [Means for solving the problem]

[0006] In order to solve the above-mentioned problems and achieve the objectives, the terminal device of the present invention is a terminal device that provides data uploaded from vehicles to an administrator, and has a controller, and the controller accepts upload setting operations on a group basis to which the driver of the vehicle belongs, and performs upload settings collectively on a group basis in accordance with the setting operations. [Effects of the Invention]

[0007] According to the present invention, upload settings can be made collectively for each group of drivers, which makes it easier for the administrator to make upload settings. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating an outline of a vehicle management system. [Figure 2] FIG. 2 is a diagram showing an example of an upload setting screen. [Figure 3] FIG. 3 is a diagram illustrating an outline of a setting method according to an embodiment. [Figure 4] FIG. 4 is a block diagram of the administrator terminal. [Figure 5] FIG. 5 is a diagram illustrating an example of the driver information. [Figure 6] FIG. 6 is a diagram illustrating an example of the setting information. [Figure 7] FIG. 7 is a flowchart showing a processing procedure executed by the administrator terminal. DETAILED DESCRIPTION OF THE INVENTION

[0009] The terminal device, vehicle management system, and setting method disclosed in the present application will be described below with reference to the accompanying drawings. Note that the present invention is not limited to the following embodiments. Note that in this disclosure, the terminal device will be described as an administrator terminal 100.

[0010] First, an overview of a vehicle management system according to an embodiment will be described using Fig. 1. Fig. 1 is an explanatory diagram of an overview of a vehicle management system. As shown in Fig. 1, a vehicle management system S according to an embodiment includes a server device 1, an in-vehicle device 50, and an administrator terminal 100. For ease of explanation, Fig. 1 illustrates one in-vehicle device 50 and one administrator terminal 100, but the vehicle management system S actually includes a plurality of in-vehicle devices 50 and a plurality of administrator terminals 100.

[0011] The vehicle management system S is a system that is introduced into, for example, a company or the like and manages the vehicles used by each company. More specifically, the vehicle management system S is a system that manages various commercial vehicles such as trucks and taxis.

[0012] 1, the vehicle management system S includes a server device 1, an in-vehicle device 50, and an administrator terminal 100. For ease of explanation, FIG. 1 shows one in-vehicle device 50 and one administrator terminal 100, but in reality, the vehicle management system S includes multiple in-vehicle devices 50 and multiple administrator terminals 100.

[0013] The server device 1 manages various data transmitted from the in-vehicle device 50 mounted in each vehicle C. The in-vehicle device 50 is mounted in the vehicle C and uploads various data to the server device 1 and the administrator terminal 100.

[0014] 1, the in-vehicle device 50 is a drive recorder equipped with a communication function. However, the in-vehicle device 50 is not limited to a drive recorder, and may be any other device such as a driver's smartphone as long as it is capable of transmitting and receiving various data of the vehicle C.

[0015] The administrator terminal 100 corresponds to an example of a terminal device according to the embodiment, and is a terminal device owned by an administrator. The administrator is a person in charge of managing each vehicle C that is a management target in each company or each department. In the example shown in FIG. 1, the administrator terminal 100 is a PC (Personal Computer), but the administrator terminal 100 may also be a tablet terminal or the like.

[0016] Next, an outline of a series of processes performed by the vehicle management system S will be described. As shown in Fig. 1, the in-vehicle device 50 detects an event based on various driving data of the vehicle C (step S1).

[0017] The events are, for example, sudden acceleration, lane departure, dozing at the wheel, smartphone operation, etc. The in-vehicle device 50 detects sudden acceleration as an event based on information related to the vehicle's traveling speed, and detects lane departure as an event based on a forward video image captured by the drive recorder of the vehicle C.

[0018] Furthermore, the in-vehicle device 50 detects events such as dozing at the wheel or operating a smartphone based on the in-vehicle video captured by the drive recorder. When the in-vehicle device 50 detects the above-mentioned events, it transmits event data to the server device 1 (step S2).

[0019] Then, the server device 1 notifies the event data to the administrator terminal 100 of the administrator of the vehicle C (step S3). At this time, the in-vehicle device 50 transmits data of contents preset by the administrator as event data for each detected event.

[0020] In this way, in the vehicle management system S, the administrator sets the data to be requested to be uploaded for each event, and the in-vehicle device 50 uploads the data set by the administrator for each event.

[0021] Here, the upload setting screen will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the upload setting screen. When the administrator sets up uploads, the setting screen shown in Fig. 2 is displayed on the administrator terminal 100. As shown in Fig. 2, the administrator can set up uploads for each event.

[0022] In the example shown in Figure 2, the administrator can set for each event: video, time lapse, still image, result only (with sensor data), result only (without sensor data), or no notification. Video is video captured by a drive recorder when the corresponding event occurs, and time lapse is images obtained by thinning out the video at a predetermined interval.

[0023] The still image is a still image taken by the drive recorder when the corresponding event occurred. The result only notifies that the event was detected, and if there is sensor data, the sensor data at the time of the event occurrence will also be uploaded. If there is no sensor data, the sensor data at that time will not be uploaded.

[0024] Furthermore, "no notification" indicates that even if an event is detected on the in-vehicle device 50 side, the event data itself will not be uploaded. Note that "no notification" may be set so that the in-vehicle device 50 side does not detect the event itself. The administrator can set upload for each event on the setting screen shown in FIG. 2.

[0025] In this way, the vehicle management system S according to the embodiment accepts a selection operation of data to be uploaded for each event to be uploaded. This allows the vehicle management system S to realize uploading according to the administrator's wishes.

[0026] In addition, in the present disclosure, the type of data to be uploaded for each event can be set from among video (including time lapse), still images, and sensor data. If the uploaded data is video, the administrator can grasp more detailed information about the event. If the uploaded data is still images, the administrator can grasp the instantaneous situation of the event. If the uploaded data is sensor data, the administrator can grasp the status of the sensor at the time the event occurred.

[0027] In other words, in the vehicle management system S of the embodiment, the type of data uploaded for each event can be set from among video (including time lapse), still images, and sensor data, making it possible to notify the administrator of the event status at the granularity required.

[0028] However, if an administrator were to configure upload settings for each driver, the administrator would have to configure the settings for each driver, which would result in inefficient work.

[0029] Therefore, in the vehicle management system S according to the embodiment, upload settings are accepted on a group basis. Fig. 3 is a diagram illustrating an outline of the setting method according to the embodiment. As shown in Fig. 3, when configuring upload settings, the administrator terminal 100 displays the following items: driver group, personal settings, and upload settings.

[0030] The administrator can set the members of each group using the driver group. After setting the members of the driver group, the administrator can set the upload settings for the corresponding group by selecting the desired upload settings from the upload settings.

[0031] The upload setting options (settings a, b, and c shown in the figure) can be set from the setting screen shown in Figure 2. Also, as shown in Figure 3, the administrator can set upload settings for each driver using personal settings.

[0032] In this case, the administrator selects the desired upload setting from the upload setting options for each driver.

[0033] In this way, the vehicle management system S accepts upload settings on a group basis, which makes it easier for the administrator to set up uploads.

[0034] Next, a configuration example of the administrator terminal 100 will be described with reference to Fig. 4. Fig. 4 is a block diagram of the administrator terminal 100. As shown in Fig. 4, the administrator terminal 100 is connected to a display unit 110 and an operation unit 111, and is also connected to the server device 1 via a network N.

[0035] The display unit 110 is a display of various types, and displays the setting screen shown in Fig. 2 etc. based on operations by the administrator. The operation unit 111 is a keyboard, mouse etc., and accepts various operations from the administrator.

[0036] 4, the administrator terminal 100 includes a communication unit 102, a controller 103, and a storage unit 104. The communication unit 102 is realized by, for example, a network interface card (NIC) or the like. The communication unit 102 is connected to a communication network via a wired or wireless connection.

[0037] The controller 103 includes a microcomputer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM, etc., and various other circuits. The controller 103 executes the overall operation of the administrator terminal 100 by having the CPU execute a program stored in the ROM using the RAM as a work area. Note that the controller 103 may be partially or entirely configured with hardware such as an ASIC (Application Specific Integrated Circuit) or FPGA (Field Programmable Gate Array).

[0038] The storage unit 104 is, for example, a RAM (Random Access Memory) or a data flash. The storage unit 104 can store information about various programs. The administrator terminal 100 may also acquire the above-mentioned programs and various information via other computers or portable recording media connected via a wired or wireless network.

[0039] In the present disclosure, the storage unit 104 stores various information related to upload settings. For example, the storage unit 104 stores driver information and setting information related to drivers. Here, the driver information stored in the storage unit 104 will be described with reference to FIG. 5.

[0040] Fig. 5 is a diagram showing an example of driver information. As shown in Fig. 5, the driver information is information in which a "driver ID," a "group ID," a "driver characteristic," a "setting ID," and the like are associated with one another.

[0041] The "driver ID" is an identifier for identifying each driver, and the "group ID" is an identifier for identifying the group to which the driver identified by the corresponding driver ID belongs.

[0042] The "driver characteristics" are driving characteristics of a driver identified by a corresponding driver ID. In the present disclosure, the driver characteristics are information relating to the results of a driving diagnosis of a driver diagnosed by the server device 1.

[0043] The "setting ID" is an identifier for identifying the setting information of the upload setting set in the driver identified by the corresponding driver ID. Next, the setting information associated with the setting ID will be further explained with reference to FIG. 6.

[0044] Fig. 6 is a diagram showing an example of the setting information. As shown in Fig. 6, the setting information is information in which "setting ID," "event 1," "event 2," "event 3," etc. are associated with one another.

[0045] "Setting ID" corresponds to the "Setting ID" shown in Figure 5 and is an identifier for identifying the setting information of the upload setting. "Event 1," "Event 2," and "Event 3" are the setting contents of the upload setting for each event. Events 1 to 3 correspond to sudden acceleration, lane departure, falling asleep at the wheel, smartphone operation, etc., respectively.

[0046] As shown in FIG. 6, each setting ID is associated with the upload setting content for each event, that is, the type of data to be requested to be uploaded when an event is detected.

[0047] 6, the data types are "video," "no notification," "still image," "time lapse," "sensor data," and "notification only." As mentioned above, the administrator can also set "no notification."

[0048] That is, by setting "no notification" for events with low importance, the administrator can eliminate unnecessary notifications from the server device 1. In other words, by making such a setting, the administrator can receive notifications only for events with high importance, and can therefore allocate time resources to events with high importance.

[0049] Returning to the explanation of Fig. 4, the controller 103 will be described. The controller 103 accepts an upload setting operation for each department to which the vehicle driver belongs, and performs upload settings for each department collectively in accordance with the setting operation.

[0050] Specifically, the controller 103 sets the type of data to be uploaded for each event from among video, still images, and sensor data, and further accepts a setting as to whether or not notification is required for each event.

[0051] The controller 103 receives the data type and notification requirement for each event via the setting screen shown in Fig. 2 and registers the information as setting information (see Fig. 6) in the storage unit 104. The controller 103 also receives the setting of the group to which the driver belongs based on the setting operation of the administrator, and creates the group. The controller 103 then receives the upload setting operation on a group-by-group basis, and performs the upload setting collectively on a group-by-group basis.

[0052] The controller 103 can also accept an upload setting operation for each driver, and sets the upload for each driver. In this case, the controller 103 sets the upload setting for the driver to the recommended setting based on the results of the driving evaluation of the driver.

[0053] More specifically, the controller 103 sets the upload settings to the recommended settings for drivers whose driving evaluation results do not meet the standards. Specifically, the controller 103 refers to the driving tendencies of the drivers shown in Fig. 5 and determines whether the driving evaluation of each driver meets the standards.

[0054] The controller 103 sets a recommended setting for a driver whose driving evaluation is determined not to satisfy the standard. For example, the recommended setting is a setting that uploads more detailed data at the time of the event, such as video, when a target event is detected.

[0055] In this way, the controller 103 can avoid setting errors by the administrator by setting the recommended settings for a specific driver.

[0056] When the controller 103 completes the upload settings for each group or each driver, it notifies the server device 1 of this information via the network N. As a result, the server device 1 updates the settings of each in-vehicle device 50 so that uploading is performed according to the settings made by the administrator.

[0057] As a result, in the vehicle management system S according to the embodiment, the manager collects and checks only the data that is necessary, thereby reducing the number of items to be checked and the amount of communication.

[0058] Next, a processing procedure executed by the administrator terminal 100 according to the embodiment will be described with reference to Fig. 7. Fig. 7 is a flowchart showing the processing procedure executed by the administrator terminal 100. The processing shown in Fig. 7 is executed by the controller 103 of the administrator terminal 100 when the administrator sets up upload settings.

[0059] 7, the controller 103 receives an upload setting request from an administrator (step S101). Subsequently, the controller 103 determines whether or not the administrator has completed the upload setting operation (step S102).

[0060] If the controller 103 determines that the setting operation is ongoing (step S102; No), it continues the determination process of step S102 until the setting operation is completed. If the controller 103 determines that the setting operation is completed (step S102; Yes), it performs upload settings collectively in group units (step S103).

[0061] Then, the controller 103 notifies the server device 1 of the setting contents (step S104), and ends the process.

[0062] As described above, the administrator terminal 100 according to the embodiment is a terminal device that provides the administrator with data uploaded from vehicles, and has a controller 103. The controller 103 accepts upload setting operations on a group basis to which the vehicle drivers belong, and performs upload settings collectively on a group basis in accordance with the setting operations.

[0063] In this way, according to the administrator terminal 100 according to the embodiment, upload settings can be made collectively for each driver's affiliation, which makes it easier for the administrator to make upload settings.

[0064] Further advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents. [Explanation of symbols]

[0065] 1. Server device 50 Onboard equipment 100 Administrator terminal 102 Communications Department 103 Controller 104 Storage section 110 Display section 111 Operation section S Vehicle management system

Claims

1. A terminal device that provides data uploaded from a vehicle to an administrator, a controller; The controller Accepting an upload setting operation for each department to which the driver of the vehicle belongs; The upload settings are performed collectively for each affiliation in accordance with the setting operation. Terminal device.

2. The controller It is also possible to accept upload setting operations on a driver-by-driver basis, and upload settings are made on a driver-by-driver basis. The terminal device according to claim 1 .

3. The controller For each event to be uploaded, you can set the data you want to upload. The terminal device according to claim 1 .

4. The controller Set the type of data to be uploaded for each event from among video, still images, and sensor data. The terminal device according to claim 3.

5. The controller Accepts settings for whether or not notifications are required for each of the above events. The terminal device according to claim 3 .

6. The controller Setting the driver's upload settings to recommended settings based on the results of the driver's driving evaluation. The terminal device according to claim 1 .

7. The controller Set the recommended settings for drivers whose driving evaluation results do not meet the standards. The terminal device according to claim 6.

8. A terminal device according to any one of claims 1 to 7; a server device that transmits data uploaded from the vehicle to the terminal device; an in-vehicle device that uploads data to the server device; A vehicle management system comprising:

9. A setting method executed by a terminal device that provides data uploaded from a vehicle to an administrator, Accepting an upload setting operation for each department to which the driver of the vehicle belongs; The upload settings are performed collectively for each affiliation in accordance with the setting operation. How to set it up.

Images