Vehicle accident information link device

The vehicle accident peripheral information linking device addresses the lack of comprehensive accident information by correlating vehicle emergency data with surrounding data, improving emergency service dispatch efficiency.

JP7594384B2Active Publication Date: 2024-12-04SUBARU CORP
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
JP2020145300
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-08-31
Publication Date
2024-12-04
Estimated Expiration
2040-08-31

AI Technical Summary

Technical Problem

Existing emergency notification systems in vehicles lack sufficient information about accident situations, particularly when multiple vehicles and pedestrians are involved, leading to inadequate dispatch of emergency services.

Method used

A vehicle accident peripheral information linking device that acquires and correlates accident information from surrounding sources, such as peripheral terminals, with emergency information from the vehicle to enhance the understanding of the accident scenario.

Benefits of technology

Enhances the accuracy of accident situation assessment by incorporating surrounding information, enabling more effective dispatch of emergency services to both vehicle occupants and pedestrians.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007594384000001
    Figure 0007594384000001
  • Figure 0007594384000002
    Figure 0007594384000002
  • Figure 0007594384000003
    Figure 0007594384000003
Patent Text Reader

Abstract

To provide a surrounding information link device for a vehicle accident that can better grasp the accident situation using an emergency notification system.SOLUTION: A surrounding information link device for a vehicle accident, which is provided in an emergency notification system that can transmit emergency information about an accident from a vehicle involved in the accident to a server device 2, includes: acquiring accident surrounding information transmitted from a peripheral terminal (mobile terminal 9) other than the vehicle; determining that the acquired accident surrounding information is the accident information of the vehicle; and generating link information to associate the accident surrounding information determined to be the accident information of the vehicle with the emergency information transmitted from the vehicle to the server device 2.SELECTED DRAWING: Figure 5
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a peripheral information link device for a vehicle accident. [Background technology]

[0002] In the case of an accident occurring in a vehicle such as an automobile, it is conceivable to report accident information. For example, an emergency reporting system such as AACN (Advanced Automatic Collision Notification) has been put to practical use in automobiles. In AACN, an automobile involved in an accident uses an automatic reporting device installed in the automobile to transmit accident information such as the operating state of the passenger protection device at the time of the accident, the location, and the input direction and strength of the impact at the time of the accident to a server device in a call center (Patent Document 1). The call center checks the accident information of each automobile received by the server device, and requests the dispatch of a doctor helicopter or an ambulance. This can shorten the lead time until the doctor helicopter or ambulance is dispatched. It increases the possibility of saving the occupants of the vehicle involved in the accident. [Prior art documents] [Patent documents]

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

[0004] However, simply transmitting accident information from a vehicle involved in an accident to a server device may result in the server device not having enough information about the accident, making it difficult to accurately grasp the circumstances of the accident. For example, when a vehicle collides with a pedestrian or cyclist, information about the pedestrian or cyclist involved in the accident may not be sufficient if it is only information about the vehicle itself at the time of the accident. In addition, for example, if an accident occurs involving multiple vehicles and multiple pedestrians, it may not be possible to determine which vehicle the pedestrian involved in the accident was hit by. Furthermore, if there is insufficient information about pedestrians or other people involved in the accident and the circumstances of the accident cannot be accurately grasped, there is a possibility that the response team dispatched based on a request from the call center will not be able to provide adequate emergency treatment to the people involved in the accident.

[0005] In this way, emergency notification systems are required to be able to grasp the circumstances of accidents with a high degree of certainty. [Means for solving the problem]

[0006] A vehicle accident peripheral information link device according to one embodiment of the present invention is a vehicle accident peripheral information link device provided in an emergency notification system capable of transmitting emergency information related to an accident from a vehicle involved in an accident to a server device, the device comprising: The server device includes a setting unit that sets search conditions for searching cloud services based on the acquired emergency information of the accident when the emergency information of the accident is received from the vehicle, and a search unit that searches the cloud services based on the set search conditions. An acquisition unit for acquiring accident surrounding information; The acquired accident surrounding information is compared with the accident emergency information, and if there is a match, The acquired accident surrounding information is information about an accident involving the vehicle. Judgment a determination unit for determining whether the accident surrounding information is information about an accident of the vehicle by the determination unit; 、 a generating unit that generates link information to be associated with the emergency information; an output unit that uses the link information generated by the generation unit to output the accident-periphery information in association with the emergency information transmitted by the vehicle to the server device; has. Preferably, the setting unit sets, as the search conditions, a search area including a location of the accident site and a search time period including a time when the accident occurred.

[0007] Preferably, The accident surrounding information is image data, The determination unit is The image components of the vehicle in the image data as the accident surrounding information are collated with attribute information such as the type and color of the vehicle involved in the accident included in the emergency information, the image components of the vehicle in the image of the image data as the accident surrounding information are collated with the image components of the vehicle in the image of the vehicle involved in the accident included in the emergency information, or the image components of people in the image of the image data as the accident surrounding information are collated with the image components of people in the image of the vehicle involved in the accident included in the emergency information, and if the collated contents match, the image data to be acquired is Information about an accident involving said vehicle. and It is good to judge.

[0009] Preferably, the vehicle involved in the accident is Place of and transmitting information on a change in the position of the image data acquired by the acquisition unit to the server device. In Vehicle or other party Place ofThe change in position is obtained from the vehicle involved in the accident. The above position When there is a correlation with the information on the change in position, it is preferable to determine that the information is about an accident involving the vehicle. Effect of the Invention

[0011] In the present invention, a vehicle accident peripheral information link device is provided in an emergency notification system capable of transmitting emergency information related to an accident from a vehicle involved in an accident to a server device. The vehicle accident peripheral information link device acquires accident peripheral information that may be transmitted from a peripheral terminal other than the vehicle, compares it with emergency information or invention information for the vehicle, and determines that the information is about a vehicle accident. The vehicle accident peripheral information link device then generates link information that associates the accident peripheral information determined to be information about a vehicle accident with the emergency information transmitted by the vehicle to the server device. As a result, in the server device or the like, in addition to the emergency information on the accident from the vehicle involved in the accident, the accident surrounding information that may be transmitted from sources other than the vehicle based on the link information can be used. Based on the accident surrounding information, the call center staff or the like can grasp the situation that cannot be fully grasped only from the emergency information from the vehicle involved in the accident. Based on the rich information supplemented by the accident surrounding information, the call center staff or the like can make a detailed and more reliable judgment on the situation at the accident site and dispatch the necessary emergency personnel to the site. Based on the rich information supplemented by the accident surrounding information, the emergency personnel can also grasp the situation of not only the passengers but also pedestrians with a higher degree of certainty and dispatch to the site when they are in a position to respond to the situation. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is an explanatory diagram of an example of an emergency call system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is an explanatory diagram of a control system of an automobile that can function as an automatic notification device for transmitting emergency information in the automobile involved in the accident in FIG. [Diagram 3]FIG. 3 is an explanatory diagram of a server device used in the call center of FIG. [Figure 4] FIG. 4 is an explanatory diagram of a client terminal used in the dispatch unit of FIG. [Diagram 5] FIG. 5 is a sequence chart showing an example of a flow of a series of processes from an emergency call of a car involved in an accident to an ambulance dispatch in the emergency call system of FIG. [Figure 6] FIG. 6 is a flowchart of a link process for information surrounding a car accident in the server device of FIG. [Figure 7] FIG. 7 is an explanatory diagram of a comparison judgment by the server device of FIG. 6 regarding images as accident surroundings information from a peripheral terminal. [Figure 8] FIG. 8 is a diagram illustrating an example of a state in which an accident involving a plurality of automobiles and a plurality of pedestrians has occurred. [Figure 9] FIG. 9 is a flowchart of a process for generating automobile accident information by the automobile control system according to the second embodiment of the present invention. [Figure 10] FIG. 10 is an explanatory diagram of a collation decision for an image as accident surroundings information by a peripheral terminal when the accident information of FIG. 9 is used in the link processing of the server device of FIG. [Figure 11] FIG. 11 is a flowchart showing a link process for peripheral information of an automobile accident by the automobile control system according to the third embodiment of the present invention. [Figure 12] FIG. 12 is an explanatory diagram of a comparison judgment of an image as accident surroundings information by a peripheral terminal in the automobile of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0014] [First embodiment] FIG. 1 is an explanatory diagram of an example of an emergency call system 1 according to a first embodiment of the present invention. The emergency notification system 1 in FIG. 1 includes a server device 2 used in a call center of an organization that manages road accidents caused by automobiles 10, a client terminal 3 used by rescue units such as firefighters, an automatic notification device 4 installed in a plurality of automobiles 10, and a wireless communication network 5 that provides communication lines to these. The wireless communication network 5 includes base stations 6 that are distributed in an area along roads, for example, to communicate with wireless terminals such as the automatic notification device 4, and a communication network 7 that connects the plurality of base stations 6. The base stations 6 function as access points to which a plurality of wireless terminals within a communication zone are connected. The communication network 7 in FIG. 1 is connected to the server device 2 of the call center and the client terminal 3 of the rescue unit. An example of such an emergency notification system 1 when an accident occurs is AACN (Advanced Automatic Collision Notification). In AACN, accident information is instantly and automatically transmitted from the automobile 10 involved in the accident to the server device 2 of the call center, and the rescue unit dispatches an ambulance 11 or a doctor helicopter based on a dispatch request from the call center. The call center can select a rescue unit based on the circumstances of the accident and issue a dispatch request. An ambulance or doctor helicopter can be dispatched to the accident scene while grasping the circumstances of the accident. This makes it possible to provide appropriate rescue treatment to the parties involved in the accident immediately with a short lead time. Although the emergency notification system 1 in FIG. 1 shows an example of use by multiple organizations in cooperation with each other, it may also be used independently by organizations that manage areas including roads on which automobiles 10 and the like can travel, such as police, fire departments, government offices, hospitals, medical institutions, security companies, and management companies. GNSS satellites 110 are also shown in Fig. 1. Each device in Fig. 1 can obtain its own position and time by receiving radio waves including position information of latitude and longitude and time information from the multiple GNSS satellites 110. The multiple devices can obtain their current time and current position with high accuracy by receiving radio waves from the multiple GNSS satellites 110 that cooperate with each other. The multiple devices can use a common synchronized time.

