In-vehicle monitoring system

Abstract

This system provides an in-vehicle monitoring system that protects the privacy of vehicle occupants while displaying camera images on a screen when an event requiring high visibility occurs. [Solution] The system includes an in-vehicle camera that takes pictures inside the vehicle, a vehicle-side display 50, a vehicle capable of automatic driving control, and a determination unit that determines whether or not an event has occurred in the vehicle. When the determination unit determines that an event has occurred, the vehicle-side display displays the camera image 64 acquired by the in-vehicle camera.

Description

Technical Field

[0001] The present invention relates to an in-vehicle monitoring system.

Background Art

[0002] The following Patent Document 1 discloses a vehicle provided with a display capable of displaying an in-vehicle camera image acquired by an in-vehicle camera.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Although it is possible to make an invention such as that of Patent Document 1 an invention in which the acquired in-vehicle camera image is always displayed on the display, it may not be preferable to always display it.

[0005] In consideration of the above facts, an object of the present invention is to obtain an in-vehicle monitoring system that can display a camera image representing an event on a display when an event with a high necessity of display occurs while protecting the privacy of vehicle occupants.

Means for Solving the Problems

[0006] An in-vehicle monitoring system according to a first aspect of the present invention includes an in-vehicle camera that photographs the interior of the vehicle, a vehicle capable of automatic driving control having a vehicle-side display, and a determination unit that determines whether or not an event has occurred in the vehicle. When the determination unit determines that the event has occurred, the vehicle-side display displays a camera image acquired by the in-vehicle camera.

[0007] In the in-vehicle monitoring system according to the second aspect of the present invention, the camera image is displayed on a display connected to a control device that can communicate wirelessly with the vehicle, in addition to the in-vehicle monitoring system according to the first aspect of the present invention.

[0008] A third aspect of the in-vehicle monitoring system of the present invention is an in-vehicle monitoring system of the first or second aspect of the present invention, wherein when the camera image is not displayed on the vehicle-side display, characters indicating that the in-vehicle camera is operating are displayed on the vehicle-side display.

[0009] A fourth aspect of the present invention is an in-vehicle monitoring system in which, in any of the first to third aspects of the present invention, the specially processed camera image is displayed on the vehicle-side display.

[0010] A fifth aspect of the present invention is an in-vehicle monitoring system in which, in any of the first to fourth aspects of the present invention, the same camera image is simultaneously displayed on a display connected to a control device that can communicate wirelessly with the vehicle and on the vehicle-side display.

[0011] A sixth aspect of the present invention is an in-vehicle monitoring system in which, in any of the first to fifth aspects of the present invention, a plurality of in-vehicle cameras are provided in the vehicle, and the vehicle-side display displays a plurality of camera images acquired by each of the in-vehicle cameras, switching between them. [Effects of the Invention]

[0012] The in-vehicle monitoring system of the first aspect of the present invention displays a camera image acquired by an in-vehicle camera on the vehicle's display when the determination unit determines that an event has occurred inside a vehicle capable of autonomous driving control. Events that occur inside a vehicle capable of autonomous driving control are events that have a high need to be displayed on the vehicle's display. Therefore, the in-vehicle monitoring system of the first aspect can display a camera image representing an event on the vehicle's display when an event that has a high need to be displayed occurs.

[0013] In the in-vehicle monitoring system of the first aspect of the present invention, if the determination unit does not determine that an event has occurred, the camera image acquired by the in-vehicle camera is not displayed on the vehicle's display. Therefore, compared to a system where the camera image is always displayed on the vehicle's display regardless of whether an event has occurred, it is easier to protect the privacy of the vehicle's occupants.

[0014] In the second aspect of the present invention, the administrator of the control device for the in-vehicle monitoring system can recognize the conditions inside the vehicle.

[0015] In the third aspect of the present invention, when the camera image is not displayed on the vehicle's display, text indicating that the in-vehicle camera is operating is displayed on the vehicle's display. Therefore, an anti-theft effect can be expected in the interior of vehicles capable of autonomous driving control.

[0016] In the in-vehicle monitoring system according to the fourth aspect of the present invention, specially processed camera images are displayed on the vehicle's display, making it easier to protect the privacy of the occupants.

[0017] In the in-vehicle monitoring system according to the fifth aspect of the present invention, the same camera image is simultaneously displayed on a display connected to a control device that can communicate wirelessly with the vehicle and on a vehicle-side display. This allows the administrator of the control device to recognize events occurring inside the vehicle.

[0018] In the in-vehicle monitoring system according to the sixth aspect of the present invention, camera images acquired by various in-vehicle cameras are displayed on the vehicle's display, thereby improving the security effect inside a vehicle capable of autonomous driving control. [Brief explanation of the drawing]

[0019] [Figure 1] This diagram shows the overall configuration of the in-vehicle monitoring system according to the embodiment. [Figure 2] This is a control block diagram of the control device for a remote monitoring system. [Figure 3]It is a functional block diagram of a control device. [Figure 4] It is a diagram showing the display of a remote monitoring device. [Figure 5] It is a diagram showing the event notification section of the display. [Figure 6] It is a control block diagram of an external server of a remote monitoring device. [Figure 7] It is a functional block diagram of an external server. [Figure 8] It is a control block diagram of an ECU of a bus. [Figure 9] It is a plan view of a bus. <% [Figure 10] It is a functional block diagram of an ECU. [Figure 11] It is a diagram showing the vehicle-side display of a bus. [Figure 12] It is a diagram showing a vehicle-side display displaying an event image different from that in FIG. 11. [Figure 13] It is a diagram showing a vehicle-side display displaying an event image different from that in FIGS. 10 and 11. [Figure 14] It is a diagram showing a vehicle-side display displaying an event image different from that in FIGS. 10 to 12. [Figure 15] It is a diagram showing the vehicle-side display when the bus has not received the first event notification information and the second event notification information. [Figure 16] It is a flowchart showing the processing executed by an external server of a remote monitoring device. [Figure 17] It is a flowchart showing the processing executed by a control device of a remote monitoring device. [Figure 18] It is a flowchart showing the processing executed by an ECU of a bus. [Figure 19] It is a diagram showing a vehicle-side display displaying an event image of a modified example.

Embodiments for Carrying Out the Invention

[0020] Hereinafter, embodiments of the in-vehicle monitoring system according to the present invention will be described with reference to the drawings.

[0021] As shown in Figure 1, the in-vehicle monitoring system 10 of the embodiment (hereinafter referred to as system 10) includes a remote monitoring device 20 and a plurality of buses (vehicles) 40A, 40B, and 40C.

