Vehicle management server, communication terminal, vehicle management program, and vehicle management method

Abstract

To provide a vehicle management server, communication terminal, vehicle management program, and vehicle management method, which satisfy a request of an owner to check the status of a vehicle being rented out while giving consideration to privacy of a robot taxi user.SOLUTION: In a vehicle management system 1, a vehicle management server 50 for managing a vehicle rented out as a robot taxi to a user from an owner terminal 30 is configured to transmit vehicle location information indicative of a distance to the vehicle from a current location of an owner or an area the vehicle 10 is currently located in to the owner terminal 30 when the vehicle 10 is operating as a robot taxi.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a vehicle management server, a communication terminal, a vehicle management program, and a vehicle management method. [Background technology]

[0002] Patent Document 1 discloses a taxi fare guidance system. This system displays and guides the taxi fare to a destination specified by a taxi user before the taxi is used. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2005-172777 A Summary of the Invention [Problem to be solved by the invention]

[0004] Patent Document 1 does not propose renting out a personally owned vehicle (POV) as a robot taxi. When renting out a POV as a robot taxi, some owners may want to check the status of their vehicle while it is being rented out as a robot taxi. On the other hand, in consideration of the privacy of robot taxi users, it is not appropriate to provide the owner with all location information of the vehicle while it is operating as a robot taxi.

[0005] The present disclosure has been made in consideration of the above-mentioned problems, and aims to satisfy the needs of robot taxi owners to check the status of their rented vehicles while respecting the privacy of robot taxi users. [Means for solving the problem]

[0006] A vehicle management server according to the present disclosure manages vehicles that are rented out by owners to users as robot taxis. When the vehicle is operating as a robot taxi, the vehicle management server transmits vehicle location information to the owner's communication terminal. The vehicle location information is the distance from the owner's current location to the vehicle, or the area in which the vehicle is currently located.

[0007] The communication terminal according to the present disclosure is operated by an owner of a vehicle that is rented to a user as a robot taxi. When the vehicle is operating as a robot taxi, the communication terminal displays vehicle position information of the vehicle on a screen in a first display format. When the vehicle is not operating, the communication terminal displays the vehicle position information on a screen in a second display format different from the first display format.

[0008] A vehicle management program according to the present disclosure manages a vehicle that is rented out by an owner to a user as a robot taxi. The vehicle management program is configured to cause a computer to execute a process of transmitting vehicle location information to a communication terminal of the owner when the vehicle is operating as a robot taxi. The vehicle location information is the distance from the owner's current location to the vehicle, or the area in which the vehicle is currently located.

[0009] A vehicle management method according to the present disclosure manages a vehicle that is rented out to a user as a robot taxi by an owner. The vehicle management method includes transmitting vehicle location information to a communication terminal of the owner when the vehicle is operating as a robot taxi. The vehicle location information is a distance from the owner's current location to the vehicle, or an area in which the vehicle is currently located. Effect of the Invention

[0010] According to the vehicle management server, vehicle management program, and vehicle management method of the present disclosure, when a vehicle is operating as a robot taxi, the distance from the owner's current location to the vehicle or the area in which the vehicle is currently located is transmitted as vehicle location information to the owner's communication terminal. The vehicle location information transmitted in this manner is approximate location information, rather than accurate enough to identify the vehicle's current location. This makes it possible to satisfy the owner's request to check the status of the vehicle while respecting the privacy of the robot taxi user.

[0011] In addition, according to the communication terminal of the present disclosure, the display format of the vehicle position information on the screen of the communication terminal is switched between a first display format and a second display format, which are different from each other, depending on whether the vehicle is operating as a robot taxi. With such a configuration, for example, when the vehicle position information is displayed in the first display format with a rougher resolution than that in the second display format, it is possible to satisfy the owner's request to check the status of the rented vehicle while respecting the privacy of the robot taxi user. [Brief description of the drawings]

