KR102316652B1 - Apparatus and method for notifying accident of vehicle using telephone - Google Patents

Abstract

The present invention proposes an apparatus and method for reporting a vehicle accident using a phone terminal for reporting a vehicle accident using wired/wireless connectivity between a vehicle and a terminal to which a phone function is assigned. A vehicle accident reporting apparatus according to the present invention includes an accident occurrence determination unit for determining whether an accident has occurred in a vehicle; a wired connection determination unit that determines whether the terminal to which the phone function is assigned is connected to the vehicle by wire when it is determined that an accident has occurred in the vehicle; a wireless connection execution unit for wirelessly connecting the terminal to which the phone function is granted to the vehicle when it is determined that the terminal to which the phone function is assigned is not connected to the vehicle by wire; and a vehicle accident reporting unit that reports an accident to a Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned when the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly.

Description

Apparatus and method for notifying accident of vehicle using telephone}

The present invention relates to an apparatus and method for reporting a vehicle accident. More particularly, it relates to an apparatus and method for reporting a vehicle accident to a Public Safety Answering Point (PSAP) using an emergency call system.

In the event of a traffic accident, fatal injuries to the driver may result in death due to failure to promptly notify the rescue team of an emergency situation. In order to prevent such a problem, a system has been developed that automatically transmits accident location information to the rescue team when a traffic accident occurs using a telematics system.

However, an emergency notification system using a general telematics system has drawbacks including structural complexity and high cost. For example, the high cost is due to the purchase price, in-vehicle installation and subscriber service. In addition, existing telematics units capable of automatically responding to vehicle accidents are hard-wired into the vehicle to transmit information from sensors or other detectors in the vehicle to the telematics unit, and installation of such telematics units is expensive and expensive. Complex.

Korean Patent Application Laid-Open No. 2011-0113379 proposes an emergency situation notification system using an OBD system built into a vehicle. This system can solve the problem of using a general telematics system, but there is a problem in that it is impossible to automatically transmit accident location information to the rescue team when the OBD system does not operate normally.

The present invention has been devised to solve the above problems. Reporting a vehicle accident using a phone terminal that reports a vehicle accident using wired/wireless connectivity between the vehicle and a terminal (eg, a smartphone) to which a phone function is granted It aims to propose an apparatus and method.

However, the object of the present invention is not limited to the above, and other objects not mentioned will be clearly understood by those skilled in the art from the following description.

The present invention has been devised to achieve the above object, an accident occurrence determination unit for determining whether an accident has occurred in the vehicle; a wired connection determination unit for determining whether a terminal to which a phone function is assigned is connected to the vehicle by wire when it is determined that the accident has occurred in the vehicle; a wireless connection execution unit for wirelessly connecting the terminal to which the phone function is granted to the vehicle when it is determined that the terminal to which the phone function is granted is not connected to the vehicle by wire; and a vehicle accident reporting unit that reports the accident to a Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned when the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly We propose a vehicle accident reporting device using a telephone terminal.

Preferably, the wired connection determining unit determines whether there is a terminal to which the phone function is assigned among terminals connected to the vehicle by a USB method to determine whether the terminal to which the phone function is assigned is connected to the vehicle by wire. decide whether

Preferably, when the wire connection determination unit determines that the terminal to which the phone function is assigned is connected to the vehicle by wire, a protocol usable in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle determine whether there is

Preferably, when it is determined that there is no protocol available in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle, the wireless connection execution unit wirelessly connects the terminal to which the phone function is granted to the vehicle make it

Preferably, the wired connection determining unit determines whether there is a protocol usable in the terminal to which the phone function is granted, among protocols supporting the call function in the vehicle, based on the information about the terminal to which the phone function is granted .

Preferably, the wireless connection execution unit determines whether the terminal to which the telephone function is granted supports a hands-free function before wirelessly connecting the terminal to which the telephone function is granted to the vehicle.

Preferably, the wireless connection execution unit determines whether another terminal is wirelessly connected to the vehicle using a predetermined wireless connection method before wirelessly connecting the terminal to which the phone function is assigned to the vehicle.

Preferably, when it is determined that the other terminal is wirelessly connected to the vehicle using the wireless connection method, the wireless connection execution unit terminates the wireless connection between the other terminal and the vehicle and then uses the wireless connection method Thus, the terminal to which the phone function is granted is wirelessly connected to the vehicle.

Preferably, when the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP ends within a predetermined time, the vehicle accident report unit is provided with the phone function The call connection between the terminal and the PSAP is re-attempted.

Preferably, the vehicle accident reporting unit measures a call connection time between the terminal to which the phone function is granted and the PSAP when a call connection between the terminal to which the phone function is granted and the PSAP is successful.

Preferably, when the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated, the vehicle accident reporting unit is prioritized among the phone numbers stored in advance. The accident is reported based on at least one phone number selected accordingly.

Preferably, the accident occurrence determining unit includes whether a predetermined signal is input by the driver of the vehicle, whether a signal for commanding deployment of an airbag in the vehicle is input, whether the load change amount of the vehicle is greater than or equal to a reference change amount; and whether the accident has occurred in the vehicle based on at least one of whether the inclination of the vehicle is equal to or greater than a reference inclination.

The present invention also includes the steps of determining whether an accident has occurred in the vehicle; determining whether a terminal to which a phone function is assigned is connected to the vehicle by wire when it is determined that the accident has occurred in the vehicle; when it is determined that the terminal to which the phone function is granted is not connected to the vehicle by wire, wirelessly connecting the terminal to which the phone function is granted to the vehicle; and when the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly, reporting the accident to a Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned. A method of reporting a vehicle accident using a terminal is proposed.

Preferably, the step of determining whether the connection is made by determining whether there is a terminal to which the phone function is granted among terminals connected to the vehicle in a USB manner is determined so that the terminal to which the phone function is assigned is connected to the vehicle Determines whether it is connected by wire or not.

Preferably, in the step of determining whether the connection is made, when it is determined that the terminal to which the phone function is assigned is connected to the vehicle by wire, the phone function is assigned among protocols supporting the call function in the vehicle. It is determined whether there is a protocol available in the terminal.

Preferably, in the connecting step, if it is determined that there is no protocol available in the terminal to which the phone function is granted among protocols supporting the calling function in the vehicle, the terminal to which the phone function is granted is wirelessly connected to the vehicle make it

Preferably, in the step of determining whether the connection is made, a protocol available in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle based on information about the terminal to which the phone function is granted is selected. determine whether there is

Preferably, in the connecting step, before wirelessly connecting the terminal to which the telephone function is granted to the vehicle, it is determined whether the terminal to which the telephone function is granted supports a hands-free function.

Preferably, in the connecting step, it is determined whether another terminal is wirelessly connected to the vehicle using a predetermined wireless connection method before wirelessly connecting the terminal to which the phone function is assigned to the vehicle.

Preferably, in the connecting step, when it is determined that the other terminal is wirelessly connected to the vehicle using the wireless connection method, the wireless connection between the other terminal and the vehicle is canceled and then the wireless connection method is used. Thus, the terminal to which the phone function is granted is wirelessly connected to the vehicle.

Preferably, in the reporting step, when the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated within a predetermined time, the phone function is given The call connection between the terminal and the PSAP is re-attempted.

Preferably, in the reporting step, if a call connection between the terminal to which the phone function is granted and the PSAP is successful, a call connection time between the terminal to which the phone function is granted and the PSAP is measured.

Preferably, in the reporting step, if the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated, the priority is selected from among the phone numbers stored in advance. The accident is reported based on at least one phone number selected accordingly.

Preferably, the determining whether the occurrence includes whether a predetermined signal is input by a driver of the vehicle, whether a signal for commanding deployment of an airbag in the vehicle is input, and the amount of change in the load of the vehicle is a reference change amount It is determined whether the accident has occurred in the vehicle based on at least one of whether or not the vehicle has an abnormality and whether the vehicle has a reference slope or greater.

The present invention can obtain the following effects by reporting a vehicle accident using wired/wireless connectivity between the vehicle and a terminal (eg, a smart phone) to which a phone function is granted.

First, it can support USB calls to improve the availability of automatic incident reporting.

Second, it becomes possible to automatically report an accident without user manipulation.

Third, there is no need for a separate modem device for automatic accident reporting by using Bluetooth and USB hands-free calling functions.

Fourth, there is no need to purchase and install a separate modem for automatic accident reporting, and users do not need to pay a separate communication fee to use the telematics service.