[0022] The remote monitoring device 20 shown in Figure 1 is installed in a building (not shown) owned by the administrator of system 10. The remote monitoring device 20 comprises a control device 21, a display 24, an input device 27, an audio input / output device 28, and an external server 29.

[0023] As shown in Figure 2, the control device 21 has a hardware configuration that includes a CPU (Central Processing Unit) (processor) 21A, ROM (Read Only Memory) 21B, RAM (Random Access Memory) 21C, storage 21D, wireless communication interface 21E, and input / output interface 21G. The CPU 21A, ROM 21B, RAM 21C, storage 21D, wireless communication interface 21E, and input / output interface 21G are connected to each other so as to be able to communicate with one another via the internal bus 21Z. The CPU 21A and the CPUs 29A and 41A, which will be described later, can acquire time-related information from the timer.

[0024] The CPU 21A is the central processing unit, which executes various programs and controls various components. The CPU 21A reads programs from ROM 21B or storage 21D and executes them using RAM 21C as the working area. The CPU 21A controls each component and performs various calculations according to the programs recorded in ROM 21B or storage 21D.

[0025] ROM21B stores various programs and data. For example, multiple programs are installed in ROM21B. ROM21B also records information related to the vehicle ID. RAM21C temporarily stores programs or data as a working area. Storage21D consists of a storage device such as an HDD (Hard Disk Drive) or SSD (Solid State Drive) and stores various programs and data.

[0026] The wireless communication interface (I / F21E) is an interface for wireless communication with various devices. For example, the wireless communication interface (I / F21E) can communicate wirelessly with the wireless communication interface (I / F41E) on buses 40A, 40B, and 40C via a network (e.g., the Internet). The wireless communication interface (I / F21E) can transmit and receive, for example, audio data, camera image data, and sensor group detection values, as described later.

[0027] The input / output interface 21G is an interface for communicating with various devices. For example, the input / output interface 21G is connected to a display 24, an input device 27, an audio input / output device 28, and an external server 29. The display 24 can display various images. For example, the display 24 can display camera images and sensor group detection values ​​received by the wireless communication interface 21E from the wireless communication interface 41E on buses 40A, 40B, and 40C, as well as second event notification information, which will be described later, received from the external server 29. The input device 27 can input various information to the control device 21. The input device 27 is, for example, a keyboard. The audio input / output device 28 is equipped with a microphone and a speaker.

[0028] Figure 3 shows a block diagram illustrating an example of the functional configuration of the control device 21. The control device 21 has a functional configuration consisting of a transmit / receive control unit 211, a SIP control unit 212, a display control unit 213, a determination unit 214, and a server control unit 215. These functions are realized by the CPU 21A reading and executing a program stored in the ROM 21B.

[0029] The transmit / receive control unit 211 controls the wireless communication interface 21E. The wireless communication interface 21E controlled by the transmit / receive control unit 211 can, for example, receive camera image data from buses 40A, 40B, and 40C, wirelessly transmit the first event notification information and the second event notification information (described later) to buses 40A, 40B, and 40C, and record the received data in the ROM 21B and storage 21D. Furthermore, when a call using SIP (described later) is being performed, the wireless communication interface 21E can wirelessly transmit audio data input to the audio input / output device 28 and receive audio data transmitted from the wireless communication interface 41E on buses 40A, 40B, and 40C.

[0030] The SIP control unit 212 controls communication between the voice input / output device 28, which uses SIP (Session Initiation Protocol), and buses 40A, 40B, and 40C (speaker 44, microphone 45). In other words, the control unit 21 functions as a SIP server.

[0031] When a first call request is transmitted from the remote monitoring device 20 to the selected vehicle (wireless communication I / F 41E) by touch operation on the first call request operation units 34A2, 34B2, and 34C2 (described later), the SIP control unit 212 enables communication between the audio input / output device 28 and the speaker 44 and microphone 45 of the selected vehicle. That is, the audio input to the audio input / output device 28 is output from the speaker 44 of the selected vehicle, and the audio input to the microphone 45 of the selected vehicle is output from the audio input / output device 28. The selected vehicle is the bus corresponding to the first call request operation unit 34A2, 34B2, and 34C2 that was touched.

[0032] When the SIP control unit 212 receives a second call request from buses 40A, 40B, or 40C, it establishes a call between the bus 40A, 40B, or 40C that sent the second call request and the control device 21. Specifically, the audio input to the microphone 45 of bus 40A, 40B, or 40C that sent the second call request is output from the audio input / output device 28, and the audio information input to the audio input / output device 28 is output from the speaker 44.

[0033] The display control unit 213 controls the touch panel display 24.

[0034] Figure 4 shows a display 24 controlled by a display control unit 213. The display 24 shows camera image display areas 33A, 33B, and 33C. Furthermore, camera image display areas 33A, 33B, and 33C have a first display area 33A1, 33B1, 33C1, a second display area 33A2, 33B2, 33C2, a third display area 33A3, 33B3, 33C3, and a fourth display area 33A4, 33B4, 33C4. The first display areas 33A1, 33B1, and 33C1 display camera images acquired by multiple in-vehicle cameras 46 of buses 40A, 40B, and 40C in real time, switching between them. The second display areas 33A2, 33B2, and 33C2 display camera images acquired by multiple external front cameras 47F of buses 40A, 40B, and 40C in real time, switching between them. The third display areas 33A3, 33B3, and 33C3 display camera images acquired by multiple external rear cameras 47R on buses 40A, 40B, and 40C in real time, switching between them. The fourth display areas 33A4, 33B4, and 33C4 display camera images acquired by multiple external front cameras 47S on buses 40A, 40B, and 40C in real time, switching between them.

[0035] Furthermore, the display 24 shows the detected value display units 34A5, 34B5, and 34C4. The detected value display unit 34A5 corresponds to bus 40A, the detected value display unit 34B5 corresponds to bus 40B, and the detected value display unit 34C5 corresponds to bus 40C. The detected value display units 34A5, 34B5, and 34C4 display the sensor group detected values ​​received from buses 40A, 40B, and 40C in real time.

[0036] Furthermore, the display 24 shows the second call request reception display units 34A1, 34B1, 34C1, the first call request operation units 34A2, 34B2, 34C2, the call termination operation units 34A3, 34B3, 34C3, and the transmit processing buttons 34A4, 34B4, 34C4. The second call request reception display unit 34A1, the first call request operation unit 34A2, the call termination operation unit 34A3, and the transmit processing button 34A4 correspond to bus 40A. The second call request reception display unit 34B1, the first call request operation unit 34B2, the call termination operation unit 34B3, and the transmit processing button 34B correspond to bus 40B. The second call request reception display unit 34C1, the first call request operation unit 34C2, the call termination operation unit 34C3, and the transmit processing button 34C4 correspond to bus 40C.