[0012] [Figure 1] 1 is a diagram illustrating an example of a configuration of a vehicle management system according to an embodiment; [Diagram 2] 2 is a flowchart showing an example of a process executed in the vehicle management system shown in FIG. [Diagram 3] 2 is a diagram showing an example of a screen of the owner terminal shown in FIG. 1. [Figure 4] 10 is a flowchart showing an example of a process executed in a vehicle management system according to a modified example of an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0014] 1. System Configuration FIG. 1 is a diagram showing an example of the configuration of a vehicle management system according to an embodiment. The vehicle management system 1 shown in FIG. 1 manages a vehicle 10 that is rented out from an owner to a user as a robot taxi. More specifically, the owner owns the vehicle 10, which is a personally owned vehicle (POV). The vehicle 10 is an autonomous vehicle capable of level 4 or higher autonomous driving as defined by the Society of Automotive Engineers (SAE) of the United States, and is configured to be able to operate as a robot taxi. Therefore, the owner can rent out the vehicle 10 to people as a robot taxi when he or she is not using the vehicle 10.

[0015] The vehicle management system (hereinafter, simply referred to as the “system”) 1 includes a vehicle 10, an owner's communication terminal (owner terminal) 30, a user terminal 40, and a vehicle management server 50.

[0016] The vehicle 10 includes a driving device 12, an electronic control unit (ECU) 14, a communication device 16, a vehicle state sensor 18, a recognition sensor 20, a GNSS (Global Navigation Satellite System) receiver 22, and an in-vehicle camera 24.

[0017] The traveling device 12 includes, for example, a driving device, a braking device, and a steering device as devices for accelerating, decelerating, and steering the vehicle 10. The ECU 14 is a computer that controls the vehicle 10. Specifically, the ECU 14 includes a processor 26 and a storage device 28. The processor 26 executes various processes. The various processes include processes related to automatic driving control of the vehicle 10. The storage device 28 stores various information. Examples of the storage device 28 include a volatile memory, a non-volatile memory, a hard disk drive (HDD), and a solid state drive (SSD). The ECU 14 (processor 26) executes various computer programs, thereby realizing various processes by the ECU 14. The various programs are stored in the storage device 28 or recorded in a computer-readable recording medium. Note that there may be a plurality of processors 26 and storage devices 28.

[0018] The communication device 16 communicates with each of the owner terminal 30, the user terminal 40, and the vehicle management server 50 via the communication network 2. The vehicle state sensor 18 detects the state of the vehicle 10. Examples of the vehicle state sensor 18 include a vehicle speed sensor, a steering angle sensor, a yaw rate sensor, and a lateral acceleration sensor. The recognition sensor 20 recognizes (detects) the situation around the vehicle 10. The recognition sensor 20 includes an exterior camera that captures images of the surroundings of the vehicle 10. The GNSS receiver 22 acquires the position and orientation of the vehicle 10 based on signals from GNSS satellites. The in-vehicle camera 24 captures images of the interior of the vehicle 10.

[0019] While the vehicle 10 configured as described above is operating as a robot taxi, it can automatically travel to a destination by autonomous driving control of level 4 or higher.

[0020] The owner terminal 30 is operated by the owner of the vehicle 10. The owner terminal 30 is, for example, a smartphone or a tablet personal computer. The owner terminal 30 includes a processor, a storage device, and a communication device. In addition, the owner terminal 30 can acquire location information of the owner who possesses the owner terminal 30 based on signals from GNSS satellites.

[0021] The user terminal 40 is operated by a user who rents the vehicle 10 from the owner. The user terminal 40 is, for example, a smartphone or a tablet personal computer. The user terminal 40 includes a processor, a storage device, and a communication device.

[0022] The vehicle management server (hereinafter, simply referred to as the "server") 50 is a computer that executes various processes in the system 1. The various processes include processes related to mediation of the rental and borrowing of the vehicle 10 between the owner and the user, and processes described below with reference to FIG. 2.

[0023] Specifically, the server 50 includes a communication device 52, a processor 54, and a storage device 56. The server 50 (communication device 52) is interposed between the owner terminal 30 and the user terminal 40 via the communication network 2, and communicates with the vehicle 10 via the communication network 2. The processor 54 executes the various processes described above. The storage device 56 stores various information. Examples of the storage device 56 include a volatile memory, a non-volatile memory, a hard disk drive (HDD), and a solid state drive (SSD). The processor 54 executes various computer programs to realize various processes by the processor 54. The various programs are stored in the storage device 56, or are recorded in a computer-readable recording medium. Note that there may be a plurality of processors 54 and storage devices 56.