1 is a block diagram of an automatic accident report service providing system according to an embodiment of the present invention.
FIG. 2 is an internal configuration diagram of the in-vehicle terminal constituting FIG. 1 .
3 is a flowchart illustrating an operation scenario of an automatic accident report service supporting wired/wireless connectivity according to an embodiment of the present invention.
4 is a conceptual diagram illustrating a flow of a Health Status message.
5 is a conceptual diagram illustrating a flow of a Paired Device List message.
6 is a conceptual diagram illustrating a flow of a Service Discovery message.
7 is a conceptual diagram illustrating a flow of a Service Connection message.
8 is a conceptual diagram illustrating a flow of an SMS Support message.
9 is a conceptual diagram illustrating a flow of an SMS Send message.
10 is a conceptual diagram illustrating a flow of a Phonebook Download message.
11 is a conceptual diagram illustrating the flow of an outgoing call message.
12 is a conceptual diagram illustrating a flow of a Terminate Call message.
13 is a conceptual diagram illustrating a flow of a Get Current Calls message.
14 is a conceptual diagram illustrating a flow of a Call Status Indication message.
15 is a block diagram schematically illustrating a vehicle accident reporting apparatus according to a preferred embodiment of the present invention.
16 is a flowchart schematically illustrating a method for reporting a vehicle accident according to a preferred embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First of all, it should be noted that in adding reference numerals to the components of each drawing, the same components are given the same reference numerals as much as possible even though they are indicated on different drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present invention, the detailed description thereof will be omitted. In addition, preferred embodiments of the present invention will be described below, but the technical spirit of the present invention is not limited thereto and may be variously implemented by those skilled in the art without being limited thereto.

The present invention relates to a method for improving the availability of a function for automatically reporting an accident using a device having a phone call function when an accident occurs in a vehicle. An object of the present invention is to secure reusability and device compatibility of automatic accident report S/W even when increasingly diverse wired and wireless mirroring technologies are grafted onto automobiles.

The recently developed smartphone connectivity technology supports the use of voice recognition, multimedia, phone calls and navigation functions provided by the smartphone when the user connects the smartphone to the vehicle. When this technology is used, there is no need for the user to register a mobile communication terminal in the vehicle using Bluetooth for hands-free phone calls. Therefore, according to the present invention, when an accident occurs, the automatic accident report service can be normally executed even if the Bluetooth-enabled device is not registered.

1 is a block diagram of an automatic accident report service providing system according to an embodiment of the present invention.

The automatic accident reporting service providing system 100 is an automatic accident reporting service providing system supporting wired/wireless mirroring connection technology.

The vehicle interface 111 is provided in the in-vehicle terminal 110, and a signal for detecting the occurrence of an accident in the vehicle is input through CAN, LIN, Flexray, PWM, or the like.

The in-vehicle terminal 110 is a terminal supporting the mobile communication terminal 120 and the wired connection technology 122 and the wireless connection technology 121 . The in-vehicle terminal 110 is a device that provides in-vehicle multimedia or infotainment functions such as navigation.

The mobile communication terminal 120 supports the wired connection technology 122 or the wireless connection technology 121 and is a portable terminal having a telephone function. The mobile communication terminal 120 is a terminal such as a smartphone that supports a phone function using Bluetooth hands-free or USB connection.

The accident report center server 130 is a server provided in an automatic accident report response center, and may be provided in a vehicle accident report center such as 119 or 112 in Korea or 911 in the United States.

The automatic accident report service providing system 100 has been described with reference to FIG. 1 above. The present invention to be described below is limited to a method of controlling peripheral devices of the in-vehicle terminal 110 . The main configuration of the in-vehicle terminal 110 will be described with reference to FIG. 2 . FIG. 2 is an internal configuration diagram of the in-vehicle terminal constituting FIG. 1 .

The external equipment interface 111 is an interface for controlling external devices connected to the in-vehicle terminal 110 through CAN, LIN, Flexray, or the like.

The MICOM 112 is a processor in charge of transmitting and receiving messages for interworking with external devices. In the present invention, the MICOM 112 controls an audio input device (eg, a microphone) and an output device (eg, an amplifier, a speaker, etc.). In addition, the MICOM 112 serves to transfer the vehicle accident occurrence event to the CPU block 113 .

The CPU block 113 is a main processor block in which a main application is driven. In the present invention, the CPU block 113 serves to recognize the occurrence of a vehicle accident. In addition, the CPU block 113 serves to automatically connect a phone call to the accident report center server 130 using the API provided by the external device interworking module 114 .

The external device interworking module 114 provides APIs that can be used by higher-level applications as S/W for interworking with various external devices. The external device interworking module 114 is composed of S/W implementing the requirements defined in each interface standard. Meanwhile, the external device interworking module 114 is in charge of an interface with a device providing a phone function connected to the in-vehicle terminal 110 .

The internal interfaces 141 , 142 , and 143 are interfaces between internal modules constituting the in-vehicle terminal 110 , such as UART, SPI, and IIC.

The Bluetooth stack 115 is a S/W and H/W module for an interface between the in-vehicle terminal 110 and the mobile communication terminal 120 supporting Bluetooth.

The USB connector 116 is a H/W connector that can be connected to the in-vehicle terminal 110 and the mobile communication terminal 120 supporting USB.

3 is a flowchart illustrating an operation scenario of an automatic accident report service supporting wired/wireless connectivity according to an embodiment of the present invention. The following description refers to FIG. 3 .

In the present invention, wired and wireless connection technologies supporting the known mirroring function are described as examples, but the present invention is not limited thereto. Examples of wired connection technology include Apple's Car play and Google's Automotive Link using USB. Examples of wireless connection technology include Bluetooth hands-free.

The in-vehicle terminal 110 of the present invention is described using Google's Android platform as an example, but is not limited thereto.

1. Accident occurrence recognition (S205)

When an accident occurs in the vehicle, the airbag sensor detects it. From this sensor, an accident occurrence event is transmitted to the MICOM 112 of the in-vehicle terminal 110 through CAN, LIN, Flexray, PWM, or the like.

The MICOM 112 transmits this message to the CPU block 113 and the telematics application of the CPU block 113 recognizes that an accident has occurred in the vehicle.

The telematics application informs the driver of an accident through voice guidance and a display device to the driver in the vehicle, and notifies the start of the automatic accident reporting service.

2. Check the device connection

2.1 Check Wired Connection (S210)

Since a wired connection is more stable than a wireless connection, when the mobile communication terminal 120 is connected via a wired connection, a call connection is attempted with priority over the wired connection. In the present invention, a method of using USB, which is one of the wired connection technologies, is described. As in Code 1 below, a USB device list is obtained and if there is at least one device, it is determined that the USB device is connected.

If there is no wired connection, go to step 3 and try wireless automatic connection.

- Code 1. How to acquire a USB device

private UsbDevice getUsbDevice() {

// Create USB-related services provided by Android.

UsbManager manager = (UsbManager) context.getSystemService(Context.USB_SERVICE);

// Acquire a list of USB devices connected to the in-vehicle terminal.

HashMap<String, UsbDevice> deviceList = manager.getDeviceList();

// Check each device connected via USB.

Iterator<UsbDevice> deviceIterator = deviceList.values().iterator();

while (deviceIterator.hasNext()) {

UsbDevice device = deviceIterator.next()

String devName = device.getDeviceName();

// Check if it is a USB hub.

if (device.getDeviceClass() != USB_CLASS_HUB ) {

if ((new File(devName)).exists())

return device;

}

}

}

2.1.1 Check if the protocol supports phone calls (S215)

It is checked whether the connected mobile communication terminal 120 is a connectivity technology supporting a phone call function. For wired connectivity protocols that do not support phone calls, go to step 2.2 and check if there is a wireless connection. In this case, Apple's Car play and Google's Automotive Link are described for wired connection, and wireless connection describes Bluetooth.

Since several protocols may exist in a wired connection supporting a phone call, the in-vehicle terminal 110 stores supportable protocols in a list form and checks whether each protocol is supported for a connected device. In this case, it can be confirmed through code 2.

- Code 2. Check whether the protocol is supported for the connected USB device

// Acquire the USB device.

UsbDevice device = getUsbDevice();

// Get a list of supported protocols stored in the in-vehicle terminal.

HashMap<String, String> ProtocolList = manager.getProtocolList();

