System and method for sharing accident information for a vehicle

Abstract

A system for sharing accident information related to a vehicle and a method thereof can include an accident vehicle collecting accident information and requesting an accident image including the accident information, and a server determining whether the accident image and the request for the accident image are received from the accident vehicle, identifying a reporting vehicle capable of providing a reporting image corresponding to the accident information and the accident image when the accident information and the request for the accident image are received, and requesting the reporting vehicle to transmit the reporting image acquired by the reporting vehicle to the accident vehicle. When a vehicle accident occurs, by sharing surrounding images with vehicles driving around the accident vehicle, the cause of the accident can be more accurately determined.

Description

[0001] Cross-citation of related applications

[0002] This application claims priority to Korean Patent Application No. 10-2020-0114825, filed on September 8, 2020, the entire contents of which are incorporated herein by reference for all purposes. Technical Field

[0003] This invention relates to systems and methods for sharing accident information. Background Technology

[0004] In general, when a vehicle accident occurs, surrounding images obtained from cameras mounted on the vehicle are used to determine the cause of the accident. In particular, to determine the cause of the accident more accurately, not only surrounding images of the vehicle involved in the accident, but also surrounding images of vehicles traveling around the vehicle involved in the accident can be used.

[0005] However, it is difficult for occupants of an accident vehicle to request surrounding images because they cannot remember the vehicles that were driving around the accident vehicle at the time of the accident. Therefore, there is a need to develop technology that can share surrounding images with vehicles driving around the accident vehicle at the time of the accident.

[0006] The information disclosed in the background section of this invention is intended only to enhance the understanding of the general background of this invention and should not be construed as an admission that such information constitutes prior art known to those skilled in the art or as any form of advice. Summary of the Invention

[0007] Various aspects of the present invention relate to providing a system and method for sharing accident information, the system being able to share surrounding images with vehicles traveling around the accident vehicle when a vehicle accident occurs.

[0008] The technical problems to be solved by the inventive concept are not limited to the foregoing problems, and those skilled in the art to which the various exemplary embodiments of the present invention pertain will clearly understand from the following description any other technical problems not mentioned herein.

[0009] According to various aspects of the present invention, a system for sharing vehicle-related accident information may include an accident vehicle that collects accident information and requests accident images including the accident information, and a server that determines whether an accident image and a request for the accident image have been received from the accident vehicle, and when the accident information and the request for the accident image are received, identifies a reporting vehicle capable of providing a report image corresponding to the accident information and the accident image, and requests the reporting vehicle to send the report image obtained by the reporting vehicle to the accident vehicle.

[0010] The accident vehicle can collect accident information including location information related to a point where the accident occurs, a search radius based on the point where the accident occurs, information related to a road where the accident occurs, adjacent road information, and direction information.

[0011] The accident vehicle is configured to extract a search factor for acquiring information related to a report image based on the accident information.

[0012] The search factor can include a license plate number, a vehicle type, a vehicle color, an accident occurrence location, an accident occurrence time, and direction information.

[0013] When the report image is provided from the report vehicle, the server can store a history of providing the report image.

[0014] The server can determine whether information related to the report vehicle is identified based on the search factor or the history of providing the report image.

[0015] When the information related to the report vehicle is identified, the server can transmit information related to the accident vehicle to the report vehicle.

[0016] When the information related to the report vehicle is not identified, the server can request a report image corresponding to the accident image from a vehicle that subscribes to an accident information sharing service.

[0017] The server can store information related to the report image provided from the report vehicle, and can determine whether an accident vehicle that requests the accident image exists even when the accident information and the request for the accident image are not received from the accident vehicle.

[0018] When the accident vehicle that requests the accident image exists, the server can identify information related to the accident vehicle, and transmit the information related to the accident vehicle to the report vehicle.

[0019] When any of the accident vehicles that request the accident image does not exist, the server can notify the report vehicle that any of the vehicles that request the accident image does not exist, and request the report vehicle to store the accident image.

[0020] When the information related to the accident vehicle is received from the server, the report vehicle can transmit the report image to the accident vehicle or a user portable terminal of the accident vehicle.

[0021] The report vehicle can extract the search factor when the report image is acquired.

[0022] According to various aspects of the present application, a method of sharing accident information can include collecting accident information by an accident vehicle and requesting an accident image including the accident information from a server, determining whether the accident information and the request for the accident image are received, and when the accident information and the request for the accident image are received, identifying a reporting vehicle capable of providing a reporting image corresponding to the accident information and the accident image, and requesting the reporting vehicle to transmit the reporting image obtained by the reporting vehicle to the accident vehicle.

[0023] The method can further include transmitting information about the accident vehicle to the reporting vehicle when information about the reporting vehicle is identified.

[0024] The method can further include requesting a reporting image corresponding to the accident image from a vehicle subscribing to an accident information sharing service through the server when information about the reporting vehicle is not identified.

[0025] The method can further include storing information about the reporting image provided from the reporting vehicle through the server, and determining whether the accident vehicle requesting the accident image exists even when the accident information and the request for the accident image are not received from the accident vehicle.

[0026] When the accident vehicle requesting the accident image exists, the server can identify information about the accident vehicle, and transmit the information about the accident vehicle to the reporting vehicle.