[0024] 2. System Processing In the vehicle management system 1 of this embodiment, the owner can access the server 50 and manage the vehicle 10 by operating a specific application on the owner terminal 30. More specifically, when renting out the vehicle 10 (in other words, operating the vehicle 10 as a robot taxi), the owner can use the server 50 to accept reservations for the vehicle 10 from users who are registered with the application. In this way, the owner and users can rent or borrow the vehicle 10 by using the application provided by the system 1.

[0025] When the vehicle 10, which is the POV, operates as a robot taxi, there is a concern that the privacy of users may be violated if the owner can obtain information about the vehicle without restrictions while it is in operation. On the other hand, if the owner cannot obtain any information, the owner cannot grasp the status of the vehicle 10 and may feel uneasy.

[0026] Therefore, in the vehicle management system 1, the following process is executed to satisfy the owner's request to check the status of the vehicle 10 being rented out while respecting the privacy of the robot taxi user.

[0027] Fig. 2 is a flowchart showing an example of processing executed in the vehicle management system 1 shown in Fig. 1. The processing of this flowchart is started when the owner operates the owner terminal 30 to access the server 50, and is repeatedly executed until the access is terminated.

[0028] 2-1. Server processing The processes of steps S100 to S112 are executed on the side of the server 50. In step S100, the server 50 (processor 54) determines whether the vehicle 10 is operating as a robot taxi.

[0029] Specifically, whether or not the vehicle is "in operation" is determined based on whether or not it is within a period from the departure time T1 to the drop-off time T2. The departure time T1 corresponds to the time when the vehicle 10 leaves the departure point P1 of the vehicle 10 when heading to a user. When the vehicle 10 is heading to a user who is renting the vehicle 10 for the first time, the departure point P1 is, for example, a parking lot at the owner's home or a rental warehouse for the vehicle 10. In addition, after lending the vehicle 10 to a certain user, the owner may make the vehicle 10 travel around in order to lend the vehicle 10 to another user who wishes to rent the vehicle 10. In such a case, when the vehicle 10 is reserved by the other user, the current position of the vehicle 10 when heading to the other user during the tour corresponds to the departure point P1. The drop-off time T2 corresponds to the time when the user gets off the vehicle 10 when the rental of the vehicle 10 to the user is completed.

[0030] Furthermore, the determination of whether or not the vehicle 10 is "in operation" may be performed as follows. That is, the server 50 may determine that the vehicle 10 is in operation, not from the above-mentioned starting point P1, but, for example, after the vehicle 10 has moved away from the above-mentioned starting point P1 by a first predetermined distance D1. The first predetermined distance D1 is a predetermined distance that specifies the surrounding area of ​​the starting point P1, and is, for example, 500 m. The first predetermined distance D1 may be a straight-line distance from the starting point P1, or may be a distance (travel distance) along the travel route of the vehicle 10 from the starting point P1.

[0031] Additionally, the period during which the vehicle 10 is traveling toward a user does not necessarily have to be included in the period of time that the vehicle 10 is "in operation."

[0032] If the vehicle 10 is operating as a robot taxi (step S100; Yes), the server 50 calculates the distance Dv from the owner's current location to the vehicle 10 in step S102, and transmits the distance Dv to the owner terminal 30 as "vehicle position information."

[0033] To calculate the distance Dv, the server 50 uses the current position of the owner transmitted from the owner terminal 30 (i.e., the current position of the owner terminal 30). To calculate the distance Dv, the server 50 uses the current position of the vehicle 10 transmitted from the vehicle 10. The current position of the vehicle 10 is acquired by the vehicle 10 using the GNSS receiver 22. In this way, the distance Dv calculated by the server 50 may be an accurate distance calculated using the current position of the vehicle 10 acquired using the GNSS receiver 22. Alternatively, the distance Dv may be calculated as a rough distance compared to the accurate distance calculated in this way, that is, an approximate distance, for example, on the order of 100 km or 10 km (for example, see FIG. 3(A) described later). Note that the distance Dv may be a straight-line distance from the current position of the owner to the vehicle 10, or a distance (travel distance) along the travel route of the vehicle 10 from the current position of the owner.