// Check if the USB connected device supports each protocol.

Iterator<String> iterator = ProtocolList.values().iterator();

while (iterator. hasNext()) {

String Protocol = iterator.next()

// Check whether each protocol is supported, and if it is confirmed that it supports it, the corresponding protocol name is returned.

if (checkProtocol(device, Protocol) == true) {

return Protocol ;

}

}

2.1.1.1 Check if the device supports Apple's "Car play"

When the wired connection state is confirmed through step 2.1 above, the in-vehicle terminal 110 checks whether the wired connection supports a phone call. In this case, we use Car play and check whether it is Apple's unique ID by acquiring the vendor ID of the device connected to the USB. You can check it with code 3.

If the USB device is identified as an Apple device, check whether it is connected with the Car play protocol that supports the phone call function. In this case, it can be determined whether Car play is executed in Code 4 or not.

- Code 3. How to check if it is an Apple device

public static final boolean isAppleDevice(UsbDevice device) {

// Check by vendor ID if the connected USB device is an Apple device

return device.getVendorId() == 0x05AC;

}

- Code 4. How to check if the device supports car play

// Check if Car play is executed by the connected USB device

return IDiPOManager.getStatus(TYPE_DIPO_STAT) == VAL_DIPO_STAT_STARTED

2.1.1.2 Checking if the device supports Google's Automotive Link

If the wired device in steps 2.1.1 and 2.1.1.1 above does not support a specific protocol, check whether the next protocol in the list is supported. In this case, it is explained using Automotive Link, and it checks whether it is Google's unique ID by acquiring the vendor ID of the device connected to the USB. This can be verified through code 6.

If the USB device is identified as a Google device, check whether it is connected with the Automotive Link protocol that supports the phone call function. In this case, it can be determined whether Automotive Link is executed in Code 5.

- Code 5. How to check whether Automotive Link is running

// Create a solution to manage Automotive link.

GpmManager mGpmManager; mGpmManager = new GpmManager((Context)mContext);

// Returns TRUE if Automotive function is running.

return mGpmManager.isGpmActivated();

- Code 6. How to check if it is an Automotive Link enabled device

public static final boolean isAoaDevice(UsbDevice device) {

// Check if the vendor ID of the connected USB device is a Google device

if (device.getVendorId() == 0x18D1) {

// Check if the product ID of the connected USB device supports Android open accessory

switch(device.getProductId()) {

case 0x2D00: // accessory

case 0x2D01: // accessory + adb

case 0x2D02: // audio

case 0x2D03: // audio + adb

case 0x2D04: // accessory + audio

case 0x2D05: // accessory + audio + adb

return true;

}

}

return false;

}

2.1.1.3. other devices

An exception is processed for a case where the device currently connected by wire does not support the callable protocol defined in the in-vehicle terminal 110 . If it is determined that the device does not provide a phone call function as a result of the final check, go to step 2.2 to check the wireless connection.

In this case, Google's Android-based devices may not start the Android Open Accessory (AOA) session by the mobile communication terminal 120 because the vendor ID of the USB uses the ID of each manufacturer. Therefore, it transmits the AOA execution request to the smartphone and waits for the vendor ID to respond to Google. If there is no response, it is judged as an unsupported terminal and moves to step 2.2.

- Code 7. Request to run Android Open Accessory

// Values defined by Google in Android Open Accessory and must be transmitted in order of index.

private static final Object[][] ACCESSORY_STRINGS = {

{ACCESSORY_STRING_MANUFACTURER, "Hyundai Mobis"},

{ACCESSORY_STRING_MODEL, "TelematicsLite"},

{ACCESSORY_STRING_DESCRIPTION, "Telematics Lite"},

{ACCESSORY_STRING_VERSION, "1.0"},

{ACCESSORY_STRING_URI, "http://www.myuvo.com/uvoapp/android.shtml"},

{ACCESSORY_STRING_SERIAL, "1234567890"}

};

// command to run AOA

public static final int ACCESSORY_SEND_STRING = 52;

public static final int ACCESSORY_START = 53;

// The in-vehicle terminal transmits the values for starting AOA to the mobile communication terminal using USB communication.

for (Object[] strings : ACCESSORY_STRINGS) {

connection.controlTransfer(UsbConstants.USB_DIR_OUT | UsbConstants.USB_TYPE_VENDOR,

ACCESSORY_SEND_STRING, 0, (Integer) strings[0], (String) strings[1], (String) strings[1]. length,

AOA_TIMEOUT);

}

connection.controlTransfer( UsbConstants.USB_DIR_OUT | UsbConstants.USB_TYPE_VENDOR,

ACCESSORY_START, 0, 0, null, 0, AOA_TIMEOUT);

2.2 Checking the wireless connection (S235)

If there is no wired connection or the protocol does not support phone calls, try to make a phone call using wireless connection technology. In the present invention, a method of using Bluetooth, which is one of the wireless connection technologies, will be described.

- Code 8. Check Bluetooth connection

private int checkBluetoothCall() {

BluetoothAdapter adapter = BluetoothAdapter.getDefaultAdapter();

// Acquire the Bluetooth-connectable device stored in the in-vehicle terminal.

Set<BluetoothDevice> deviceList = adapter.getBondedDevices();

// If the device list is 0 or less, it means that there are no saved devices.

if (deviceList == null || deviceList.size() < 1)

return NOT_PAIRED;

// If there is a saved device and there is a device currently connected via Bluetooth, a call can be made to the automatic accident report center.

if(mLocalManager.IbtcmGetHFConnectedDevice() != null)

return CONNECTED;

// If there is a saved device but no device currently connected via Bluetooth, an automatic connection should be attempted.

else

return NOT_CONNECTED;

}

2.2.1 Check if the device supports Bluetooth Hands-free (S240)

In this case, it is checked whether the mobile communication terminal 120 connected through Bluetooth supports the Hands-free function.

The in-vehicle terminal 110 transmits 'PAIRED_DEVICE_LIST_REQ' to the Bluetooth Stack 115 to request a list of currently registered Bluetooth-enabled devices. Then, by receiving 'PAIRED_DEVICE_LIST_IND', the currently registered Bluetooth-enabled device is checked.

The in-vehicle terminal 110 checks whether the registered Bluetooth-enabled device supports the Handsfree function. This can be confirmed because the service supported by transmitting 'SERVICE_DISCOVERY_REQ' and receiving 'SERVICE_DISCOVERY_IND' from the Bluetooth Stack 115 when registering the Bluetooth device to the in-vehicle terminal 110 is stored in the non-volatile memory in advance.

If there is no device that supports Handfree, it induces the driver to directly report an accident through voice guidance and display devices, and terminates the automatic accident reporting service.

When there is a device supporting Handsfree, the in-vehicle terminal 110 transmits 'HEALTH_STATUS_REQ' to the Bluetooth Stack 115 to request status information of the Bluetooth service. Then, the 'HEALTH_STATUS_CFM' response message is received to check the Handsfree status.

If the Handsfree status is 'INITIALISING', 'READY' or 'CONNECTING', it is not currently connected, so go to step 3.

If Handsfree status is 'CONNECTED', 'INCOMING_CALL', 'OUTGOING_CALL', 'ACTIVE_CALL', 'WAITING_CALL', 'MULTI_ACTIVE_CALL', 'HELD_CALL', 'ACTIVE_AND_HOLD', or 'MULTI_HELD_CALL' because it is already in a connected step do.

2.2.2 Other devices (S245)

If it does not support Bluetooth hands-free or there is no Bluetooth-connected device, go to step 3 to try Bluetooth auto-connection.

4 is a conceptual diagram illustrating a flow of a Health Status message.

Message (Parameter)

- HEALTH_STATUS_REQ ( )

- HEALTH_STATUS_CFM (Handsfree Status, A2DP Status, AVRCP Status, PBAP Status, Call Status)

The CPU block 113 may request the status of the Bluetooth stack 115 by transmitting HEALTH_STATUS_REQ ( 311 ). The Bluetooth Stack 115 informs all current states with the values of each parameter (312).

5 is a conceptual diagram illustrating a flow of a Paired Device List message.

Message (Parameter)

- PAIRED_DEVICE_LIST_REQ ( )

- PAIRED_DEVICE_LIST_IND (Index, BD Address, Device Name)

- PAIRED_DEVICE_LIST_CFM (Result)

