JP2024052949A - Information processing method, information processing device, and program. - Google Patents

Abstract

The present invention provides an apparatus and method for realizing appropriate disclosure restrictions on the movement history, etc., of a moving object.
[Solution] An information processing method executed by a system including an information display device includes acquiring mobile body information regarding a mobile body, and if no restrictions are set on viewing of the mobile body information, displaying the mobile body information on the information display device, and if restrictions are set, restricting the display of the mobile body information on the information display device.
[Selected Figure] Figure 1

Description

The present invention relates to information processing technology for managing the movement history information of moving objects.

There is a social demand for more efficient management of mobile objects and their users (drivers), such as in fleet management, which manages multiple mobile objects. For example, Patent Literature 1 discloses a traffic management device for managing the operational status of vehicles.

JP 2015-38672 A

However, when collecting movement history and other data related to a mobile object, there is a problem in that the collected movement history and other data may be viewed by the system administrator or other users more than necessary, giving the user of the mobile object a sense of discomfort as if they are being excessively monitored.

The present invention aims to solve the above problems by implementing appropriate disclosure restrictions on the movement history, etc., of moving objects.

According to one aspect of the present invention, there is provided an information processing method executed by a system including an information display device, which includes acquiring mobile body information related to a mobile body, and if no restrictions are set on the viewing of the mobile body information, displays the mobile body information on the information display device, and if restrictions are set, restricts the display of the mobile body information on the information display device.

The information processing method according to the present invention can determine whether or not to display mobile object information on an information display device based on the restriction settings regarding the viewing of mobile object information, thereby providing a comfortable work environment for users of mobile objects.

FIG. 1 is a diagram showing an example of a system configuration of a mobile object management system according to an embodiment. FIG. 4 is a block diagram showing an example of information stored in a storage unit of the server according to the first embodiment. FIG. 4 is a diagram showing an example of vehicle registration data according to the first embodiment. FIG. 4 is a diagram showing an example of user registration data according to the first embodiment. FIG. 2 is a diagram showing an example of a fleet management database according to the first embodiment. 10 is a flowchart showing an example of the flow of information processing according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the in-vehicle terminal according to the first embodiment. FIG. 4 is a diagram showing an example of a display screen displayed on a display unit of the administrator terminal according to the first embodiment. FIG. 11 is a diagram showing an example of user registration data according to a first modified example. FIG. 11 is a diagram showing an example of a restriction target item table according to a first modified example. 10 is a flowchart showing an example of the flow of information processing according to the second embodiment. 10 is a flowchart showing an example of the flow of information processing according to the second embodiment. FIG. 11 is a diagram showing an example of a display screen displayed on a display unit of an administrator terminal according to the second embodiment. 10 is a flowchart showing an example of the flow of information processing according to a second modified example. 13 is a flowchart showing an example of the flow of information processing according to the third embodiment. FIG. 13 is a diagram showing an example of a display screen displayed on a display unit of an administrator terminal according to the third embodiment. FIG. 13 is a diagram showing a specific example of a relationship between an electronic map area and vehicle position coordinates according to a third modified example.

Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.
In the description of the drawings, the same elements are denoted by the same reference numerals, and duplicate descriptions may be omitted.
Furthermore, the components described in these embodiments are merely examples and are not intended to limit the scope of the present invention.

[Embodiment]
Hereinafter, an embodiment for realizing the information processing technology of the present invention will be described.
The contents described in this embodiment are applicable to any of the other examples and modified examples.

FIG. 1 is a diagram showing an example of a system configuration of a mobile object management system 1 according to the present embodiment.
A system is a mechanism that includes a plurality of information processing devices and that executes processing in cooperation with each other.
In the mobile object management system 1, for example, a server 10, a plurality of in-vehicle terminals 40, and an administrator terminal 20 are communicatively connected via a network 30 (e.g., the Internet). Note that Fig. 1 illustrates only one representative component, the in-vehicle terminal 40. In addition, in the mobile object management system 1, a plurality of servers 10 may be connected, and a plurality of administrator terminals 20 may be connected.

The server 10 has a function of, for example, acquiring vehicle information related to a vehicle driven by a user via the in-vehicle terminal 40 and processing the vehicle information, status information, and the like.
Here, mobile object information refers to information acquired in a time series regarding a mobile object, and includes, for example, the mobile object's position information, acceleration information, operation information, cargo portion temperature information, tire air pressure information, etc., but is not limited to these and may be composed of other appropriate information.
The situation information is, for example, information about the user's situation that is input by the user to the in-vehicle terminal 40, and will be described in detail later.

Figure 1 shows an example of the functional configuration of server 10. Server 10 is configured, for example, as a single server, or as a distributed server consisting of separate servers for each function. Server 10 can also be configured as a distributed virtual server created in a cloud environment called a cloud server. As shown in Figure 1, server 10 is configured to include, for example, a processing unit 11, a memory unit 12, and a communication unit 17.

The processing unit 11 is a processing device that comprehensively controls each part of the server 10 according to various programs such as system programs stored in the memory unit 12 and performs various processes related to information processing, and is configured with processors such as a CPU, GPU, and DSP, and integrated circuits such as ASICs.

The storage unit 12 is a storage device that includes volatile or non-volatile memory such as ROM, EEPROM, flash memory, RAM, etc., a hard disk drive, etc. The storage unit 12 stores, for example, various programs such as programs corresponding to the processes performed in this embodiment and system programs, mobile object information received from the in-vehicle terminal 40, and the results of processing by the various programs.

The communication unit 17 is a communication device for transmitting and receiving information used within the server 10 to and from external devices via a network. As a communication method for the communication unit 17, various methods can be applied, such as a wired connection via a cable that complies with a specific communication standard such as Ethernet or USB (Universal Serial Bus), a wireless connection using a wireless communication technology that complies with a specific communication standard such as Wi-Fi (registered trademark) or 5G (fifth generation mobile communication system), and a connection using short-range wireless communication such as Bluetooth (registered trademark).

The administrator terminal 20 is a device used by, for example, an administrator who manages mobile objects to grasp the status of the mobile objects. The administrator terminal 20 is realized, for example, by a laptop personal computer or a tablet terminal. The administrator terminal 20 receives information such as the results of processing by the server 10, and displays information related to mobile object management. An example of a display related to mobile object management is a display in which an object (vehicle icon) indicating the position coordinates of each mobile object is superimposed on an electronic map based on the acquired mobile object position information.

Figure 1 shows an example of the functional configuration of the administrator terminal 20. As shown in Figure 1, the administrator terminal 20 is configured to include, for example, a processing unit 21, a storage unit 22, an operation unit 23, a display unit 24, a sound input unit 25, a sound output unit 26, and a communication unit 27.

The processing unit 21 is a processing device that comprehensively controls each part of the administrator terminal 20 according to various programs such as system programs stored in the memory unit 22 and performs various processes related to information processing, and is configured with processors such as a CPU, GPU, and DSP, and integrated circuits such as ASICs.

The memory unit 22 is a storage device configured to include volatile or non-volatile memory such as ROM, EEPROM, flash memory, RAM, etc., a hard disk drive, etc., similar to the memory unit 12. The memory unit 22 stores, for example, various programs such as programs corresponding to the processes performed in this embodiment and system programs, information received from the server 10, etc., and processing results by various programs, etc.

The operation unit 23 is configured with input devices such as a keyboard and a mouse that allow the user to input various operations to the server. Operation signals corresponding to user operations are output from the operation unit 23 to the processing unit 21.

The display unit 24 is a display device including an LCD (Liquid Crystal Display) or an OELD (Organic Electro-luminescence Display), and performs various displays based on the display signal output from the processing unit 21.

The operation unit 23 has a touch panel (not shown) that is integral with the display unit 24, and this touch panel may function as an input interface between the user (administrator) and the administrator terminal 20.

The sound input unit 25 is a sound input device that includes a microphone, an A/D converter, etc., and performs various sound inputs based on the sound input signal input to the processing unit 21.

The sound output unit 26 is a sound output device that includes a D/A converter, a speaker, etc., and outputs various sounds based on the sound output signal output from the processing unit 21.

The communication unit 27 is a communication device for transmitting and receiving information used within the administrator terminal 20 between external devices and the network 30. The configuration of the communication unit 27 can be configured in the same way as the communication unit 17, for example, and therefore a detailed description thereof will be omitted.

The in-vehicle terminal 40 has a function to perform processing to acquire vehicle information related to a vehicle driven by a user (driver) and transmit the information to the server 10. The in-vehicle terminal 40 may also receive information from an external source such as the server 10 and perform processing such as displaying the information.

Figure 1 shows an example of the functional configuration of the in-vehicle terminal 40. As shown in Figure 1, the in-vehicle terminal 40 is configured to include, for example, a processing unit 41, a memory unit 42, an operation unit 43, a display unit 44, a sound input unit 45, a sound output unit 46, a communication unit 47, an imaging unit 48, a clock unit 49A, and a location information acquisition unit 49B.