[0027] The method can further include, when any vehicle requesting the accident image does not exist, notifying the reporting vehicle that any vehicle requesting the accident image does not exist through the server, and requesting the reporting vehicle to store the reporting image.

[0028] The method can further include, when the information about the accident vehicle is received from the server, transmitting the reporting image to the accident vehicle or a user portable terminal of the accident vehicle.

[0029] The method and apparatus of the present application have other features and advantages which will be apparent from or that will be more readily understood by those skilled in the art upon a reading of the following detailed description in conjunction with the accompanying drawings, which are incorporated in and form a part of the present application. The drawings, which are not necessarily to scale, illustrate various embodiments of the present application and are as follows: BRIEF DESCRIPTION OF DRAWINGS

[0030] Figure 1 is a block diagram illustrating a configuration of a system for sharing accident information according to various exemplary embodiments of the present application;

[0031] Figure 2 is a block diagram illustrating a configuration of an accident vehicle according to various exemplary embodiments of the present application;

[0032] Figure 3 and Figure 4is a diagram schematically showing collection of accident information according to various exemplary embodiments of the present application;

[0033] Figure 5 is a block diagram showing a configuration of a reporting vehicle according to various exemplary embodiments of the present application;

[0034] Figure 6 is a block diagram showing a configuration of a server according to various exemplary embodiments of the present application;

[0035] Figure 7 is a flowchart showing a method of collecting accident information related to an accident vehicle according to various exemplary embodiments of the present application;

[0036] Figure 8 is a flowchart showing a method of sharing accident information according to various exemplary embodiments of the present application;

[0037] Figure 9 is a flowchart showing a method of sharing accident information according to various exemplary embodiments of the present application;

[0038] Figure 10 is a flowchart showing a method of sharing accident information according to various exemplary embodiments of the present application; and

[0039] Figure 11 is a diagram showing a computing system for performing a method according to various exemplary embodiments of the present application.

[0040] It is to be understood that the figures are not necessarily to scale, presenting a somewhat simplified representation of various features illustrative of the basic principles of the application. The specific design features of this application as disclosed herein, including, for example, specific dimensions, orientations, locations, and shapes, will be determined in part by the particular intended application and use environment.

[0041] In the drawings, like reference numerals refer to like parts throughout the various views thereof. DETAILED DESCRIPTION

[0042] Reference will now be made in detail to various embodiments of the application, examples of which are illustrated in the accompanying drawings and described below. While the application will be described in conjunction with the exemplary embodiments, it will be understood that the description is not intended to limit the application to those exemplary embodiments. On the contrary, the description is intended to cover all alternatives, modifications, equivalents and other embodiments that can be included within the spirit and scope of the application as defined by the appended claims.

[0043] Hereinafter, various exemplary embodiments of the present application will be described in detail with reference to exemplary drawings. In adding reference numerals to components in each drawing, it should be noted that the same or equivalent components are denoted by the same reference numerals even though they are shown on other drawings. Also, detailed descriptions of known features or functions will be omitted in order not to unnecessarily obscure the principle of the present application.

[0044] In describing components of the exemplary embodiments according to various exemplary embodiments of the present application, terms such as first, second, "A", "B", (a), (b), etc. can be used. These terms are merely intended to distinguish one component from another component, and the terms do not limit the nature, sequence, or order of the components constituting the components. Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which various exemplary embodiments of the present application belong. Terms defined in commonly used dictionaries should be interpreted as having a same meaning as the contextual meaning in the relevant art, and should not be interpreted in an idealized or overly formal sense, unless otherwise defined herein.

[0045] Figure 1 is a block diagram illustrating a configuration of a system for sharing accident information according to various exemplary embodiments of the present application.

[0046] As Figure 1 indicated, a system 100 for sharing accident information according to various exemplary embodiments of the present application can include an accident vehicle 110, a reporting vehicle 120, a server 130, and a portable terminal 140.

[0047] The accident vehicle 110 can determine whether an accident has occurred based on information obtained from a camera and a sensor. When it is determined that an accident has occurred, the accident vehicle 110 can collect accident information and request an accident image from the server 130 to determine a cause of the accident. Also, when there is a reporting image corresponding to the accident image, the accident vehicle 110 can receive the reporting image from the reporting vehicle 120. The accident vehicle 110 can determine the cause of the accident based on the reporting image received from the reporting vehicle 120. In the current case, the accident image can refer to an image obtained by photographing a collision scene including the accident vehicle, and the accident information corresponds to information related to the accident image. The reporting image can correspond to the accident image, and can represent an image of a collision scene photographed by a vehicle traveling around the accident vehicle.

[0048] According to various exemplary embodiments of the present application, when the accident vehicle 110 requests the accident image from the server 130 and receives the reporting image from the reporting vehicle 120, the accident vehicle 110 can be a vehicle that subscribes to an accident information sharing service.

[0049] The reporting vehicle 120 can receive a request for providing a reporting image corresponding to the accident image from the server 130, and can transmit the reporting image corresponding to the accident image to the accident vehicle 110 or the user portable terminal 140 of the accident vehicle 110. The reporting vehicle 120 can include a vehicle that travels within a designated radius from the accident vehicle 110 at the time of the accident. According to various exemplary embodiments of the present application, when the reporting vehicle 120 is requested by the server 130 to provide a reporting image or to transmit a reporting image to the accident vehicle 110, the reporting vehicle 120 can be a vehicle that subscribes to an accident information sharing service.

