Information processing method, information processing device, and program.

Abstract

To impose appropriate restrictions on the disclosure of movement history and other information concerning moving objects.SOLUTION: An information processing method executed by a system including an information display device includes steps of obtaining mobile information about a moving object, displaying mobile information on the information display device when no restriction is set on viewing the mobile information, and restricting the display of the mobile information on the information display device when the restriction has been set.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to an information processing technique for managing movement history information of a mobile object. [Background technology]

[0002] There is a social demand for more efficient management of mobile objects and their users (drivers), such as in fleet management that manages multiple mobile objects. For example, Patent Document 1 discloses a vehicle operation management device for managing the operation status of vehicles. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-38672 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when collecting movement history, etc., of a mobile object, there is a problem in that the collected movement history, etc., is viewed more than necessary by the system administrator or other users, etc., which gives the user of the mobile object an uncomfortable feeling as if they are being excessively monitored.

[0005] In order to solve the above problems, the present invention aims to realize appropriate restrictions on the disclosure of movement history and the like related to a moving object. [Means for solving the problem]

[0006] 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 regarding a mobile body, and if no restrictions are set on viewing 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. [Effects of the Invention]

[0007] According to the information processing method of the present invention, it is possible to determine whether or not to display mobile body information on an information display device based on restriction settings regarding viewing of mobile body information, thereby achieving the effect of providing a comfortable working environment for users of mobile bodies. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of a mobile object management system according to an embodiment. [Figure 2] FIG. 2 is a block diagram showing an example of information stored in a storage unit of the server according to the first embodiment. [Figure 3] FIG. 2 is a diagram showing an example of vehicle registration data according to the first embodiment. [Figure 4] FIG. 3 is a diagram showing an example of user registration data according to the first embodiment. [Figure 5] FIG. 2 is a diagram showing an example of an operation management database according to the first embodiment. [Figure 6] 4 is a flowchart showing an example of the flow of information processing according to the first embodiment. [Figure 7] FIG. 3 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. [Figure 8] 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. [Figure 9] FIG. 10 is a diagram showing an example of user registration data according to a first modified example. [Figure 10] FIG. 10 is a diagram showing an example of a restriction target item table according to a first modified example. [Figure 11] 10 is a flowchart showing an example of the flow of information processing according to the second embodiment. [Figure 12] 10 is a flowchart showing an example of the flow of information processing according to the second embodiment. [Figure 13] FIG. 10 is a diagram showing an example of a display screen displayed on a display unit of an administrator terminal according to the second embodiment. [Figure 14] 10 is a flowchart showing an example of the flow of information processing according to a second modified example. [Figure 15] 10 is a flowchart showing an example of the flow of information processing according to the third embodiment. [Figure 16] FIG. 11 is a diagram showing an example of a display screen displayed on a display unit of an administrator terminal according to the third embodiment. [Figure 17] FIG. 11 is a diagram showing a specific example of the relationship between an electronic map area and vehicle position coordinates according to a third modified example. DETAILED DESCRIPTION OF THE INVENTION

[0009] 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 duplicated 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.

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

[0011] FIG. 1 is a diagram showing an example of the system configuration of a mobile object management system 1 according to this 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 communicably connected via a network 30 (e.g., the Internet). Note that FIG. 1 illustrates only one representative component of the in-vehicle terminal 40. Furthermore, 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.

[0012] The server 10 has a function of, for example, acquiring mobile object information relating to a mobile object driven by a user using the in-vehicle terminal 40, and processing the mobile object 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 location 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. Moreover, 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.

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

[0014] The processing unit 11 is a processing device that comprehensively controls each part of the server 10 in accordance with 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, DSP, etc., and integrated circuits such as ASIC, etc.

[0015] The storage unit 12 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. 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, processing results by the various programs, etc.

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

[0017] The administrator terminal 20 is a device used, for example, by an administrator who manages mobile objects to understand the status of the mobile objects. The administrator terminal 20 is realized, for example, by a laptop personal computer, a tablet terminal, or the like. 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 position information of the mobile object.

[0018] Fig. 1 shows an example of the functional configuration of the administrator terminal 20. As shown in Fig. 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, a communication unit 27, and the like.

[0019] The processing unit 21 is a processing device that comprehensively controls each part of the administrator terminal 20 in accordance with 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, DSP, etc., and integrated circuits such as ASIC.

[0020] The storage 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 storage unit 12. The storage 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 of the various programs.

[0021] The operation unit 23 is configured to have input devices such as a keyboard, a mouse, etc., with which the user inputs various operations to the server. The operation unit 23 outputs an operation signal corresponding to the user operation to the processing unit 21.

[0022] The display unit 24 is a display device configured to include an LCD (Liquid Crystal Display), an OLED (Organic Electro-luminescence Display), or the like, and performs various displays based on display signals output from the processing unit 21.

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

[0024] The sound input unit 25 is a sound input device including a microphone, an A / D converter, etc., and performs various sound inputs based on sound input signals input to the processing unit 21.

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

[0026] The communication unit 27 is a communication device for transmitting and receiving information used within the administrator terminal 20 to and from external devices via the network 30. The configuration of the communication unit 27 can be configured similarly to the communication unit 17, for example, and therefore detailed description thereof will be omitted.