The processing unit 41 to the sound output unit 46 can be configured in the same way as the processing unit 21 to the sound output unit 26 of the administrator terminal 20, for example, so a detailed description thereof will be omitted.

The communication unit 47 is configured to be able to communicate with a network NW such as the Internet. The communication unit 27 can be configured, for example, in the same manner as the communication unit 17. Note that the communication by the communication unit 47 may, for example, transmit information to a roadside device installed at the side of the road, and the roadside device may be connected to the network 30, thereby indirectly communicating with the server 10, etc.

The imaging unit 48 is an imaging device composed of a camera or the like, and acquires image data (still images and moving images) to be input to the processing unit 21. The imaging unit 48 may be configured to capture images only when a specific event occurs (for example, a dangerous situation in the vehicle detected by detection of sudden acceleration/deceleration, sudden steering, etc.).

The clock unit 49A is a built-in clock of the in-vehicle terminal 40, and outputs time information (timekeeping information) acquired based on a clock using, for example, a crystal oscillator. The clock unit 49A may also acquire time information via the communication unit 47 and the network 30 in accordance with the NITZ (Network Identity and Time Zone) standard or the like.

The location information acquisition unit 49B acquires location information (e.g., latitude and longitude information) of the vehicle-mounted terminal 40 in chronological order based on radio waves arriving from GNSS satellites (e.g., GPS satellites), for example. That is, it is possible to acquire location information of the mobile body on which the vehicle-mounted terminal 40 is installed in chronological order. Note that the location information acquisition unit 49B is not limited to such a configuration, and any location information acquisition method may be applied. For example, the location information of the vehicle-mounted terminal 40 may be acquired by receiving radio waves, which include location information specific to a roadside unit installed on the side of the road, when a mobile body equipped with the vehicle-mounted terminal 40 approaches the roadside unit.

In addition, the in-vehicle terminal 40 may be configured to include multiple devices, including a device installed in a vehicle to collect mobile object information (e.g., a cigarette lighter-type sensing device or a sensing device integrated with a drive recorder) and a device held by a user who is a passenger in the mobile object (e.g., a smartphone).

In this case, the device held by the user, who is a passenger in the vehicle, is not limited to a smartphone or the like. For example, it may be a head-up display or a car navigation device. Or, it may be a smart speaker or the like that allows communication with the user through voice input and output.

In this case, the device for collecting mobile object information may be any IoT device, or even a part of a mobile object, and the configuration is not particularly limited as long as it has each of the components of the in-vehicle terminal 40, either individually or in combination.

Network 30 is a communications network that connects devices together via wired or wireless connections, or both.

[First embodiment]
The first embodiment is an embodiment in which a user (driver) who is a passenger in a mobile object selects mobile object information to be shared, thereby restricting the administrator or the like from viewing the mobile object information.
The contents described in the first embodiment are applicable to any of the other embodiments and modifications.

In this embodiment, a vehicle management system is illustrated as an example of a mobile object management system. Furthermore, an application for users (e.g., an administrator or a driver) provided in the vehicle management system is referred to as a vehicle management application. Furthermore, a user of the administrator terminal 20 (hereinafter referred to as the "administrator") and a user of the in-vehicle terminal 40 (hereinafter referred to as the "driver") are collectively referred to as the "user" of the vehicle management system. Note that, if the administrator also serves as the driver, there is no need to distinguish between the administrator terminal 20 and the in-vehicle terminal 40.

FIG. 2 is an example of information stored in the storage unit 12 of the server 10 in this embodiment.
The storage unit 12 stores, for example, vehicle registration data 121, user registration data 123, electronic map data 125, and an operation management database 127.

The vehicle registration data 121 is registration data relating to vehicles managed in a vehicle management system, and an example of the data structure is shown in FIG.
The vehicle registration data 121 stores, in association with each other, for example, a vehicle ID, a vehicle name, a vehicle number, and other registration information.

The vehicle ID is information used to identify a vehicle managed in the vehicle management system. This vehicle ID is preferably a unique value for each vehicle, and is set and stored, for example, by the server 10 for each vehicle.

The vehicle name is the name of the vehicle in the vehicle management system. For example, the name specified by the administrator when registering the vehicle in the vehicle management system is stored.

The vehicle number is the number written on the vehicle's license plate (automobile registration plate). The vehicle number may also be used as the vehicle ID.

Other registration information may include various information such as the terminal ID (e.g., IMEI (International Mobile Equipment Identity)) of the in-vehicle terminal 40 mounted in the vehicle, vehicle model, vehicle manufacturer, first year of registration, mileage, etc.

The user registration data 123 is registration data for each user (account) who uses the vehicle management system (vehicle management application), and an example of the data configuration of first user registration data 123A, which is an example of the data configuration, is shown in FIG.
In the user registration data 123A, for example, a user ID, a user name, a job title class, a business status, and other registration information are stored in association with each other.

The user ID is information for identifying a user (account) who uses the vehicle management system (vehicle management application). This user ID is preferably a value unique to each user, and is set and stored by the server 10 for each user, for example.
In addition, when a user who operates a specific vehicle is uniquely determined, the vehicle ID may be set to be equal to the user ID. In this case, the in-vehicle terminal 40 may be configured as an integrated device for collecting mobile object information and a device held by the driver of the mobile object.

The user name is the name of the user who uses the vehicle management system. For example, the name that the user registers when using the vehicle management application is stored.

The position class is information about the type of the user's role in the vehicle management system, and is, for example, an identification flag set by the administrator. In this example, for example, the position class of the vehicle administrator is expressed as "manager," and the position class of the vehicle driver is expressed as "staff."
The position class is not limited to two types. For example, the position class of a manager who has full operational authority over the vehicle management system may be defined as "director." Managers and staff may be further subdivided.

The work status is information about the type of each working situation of the user, and is, for example, information that is sequentially input to the in-vehicle terminal 40 or the manager terminal 20. The work status is an example of situation information.
In this example, the following four types of business status are shown.
・While performing duties (e.g., while driving to a destination)
・While on duty (during working hours and on standby or patrol, etc.)
・During rest (e.g. during working hours but taking a temporary break)
Outside working hours The work status may be automatically updated according to a work schedule stored in the other registration information, for example. Other work statuses may also be defined.

Other registration information may include, for example, authentication information for the vehicle management application, the terminal ID of the device held by the vehicle driver, the user's home address, business address, and other information.

The electronic map data 125 is information about an electronic map. Note that the server 10 may not store the electronic map data 125, but may receive it successively from an electronic map data server (not shown).

The operation management database 127 is a database for storing and managing information relating to vehicle operation, and an example of the data structure is shown in FIG.
The traffic management database 127 stores traffic management data as management data for each vehicle operation unit (for example, from when the ignition of the vehicle is turned on to when the ignition is turned off). The traffic management data is an example of mobile object information.

Each operation management data may store, for example, an operation management ID, a user ID, a vehicle ID, a business status, vehicle operation data, and operation authority management data. The operation management data may also store information about the vehicle's departure point, intermediate points, and destination. Information about the vehicle's departure point and destination is an example of status information.

The fleet management ID is identification information for identifying the fleet management data, and is set and stored as a unique value by the server 10, for example.
The user ID stores the user ID of the user who operated the vehicle.
The vehicle ID stores the vehicle ID of the operated vehicle.
The business status stores, for example, the business status of the user while the vehicle is being operated.

Vehicle operation data is data for storing various information about a vehicle that has been operated, and for example, the date and time, vehicle position coordinates, acceleration status, drive recorder image URI, and other information are stored in association with each other. Vehicle operation data is an example of mobile object information.

As the date and time, for example, the date and time when the vehicle was operated is stored for each unit time (for example, 10 seconds).
The vehicle position coordinates store the vehicle's position information (e.g., latitude, longitude, and altitude) at that date and time. Note that the vehicle position coordinates may also include information about the vehicle's traveling direction (travel information) obtained by the electronic compass of the in-vehicle terminal 40.
The acceleration status stores information about the acceleration of the vehicle at that date and time. Note that the acceleration status may also include information about the vehicle speed at that date and time (speed information).
The drive recorder image URI stores the storage destination URI of the drive recorder image before and after the date and time (for example, within 5 seconds).
The other information may include, for example, a driving score calculated based on the acceleration status, etc. Note that the other information may also include a task status for each date and time.

The operation authority management data is data for storing a combination of an operating user who operates the fleet management data and an operation authority, which is an operation that the operating user is allowed to perform.
Here, operational authorities for operation management data can be defined as, for example, "view", which is the authority to operate to view operation management data, "edit", which is the authority to operate to change user ID, vehicle ID, business status, destination, etc., and "delete", which is the authority to operate to erase operation management data.
In addition, the operating user can be defined as a type such as "self," in which the operation is performed by a user identified by a user ID stored in the operation management data, "same position class," in which the operation is performed by a user who belongs to the same position class as the user identified by the user ID, or "everyone," which does not limit the user.