[0050] When the server 130 determines whether a request for an accident image has been received from the accident vehicle 110 and receives a request for accident information and an accident image, the server 130 can identify a reporting vehicle 120 capable of providing a reporting image corresponding to the accident image, and request the reporting vehicle 120 to transmit a reporting image obtained by the reporting vehicle 120 to the accident vehicle 110.

[0051] The portable terminal 140 can include a portable electronic device, and according to various exemplary embodiments of the present application, the portable terminal 140 can include a smartphone, a smart tablet, a laptop, etc. When the portable terminal 140 receives a reporting image from the reporting vehicle 120, the portable terminal 140 can be set to share the reporting image with a terminal registered as an emergency contact.

[0052] Figure 2 is a block diagram illustrating a configuration of an accident vehicle according to various exemplary embodiments of the present application.

[0053] As Figure 2 indicated, the accident vehicle 110 according to various exemplary embodiments of the present application can include a sensor 111, a navigation device 112, a camera 113, a communication device 114, an input device 115, a storage device 116, and a controller 117.

[0054] The sensor 111 can acquire driving information and surrounding information related to a vehicle. The sensor 111 can include a vehicle speed sensor, a steering angle sensor, a yaw rate sensor, a distance sensor, an image sensor, an infrared sensor, a gyro sensor, an impact detection sensor, an airbag sensor, etc.

[0055] The navigation device 112 can include a global positioning system (GPS) receiving device to receive a current position of a vehicle, and provide map image information related to a specific area based on the current position of the vehicle. In addition, the navigation device 112 can provide information related to a road on which the vehicle is located and information related to a regulated speed set for the road.

[0056] The camera 113 can obtain images of the surroundings of the vehicle. According to various exemplary embodiments of the present application, the camera 133 can include front and rear cameras capable of acquiring front and rear images of the vehicle and left and right cameras capable of capturing left and right images of the vehicle.

[0057] The communication device 114 can communicate with the reporting vehicle 120 and the server 130. The communication device 114 can communicate in various wireless communication schemes, such as Wi-Fi, WiBro, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System (UMTS), Time Division Multiple Access (TDMA), Long Term Evolution (LTE), etc.

[0058] The input device 115 can receive an input signal corresponding to a user's manipulation, operation, or voice. According to various exemplary embodiments of the present application, when an accident occurs, the input device 115 can input accident information by a user. To this end, the input device 115 can be implemented by at least one of a jog wheel, a button, a knob, a touch screen, a touch pad, a joystick, a trackball, etc. manipulated by a user, a motion sensor for detecting a motion of an occupant, a voice recognition sensor, or a combination thereof.

[0059] The storage device 116 can store at least one algorithm that performs an operation or execution of various commands for an operation of the accident vehicle. In addition, the storage device 116 can store a report image received from the reporting vehicle 120. The storage device 116 can include at least one storage medium of a flash memory, a hard disk, a memory card, a Read Only Memory (ROM), a Random Access Memory (RAM), and an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, and an optical disk.

[0060] According to various exemplary embodiments of the present application, the controller 117 can be implemented with various processing devices such as a microprocessor including a semiconductor chip capable of performing an operation or execution of various commands, and control an operation of the accident vehicle.

[0061] The controller 117 can determine whether an accident has occurred in the accident vehicle 110 based on information obtained from the sensor 111 and the camera 113. When it is determined that an accident has occurred, the controller 117 can collect accident information. According to various exemplary embodiments of the present application, when an airbag is deployed and it is determined that an accident has occurred, the controller 117 can automatically collect accident information. When it is not possible to determine whether an accident has occurred, the controller 117 can allow a user to input accident information.

[0062] The controller 117 can collect accident information based on information about a portion where a collision has occurred, location information about an accident location, a search radius based on an accident location, information about a road where an accident has occurred, surrounding road information, and orientation information.

[0063] First, the controller 117 can determine a vehicle collision location. The controller 117 can determine an accident occurrence location from an impact detection sensor. According to various exemplary embodiments of the present application, the controller 117 can determine an accident occurrence location of a vehicle by dividing the vehicle into a front center, a front left, a front right, a rear center, a rear left, a rear right, a left direction, and a right direction of the vehicle. In addition, the controller 117 can acquire a front image and a rear image, acquire license plate information about a nearby vehicle based on the front image and the rear image, and transmit the acquired information to the server 130.

[0064] In addition, the controller 117 can collect location information (GPS information) of an accident occurrence location. The controller 117 can collect orientation information. In the current case, the orientation information can indicate driving direction information about a vehicle, and can be divided into east, west, south, north, southwest, southeast, northeast, and northwest based on an accident occurrence location.

[0065] The controller 117 can collect road information about an accident location based on map data of the navigation device 112. According to various exemplary embodiments of the present application, the controller 117 can collect the number of roads adjacent to a road at an accident occurrence location, information about a type of a road, and a regulated speed set for a road.