[0027] The in-vehicle terminal 40 has a function of, for example, acquiring mobile object information related to a mobile object driven by a user (driver) and transmitting 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.

[0028] Fig. 1 shows an example of the functional configuration of the in-vehicle terminal 40. As shown in Fig. 1, the in-vehicle terminal 40 is configured to include, for example, a processing unit 41, a storage 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.

[0029] The processing unit 41 to the sound output unit 46 can be configured in the same manner as the processing unit 21 to the sound output unit 26 of the administrator terminal 20, for example, and therefore a detailed description thereof will be omitted.

[0030] 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 involve, for example, transmitting information to a roadside device installed at the side of the road, and the roadside device being connected to the network 30, thereby indirectly communicating with the server 10 or the like.

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

[0032] 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 acquire the 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.

[0033] The location information acquisition unit 49B acquires location information (e.g., latitude and longitude information) of the in-vehicle terminal 40 in chronological order based on radio waves received 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 in-vehicle terminal 40 is installed in chronological order. Note that the location information acquisition unit 49B is not limited to this configuration, and any location information acquisition method may be applied. For example, the location information of the in-vehicle terminal 40 may be acquired by receiving radio waves, which are emitted by a roadside unit installed on the side of the road and contain location information specific to the roadside unit, when the mobile body equipped with the in-vehicle terminal 40 approaches.

[0034] In addition, the vehicle-mounted terminal 40 may be composed of 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).

[0035] In this case, the device held by the user, who is a passenger of 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. Alternatively, it may be a device that communicates with the user through voice input and output, such as a smart speaker.

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

[0037] The network 30 is a communication network that connects the devices together via wired or wireless connections, or both.

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

[0039] In this embodiment, a vehicle management system is illustrated as an example of a mobile object management system. 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. A user of the administrator terminal 20 (hereinafter referred to as "administrator") and a user of the in-vehicle terminal 40 (hereinafter referred to as "driver") are collectively referred to as "users" of the vehicle management system. Note that if the administrator also serves as a driver, there is no need to distinguish between the administrator terminal 20 and the in-vehicle terminal 40.

[0040] 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.

[0041] 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.

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

[0043] The vehicle name is the name of the vehicle in the vehicle management system, and for example, the name specified by the administrator when registering the vehicle in the vehicle management system is stored.

[0044] The vehicle number is the number written on the license plate (automobile registration plate) of the vehicle. The vehicle number may also be used as the vehicle ID.

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

[0046] 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 position class, a business status, and other registration information are stored in association with each other.

[0047] 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, if a user who operates a specific vehicle is uniquely determined, the vehicle ID may be set to the user ID. In this case, the in-vehicle terminal 40 may be configured as an integrated device that collects mobile object information and a device held by the driver of the mobile object.

[0048] The user name is the name of the user who uses the vehicle management system, and for example, the name registered when the user uses the vehicle management application is stored.

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

[0050] 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 administrator terminal 20. The work status is an example of situation information. In this example, the following four types of business status are shown. While on duty (e.g., while driving to a destination) While on duty (during working hours and on standby or patrol, etc.) During rest (during working hours but taking a temporary break, etc.) ·Outside working hours The work status may be automatically updated according to the work schedule stored in the other registration information, for example. Other work statuses may also be defined.

[0051] 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 various information.

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

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

[0054] 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. Note that the operation management data may also store information about the vehicle's departure point, intermediate points, and destination. The information about the vehicle's departure point and destination is an example of situation information.

[0055] The fleet management ID is identification information for identifying 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 vehicle that was operated. The business status stores, for example, the business status of the user when the vehicle is in operation.

[0056] The vehicle operation data is data for storing various information about the operated vehicle, such as the date and time, vehicle position coordinates, acceleration status, drive recorder image URI, and other information, which are stored in association with each other. The vehicle operation data is an example of mobile object information.

[0057] 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, for example. 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.

[0058] 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, the operational permissions for operation management data can be defined as, for example, "view," which is the permission to view operation management data; "edit," which is the permission to change user ID, vehicle ID, business status, destination, etc.; and "delete," which is the permission to erase operation management data. In addition, the operating user can be defined as "self," which means that the operation is performed by a user identified by a user ID stored in the operation management data; "same position class," which means that 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.

[0059] For example, in the operation authority management data in Figure 5, it is stored that "myself" has the operation authority for "viewing" and "editing", but does not have the operation authority for "deleting". Also, it is stored that users in the "same position class" only have the operation authority for "viewing", and "everyone" has no operation authority at all.

[0060] The operation authority management data may store only "view" or any combination of operation authorities such as "view" and "delete." Also, a user with 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 with the same position class. A user with 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.

[0061] 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.

[0062] An example of the processing procedure in Example 1 will be described below. Fig. 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.

[0063] 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.

[0064] 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 on the operation authority related to the operation management data of this operation set by the user who operates the vehicle, the destination, etc.

[0065] In addition, 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 operating the vehicle (for example, the in-vehicle terminal 40 of another user whose setting has been permitted by the user operating the vehicle), and transmitted to the server 10.

[0066] When the control unit 11 of the server 10 receives the 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).

[0067] 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.

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