[0034] Also, in step S102, the server 50 may transmit, as "vehicle distance information", the area Av in which the vehicle 10 is currently located, to the owner terminal 30, instead of transmitting the distance Dv. The area Av is information indicating the approximate current location of the vehicle 10, and is, for example, an area specified by administrative district unit such as a "city", "town", or "village".

[0035] Next, in step S104, the server 50 prohibits the owner terminal 30 from accessing a camera mounted on the vehicle 10. The camera in question is at least one of the exterior camera included in the recognition sensor 20 and the interior camera 24.

[0036] Next, in step S106, the server 50 prohibits the owner from remotely controlling the vehicle 10. Specifically, the server 50 prohibits, for example, the owner from operating the owner terminal 30 to set a new destination for the vehicle 10.

[0037] On the other hand, if the vehicle 10 is not operating as a robot taxi (step S100; No), that is, if there is no or little need to consider the user's privacy, the server 50, in step S108, transmits to the owner terminal 30 the current position of the vehicle 10 (for example, see Figure 3(B) described below) that is more accurate than when the vehicle 10 is operating, as "vehicle position information."

[0038] Next, in step S110, the server 50 permits the owner terminal 30 to access the camera mounted on the vehicle 10. This enables the owner to operate the "camera" button (see FIG. 3(B)) displayed on the screen 32 of the owner terminal 30 to display an image from the camera on the screen 32.

[0039] Next, in step S112, the server 50 permits the owner to remotely control the vehicle 10. Specifically, the server 50 permits, for example, the owner to operate the owner terminal 30 to set a new destination for the vehicle 10. This allows the owner to instruct the vehicle 10 to automatically travel to the destination set by the owner himself / herself (i.e., to remotely control the vehicle 10).

[0040] The destination setting may be transmitted from the owner terminal 30 to the vehicle via the server 50 by the owner operating a "destination setting" button (see FIG. 3(B)) displayed on the screen 32 of the owner terminal 30. Alternatively, the destination setting may be transmitted directly from the owner terminal 30 to the vehicle 10. In addition, when the owner wishes to further lend the vehicle 10 to another user after the lending of the vehicle 10 to a certain user is completed, the vehicle 10 may be located in an inconvenient place for further lending (i.e., a new reservation for a robot taxi) depending on the drop-off location of the previous user. According to the process of step S112, in such a case, the owner can move the vehicle 10 to a place where further lending is promoted (for example, an urban area where the need for lending is high) by setting a destination. In addition, when the owner is out, the owner can call the vehicle 10 to the owner by setting a destination.