[0015] FIG. 2 is an explanatory diagram of a control system 20 of the automobile 10 capable of functioning as the automatic notification device 4 for transmitting emergency information in the automobile 10 involved in an accident in FIG. 2, a control system 20 of the automobile 10 is shown as a representative of a plurality of control devices, each of which is built into a control ECU (Electronic Control Unit). In addition to the control ECU, the control device may have, for example, a memory for recording control programs and data, an input / output port for connecting to a controlled object or a device for detecting the state of the controlled object, a timer for measuring time or hours, and an internal bus to which these are connected. 2 specifically includes, for example, a drive ECU 21, a steering ECU 22, a braking ECU 23, a driving control ECU 24, a driving operation ECU 25, a detection ECU 26, an external communication ECU 27, an internal communication ECU 28, a UI operation ECU 29, and an occupant protection ECU 30. The control system 20 of the automobile 10 may include other control ECUs not shown.

[0016] The control ECUs are connected to a vehicle network 36, such as a controller area network (CAN) or a local interconnect network (LIN) used in the automobile 10. The vehicle network 36 may be configured with a plurality of bus cables 37 that can connect the control ECUs, and a central gateway (CGW) 38 as a relay device to which the bus cables 37 are connected. The control ECUs are assigned IDs as identification information that are different from each other. Basically, the control ECUs periodically output data to other control ECUs. The ID of the control ECU that is the output source and the ID of the control ECU that is the output destination are added to the data. The other control ECUs monitor the bus cable 37, and when the ID of the output destination is, for example, their own, acquire the data and execute processing based on the data. The central gateway 38 monitors each of the multiple bus cables 37 that are connected, and when it detects a control ECU that is connected to a bus cable 37 different from the control ECU that is the output source, it outputs data to that bus cable 37. Such relay processing by the central gateway 38 allows a plurality of control ECUs to input and output data between other control ECUs that are connected to a bus cable 37 different from the bus cable 37 to which each control ECU is connected.

[0017] The UI operation ECU 29 is connected to a display device 41 and an operation device 42 as user interface devices for a passenger in the vehicle. The display device 41 may be, for example, a liquid crystal device or a video projection device. The operation device 42 may be, for example, a touch panel, a keyboard, or a non-contact operation detection device. The display device 41 and the operation device 42 may be installed on the inner surface of the vehicle interior in which the passenger sits. The UI operation ECU 29 acquires data from the vehicle network 36 and displays the data on the display device 41. The UI operation ECU 29 outputs an operation input to the operation device 42 to the vehicle network 36. The UI operation ECU 29 may also execute processing based on the operation input and include the processing result in the data. The UI operation ECU 29 may, for example, display a navigation screen for setting a destination or the like on the display device 41, search for a route to the destination selected by the operation input, and include the route data in the data. The route data may include attribute information, such as lanes, of the road used to travel from the current location to the destination.

[0018] The driving operation ECU 25 is connected to operation members for the occupant to control the traveling of the automobile 10, such as a steering wheel, a brake pedal, an accelerator pedal, a shift lever, etc. (not shown). When an operation member is operated, the driving operation ECU 25 outputs data including the presence or absence of the operation and the amount of operation to the vehicle network 36. The driving operation ECU 25 may also execute processing regarding the operation of the operation member and include the processing result in the data. For example, when the accelerator pedal is operated in a situation where there is another moving object or a fixed object in the traveling direction of the automobile 10, the driving operation ECU 25 may determine that the operation is abnormal and include the determination result in the data.

[0019] The detection ECU 26 is connected with, as detection members for detecting the running state of the automobile 10, for example, a speed sensor 51 for detecting the speed of the automobile 10, a three-axis acceleration sensor 52 for detecting the acceleration of the automobile 10, a stereo camera 53 for capturing images of the surroundings outside the automobile 10, an in-car camera 54 for capturing images of passengers in the vehicle cabin, a microphone 55 for converting sounds inside and outside the vehicle into data, and a GNSS receiver 56 for detecting the position of the automobile 10. The GNSS receiver 56 receives radio waves from a plurality of GNSS satellites 110 and obtains the latitude, longitude, and current time, which are the current position of the vehicle. The detection ECU 26 obtains detection information from the detection members and outputs data including the detection information to the vehicle network 36. The detection ECU 26 may also execute processing based on the detection information and include the processing result in the data. For example, when the three-axis acceleration sensor 52 detects acceleration exceeding a threshold value for collision detection, the detection ECU 26 may determine collision detection and include the collision detection result in the data. The detection ECU 26 may extract objects around the vehicle, such as pedestrians, other vehicles, street trees, utility poles, and guardrails, based on images from the stereo camera 53, determine the type and attributes of the objects, and estimate the relative direction and relative distance of the object, and the direction of movement if it is moving, based on the position, size, and changes of the object in the image.The detection ECU 26 may output data including prediction information for collisions with other objects, including these estimation results, to the vehicle network 36.

[0020] An external communication device 61 is connected to the external communication ECU 27. These constitute an external communication terminal 60 as a communication device provided in the automobile 10. The external communication device 61 wirelessly communicates with a base station 6 of a wireless communication network 5 located near the automobile 10. The external communication ECU 27 transmits and receives data to and from the server device 2 and the like through the wireless communication network 5 using the wireless communication between the external communication device 61 and the base station 6. The external communication terminal 60 is a transmitting device provided in the automobile 10, and is a type of wireless terminal.

[0021] An internal communication device 71 is connected to the internal communication ECU 28. These constitute an internal communication terminal 70 as another communication device provided in the automobile 10. The internal communication device 71 performs short-distance wireless communication with, for example, a portable terminal 9 of an occupant inside the automobile 10. The portable terminal 9 wirelessly communicates with a base station 6 of a nearby wireless communication network 5. FIG. 1 illustrates a portable terminal 9 carried by a pedestrian. The internal communication ECU 28 transmits and receives data between the portable terminal 9 of the occupant inside the automobile 10 and the internal communication device 71 using short-distance wireless communication between the portable terminal 9 and the occupant. Note that the portable terminal 9 may basically be capable of wireless communication with a base station 6 of a nearby wireless communication network 5. The internal communication terminal 70 that communicates with the mobile terminal 9 of the passenger in the vehicle may wirelessly communicate with the mobile terminal 9 based on a standard such as IEEE802.15.1. In a standard such as IEEE802.15.1, the internal communication terminal 70 and the mobile terminal 9 search for communication-enabled communication devices in the vicinity and can connect to each other based on matching authentication information. The internal communication terminal 70 and the mobile terminal 9 are directly connected and paired without using a base station 6. The authentication information may be registered in each memory (not shown). For subsequent communication between the internal communication terminal 70 and the mobile terminal 9, the internal communication ECU 28 automatically authenticates and connects the mobile terminal 9 based on the authentication information registered in advance. As a result, the mobile terminal 9 used by the passenger or the like is automatically connected to the internal communication terminal 70 when the passenger gets into the automobile 10, and becomes capable of communicating with the internal communication terminal 70.