For example, in the operation authority management data in Figure 5, it is stored that "Self" has the operation authority for "viewing" and "editing", but does not have the operation authority for "deleting". It is also stored that users of the "same position class" only have the operation authority for "viewing", and "Everyone" has no operation authority at all.

Note that the operation authority management data may store only "view" or any combination of operation authorities such as "view" and "delete." Also, a user who is in a higher position class (e.g., manager) than "the user's" position class (e.g., staff) may have the same operation authority as a user of the same position class. A user of a privileged position class (e.g., director) may be able to perform any operation without being bound by the restrictions of the operation authority management data.

The storage unit 22 of the administrator terminal 20 stores, for example, the user ID of the user of the administrator terminal 20. The storage unit 42 of the in-vehicle terminal 40 stores, for example, the user ID of the user of the in-vehicle terminal 40 and the vehicle ID of the vehicle in which the in-vehicle terminal 40 is installed. Note that, instead of the user ID and vehicle ID, the terminal ID of each terminal may be stored.

The following describes an example of the processing procedure in the first embodiment. Figure 6 is a flowchart of the processing performed by the server 10, the administrator terminal 20, and the in-vehicle terminal 40 in cooperation with each other, from the start of vehicle operation to the end of vehicle operation and viewing of vehicle operation data.

The symbols A, B, and S in the flowchart of FIG. 6 represent steps executed by the control units of the administrator terminal 20, the vehicle-mounted terminal 40, and the server 10, respectively.
Furthermore, the flowchart described below merely shows one example of the information processing procedure in this embodiment, and other steps may be added, some steps may be deleted, or some steps may be executed in the control unit of another device.

First, when the control unit 41 of the in-vehicle terminal 40 acquires operation setting information based on, for example, an operation input to the operation unit 43, it transmits the operation setting information to the server 10 via the communication unit 47 (B110). Here, the operation setting information includes, for example, the user ID and business status of the user who operates the vehicle in which the in-vehicle terminal 40 is installed, the vehicle ID of the operated vehicle, information regarding the operation authority for the operation management data of this operation set by the user who operates the vehicle, the destination, etc.

The operation setting information may be set, for example, by the administrator terminal 20 or the in-vehicle terminal 40 of a user other than the user who operates the vehicle (for example, the in-vehicle terminal 40 of another user whose setting is permitted by the user who operates the vehicle) and transmitted to the server 10.

When the control unit 11 of the server 10 receives operation setting information from the in-vehicle terminal 40, it adds a record to the operation management database 127 and initializes the added operation management data based on the received operation setting information (S110).

Next, the control unit 41 of the in-vehicle terminal 40 acquires vehicle information using the imaging unit 48, clock unit 49A, position information acquisition unit 49B, etc., and transmits the acquired vehicle information to the server 10 via the communication unit 47 (B120). Here, the vehicle information includes, for example, vehicle position coordinates associated with the date and time, acceleration status, drive recorder image information, etc.

When the control unit 11 of the server 10 receives the vehicle information from the in-vehicle terminal 40, it adds it to the vehicle operation data of the operation management data and stores it (S120).

The control unit 41 of the in-vehicle terminal 40 determines whether or not the operation of the vehicle is to be terminated based on, for example, an operation input to the operation unit 43 or a signal input from an in-vehicle ECU (not shown) (B130). When it is determined that the operation of the vehicle is to be terminated (B130: YES), the control unit 41 of the in-vehicle terminal 40 transmits vehicle operation termination information indicating that the operation of the vehicle is to be terminated to the server 10 via the communication unit 47 (B140).
If it is determined that the vehicle operation has not ended (B130: NO), the control unit 41 of the in-vehicle terminal 40 returns the process to step B120.

When it is determined that vehicle operation end information has been received from the in-vehicle terminal 40 (S130: YES), the control unit 11 of the server 10 closes the operation management data being recorded (S140). When it is determined that vehicle operation end information has not been received from the in-vehicle terminal 40 (S130: NO), the control unit 11 of the server 10 waits to receive vehicle information again and executes step S120.

When it is determined that vehicle operation end information has been received from the in-vehicle terminal 40 (S130: YES), the control unit 11 of the server 10 may not close the operation management data being recorded, but may set the vehicle to a non-operating state and continue acquiring vehicle information.

The control unit 21 of the manager terminal 20 transmits operation management data viewing request information for viewing operation management data specified by the operation management ID to the server 10 via the communication unit 47 based on, for example, an operation input to the operation unit 23 (A110). Prior to this step, the control unit 21 of the manager terminal 20 may receive list information of operation management IDs stored in the operation management database 127 from the server 10.

When traffic management data viewing request information is received from the manager terminal 20, the control unit 11 of the server 10 determines whether or not viewing and operating the traffic management data of the specified traffic management ID is possible based on the received traffic management data viewing request information (S150). More specifically, it refers to the job class of the user of the manager terminal 20, the job class of the user ID of the specified traffic management data, and the operation authority management data of the specified traffic management data to determine whether or not the user of the manager terminal 20 is able to view. Note that operation authority other than viewing operations can also be determined in a similar manner.

When it is determined that the user of the manager terminal 20 is able to view and operate the fleet management data (S150: YES), the control unit 11 of the server 10 transmits the fleet management data to the manager terminal 20 via the communication unit 17 (S160).
When it is determined that the browsing operation is not permitted (S150: NO), the control unit 11 of the server 10 ends the process. When it is determined that the browsing operation is not permitted (S150: NO), the control unit 11 of the server 10 may transmit information indicating that the browsing operation is not permitted to the manager terminal 20, and the control unit 21 of the manager terminal 20 may display the received information indicating that the browsing operation is not permitted on the display unit 24. Furthermore, the control unit 11 of the server 10 may transmit data other than the vehicle operation data among the operation management data, and the control unit 21 of the manager terminal 20 may display a part of the received operation management data on the display unit 24.

When it is determined that operation management data has been received from the server 10 (A120: YES), the control unit 21 of the manager terminal 20 causes the display unit 24 to display the received operation management data (A130).

The above process illustrates an example in which the operation management data is referenced on the manager terminal 20 after the vehicle has been operated. However, when the operation management data for a vehicle in operation is referenced on the manager terminal 20 (displayed in real time), this can be achieved by executing steps A110 to A130 and S150 to S160, for example, between steps S120 and S130.

The control unit 41 of the in-vehicle terminal 40 may also acquire operation setting information at any time and transmit the operation setting information to the server 10. In this case, the operation authority for the operation management data can be changed even while the vehicle is in operation or after the operation has ended.

Figure 7 shows an example of an operation setting information acquisition screen displayed on the display unit 44 of the in-vehicle terminal 40. In this example, an example of a display screen of a smartphone held by the driver, which is part of the configuration of the in-vehicle terminal 40, is shown.

Figure 7 is an example of a driving history viewing screen for viewing the driving management data of a vehicle operated by user "B.B.", who is a "staff" in the job title class, after the vehicle was operated on "August 8, 2021." In this screen, the date on which the driving management data was collected is displayed at the top, and below that, the vehicle's driving route is displayed on an electronic map based on the vehicle position coordinates of the collected vehicle driving data. In addition to the driving route, the location where dangerous operations such as sudden braking and sudden steering were performed may be displayed. Below the driving route, for example, a driving score calculated out of 100 points based on the acceleration status of the vehicle driving data is displayed. The driving score can be calculated, for example, according to the invention of JP Patent Publication No. 2006-243856. In addition, the distance and time traveled by the vehicle during this operation are displayed at the bottom, and below that, the vehicle's position at each time is listed in a list linked to the address.

For example, when a change of viewing operation authority is selected from the setting menu button on the driving history viewing screen, for example, a viewing restriction setting object SOB is displayed by rising from the bottom of the screen. The viewing restriction setting object SOB is configured to display a selection item of "Only B.B. can view" that sets viewing permission to "yourself" only, a setting item of "Only staff can view" that gives viewing permission to "yourself" and "same position class", and a selection item of "Everyone can view" that sets viewing permission to "everyone" including "yourself". When these selection items are selected by a tap operation, the operation setting information is transmitted from the in-vehicle terminal 40 to the server 10.

Fig. 8 is an example of a vehicle management application management screen displayed on the display unit 24 of the administrator terminal 20 when, for example, the selection item "Only B.B. can view" is selected in the viewing restriction setting object SOB in Fig. 7. In this screen, for example, the "Driving History" menu for viewing the driving history is selected in the management menu selection area in the left pane. Also, the user information display area at the top right shows that user "A.A." of the job class "Manager" is logged in to the administrator terminal 20.
To the right of the management menu selection area, a driving history list display for displaying an overview of the operation management data is displayed based on the selection of the "Driving History" menu. In the driving history list display, the operation date and time, the user name who operated the vehicle, and the job class are displayed in a row in association with each other for each operation management data.
For example, when the column "August 8, 8:02-10:34, Staff B.B.", which the user "B.B." has set as viewable only to "himself," is tapped, the electronic map area MR showing the vehicle's operating route is displayed to the right of the driving history list display. However, since the user "A.A." does not have the authority to view this operation management data, the electronic map area MR displays a viewing restriction object RD indicating that viewing of the operating route is restricted, and the user "A.A." cannot check the operating route.