[0041] Alternatively, the permission of remote control in step S112 may be given by the owner operating the owner terminal 30 to instruct the vehicle 10 to end its business as a robot taxi. This instruction to end business may be sent directly from the owner terminal 30 to the vehicle 10, or may be sent to the vehicle via the server 50. After the vehicle 10 receives the instruction to end business, the vehicle 10 will no longer accept new reservations for the robot taxi, and will automatically drive back to the owner (more specifically, the owner's home parking lot or a rented warehouse).

[0042] 2-2. Processing of Owner Device The process of steps S200 to S204 is executed on the owner terminal 30 side. In step S200, the owner terminal 30 (processor) determines whether or not the vehicle 10 is operating as a robot taxi. Specifically, the owner terminal 30 receives, for example, the determination result of step S100 above from the server 50, and makes the determination of step S200 using the received determination result.

[0043] 3(A) and 3(B) are diagrams showing an example of the screen 32 of the owner terminal 30 shown in FIG. 1. The owner can receive information shown on the screen 32 shown in FIG. 3(A) and 3(B) from the server 50 by operating the owner terminal 30 to access the server 50. On the screen 32, for example, information showing the operation status of the robot taxi, information on the current position of the vehicle 10, and information showing the current position on a map are displayed. Of these three pieces of information, the second and third pieces of information correspond to the "vehicle position information" that the owner terminal 30 receives from the server 50. In addition, on the screen 32, for example, a "camera" button for accessing the camera of the vehicle 10 and a "destination setting" button for setting a destination are displayed.

[0044] The owner terminal 30 switches the display format of the "vehicle position information" on the screen 32 depending on the determination result in step S200, that is, depending on whether the vehicle 10 is operating as a robot taxi or not.

[0045] Specifically, when the vehicle 10 is operating as a robot taxi (step S200; Yes), in step S202, the owner terminal 30 displays "vehicle position information" on the screen 32 in the first display format. FIG. 3(A) shows an example of a screen display in this first display format. The screen 32 shown in FIG. 3(A) displays that the vehicle 10 is "operating" as a robot taxi. In addition, the screen 32 displays an approximate distance of "up to 100 km (within 100 km)", which is an example of the above-mentioned distance Dv received from the server 50, as information regarding the current position of the vehicle 10. Instead of the distance Dv, information indicating the area Av may be displayed on the screen. Furthermore, since the vehicle 10 is operating as a robot taxi, a message indicating that the current position cannot be displayed on the map (i.e., the accurate vehicle position information cannot be displayed) is displayed on the screen 32. In addition, when the vehicle 10 is operating as a robot taxi, the server 50 does not permit access to the camera and destination setting. For this reason, on the screen 32 shown in FIG. 3(A), the "Camera" and "Set Destination" buttons are grayed out and unavailable.

[0046] On the other hand, if the vehicle 10 is not operating as a robot taxi (step S200; No), in step S204, the owner terminal 30 displays "vehicle location information" on the screen 32 in the second display format. FIG. 3(B) shows an example of a screen display in this second display format. The screen 32 shown in FIG. 3(B) displays "waiting for reservation" as the operating status of the robot taxi. The screen 32 also displays information on the current location of the vehicle 10 on a map, together with information on the area Av (e.g., Susono City) as information on the current location of the vehicle 10. That is, accurate vehicle location information received from the server 50 is displayed on the screen 32.

[0047] As described above, the first display format, which is the display format during operation, displays approximate (in other words, rough) "vehicle position information," whereas the second display format, which is the display format during non-operation, displays "vehicle position information" accurate enough to identify the current position of vehicle 10.

[0048] 3.Effects As described above, according to this embodiment, when the vehicle 10 is operating as a robot taxi, the server 50 transmits the distance Dv from the owner's current location to the vehicle 10 as vehicle location information to the owner terminal 30. The distance Dv or the above-mentioned area Av is not accurate location information that can identify the current location of the vehicle 10, but is approximate location information. The owner terminal 30 then displays the approximate location information on the screen 32 (first display format). This configuration makes it possible to satisfy the owner's request to check the status of the vehicle 10 during rental (in other words, to reduce the owner's anxiety) while taking into consideration the privacy of the robot taxi user.

[0049] As already described, the server 50 may determine that the vehicle 10 is operating as a robot taxi after the vehicle 10 moves away from the starting point P1 of the vehicle 10 by the first predetermined distance D1 when the vehicle 10 is heading toward the user. This allows the vehicle position information transmitted to the owner terminal 30 (in other words, the vehicle position information displayed on the screen 32 of the owner terminal 30) to be limited to approximate position information during the period when the vehicle 10 is automatically traveling toward the user, thereby taking into consideration the privacy of the user. In addition, the restriction is lifted in an area within the first predetermined distance D1 from the starting point P1 (for example, around the owner's home), that is, in an area where the need to take into consideration the privacy of the user is low. This allows the owner to more reliably watch over the vehicle 10 in that area, compared to a case in which the restriction is not lifted.

[0050] Furthermore, according to this embodiment, when the vehicle 10 that has left the owner is operating as a robot taxi, the owner terminal 30 is prohibited from accessing the camera mounted on the vehicle 10, and when the vehicle is not operating, access to the camera is permitted. This allows the owner to more effectively monitor the vehicle 10 when there is no or little need to consider the user's privacy.

[0051] 4. Other examples of processing after passengers disembark The "vehicle location information" transmitted from the server 50 to the owner terminal 30 after the vehicle 10 ceases to operate as a robot taxi as a result of the user getting off the vehicle 10 may be restricted as follows: Figure 4 is a flowchart showing an example of processing executed in a vehicle management system according to a modified example of the embodiment.

[0052] In FIG. 4, when the vehicle 10 is no longer in operation in step S100, the server 50 determines in step S300 whether the vehicle 10 is located within a second predetermined distance D2 from the user's drop-off point P2. The second predetermined distance D2 is a predetermined distance that specifies the surrounding area of ​​the drop-off point P2, and is, for example, 500 m. The second predetermined distance D2 may be a straight-line distance from the drop-off point P2, or may be a distance (travel distance) along the travel route of the vehicle 10 from the drop-off point P2. In addition, the second predetermined distance D2 may be the same as or different from the above-mentioned first predetermined distance D1.

[0053] In step S300, if the vehicle 10 is located within the second predetermined distance D2 from the drop-off point P2, that is, until the vehicle 10 is away from the user's drop-off point P2 by the second predetermined distance D2, the process proceeds to step S102. On the other hand, if the vehicle 10 is away from the drop-off point P2 by the second predetermined distance D2 or more in step S300, the process proceeds to step S108.

[0054] As in the process shown in Fig. 4, the server 50 may prohibit vehicle position information that is more accurate than that during operation from being transmitted to the owner terminal 30 until the vehicle 10 has moved a second predetermined distance D2 away from the user's drop-off point P2. Also, according to the process shown in Fig. 4, the server 50 prohibits the owner terminal 30 from accessing the vehicle's camera and also prohibits remote control of the vehicle 10 by operating the owner terminal 30 until the vehicle 10 has moved a second predetermined distance D2 away from the user's drop-off point P2.

[0055] 4, when the vehicle 10 is no longer in operation in step S200, the owner terminal 30 determines in step S400 whether the vehicle 10 is located within a second predetermined distance D2 from the user's drop-off point P2. Specifically, the owner terminal 30 receives, for example, the determination result of step S300 from the server 50, and makes the determination of step S400 using the received determination result.

[0056] If the vehicle 10 is located within the second predetermined distance D2 from the drop-off point P2 in step S400, that is, until the vehicle 10 moves away from the user's drop-off point P2 by the second predetermined distance D2, the process proceeds to step S202. On the other hand, if the vehicle 10 moves away from the drop-off point P2 by the second predetermined distance D2 or more in step S400, the process proceeds to step S204. According to this process, even after the vehicle 10 is no longer operating as a robot taxi, until the vehicle 10 moves away from the user's drop-off point P2 by the second predetermined distance D2, the display of vehicle position information (i.e., position information in the second display format) that is more accurate than when the vehicle 10 is in operation is prohibited on the screen 32.

[0057] According to the process shown in FIG. 4 described above, by taking into consideration the period from when the user gets off the vehicle 10 until the vehicle 10 leaves the vicinity of the user's drop-off point P2, it is possible to satisfy the owner's request to check the status of the vehicle 10 during rental while giving greater consideration to the privacy of the robot taxi user. [Explanation of symbols]

[0058] 1 vehicle management system, 2 communication network, 10 vehicle, 12 running gear, 14 electronic control unit (ECU), 20 recognition sensor (including exterior camera), 24 in-vehicle camera, 30 owner terminal, 32 owner terminal screen, 40 user terminal, 50 vehicle management server

Claims

1. A vehicle management server that manages vehicles rented out as robot taxis by owners to users, The vehicle management server transmits vehicle position information to the owner's communication terminal when the vehicle is operating as the robot taxi; The vehicle location information is a distance from the owner's current location to the vehicle or an area in which the vehicle is currently located, The vehicle management server determines that the vehicle is in operation after the vehicle moves a first predetermined distance away from a starting point of the vehicle as the vehicle travels to the user. Fleet management server.

2. A vehicle management server that manages vehicles rented out as robot taxis from owners to users, The vehicle management server transmits vehicle position information to the owner's communication terminal when the vehicle is operating as the robot taxi; The vehicle location information is a distance from the owner's current location to the vehicle or an area in which the vehicle is currently located, The vehicle management server prohibits transmission of vehicle position information, which is more accurate than the vehicle position information during operation, to the communication terminal until the vehicle moves away from the point where the user gets off the vehicle by a second predetermined distance after the vehicle is no longer in operation as a result of the user getting off the vehicle. Fleet management server.

3. A vehicle management server that manages vehicles rented out as robot taxis by owners to users, The vehicle management server transmits vehicle position information to the owner's communication terminal when the vehicle is operating as the robot taxi; The vehicle location information is a distance from the owner's current location to the vehicle or an area in which the vehicle is currently located, The vehicle management server prohibits the communication terminal from accessing the camera mounted on the vehicle when the vehicle is in operation, and permits the communication terminal from accessing the camera when the vehicle is not in operation. Fleet management server.

Images