[0022] The driving control ECU 24 controls the driving of the automobile 10. The driving control ECU 24 acquires data from the external communication ECU 27, the detection ECU 26, the driving operation ECU 25, etc., via the vehicle network 36, and executes control of automatic driving or manual driving assistance for the driving of the automobile 10. The driving control ECU 24 generates driving control data for controlling the driving of the automobile 10 based on the acquired data, and outputs the data to the drive ECU 21, the steering ECU 22, and the braking ECU 23. The drive ECU 21, the steering ECU 22, and the braking ECU 23 control the driving of the automobile 10 based on the input driving control data.

[0023] A plurality of seat belt devices, a plurality of airbag devices, and an occupant protection memory 87 are connected to the occupant protection ECU 30. The seat belt devices include, for example, a driver's side seat belt device 81 for an occupant driving the automobile 10, and a passenger's side seat belt device 82 for an occupant riding in the automobile 10. The airbag devices include, for example, a driver's side front airbag device 83 that deploys in front of the occupant driving the automobile 10, a driver's side curtain airbag device 84 that deploys outside the occupant driving the automobile 10, a passenger's side front airbag device 85 that deploys in front of the occupant riding in the automobile 10, and a passenger's side curtain airbag device 86 that deploys outside the occupant riding in the automobile 10. These devices constitute the occupant protection device 80. Based on the information from the detection ECU 26 predicting a collision with another object or on the information of the collision detection result, the occupant protection ECU 30 activates or controls a seat belt device or an air bag device.

[0024] The occupant protection memory 87 is a computer-readable recording medium, and stores programs executed by the occupant protection ECU 30, setting values, etc. The occupant protection memory 87 may store information on the control contents by the occupant protection ECU 30. The occupant protection ECU 30 reads and executes the programs from the occupant protection memory 87. In this way, the occupant protection ECU 30 can function as an occupant protection control unit of the automobile 10. The occupant protection ECU 30, which serves as an occupant protection control unit of the automobile 10, executes occupant protection processing when it detects a collision, for example, and also collects and transmits emergency information and the like about the automobile 10. The occupant protection ECU 30 instantly transmits the collected emergency information about the accident and the like to the server device 2 via the base station 6 and the communication network 7 using the external communication terminal 60.

[0025] FIG. 3 is an explanatory diagram of the server device 2 used in the call center of FIG. The server device 2 in FIG. 3 includes a server communication device 91, a server memory 92, a server CPU 93, a server GNSS receiver 94, a server monitor 95, a server call device 96, and a server bus 97 to which these are connected.

[0026] The server communication device 91 is connected to the communication network 7 of the wireless communication network 5. The server communication device 91 transmits and receives data to and from other devices, for example, the external communication terminal 60 as a wireless terminal of the automobile 10, and the client terminal 3, through the wireless communication network 5. The server GNSS receiver 94 receives radio waves from the GNSS satellites 110 to obtain the current time. The server device 2 may include a server timer (not shown) that is calibrated by the current time of the server GNSS receiver 94. The server monitor 95 displays information of the server device 2. The server monitor 95 displays, for example, emergency information that the server device 2 receives from the automobile 10 that has been involved in an accident or the like. The server communication device 96 is used by call centre staff to make calls to and from users of mobile terminals 9 that are connected using the server communication device 91 .

[0027] The server memory 92 is a computer-readable recording medium, and stores programs executed by the server CPU 93, setting values, etc. The server memory 92 may store information on the contents of control by the server CPU 93. The server CPU 93 reads and executes programs from the server memory 92. In this way, a server control unit is realized in the server device 2. The server CPU 93 as the server control unit manages the overall operation of the server device 2. For example, when the server communication device 91 receives emergency information instantly transmitted from each automobile 10 involved in an accident, the server CPU 93 of the call center server device 2 displays the received emergency information on the server monitor 95. A call center staff member determines the situation of the accident based on the displayed emergency information of each automobile 10 and inputs a dispatch request accordingly. The server CPU 93 transmits the dispatch request to the client terminal 3 using the server communication device 91.

[0028] FIG. 4 is an explanatory diagram of the client terminal 3 used by the dispatch unit of FIG. The client terminal 3 in FIG. 4 includes a client communication device 101, a client memory 102, a client CPU 103, a client announcement device 104, a client GNSS receiver 105, a client monitor 106, a client call device 107, and a client bus 108 to which these are connected.

[0029] The client communication device 101 is connected to a communication network 7 of the wireless communication network 5. The client communication device 101 transmits and receives data to and from other devices, for example, an external communication device 61 as a wireless terminal of the automobile 10, and the server device 2, through the wireless communication network 5. The client GNSS receiver 105 obtains the current time by receiving radio waves from the GNSS satellites 110. The client terminal 3 may include a server timer (not shown) that is calibrated by the current time of the client GNSS receiver 105. The client monitor 106 displays information of the client terminal 3. The client monitor 106 displays, for example, a call-out request received from the server device 2. The client notification device 104 outputs a sound requesting dispatch to the members of the dispatch unit. The client calling device 107 is used by the dispatch team members to make calls to and from users of mobile terminals 9 that are connected using the client communication device 101 .

[0030] The client memory 102 is a computer-readable recording medium, and stores programs executed by the client CPU 103, setting values, etc. The client memory 102 may store information on the contents of control by the client CPU 103. The client CPU 103 reads and executes the programs from the client memory 102. In this way, a client control unit is realized in the client terminal 3. The client CPU 103 as the client control unit manages the overall operation of the client terminal 3. For example, when the client communication device 101 receives a dispatch request, the client CPU 103 of the client terminal 3 of the rescue dispatch team reports the dispatch request via the client notification device 104. As a result, the rescue dispatch team dispatches an ambulance 11 or a doctor helicopter to the accident scene based on the dispatch request. The dispatch team can be dispatched to the accident scene while understanding the accident situation for each automobile 10. The dispatch team can immediately provide appropriate rescue treatment to the parties involved in the accident with a short lead time.

[0031] FIG. 5 is a sequence chart showing an example of a flow of a series of processes from an emergency call from the automobile 10 involved in an accident to an ambulance dispatch in the emergency call system 1 of FIG. 5 shows a control system 20 as an automatic reporting device 4 of an automobile 10, a server device 2 of a call center, a client terminal 3 of a dispatch unit, a mobile terminal 9 of a pedestrian who is not involved in an accident, and an SNS server 12. Time flows from top to bottom.

[0032] In step ST21, the detection ECU 26 of the control system 20 of the automobile 10 detects a collision of the automobile 10. The detection ECU 26 detects a collision, for example, when the magnitude of acceleration detected by the three-axis acceleration sensor 52 is greater than a predetermined threshold value. If a collision is not detected, the detection ECU 26 repeats this process. If a collision is detected, the detection ECU 26 transmits collision detection information to the occupant protection ECU 30 and proceeds to step ST4. Note that the detection ECU 26 may end this process if no collision is detected after a certain time has elapsed since starting this process. The detection ECU 26 may predict that a collision is unavoidable before detecting the collision. Furthermore, the occupant protection ECU 30 may execute pre-processing for occupant protection before detecting the collision based on the prediction that a collision is unavoidable. As the pre-processing, the occupant protection ECU 30 may wind up the surplus of the seat belt of the seat belt device to set the seat belt device in a pre-tensioned state, or execute other processing. For example, the occupant protection ECU 30 may execute pre-deployment of an airbag device. In step ST22, the occupant protection ECU 30 of the automobile 10 that has detected the collision executes a process for protecting the occupant based on the information that the detection ECU 26 has detected the collision. The occupant protection ECU 30 selects a seat belt device and an airbag device to be activated. The occupant protection ECU 30 may select a seat belt device for a seat in which an occupant is seated, and an airbag device that deploys in a direction in which the occupant's upper body falls due to a collision. The occupant protection ECU 30 winds up the remaining seat belt of the selected seat belt device to set it in a pretensioned state. The occupant protection ECU 30 selects an airbag device that can be deployed in a direction in which the occupant's upper body falls due to a collision, based on the input direction and magnitude of the detected collision. In this embodiment, the occupant protection ECU 30 executes the occupant protection control after detecting a collision in step ST21. However, the occupant protection control may be executed at the collision prediction stage before detecting a collision. In step ST23, the occupant protection ECU 30 of the automobile 10 that has executed the occupant protection control collects emergency information about the accident. The emergency information about the accident may basically be information collected by the AACN described above. The AACN collects emergency information such as the operating state and position of the occupant protection device 80 at the time of the accident, and the input direction and strength of the impact at the time of the accident. In step ST24, the occupant protection ECU 30 of the automobile 10 executes an automatic notification.