[0066] The controller 117 can determine in which direction to request an accident image according to a road type. According to various exemplary embodiments of the present application, the controller 117 can determine a direction identical to a driving direction of an accident vehicle, a direction opposite to the driving direction of the accident vehicle, and a driving direction of a road entering an accident site as its search direction. When the accident site is a circular intersection, the controller 117 can request an accident image of a vehicle near the accident site without determining its search direction. In the current case, the controller 117 can exclude a search direction in which a collision location is not exposed from the determined search direction.

[0067] The controller 117 can collect attributes of a road at an accident occurrence location based on map data of the navigation device 112. According to various exemplary embodiments of the present application, the controller 117 can calculate an average speed of a road at an accident occurrence location, and set a time of an accident image (a time before and after an accident time point).

[0068] The controller 117 can calculate a search radius based on a regulated speed of a road. The controller 117 can calculate a search radius by using Equation 1 below.

[0069] < Equation 1 >

[0070] Search radius = (((Regulation speed of road * 1000) / 60) / 60) * td(Time of accident image)

[0071] The controller 117 can extract a search factor for acquiring information about a report image based on the accident information collected in the above-described manner. In the current case, the search factor can include a license plate number, a vehicle type, a vehicle color, an accident occurrence location, an accident occurrence time, and orientation information.

[0072] Hereinafter, the operation of collecting accident information will be described in detail with reference to Figure 3 and Figure 4

[0073] Figure 3 and Figure 4 are diagrams schematically illustrating collection of accident information according to various exemplary embodiments of the present application.

[0074] As shown in Figure 3 , when an accident occurs on a two-lane road, the controller 117 can determine road information related to an accident occurrence location as a two-lane road and a regulation speed (e.g., 60 km / h) of the accident occurrence location. Based on orientation information, the controller 117 can determine a driving direction of a vehicle as a west direction, and determine a search direction as a west direction in which a rear image of an accident vehicle is obtained and an east direction in which a front image of the accident vehicle is obtained. In addition, the controller 117 can determine a collision location as a rear center portion based on an impact detection sensor. When a time of an accident image is 5 seconds, the controller 117 can set a search radius to 83.3 m by using Equation 1.

[0075] As described above, the controller 117 can collect accident occurrence location information, a search direction (west, east), and a search radius (83 m) as accident information, and can request an accident image including the accident information from the server 130.

[0076] As shown in Figure 4 ​As illustrated, when an accident occurs in a three-way road, the controller 117 can determine road information related to the accident occurrence location as a three-way road and a regulation speed at the accident occurrence location (e.g., 80 km / h). Based on the heading information, the traveling direction of the vehicle can be determined as a west direction, and the search direction can be determined as a west direction in which a front image of the accident vehicle is obtained, an east direction in which a rear image of the accident vehicle is obtained, and a northwest direction in which a rear left image of the vehicle is obtained. In addition, the controller 117 can determine the collision location as a rear center portion based on the impact detection sensor. When the time of the accident image is 5 seconds, the controller 117 can set the search radius to 111 m by using Equation 1.

[0077] As described above, the controller 117 can collect the accident occurrence location information, the search direction (west, east, northwest), and the search radius (111 m) as accident information, and can request the accident image including the accident information from the server 130.

[0078] Figure 5 is a block diagram illustrating a configuration of a reporting vehicle according to various exemplary embodiments of the present application.

[0079] As Figure 5 illustrated, the reporting vehicle 120 according to various exemplary embodiments of the present application can include a sensor 121, a navigation device 122, a camera 123, a communication device 124, an input device 125, a storage device 126, and a controller 127.

[0080] The sensor 121 can acquire traveling information and surrounding information related to the vehicle. The sensor 121 can include a vehicle speed sensor, a steering angle sensor, a yaw rate sensor, a distance sensor, an image sensor, an infrared sensor, a gyro sensor, an impact detection sensor, an airbag sensor, etc.

[0081] The navigation device 122 can include a global positioning system (GPS) receiving device to receive a current location of the vehicle and provide map image information related to a specific area based on the current location of the vehicle. In addition, the navigation device 122 can provide information related to a road on which the vehicle is located and information related to a regulation speed set for the road.

[0082] The camera 123 can obtain images of the surroundings of the vehicle. According to various exemplary embodiments of the present application, the camera 123 can include front and rear cameras capable of acquiring front and rear images of the vehicle and left and right cameras capable of capturing left and right images of the vehicle.

[0083] The communication device 124 can communicate with the accident vehicle 110 and the server 130. The communication device 124 can communicate in various wireless communication schemes, such as Wi-Fi, WiBro, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunication System (UMTS), Time Division Multiple Access (TDMA), Long Term Evolution (LTE), etc.

[0084] The input device 125 can receive an input signal corresponding to a user's manipulation, operation, or voice. According to various exemplary embodiments of the present application, when an accident occurs, the input device 125 can input accident information by a user.

[0085] The storage device 126 can store at least one algorithm that performs an operation or execution of various commands for reporting the operation of the vehicle. In addition, the storage device 126 can store a report image obtained from the camera.

[0086] According to various exemplary embodiments of the present application, the controller 127 can be implemented with various processing devices such as a microprocessor including a semiconductor chip capable of performing an operation or execution of various commands, and control the operation of the reporting vehicle.