[0037] The second call request reception indicators 34A1, 34B1, and 34C1 are equipped with illumination fixtures and blink when the wireless communication I / F21E receives a second call request from buses 40A, 40B, and 40C.

[0038] As described above, when a touch operation is performed on the first call request operation units 34A2, 34B2, and 34C2, and when a second call request is issued from buses 40A, 40B, and 40C, a call is established between the corresponding buses 40A, 40B, and 40C and the control device 21 (voice input / output device 28).

[0039] When a touch operation is performed on the call termination operation units 34A3, 34B3, or 34C3, the SIP control unit 212 controls the communication between the remote monitoring device 20 and buses 40A, 40B, and 40C, rendering it impossible to communicate between them.

[0040] When a touch operation is performed on the transmit processing buttons 34A4, 34B4, or 34C4, the wireless communication I / F 21E controlled by the transmit / receive control unit 211, as described later, wirelessly transmits the first event notification information, as described later, to the buses 40A, 40B, and 40C corresponding to the touched transmit processing buttons 34A4, 34B4, or 34C4.

[0041] Furthermore, as shown in Figure 4, an event notification unit 36 ​​is provided on the right side of the display 24. As will be described later, when the external server 29 determines that a second event has occurred and the second event notification information, as will be described later, is transmitted from the external server 29 to the control device 21, the event notification unit 36 ​​displays the second event notification information.

[0042] Furthermore, the administrator of the remote monitoring device 20 determines whether a first event has occurred in any of the buses 40A, 40B, or 40C based on at least one of the following: the content of the camera images displayed in the camera image display areas 33A, 33B, and 33C of the display 24; the sensor group detection values ​​displayed in the detection value display units 34A5, 34B5, and 34C4; and the content of the conversation using the audio input / output device 28 and the speakers 44 and microphones 45 of the buses 40A, 40B, and 40C. When it is determined that a first event has occurred, the administrator touches the transmission processing buttons 34A4, 34B4, and 34C4. At this time, the administrator of the remote monitoring device 20 uses the input device 27 to input camera ID information to the control device 21 to identify each of the in-vehicle cameras 46, each of the exterior front cameras 47F, each of the exterior rear cameras 47R, and each of the exterior side cameras 47S, which will be described later. As a result, the determination unit 214 generates first event notification information linked to the input camera ID information. Furthermore, when a touch operation is performed on the transmission processing buttons 34A4, 34B4, and 34C4, the wireless communication I / F 21E wirelessly transmits the first event notification information to buses 40A, 40B, and 40C, which represent the camera ID information. The determination unit 214 determines (recognizes) that a first event has occurred on buses 40A, 40B, and 40C when a touch operation is performed on the transmission processing buttons 34A4, 34B4, and 34C4.

[0043] The first event of this embodiment includes, for example, the following events A to C. Event A: Disputes between passengers on buses 40A, 40B, and 40C. Event B: Remote monitoring device 20 receives a second call request from buses 40A, 40B, and 40C (passengers). Event C: The administrator of the remote monitoring device 20 recognizes or anticipates a problem occurring inside buses 40A, 40B, and 40C based on camera images and sensor group detection values ​​displayed on the display 24.

[0044] Furthermore, when the event notification unit 36 ​​displays the second event notification information due to the control device 21 receiving the second event notification information from the external server 29, the determination unit 214 determines that the second event (event) described later has occurred on buses 40A, 40B, and 40C represented by the camera ID information included in the second event notification information. In addition, the wireless communication interface 21E controlled by the transmission / reception control unit 211 automatically wirelessly transmits this second event notification information to buses 40A, 40B, and 40C represented by the camera ID information.

[0045] The server control unit 215 controls the external server 29 based on instructions input to the control device 21 using the input device 27.

[0046] As shown in Figure 6, the external server 29 has a hardware configuration that includes a CPU 29A, ROM 29B, RAM 29C, storage 29D, wireless communication interface 29E, and input / output interface 29G. The CPU 29A, ROM 29B, RAM 29C, storage 29D, wireless communication interface 29E, and input / output interface 29G are interconnected via an internal bus 29Z. As shown in Figure 1, the external server 29 is connected to the control unit 21 by a cable.

[0047] Figure 7 shows an example of the functional configuration of the external server 29 in a block diagram. The external server 29 has a functional configuration consisting of a transmit / receive control unit 291, an event determination unit 292, and a data management unit 293. These functions are realized by the CPU 29A reading and executing a program stored in the ROM 29B.

[0048] The transmit / receive control unit 291 controls the wireless communication interface 29E. The wireless communication interface 29E, controlled by the transmit / receive control unit 291, repeatedly receives camera image data and sensor group detection values ​​from the in-vehicle camera 46, the exterior front camera 47F, the exterior rear camera 47R, and the exterior side camera 47S (described later) via wireless communication from buses 40A, 40B, and 40C at predetermined intervals. The camera image data and sensor group detection values ​​are linked to information regarding the date and time of acquisition and the location information of buses 40A, 40B, and 40C at the time of acquisition.

[0049] The event determination unit 292 determines whether a predetermined second event has occurred on buses 40A, 40B, and 40C based on the camera image data and sensor group detection values ​​received from buses 40A, 40B, and 40C and recorded in storage 29D. Specifically, the event determination unit 292 reads all camera image data and sensor group detection values ​​recorded in storage 29D and determines whether a second event has occurred on any of the buses 40A, 40B, and 40C. Furthermore, when the event determination unit 292 receives an emergency signal, described later, from buses 40A, 40B, and 40C, it determines that a second event has occurred on the bus that sent the emergency signal.

[0050] The event determination unit 292 may also determine whether or not a second event has occurred by using a learning model (machine learning) that determines the relationship between the camera image data and the sensor group detection values ​​and the second event.

[0051] The second event of this embodiment includes, for example, the following events D to H. Event D: Buses 40A, 40B, and 40C, which were performing autonomous driving control (Level 4 or 5 driver assistance control), suddenly terminated the autonomous driving control. Event E: Passenger congestion inside the vehicle exceeds a predetermined level. Event F: Collision Event G: Passenger's health deteriorates. Event H: Approach of buses 40A, 40B, and 40C to the bus stop