[0033] In step ST25, the server communication device 91 of the call center server device 2 receives automatic notification information from the automobile 10 involved in the accident. The automatic notification information received by the server communication device 91 may be recorded in the server memory 92. The server communication device 91 of the call center server device 2 may receive automatic notification information from other automobiles involved in the same accident before or after step ST25. In step ST26, the server CPU 93 of the call center server device 2 displays the emergency information of the automatic report received by the server communication device 91 on the server monitor 95. The staff of the call center can check the status of the accident of the automobile 10 based on the emergency information of the accident displayed on the server monitor 95. In step ST27, the server CPU 93 of the server device 2 of the call center communicates with the external communication ECU 27 of the automobile 10 involved in the accident. In step ST28, the occupant protection ECU 30 of the automobile 10 responds to the voice call. This establishes a communication line that allows communication between the server call device 96 and, for example, the microphone 55 of the automobile 10. The call center staff confirms the safety and health of the occupants by voice. This allows the staff to directly confirm the condition of the occupants in the automobile 10 involved in the accident, such as the degree of injury. The call center staff may input the confirmation result to the server device 2. In step ST29, the server CPU 93 of the call center server device 2 estimates the situation. The server CPU 93 may estimate the situation based on the automatic report information received by the server communication device 91, the accident inconsistency judgment result, and the input information of the call center staff. The server CPU 93 may compare the information with emergency information of past accidents and estimate the situation by artificial intelligence processing. In addition, the call center staff may estimate the situation by comprehensively considering the situation and input the estimation result to the server device 2. In step ST30, the server CPU 93 of the server device 2 of the call center arranges for a dispatch. The server CPU 93 transmits a dispatch request to the client terminal 3 of the dispatch unit using the server communication device 91. The server CPU 93 may transmit the dispatch request based on an operation of a staff member of the call center.

[0034] In step ST31, the client communication device 101 of the client terminal 3 of the dispatch unit receives the dispatch request from the server device 2. The dispatch request received by the client communication device 101 may be recorded in the client memory 102. In step ST32, the client CPU 103 of the client terminal 3 of the dispatch unit notifies the dispatch. The client CPU 103 outputs a dispatch request sound from the client notification device 104 based on the fact that the client communication device 101 has received the dispatch request. The client CPU 103 may also display a dispatch request screen on the client monitor 106. The dispatch request screen may display information on the automatic report and information input by the call center staff. In step ST33, the members of the response unit are dispatched. The members of the response unit understand that a request for dispatch has been made to their unit by the dispatch request sound and the dispatch request screen, and can make an emergency dispatch using a doctor helicopter or an ambulance 11.

[0035] This allows the doctor helicopter and ambulance dispatch unit to be dispatched without delay and with the minimum lead time required based on the emergency accident information automatically reported from the accident-hit vehicle 10. The doctor helicopter and ambulance dispatch unit can be dispatched in an emergency with appropriate preparations based on the emergency accident information obtained in advance. This increases the possibility of saving the person involved in the accident.

[0036] Meanwhile, the automobile 10 traveling on the road may collide with a moving object other than another automobile, such as a pedestrian or a cyclist. In this case, the automobile 10 involved in the accident can transmit the above-mentioned emergency information of the accident to the server device 2, but the pedestrian or the like cannot necessarily transmit the emergency information of the accident to the server device 2. In particular, if the pedestrian involved in the accident is in a state of confusion, it is difficult for him or her to operate the mobile terminal 9 that he or she carries. As a result, the server device 2 may lack information about the accident, and the situation of the accident may not be accurately understood. In addition, for example, if an accident involving multiple automobiles 10 and multiple pedestrians occurs, it may not be possible to ascertain which automobile 10 the pedestrian involved in the accident collided with. The degree of injury to the pedestrian, etc. varies greatly depending on the manner of the collision with the automobile 10. The automobile 10 involved in the accident can include information in the emergency information that allows the degree of injury of the pedestrian or cyclist involved to be estimated, such as the position, direction, and degree of the impact input, and images of the pedestrian or cyclist involved. However, if it is not possible to link multiple pedestrians to which automobile 10 they were hit by, it may be difficult or time-consuming to determine which pedestrian the information applies to when utilizing the emergency information. For example, if an accident involving multiple automobiles 10 and multiple pedestrians occurs during the daytime on a clear day, if the emergency information includes an image captured by the automobile 10, it is relatively easy to distinguish between the emergency information of the automobile 10 and the pedestrian who actually collided based on the size, gender, and clothing characteristics of the pedestrian. On the other hand, if it is rainy at night, the image captured by the automobile 10 may not be able to clearly capture all of the characteristics of the pedestrian. It may be difficult to determine which pedestrian has been hit by the automobile 10 that issues the emergency information. As a result, there is a possibility that a response team dispatched based on a request from the call center will not be able to provide adequate emergency treatment to those involved in the accident. In this way, it is desirable for the emergency call system 1 to be able to grasp the circumstances of the accident with a higher degree of certainty.

[0037] Therefore, in the emergency notification system 1 of FIG. 5, the server device 2 receives automatic notification information from the automobile 10 involved in the accident in step ST25, and then extracts and sets search conditions from the received information in step ST43, and searches for surrounding information on the web with the set conditions in step ST44. For example, as shown in the emergency notification system 1 of FIG. 1, another pedestrian near the accident scene operates his / her mobile terminal 9 to take an image of the accident scene in step ST41 and upload it to an SNS in step ST42. The mobile terminal 9 transmits the captured image data to an SNS server 12 connected to the communication network 7 through the base station 6 of the wireless communication network 5 and the communication network 7. The captured image data of the accident scene is registered in the SNS server 12 for this cloud service. The captured image data usually includes information related to the image capture, such as the location of the image capture point and the image capture time, as tag data or the like. In addition, there is a high probability that the captured image of the accident scene includes the automobile 10, which is the subject involved in the accident, and the pedestrian, which is the other party. By acquiring such captured image data of the accident scene, the server device 2 may be able to provide call center staff and the like with information that is insufficient in the emergency information from the automobile 10. This will be described in detail below.

[0038] Fig. 6 is a flowchart of link processing for information surrounding an accident in the server device 2 of Fig. 1. Fig. 6 corresponds to the processing from step ST25 to step ST26 of Fig. 5. When the automobile 10 detects a collision caused by an accident involving the automobile 10, it transmits emergency information relating to the accident to the server device 2 of the emergency notification system 1. When the server CPU 93 of the server device 2 receives new emergency information from the automobile 10, it executes the link processing of FIG.

[0039] In step ST25, the server CPU 93 judges whether or not emergency information of an accident has been received from the automobile 10 that has been involved in a new accident. The emergency information of an accident may include, for example, the location of the accident site, the time of the accident, occupant protection information in the automobile 10, the input part of the impact of the accident, the input direction, and the size of the impact, as well as additional information such as the automobile 10 attributes such as the vehicle type and color, images of the interior and exterior captured by the vehicle, and the detection value of the vehicle sensor. If emergency information of a new accident has not been received, the server CPU 93 repeats this process. If emergency information of a new accident has been received, the server CPU 93 advances the process to step ST43.

[0040] In step ST43, the server CPU 93 sets search conditions for searching cloud services such as SNS based on the acquired emergency information of the accident. For example, the server CPU 93 may set a search area including the location of the accident site and a search time period including the time of the accident as the search conditions.

[0041] In step ST3, the server CPU 93 starts the process of step ST44 and searches the cloud service according to the set search conditions. There is a possibility that accident surrounding information such as image data of the accident scene has been uploaded to the SNS server 12 of the cloud service from a peripheral terminal such as a mobile terminal 9 of a pedestrian who was in the vicinity of the accident scene. The server CPU 93 searches for and acquires the accident surrounding information from such peripheral terminals according to the set search conditions. Here, the peripheral terminal may be any terminal other than the automobile 10 involved in the accident, and may be another automobile.

[0042] In step ST4, the server CPU 93 judges whether or not the accident surrounding information, such as image data of the accident scene, has been acquired. If the accident surrounding information has not been acquired, the server CPU 93 returns the process to step ST3 and continues searching the cloud service. This makes it possible to acquire the accident surrounding information uploaded to the cloud service after the server device 2 receives the emergency information of the accident. When the accident surrounding information is acquired, the server CPU 93 advances the process to step ST5.