[0087] When the report image is obtained, the controller 127 can extract an image at the time of the accident occurrence, analyze the image, and extract a search factor.

[0088] In addition, the controller 127 can transmit the search factor to the server 130. The controller 127 can receive information about the accident vehicle from the server 130, and transmit the report image to the accident vehicle or a user portable terminal of the accident vehicle.

[0089] When the controller 127 receives a request for a report image corresponding to an accident image from the server 130, the controller 127 can search for a report image corresponding to the accident image among the images stored in the storage device 126. The controller 127 can determine whether the location information at the time of the accident occurrence is located within a designated radius of the reporting vehicle. When it is determined that the direction information related to the accident vehicle matches the direction information related to the reporting vehicle, the controller 127 can determine that the report image corresponding to the accident image has been found, and transmit the found report image to the accident vehicle 110.

[0090] The controller 127 can store the report image as a tag 1 and provide the report image to the server 130 even when the report image corresponding to the accident image is not requested from the server 130. When there is no accident vehicle that requests the report image to be provided to the server 130, the controller 127 can store the report image as a tag 2 allocated by the server 130. This is to provide the report image in the future when the accident vehicle requests the report image.

[0091] Figure 6 is a block diagram illustrating a configuration of a server according to various exemplary embodiments of the present application.

[0092] As Figure 6 indicated, the server 130 can include a communication device 131, a storage device 132, and a controller 133.

[0093] The communication device 131 can communicate with the accident vehicle 110 and the report vehicle 120. The communication device 131 can communicate in various wireless communication schemes such as Wi-Fi, WiBro, Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Universal Mobile Telecommunications System (UMTS), Time Division Multiple Access (TDMA), Long Term Evolution (LTE), etc.

[0094] The storage device 132 can store at least one algorithm that performs operations of various commands for the operation of the server or performs. Further, the storage device 132 can store a history in which the accident image is requested by the accident vehicle 110, and can store a history in which the report image is provided by the report vehicle 120. Further, information on vehicles that subscribe to the accident information sharing service (for example, a vehicle modem, a user phone number, or an app ID), that is, member information of sharing (member vehicle information) can be stored.

[0095] According to various exemplary embodiments of the present application, the controller 133 can be implemented with various processing devices such as a microprocessor including a semiconductor chip capable of performing operations or executions of various commands, and controls the operation of the server.

[0096] According to various exemplary embodiments of the present application, when the controller 133 receives a request for accident information (search factor) and accident images from the accident vehicle 110, the controller 133 can determine whether there is a reporting vehicle capable of providing a report image corresponding to the received information. According to various exemplary embodiments of the present application, when the controller 133 receives license plate information related to a vehicle as a search factor from the accident vehicle 110, the controller 133 can search for a vehicle having the license plate information based on the sharing member information. When a vehicle having the license plate information received from the accident vehicle 110 is searched for, the controller 133 can request a report image from the found vehicle and transmit information related to the accident vehicle. Meanwhile, when there is no license plate information received from the accident vehicle 110, the controller 133 can request a report image from unspecified vehicles that have subscribed to an accident information sharing service based on accident information (e.g., a global positioning system (GPS) location, orientation information, a search direction thereof, a search radius, etc.) received from the accident vehicle 110.

[0097] According to another exemplary embodiment of the present application, when the controller 133 receives a request for accident information (search factor) and accident images from the accident vehicle 110, the controller 133 can determine whether there is a report image matching the requested accident image based on the accident information. The controller 133 can determine whether there is a report image matching the requested accident image based on a history of providing a report image previously stored in the storage 132. When it is determined that there is a report image matching the accident image, the controller 133 can identify information related to a reporting vehicle based on the sharing member information and transmit information related to the accident vehicle to the reporting vehicle whose information is identified. Meanwhile, when it is determined that there is no report image matching the accident image, the controller 133 can store an image request history and request a search for the accident image from vehicles (unspecified vehicles) that have subscribed to an accident information sharing service. When there is no report image matching the accident image, the controller 133 can store an image request history so that the report image is transmitted to the accident vehicle in the future when the reporting vehicle provides the report image.

[0098] According to various exemplary embodiments of the present application, when accident information (report image) input by a user is received from the reporting vehicle 120, the controller 133 can store a history of providing the report image. As an example, the controller 133 can store a reporting vehicle that provides the report image, a search factor, and a tag number generated in the vehicle.

[0099] The controller 133 can determine whether an accident vehicle requests an accident image corresponding to a reported image based on accident information received from the reporting vehicle 120. When it is determined that an accident vehicle requests an accident image, the controller 133 can identify information related to the accident vehicle based on shared member information and send the information related to the accident vehicle to the reporting vehicle. Conversely, when it is determined that no accident vehicle requests an accident image, the controller 133 can store the reported image provided by the reporting vehicle 120 as tag 2 and send the fact that no accident vehicle requests an accident image to the reporting vehicle 120.

[0100] Figure 7 This is a flowchart illustrating a method for collecting accident information related to a vehicle involved in an accident, according to various exemplary embodiments of the present invention.

[0101] like Figure 7 As shown, in S110, the controller 117 of the accident vehicle 110 can determine the vehicle collision location. In S110, the controller 117 can determine the accident location from the impact detection sensor. According to various exemplary embodiments of the present invention, the controller 117 can determine the vehicle accident location by dividing the accident location into the front center, front left, front right, rear center, rear left, rear right, left direction, and right direction of the vehicle.