[Effects of the First Embodiment]
The information processing method in this embodiment is an information processing method executed by a system including an information display device (e.g., an administrator terminal 20), and includes acquiring mobile body information (e.g., vehicle information) related to a mobile body (e.g., a vehicle), and shows a configuration in which, if no restrictions are set on viewing of the mobile body information (e.g., when the user of the administrator terminal 20 has viewing authority), the mobile body information is displayed on the information display device, and, if restrictions are set (e.g., when the user of the administrator terminal 20 does not have viewing authority), the display of the mobile body information on the information display device is restricted.
This makes it possible to determine whether or not to display mobile body information on the information display device based on the restriction settings regarding viewing of mobile body information, thereby providing a comfortable work environment by making it less likely for users of the mobile body to feel uncomfortable or averse as if they are being excessively monitored.

In addition, this embodiment shows a configuration in which it is possible to set restrictions and release the restriction settings based on operations on a terminal (e.g., in-vehicle terminal 40) of a first user (e.g., a user of in-vehicle terminal 40) associated with the mobile body.
This allows the first user to set restrictions on viewing of mobile object information himself/herself, thereby providing an effect of improving user convenience.

[First Modification (1)]
In the first embodiment, an example in which the operation authority is set for each piece of fleet management data has been described, but the present invention is not limited to this. For example, a predetermined operation authority may be set for each user.

FIG. 9 shows an example of the data structure of the second user registration data 123B, which is an example of the data structure of the user registration data 123 in this modified example.
In the user registration data 123B, for example, a user ID, a user name, a position class, an information restriction level, a business status, and other registration information are stored in association with each other.
The user ID, user name, position class, business status, and other registered information can be configured in the same manner as the first user registration data 123A, for example.

The information restriction level is information for setting the range of operational management data that the user can operate, and for example, a level identification flag set by the administrator is stored.
The information restriction level can be set, for example, as follows:
- "Level 0": All users can view the traffic management data associated with this user.
- "Level 1": Users of the same job title and class can view the operation management data linked to this user.
- "Level 2": Only the user can view the operation management data associated with this user.
In addition to the above three levels, an information restriction level may be set such that users of a higher position class than the user's position class and the user himself/herself can view the operation management data linked to the user. Information restriction levels may also be set in a similar manner for operations other than viewing. Users of a privileged position class may be able to perform any operation without being bound by the information restriction level.

In the example of Figure 9, the information restriction level for user "A.A." is "Level 2," so the operation management data for vehicles operated by user "A.A." can only be viewed by user "A.A." Also, the information restriction level for user "C.C." is "Level 1," so the operation management data for vehicles operated by user "C.C." can only be viewed by users with a job title of "Staff."

When setting an information restriction level, it may be possible to prevent the setting of operation authority management data for operation management data. Furthermore, when using both the information restriction level and operation authority management data for operation management data, priority may be given to the operation authority based on the information restriction level, or priority may be given to the operation authority based on the operation authority management data.

In addition, the information restriction level is not limited to being set manually by an administrator or the like. For example, the control unit 11 of the server 10 may refer to the operation management database 127 and set the information restriction level of each user based on, for example, the average value of the driving score. In this case, for example, if the average value of the driving score of a user in a predetermined period (for example, the last month) exceeds a safe driving setting value (for example, 90 points), the information restriction level of the user is set to "Level 2", and if it is below, the information restriction level of the user is set to "Level 1". In addition, if the average value of the driving score falls below a dangerous driving setting value (for example, 50 points), the information restriction level of the user is set to "Level 0".
In this way, if a user's driving score is high, the user is judged to be a good driver and the scope of viewing of the driving management data can be narrowed. Also, if a user's driving score is low, the driving management data can be made public to keep a watchful eye on each other and to warn users of their driving behavior that is prone to dangerous driving.

This modified example shows a configuration in which the restriction setting can be performed for each second user associated with an information display device (for example, the in-vehicle terminal 40 or the administrator terminal 20).
This eliminates the need to set restriction settings for each user individually, and has the effect of making it possible to set restriction settings for each certain range more simply and appropriately.

[First Modification (2)]
In the first embodiment, an example of setting the operation authority for the entire operation management data is illustrated, but the present invention is not limited to this. For example, the operation authority may be set for each item of the operation management data or each item of the vehicle operation data.

FIG. 10 shows a table of an example of restrictions on operation content for the settings of restricted items and viewing modes in this variation. Here, restricted items are items in the operation management data for which operation authority is restricted. Here, "viewing" is shown as an example of operation authority. Also, the viewing mode is a type of viewing method for viewing the operation management data. Here, the following three types of display modes are shown as examples of viewing modes.
- "Real-time display" for viewing operation management data in real time while the vehicle is in operation.
- "Driver daily report display" for viewing all of a specific user's driving management data for a specified period (e.g., one day) at once.
- "Vehicle daily report display" for viewing all operational management data for a specific vehicle for a specified period (e.g., one day) at once.
In addition, the specified period for "Driver daily report display" and "Vehicle daily report display" may be the period from the start of work of the user operating the vehicle to the end of work, and each daily report may be automatically created when work is completed.

When the item "User name" is set to hidden, the name of the user who operates the vehicle cannot be viewed in "Real-time display" and "Vehicle daily report display." That is, the control unit 11 of the server 10 transmits operation management data with the user name anonymized to the manager terminal 20. Also, in "Driver daily report display," the operation management data related to that user cannot be viewed.
When the item "Vehicle location information" is set to hidden, the vehicle location coordinates of the vehicle operation data cannot be viewed in "Real-time display" and "Driver daily report display." In addition, in "Vehicle daily report display," the operation management data related to the vehicle cannot be viewed.
Similarly, for other items subject to restriction, when the item is set to be hidden, the item in the operation management data cannot be viewed.

When restricting items from being viewed, the server 10 may transmit the operation management data without anonymizing it, and may display the restricting items on the administrator terminal 40 in an anonymous manner, or may not display them.

The restricted items may be set by each user, for example, using a viewing restriction setting object SOB, or may be set collectively by an administrator. The restricted items that can be set by a user may be selected based on, for example, a driving score. In this case, it is possible to select such a setting that a user with a high driving score can set "Dashcam images" to hidden, but a user with a low score cannot set it to hidden.

The users to whom the restriction on the restricted items applies may be "everyone" except "yourself," or different restrictions may be set for each user, as with the operation authority management data. Operation authority other than "viewing" may also be set for each restricted item. The restricted items may be set on a per-operation management data basis by adding them to the operation authority management data for each operation management data, or may be incorporated into the information restriction level so that they can be set on a per-user basis.

In addition, the restricted items may be set for each viewing mode. For example, if viewing of "vehicle position coordinates" is restricted as a restricted item, the vehicle position coordinates can be set to be unviewable in the viewing mode "real-time display," but viewable in the viewing modes "driver daily report display" and "vehicle daily report display."

This modified example shows a configuration in which the restriction setting can be performed for each type of mobile object information (for example, the restricted item "user name" or the restricted item "vehicle position information").
This provides the advantage of making it possible to set restrictions more flexibly depending on the type of mobile object information.

In addition, this modified example includes generating a daily report (e.g., information for displaying in the viewing mode "Driver daily report display") based on mobile body information in response to the end of work of a first user (e.g., a user of the in-vehicle terminal 40) associated with the mobile body, and shows a configuration for generating a daily report based on a common mobile body information when restrictions are not set and when restrictions are set.
This has the effect of enabling a user of the information display device to display mobile object information in the daily report regardless of the restriction settings, thereby enabling accurate understanding of the work of the first user.

In addition, this modified example shows a configuration in which the mobile object information includes evaluation information (e.g., a driving score) regarding the driving of the first user associated with the mobile object, and restrictions can be set when a predetermined condition regarding the evaluation information is met.
According to this, restrictions can be set only when the driving conditions of the first user are good based on the evaluation information, which has the effect of improving the motivation of the first user for safe driving.

[First Modification (3)]
In the first embodiment, an example in which the operation authority is set based on a user operation is described, but the present invention is not limited to this. For example, the operation authority may be automatically set based on the business status of the user when driving the vehicle.

For example, if a user's work status is "outside working hours," the operation management data for the vehicle operated by that user is likely to involve private activities, so the system may be set to automatically restrict operations by anyone other than the user.

[First Modification (4)]
In the first embodiment, a vehicle management system for an automobile is illustrated as an example of a mobile object management system, but the present invention is not limited thereto. For example, the present invention can be applied to various vehicles other than automobiles, such as two-wheeled vehicles such as bicycles and motorcycles, agricultural machinery such as tractors, construction machinery, and railroad cars. In addition, by mounting the in-vehicle terminal 40 on a mobile object other than a vehicle, the present invention can be applied to various mobile object management systems, such as a visiting nurse management system, a drone management system, and a ship management system.