[0043] In step ST5, the server CPU 93 compares the acquired accident surrounding information such as image data of the accident scene with the emergency information of the accident from the automobile 10 acquired in step ST25. For example, the server CPU 93 extracts an image component of the automobile 10 from the image of the image data as the accident surrounding information, and compares it with attribute information such as the type and color of the automobile 10 involved in the accident included in the emergency information. In addition, for example, the server CPU 93 may compare the image component of the automobile 10 included in the image of the image data as the accident surrounding information with the image component of the own automobile in the image of the automobile 10 involved in the accident included in the emergency information. In addition, the server CPU 93 may compare the image component of a person such as a pedestrian included in the image of the image data as the accident surrounding information with the image component of a person such as a pedestrian in the image of the automobile 10 involved in the accident included in the emergency information. Furthermore, the server CPU 93 may compare again here whether the accident surrounding information is the position of the accident scene or the time of occurrence.

[0044] In step ST6, the server CPU 93 judges whether the collated accident-periphery information matches the emergency information of the accident from the automobile 10 acquired in step ST25. If all collation elements, such as the model and color of the automobile 10, related to the collation judgment described above, match, the server CPU 93 judges that the accident-periphery information matches the emergency information and proceeds to step ST7. If any element related to the collation judgment does not match, the server CPU 93 judges that the accident-periphery information does not match the emergency information, skips step ST7, and proceeds to step ST8.

[0045] In step ST7, the server CPU 93 generates link information that associates the matched accident periphery information with the emergency information of the accident from the automobile 10 acquired in step ST25. The link information may be, for example, an address such as a URL in the SNS server 12 for the matched accident periphery information and a management ID to be added to the emergency information. In this way, the server device 2 generates link information that can be used in the server device 2 by itself. The link information is recorded in the server memory 92 in association with the emergency information of the accident.

[0046] In step ST8, the server CPU 93 judges whether to continue the search for cloud services. Searching for cloud services takes time. The server CPU 93 may search for multiple cloud services. On the other hand, the server device 2 needs to provide emergency information, etc. to the call center staff as soon as possible. If the time elapsed since receiving the emergency information does not exceed a predetermined threshold, the server CPU 93 judges to continue the search for cloud services and returns the process to step ST3. As a result, the server CPU 93 executes a search for the next accident surrounding information. If the time elapsed since receiving the emergency information exceeds the predetermined threshold, the server CPU 93 ends the search for cloud services as the process of step ST44 and proceeds to step ST9.

[0047] In step ST9, the server CPU 93 starts the process of step ST26, reads the emergency information from the server memory 92, and displays it on the server monitor 95. For example, an AACN standard screen is displayed on the server monitor 95. The AACN standard screen displays the location of the accident site, the time of the accident, occupant protection information in the automobile 10, and the input part, input direction, and magnitude of the impact of the accident. In addition, the AACN standard screen may also display a selection button for link information by cloud search, etc.

[0048] In step ST10, the server CPU 93 determines whether or not link information has been selected. The server CPU 93 may determine whether or not link information has been selected based on whether or not a selection button for link information displayed together with the AACN standard screen has been operated by a call center staff member. If link information has not been selected, the server CPU 93 returns the process to step ST9 and continues to display the AACN standard screen. If link information has been selected, the server CPU 93 advances the process to step ST11.

[0049] In step ST11, the server CPU 93 acquires accident periphery information, such as image data of the accident scene, from the SNS server 12 or the like based on the selected link information, and displays it on the server monitor 95. The server CPU 93 uses the link information generated by itself in the server device 2 to output the accident periphery information in association with the emergency information transmitted to the server device 2 by the automobile 10 involved in the accident. This causes the server CPU 93 to end the processing of step ST44.

[0050] FIG. 7 is an explanatory diagram of a collation decision for an image as accident surroundings information by a peripheral terminal in the link processing of the server device 2 in FIG.

[0051] 7A shows an image of a traveling automobile 10 captured by a mobile terminal 9 at a location away from the accident site. In this case, the image as the accident surroundings information is added with an image capturing position and image capturing time different from those of the accident site. Therefore, in step ST3 or step ST6, the server CPU 93 determines that the position and time of the image as the accident surroundings information do not match the position at the accident site and the accident included in the emergency information acquired from the automobile 10 involved in the accident.

[0052] 7B shows an image of the automobile 10 involved in the accident and a pedestrian captured by the mobile terminal 9 near the accident scene. In this case, the image as the accident surroundings information is added with the image capturing position and image capturing time that are substantially the same as those of the accident scene. Therefore, in step ST3 or step ST6, the server CPU 93 determines that the position and time of the image as the accident surroundings information match the position and accident at the accident scene included in the emergency information acquired from the automobile 10 involved in the accident.

[0053] In this case, the server CPU 93 generates link information by determining that only the image in Fig. 7(B) matches the image in Fig. 7(A) and the image in Fig. 7(B) uploaded to the SNS server 12. In step ST11, only the image in Fig. 7(B) is displayed on the server monitor 95 among the images in Fig. 7(A) and 7(B).

[0054] As described above, in this embodiment, the accident surrounding information link device is provided in the server device 2 of the emergency notification system 1 that can transmit emergency information related to the accident from the automobile 10 that has been involved in the accident to the server device 2. The accident surrounding information link device acquires accident surrounding information, such as an image of the accident scene, transmitted from a peripheral terminal other than the automobile 10 that has been involved in the accident to a cloud service such as the SNS server 12, and compares it with the emergency information of the automobile 10 that has been involved in the accident to determine that it is information about the accident of the automobile 10. Then, link information that associates the accident surrounding information of the peripheral terminal that has been determined to be information about the accident of the automobile 10 with the emergency information transmitted by the automobile 10 to the server device 2 is generated so that it can be used in the server device 2. As a result, in addition to the emergency information related to the accident from the automobile 10 that has been involved in the accident, the server device 2 and the like can use the accident surrounding information transmitted from the peripheral terminal other than the automobile 10 that has been involved in the accident to the cloud service such as the SNS server 12 based on the link information. It becomes possible for the staff of the call center and the like to grasp a situation that cannot be grasped only by the emergency information from the automobile 10 that has been involved in the accident, based on the accident surrounding information. Call center staff and others can make detailed and more reliable judgments about the situation at the accident site based on the rich information supplemented by the accident surroundings information, and can dispatch the necessary emergency personnel to the site. Emergency personnel can also grasp the situation of not only the passengers but also pedestrians based on the rich information supplemented by the accident surroundings information, and can dispatch to the site when they are able to respond to the situation.

[0055] For example, if a pedestrian or cyclist is involved in an accident involving the automobile 10, it is expected that the pedestrian or cyclist involved in the accident can be identified from the accident surroundings information associated with the accident through the link information.

[0056] In addition, for example, even if an accident occurs involving multiple automobiles 10 and multiple pedestrians, it is expected that the correspondence between which automobile 10 each pedestrian collided with can be appropriately determined based on the information about the surrounding area of ​​the accident that is associated with the information by the link information. Information on which direction a pedestrian who collided with the automobile 10 was thrown is obtained from an image of the accident included in emergency information of one of the automobiles 10. For example, when acquiring accident periphery information such as an image of the accident scene and comparing it with emergency information on the automobile 10 involved in the accident, the peripheral information link device compares the direction in which the pedestrian who collided with the automobile 10 in the emergency information was thrown from an image of both the automobile 10 and the thrown pedestrian in the accident periphery information. If the accident periphery information and the emergency information match, the peripheral information link device associates the pedestrian in the accident periphery information with the emergency information as someone who came into contact with the automobile 10. Even if the accident surroundings information is an image capturing only a pedestrian who was thrown away, if information on the position of the photographer and the shooting direction can be obtained, the pedestrian's position can be estimated and the relative positional relationship with the position of the automobile 10 included in the emergency information can be used to associate the pedestrian in the accident surroundings information with the emergency information as having come into contact with one automobile 10. In this way, even if an accident involves multiple automobiles 10 and multiple pedestrians and it is not possible to determine which pedestrian has been hit from the emergency information alone, the surrounding information link device can associate the pedestrian with the emergency information, making it possible to utilize the emergency information to provide rescue to the pedestrian.