[0102] Furthermore, in S120, the controller 117 can acquire front and rear images, and in S130, based on the front and rear images, acquire license plate information related to nearby vehicles. Additionally, in S140, the controller 117 can send the acquired information to the server 130.

[0103] In addition, controller 117 can collect location information (GPS information) of the accident location in S150. Controller 117 can collect orientation information in S160. In the current situation, orientation information can represent driving direction information related to the vehicle, and can be divided into east, west, south, north, southwest, southeast, northeast, and northwest based on the accident location.

[0104] In S170, the controller 117 can collect road information related to the accident location based on map data from the navigation device 112. According to various exemplary embodiments of the present invention, the controller 117 can collect the number of roads adjacent to the road at the accident location, road-related type information, and the adjustment speed set to the road.

[0105] In S180, the controller 117 can determine a direction in which to request an accident image corresponding to a road type. That is, the controller 117 can determine a search direction. According to various exemplary embodiments of the present application, the controller 117 can determine a direction identical to a driving direction of an accident vehicle, a direction opposite to the driving direction of the accident vehicle, and a driving direction of a road entering an accident site as its search direction. When the accident site is a circular intersection, the controller 117 can request an accident image of a vehicle in the vicinity of an accident occurrence position without determining a search direction. In the current case, the controller 117 can exclude a search direction in which a collision position is not exposed from the determined search direction.

[0106] In S190, the controller 117 can collect attributes of a road at an accident occurrence position based on map data of the navigation device 112. According to various exemplary embodiments of the present application, the controller 117 can calculate an average speed of the road at the accident occurrence position, and set a time of an accident image (a time in the vicinity of an accident time point).

[0107] In S200, the controller 117 can calculate a search radius based on an adjusted speed of a road. The controller 117 can calculate the search radius by using Equation 1. In S210, the controller 117 can extract a search factor for acquiring information related to a report image based on accident information collected in S150 to S200. In the current case, the search factor can include a license plate number, a vehicle type, a vehicle color, an accident occurrence position, an accident occurrence time, and orientation information.

[0108] Figure 8 FIG. 4 is a flowchart illustrating a method of sharing accident information according to various exemplary embodiments of the present application.

[0109] As Figure 8 indicated in S310, the accident vehicle 110 can request an accident image from the server 130. According to various exemplary embodiments of the present application, when requesting an accident image from the server 130, a search factor can be set to license plate information (PID) of a vehicle.

[0110] When a request for an accident image is received from the accident vehicle 110, in S320, the server 130 can determine whether license plate information related to vehicles surrounding the accident vehicle exists in the member information based on the shared member information database. If, in S320, it is determined that the license plate information related to vehicles surrounding the accident vehicle is in the member information (Y), in S330, the server 130 can request an image report from the vehicle with the license plate information (the reporting vehicle) and can send information related to the accident vehicle. Conversely, if, in S320, it is determined that the license plate information related to vehicles surrounding the accident vehicle is not in the member information (N), in S350, the server 130 can request an image report from vehicles subscribed to the accident information service (unspecified members) based on search factors (GPS information, orientation information, search direction, search radius).

[0111] When the reporting vehicle 120 receives a request for a report image and accident vehicle information from the server 130, in S340, the reporting vehicle 120 can extract an image corresponding to the accident image from the image acquired by the reporting vehicle 120, and send the report image corresponding to the accident image to the accident vehicle 110 or the user's portable terminal of the accident vehicle.

[0112] When a reported image is received from the reporting vehicle 120, the accident vehicle 110 can store the image in S360.

[0113] Figure 9 This is a flowchart illustrating a method for sharing accident information according to various exemplary embodiments of the present invention.

[0114] like Figure 9 As shown, in S410, the accident vehicle 110 can determine whether an accident has occurred based on information obtained from the sensor 111 and the camera 113. When the airbag deploys and it is determined in S410 that an accident has occurred (Y), the accident vehicle 110 can automatically collect accident information in S420. Meanwhile, when the accident vehicle 110 cannot determine that an accident has occurred (N), the user can input accident information in S430.

[0115] In S440, the accident vehicle 110 can collect accident information based on information about the parts that have collided, location information related to the location of the accident, search radius based on the location of the accident, information about the road where the accident occurred, surrounding road information, and orientation information.

[0116] In addition, in S450, the accident vehicle 110 can request accident information and accident images from the server 130.

[0117] In S460, the server 130 can determine whether there is a report image matching the accident image requested by the accident vehicle 110. When it is determined in S460 that there is a report image matching the accident image (Y), the server 130 can identify information related to the report vehicle based on the sharing member information in S470, and can transmit the information related to the accident vehicle to the report vehicle whose information is identified in S480. Meanwhile, when it is determined in S460 that there is no report image matching the accident image (N), the server 130 can request to search for the accident image from the vehicle subscribed to the accident information sharing service in S510.