By transmitting PAIRED_DEVICE_LIST_REQ from the CPU block 113 , a list of paired devices stored in the Bluetooth stack 115 may be retrieved ( 321 ). In response to this, the Bluetooth Stack 115 transmits information on the paired device through a PAIRED_DEVICE_LIST_IND message (322) and transmits a PAIRED_DEVICE_LIST_CFM message when all list transmissions are completed (323). However, the maximum number of paired devices may be limited depending on the development environment.

6 is a conceptual diagram illustrating a flow of a Service Discovery message.

Message (Parameter)

- SERVICE_DISCOVERY_REQ (BD Address, Profile ID List Number , Profile ID List )

- SERVICE_DISCOVERY_IND (Supported Profile ID , Result )

- SERVICE_DISCOVERY_CFM (Result)

You can search for support services for a specified Bluetooth device. When the UI System transmits the information (BD Address) and Profile IDs of the device for which the support service is to be searched to the Bluetooth Stack 115 together with the SERVICE_DISCOVERY_REQ message, the support service of the designated device is searched (331).

The search result of the support service is delivered by SERVICE_DISCOVERY_IND (332).

SERVICE_DISCOVERY_CFM notifies the end of the search result delivery (333).

3. Attempt to automatically connect wirelessly (S245, S250)

The Bluetooth automatic connection target device is limited to a device that is registered in the in-vehicle terminal 110 and supports the Handsfree service.

It attempts to connect to the most recently connected device among the registered devices. In this case, when connecting a Bluetooth device, 'BT_DEVICE_ADDRESS' is stored in non-volatile memory, and then the recently connected device can be found by searching from the registered device list obtained through 'PAIRED_DEVICE_LIST_IND' in step 2.2.1.

If 'BT_DEVICE_ADDRESS' of a recently connected Bluetooth-enabled device exists in the list, 'BT_DEVICE_ADDRESS' and 'HANDSFREE_PROFILE_ID' are included in the 'SERVICE_CONNECT_REQ' message and transmitted to the Bluetooth Stack 115 to request a connection.

The automatic connection success condition is when 'RESULT_SUCESS' is received in the result field of 'SERVICE_CONNECT_CFM'.

If the connection fails, try to connect one or several times to each of the registered devices that support Handsfree. If all devices fail despite the automatic connection attempt, the user is encouraged to report an accident directly using the voice guidance and display device, and the automatic accident reporting service is terminated.

7 is a conceptual diagram illustrating a flow of a Service Connection message.

Message (Parameter)

- SERVICE_CONNECT_REQ (BD Address, Profile ID)

- SERVICE_CONNECT_CFM (Result, BD Address, Profile ID, Connection ID Remote Name )

A service connection may be attempted to a designated Bluetooth-enabled device. When the CPU block 113 transmits the address (BD Address) and Profile ID of a specific device together with the SERVICE_CONNECT_REQ message to the Bluetooth Stack 115 (341), a SERVICE_CONNECT_CFM message is transmitted to the CPU block 113 along with the processing result. (342).

4. Try to make a call (S220, S240).

A telephone connection is attempted to the accident report center server 130 using a wired or wireless connection technology.

4.1. Attempt to make a call using wired connection technology (S220)

When the device connected to the in-vehicle terminal 110 by wire supports a phone call function, a call is made to the accident report center server 130 . In this case, Apple's Car Play function is explained.

4.1.1 Dial-up Attempts

An attempt is made to make a phone call to the accident report center server 130 . In this case, a method of requesting to make a call to the mobile communication terminal 120 using Apple's Car Play through a USB channel will be described. You can make a call through code 10.

After requesting to make a call, check whether the call is connected normally using the call status and the phone number being called. This example describes how to use apple's iap2. This can be seen in code 9.

If the phone is connected normally, you can talk to the accident report center counselor.

If the wired connection is disconnected or becomes inoperable while connecting a phone, an automatic wireless connection is attempted. You can see it in code 11.

- Code 9. Check phone connection status

public void onReceive(Context context, Intent intent) {

String action = intent.getAction();

Bundle extras = intent.getExtras();

// Receive phone status information of car play.

if(action.equals(ACTION_CARPLAY_CALL_INFORMATION)){

// Receive the phone number of the other party who is talking on the phone with Car play.

String callNumber = extras.getString("carPlayCallNumber");

// Receive call status of car play.

int callStatus = extras.getInt("carPlayCallStatus");

int callDirection = extras.getInt("carPlayCallDirection");

switch(callStatus) {

// Connecting the phone

case Iap2Const.CallStateStatus.Connecting:

onCarPlayCallDialing(callNumber);

break;

// phone connected

case Iap2Const.CallStateStatus.Active:

onCarPlayCallActive(callNumber);

break;

// Call hung up.

case Iap2Const.CallStateStatus.Disconnected:

onCarPlayCallDisconnected(callNumber);

break;

}

}

- Code 10. Attempt to connect the phone

private void requestAcnCarPlayCalling() {

changeAcnProgressState(AcnProgressState.REQUEST_DIALING);

startDtmfReceiverService();

// Request to make a call to car play.

Intent intent = new Intent("android.intent.action.UVO_REQUEST");

intent.putExtra("command", 0x01); //UVO Call

intent.putExtra("url","tel:" + getAcnCallNumber());

sendBroadcast(intent);

}

- Code 11. Attempt to automatically connect wirelessly when disconnected from wired connection

// When car play is connected

if(mCarPlayStateUpdateService.carPlayDipoStatus() == DIPO_STAT_STARTED) {

mCarPlayCallScreen = true;

// Make a call to car play.

startAcnCarPlayCall();

}

// if the car pay is disconnected

else {

// If Bluetooth is not connected

if (checkBluetoothCall() == AcnBluetoothStatus.NOT_CONNECTED) {

// Attempt to automatically connect to Bluetooth.

startBluetoothAutoConnection();

return;

}

// If Bluetooth is connected, make a call using Bluetooth.

startAcnBluetoothCall();

}

4.1.2 Dial Connection Retry (S225, S230)

Due to an error in the mobile communication terminal 120 or a temporary failure of the mobile communication network, a call connection with the accident report center server 130 may not be automatically performed. Therefore, in the present invention, a call connection retry function is added to improve the availability of the automatic accident report service.

If the user does not end the call using the H/U user interface (hard key, screen touch, steering wheel remote control, etc.) and the call state becomes 'Disconnected', the call connection is retryed. In the present invention, a method of using apple's iap2 for call connection failure determination will be described as an example. You can see it in code 12.

If the mobile communication terminal 120 fails to connect to the accident report center server 130 because the mobile communication terminal 120 is already in a call before making a call, the existing call is forcibly terminated. Therefore, when a call other than the accident report center phone number is terminated, the call connection retry function is not performed and it waits to be connected to the accident report center server 130 .

If the phone call connection is successful but the call is terminated within 5 seconds, it is difficult to see that a normal call with the agent at the accident report center has been made, so retry the phone connection.

The call connection is retried only once. If it fails again, the service is terminated and the user is notified.

- Code 12. Logic to determine if the phone is disconnected

private void onCarPlayCallDisconnected(String number) {

// If the call corresponding to another phone number is disconnected, it is ignored.

if (!isEmergencyNumber(number) && (mCallActiveTimeMillis != -1)) {

return;

}

// If the user ends using the user interface of H/U, do not retry the phone connection.

if (mUuserCallEnd == true){

mServiceResultSuccess = false;

// If the call is terminated before the phone call is connected, try again.

} else if (mCarPlayCallRequested ) {

// If this is the first failure, retry once.

if (mRetryCountForCallDrop < 1) {

mRetryCountForCallDrop++;

mRetryCallingRequested = true;

dialFailed(false);

// If it is retryed once and fails again, it is treated as a service termination.

} else {

dialFailed(true);

}Call connected but disconnected within 5 seconds

// If the call ends within 5 seconds after connection, retry.

} else if (disconnectedTimeMillis - mCallActiveTimeMillis) < 5000) {

if (mRetryCountForCallDrop < 1) {

mRetryCountForCallDrop++;

mRetryCallingRequested = true;

dialFailed(false);

} else {

dialFailed(true);

}

}

// if you need to retry

if (mRetryCallingRequested) {

// Send a message for retrying the call connection.

mHandler.sendEmptyMessageDelayed(H_REQUEST_REDIALING_EMERGENCY_CALL, 2000);

return;

}

}

- Code 13. Auto Retry Call Connection