[0057] FIG. 8 is a diagram illustrating an example of a state in which an accident involving a plurality of automobiles and a plurality of pedestrians has occurred. In Fig. 8, a first vehicle 10A and a second vehicle 10B traveling in opposite directions on a road collide with each other, then move toward the left and right shoulders of the road and stop. The first vehicle 10A collides with a first pedestrian 120A on one shoulder. The second vehicle 10B collides with a second pedestrian 120B on the other shoulder. When acquiring information about such an accident, the surrounding information link device can determine, based on the acquired information, that an accident has occurred involving multiple automobiles 10A, 10B and multiple pedestrians 120A, 120B. Furthermore, the peripheral information link device may identify or attempt to identify that the first automobile 10A has collided with the first pedestrian 120A and that the second automobile 10B has collided with the second pedestrian 120B in the accident. The peripheral information link device may identify, for example, from an image in which both the first automobile 10A and the first pedestrian 120A are involved in an accident. The peripheral information link device may identify, for example, from an image in which both the second automobile 10B and the second pedestrian 120B are involved in an accident. If either of these identifications can be made, the peripheral information link device may estimate the extent of the collision with the first pedestrian 120A and the extent of injury from information on the acceleration of the first automobile 10A during the accident, or estimate the extent of the collision with the second pedestrian 120B and the extent of injury from information on the acceleration of the second automobile 10B during the accident. By obtaining information from the analysis of such accidents, a response unit can rush to the scene with equipment and scale appropriate to the circumstances of the accident.

[0058] [Second embodiment] Next, an emergency call system 1 according to a second embodiment of the present invention will be described. In the following description, differences from the above-described embodiment will be mainly described. The same components as those in the above-described embodiment are designated by the same reference numerals, and the description thereof will be omitted.

[0059] FIG. 9 is a flowchart of a process for generating accident information in the automobile 10 by the control system 20 of the automobile 10 according to the second embodiment of the present invention. When the control system 20 of the automobile 10 detects a collision caused by an accident involving the automobile itself, it executes the process of generating accident information shown in FIG.

[0060] In step ST21, the detection ECU 26 determines whether or not a collision has been detected. The detection ECU 26 detects a collision when, for example, the magnitude of acceleration detected by the three-axis acceleration sensor 52 is greater than a predetermined threshold value. If a collision is not detected, the detection ECU 26 repeats this process. If a collision is detected, the detection ECU 26 transmits collision detection information to the occupant protection ECU 30 and proceeds to step ST4. Note that the detection ECU 26 may end this process if no collision is detected after a certain time has elapsed since the start of this process.

[0061] In step ST22, the occupant protection ECU 30 executes occupant protection processing based on the collision detection information from the detection ECU 26. The occupant protection ECU 30 selects and activates the seat belt device and the airbag device based on the magnitude, direction, and input part of the impact, and the riding position of the occupant. This makes it possible to protect the occupant from the impact. In this embodiment, the passenger protection control is executed after the collision is detected in step ST21. However, the passenger protection control may be executed at the pre-control stage in step ST2 after the collision is predicted. Passenger protection control may be performed at the stage of collision prediction before a collision is detected.

[0062] In step ST23, the occupant protection ECU 30 collects accident information. The occupant protection ECU 30 acquires image data of the outside of the vehicle captured by the stereo camera 53 in addition to accident information of the AACN standard such as the position of the vehicle.

[0063] In step ST54, the occupant protection ECU 30 or the detection ECU 26 generates information on the position or change in position of the vehicle. The occupant protection ECU 30 or the detection ECU 26 generates the position of the vehicle during a predetermined period from before the accident to after the accident, or the direction and amount of change in the position of the vehicle, based on, for example, the position of the GNSS receiver 56 and the detection value of the three-axis acceleration sensor 52. Here, the information on the position or change in position of the vehicle may be based on absolute values ​​such as latitude and longitude, or may be based on values ​​based on a predetermined position of the vehicle before the accident.

[0064] In step ST55, the occupant protection ECU 30 or the detection ECU 26 generates information on the position or change in position of the other party involved in the accident with the vehicle. The occupant protection ECU 30 or the detection ECU 26 generates the other party's position during a predetermined period from before the accident to after the accident, or the direction and amount of change in the other party's position, from images captured by the stereo camera 53, for example. The other party's position and change in position may be absolute values ​​based on latitude and longitude, etc., determined from images captured by the stereo camera 53, or may be relative values ​​based on the position or change in position of the vehicle.

[0065] In step ST24, the external communication ECU 27 transmits the emergency information collected or generated by the above-mentioned processing to the server device 2 of the emergency call system 1. The emergency information in this case includes accident information according to the AACN standard, image data of the outside of the vehicle captured by the stereo camera 53, information on the position or change in position of the vehicle, and information on the position or change in position of the other party.

[0066] When the server CPU 93 of the server device 2 receives new emergency information from the automobile 10, it executes the link processing of FIG. 6 as the processing from step ST25 to step ST26 of FIG. In the collation process and the match determination in step ST5 in FIG. 6, the server CPU 93 compares the position or change in position of the automobile 10 or the other party in the accident surrounding information of the peripheral terminal with the information on the position or change in position of the own vehicle and the other party involved in the accident contained in the emergency information to determine whether they match. If the position or change in position of the automobile 10 or the other party in the accident surrounding information of the acquired peripheral terminal matches so as to be correlated with the position information or change in position information acquired from the automobile 10 involved in the accident, the server CPU 93 determines that the accident surrounding information is information about the automobile 10's accident. If there is no match, the accident surrounding information is not determined to be information about the automobile 10's accident. In this case, the information of the automobiles 10 may be compared, the information of the pedestrians may be compared, or the information of the automobile 10 and the pedestrian may be compared. Even when the information of the automobile 10 and the pedestrian is compared, it is considered that there is a certain correlation because the position of the pedestrian changes in the direction of the change in position of the automobile 10.

[0067] FIG. 10 is an explanatory diagram of a collation decision for an image as accident surroundings information by a peripheral terminal when the accident information of FIG. 9 is used in the link processing of the server device 2 of FIG.

[0068] FIG. 10(A) is an image of the automobile 10 and the pedestrian involved in the accident captured by the mobile terminal 9 near the accident site. In this case, the image as the accident surrounding information is added with the image capturing position and image capturing time that are substantially the same as those of the accident site. Therefore, in step ST3 or step ST6, the server CPU 93 determines that the position and time of the image as the accident surrounding information match the position and accident at the accident site included in the emergency information acquired from the automobile 10 involved in the accident. Also, in the image as the accident surrounding information, the pedestrian involved in the accident is lying in a position in the left front direction of the automobile 10 involved in the accident. The server CPU 93 compares the position or position change of the pedestrian involved in the accident based on the automobile 10 in the image of FIG. 10(A) with the position or position change of the pedestrian involved in the accident included in the emergency information acquired from the automobile 10 involved in the accident. Then, since these match in the image of FIG. 10(A), the server CPU 93 determines that the image of FIG. 10(A) is image data of the accident surrounding information, and generates link information.

[0069] FIG. 10(B) is an image of the automobile 10 involved in the accident and a pedestrian who was not involved in the accident captured by the mobile terminal 9 near the accident site. In this case, the image as the accident surrounding information is added with the image capturing position and image capturing time that are almost the same as those of the accident site. Therefore, in step ST3 or step ST6, the server CPU 93 determines that the position and time of the image as the accident surrounding information match the position and accident at the accident site included in the emergency information acquired from the automobile 10 involved in the accident. Also, in the image as the accident surrounding information, the pedestrian who was not involved in the accident is standing in a position in the right front direction of the automobile 10 involved in the accident. The server CPU 93 compares the position or position change of the pedestrian who was not involved in the accident based on the automobile 10 in the image of FIG. 10(B) with the position or position change of the pedestrian who was involved in the accident included in the emergency information acquired from the automobile 10 involved in the accident. Then, since these do not match in the image of FIG. 10(B), the server CPU 93 does not determine that the image of FIG. 10(B) is image data of the accident surrounding information. In this case, the server CPU 93 does not generate link information for the image in FIG.

[0070] In this way, the server CPU 93 judges the position or change in position of the own vehicle or the other pedestrian in the image acquired from the SNS server 12 of the cloud service by comparing it with the information on the position or change in position of the own vehicle or the other pedestrian at the accident scene acquired from the automobile 10 involved in the accident. The server CPU 93 can make a judgment based on the image of the dark outside of the automobile 10 involved in the accident, in which the headlights may be damaged, without performing a process to obtain information on the position or change in position of the own vehicle or the other pedestrian in the image. In a dark image, it may not be easy to clearly extract the color or shape of the automobile 10 or pedestrian in the image.