[0052] For example, even if the event determination unit 292 has not received a signal from any of the buses 40A, 40B, or 40C indicating that the start button (ignition switch) has switched from ON to OFF, if it suddenly stops receiving the automatic driving execution signal that it had been continuously receiving from buses 40A, 40B, or 40C, it determines that a problem has occurred in the driver assistance control function of bus 40A, 40B, or 40C, and determines that event D has occurred in bus 40A, 40B, or 40C.

[0053] The event determination unit 292 determines, for example, that an event E has occurred in bus 40A, 40B, or 40C if it determines, based on camera image data received from the in-vehicle camera 46 of any of the buses 40A, 40B, or 40C, that the population density in at least a portion of the area (space) inside the vehicle exceeds a predetermined threshold density.

[0054] The event determination unit 292 determines that event F has occurred on buses 40A, 40B, and 40C if, for example, the camera image data recorded in storage 29D includes another vehicle or obstacle that has collided with any of the buses 40A, 40B, and 40C. This other vehicle includes vehicles other than four-wheeled vehicles. That is, for example, other vehicles include motorcycles and bicycles. Obstacles include, for example, guardrails, road curbs, and buildings. The event determination unit 292 also determines that event F has occurred on any of the buses 40A, 40B, and 40C if an acceleration in a predetermined direction that would not normally occur during normal driving occurs in that bus.

[0055] The event determination unit 292 determines, for example, that event G has occurred in bus 40A, 40B, or 40C if it determines, based on camera image data received from the in-vehicle camera 46 of any of the buses 40A, 40B, or 40C, that at least one passenger inside the bus is unwell. For example, if, as a result of analyzing the camera image data, it is determined that the body temperature of a passenger included in the camera image data is above a predetermined value, the event determination unit 292 determines that event G has occurred.

[0056] The event determination unit 292 determines that event H has occurred when it determines that a bus 40A, 40B, or 40C is approaching a bus stop located on its route, based on, for example, the position signal, vehicle speed information received from any of the buses 40A, 40B, or 40C, and the route information of the buses 40A, 40B, or 40C recorded in the storage 29D. For example, the event determination unit 292 determines that event H has occurred when the distance between the buses 40A, 40B, or 40C and the bus stop becomes 50m or less.

[0057] When the system determines that a second event has occurred, the event determination unit 292 generates second event notification information. This second event notification information includes the camera ID information of the camera that captured the subject representing the second event, and the vehicle ID information of buses 40A, 40B, and 40C that transmitted the emergency signal or sensor group detection value. The generated second event notification information is automatically transmitted to the control device 21 by the transmission / reception control unit 291.

[0058] As a result, as shown in Figure 5, the event notification unit 36 ​​of the display 24 sequentially displays the second event notification information EV2 related to the second event that occurred. Although not shown in the figure, the event notification unit 36 ​​also displays information regarding the date and time each event occurred.

[0059] The data management unit 293 records various data in the ROM 29B or storage 29D, and deletes data recorded in storage 29D. For example, the data management unit 293 sequentially records camera image data and sensor group detection values ​​received by the transmission / reception control unit 291 in storage 29D. Furthermore, the data management unit 293 automatically deletes data recorded in storage 29D as needed. For example, the data management unit 293 automatically deletes camera image data and sensor group detection values ​​that were not determined to have occurred as a second event after a predetermined time has elapsed since they were recorded in storage 29D.

[0060] As shown in Figure 8, buses 40A, 40B, and 40C are equipped with an ECU 41, a GNSS (Global Navigation Satellite System) receiver 43, a speaker 44, a microphone 45, an in-vehicle camera 46, an out-of-vehicle front camera 47F, an out-of-vehicle rear camera 47R, an out-of-vehicle side camera 47S, a second call request operation unit 49S, a call termination operation unit 49F, a touch-panel vehicle-side display 50, a sensor group 51, a driver assistance operation unit 62, and an emergency button 63. As shown in Figure 8, the ECU 41 has the same hardware configuration as the control unit 21. That is, the ECU 41 has a hardware configuration of a CPU 41A, ROM 41B, RAM 41C, storage 41D, wireless communication I / F 41E, input / output I / F 41G, and an internal bus 41Z. For example, multiple programs are installed in ROM 41B.

[0061] The input / output interface 41G of the ECU 41 is connected to a GNSS receiver 43, a speaker 44, a microphone 45, an in-vehicle camera 46, an out-of-vehicle front camera 47F, an out-of-vehicle rear camera 47R, an out-of-vehicle side camera 47S, a second call request operation unit 49S, a call termination operation unit 49F, a vehicle-side display 50, a sensor group 51, a driver assistance operation unit 62, and an emergency button 63.

[0062] The GNSS receiver 43 receives GNSS signals transmitted from GNSS satellites and acquires position information for buses 40A, 40B, and 40C equipped with an ECU 41. The acquired position information is repeatedly transmitted wirelessly to the remote monitoring device 20 and the external server 29 via the wireless communication interface 41E at predetermined intervals.

[0063] Speaker 44 can output various sounds. For example, if communication is established between the remote monitoring device 20 and buses 40A, 40B, and 40C, speaker 44 can output audio data based on the audio input to the audio input / output device 28.

[0064] Various types of audio are input to microphone 45. For example, when audio is input to microphone 45 when communication is established between the remote monitoring device 20 and buses 40A, 40B, and 40C, this audio is output from the audio input / output device 28 of the remote monitoring device 20.

[0065] Multiple in-vehicle cameras 46 are installed inside the buses 40A, 40B, and 40C. In this embodiment, four in-vehicle cameras 46, spaced apart from each other in the front-to-back direction, are installed on the ceiling of the buses 40A, 40B, and 40C. Furthermore, each in-vehicle camera 46 is rotatable around an axis extending in the vertical direction. Therefore, each in-vehicle camera 46 can capture images of the front, back, left, and right areas within the area located below it. The in-vehicle cameras 46 repeatedly acquire image data representing subjects inside the buses 40A, 40B, and 40C at predetermined intervals.

[0066] As shown in Figure 9, the external forward cameras 47F are installed at the front ends of buses 40A, 40B, and 40C. In this embodiment, three external forward cameras 47F are installed side by side in the left-right direction at the front ends of buses 40A, 40B, and 40C. Each external forward camera 47F repeatedly acquires image data representing an external subject located in front of the front end of buses 40A, 40B, and 40C at predetermined intervals. Note that in Figure 9, arrow FR indicates the front of the vehicle, and arrow LH indicates the left side of the vehicle.

[0067] As shown in Figure 9, the external rear cameras 47R are installed at the rear ends of buses 40A, 40B, and 40C. In this embodiment, three external rear cameras 47R are installed side by side at the rear ends of buses 40A, 40B, and 40C. Each external rear camera 47R repeatedly acquires image data representing an external subject located behind the rear end of buses 40A, 40B, and 40C at predetermined intervals.