[Second embodiment]
The second embodiment is an embodiment in which, for example, an administrator obtains operating authority as needed by requesting a change in the operating authority for mobile information that is restricted by settings of the driver who operates the vehicle.
The contents described in the second embodiment are applicable to any of the other embodiments and modifications.

The following describes an example of the processing procedure in the second embodiment. Figures 11 and 12 are flowcharts showing the process of transferring vehicle operation and operation management data viewing authority and viewing vehicle operation data, which is performed by the server 10, the administrator terminal 20, and the in-vehicle terminal 40 in cooperation with each other.

If it is determined that no operation management data has been received from the server 10 (A120: NO), the control unit 21 of the manager terminal 20 displays on the display unit 24 a screen for determining whether or not to request permission to view the operation management data that has been made inaccessible (A220).
For example, when it is determined that a request for viewing authority is selected based on an operation input to the operation unit 23 (A220: YES), the control unit 21 of the manager terminal 20 transmits, for example, operation management data viewing authority request information including an operation management ID to the server 10 via the communication unit 27 (A230). Note that the operation management data viewing authority request information may include a comment such as the reason for requesting the viewing operation authority.

If it is determined that operation management data viewing authority request information has been received from the administrator terminal 20 (S220: YES), the control unit 11 of the server 10 transmits operation management data viewing authority request information to the in-vehicle terminal 40 via the communication unit 17, requesting a user with operation authority for the operation management data (e.g., a user recorded in the user ID) to grant viewing operation authority to the user of the administrator terminal 20 (S230).

If it is determined that a request for authority to view the operational management data has been received from the server 10 (B210: YES), the control unit 41 of the in-vehicle terminal 40 causes the display unit 44 to display a screen for determining whether or not to grant the user of the manager terminal 20 authority to view the operational management data (B220).
For example, if it is determined that permission to view has been selected based on an operation input to the operation unit 43 (B220: YES), the control unit 41 of the in-vehicle terminal 40 transmits operation management data viewing permission information indicating that the user of the manager terminal 20 is given the authority to view the operation management data to the server 10 via the communication unit 47 (B230).

If it is determined that the operation management data viewing permission information has been received from the in-vehicle terminal 40 (S240: YES), the control unit 11 of the server 10 transmits the operation management data to the manager terminal 20 (S260). When it is determined that the operation management data viewing permission information has been received, the control unit 11 of the server 10 may permanently lift the operation restriction on the user of the manager terminal 20 by overwriting the operation authority management data of the operation management data, or may lift the operation restriction only for a predetermined period (e.g., one hour) from the reception of the operation management data viewing permission information, or may require the reception of operation management data viewing permission information each time the operation restriction is lifted.

The control unit 11 of the server 10 may transmit the operation management data to the manager terminal 20 regardless of the judgment result of S240. In this case, a notification is displayed on the in-vehicle terminal 40 that operation management data that is not permitted for viewing is about to be viewed, but the manager can view the operation management data without the approval of the user of the in-vehicle terminal 40.

If it is determined that operation management data has been received from the server 10 (A240: YES), the control unit 21 of the manager terminal 20 displays the received operation management data on the display unit 24 (A250).

The above process illustrates the case where the operation management data is referenced on the manager terminal 20 after the vehicle has been operated. However, when the operation management data of a vehicle in operation is referenced on the manager terminal 20 (displayed in real time), this can be achieved by executing steps A220 to A250, B210 to B230, and S220 to S260, for example, between steps S120 and S130.

You can also request to have restrictions lifted on operations other than viewing operations in the same way as you would for viewing operations.

13 is an example of a vehicle management application management screen displayed on the display unit 24 of the administrator terminal 20 when, for example, the selection item "Viewable only by B.B." is selected in the viewing restriction setting object SOB on the in-vehicle terminal 40 of user "B.B." On this screen, for example, in the management menu selection area in the left pane, the "real-time" menu for checking the current vehicle operating status is selected.
On the right of the management menu selection area, a vehicle icon and a vehicle name are displayed in association with the current vehicle position coordinates in the electronic map area MR based on the selection of the "real-time" menu. On the right of the electronic map area MR, a vehicle status list display area is displayed for displaying a list of the statuses of the vehicles managed in the vehicle management application. In the vehicle status list display area, the vehicle name, the name of the user who operates the vehicle, and the vehicle status (e.g., whether the vehicle is running or stopped) are displayed in association with each other for each vehicle.

In this example, user "B.B." is driving vehicle "Tokyo 002," but the vehicle's location is not displayed in the electronic map area MR because the user has set the vehicle's location coordinates to be hidden except for the vehicle's own location. In addition, the vehicle status list display area shows that the vehicle's status for vehicle "Tokyo 002" is that it is traveling but the vehicle's location coordinates are not displayed.

For example, a situation arises where the user of the administrator terminal 20 needs to check the vehicle location coordinates of a vehicle named "Tokyo 002". At this time, when the vehicle status display in the vehicle status list display area is tapped, a traffic management data viewing authority request determination object ARD is displayed with the title "Requesting permission to display vehicle location". This traffic management data viewing authority request determination object ARD is provided with a comment input field for notifying user "B.B." of the reason for requesting viewing authority. Note that the input of a comment may or may not be required.
Below the comment input field, a traffic management data viewing authority request button, indicated by the word “Request”, for requesting authority to view traffic management data, and a cancel button for canceling the operation are displayed.

When the traffic management data viewing authority request button is tapped, a notification is displayed on the in-vehicle terminal 40 of user "B.B." that user "A.A." has requested that the viewing operation restriction on the vehicle position coordinates be lifted. When user "B.B." agrees to the lifting of the viewing operation restriction, a vehicle icon with the vehicle name "Tokyo 002" is displayed in the electronic map area MR, and user "A.A." is able to ascertain the vehicle position.

[Effects of the Second Embodiment]
This embodiment shows a configuration in which a request to release the restriction setting is sent to a terminal (e.g., an in-vehicle terminal 40) based on the operation of a second user (e.g., an administrator) associated with the information display device (e.g., an administrator terminal 20).
According to this, even if a restriction has been set, the second user can request the first user of the terminal to lift the restriction setting as necessary, thereby improving convenience for the second user while taking into consideration the first user's discomfort or aversion to viewing information (for example, while preventing the driver from feeling like he is being overly monitored).

[Second Modification Example (1)]
In the second embodiment, an example in which the operation restriction is lifted based on the user operation of the administrator terminal 20 has been described, but the present invention is not limited to this. For example, when a specific event (e.g., a danger to the vehicle) is detected based on the vehicle information received from the in-vehicle terminal 40, the operation restriction on the operation management data may be automatically lifted.

FIG. 14 is an example of a flowchart according to this modified example.
When it is determined that the operation management data viewing authority request information has been received from the manager terminal 20 (S220: YES), the control unit 11 of the server 10 determines whether or not a specific event has occurred in the behavior of the vehicle based on the vehicle operation data of the operation management data (S250). Here, examples of specific events of the vehicle behavior include the following.
- When sudden acceleration, deceleration, or sudden operation exceeding a predetermined threshold is detected in the acceleration status.
・If the decrease in driving score exceeds a certain value.
- If the tire pressure or engine coolant temperature is outside the specified range.
- If a traffic accident is detected near the vehicle location coordinates.
- When automatic analysis of dashcam images detects drowsy driving, use of a mobile phone, or lane departure.
- If a vehicle collision is detected.
- If the airbag is confirmed to be deployed.
- If you drive a certain distance (for example, 200 km) or more in one day.
- When a trigger is issued by the vehicle user (e.g. pressing the emergency call button).

When the control unit 11 of the server 10 determines that a specific event has occurred in the behavior of the vehicle (S250: YES), the control unit 11 transmits the operation management data to the manager terminal 20 (S260).
The control unit 11 of the server 10 may transmit, together with the driving management data, to the manager terminal 20, vehicle abnormality detection information indicating that a specific event has occurred in the vehicle behavior.

When displaying real-time operation management data for a vehicle in operation, the control unit 11 of the server 10 may execute step S250 regardless of the result of the determination in step S220. In this case, when it is determined that a specific event has occurred in the vehicle's behavior (S250: YES), vehicle abnormality detection information may be sent to the manager terminal 20 of a specific user (e.g., the operation manager) linked to the vehicle ID or the user ID of the user operating the vehicle. The manager terminal 20 may then display the received vehicle abnormality detection information.

In this case, the consent of the user of the in-vehicle terminal 40 may or may not be required to view the operation management data for which viewing restrictions are set.

In addition, as an operation authority classification of the operation authority management data, in addition to operation allowed/not allowed, it may be possible to set operation authority that is conditionally allowed when a specific event is detected. It may also be possible to request the lifting of operation restrictions for each restricted item. For example, if it is set that only "yourself" can view drive recorder images and "everyone" can view vehicle position coordinates, when a specific event is detected, it may be possible to request viewing authority for drive recorder images for a specified period of time (for example, 30 seconds before and after) at the time of detection.