[0071] As described above, in this embodiment, the automobile 10 generates information on the position or the position change of the automobile 10 or the other party before and after the accident, and transmits it to the server device 2. Then, the server device 2 determines whether the information is about the accident of the automobile 10 based on the correlation between the position or the position change of the automobile 10 or the other party in the accident surrounding information of the surrounding terminal acquired by the acquisition unit and the position information or the position change information acquired from the automobile 10 involved in the accident. This can reduce the processing load of the server device 2. In addition, the server device 2 can determine the suitability of the acquired accident surrounding information of the surrounding terminal with a high degree of certainty based on the position information or the position change information with a high degree of certainty collected at each accident site. It is possible to increase the selection accuracy of the accident surrounding information while reducing the processing load of the server device 2. Moreover, the server device 2 can compare images captured by the surrounding terminals as accident surrounding information without extracting the positions of the automobile 10 and pedestrians from images captured outside the automobile 10 that has had an accident in a dark place such as at night or in a tunnel. Images captured by the surrounding terminals are likely to have been captured with a bright subject using a flash, even if they are captured at night or in a dark place such as a tunnel, because the surrounding terminals themselves are not broken. Extraction of the positions of the automobile 10 and pedestrians from images in which the subject is bright is easy. Furthermore, similar to the embodiment described above, in a situation where an accident involving multiple automobiles 10 and multiple pedestrians has occurred as shown in FIG. 8, the server device 2 can determine that a first automobile 10A has collided with a first pedestrian 120A and that a second automobile 10B has collided with a second pedestrian 120B.

[0072] [Third embodiment] Next, an emergency call system 1 according to a third embodiment of the present invention will be described. In the above-described embodiment, the server device 2 executes link processing for information surrounding an accident. In this embodiment, the automobile 10 executes link processing for information surrounding an accident. In the following description, differences from the above-described embodiment will be mainly described. Components similar to those in the above-described embodiment are given the same reference numerals, and descriptions thereof will be omitted.

[0073] FIG. 11 is a flowchart of link processing for accident surrounding information by the control system 20 of the automobile 10 according to the third embodiment of the present invention. When the occupant protection ECU 30 of the control system 20 of the automobile 10 detects a collision caused by an accident of the host vehicle, the occupant protection ECU 30 executes the process of generating accident information shown in FIG.

[0074] In step ST21, the detection ECU 26 judges whether or not a collision due to an accident of the host vehicle has been detected. For example, the three-axis acceleration sensor 52 can detect the acceleration of a large impact that would not occur during normal driving. When the detection ECU 26 judges that a collision due to an accident has not been detected based on the detection value of the three-axis acceleration sensor 52, the detection ECU 26 repeats this process. When the detection ECU 26 judges that a collision due to an accident of the host vehicle has been detected, the detection ECU 26 transmits collision detection information to the occupant protection ECU 30 and advances the process to step ST22.

[0075] In step ST22, the occupant protection ECU 30 executes occupant protection processing based on the collision detection information. The occupant protection ECU 30 selects and activates the seat belt device and the airbag device based on the magnitude, direction, and input part of the impact, and the riding position of the occupant. This makes it possible to protect the occupant from the impact.

[0076] In step ST23, the occupant protection ECU 30 collects accident information. The occupant protection ECU 30 acquires image data of the outside of the vehicle captured by the stereo camera 53 in addition to accident information of the AACN standard such as the position of the vehicle.

[0077] In step ST24, the occupant protection ECU 30 immediately transmits the emergency accident information generated by the above-mentioned process to the server device 2 of the emergency notification system 1.

[0078] In step ST65, the internal communication ECU 28 searches for peripheral terminals present around the vehicle. The internal communication ECU 28 searches for the peripheral mobile terminals 9, for example, by short-range communication using the internal communication device 71. This allows the internal communication ECU 28 to search for the mobile terminals 9 of pedestrians outside the vehicle whose authentication information has not been registered.

[0079] In step ST66, the internal communication ECU 28 connects to the searched peripheral terminal. For example, the internal communication ECU 28 uses the internal communication device 71 to connect to the mobile terminal 9 of a pedestrian outside the vehicle whose authentication information has not been registered. At this time, the internal communication ECU 28 may connect to the searched peripheral terminal after obtaining approval from the terminal.

[0080] In step ST67, the internal communication ECU 28 acquires accident surroundings information from the connected peripheral terminal. If the peripheral terminal captures an image of the accident scene at the site, the image data is acquired as the accident surroundings information.

[0081] In step ST68, the occupant protection ECU 30 or the detection ECU 26 compares the acquired accident surrounding information, such as the image data of the accident scene, with various information possessed by the vehicle. For example, the occupant protection ECU 30 or the detection ECU 26 extracts an image component of the automobile 10 from the image of the image data as the accident surrounding information, and compares it with attribute information of the vehicle, such as the vehicle type and color, possessed by the vehicle. In addition, for example, the occupant protection ECU 30 or the detection ECU 26 may compare the image component of the automobile 10 contained in the image of the image data as the accident surrounding information with the image component of the vehicle in the image of the outside of the vehicle captured by the vehicle. In addition, the occupant protection ECU 30 or the detection ECU 26 may compare the image component of a person, such as a pedestrian, contained in the image of the image data as the accident surrounding information with the image component of a person, such as a pedestrian, in the image of the outside of the vehicle captured by the vehicle. Furthermore, the occupant protection ECU 30 or the detection ECU 26 may verify whether the image capture location and image capture time included in the accident surroundings information are the same as the accident occurrence location and accident occurrence time in the emergency information possessed by the vehicle itself.

[0082] In step ST69, the occupant protection ECU 30 or the detection ECU 26 judges whether the collated accident surrounding information matches various information possessed by the vehicle. If all collation elements related to the collation judgment, such as the model and color of the automobile 10, match, the occupant protection ECU 30 or the detection ECU 26 judges that the accident surrounding information matches the vehicle information, and proceeds to step ST70. If any element related to the collation judgment does not match, the occupant protection ECU 30 or the detection ECU 26 judges that the accident surrounding information does not match the vehicle information, skips step ST70, and proceeds to step ST71.

[0083] In step ST70, the occupant protection ECU 30 or the detection ECU 26 generates link information that associates the matched accident-periphery information with emergency information of the accident to be transmitted to the server device 2. The link information may be, for example, information that associates a file name for the matched accident-periphery information with a management ID to be added to the emergency information. This allows the occupant protection ECU 30 to generate link information that can be used in the server device 2.

[0084] In step ST71, the occupant protection ECU 30 or the detection ECU 26 judges whether to continue searching for peripheral terminals. The process of searching for peripheral terminals and connecting to them in order to obtain accident surrounding information takes time. On the other hand, the call center staff needs to request an emergency dispatch as soon as possible after the server device 2 receives the emergency information. For example, if the elapsed time since the emergency information was transmitted does not exceed a predetermined threshold, the occupant protection ECU 30 or the detection ECU 26 judges to continue searching for peripheral terminals and returns the process to step ST65. As a result, the occupant protection ECU 30 or the detection ECU 26 executes a search for peripheral terminals to obtain the next accident surrounding information. If the elapsed time since the emergency information was transmitted exceeds a predetermined threshold, the occupant protection ECU 30 or the detection ECU 26 ends the search for peripheral terminals and advances the process to step ST72.

[0085] In step ST72, the external communication ECU 27 transmits to the server device 2 of the emergency call system 1 the accident surroundings information and link information of the surrounding terminals obtained by the above-mentioned process.

[0086] The server CPU 93 of the server device 2 receives the accident surroundings information and link information of the peripheral terminals from the accidented automobile 10 while receiving new emergency information and executing the link processing of Fig. 6. The server CPU 93 records the accident surroundings information and link information of the peripheral terminals received from the accidented automobile 10 in the server memory 92 in the same manner as the emergency information. Then, when link information is selected in step ST10 of Figure 6, in step ST11, the server CPU 93 uses the link information received from the automobile 10 involved in the accident to display a screen of accident surrounding information of the peripheral terminal received from the automobile 10 involved in the accident on the server monitor 95.

[0087] FIG. 12 is an explanatory diagram of a comparison judgment of an image serving as accident surroundings information by a peripheral terminal, by the automobile 10 of FIG. Fig. 12(A) is an image as accident surroundings information acquired from a peripheral terminal by the automobile 10. The peripheral terminal records the image of Fig. 12(A) by capturing an image of the accident scene. 12(B) is an image of the outside of the vehicle captured by the vehicle 10. The vehicle 10 captures an image of the outside of the vehicle with the stereo camera 53, thereby recording the image of FIG.