[0068] As shown in Figure 9, the exterior cameras 47S are installed on both the left and right sides of buses 40A, 40B, and 40C. In this embodiment, three exterior cameras 47S are installed in a row in the front-to-back direction on the left and right sides of buses 40A, 40B, and 40C. The left exterior camera 47S repeatedly acquires image data representing an external subject located to the left of buses 40A, 40B, and 40C at predetermined intervals. The right exterior camera 47S repeatedly acquires image data representing an external subject located to the right of buses 40A, 40B, and 40C at predetermined intervals.

[0069] The image data acquired by each in-vehicle camera 46, each exterior front camera 47F, each exterior rear camera 47R, and each exterior side camera 47S is tagged with camera ID information to identify each camera. Furthermore, the camera ID information includes vehicle ID information to identify the bus on which that camera is installed.

[0070] The second call request operation unit 49S and the call termination operation unit 49F are, for example, mechanical buttons installed inside the buses 40A, 40B, and 40C. However, the second call request operation unit 49S and the call termination operation unit 49F may also be images (operation images) displayed on the vehicle-side display 50.

[0071] The vehicle-side displays 50 are installed inside the buses 40A, 40B, and 40C. For example, the vehicle-side displays 50 are installed on the interior walls of the buses 40A, 40B, and 40C. There may be one or more vehicle-side displays 50.

[0072] Sensor group 51 is a collective term for the sensors installed on buses 40A, 40B, and 40C. These sensors include, for example, a vehicle speed sensor, an accelerator pedal sensor, a brake pedal sensor, a turn signal sensor, a LiDAR sensor, a radar sensor, air pressure sensors installed on the tires of each wheel, a steering angle sensor that detects the steering angle of the steering wheel, and an acceleration sensor that detects acceleration in various directions generated on the vehicle body. Each of these sensors repeatedly performs a detection operation after a predetermined time has elapsed. In this specification, the detection value acquired by each sensor included in sensor group 51 is referred to as the sensor group detection value.

[0073] The driver assistance control unit 62 is a switch located on the instrument panel of buses 40A, 40B, and 40C.

[0074] Emergency button 63 is a mechanical button located in multiple places inside buses 40A, 40B, and 40C.

[0075] Figure 10 shows an example of the functional configuration of the ECU 41 in a block diagram. The ECU 41 has a functional configuration consisting of a transmit / receive control unit 411, a call control unit 412, a display control unit 413, and a driver assistance control unit 414. These functions are realized by the CPU 41A reading and executing a program stored in the ROM 41B.

[0076] The transmit / receive control unit 411 controls the wireless communication interface 41E. The wireless communication interface 41E controlled by the transmit / receive control unit 411 can communicate wirelessly with the wireless communication interface 21E of the remote monitoring device 20 and the wireless communication interface 29E of the external server 29 via the network. For example, by controlling the wireless communication interface 41E, the transmit / receive control unit 411 wirelessly transmits image data, location information, and sensor group detection values ​​from the in-vehicle camera 46, the out-of-vehicle front camera 47F, the out-of-vehicle rear camera 47R, and the out-of-vehicle side camera 47S to the remote monitoring device 20 and the external server 29 at predetermined intervals, while linking them with the bus ID information and camera ID information. Furthermore, the wireless communication interface 41E receives the first event notification information and the second event notification information wirelessly transmitted by the wireless communication interface 21E.

[0077] Furthermore, when the driver assistance operation unit 62 is turned ON and buses 40A, 40B, and 40C are performing Level 4 or Level 5 driver assistance control (automatic driving control) as described later, the transmission / reception control unit 411 repeatedly transmits an automatic driving execution signal wirelessly to the remote monitoring device 20 and the external server 29 at predetermined intervals.

[0078] Furthermore, when the emergency button 63 is operated by a crew member, the transmission / reception control unit 411 wirelessly transmits an emergency signal to the external server 29, linking it with the vehicle ID information of buses 40A, 40B, and 40C.

[0079] The call control unit 412 controls the speaker 44 and microphone 45. For example, when the wireless communication interface 41E receives a first call request from the remote monitoring device 20, the call control unit 412 enables the functions of the speaker 44 and microphone 45.

[0080] Furthermore, when the second call request operation unit 49S is operated by a crew member, the call control unit 412 causes the wireless communication I / F 41E to wirelessly transmit the second call request to the remote monitoring device 20.

[0081] Furthermore, the call control unit 412 terminates the call between the buses 40A, 40B, and 40C and the remote monitoring device 20 when the call termination operation unit 49F is operated by a crew member.

[0082] When the wireless communication interface 21E of the control device 21 transmits at least one of the first event notification information and the second event notification information to buses 40A, 40B, and 40C, the display control unit 413 displays this information and the associated camera image on the vehicle-side display 50 in real time for a predetermined period of time.

[0083] For example, let's assume that the administrator of the remote monitoring device 20 determines that a dispute has occurred between passengers inside the bus 40A while viewing an image of the interior of the bus displayed in the camera image display area 33A of the display 24. This dispute may include criminal activity. In other words, let's assume that event A occurs inside the bus 40A. In this case, the administrator uses the input device 27 to input the camera ID information of the in-vehicle camera 46 that captured the dispute into the control device 21, and also touches the transmission processing button 34A4. As a result, the first event notification information linked to this camera ID information is received by the wireless communication I / F 41E of the bus 40A. Therefore, as shown in Figure 11, the camera image 64 captured by the in-vehicle camera 46 represented by this camera ID information is displayed in real time across the entire vehicle-side display 50.

[0084] Furthermore, as shown in Figure 11, when an event occurs, the camera image 64 representing a person (e.g., a passenger) displayed on the vehicle-side display 50 is subjected to special processing. That is, the display control unit 413 applies special image processing to the camera image. In this specification, special processing refers to processing that makes it more difficult for a third party to identify the person being processed compared to when no special processing is applied. For example, special processing includes mosaic processing applied to a person's face, mask processing applied to a person's face, silhouette processing applied to a person, blurring applied to a person, processing that renders only the skeletal information and joint point information of a person, processing that displays only the outline of a person, processing that converts a camera image of a person into an illustration, and AR (Augmented Reality) rendering (processing that superimposes a digital image on an image of a person). In the examples in Figure 11 and Figures 12 to 14 described later, special processing that displays only the outline of a person is applied to the camera image. In this way, the privacy of passengers on buses 40A, 40B, and 40C is appropriately protected.