[0069] The control unit 41 of the in-vehicle terminal 40 determines whether or not the operation of the vehicle will end based on, for example, an operation input to the operation unit 43 or a signal input from an in-vehicle ECU (not shown) (B130). If it is determined that the operation of the vehicle will end (B130: YES), the control unit 41 of the in-vehicle terminal 40 transmits vehicle operation end information indicating that the operation of the vehicle will end 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.

[0070] If it is determined that the 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). If it is determined that the 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 for the reception of vehicle information again and executes step S120.

[0071] In addition, 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.

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

[0073] 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 it is possible to view and operate the traffic management data of the specified traffic management ID based on the received traffic management data viewing request information (S150). More specifically, it determines whether or not the user of the manager terminal 20 is allowed to view the data by referring to the position class of the user of the manager terminal 20, the position class of the user ID of the specified traffic management data, and the operation authority management data of the specified traffic management data. Note that it is also possible to similarly determine operation authority other than viewing operations.

[0074] If it is determined that the user of the administrator terminal 20 is able to view and operate the operation management data (S150: YES), the control unit 11 of the server 10 transmits the operation management data to the administrator terminal 20 via the communication unit 17 (S160). If it is determined that the viewing operation is not permitted (S150: NO), the control unit 11 of the server 10 terminates the processing. Note that, if it is determined that the viewing operation is not permitted (S150: NO), the control unit 11 of the server 10 may transmit information indicating that the viewing operation is not permitted to the administrator terminal 20, and the control unit 21 of the administrator terminal 20 may display the received information indicating that the viewing 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 administrator terminal 20 may display a portion of the received operation management data on the display unit 24.

[0075] When it is determined that the fleet 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 fleet management data (A130).

[0076] The above processing has been exemplified as an example in which the operation management data is referenced on the administrator terminal 20 after the vehicle has been operated, but if the operation management data for a vehicle in operation is to be referenced on the administrator 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.

[0077] Furthermore, the control unit 41 of the in-vehicle terminal 40 may acquire operation setting information at any timing 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.

[0078] 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.

[0079] Figure 7 shows an example of a driving history viewing screen for user "BB," whose job title is "Staff," to view the vehicle's operation management data after the vehicle was operated on August 8, 2021. This screen displays the date the operation management data was collected at the top, and below that, the vehicle's route is displayed on an electronic map based on the vehicle's position coordinates in the collected vehicle operation data. Locations where dangerous maneuvers, such as sudden braking or sudden steering, were performed may also be displayed along with the route. Below the route, a driving score calculated on a scale of 100 points based on the acceleration status of the vehicle operation data is displayed. The driving score can be calculated, for example, according to the invention disclosed in Japanese Patent Publication No. 2006-243856. The distance and time traveled by the vehicle during this operation are displayed at the bottom, and below that, the vehicle's location at each time is listed and linked to its address.

[0080] For example, when a change of viewing operation authority is selected from the setting menu button on the driving history viewing screen, a viewing restriction setting object SOB is displayed, for example, by rising from the bottom of the screen. The viewing restriction setting object SOB is configured to display a selection item of "Viewable only by BB" that sets viewing permission to "yourself" only, a setting item of "Viewable only by staff" that gives viewing permission to "yourself" and "same position class," and a selection item of "Viewable by everyone" 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.

[0081] 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 "Viewable only by BB" selection item is selected in the viewing restriction setting object SOB in FIG. 7. On 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 indicates that user "AA" of the position class "Manager" is logged in to the administrator terminal 20. To the right of the management menu selection area, when the "Driving History" menu is selected, a driving history list display is displayed to display an overview of the operation management data. The driving history list display displays the operation date and time, the name of the user who operated the operation, and the position class for each operation management data in a row. For example, when the column "August 8th 8:02~10:34 Staff BB" that user "BB" has set as viewable only to "himself" is tapped, an electronic map area MR showing the vehicle's route is displayed to the right of the driving history list display. However, since user "AA" does not have the authority to view this operation management data, a view restriction object RD indicating that viewing of the route is restricted is displayed in the electronic map area MR, and user "AA" cannot check the route.