[0118] The report vehicle 120 can acquire the report image in S610, and store the report image in a storage device (storage database). The report vehicle 120 can extract an image at the time of the accident from the reported image in S620, and can analyze the image to extract a search factor in S630 and S640. When the information related to the accident vehicle is received from the server 130, the report vehicle 120 can transmit the image extracted in S620 to the accident vehicle or the user portable terminal of the accident vehicle in S490.

[0119] Meanwhile, the vehicle subscribed to the accident information sharing service and receiving the search request for the accident image from the server 130 searches for a report image corresponding to the accident image in S520, determines whether the accident vehicle is located within the designated radius of the host vehicle based on the GPS information related to the accident vehicle in S530, and determines whether the orientation information related to the accident vehicle matches the orientation information related to the host vehicle when it is determined based on the GPS information related to the accident vehicle that the accident vehicle is located within the designated radius of the host vehicle in S540.

[0120] When it is determined in S540 that the orientation information related to the accident vehicle matches the orientation information related to the host vehicle (Y), the vehicle subscribed to the accident information sharing service can extract an image at the accident time point from the report image and transmit the extracted image to the accident vehicle or the user portable terminal of the accident vehicle in S550. Meanwhile, when it is determined in S540 that the orientation information related to the accident vehicle does not match the orientation information related to the host vehicle, the vehicle subscribed to the accident information sharing service ends without a result in S560.

[0121] In S500, the accident vehicle can store the report image received from the report vehicle 120 or the vehicle subscribed to the accident information sharing service.

[0122] Figure 10 FIG. 1 is a flowchart illustrating a method of sharing accident information according to various exemplary embodiments of the present application.

[0123] AsFigure 10 As illustrated, in S710, the user of the reporting vehicle 120 can input accident information. The current time point can be before the server 130 receives a request for an accident image from an accident vehicle. When the accident information (reporting image) is input by the user, in S730, the reporting vehicle 120 can store the accident information and the reporting image as Tag 1. Further, in S720, the reporting vehicle 120 can transmit the reporting image (information related to the reporting image) to the server 130. The server 130 can store the reporting image (information related to the reporting image) received in S720. For example, the server 130 can store a reporting vehicle which provides the reporting image, a search factor, and a tag number generated in the vehicle.

[0124] The server 130 can determine whether there is an accident vehicle which requests an accident image corresponding to the reporting image based on the reporting image (the reporting image is information) received from the reporting vehicle 120 (S740). When it is determined that there is an accident vehicle which requests an accident image corresponding to the reporting image (Y) in S740, the server 130 can identify accident vehicle information based on the sharing member information in S750, and can transmit the accident vehicle information to the reporting vehicle 120 in S760.

[0125] Meanwhile, when it is determined that there is no accident vehicle which requests an accident image corresponding to the reporting image (N) in S740, the server 130 can store the reporting image provided from the reporting vehicle 120 as Tag 2 in S790, and can transmit the accident vehicle which does not request an accident image corresponding to the reporting image to the reporting vehicle 120 in S800.

[0126] When the reporting vehicle 120 receives the accident vehicle which does not request an accident image from the server 130, the reporting vehicle 120 can store the reporting image (information related to the reporting image) transmitted in S720 as Tag 2 in S810. Further, when the information related to the accident vehicle is received in S760, the reporting vehicle 120 can extract the reporting image stored as Tag 1, and transmit the reporting image to the accident vehicle 110 and the user portable terminal of the accident vehicle in S780.

[0127] Figure 11 FIG. 1 is a diagram illustrating a computing system for performing a method according to various exemplary embodiments of the present application.

[0128] Referring to Figure 11 , the computing system 1000 can include at least one processor 1100, a memory 1300, a user interface input device 1400, a user interface output device 1500, a storage device 1600, and a network interface 1700 connected through a bus 1200.

[0129] The processor 1100 can be a central processing unit (CPU) or a semiconductor device that processes instructions stored in the memory 1300 and / or the storage 1600. The memory 1300 and the storage 1600 can include various types of volatile or non-volatile storage media. For example, the memory 1300 can include read-only memory (ROM) 1310 and random access memory (RAM) 1320.

[0130] Accordingly, the processing of the method or algorithm described with respect to the exemplary embodiments of the present application can be embodied directly in hardware, in a software module executed by a processor 1100, or in a combination of the two. A software module can reside in a storage medium (i.e., the memory 1300 and / or the storage 1600), such as RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disk, solid state drive (SSD), external or internal disk drives, or CD-ROM. An example storage medium is coupled to the processor 1100, and the processor 1100 can read information from the storage medium and can write information to the storage medium. In another method, the storage medium can be integrated with the processor 1100. The processor and the storage medium can reside in an application-specific integrated circuit (ASIC). The ASIC can reside in a user terminal. In another method, the processor and the storage medium can reside as separate components in the user terminal.

[0131] According to the system and method for sharing accident information of the present application, when a vehicle accident occurs, by sharing the surrounding image with vehicles driving around the accident vehicle, the cause of the accident can be more accurately determined. In addition, according to the system and method for sharing accident information of the present application, not only the surrounding image can be transmitted to the accident vehicle, but also the surrounding image can be transmitted to the portable terminal of the occupant of the accident vehicle, so that the surrounding image can be shared with the family.

[0132] The above description is a simple example of the technical spirit of the present application, and those skilled in the art to which various exemplary embodiments of the present application belong can make various modifications and modifications to the present application without departing from the essential characteristics of the present application.