[0085] Furthermore, consider a scenario where, for example, event H occurs when bus 40B approaches a designated bus stop, and a second event notification information linked to the camera ID information of one in-vehicle camera 46 and the camera ID information of one external front camera 47F is transmitted from the control device 21 to bus 40B. In this case, as shown in Figure 12, the display control unit 413 divides the vehicle-side display 50 into two areas 53-1 and 53-2. In addition, a camera image 66 taken by the in-vehicle camera 46 represented by the camera ID information is displayed in real time in one area 53-1, and a camera image 67 taken by the external front camera 47F represented by the camera ID information is displayed in real time in the other area 53-2. The camera image 66 includes multiple passengers PS1 near and around the bus 40B's exit 40B1. The camera image 67 includes the bus stop BS and multiple passengers PS2 who are scheduled to board.

[0086] Furthermore, based on the camera image data acquired by the three in-vehicle cameras 46, we assume that event E occurs in bus 40C when the population density in each of the three areas inside bus 40C exceeds the threshold density. In this case, the control device 21 sends a second event notification information linked to the camera ID information of the three in-vehicle cameras 46 to bus 40C. In this case, as shown in Figure 13, the vehicle-side display 50 is divided into three areas 53-1, 53-2, and 53-3. Area 53-1 displays the camera image 70 taken by the in-vehicle camera 46 located furthest forward in real time, area 53-2 displays the camera image 71 taken by the in-vehicle camera 46 located immediately behind this camera in real time, and area 53-3 displays the camera image 72 taken by the in-vehicle camera 46 located furthest rear in real time. Camera images 70, 71, and 72 each contain multiple passengers PS.

[0087] Furthermore, we assume a scenario where the emergency button 63 on bus 40A is operated, causing the external server 29 to receive an emergency signal from bus 40A, and the event determination unit 292 determines that a second event has occurred on bus 40A. In this case, the control device 21 sends second event notification information, which is associated with the four camera IDs, to bus 40A. In this case, as shown in Figure 14, the vehicle-side display 50 is divided into four areas 53-1, 53-2, 53-3, and 53-4. Area 53-1 displays the camera image 80 taken by the frontmost in-vehicle camera 46 in real time, area 53-2 displays the camera image 81 taken by the in-vehicle camera 46 located immediately behind this in-vehicle camera 46 in real time, area 53-3 displays the camera image 82 taken by the in-vehicle camera 46 located immediately behind this in-vehicle camera 46 in real time, and area 53-4 displays the camera image 83 taken by the rearmost in-vehicle camera 46 in real time.

[0088] Although not shown in the diagram, if event B or event C occurs in any of the buses 40A, 40B, or 40C, the administrator of the remote monitoring device 20 inputs the camera ID information of at least one in-vehicle camera 46 to the control device 21 while viewing the camera image display areas 33A, 33B, and 33C on the display 24. In this case, the camera image captured by the in-vehicle camera 46 corresponding to this camera ID information is displayed in real time on the vehicle-side display 50.

[0089] Although not shown in the diagram, if event D occurs in any of the buses 40A, 40B, or 40C, the display control unit 413 controls the vehicle-side display 50 to display the camera images of each in-vehicle camera 46, each external front camera 47F, each external rear camera 47R, and each external side camera 47S in a switching manner. In this case, the vehicle-side display 50 may be divided into multiple areas, and these camera images may be displayed in each area in a switching manner.

[0090] Although not shown in the diagram, if event F or event G occurs in any of the buses 40A, 40B, or 40C, the display control unit 413 controls the vehicle-side display 50 to display the camera image of the camera capturing the event.

[0091] Furthermore, when the display control unit 413 has not received the first event notification information and the second event notification information from the control device 21, it causes the words "Security camera in operation" and "Remote monitoring in progress" to be displayed on the vehicle-side display 50, as shown in Figure 15.

[0092] When the driver assistance control unit 62, provided on buses 40A, 40B, and 40C, is turned ON, the driver assistance control unit 414 performs driver assistance control using data acquired by the GNSS receiver 43, the external front camera 47F, the external rear camera 47R, and the sensor group 51. This driver assistance control is performed by operating various devices on buses 40A, 40B, and 40C, including the brake system, engine, electric motor, steering system (not shown), and turn signals. In this specification, "driver assistance control" includes driver assistance control levels 1 to 5 as defined by the SAE (Society of Automotive Engineers). When a predetermined operation is performed on the driver assistance control unit 62, the driver assistance control unit 414 determines (selects) the level of driver assistance control to be performed from levels 1 to 5.

[0093] (Mechanism of action and effect) Next, the operation and effects of this embodiment will be described.

[0094] First, the processing flow performed by the CPU 29A of the external server 29 in this embodiment will be explained using the flowchart in Figure 16. The CPU 29A repeatedly executes the processing shown in the flowchart in Figure 16 after a predetermined amount of time has elapsed.

[0095] First, in step S10 (hereinafter the word "step" will be omitted), the CPU 29A determines whether or not it has received at least one of the following from buses 40A, 40B, and 40C: camera image data, sensor group detection value, and emergency signal.

[0096] CPU29A, which determined Yes in S10, proceeds to S11, where it determines whether a second event occurred on any of the buses 40A, 40B, or 40C.

[0097] If CPU 29A determines "Yes" in S11, it proceeds to S12 and sends second event notification information to control device 21.

[0098] When the process in S12 is completed, or when the result in S10 or S11 is determined to be No, the CPU 29A temporarily terminates the process shown in the flowchart in Figure 16.

[0099] Next, we will explain the process performed by the CPU 21A of the control device 21 using the flowchart in Figure 17. The CPU 21A repeatedly executes the process shown in the flowchart in Figure 17 at predetermined intervals.

[0100] First, in S20, the CPU 21A determines whether or not it has received camera image data and sensor group detection values ​​from buses 40A, 40B, and 40C.

[0101] If CPU 21A determines "Yes" in S20, it proceeds to S21 and displays the camera image data and sensor group detection values ​​on display 24.

[0102] When the processing of S21 is completed, CPU21A proceeds to S22 and determines whether or not it has received second event notification information from the external server 29.

[0103] If CPU 21A determines "Yes" in S22, it proceeds to S23, displays the second event notification information on display 24, and wirelessly transmits the second event notification information to at least one bus 40A, 40B, or 40C.

[0104] When the processing in S23 is completed, the CPU 21A proceeds to S24 and determines whether or not there has been input processing of camera ID information using the input device 27.

[0105] If CPU 21A determines "Yes" in S24, it proceeds to S25 to determine whether or not there was a touch operation on the transmit buttons 34A4, 34B4, and 34C4.