[0088] When the passenger protection ECU 30 of the automobile 10 involved in the accident acquires an image as the accident surrounding information in FIG. 12(A) from a peripheral terminal, the passenger protection ECU 30 analyzes the image and extracts image components of the automobile 10 and image components of people such as pedestrians. The passenger protection ECU 30 compares the extracted image components of the automobile 10 with attribute information such as the vehicle model and color of the own vehicle. The passenger protection ECU 30 may compare with the stereo camera 53 in FIG. 12(B). However, at night when there is no lighting, the color of the own vehicle may not be reflected correctly in the image captured by the stereo camera 53. For this reason, it is preferable to compare with attribute information such as the vehicle model and color that the own vehicle possesses as information as much as possible. The passenger protection ECU 30 obtains information on the position or change in position of the pedestrian, the other party in the collision, obtained from the image captured by the stereo camera 53 or the own vehicle information such as the input part of the collision, and compares it with the image components of people such as pedestrians. The occupant protection ECU 30 may obtain information on the direction of the relative position of the other pedestrian based on the position of the vehicle itself, for example, based on the vehicle information, and compare it with the direction of the image capturing position of the person based on the image capturing position of the vehicle 10 on the peripheral terminal. If the comparisons for all of these elements match, the occupant protection ECU 30 determines that the image acquired from the peripheral terminal is related to the vehicle's own accident, and generates link information. The occupant protection ECU 30 transmits the image acquired from the peripheral terminal to the server device 2 together with the generated link information. In this way, the vehicle 10 can accurately determine a match for the accident surroundings information acquired from the peripheral terminal by using the information possessed by the vehicle itself.

[0089] As described above, in this embodiment, in the emergency notification system 1 capable of transmitting emergency information related to an accident from an automobile 10 involved in an accident to a server device 2, a control ECU such as the passenger protection ECU 30 of the automobile 10 performs an acquisition process and a link process of the accident surrounding information as an accident surrounding information link device. For example, the control ECU such as the passenger protection ECU 30 pairs the communication terminal 70 in the automobile 10 involved in the accident with a peripheral terminal at the accident site, receives and collects accident surrounding information such as captured images of the accident site from the peripheral terminal, and compares it with information owned by the automobile. Then, when it is determined that the information is about an accident of the automobile, the control ECU such as the passenger protection ECU 30 generates link information that associates the determined accident surrounding information of the peripheral terminal with the emergency information so that it can be used in the server device 2, and transmits it to the server device 2 together with the acquired accident surrounding information. As a result, the server device 2 can use the accident surrounding information of the peripheral terminal about the accident in association with the emergency information of the automobile 10 involved in the accident without performing a process of generating the accident surrounding information link information by itself. Call center staff and the like can grasp the situation based on the accident periphery information, which cannot be fully grasped only from the emergency information from the automobile 10 involved in the accident. Based on the rich information supplemented by the accident periphery information, the call center staff and the like can make a detailed and more reliable judgment on the situation at the accident site and dispatch the necessary emergency personnel to the site. Based on the rich information supplemented by the accident periphery information, the emergency personnel can also grasp the situation of not only the passengers but also pedestrians, etc., and can dispatch to the site when they are able to respond to the situation. Furthermore, similar to the embodiment described above, in a situation where an accident involving multiple automobiles 10 and multiple pedestrians has occurred as shown in FIG. 8, the server device 2 can determine that a first automobile 10A has collided with a first pedestrian 120A and that a second automobile 10B has collided with a second pedestrian 120B.

[0090] The above-described embodiment is an example of a preferred embodiment of the present invention, but the present invention is not limited to this, and various modifications and changes are possible without departing from the gist of the invention.

[0091] In the above-described embodiment, the automobile 10 has a plurality of separate ECUs, but some or all of these may be integrated into a single ECU.

[0092] For example, in the above-described embodiment, the server device 2 or the automobile 10 involved in the accident executes the process of generating link information based on the detection of the accident and the reception of emergency information about the accident based on the detection. In addition, for example, the server device 2 or the vehicle 10 involved in the accident may execute a process of generating link information based on the operation of the server device 2 by a call center staff member who determines that the circumstances of the accident may not be fully understood from the emergency information alone.

[0093] In the embodiment described above, the occupant protection ECU 30 in the automobile 10 generates the link information or executes the process for generating the link information. Alternatively, for example, a control ECU other than the occupant protection ECU 30 in the automobile 10 may execute the process of generating link information or the process therefor. [Explanation of symbols]

[0094] 1...emergency call system, 2...server device, 3...client terminal, 4...automatic call device, 5...wireless communication network, 6...base station, 7...communication network, 9...mobile terminal (peripheral terminal), 10...automobile (vehicle), 11...ambulance, 12...SNS server, 20...control system, 21...driving ECU, 22...steering ECU, 23...braking ECU, 24...driving control ECU, 25...driving operation ECU, 26...detection ECU, 27...external communication ECU, 28...internal Communication ECU, 29...UI operation ECU, 30...Occupant protection ECU (peripheral information link device for vehicle accidents), 36...Vehicle network, 37...Bus cable, 38...Central gateway, 41...Display device, 42...Operation device, 51...Speed ​​sensor, 52...3-axis acceleration sensor, 53...Stereo camera, 54...In-vehicle camera, 55...Microphone, 56...GNSS receiver, 60...External communication terminal, 61...External communication device, 70... Internal communication terminal, 71...internal communication device, 80...occupant protection device, 81...driver's side seat belt device, 82...passenger's side seat belt device, 83...driver's side front airbag device, 84...driver's side curtain airbag device, 85...passenger's side front airbag device, 86...passenger's side curtain airbag device, 87...occupant protection memory, 91...server communication device, 92...server memory, 93...server CPU (vehicle accident peripheral information link device), 94...server GNSS receiver, 95...server monitor, 96...server call device, 97...server bus, 101...client communication device, 102...client memory, 103...client CPU, 104...client notification device, 105...client GNSS receiver, 106...client monitor, 107...client call device, 108...client bus, 110...GNSS satellite

Claims

1. A vehicle accident surrounding information link device provided in an emergency notification system capable of transmitting emergency information related to an accident from a vehicle involved in an accident to a server device, comprising: The server device includes: a setting unit that sets search conditions for searching a cloud service based on the acquired emergency accident information when the emergency accident information is received from the vehicle; An acquisition unit that searches the cloud service according to the set search conditions to acquire accident-periphery information; a determination unit that compares the acquired accident surrounding information with emergency accident information, and determines that the acquired accident surrounding information is information about an accident involving the vehicle if the information matches; a generating unit that generates link information that associates the accident surrounding information, which is determined by the determining unit to be information about the vehicle accident, with the emergency information; an output unit that uses the link information generated by the generation unit to output the accident-periphery information in association with the emergency information transmitted by the vehicle to the server device; A vehicle accident surrounding information link device having the above-mentioned configuration.

2. The setting unit sets, as the search conditions, a search area including a location of the accident site and a search time period including a time when the accident occurred.

2. The vehicle accident peripheral information link device according to claim 1.

3. The accident surroundings information is image data, The determination unit is A comparison is made between the image components of the vehicle in the image data as the accident surroundings information and attribute information such as the type and color of the vehicle involved in the accident included in the emergency information; A comparison is made between an image component of a vehicle included in the image of the image data as the accident surrounding information and an image component of the vehicle involved in the accident included in the emergency information, or comparing image components of people included in the image of the image data as the accident surroundings information with image components of people included in the image of the vehicle involved in the accident included in the emergency information; If the collation contents match, it is determined that the acquired image data is information about an accident involving the vehicle.

3. A vehicle accident peripheral information link device according to claim 1 or 2.

4. the vehicle involved in the accident generates information on a change in position of the vehicle itself or the other vehicle and transmits the information to the server device; The determination unit is When a position change of the vehicle or the other party in the image data acquired by the acquisition unit is correlated with information on the position change acquired from the vehicle involved in the accident, the information is determined to be information on an accident involving the vehicle.

4. A vehicle accident peripheral information link device according to claim 3.

Citation Information

Patent Citations

  • On-vehicle emergency aviso system and terminal

    JP2001216588A

  • Emergency informing equipment

    JP2001357480A

  • Information processing device, information processing method, and program

    JP2016118904A

  • Accident information recorder and accident information collection server

    JP2019185453A

  • Method and system for transmitting an emergency call

    US20110124311A1