The lifting of the operation restriction on the operation management data may continue until the next setting operation for the operation restriction is performed, or may be temporary (e.g., 24 hours).

[Third Example]
The third embodiment is an embodiment in which mobile object information under viewing restriction is displayed by changing the display mode on the electronic map.
The contents described in the third embodiment are applicable to any of the other embodiments and modifications.

The following describes an example of the processing procedure in the third embodiment. Figure 15 is a flowchart of the processing performed by the server 10, the administrator terminal 20, and the in-vehicle terminal 40 in cooperation with each other, from the start of vehicle operation to the end of vehicle operation and viewing of vehicle operation data.

When receiving the traffic management data viewing request information from the manager terminal 20, the control unit 11 of the server 10 determines whether or not the traffic management data of the specified traffic management ID can be viewed (S310), in the same manner as S150 in Fig. 6. If the user of the manager terminal 20 determines that the traffic management data can be viewed (S310: YES), the control unit 11 of the server 10 transmits the traffic management data to the manager terminal 20 (S160).
When it is determined that the viewing operation is not possible (S310: NO), the control unit 11 of the server 10 executes, for example, a coordinate identifiability reduction process of the vehicle position coordinates in the operation management data. The coordinate identifiability reduction process is a process that makes it difficult to identify the vehicle position coordinates based on the position information (e.g., latitude and longitude information) of the in-vehicle terminal 40 on the electronic map. For example, when the coordinate identifiability reduction process is executed, the probability that the vehicle icon is displayed at a position different from the vehicle position coordinates on the electronic map becomes higher compared to when the coordinate identifiability reduction process is not executed (one example of a decrease in the position accuracy of the displayed vehicle icon). The coordinate identifiability reduction process of the vehicle position coordinates may be called a low-resolution process.

In the coordinate distinctiveness reduction process, the electronic map is divided into specified grid-like areas (hereinafter referred to as "low distinctiveness vehicle position areas"), and it is determined which low distinctiveness vehicle position area the vehicle position coordinates belong to. Then, the control unit 11 of the server 10 transmits low distinctiveness operation management data including identification information of the low distinctiveness vehicle position area to the administrator terminal 20 instead of the vehicle position coordinates (S320).