[0106] CPU21A, which determined Yes in S25, proceeds to S26 and wirelessly transmits the first event notification information to buses 40A, 40B, and 40C, linked to the camera ID information.

[0107] When the process in S26 is completed, or when the result in S20, 22, 24, or 25 is determined to be "No", the CPU 21A temporarily terminates the process in the flowchart shown in Figure 17.

[0108] Next, we will explain the processes performed by CPU 41A on buses 40A, 40B, and 40C using the flowchart in Figure 18. CPU 41A repeatedly executes the processes shown in the flowchart in Figure 18 at predetermined intervals.

[0109] First, in S30, the CPU 41A determines whether or not it has received at least one of the first event notification information and the second event notification information from the control device 21.

[0110] If CPU 41A determines "Yes" in S30, it proceeds to S31 and displays the camera image associated with at least one of the received first event notification information and second event notification information on the vehicle-side display 50 in real time.

[0111] When the process in S31 is completed, or when the result in S30 is determined to be No, the CPU 41A temporarily terminates the process shown in the flowchart in Figure 18.

[0112] As described above, in the system 10 of the embodiment, when the control device 21 (determination unit 214) determines that an event (first event, second event) has occurred inside a bus 40A, 40B, or 40C capable of performing automated driving control (level 4 or 5 driver assistance control), the camera image acquired by the in-vehicle camera 46 is displayed on the vehicle-side display 50. There is a possibility that there is no driver inside the bus 40A, 40B, or 40C capable of automated driving control. Therefore, events that occur inside the bus 40A, 40B, or 40C capable of automated driving control are events that have a high need to be displayed on the vehicle-side display 50. In other words, if passengers are not notified at all about an event that occurred inside a vehicle without a driver, they are likely to become anxious. Therefore, when an event occurs that has a high need to be displayed on the vehicle-side display 50, the system 10 displays the camera image representing the event on the vehicle-side display 50. As a result, passengers are less likely to become anxious compared to when the camera image is not displayed on the vehicle-side display 50.

[0113] For example, when event A (a dispute between passengers) occurs inside bus 40A, if the camera image shown in Figure 11 is displayed on the vehicle-side display 50, the parties involved in the dispute who see the vehicle-side display 50 are more likely to feel psychological pressure, realizing that they are being monitored by other passengers and the administrator of the remote monitoring device 20. As a result, the passengers involved are more likely to be inclined to resolve the dispute on their own. Therefore, displaying such camera images on the vehicle-side display 50 can provide a security benefit.

[0114] Furthermore, when event H occurs, indicating that bus 40B is approaching a designated bus stop, if the camera image shown in Figure 12 is displayed on the vehicle-side display 50, passenger PS1 near the exit 40B1, who is looking at area 53-1 of the vehicle-side display 50, is more likely to intend to move away from the exit 40B1 to another location for the sake of other passengers moving to the exit 40B1 to disembark. Therefore, displaying such a camera image on the vehicle-side display 50 makes it easier to achieve smooth disembarkation by passengers. In addition, it is less likely that troubles will occur between passengers who are about to disembark and passengers near the exit 40B1, thus providing a crime prevention effect. Moreover, it becomes less likely that one of the passengers who is about to disembark or one of the passengers near the exit 40B1 will be subjected to crimes such as pickpocketing by other passengers. Furthermore, when the camera image shown in Figure 12 is displayed on the vehicle-side display 50, passengers near the boarding entrance (not shown), who are looking at area 53-2 of the vehicle-side display 50, can recognize the number of passengers PS2 who are about to board bus 40B. In other words, these passengers are more likely to move to other locations within the vehicle for the sake of the passenger PS2 who is scheduled to board. Therefore, displaying such camera images on the vehicle's display 50 makes it easier to facilitate the smooth boarding process for the passenger PS2. Furthermore, it reduces the likelihood of disputes between the passenger PS2 and passengers near the entrance, thus providing a security benefit.

[0115] Furthermore, let's consider the case where, when event E occurs in each of the three areas inside the bus 40C, the camera image shown in Figure 13 is displayed on the vehicle-side display 50. Generally, it is said that crimes such as pickpocketing are more likely to occur in areas inside the vehicle where event E (crowding) occurs compared to areas where crowding does not occur. However, when the camera image shown in Figure 13 is displayed on the vehicle-side display 50, a person who is considering committing a crime in this crowded area is likely to feel psychological pressure, knowing that they are being monitored by other passengers and the administrator of the remote monitoring device 20. Therefore, this person is more likely to abandon their plan to commit a crime. Thus, it is possible to achieve a crime prevention effect by displaying such a camera image on the vehicle-side display 50.

[0116] Furthermore, consider the scenario where a passenger on bus 40A operates the emergency button 63, causing bus 40A to send an emergency signal to the external server 29, resulting in the camera image shown in Figure 14 being displayed on the vehicle's display 50. In this case, the passenger may be involved in some kind of trouble. However, when the camera image shown in Figure 14 is displayed on the vehicle's display 50 in this situation, the person involved in the trouble is likely to feel psychological pressure, realizing they are being monitored by other passengers and the administrator of the remote monitoring device 20. Therefore, the passenger who operates the emergency button 63 in such a case is likely to be released from the trouble early.

[0117] Furthermore, in system 10, if the control device 21 does not determine that an event has occurred, the camera image acquired by the in-vehicle camera 46 is not displayed on the vehicle-side display 50. Therefore, compared to a system where the camera image is always displayed on the vehicle-side display 50 regardless of whether an event has occurred, system 10 makes it easier to protect the privacy of passengers on buses 40A, 40B, and 40C.

[0118] Furthermore, in system 10, the camera image from the in-vehicle camera 46 is displayed on a display 24 connected to a control device 21 that can wirelessly communicate with buses 40A, 40B, and 40C. Therefore, the administrator of the remote monitoring device 20 can always be aware of the situation inside buses 40A, 40B, and 40C through the display 24. In addition, when buses 40A, 40B, and 40C have not received the first event notification information and the second event notification information from the control device 21, the words "Remote Monitoring in Progress" are displayed on the vehicle-side display 50, as shown in Figure 15. In other words, passengers can be aware that the situation inside the vehicle is being remotely monitored. Therefore, passengers inside buses 40A, 40B, and 40C when the driver is absent are less likely to feel anxious.

[0119] Furthermore, in system 10, when the camera image is not displayed on the vehicle-side display 50, the words "Security camera in operation" are displayed on the vehicle-side display 50. Therefore, an enhanced security effect can be expected inside buses 40A, 40B, and 40C, which are capable of autonomous driving control.