[0082] [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 is configured to display the mobile body information on the information display device if no restrictions are set on viewing the mobile body information (e.g., when the user of the administrator terminal 20 has viewing authority), and to restrict the display of the mobile body information on the information display device if restrictions are set (e.g., when the user of the administrator terminal 20 does not have viewing authority). 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.

[0083] In addition, this embodiment shows a configuration in which restriction settings can be made and released based on operations on the terminal (e.g., the in-vehicle terminal 40) of a first user (e.g., the user of the in-vehicle terminal 40) associated with the mobile body. This allows the first user to set restrictions on viewing of the mobile body information, thereby providing an advantage of improving user convenience.

[0084] [First Modification (1)] In the first embodiment, an example in which 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.

[0085] FIG. 9 shows an example of the data structure of second user registration data 123B, which is an example of the data structure of 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, job status, and other registered information can be configured in the same way as the first user registration data 123A, for example.

[0086] 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 with the same job title can view the traffic management data associated with this user. Level 2: Only you can view the traffic management data associated with this user. In addition to the above three levels, an information restriction level may be set that allows users of a higher position class than the user's position class and the user himself / herself to 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 privileged position classes may be able to perform any operation without being bound by information restriction levels.

[0087] In the example of Fig. 9, the information restriction level for user "AA" is "Level 2," so the operation management data for the vehicle operated by user "AA" can only be viewed by user "AA." Also, the information restriction level for user "CC" is "Level 1," so the operation management data for the vehicle operated by user "CC" can only be viewed by users with a job title of "Staff."

[0088] When setting the information restriction level, it may be possible to prevent the setting of the operation authority management data for the operation management data. Furthermore, when the information restriction level and the operation authority management data for the operation management data are used in combination, the operation authority based on the information restriction level may be given priority, or the operation authority based on the operation authority management data may be given priority.

[0089] Furthermore, 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 for each user based on, for example, the average value of the driving score. In this case, for example, if the average value of the user's driving score over a predetermined period (for example, the past month) exceeds a safe driving setting value (for example, 90 points), the information restriction level for that user is set to "Level 2," and if it is below that value, the information restriction level for that user is set to "Level 1." Furthermore, if the average value of the driving score falls below a dangerous driving setting value (for example, 50 points), the information restriction level for that user is set to "Level 0." This allows users with a high driving score to be judged as a good driver and the scope of viewing of their driving management data to be narrowed. Also, if a user's driving score is low, the driving management data can be made public to encourage mutual monitoring and to warn users who tend to drive dangerously.

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

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

[0092] 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, viewing modes are types of viewing methods for viewing operation management data. Here, the following three types of display modes are shown as examples of viewing modes. - "Real-time display" for viewing fleet 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 (for example, one day). - "Vehicle daily report display" for viewing all the operation management data for a specific vehicle for a specified period (for example, one day). The specified period for "Driver Daily Report Display" and "Vehicle Daily Report Display" may be the period from the start of work to the end of work for the user operating the vehicle, and each daily report may be automatically created when work is completed.

[0093] When the "User Name" item is set to hidden, the name of the user operating 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 the operation management data with the user name anonymized to the administrator terminal 20. Also, in "Driver Daily Report Display," the operation management data related to that user cannot be viewed. If the item "Vehicle location information" is set to hidden, the vehicle location coordinates of the vehicle operation data will not be viewable in "Real-time display" and "Driver daily report display." Also, in "Vehicle daily report display," the operation management data related to that vehicle will not be viewable. Similarly, for other items subject to restriction, if the item is set to be hidden, the item in the operation management data cannot be viewed.

[0094] In addition, when restricting items to be made unavailable for viewing, the server 10 may transmit the operation management data without concealing it, and the restricting items may be displayed on the administrator terminal 40 in a concealed manner, or may not be displayed at all.

[0095] Furthermore, the restriction items may be set by each user, for example, using a viewing restriction setting object SOB, or may be set collectively by an administrator. Furthermore, the restriction 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 that a user with a high driving score can set "Dash Cam Images" to not be displayed, but a user with a low driving score cannot set it to not be displayed.

[0096] The users to whom the restriction on the restricted items applies may be "everyone" except for "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 setting of the restricted items may be added to the operation authority management data of each operation management data so that it can be set for each operation management data, or may be incorporated into the information restriction level so that it can be set for each user.

[0097] Furthermore, the setting of the restricted items may be set for each viewing mode. For example, if viewing of "vehicle location coordinates" is restricted as a restricted item, the vehicle location coordinates can be set to be unavailable in the viewing mode "real-time display," but can be set to be available in the viewing modes "driver daily report display" and "vehicle daily report display."

[0098] This modified example shows a configuration in which restriction settings can be made for each type of mobile object information (for example, restriction target item "user name" or restriction target item "vehicle location information"). This provides the advantage of enabling more flexible restriction setting depending on the type of mobile body information.

[0099] In addition, this modified example includes generating a daily report (e.g., information for display in the viewing mode "Driver Daily Report Display") based on mobile body information in response to the end of work for a first user (e.g., a user of the in-vehicle terminal 40) associated with the mobile body, and shows a configuration in which a daily report based on common mobile body information is generated whether or not restrictions are set. This provides the advantage that the user of the information display device can display the mobile object information in the daily report regardless of the restriction setting, and can accurately grasp the work of the first user.

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

[0101] [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 set automatically based on the user's business status when driving a vehicle.

[0102] 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.

[0103] [First Modification (4)] In the first embodiment, a vehicle management system for automobiles is exemplified as an example of a mobile object management system, but the present invention is not limited to this. 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. Furthermore, by installing the in-vehicle terminal 40 in 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.

[0104] [Second Example] 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 operating the vehicle. The contents described in the second embodiment can be applied to any of the other embodiments and modifications.

[0105] An example of the processing procedure in Example 2 will be described below. Figures 11 and 12 are flowcharts showing the processing performed by the server 10, the administrator terminal 20, and the in-vehicle terminal 40 in cooperation with each other, from delegating the authority to view vehicle operation and operation management data to viewing vehicle operation data.

[0106] If it is determined that operation management data has not been received from the server 10 (A120: NO), the control unit 21 of the administrator terminal 20 displays a screen on the display unit 24 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 has been 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 viewing operation authority.

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

[0108] If it is determined that request information for permission to view operation management data has been received from the server 10 (B210: YES), the control unit 41 of the in-vehicle terminal 40 displays on the display unit 44 a screen for determining whether or not to grant the user of the administrator terminal 20 permission to view operation management data (B220). For example, if it is determined that permission to view has been selected based on the 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 administrator terminal 20 is given the authority to view the operation management data to the server 10 via the communication unit 47 (B230).

[0109] 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 administrator 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 administrator 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 (for example, 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.

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

[0111] If it is determined that the fleet management data has been received from the server 10 (A240: YES), the control unit 21 of the manager terminal 20 causes the display unit 24 to display the received fleet management data (A250).

[0112] The above processing has been exemplified as an example in which the operation management data is referenced on the administrator terminal 20 after the vehicle has been operated, but if the operation management data for a vehicle in operation is to be referenced on the administrator 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.

[0113] In addition, with respect to restrictions on operations other than browsing operations, it is possible to request the lifting of restrictions on operations in the same way as with browsing operations.

[0114] 7, Fig. 13 shows 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 BB" is selected in the viewing restriction setting object SOB on the in-vehicle terminal 40 of user "BB." 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. To the right of the management menu selection area, based on the selection of the "Real Time" menu, a vehicle icon and vehicle name are displayed in the electronic map area MR in association with the current vehicle position coordinates. To the right of the electronic map area MR, a vehicle status list display area is displayed for displaying a list of the statuses of vehicles managed by the vehicle management application. The vehicle status list display area is configured to display, for each vehicle, the vehicle name, the name of the user operating the vehicle, and the vehicle status (for example, whether the vehicle is moving or stopped) in association with each other.

[0115] In this example, the user "BB" is driving a vehicle named "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. Also, the vehicle status list display area displays that the vehicle's status for the vehicle named "Tokyo 002" is that it is traveling, but the vehicle's location coordinates are not displayed.

[0116] For example, a situation may arise 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, an operation management data viewing authority request determination object ARD is displayed, which is indicated by the title "Requesting permission to display vehicle location." This operation management data viewing authority request determination object ARD is provided with a comment input field for notifying user "BB" 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 request button for permission to view operation management data, indicated by the word "Request," is displayed to request permission to view operation management data, and a cancel button is displayed to cancel the operation.

[0117] When the traffic management data viewing authority request button is tapped, a notification that user "AA" has requested that the viewing operation restriction on the vehicle position coordinates be lifted is displayed on user "BB's" in-vehicle terminal 40. When user "BB" 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 "AA" can grasp the vehicle position.

[0118] [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). This has the effect of improving convenience for the second user, even if a restriction is set, by allowing the first user of the terminal to request that the restriction be lifted if necessary, while taking into consideration the first user's discomfort or aversion to viewing information (for example, while preventing the driver from feeling that they are being excessively monitored).

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

[0120] FIG. 14 is an example of a flowchart in this modified example. When it is determined that the 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 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 in the behavior of the vehicle include the following. - When sudden acceleration, deceleration or operation exceeding a certain threshold is detected in the acceleration status. -When 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's location coordinates. - When automatic analysis of dashcam images detects drowsy driving, cell phone use, or lane departure. - If a vehicle collision is detected. -If the airbag is confirmed to be deployed. - If you drive a specified distance (e.g., 200 km) or more in one day. - When a trigger is issued by the vehicle user (for example, pressing the emergency call button).

[0121] 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 to the administrator terminal 20, together with the operation management data, vehicle abnormality detection information indicating that a specific event has occurred in the behavior of the vehicle.

[0122] When displaying the operation management data of a vehicle in operation in real time, the control unit 11 of the server 10 may execute step S250 regardless of the determination result of step S220. In this case, when it is determined that a specific event has occurred in the behavior of the vehicle (S250: YES), vehicle abnormality detection information may be transmitted to the manager terminal 20 of a specific user (e.g., the operations manager) associated with the vehicle ID or the user ID of the person operating the vehicle. Then, the manager terminal 20 may display the received vehicle abnormality detection information.

[0123] In this case, the consent of the user of the in-vehicle terminal 40 may or may not be required to view the fleet management data for which viewing restrictions have been set.

[0124] Furthermore, the operation authority classification of the operation authority management data may be set to allow or prohibit operation, or to allow operation conditionally 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 drive recorder images are set to be viewable only by "the user" and vehicle location coordinates are set to be viewable by "everyone," when a specific event is detected, it may be possible to request permission to view drive recorder images for a predetermined period (e.g., 30 seconds before and after) at the time of detection.

[0125] Furthermore, the lifting of the operation restriction on the fleet management data may continue until the next setting operation for the operation restriction is performed, or may be temporary (for example, for 24 hours).

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

[0127] An example of the processing procedure in Example 3 will be described below. Fig. 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.

[0128] When receiving the traffic management data viewing request information from the administrator 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), similarly to S150 in Fig. 6. If the user of the administrator 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 administrator 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 process of lowering the coordinate identifiability of the vehicle position coordinates among the operation management data. The coordinate identifiability lowering process is a process of making it difficult to identify the vehicle position coordinates on the electronic map based on the position information (e.g., latitude and longitude information) of the in-vehicle terminal 40. For example, when the coordinate identifiability lowering process is executed, the probability that the vehicle icon will be displayed at a position different from the vehicle position coordinates on the electronic map increases compared to when the coordinate identifiability lowering process is not executed (one example of a decrease in the position accuracy of the displayed vehicle icon). The coordinate identifiability lowering process of the vehicle position coordinates may also be called a resolution lowering process.

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

[0130] Here, the low-distinguishability vehicle position area in the electronic map may be divided, for example, in the following manner. The area is divided into rectangular areas defined by predetermined long and short sides (for example, 500m square). Note that instead of rectangular areas, the area may be divided into polyhedral areas such as equilateral triangles or regular hexagons. - Separation by address area defined by place name. For example, an address area defined by "XX town" includes vehicle position coordinates that are determined to be within "XX town" regardless of the "block" or "banchi" number. The area around the home (for example, the area around the user's home while driving) is divided into coarse areas (for example, a rectangular area of ​​1 km x 1 km), and the area around the work area (for example, the area around the company or the area around the places visited) is divided into fine areas (for example, a rectangular area of ​​200 m x 200 m). The method of dividing the low-discriminability vehicle location areas 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," while the low-discriminability vehicle location area of ​​another user may be set to an address area divided by "banchi."

[0131] Furthermore, the way in which the low-distinguishability vehicle location area is divided (for example, the position of the rectangular area) may be changed every certain period (for example, every six hours).

[0132] 16 is an example of a display screen of the 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 into, for example, 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 necessarily need to be displayed on the actual display screen.

[0133] Below each low-distinguishability vehicle location area, a vehicle location confirmation box BX is displayed to display the vehicle location in the operation management data after the coordinate distinguishability reduction process for the vehicle location coordinates has been executed. For example, in area "A," the vehicle location 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 positioned further to the left. Also, an arrow icon indicating the vehicle's direction of travel may be added to the vehicle icon. This allows a rough understanding of the movement of vehicles within the low-distinguishability vehicle position area. Furthermore, for example, a parked vehicle may be distinguished by adding a "stopped" icon to the vehicle icon.

[0134] For example, in area "B," a vehicle icon with the vehicle name "Tokyo 004," whose location information is permitted to be viewed, is displayed in the area where the vehicle location confirmation box BX is displayed by default. In this case, the vehicle location 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. Also, 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 (e.g., whether traveling or stopped) of a vehicle whose location information is not permitted to be viewed. The traveling speed may be displayed superimposed on the vehicle icon.

[0135] 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.Furthermore, for vehicles whose location information is permitted to be viewed, the speed (or acceleration) while moving may be displayed within the vehicle icon, and for vehicles whose location information is not permitted to be viewed, the speed (or acceleration) while moving may not be displayed within the vehicle icon.

[0136] For example, in area "D," if no vehicle is present in this low-discriminability vehicle location area, the vehicle location confirmation box BX may not be displayed. This allows the user to quickly determine the low-discriminability vehicle location area where a vehicle is present.

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

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

[0139] Furthermore, unlike the electronic map area MR illustrated in the above display example, it is not necessary to place a vehicle location confirmation box BX for each low-distinct vehicle location area. In this case, it is possible to place one vehicle location confirmation box BX within or outside the electronic map area MR, and display a vehicle icon in that vehicle location confirmation box BX regardless of the low-distinct vehicle location area to which the vehicle belongs. This makes it easy to identify vehicles with low-distinct location coordinates even when vehicles are distributed over a wide area.

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

[0141] In addition, this embodiment shows a configuration in which, when viewing restrictions are set on the location information of a mobile body, the mobile body display is displayed in an area different from the map (for example, a vehicle location 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 a restriction has been set on viewing the location information of each mobile object.

[0142] In addition, this embodiment shows a configuration in which, when viewing restrictions are set on the location information of a moving body, a moving body display is superimposed on a predetermined area (e.g., a vehicle location confirmation box BX) within a map area corresponding to the location information among multiple map areas (e.g., low-identification vehicle location areas) set on a map based on the location information. This has the effect of allowing the user of the information display device to easily identify at a glance information on whether or not viewing restrictions have been set on the location information of each mobile object, as well as the detailed or rough location information of the mobile object.

[0143] In addition, this embodiment shows a configuration in which the mobile body information includes progress information regarding the direction of travel of the mobile body, and if no viewing restriction is set for the mobile body's location information, the mobile body display (e.g., a vehicle icon) is displayed on the information display device in a first mode related to the progress information (e.g., a display mode in which an arrow icon is added), and if a viewing restriction is set for the mobile body's location information, the display of the mobile body information in the first mode is restricted. This has the effect of preventing the user of the mobile object from feeling that excessive surveillance is being conducted, since the user of the information display device cannot grasp the direction of travel of the mobile object when restrictions are set on viewing the location information of the mobile object.

[0144] In addition, this embodiment shows a configuration in which the mobile body information includes speed information related to the moving speed of the mobile body or acceleration information related to the acceleration of the mobile body, and if no viewing restriction is set for the mobile body's location information, the mobile body display (vehicle status display in the vehicle location 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 if a viewing restriction is set for the mobile body's location information, the display of the mobile body information in the second mode is restricted. This has the effect of preventing the user of the mobile object from feeling that excessive surveillance is being conducted, since the user of the information display device cannot grasp the moving speed of the mobile object when a viewing restriction is set on the location information of the mobile object.

[0145] [Third Modification (1)] In the third embodiment, for example, the determination as to whether or not access to the location information is restricted is made according to the settings of the user who operates the vehicle, but this is not limiting. For example, the following three types of settings may be possible as access restriction settings. - Unable to view (vehicle location coordinates are not displayed on the electronic map or in the vehicle location confirmation box BX). - Can be viewed with low distinctiveness (a vehicle icon based on the vehicle location coordinates is displayed in the vehicle location confirmation box BX). -Highly identifiable (vehicle icons are displayed on the electronic map based on the vehicle's location coordinates).

[0146] The setting of the access restriction is not limited to being based on the user setting, and may be set automatically as follows, for example. -Cannot be viewed near the user's home address or can be viewed with low visibility. - Highly recognizable when viewed 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 data cannot be viewed. If the user's driving score is below a certain fail value (e.g., 40 points), the data can be viewed with high distinctiveness. If the user's driving score is any other value, the data 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 within a specified period of time. Normally, the data will follow user settings, but after a certain period of time (e.g., one week) has passed since the end of operation, the data can be viewed with high visibility. Normally, the system follows user settings, but it can be viewed with high discrimination for a specified period (for example, 5 minutes) before and after designated work times (visit times, delivery times, etc.). In addition, it can be viewed with low discrimination or not during outside working hours or during temporary breaks.

[0147] [Third Modification (2)] In the third embodiment, an example has been shown in which adjacent low-discriminability vehicle location areas are separated so as not to overlap each other, but this is not limiting. For example, the boundaries of adjacent low-discriminability vehicle location areas may be overlapped. An example of a low-distinguishability vehicle position area in the electronic map area MR in this modification is shown in Figure 17. In this figure, area "A" and area "B" overlap in the overlap area of ​​area "A" and area "B" indicated by the dashed line. Here, consider a case where the vehicle location coordinates of a vehicle named "Tokyo 001," whose location information is not permitted to be viewed, move from vehicle location "X" to vehicle location "Y" and then to vehicle location "Z." At this time, at vehicle location "X," a vehicle icon is displayed in the vehicle location confirmation box BX corresponding to area "A." If the vehicle location subsequently moves to the overlapping area between areas "A" and "B," a vehicle icon can be configured to be displayed in the vehicle location confirmation box BX corresponding to area "A" based on the fact that the vehicle location was in area "A" of areas "A" and "B" until it left area "A." Therefore, at vehicle location "Y," a vehicle icon is displayed in the vehicle location confirmation box BX corresponding to area "A." Then, when the vehicle location leaves the overlapping area between areas "A" and "B," a vehicle icon can be configured to be displayed in the vehicle location confirmation box BX corresponding to area "B." Therefore, at vehicle location "Z," a vehicle icon is displayed in the vehicle location confirmation box BX corresponding to area "B."

[0148] By superimposing the low-discriminability vehicle location area in this manner, the display within the vehicle location confirmation box BX is prevented from reacting sensitively when the vehicle location coordinates move back and forth across the low-discriminability vehicle location area, making it easier to view the vehicle icon and preventing the vehicle location from being specifically inferred from changes in the display within the vehicle location confirmation box BX.

[0149] In addition, when the vehicle position moves into the overlapping area between area "A" and area "B," the vehicle icon may be displayed in the vehicle position confirmation box BX corresponding to area "B" based on the fact that the vehicle position has moved from area "A" excluding the overlapping area of ​​area "A" to area "B" (the overlapping area of ​​area "B").

[0150] In addition, when the vehicle position moves into the overlapping area between 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."

[0151] In addition, 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 different manner than when the vehicle position is within a single low-distinguishability vehicle position area, such as by flashing the vehicle icon to indicate that the vehicle is moving between areas.

[0152] 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."

[0153] For example, as a condition for determining which vehicle position confirmation box BX should display a vehicle icon, not only the vehicle position but also a condition other than the vehicle position may be used. For example, the condition may be one or more of vehicle-related parameters other than position information, such as vehicle acceleration information or speed information (e.g., acceleration or speed at or before entering the superimposed area), time information (e.g., time of entry into the superimposed area, current time within the superimposed area), and environmental parameters, such as weather information (weather, temperature, humidity, wind direction, wind speed at or before entering the superimposed area).

[0154] Then, 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 superimposed area, or the above decision may be made based on the parameter (one or more) 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 superimposed area from area "A", making it easier to grasp the movement by switching the display at an early timing.

[0155] 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 or the like each time the vehicle position enters the overlap area.

[0156] In this way, depending on the different circumstances when entering the overlap area, the parameters that contribute to the above determination may differ, or the contents or numerical 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.

[0157] 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 may not be a straight line but 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 also be set for each user. In this case, the second user (administrator) may be prevented from viewing the virtual boundary line within the overlapping area by not displaying the virtual boundary line, etc. In other words, the display of the virtual boundary line to the second user may be restricted.

[0158] This modified example shows a configuration in which a first map area (for example, area "A" of a low-discriminability vehicle location area) has an overlapping area that overlaps with a second map area (for example, area "B" of 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 (vehicle location confirmation box BX corresponding to area "A") or a predetermined area within the second map area (vehicle location confirmation box BX corresponding to area "B"). According to this, when the coordinates corresponding to the location information of a mobile object move across the first map area and the second map area, by providing an overlapping area, it becomes difficult for the user of the information display device to specifically guess the location of the mobile object, and as a result, it is possible to provide a comfortable work environment without making the user of the mobile object feel that they are being excessively monitored.

[0159] 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 superimposition area and then included in the superimposition area, a moving body display is displayed in a predetermined area within the first map area, and, when the coordinates are included in an area of ​​the second map area excluding the superimposition area, a moving body display is displayed in a predetermined area within the second map area. This allows the second user to know that the moving object is moving and the general location of the moving object, even if the second user cannot know the exact location of the moving object. Also, when the moving object moves back and forth near the boundary between the first map area and the second map area within the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area within the first map area and a predetermined area within the second map area.

[0160] 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, the moving body display is displayed in a predetermined area within the first map area, and, when the coordinates are included in the superimposed area, the moving body display is displayed in a predetermined area within the second map area. This allows the second user to know that the moving object is moving and the general location of the moving object, even if the second user cannot know the exact location of the moving object. Also, when the moving object moves back and forth near the boundary between the first map area and the second map area within the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area within the first map area and a predetermined area within the second map area.

[0161] 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. This allows the second user to know that the moving object is moving and the general location of the moving object, even if the second user cannot know the exact location of the moving object. Also, when the moving object moves back and forth near the boundary between the first map area and the second map area within the superimposed area, it is possible to prevent the moving object display from frequently switching between a predetermined area within the first map area and a predetermined area within the second map area.

[0162] 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 included in the superimposition area. This provides the advantage that the user of the information display device can easily identify whether or not the coordinates corresponding to the position information are in the overlap area.

[0163] [Third Modification (3)] The low-distinguishability vehicle location area may be divided into stages of low discernibility. 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, each of which is 2x2 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, 3x3 in length and width, and a second low-discriminability vehicle position area that divides the electronic map area MR into four areas, 2x2 in length and width.

[0164] When the area is divided by the first low-discriminability vehicle location area, the vehicle icon is displayed on the administrator terminal 20 based on vehicle location coordinates with a lower degree of reduction in discriminability than when the area is divided by the second low-discriminability vehicle location area. Therefore, when the area is divided by the first low-discriminability vehicle location area, the administrator can grasp the vehicle location coordinates more accurately than when the area is divided by the second low-discriminability vehicle location area.

[0165] The discriminability reduction stage setting regarding which low-discriminability area 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, using a viewing restriction setting object SOB, or may be set collectively by an administrator. Furthermore, 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 driving score can select only the first low-discriminability vehicle location area.

[0166] For example, the discriminability reduction stage setting may be set to any number of stages equal to or greater than two.Furthermore, if the condition is satisfied that the degree of discriminability reduction of the first low-discriminability vehicle location area is smaller than that of the second low-discriminability vehicle location area, each low-discriminability vehicle location area may be set to any area other than a rectangular area.

[0167] [others] In one aspect, a system may be configured that includes an information display device and a control unit that acquires mobile body information regarding a mobile body, and the control unit displays the mobile body information on the information display device when no restrictions are set regarding 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. [Explanation of symbols]

[0168] 1. Mobile Management System 10 Servers 20 Administrator terminal 30 Network 40 In-vehicle terminal

Claims

1. An information processing method executed by a system including an information display device, Obtaining mobile object information relating to the mobile object; Obtaining driving score information of a user associated with the moving object; generating, based on the mobile object information, a first content to be displayed in a real-time display viewing mode and a second content to be displayed in a viewing mode different from the real-time display viewing mode; determining whether the driving score information satisfies a predetermined condition; If the condition is satisfied, restricting the display of the first content on the information display device while permitting the display of the second content on the information display device; An information processing method, including:

2. 2. The information processing method according to claim 1, The driving score information is calculated based on the moving object information. Information processing methods.

3. 3. The information processing method according to claim 1, further comprising: The moving object information is acquired in time series, The determination is made based on acquisition of the mobile object information. Information processing methods.

4. In a system including an information display device, Obtaining mobile object information relating to the mobile object; Obtaining driving score information of a user associated with the moving object; generating, based on the mobile object information, a first content to be displayed in a real-time display viewing mode and a second content to be displayed in a viewing mode different from the real-time display viewing mode; determining whether the driving score information satisfies a predetermined condition; If the condition is satisfied, restricting the display of the first content on the information display device while permitting the display of the second content on the information display device; A program that executes.

5. A system including an information display device, a mobile object information acquisition unit that acquires mobile object information related to the mobile object; a driving score information acquisition unit that acquires driving score information of a user associated with the moving object; a content generation unit that generates, based on the mobile object information, a first content to be displayed in a real-time display viewing mode and a second content to be displayed in a viewing mode different from the real-time display viewing mode; a determination unit that determines whether the driving score information satisfies a predetermined condition; a restriction unit that, when the requirement is satisfied, restricts display of the first content on the information display device while permitting display of the second content on the information display device; A system comprising:

Images