public void handleMessage(Message msg) {

switch(msg.what) {

// If a message to retry the call is received

case H_REQUEST_REDIALING_EMERGENCY_CALL:

// If Car Play is available, try calling Car Play

if(mCarPlayStateUpdateService.carPlayDipoStatus() == DIPO_STAT_STARTED) {

requestAcnCarPlayCalling();

}

// Otherwise, try calling via Bluetooth.

else {

requestAcnBluetoothCalling();

}

break;

}

}

4.2. Attempt to make a call using wireless connection technology (S240)

If a device supporting Bluetooth Handsfree is connected, call the accident report center using Bluetooth.

4.2.1 Notification of accident to acquaintances before connecting the call

If the Bluetooth Handsfree connection status checked using the 'HEALTH_STATUS_CFM' message is connected, the accident report is first made to the Vehicle Accident Report Center using the Bluetooth Handsfree service via SMS. This is to prepare in case the driver in the vehicle loses consciousness. In this case, 'SMS_SUPPORT_REQ' is transmitted to the Bluetooth Stack 115 to request confirmation of whether the connected device supports the SMS transmission function. The in-vehicle terminal 110 may receive 'SMS_SUPPORT_CFM' to know the available SMS memory area and the type of SMS (PDU binary or text). If the connected device does not support it, SMS transmission is omitted.

When the connected device supports the SMS service, the in-vehicle terminal 110 acquires a list of calls existing in the connected device. In this case, the 'PBAPC_DOWNLOAD_PHONEBOOK_REQ' message is transmitted, and 'PHONEBOOK_TYPE_INCOMING_CALL', 'PHONEBOOK_TYPE_OUTGOING_CALL', and 'PHONEBOOK_TYPE_MISSED_CALL' are passed as parameters to obtain the incoming, outgoing, and missed call history from the phone.

An SMS/MMS message containing the accident details is transmitted using the call list obtained in the above step. In this case, after sorting the call list in the order of the most recent time, the phone number to which the SMS/MMS message is sent is selected by selecting 5 different phone numbers. Transmits the 'SMS_SEND_REQ' message including the mode (PDU or Text) information provided by the connected device, data size, and accident guidance message data. In the accident information message data, the recipient's phone number, an accident information message, the vehicle's latitude and longitude coordinates, and the time of the accident are recorded.

If the SMS message transmission fails, it is retried only once. In this case, the result value of each 'SMS_SEND_CFM' received from the Bluetooth Stack 115 for a total of 5 'SMS_SEND_REQ' transmissions is not 'RESULT_SUCESS'. In this case, after waiting 5 seconds, the failed 'SMS_SEND_REQ' is retransmitted only once.

If the Bluetooth Handsfree connection status checked using the 'HEALTH_STATUS_CFM' message is connected, make a call to the Vehicle Accident Report Center using Bluetooth Handsfree. In this case, the phone number (ex. 911) of the vehicle accident report center is stored in 'OUTGOING_CALL_REQ' and transmitted to the Bluetooth Stack (115).

If the Bluetooth connection is disconnected before making a call, go back to step 3 and try automatic connection. In this case, since the 'SERVICE_DISCONNECT_IND' notification message is transmitted from the Bluetooth Stack 115 to the in-vehicle terminal 110 , the Handsfree connection disconnection can be detected.

8 is a conceptual diagram illustrating a flow of an SMS Support message.

Message (Parameter)

- SMS_SUPPORT_REQ ( Connection ID )

- SMS_SUPPORT_CFM (Result, Connection ID, Supported Memory, Mode )

It is checked whether the connection device supports the SMS reception function using the AT command (351). Then, the available SMS Memory area and SMS types (PDU, Text) can be found (352).

9 is a conceptual diagram illustrating a flow of an SMS Send message.

Message (Parameter)

- SMS_SEND_REQ ( Connection ID, Mode, SMS Size, Sequence, Length, Data, )

- SMS_SEND_CFM (Result, Connection ID)

The CPU block 113 transmits an SMS of a PDU or Text using SMS_SEND_REQ (361). Then, the Bluetooth Stack 115 transmits a message in response thereto (362).

10 is a conceptual diagram illustrating a flow of a Phonebook Download message.

Message (Parameter)

- PBAPC_DOWNLOAD_PHONEBOOK_REQ (Connection ID, Repository, Path, Start, End, Format,

AT-C charset, AT-C charset data)

- PBAPC_PHONEBOOK_SIZE_IND (Connection ID, Size, Index Start, Index End,

Supported AT-C charset length, Supported AT-C charset data)

- PBAPC_PHONEBOOK_DATA_IND (Connection ID, Method, Length of Data, Data )

- PBAPC_DOWNLOAD_PHONEBOOK_CFM (Result, Connection ID)

The Bluetooth Stack 115 downloads the Phonebook stored in the phone (or SIM) (374). The CPU block 113 parses and processes the received data. If the connection id of PBAPC_DOWNLOAD_PHONEBOOK_REQ(371) corresponds to PBAPS, try to download the phonebook using PBAP, and if it corresponds to HFAG, use the AT Command method (372, 373).

11 is a conceptual diagram illustrating the flow of an outgoing call message.

Message (Parameter)

- OUTGOING_CALL_REQ ( Connection ID, Type of call, Number )

- OUTGOING_CALL_CFM (Result, Connection ID)

Various types of outgoing calls may be requested by transmitting OUTGOING_CALL_REQ from the CPU block 113 (381). The Bluetooth Stack 115 responds by sending an OUTGOING_CALL_CFM message (382).

4.2.2 Dial-up Attempts

If the mobile communication terminal 120 is already on a call, the phone number is checked and compared with the phone number of the vehicle accident reporting center. In this case, if the Handsfree status of 'HEALTH_STATUS_CFM' is 'INCOMING_CALL', 'OUTGOING_CALL', 'ACTIVE_CALL', 'WAITING_CALL', 'MULTI_ACTIVE_CALL', 'HELD_CALL', 'ACTIVE_AND_HOLD' or 'DEMULTI_HEL' already in a call. Alternatively, it can also be known as 'CALL_STATUS_EVENT_IND'. In the case of a call, 'GET_CURRENT_CALLS_REQ' is transmitted to the Bluetooth stack 115, and the phone number being called can be obtained in ASCII code through the response 'HFP_CURRENT_CALLS_IND'.

If the two numbers compared are not the same, the current call is forcibly terminated and the user is notified through a voice guidance and display device that a call is made to the vehicle accident report center. After that, it waits for the user's input, and if there is no input for a certain period of time, the current call is forcibly terminated and a call is made to the vehicle accident report center. In this case, 'HFP_TERMINATE_CALL_REQ' is transmitted to the Bluetooth Stack 115 to request termination of the call. Check 'CALL_STATUS_EVENT_IND' every 3 seconds, and if 'CALL_EVENT_NO_CALL' is not received, 'HFP_TERMINATE_CALL_REQ' is sent again to disconnect the call.

When a call is made to the mobile communication terminal 120 connected through Bluetooth after a call is connected to the vehicle accident report center, the incoming call is rejected (rejected call) in order to maintain the current automatic accident report call. In this case, the value of 'CALL_STATUS_EVENT_IND' is received as 'WAITING_CALL'. In this case, the incoming call may be rejected by transmitting 'HFP_REJECT_CALL_REQ' to the Bluetooth stack 115 .

After a call is connected to the vehicle accident report center, some key input is blocked so that the call is not terminated by the user's mistake or unintentional action. However, it does not block the means by which the user can end a call, or a function that helps the user to determine the current location, vehicle status, and the like. In this case, AV and other entertainment related keys are blocked, but the 'Cancel' key on the GUI, the 'Call end' key on the steering wheel, and the navigation related keys are not blocked.

When the call end key is input, it is determined that the call is terminated by the user's intention and the automatic accident report service is terminated.

12 is a conceptual diagram illustrating a flow of a Terminate Call message.

Message (Parameter)

- TERMINATE_CALL_REQ ( Connection ID )

- TERMINATE_CALL_CFM (Result, Connection ID)

The CPU block 113 may transmit TERMINATE_CALL_REQ to request termination of the call ( 391 ). The Bluetooth Stack 115 responds by sending a TERMINATE_CALL_CFM message (392).

13 is a conceptual diagram illustrating a flow of a Get Current Calls message.

Message (Parameter)

- GET_CURRENT_CALLS_REQ (Connection ID)