[0120] Furthermore, buses 40A, 40B, and 40C are equipped with multiple in-vehicle cameras 46, and the vehicle-side displays 50 of buses 40A, 40B, and 40C that receive at least one of the first event notification information and the second event notification information can switch between and display multiple camera images acquired by each in-vehicle camera 46. In this way, camera images acquired by various in-vehicle cameras 46 are displayed on the vehicle-side displays 50, making it less likely for blind spots to occur inside the vehicle for all in-vehicle cameras 46. As a result, the security effect inside buses 40A, 40B, and 40C is improved.

[0121] Although the system 10 according to the embodiment has been described above, these can be modified as appropriate without departing from the spirit of the present invention.

[0122] When buses 40A, 40B, and 40C receive at least one of the first event notification information and the second event notification information from the control device 21, the same camera image displayed on the vehicle-side display 50 may be simultaneously displayed on the display 24. This allows the administrator of the remote monitoring device 20 to more accurately recognize events occurring inside and outside buses 40A, 40B, and 40C.

[0123] When the vehicle-side display 50 displays multiple event images (camera images), the vehicle-side display 50 may not be divided into multiple areas as shown in Figures 12 to 14, but rather each event image may be displayed sequentially across the entire vehicle-side display 50 while switching between them.

[0124] Furthermore, when the vehicle-side display 50 displays multiple event images (camera images), the display mode may be adjusted based on the importance of each event image. For example, in the example shown in Figure 13, consider a case where the population density represented by camera image 70 is significantly higher than the population density represented by camera images 71 and 72. In this case, the event determination unit 292 determines that the importance of the event represented by camera image 70 is higher than the importance of the events represented by camera images 71 and 72. In this case, the second event notification information received by buses 40A, 40B, and 40C includes information regarding this importance. In this case, if each event image is displayed sequentially across the entire vehicle-side display 50, the display control unit 413 may control the vehicle-side display 50 so that the display time of camera image 70 is longer than the display time of camera images 71 and 72. Furthermore, in this case, if the vehicle-side display 50 is divided into multiple areas (three areas) and camera images 70, 71, and 72 are displayed in each area, the size of area 53-1 for displaying camera image 70 may be larger than the other areas 53-2 and 53-3.

[0125] Alternatively, the vehicle-side display 50 may display the specially processed image shown in Figure 19. In this modified version, the vehicle-side display 50 displays a bus illustration image 80 that depicts the interior (including seats) of buses 40A, 40B, and 40C in a two-dimensional manner, and an illustration image 81 that represents passengers captured by each in-vehicle camera 46 as circles (●). In this way, passengers who look at the vehicle-side display 50 can recognize where other passengers are located inside the vehicle and their movements, while also ensuring the protection of passenger privacy.

[0126] If an event occurs, the camera image that has not undergone any special processing may be displayed on the vehicle-side display 50.

[0127] Buses 40A, 40B, and 40C may have a function to determine the occurrence of events on the control device 21 and the external server 29.

[0128] An operating terminal (e.g., a smartphone or tablet computer) that is capable of wireless communication with the external server 29 and is held by a person who has been granted the prescribed authority by the administrator may communicate wirelessly with the external server 29 to enable the display of all image data and sensor group detection values ​​recorded in the storage 29D on the display unit of the operating terminal. In this way, for example, after an event occurs, police officers who arrive at the buses 40A, 40B, and 40C where the event occurred can use their operating terminals to check camera images and sensor group detection values ​​acquired at the time of the event or at a different time. Therefore, police officers can, for example, use their operating terminals to view images taken by the in-vehicle camera 46 at the time the event occurred, thereby confirming the situation inside the vehicle at the time of the event.

[0129] Buses 40A, 40B, and 40C do not need to be equipped with external cameras (external front camera 47F, external rear camera 47R, and external side camera 47S).

[0130] The external front camera 47F, the external rear camera 47R, and the external side camera 47S may be one unit or multiple units other than three.

[0131] Communication control between the remote monitoring device 20 and buses 40A, 40B, and 40C may be performed using a control method other than SIP. For example, communication control may be performed using Web Real-Time Communication. In this case, SIP may be combined with a control method other than SIP.

[0132] Multiple speakers 44 and microphones 45 may be provided on buses 40A, 40B, and 40C.

[0133] Furthermore, a bus may have multiple vehicles. For example, if a bus consists of multiple vehicles connected to each other, each vehicle may be provided with a vehicle-side display 50. In this case, the remote monitoring device 20 may display camera images representing events on the vehicle-side displays 50 of all vehicles, or it may display camera images representing events on the vehicle-side displays 50 of only some of the vehicles.

[0134] The present invention may also be applied to vehicles of a different type than buses 40A, 40B, and 40C (for example, passenger cars).

[0135] When the wireless communication interface 21E receives a second call request from buses 40A, 40B, or 40C, the speaker of the audio input / output device 28 may generate a predetermined sound. Also, when the wireless communication interface 21E receives a second call request from buses 40A, 40B, or 40C, the display 24 may display a message indicating the receipt of the second call request. [Explanation of Symbols]

[0136] 10. In-vehicle monitoring system (system) 21 Control device 214 Judgment section 24 displays 40A 40B 40C Bus (vehicle) 46 In-car camera 50 Vehicle-side displays

Claims

1. A vehicle capable of autonomous driving control, equipped with an in-vehicle camera for capturing images inside the vehicle and a vehicle-side display, A determination unit that determines whether or not an event has occurred in the vehicle, Equipped with, An in-vehicle monitoring system in which, when the determination unit determines that the aforementioned event has occurred, the in-vehicle camera's acquired camera image is displayed on the vehicle-side display.

2. The in-vehicle monitoring system according to claim 1, wherein the camera image is displayed on a display connected to a control device that can communicate wirelessly with the vehicle.

3. The in-vehicle monitoring system according to claim 1 or claim 2, wherein when the camera image is not displayed on the vehicle-side display, text indicating that the in-vehicle camera is operating is displayed on the vehicle-side display.

4. The in-vehicle monitoring system according to claim 1 or claim 2, wherein the specially processed camera image is displayed on the vehicle-side display.

5. The in-vehicle monitoring system according to claim 1 or claim 2, wherein the same camera image is simultaneously displayed on a display connected to a control device capable of wireless communication with the vehicle and on the vehicle-side display.

6. The in-vehicle monitoring system according to claim 1 or claim 2, wherein the vehicle is provided with a plurality of in-vehicle cameras, and the vehicle-side display displays a plurality of camera images acquired by each of the in-vehicle cameras while switching between them.

Images