[0133] For ease of explanation and accurate definition in the appended claims, the terms "upper", "lower", "inner", "outer", "up", "down", "upwards", "downwards", "front", "rear", "back", "inside", "outside", "inwardly", "outwardly", "interior", "exterior", "internal", "external", "forwards", "backwards" describe features of the example embodiments with reference to the position of such features as shown in the drawings. It should further be understood that the term "connect" or its derivatives refers both to direct and indirect connection.

[0134] The foregoing description of specific exemplary embodiments of the application has been presented for the purposes of illustration and description. They are not intended to be exhaustive or to limit the application to the precise forms disclosed, and obviously many modifications and variations are possible in light of the above teachings. The example embodiments were chosen and described in order to explain certain principles of the application and their practical application to thereby enable others skilled in the art to make and utilize various exemplary embodiments of the present application, as well as various alternatives and modifications thereof. It is intended that the scope of the application be defined by the claims appended hereto, rather than the description and examples presented above.

Claims

1. A system for sharing accident information related to a vehicle, the system comprising: an accident vehicle configured to collect the accident information and request an accident image including the accident information; and a server configured to determine whether the accident image and a request for the accident image are received from the accident vehicle, to identify a reporting vehicle configured to provide a reporting image corresponding to the accident information and the accident image upon determining that the accident information and the request for the accident image are received, and to request the reporting vehicle to transmit the reporting image acquired by the reporting vehicle to the accident vehicle; and wherein the server is configured to store information related to the reporting image provided from the reporting vehicle, and to determine whether an accident vehicle requesting the accident image exists upon not receiving the accident information and the request for the accident image from the accident vehicle.

2. The system of claim 1, wherein, The accident vehicle is configured to collect the accident information including location information related to an accident occurrence point, a search radius based on the accident occurrence point, information related to a road where an accident occurs, adjacent road information, and orientation information.

3. The system of claim 1, wherein, The accident vehicle is configured to extract a search factor for acquiring information related to the reporting image based on the accident information.

4. The system of claim 3, wherein, The search factor includes a license plate number, a vehicle type, a vehicle color, an accident occurrence location, an accident occurrence time, and orientation information.

5. The system of claim 4, wherein, The server is configured to store a history of providing the reporting image upon determining that the reporting image is provided from the reporting vehicle.

6. The system of claim 5, wherein, The server is configured to determine whether information related to the reporting vehicle is identified based on the search factor or the history of providing the reporting image.

7. The system of claim 1, wherein, The server is configured to transmit information related to the accident vehicle to the reporting vehicle upon determining that information related to the reporting vehicle is identified.

8. The system of claim 1, wherein, The server is configured to request the reporting image corresponding to the accident image from a vehicle subscribing to an accident information sharing service upon determining that information related to the reporting vehicle is not identified.

9. The system of claim 1, wherein, The server is configured to identify information related to the accident vehicle and transmit information related to the accident vehicle to the reporting vehicle upon determining that the accident vehicle requesting the accident image exists.

10. The system of claim 1, wherein, The server is configured to notify the reporting vehicle that any vehicle requesting the accident image does not exist and to request the reporting vehicle to store the accident image upon determining that any accident vehicle requesting the accident image does not exist.

11. The system of claim 1, wherein, The reporting vehicle is configured to transmit the reporting image to the accident vehicle or a user portable terminal of the accident vehicle upon receiving information related to the accident vehicle from the server.

12. The system of claim 11, wherein, The reporting vehicle is configured to extract a search factor upon acquiring the reporting image. 13.A method of sharing accident information, the method comprising: collecting accident information by an accident vehicle and requesting an accident image including the accident information from a server by the accident vehicle; determining, by the server, whether the accident information and the request for the accident image are received, and identifying, by the server, a reporting vehicle configured to provide a reporting image corresponding to the accident information and the accident image upon determining that the accident information and the request for the accident image are received; requesting, by the server, the reporting vehicle to transmit the reporting image obtained by the reporting vehicle to the accident vehicle; and storing, by the server, information about the reporting image provided from the reporting vehicle, and determining, by the server, whether the accident vehicle requesting the accident image exists upon not receiving the accident information and the request for the accident image from the accident vehicle. 14.The method of claim 13, further comprising: transmitting, by the server, information about the accident vehicle to the reporting vehicle upon determining that information about the reporting vehicle is identified. 15.The method of claim 13, further comprising: requesting, by the server, the reporting image corresponding to the accident image from a vehicle subscribed to an accident information sharing service upon determining that information about the reporting vehicle is not identified.

16. The method of claim 13, wherein, the server is configured to identify information about the accident vehicle upon determining that the accident vehicle requesting the accident image exists, and transmit information about the accident vehicle to the reporting vehicle. 17.The method of claim 13, further comprising: notifying, by the server, the reporting vehicle that any vehicle requesting the accident image does not exist upon determining that any vehicle requesting the accident image does not exist, and requesting, by the server, the reporting vehicle to store the reporting image. 18.The method of claim 13, further comprising: transmitting, by the reporting vehicle, the reporting image to the accident vehicle or a user portable terminal of the accident vehicle upon determining that information about the accident vehicle is received from the server.

Images