- GET_CURRENT_CALLS_IND (Connection ID, Call Index, Call Direction, Call Status, Call Multiparty, Call Number)

- GET_CURRENT_CALLS_CFM (Result, Connection ID)

In order to know the current call information, the CPU block 113 transmits a GET_CURRENT_CALLS_REQ message to the Bluetooth Stack 115 (401). Accordingly, the Bluetooth Stack 115 transmits the current call information to the CPU block 113 through the GET_CURRENT_CALLS_IND message (402). When all call information is transmitted, the Bluetooth Stack 115 transmits a GET_CURRENT_CALLS_CFM message to the CPU block 113 (403).

14 is a conceptual diagram illustrating a flow of a Call Status Indication message.

Message (Parameter)

- CALL_STATUS_EVENT_IND (Connection ID, Status)

During a call, the Bluetooth Stack 115 notifies the current CALL state change using the CALL_STATUS_EVENT_IND message (411).

4.2.3 Telephone Connection Retry (S225, S230)

After making a call using Bluetooth, a response message corresponding to a call failure may be given depending on the state of the phone. If you receive such a message, it will retry once or several times. In this case, the value of 'OUTGOING_CALL_CFM', which is a response message to 'OUTGOING_CALL_REQ' transmitted to the Bluetooth Stack 115, is 'RESULT_FAIL', 'RESULT_BUSY', 'RESULT_NOT_READY_STATE' or 'RESULT_TIMEOUT'. In this case, it waits for 5 seconds so that the operation status of the current Bluetooth-enabled device is cleaned up to some extent, and then transmits 'OUTGOING_CALL_REQ' again.

After making a call using Bluetooth, if the Bluetooth call status does not change to an active call within a certain period of time, retry once or several times. In this case, the value of 'CALL_STATUS_EVENT_IND' does not become 'CALL_EVENT_ACTIVE_CALL' within 20 seconds. If 'CALL_STATUS_EVENT_IND' maintains 'CALL_EVENT_NO_CALL', 'OUTGOING_CALL_REQ' is transmitted again. In addition, if a call connection is being attempted, such as 'CALL_EVENT_INCOMING_CALL', it is regarded as an abnormal state of the mobile communication network, and 'HFP_TERMINATE_CALL_REQ' is sent to the Bluetooth Stack 115 to end the current call. .

If a call is made using Bluetooth and the Bluetooth call status has also become an active call, but the call is terminated within a specific time for reasons other than the user's intention, it is retried once or several times. In this case, after receiving 'CALL_EVENT_ACTIVE_CALL' as the value of 'CALL_STATUS_EVENT_IND', the 'SERVICE_DISCONNECT_IND' notification message and 'CALL_EVENT_NO_CALL' as the value of 'CALL_STATUS_EVENT_IND' are received within 5 seconds. Considering this case as an abnormal state of the mobile communication network, 'OUTGOING_CALL_REQ' is sent again after 5 seconds to retry the call connection.

In the case of retrying a call using Bluetooth, it waits for a certain period of time and waits for conditions due to a previous call failure to be cleared before retrying. In this case, a timer of 5 seconds is set to retry when a time-out event occurs.

In the case of retrying to make a call using Bluetooth, the driver is notified that the service is being retryed through a voice guidance and display device.

If a call is attempted again using Bluetooth but the call fails, the driver is notified of service connection failure through voice guidance and a display device.

When the user ends the call through the vehicle terminal or other manipulation, it is determined that the user's intention to end the call is not retryed. In this case, the 'Cancel' button on the GUI or the 'Call end' key on the steering wheel key is pressed.

An embodiment of the present invention has been described above with reference to FIGS. 1 to 14 . Hereinafter, a preferred embodiment of the present invention that can be inferred from such an embodiment will be described.

15 is a block diagram schematically illustrating an apparatus for reporting a vehicle accident according to a preferred embodiment of the present invention.

The vehicle accident reporting apparatus 500 reports a vehicle accident using a phone terminal, and has the same concept as the in-vehicle terminal 110 described with reference to FIGS. 1 and 2 .

15 , the vehicle accident reporting device 500 includes a power supply unit 510 , a main control unit 520 , an accident occurrence determination unit 530 , a wired connection determination unit 540 , a wireless connection execution unit 550 , and a vehicle accident and a reporting unit 560 .

The power supply unit 510 performs a function of supplying power to each component constituting the vehicle accident reporting device 500 . The main control unit 520 performs a function of controlling the overall operation of each component constituting the vehicle accident reporting device 500 . Considering that the vehicle accident reporting device 500 is provided in the AVN system, the power supply unit 510 and the main control unit 520 may not be provided in the present embodiment.

The accident occurrence determination unit 530 performs a function of determining whether an accident has occurred in the vehicle.

The accident occurrence determination unit 530 determines whether a predetermined signal is input according to an emergency call button input by the driver of the vehicle, whether a signal for commanding the deployment of the airbag in the vehicle is input, and the amount of change in the vehicle's load It may be determined whether an accident has occurred in the vehicle based on at least one of whether the reference change amount or more and whether the vehicle inclination is greater than or equal to the reference inclination.

When determining whether an accident has occurred in the vehicle based on whether the load change amount of the vehicle is greater than or equal to the reference change amount, the accident occurrence determination unit 530 may include a vehicle load detection unit, a vehicle load change amount calculation unit, and a vehicle accident determination unit have.

The vehicle load detection unit performs a function of detecting a vehicle load. The vehicle load detector may detect the load of the vehicle by using at least one sensor of a strain gauge and a load cell. The sensor may include at least one first sensor positioned at the front of the vehicle and at least one second sensor positioned at the rear of the vehicle. The first sensor may be attached to a location that can measure the weight of the vehicle, such as a front wheel axle and a front wheel of the vehicle, and the second sensor is attached to a location that can measure the weight of the vehicle, such as a rear wheel axle and a rear wheel of the vehicle can be

The vehicle load change calculation unit collects the load detected by the vehicle load detection unit and calculates the vehicle load change amount for a predetermined time.

The vehicle accident determination unit performs a function of determining whether an accident has occurred in the vehicle by comparing the load change calculated by the vehicle load change amount calculating unit with the reference change amount. The vehicle accident determination unit determines that an accident has occurred in the vehicle when the load change is greater than or equal to the reference change amount, and determines that no accident has occurred in the vehicle when the load change is less than the reference change amount.

The vehicle load detection unit may detect the load of the vehicle by using each sensor mounted at different positions of the vehicle. In this case, the accident occurrence determination unit 530 may further include an abnormal sensor extraction unit.

The abnormal sensor extractor performs a function of extracting a sensor that does not operate normally by comparing the loads of the vehicle detected from each sensor.

When the accident occurrence determination unit 530 further includes an abnormal sensor extraction unit, the vehicle load change calculation unit calculates the vehicle load change amount by using the vehicle load detected by the remaining sensors except for the sensor that does not normally operate.

Meanwhile, the accident occurrence determination unit 530 may further include at least one of a driving information detection unit, a collision determination unit, a position detection unit, and a door lock detection unit.

The driving information detecting unit performs a function of detecting driving information of the vehicle every predetermined time. In this embodiment, driving information is a concept that encompasses various types of information related to driving of a vehicle, information on operating states of various devices mounted on the vehicle, and the like.

The driving information detector may detect gear state information of a transmission mounted on the vehicle or a current speed of the vehicle as the driving information.

The vehicle accident determination unit performs a function of additionally determining whether a vehicle accident has occurred based on the driving information of the vehicle.

The vehicle accident determining unit may determine that an accident has occurred in the vehicle when the gear state information is in a mode other than the parking (P) mode and the neutral (N) mode and the current speed is less than or equal to the first reference speed. In addition, the vehicle accident determination unit may determine that an accident has occurred in the vehicle when the gear state information or the current speed is not detected. In the above, the first reference speed may be, for example, 0.

Meanwhile, considering a case in which the speed is momentarily changed to 0 km, the driving information detecting unit and the vehicle accident determining unit may be driven as follows.

That is, the driving information detecting unit may detect the current time together when detecting the current speed. And when the current speed is 0, the difference value between the previous speed and the current speed is greater than or equal to the first reference value, and when the difference value between the previous time and the current time detected together with the previous speed is less than or equal to the second reference value, the vehicle It can be concluded that an accident has occurred in

Meanwhile, the vehicle accident determination unit may be operated when the gear state information is in a mode other than the parking (P) mode and the neutral (N) mode and the current speed is equal to or greater than the second reference speed. In this case, the second reference speed may be, for example, 0.