Here, the low-distinguishability vehicle position area in the electronic map may be divided, for example, in the following manner.
- Divide into rectangular areas defined by predetermined long and short sides (for example, 500 m square). Note that instead of rectangular areas, it may be divided into polyhedral areas such as equilateral triangles and regular hexagons.
For example, an address area defined by "XX town" includes vehicle position coordinates determined to be within "XX town" regardless of the "block number" or "banchi" number.
- The area around the home (e.g., the area around the user's home while driving the vehicle) is divided into coarse areas (e.g., a rectangular area of 1 km square), and the work area (e.g., the area around the company or the areas around places to be visited) is divided into fine areas (e.g., a rectangular area of 200 m square).
The method of dividing the low-discriminability vehicle location area may be the same for all users, or may be different for each user. For example, the low-discriminability vehicle location area of one user may be set to an address area divided by "block number," and the low-discriminability vehicle location area of another user may be set to an address area divided by "banchi."

In addition, the way in which the low-discriminability vehicle location area is divided (e.g., the position of the rectangular area) may be changed every certain period of time (e.g., six hours).

Figure 16 is an example of a vehicle management application management screen displayed on the display unit 24 of the administrator terminal 20. In this figure, the electronic map area MR is divided, for example, into four low-discriminability vehicle location areas indicated by two-dot chain lines. Here, the four low-discriminability vehicle location areas are identified as areas "A" to "D" clockwise from the low-discriminability vehicle location area in the upper left. Note that the two-dot chain line bounding boxes indicating the boundaries of the low-discriminability vehicle location areas in this figure and the names of each area are displayed for convenience of explanation and do not need to be displayed on the actual display screen.

Below each low-distinct vehicle position area, a vehicle position confirmation box BX is displayed to display the vehicle positions in the traffic management data in which the coordinate discriminability reduction process of the vehicle position coordinates has been performed. For example, in area "A", the vehicle position confirmation box BX displays vehicle icons with the vehicle names "Tokyo 002" and "Tokyo 003", indicating that these two vehicles are located somewhere within area "A".
In addition, within the vehicle position confirmation box BX, for example, the vehicle icon of a vehicle traveling at a high speed may be placed further to the left. Also, an arrow icon indicating the vehicle's traveling direction may be added to the vehicle icon. This allows the movement of vehicles within the low-distinguishability vehicle position area to be roughly grasped. In addition, for example, a parked vehicle may be added with a "stopped" icon to make it easier to distinguish the vehicle icon.

For example, in area "B", the vehicle icon of the vehicle name "Tokyo 004", whose location information is permitted to be viewed, is displayed in the area where the vehicle position confirmation box BX is displayed by default. In this case, the vehicle position confirmation box BX can be configured to automatically move to an area (e.g., upward) that does not obstruct the display of the vehicle icon whose location information is permitted to be viewed. In addition, the vehicle status list display area can be configured to display in more detail the vehicle status of the vehicle name "Tokyo 004", whose location information is permitted to be viewed, such as the speed and acceleration (decelerating/accelerating) while traveling, in addition to the vehicle status of a vehicle whose location information is not permitted to be viewed (e.g., whether traveling or stopped). The traveling speed may be configured to be displayed superimposed on the vehicle icon.

In the electronic map area MR, for vehicles whose location information is permitted to be viewed, an arrow icon indicating the direction of travel and information on whether the vehicle is moving or not may be displayed within the vehicle icon, and for vehicles whose location information is not permitted to be viewed, the arrow icon and information on whether the vehicle is moving or stopped may not be displayed within the vehicle icon. Also, for vehicles whose location information is permitted to be viewed, the vehicle speed (or acceleration) while the vehicle is moving may be displayed within the vehicle icon, and for vehicles whose location information is not permitted to be viewed, the vehicle speed (or acceleration) while the vehicle is moving may not be displayed within the vehicle icon.

For example, in area "D", if no vehicle is present within this low-distinct vehicle location area, the vehicle location confirmation box BX may be configured not to be displayed. This allows the low-distinct vehicle location area in which a vehicle is present to be quickly identified.

In addition, for vehicles whose business status is set to "off-duty hours" or for which a certain amount of time (e.g., one hour) has passed since becoming "off-duty hours," the vehicle icon may not even be displayed in the vehicle location confirmation box BX from the perspective of privacy protection.

In addition, whether or not detailed vehicle positions are displayed may be changed depending on the viewing mode. For example, in the viewing mode "real-time display," vehicles whose position information is not approved for viewing may be displayed in a vehicle position confirmation box BX, and in the viewing mode "vehicle daily report display," even vehicles whose position information is not approved for viewing may have a vehicle icon displayed on an electronic map based on the specific vehicle position coordinates.

Also, unlike the electronic map area MR illustrated in the above display example, for example, it is not necessary to place a vehicle position confirmation box BX for each low-distinct vehicle position area. In this case, one vehicle position confirmation box BX can be placed within or outside the electronic map area MR, and a vehicle icon can be displayed within that vehicle position confirmation box BX regardless of the low-distinct vehicle position area to which the vehicle belongs. This makes it easy to identify vehicles whose position coordinates are made low-distinct, even when vehicles are distributed over a wide area.

[Effects of the Third Embodiment]
In this embodiment, the mobile object information includes at least position information (e.g., vehicle position coordinates) regarding the position of the mobile object, and includes displaying a map (e.g., electronic map area MR) on an information display device, and when no restriction is set, a mobile object display (e.g., a vehicle icon) associated with the position information is superimposed on a position corresponding to the vehicle position coordinates on the electronic map, and when a restriction is set, the position accuracy of the display of the mobile object display is reduced compared to when no restriction is set.
According to this, even if a restriction is set on viewing the location information of a moving object, by displaying the moving object in a manner that results in a low positional accuracy on the display, a user of the information display device can grasp the approximate location of the moving object, even if he or she cannot grasp the exact location of the moving object, and can grasp the situation to a degree that is appropriate for business purposes.

In addition, this embodiment shows a configuration in which, when viewing restrictions are set on the location information of a moving body, the moving body display is displayed in an area different from the map (for example, a vehicle position confirmation box BX outside the electronic map area MR).
This provides the advantage that the user of the information display device can tell at a glance whether or not restrictions have been set on viewing the location information of each mobile object.

Furthermore, this embodiment illustrates a configuration in which, when viewing restrictions are set on the location information of a moving object, a moving object display is superimposed on a predetermined area (e.g., a vehicle location confirmation box BX) within a map area that corresponds to the location information among multiple map areas (e.g., low-distinct vehicle location areas) set on a map based on the location information.
This has the effect of allowing a user of the information display device to easily identify at a glance information as to whether or not viewing restrictions have been set for the location information of each mobile object, and the detailed or rough location information of the mobile object.

Furthermore, in this embodiment, the moving body information includes progress information regarding the direction of travel of the moving body, and when no restriction is set on viewing the position information of the moving body, a moving body display (e.g., a vehicle icon) is displayed on the information display device in a first aspect related to the progress information (e.g., a display aspect in which an arrow icon is added), and when a restriction is set on viewing the position information of the moving body, the display of the moving body information in the first aspect is restricted.
According to this, when a restriction is set on viewing the location information of a moving object, the user of the information display device cannot grasp the direction of travel of the moving object, and therefore it is possible to prevent the user of the moving object from feeling that excessive surveillance is being conducted.

In addition, this embodiment shows a configuration in which the moving body information includes speed information related to the moving speed of the moving body or acceleration information related to the acceleration of the moving body, and when no restriction is set on viewing of the position information of the moving body, the moving body display (vehicle status display in the vehicle position confirmation box BX) is displayed on the information display device in a second mode related to the speed information or acceleration information (for example, a display mode that adds the vehicle's traveling speed), and when a restriction is set on viewing of the position information of the moving body, the display of the moving body information in the second mode is restricted.
According to this, when a restriction is set on viewing the location information of a mobile object, the user of the information display device cannot ascertain the moving speed of the mobile object, and therefore it is possible to prevent the user of the mobile object from feeling that excessive surveillance is being conducted.

[Third Modification (1)]
In the third embodiment, for example, the determination as to whether or not the viewing of the location information is restricted is performed according to the user setting of the vehicle driver, but is not limited thereto. For example, the following three types of settings may be possible as the viewing restriction setting.
- Unable to view (vehicle position coordinates are not displayed on the electronic map or in the vehicle position confirmation box BX).
- Can be viewed with low distinctiveness (a vehicle icon based on the vehicle position coordinates is displayed in the vehicle position confirmation box BX).
- Highly identifiable (vehicle icon based on vehicle position coordinates is displayed on electronic map).

Note that the setting of the viewing restriction is not limited to being based on the user setting, and may be performed automatically, for example, as described below.
- Cannot be viewed near the user's home address or can be viewed with low identity.
- High visibility is possible near the user's business address or destination.
If the user's driving score is above a certain pass value (e.g., 80 points), the video cannot be viewed. If the user's driving score is below a certain fail value (e.g., 40 points), the video can be viewed with high distinctiveness. If the user's driving score is any other value, the video can be viewed with low distinctiveness.
- Normally it follows the user settings, but if sudden steering or braking is detected based on the acceleration status etc., it can be viewed with high discrimination for a specified period of time.
- Normally, the user settings are followed, but after a certain period of time (for example, one week) has passed since the end of operation, the information can be viewed with high distinctiveness.
- Normally, the user settings are followed, but viewing is possible with high discrimination during a specified period (e.g., 5 minutes) before and after a designated work time (visit time, delivery time, etc.). In addition, viewing is not possible or viewing is possible with low discrimination outside of working hours or during temporary breaks.

[Third Modification (2)]
In the third embodiment, the low-discriminability vehicle location areas are divided such that adjacent low-discriminability vehicle location areas do not overlap each other, but the present invention is not limited to this. For example, the boundaries of adjacent low-discriminability vehicle location areas may be overlapped.
17 shows an example of a low-distinguishability vehicle position area of the electronic map area MR in this modified example. In this figure, area "A" and area "B" overlap in the overlap area of area "A" and area "B" shown by the dashed line.
Here, consider a case where the vehicle position coordinates of the vehicle name "Tokyo 001", whose position information is not permitted to be viewed, move from vehicle position "X" to vehicle position "Z" via vehicle position "Y". At this time, at vehicle position "X", a vehicle icon is displayed in the vehicle position confirmation box BX corresponding to area "A". When the vehicle position moves to the overlapping area of area "A" and area "B" thereafter, a vehicle icon can be configured to be displayed in the vehicle position confirmation box BX corresponding to area "A" based on the fact that the vehicle position was in area "A" of areas "A" and "B" until it leaves area "A". Therefore, at vehicle position "Y", a vehicle icon is displayed in the vehicle position confirmation box BX corresponding to area "A". Then, when the vehicle position leaves the overlapping area of area "A" and area "B", a vehicle icon can be configured to be displayed in the vehicle position confirmation box BX corresponding to area "B". Therefore, at vehicle position "Z", a vehicle icon is displayed in the vehicle position confirmation box BX corresponding to area "B".

By superimposing the low-distinct vehicle position area in this manner, when the vehicle position coordinates move across the low-distinct vehicle position area, the display in the vehicle position confirmation box BX is prevented from reacting sensitively, making it easier to view the vehicle icon and preventing the vehicle position from being specifically inferred from changes in the display in the vehicle position confirmation box BX.

When the vehicle position moves into the overlapping area between area "A" and area "B", a vehicle icon may be displayed in the vehicle position confirmation box BX corresponding to area "B" based on the vehicle position moving from area "A" excluding the overlapping area of area "A" to area "B" (the overlapping area of area "B").

In addition, when the vehicle position moves into the overlapping area of area "A" and area "B," the vehicle icon may be displayed in both the vehicle position confirmation box BX corresponding to area "A" and the vehicle position confirmation box BX corresponding to area "B."

When the vehicle position moves through the overlapping area between area "A" and area "B," the vehicle position confirmation box BX may be configured to display the vehicle icon in a flashing manner, or in other ways, differently from when the vehicle position is within a single low-distinct vehicle position area, to indicate that the vehicle is moving between areas.

In addition, when the vehicle position moves through the overlapping area between area "A" and area "B", it may be possible to randomly determine in which vehicle position confirmation box BX the vehicle icon will be displayed: the vehicle position confirmation box BX corresponding to area "A" or the vehicle position confirmation box BX corresponding to area "B".

For example, the conditions for determining in which vehicle position confirmation box BX the vehicle icon is to be displayed may be not only the vehicle position, but also conditions other than the vehicle position in addition to the vehicle position. These conditions may include, for example, one or more of the following: vehicle-related parameters other than the position information, such as vehicle acceleration information or speed information (e.g., acceleration or speed at or before entering the superimposition area), time information (e.g., time of entering the superimposition area, current time within the superimposition area), and environmental parameters, such as weather information (current weather, temperature, humidity, wind direction, wind speed at or before entering the superimposition area).

Each of the multiple parameters may be weighted according to the situation (the content and numerical value of each parameter), and the above decision may be made based on the multiple parameters (the combined value of the multiple parameters) each time a vehicle enters the overlapping area, or the above decision may be made based on the top (one or more) parameters with the highest priority as a result of the weighting. For example, for a vehicle whose speed or acceleration exceeds a predetermined value, a vehicle icon may be displayed in area "B" immediately after the vehicle enters the overlapping area from area "A", making it easier to grasp the movement by switching the display at an early timing.

The parameter on which the above decision will be based may be selected in advance by the director at his/her discretion, or may be selected automatically based on a random number value, etc., each time the vehicle position enters the overlapping area.

In this way, depending on the different circumstances when entering the overlapping area, the parameters that contribute to the above determination may differ, or the contents or values of the parameters that contribute to the above determination may differ, thereby creating irregularity in which vehicle position confirmation box BX the vehicle icon is displayed in.

A virtual boundary line between area "A" and area "B" may be set within the superimposed area, and when the vehicle position moves from area "A" to area "B" across the virtual boundary line, a vehicle icon may be displayed in the vehicle position confirmation box BX corresponding to area "B". The virtual boundary line is not limited to a straight line and may be a curved line, and may be set based on the various parameters described above, for example, and may be updated at a predetermined timing. The virtual boundary line may be set for each user.
In this case, the virtual boundary line in the overlapping area may be prevented from being displayed, so that the second user (administrator) cannot see the virtual boundary line. In other words, the display of the virtual boundary line to the second user may be restricted.

This modified example shows a configuration in which a first map area (e.g., area "A" in a low-discriminability vehicle location area) has an overlapping area that overlaps with a second map area (e.g., area "B" in a low-discriminability vehicle location area), and when coordinates corresponding to location information are included in the overlapping area, a moving object display is displayed in either a predetermined area within the first map area (a vehicle position confirmation box BX corresponding to area "A") or a predetermined area within the second map area (a vehicle position confirmation box BX corresponding to area "B").
According to this, when the coordinates corresponding to the position information of a moving object move across the first map area and the second map area, by providing an overlapping area, it is possible to make it difficult for the user of the information display device to specifically guess the position of the moving object, resulting in the effect of providing a comfortable work environment without making the user of the moving object feel as if they are being excessively monitored.

In addition, this modified example illustrates a configuration in which, when coordinates corresponding to location information are included in an area of the first map area excluding the superimposed area and then included in the superimposed area, a moving object display is displayed in a specified area within the first map area, and, when coordinates corresponding to location information are included in an area of the second map area excluding the superimposed area, a moving object display is displayed in a specified area within the second map area.
According to this, even if the second user cannot grasp the exact location of the moving object, the second user can at least grasp that the moving object is moving and the general location of the moving object. In addition, when the moving object moves back and forth near the boundary between the first map area and the second map area in the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area in the first map area and a predetermined area in the second map area.

In addition, this modified example shows a configuration in which, when the coordinates corresponding to the location information are included in an area of the first map area excluding the superimposed area, a moving object display is displayed in a specified area within the first map area, and, when the coordinates are included in the superimposed area, a moving object display is displayed in a specified area within the second map area.
According to this, even if the second user cannot grasp the exact location of the moving object, the second user can at least grasp that the moving object is moving and the general location of the moving object. In addition, when the moving object moves back and forth near the boundary between the first map area and the second map area in the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area in the first map area and a predetermined area in the second map area.

In addition, this modified example shows a configuration in which the first map area has an overlapping area that overlaps with the second map area, and when coordinates corresponding to location information are included in the overlapping area, a moving object display is displayed in a specified area within the first map area and a specified area within the second map area, respectively.
According to this, even if the second user cannot grasp the exact location of the moving object, the second user can at least grasp that the moving object is moving and the general location of the moving object. In addition, when the moving object moves back and forth near the boundary between the first map area and the second map area in the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area in the first map area and a predetermined area in the second map area.

In addition, this modified example shows a configuration in which the display mode of the moving object display differs (for example, flashing or lit) depending on whether the coordinates corresponding to the location information are included in the first map area excluding the superimposition area or are included in the superimposition area.
This provides the advantage that a user of the information display device can easily identify whether or not the coordinates corresponding to the position information are in an overlapping area.

[Third Modification (3)]
The low-discriminability vehicle location area may be divided into stages of low discriminability. For example, in the third embodiment, the electronic map area MR displayed on the display unit 24 of the administrator terminal 20 is divided into four areas, 2×2 in length and width.
In contrast to this, for example, it may be possible to set a first low-discriminability vehicle position area that divides the electronic map area MR into nine areas with a 3 x 3 dimension vertically and horizontally, and a second low-discriminability vehicle position area that divides the electronic map area MR into four areas with a 2 x 2 dimension vertically and horizontally.

When the administrator terminal 20 separates the vehicle location area using the first low-distinctness vehicle location area, the vehicle icon is displayed based on vehicle location coordinates that have a lower degree of reduction in discernibility than when the administrator terminal 20 separates the vehicle location area using the second low-distinctness vehicle location area. Therefore, when the administrator separates the vehicle location area using the first low-distinctness vehicle location area, the administrator can grasp the vehicle location coordinates more accurately than when the administrator separates the vehicle location area using the second low-distinctness vehicle location area.

The discriminability reduction stage setting regarding whether to use the first low-discriminability vehicle location area or the second low-discriminability vehicle location area may be set by each user, for example, from a viewing restriction setting object SOB, or may be set collectively by an administrator. Also, for example, a discriminability reduction stage setting that can be set by a user may be selected based on a driving score. In this case, a setting is possible in which a user with a high driving score can select the second low-discriminability vehicle location area, while a user with a low score can only select the first low-discriminability vehicle location area.

For example, the discriminability reduction stage setting may be set to any stage of two or more. Also, if the condition is met that the degree of discriminability reduction of the first low discriminability vehicle position area is smaller than that of the second low discriminability vehicle position area, each low discriminability vehicle position area may be set to any area other than a rectangular area.

[others]
In one aspect, a system may be configured that includes an information display device and a control unit that acquires mobile body information related to a mobile body, and the control unit causes the mobile body information to be displayed on the information display device when no restrictions are set on viewing of the mobile body information, and restricts the display of the mobile body information on the information display device when the restrictions are set.

Reference Signs List 1: Mobile object management system 10: Server 20: Administrator terminal 30: Network 40: In-vehicle terminal

Claims (21)

An information processing method executed by a system including an information display device, comprising:
obtaining mobile object information relating to the mobile object;
An information processing method, comprising: when no restriction is set regarding viewing of the mobile object information, displaying the mobile object information on the information display device; and when the restriction is set, restricting the display of the mobile object information on the information display device. 2. The information processing method of claim 1,
the mobile object information includes at least location information regarding a location of the mobile object;
Displaying a map on the information display device;
When the restriction setting is not made, a moving object display associated with the location information is displayed at a position on the map corresponding to the location information, and when the restriction setting is made, the position accuracy of the display of the moving object display is reduced compared to when the restriction setting is not made. 3. The information processing method of claim 2,
When the restriction is set, the moving object display is displayed in an area different from the map. 3. The information processing method of claim 2,
When the restriction setting is set, the moving object display is displayed in a predetermined area within a map area corresponding to the location information among a plurality of map areas set on the map, based on the location information. 5. An information processing method according to claim 4,
the first map area has an overlap area that overlaps with the second map area;
when the coordinates corresponding to the position information are included in the superimposed area, the moving object display is displayed in either a predetermined area in the first map area or a predetermined area in the second map area. 6. An information processing method according to claim 5,
An information processing method which, when coordinates corresponding to the position information are included in the superimposed area, determines based on a first condition whether the moving object display is to be displayed in a predetermined area within the first map area or a predetermined area within the second map area, and then, when coordinates corresponding to the position information are again included in the superimposed area, determines based on a second condition different from the first condition whether the moving object display is to be displayed in a predetermined area within the first map area or a predetermined area within the second map area. 6. An information processing method according to claim 5,
It is possible to determine whether the moving object display is to be displayed in a predetermined area in the first map area or in a predetermined area in the second map area based on a virtual boundary line in the superimposed area,
The virtual boundary line is restricted from being viewed by a user associated with the information display device. 6. An information processing method according to claim 5,
an information processing method, when coordinates corresponding to the location information are included in an area of the first map area excluding the superimposed area and then included in the superimposed area, displaying the moving object display in a predetermined area within the first map area, and when coordinates corresponding to the location information are included in an area of the second map area excluding the superimposed area, displaying the moving object display in a predetermined area within the second map area. 6. An information processing method according to claim 5,
When coordinates corresponding to the location information are included in an area of the first map area excluding the superimposed area, the moving object display is displayed in a predetermined area within the first map area, and when the coordinates are included in the superimposed area, the moving object display is displayed in a predetermined area within the second map area. 5. An information processing method according to claim 4,
the first map area has an overlap area that overlaps with the second map area;
when the coordinates corresponding to the position information are included in the superimposed area, the moving object display is displayed in a predetermined area in the first map area and in a predetermined area in the second map area. An information processing method according to any one of claims 5 to 10,
The information processing method, wherein a display manner of the moving object display differs depending on whether the coordinates corresponding to the position information are included in the first map area excluding the superimposed area or included in the superimposed area. An information processing method according to any one of claims 1 to 11,
the moving object information includes travel information regarding a travel direction of the moving object,
When the restriction setting is not set, the moving object display is displayed on the information display device in a first aspect related to the progress information, and when the restriction setting is set, the display of the moving object information in the first aspect is restricted. An information processing method according to any one of claims 1 to 12, comprising:
the moving object information includes at least one of speed information relating to a speed of the moving object and acceleration information relating to an acceleration of the moving object;
When the restriction setting is not set, the moving object display is displayed on the information display device in a second aspect related to at least one of the speed information and the acceleration information, and when the restriction setting is set, the display of the moving object information in the second aspect is restricted. An information processing method according to any one of claims 1 to 13, comprising:
The information processing method is capable of setting the restriction and releasing the restriction based on an operation on a terminal of a first user associated with the mobile object. 15. An information processing method according to claim 14, comprising:
an information processing method comprising: transmitting, to the terminal, a request for canceling the restriction setting based on an operation of a second user associated with the information display device. 16. An information processing method according to any one of claims 1 to 15, comprising:
The information processing method, wherein the restriction setting can be performed for each type of the mobile object information. An information processing method according to any one of claims 1 to 16, comprising:
The information processing method, wherein the restriction setting can be performed for each second user associated with the information display device. 18. An information processing method according to any one of claims 1 to 17, comprising:
generating a daily report based on the mobile object information in response to a work end of a first user associated with the mobile object;
generating the daily report based on the mobile object information common to a case where the restriction is not set and a case where the restriction is set. 19. An information processing method according to any one of claims 1 to 18, comprising:
The mobile object information includes evaluation information regarding driving of a first user associated with the mobile object,
The information processing method is capable of setting the restriction when a predetermined condition regarding the evaluation information is satisfied. A program executed by an information processing device connected to an information display device,
A control unit of the information processing device controls acquisition of moving object information related to the moving object,
A program in which, when no restrictions are set regarding the viewing of the mobile body information, the control unit controls the display of the mobile body information on the information display device, and, when the restrictions are set, the control unit controls the display of the mobile body information on the information display device. An information processing device connected to an information display device,
A control unit is provided to acquire mobile object information relating to the mobile object,
The control unit displays the mobile object information on the information display device when no restriction is set regarding viewing of the mobile object information, and restricts the display of the mobile object information on the information display device when the restriction is set.

Images