The collision determination unit performs a function of determining whether a collision exists between the vehicle and an object located outside. In this case, the vehicle accident determination unit may determine whether or not an accident of the vehicle has occurred according to whether a collision has occurred. When it is determined that there is a collision between the vehicle and the object, the vehicle accident determination unit determines that an accident has occurred in the vehicle.

The collision determination unit may determine whether there is a collision by using at least one of a camera for photographing the front of the vehicle, a radar for detecting an object from each side of the vehicle, and an acceleration sensor for measuring the acceleration of the vehicle.

When determining whether or not a collision occurs using a camera, the collision determination unit is the first reference distance or less from the image acquired by the camera to the object, or the image is not acquired by the camera for a predetermined time, or When the detection signal for the vehicle is not detected, it may be determined that there is a collision between the vehicle and the object.

When determining whether a collision occurs using the radar, the collision determination unit causes a collision between the vehicle and the object when the distance to the object obtained by the radar is less than or equal to the second reference distance, or when a detection signal for the radar is not detected. It can be judged that there is

When the acceleration sensor is used, the collision determination unit may determine that there is a collision between the vehicle and the object when the intensity of the impact measured by the acceleration sensor is equal to or greater than the reference intensity.

The position detector detects the position of the vehicle and performs a function of measuring the time when the position is detected.

The door lock detection unit performs a function of detecting information on a door lock state of the vehicle.

In the above case, the vehicle accident determination unit sends the vehicle to the vehicle if the location of the vehicle detected at the previous time and the location of the vehicle detected at the current time are the same, and the door unlock information of the vehicle is not detected for a predetermined time at the previous time and the current time. It can be concluded that an accident has occurred.

When determining whether an accident has occurred in the vehicle based on whether the slope of the vehicle is equal to or greater than the reference slope, the accident occurrence determination unit 530 may include a slope obtaining unit, a vehicle signal obtaining unit, and a vehicle accident determining unit.

The inclination acquiring unit performs a function of acquiring the inclination of the vehicle. The inclination acquiring unit may acquire the inclination of the vehicle by using a three-axis acceleration sensor or a gyro sensor.

The vehicle signal acquisition unit performs a function of acquiring a signal by a vehicle device.

The vehicle signal acquisition unit is a signal from the vehicle device, a signal for whether the vehicle's airbag is deployed, a signal for the starting state of the vehicle, a signal for the speed of the vehicle, a signal for the shift state of the vehicle, and a signal for whether the vehicle battery is removed , and signals obtained by photographing the front or interior of the vehicle may be obtained.

The vehicle accident determination unit performs a function of determining whether an accident has occurred in the vehicle based on the inclination of the vehicle and a signal from the vehicle device.

When it is determined that the inclination of the vehicle is equal to or greater than the reference inclination, the vehicle accident determination unit may determine whether an accident has occurred in the vehicle based on a signal from the vehicle device.

The vehicle accident determination unit may determine that an accident has occurred in the vehicle when a signal to deploy the vehicle's airbag is obtained as a signal for whether the vehicle's airbag is deployed.

The vehicle accident determination unit obtains a signal that the vehicle's ignition is on as a signal for the starting state of the vehicle even if a signal to deploy the vehicle's airbag is not obtained as a signal for whether the vehicle's airbag is deployed When a signal that the speed of is 0 is obtained and a signal indicating that the transmission of the vehicle is located in a mode other than the P (Parking) mode is obtained as a signal for the shift state of the vehicle, it may be determined that an accident has occurred in the vehicle.

The vehicle accident determination unit obtains a signal indicating that the vehicle's ignition is off as a signal for the starting state of the vehicle and a signal indicating that the vehicle's transmission is in P mode as a signal for the shifting state of the vehicle, or a signal indicating that the vehicle's ignition is off If is acquired before the signal that the transmission of the vehicle is located in the P mode, it may be determined that an accident has occurred in the vehicle.

The vehicle accident determination unit may determine that an accident has occurred in the vehicle when a signal indicating that the voltage supplied from the vehicle battery for starting the vehicle is LOW is obtained as a signal for whether the vehicle battery is removed.

The vehicle accident determination unit may determine an accident type of the vehicle, such as a vehicle overturn, based on the inclination of the vehicle.

When it is determined by the accident occurrence determining unit 530 that an accident has occurred in the vehicle, the wired connection determination unit 540 determines whether the terminal to which the phone function is assigned is connected to the vehicle by wire.

Wired connection determination unit 540 may determine whether the terminal to which the phone function is granted is connected to the vehicle by wire by determining whether there is a terminal provided with a phone function among terminals connected to the vehicle by a USB method. have.

When it is determined that there is a terminal to which a phone function is assigned among terminals connected to the vehicle by the USB method, the wired connection determination unit 540 determines that the terminal to which the phone function is assigned is connected to the vehicle by wire. On the other hand, when it is determined that there is no terminal to which the phone function is assigned among terminals connected to the vehicle by the USB method, the wired connection determination unit 540 determines that the terminal to which the phone function is assigned is not connected to the vehicle by wire.

The wired connection determination unit 540 may determine whether there is a terminal to which the phone function is granted among terminals connected to the vehicle through a USB method, based on information about the terminal to which the phone function is granted.

The wired connection determination unit 540 may determine whether there is a protocol usable in the terminal to which the phone function is granted, among protocols supporting the call function in the vehicle, based on information about the terminal to which the phone function is granted.

The wired connection determination unit 540 may use a terminal vendor ID, a terminal manufacturer ID, and the like as information about a terminal to which a phone function is granted.

When it is determined by the wired connection determining unit 540 that the terminal to which the telephone function is assigned is not connected to the vehicle by wire, the wireless connection execution unit 550 performs a function of wirelessly connecting the terminal to which the telephone function is assigned to the vehicle. carry out

The wireless connection execution unit 550 may wirelessly connect the terminal to which the phone function is granted to the vehicle using Bluetooth.

The wireless connection execution unit 550 may determine whether the terminal to which the telephone function is granted supports the hands-free function before wirelessly connecting the terminal to which the telephone function is granted to the vehicle.

When it is determined that the terminal to which the phone function is assigned supports the hands-free function, the wireless connection execution unit 550 wirelessly connects the terminal to which the phone function is assigned to the vehicle. On the other hand, if it is determined that the terminal to which the phone function is assigned does not support the hands-free function, the wireless connection execution unit 550 does not wirelessly connect the terminal to which the phone function is assigned to the vehicle.

The wireless connection execution unit 550 may determine whether another terminal is wirelessly connected to the vehicle using a predetermined wireless connection method before wirelessly connecting the terminal to which the phone function is assigned to the vehicle.

If it is determined that the other terminal is not wirelessly connected to the vehicle using a predetermined wireless connection method (eg, Bluetooth), the wireless connection execution unit 550 is a terminal to which a phone function is assigned using the above-described wireless connection method. connect wirelessly to the vehicle. On the other hand, if it is determined that the other terminal is wirelessly connected to the vehicle using the wireless connection method, the wireless connection execution unit 550 terminates the wireless connection between the other terminal and the vehicle and then uses the wireless connection method. A terminal with a phone function is wirelessly connected to the vehicle.

When it is determined that the other terminal is wirelessly connected to the vehicle using the wireless connection method, the wireless connection execution unit 550 cancels the wireless connection between the other terminal and the vehicle, and then performs a telephone function using the wireless connection method. This granted terminal can be wirelessly connected to the vehicle.

In this embodiment, the above-described functions of the wired connection determining unit 540 and the wireless connection executing unit 550 consider that a wired connection is more stable than a wireless connection.

The vehicle accident report unit 560 uses the terminal to which the telephone function is granted when the terminal to which the telephone function is granted by the wired connection execution unit (not shown) or the wireless connection execution unit 550 is connected to the vehicle by wire or wirelessly. It performs the function of reporting an accident to PSAP (Public Safety Answering Point).

The vehicle accident reporting unit 560 is a call between the terminal to which the phone function is granted and the PSAP when the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated within a predetermined time. The connection may be retried.

The vehicle accident reporting unit 560 may measure a call connection time between the terminal to which the phone function is granted and the PSAP when a call connection between the terminal to which the phone function is granted and the PSAP is successful.

The vehicle accident reporting unit 560 is at least one selected according to the priority from among the phone numbers stored in advance when the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated. You can report an accident based on your phone number.

On the other hand, when it is determined that the terminal to which the phone function is assigned is connected to the vehicle by wire, the wired connection determination unit 540 determines whether there is a protocol available in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle. can judge

If it is determined that there is a protocol usable in the terminal to which the telephone function is assigned among protocols supporting the call function in the vehicle, the vehicle accident reporting unit 560 reports an accident to the PSAP using the terminal to which the telephone function is assigned.

On the other hand, if it is determined that there is no protocol available to the terminal to which the phone function is assigned among protocols supporting the call function in the vehicle, the wired connection determination unit 540 determines that the terminal to which the phone function is assigned is not connected to the vehicle by wire. it is determined, and it is determined whether the terminal to which the phone function is granted is wirelessly connected to the vehicle. If it is determined that there is no protocol available in the terminal to which the phone function is assigned among protocols supporting the call function in the vehicle, the wireless connection execution unit 550 wirelessly connects the terminal to which the phone function is assigned to the vehicle.

Next, an operation method of the vehicle accident reporting device 500 will be described. 16 is a flowchart schematically illustrating a vehicle accident reporting method according to a preferred embodiment of the present invention.

First, the accident occurrence determination unit 530 determines whether an accident has occurred in the vehicle (S610).

If it is determined that an accident has occurred in the vehicle, the wired connection determination unit 540 determines whether the terminal to which the phone function is assigned is connected to the vehicle by wire ( S620 ).

If it is determined that the terminal to which the telephone function is assigned is not connected to the vehicle by wire, the wireless connection execution unit 550 wirelessly connects the terminal to which the telephone function is assigned to the vehicle (S630).

When the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly (S620, S630), the vehicle accident reporting unit 560 reports the accident to the Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned. (S640).

Even if all the components constituting the embodiment of the present invention described above are described as being combined or operated in combination, the present invention is not necessarily limited to this embodiment. That is, within the scope of the object of the present invention, all the components may operate by selectively combining one or more. In addition, although all of the components may be implemented as one independent hardware, some or all of the components are selectively combined to perform some or all of the functions of one or a plurality of hardware programs It may be implemented as a computer program having In addition, such a computer program is stored in a computer readable media such as a USB memory, a CD disk, a flash memory, etc., read and executed by a computer, thereby implementing the embodiment of the present invention. The computer program recording medium may include a magnetic recording medium, an optical recording medium, a carrier wave medium, and the like.

In addition, all terms including technical or scientific terms have the same meaning as commonly understood by one of ordinary skill in the art to which the present invention belongs, unless otherwise defined in the detailed description. Terms commonly used, such as those defined in the dictionary, should be interpreted as being consistent with the contextual meaning of the related art, and are not interpreted in an ideal or excessively formal meaning unless explicitly defined in the present invention.

The above description is merely illustrative of the technical idea of the present invention, and various modifications, changes, and substitutions are possible within the range that does not depart from the essential characteristics of the present invention by those of ordinary skill in the art to which the present invention pertains. will be. Accordingly, the embodiments disclosed in the present invention and the accompanying drawings are for explaining, not limiting, the technical spirit of the present invention, and the scope of the technical spirit of the present invention is not limited by these embodiments and the accompanying drawings. . The protection scope of the present invention should be interpreted by the following claims, and all technical ideas within the scope equivalent thereto should be construed as being included in the scope of the present invention.

Claims (14)

An accident occurrence determination unit for determining whether an accident has occurred in the vehicle;
a wired connection determination unit configured to determine whether a terminal to which a phone function is assigned is connected to the vehicle by wire when it is determined that the accident has occurred in the vehicle;
a wireless connection execution unit for wirelessly connecting the terminal to which the phone function is granted to the vehicle when it is determined that the terminal to which the phone function is assigned is not connected to the vehicle by wire; and
When the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly, including a vehicle accident reporting unit that reports the accident to a Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned,
The wireless connection execution unit determines whether another terminal is wirelessly connected to the vehicle using a predetermined wireless connection method before wirelessly connecting the terminal to which the phone function is assigned to the vehicle. A vehicle accident reporting device using The method of claim 1,
The wired connection determining unit determines whether there is a terminal provided with the phone function among terminals connected to the vehicle in a USB manner to determine whether the terminal provided with the phone function is connected to the vehicle by wire Vehicle accident reporting device using a phone terminal, characterized in that. 3. The method of claim 2,
When it is determined that the terminal to which the phone function is assigned is connected to the vehicle by wire, the wired connection determination unit determines whether there is a protocol available in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle. Vehicle accident reporting device using a phone terminal, characterized in that the determination. 4. The method of claim 3,
When it is determined that there is no protocol available in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle, the wireless connection execution unit wirelessly connects the terminal to which the phone function is granted to the vehicle A vehicle accident reporting device using a telephone terminal. 4. The method of claim 3,
The wired connection determining unit determines whether there is a protocol usable in the terminal to which the phone function is granted, among protocols supporting the call function in the vehicle, based on the information on the terminal to which the phone function is granted A vehicle accident reporting device using a telephone terminal. The method of claim 1,
The wireless connection execution unit using a phone terminal, characterized in that before wirelessly connecting the terminal to which the phone function is granted to the vehicle, it is determined whether the terminal to which the phone function is granted supports a hands-free function. Vehicle Accident Reporting Device. delete The method of claim 1,
When it is determined that the other terminal is wirelessly connected to the vehicle using the wireless connection method, the wireless connection execution unit terminates the wireless connection between the other terminal and the vehicle and then uses the wireless connection method to perform the phone function A vehicle accident reporting device using a telephone terminal, characterized in that wirelessly connecting the given terminal to the vehicle. The method of claim 1,
When the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated within a predetermined time, the vehicle accident report unit and the terminal to which the phone function is granted and the PSAP A vehicle accident reporting device using a phone terminal, characterized in that retrying a call connection between PSAPs. An accident occurrence determination unit for determining whether an accident has occurred in the vehicle;
a wired connection determination unit configured to determine whether a terminal to which a phone function is assigned is connected to the vehicle by wire when it is determined that the accident has occurred in the vehicle;
a wireless connection execution unit for wirelessly connecting the terminal to which the phone function is granted to the vehicle when it is determined that the terminal to which the phone function is assigned is not connected to the vehicle by wire; and
When the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly, including a vehicle accident reporting unit that reports the accident to a Public Safety Answering Point (PSAP) using the terminal to which the phone function is assigned,
The vehicle accident reporting unit is a vehicle accident reporting device using a phone terminal, characterized in that when the call connection between the terminal to which the phone function is granted and the PSAP is successful, measures the call connection time between the terminal to which the phone function is granted and the PSAP . The method of claim 1,
When the call connection between the terminal to which the phone function is granted and the PSAP fails or the call connection between the terminal to which the phone function is granted and the PSAP is terminated, the vehicle accident reporting unit at least one selected according to priority from among the phone numbers stored in advance Vehicle accident reporting device using a phone terminal, characterized in that for reporting the accident based on the phone number of. The method of claim 1,
The accident occurrence determining unit determines whether a predetermined signal is input by the driver of the vehicle, whether a signal for commanding deployment of the airbag in the vehicle is input, whether the load change amount of the vehicle is greater than or equal to a reference change amount, and Vehicle accident reporting apparatus using a phone terminal, characterized in that it is determined whether the accident has occurred in the vehicle based on at least one of whether the inclination is equal to or greater than a reference inclination. determining whether an accident has occurred in the vehicle;
determining whether a terminal to which a phone function is assigned is connected to the vehicle by wire when it is determined that the accident has occurred in the vehicle;
when it is determined that the terminal to which the phone function is assigned is not connected to the vehicle by wire, wirelessly connecting the terminal to which the phone function is assigned to the vehicle; and
Comprising the step of reporting the accident to PSAP (Public Safety Answering Point) using the terminal to which the phone function is granted when the terminal to which the phone function is assigned is connected to the vehicle by wire or wirelessly,
The step of determining whether the connection is made by determining whether there is a terminal provided with the phone function among terminals connected to the vehicle by a USB method is connected to the vehicle by wire to determine whether or not
When it is determined that the terminal to which the phone function is granted is connected to the vehicle by wire, it is determined whether there is a protocol usable in the terminal to which the phone function is granted among protocols supporting the call function in the vehicle. How to report a car accident using a telephone terminal.
delete

Images