Onboard apparatus and discharge method

The in-vehicle device addresses the challenge of identifying accident vehicles by ejecting RFID tags upon detection, ensuring reliable identification and evidence preservation, even in poor communication conditions.

JP2025131291APending Publication Date: 2025-09-09DENSO TEN LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2024028946
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2024-02-28
Publication Date
2025-09-09

AI Technical Summary

Technical Problem

Conventional methods struggle to reliably identify vehicles involved in accidents, especially when exterior parts with embedded RFID tags are not destroyed, and communication environments are poor.

Method used

An in-vehicle device with an ejection mechanism that actively releases storage media, such as RFID tags, upon detecting an accident and loss of communication, ensuring the tags are left at the scene to provide identifying information.

Benefits of technology

The solution ensures reliable vehicle identification by scattering RFID tags at the accident site, even if the vehicle is undamaged, and enhances visibility and evidence preservation, particularly in challenging environments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2025131291000001_ABST
    Figure 2025131291000001_ABST
Patent Text Reader

Abstract

To reliably identify an accident vehicle.SOLUTION: An onboard apparatus 30 in accordance with an embodiment includes: an RFID tag 40 that stores information on a vehicle V; dischargers 311, 312, and 313 that accommodate the RFID tag 40; and a controller 34 that controls each of the dischargers. When occurrence of an accident is detected based on data of a sensor included in the vehicle V and the vehicle V and a center cannot communicate with each other, the controller 34 forces the dischargers to discharge the RFID tags 40.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to an in-vehicle device and an ejection method. [Background technology]

[0002] One method is to narrow down the vehicles involved in an accident based on parts and paint found at the scene of the accident. This method is time-consuming and makes it difficult to identify the vehicle. Furthermore, in mountainous areas where the communication environment is poor, it is difficult to detect accidents based on vehicle communications.

[0003] In response to this, a method has been proposed in which an RFID (Radio Frequency Identification) tag recording data such as vehicle body information is embedded in an exterior part of a vehicle, such as a headlight cover (see, for example, Patent Document 1). According to the method described in Patent Document 1, it becomes possible to identify a vehicle by reading an RFID tag that has fallen off in the event of an accident. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2006-232029 Summary of the Invention [Problem to be solved by the invention]

[0005] However, conventional technologies may not be able to identify the vehicle involved in the accident. For example, in the technology described in Patent Document 1, the RFID tag will not fall off unless the exterior part in which it is embedded is destroyed. Therefore, even if a vehicle is involved in a collision accident, if the exterior part is not destroyed, the RFID tag will not fall off and the vehicle cannot be identified.

[0006] The present invention has been made in view of the above, and has an object to provide an in-vehicle device and an ejection method that can more reliably identify an accident vehicle. [Means for solving the problem]

[0007] The in-vehicle device according to the present invention includes an ejection device that stores a storage medium that stores vehicle information, and a controller that controls the ejection device. The controller causes the ejection device to eject the storage medium when an accident is detected based on data from a sensor provided in the vehicle and communication between the vehicle and a communication destination is not possible. [Effects of the Invention]

[0008] The in-vehicle device of the present invention actively ejects the storage medium storing vehicle information when an accident is detected by a sensor or the like, taking into consideration the communication environment. Therefore, the in-vehicle device can leave the storage medium at the accident site even if the container containing the storage medium is not destroyed. As a result, it is possible to more reliably identify the accident vehicle. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a vehicle according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of an RFID tag. [Figure 3] FIG. 3 is a diagram illustrating an example of the configuration of an RFID tag. [Figure 4] FIG. 4 is a diagram illustrating the arrangement of the outlets. [Figure 5] FIG. 5 is a flowchart showing a processing procedure of the in-vehicle device according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The following detailed description of embodiments of the in-vehicle device and the ejection method disclosed herein will be given with reference to the accompanying drawings. Note that the present invention is not limited to the following embodiments.

[0011] 1 is a diagram showing an example of the configuration of a vehicle according to an embodiment. As shown in FIG. 1, the vehicle V includes an ECU (Electronic Control Unit) 10, a sensor group 20, and an on-vehicle device 30.

[0012] The ECU 10 controls the entire vehicle V. The ECU 10 also controls a communication module and can communicate with a center via communication means such as a telephone line or the Internet. The ECU 10 also detects the occurrence of an accident of the vehicle V based on data (sensor values) from sensors included in the sensor group 20.

[0013] The sensor group 20 includes a plurality of cameras, a plurality of microphones, an acceleration sensor, a GPS sensor, etc. Some of the cameras included in the sensor group 20 may be provided in a drive recorder.

[0014] The in-vehicle device 30 has an RFID tag 40, a discharge device 311, a discharge device 312, and a discharge device 313. The discharge devices 311, 312, and 313 each store a plurality of RFID tags 40. Note that the discharge devices 311, 312, and 313 may be referred to as discharge devices 31 without distinction. Furthermore, the in-vehicle device 30 has a controller 34 and a memory 35.

[0015] The ejection device 311 has an ejection port 321 and a writing unit 331. The ejection device 312 has an ejection port 322 and a writing unit 332. The ejection device 313 has an ejection port 323 and a writing unit 333.

[0016] The discharge devices 311, 312, and 313 operate in the same manner. Therefore, the operation of the discharge device 311 will be described, and the description of the operations of the discharge devices 312 and 313 may be omitted.

[0017] The controller 34 reads and executes a program stored in the memory 35. The controller 34 is a central processing unit (CPU), a digital signal processor (DSP), a field programmable gate array (FPGA), a graphics processing unit (GPU), a system on a chip (SoC), or the like.

[0018] The controller 34 may be a single processor, a multiprocessor configuration, or a multicore configuration having multiple cores in a single chip connected via a single socket.

[0019] The memory 35 is a storage medium such as an eMMC (embedded multi media card), etc. The memory 35 functions as a ROM (read only memory) or a RAM (random access memory).

[0020] The controller 34 causes the ejection device 31 to eject the RFID tag 40 when an accident is detected based on data from a sensor provided in the vehicle V and communication between the vehicle V and the communication destination is not possible. As a result, when an accident occurs, the RFID tags 40 storing information about the vehicle V are scattered on the ground, leaving evidence at the accident scene, making it possible to verify the accident after the accident even if communication with the center is not possible. If communication with the center is possible, accident verification is possible without scattering the RFID tags 40, so the number of RFID tags 40 can be saved by not scattering them.

[0021] The RFID tag 40 also stores information identifying the owner of the vehicle V, information identifying the vehicle V, images captured by a camera installed on the vehicle V, the speed of the vehicle V, and the acceleration of the vehicle V. As a result, detailed information about the accident can be obtained by reading the scattered RFID tags 40.

[0022] When the controller 34 receives a signal from the ECU 10 indicating that an accident has occurred and that communication with the center is not possible, the controller 34 causes the ejection device 31 to eject the RFID tag 40. Therefore, the controller 34 does not need to detect the occurrence of an accident or determine whether communication is possible.

[0023] Furthermore, regardless of whether an impact has occurred, the ECU 10 can detect the occurrence of an accident based on the video captured by the camera provided in the vehicle V and the audio collected by the microphone provided in the vehicle V. When the occurrence of an accident is detected based on the video captured by the camera provided in the vehicle V and the audio collected by the microphone provided in the vehicle V and communication between the vehicle V and the communication destination is not possible, the controller 34 causes the ejection device 31 to eject the RFID tag 40.

[0024] Therefore, even accidents that do not cause damage to the vehicle V can be detected. For example, if a camera or the like detects that the vehicle V has come into contact with a person, the RFID tag 40 is ejected even if no damage has occurred to the vehicle V. This also leaves evidence of the accident, which can, for example, prevent hit-and-run accidents.

[0025] The RFID tag 40 is an example of a storage medium. The storage medium is not limited to an RFID tag, and may be, for example, an IC tag. Each emission device can store multiple RFID tags 40. The writing unit 331 writes data related to the vehicle V to the RFID tag 40. The writing unit 331 is an RFID writer. This makes it possible to write data to multiple storage media in a contactless manner.

[0026] FIG. 2 is a diagram showing an example of the configuration of an RFID tag 40. RFID tag 40a is an example of the RFID tag 40. As shown in FIG. 2, RFID tag 40a is an oval disk shape. This makes RFID tag 40a less likely to roll and more likely to remain at the accident scene. Furthermore, because RFID tag 40a has an oval shape, it rolls randomly like a rugby ball after hitting the ground, preventing it from being crushed by following vehicles.

[0027] 2, the RFID tag 40a includes a memory 41a, a lamp 42a, and a battery 43a. The memory 41a stores written data. The lamp 42a is, for example, an LED (Light Emitting Diode). The battery 43a supplies power to the lamp 42a.

[0028] The lamp 42a flashes. This improves the visibility of the RFID tag 40a when an accident occurs in a mountainous region or at night. Furthermore, when the vehicle V falls off a cliff or the like, the flashing lamp 42a causes the flashing RFID tags 40 to be scattered along the path of the fall. This makes it possible to visualize the path leading to the fall. As a result, it becomes possible to find the vehicle V and rescue its occupants in a short time.

[0029] The lamp 42a may emit visible light or infrared light. If the lamp 42a emits infrared light, it can be seen by an infrared camera. The lamp 42a may be provided on both sides of the RFID tag 40a, not just on one side.

[0030] Furthermore, by flashing the lamp 42a, in the event of a nighttime accident, it is possible to alert the victim who has been hit by the vehicle V to the presence of an accident site so as to prevent further contact with vehicles passing behind. Furthermore, the lamp 42a may be provided with a cover having a light-guiding function that diffuses light in order to improve visibility.

[0031] Furthermore, the RFID tag 40a may have a wireless output function and output a wireless alarm (SOS), which can speed up the discovery of the vehicle V in the event of an accident in a mountainous area or the like.

[0032] The ejection device 31 may also eject an RFID tag 40b that does not have a lamp, as shown in Fig. 3. As shown in Fig. 3, the RFID tag 40b has a memory 41b. On the other hand, the RFID tag 40b does not have a lamp or a battery.

[0033] For example, since the RFID tag 40a is highly visible, it may be discovered by a hit-and-run driver and retrieved to conceal evidence. By simultaneously discharging the RFID tag 40a and the RFID tag 40b, the ejection device 31 can improve visibility and prevent the destruction of evidence.

[0034] The ejector 31 may eject a predetermined number of RFID tags 40a and a predetermined number of RFID tags 40b at a time. For example, the ejector 31 may eject two RFID tags 40a and ten RFID tags 40b. In this way, ejecting a large number of low-cost RFID tags 40b reduces costs.

[0035] 4, the discharge device 31 has a discharge outlet 321 at a position that overlaps with a straight line (dashed line in FIG. 4) that passes through the center of the bottom surface of the vehicle V and extends in the front-to-rear direction of the vehicle V. Discharge outlets 322 and 323 are also similarly provided at positions that overlap with the straight line.

[0036] FIG. 4 is a view of the bottom of vehicle V as seen from the ground side. Tire 60FR is the front right tire. Tire 60FL is the front left tire. Tire 60RR is the rear right tire. Tire 60RL is the rear left tire. When RFID tags 40 are discharged from each discharge outlet toward the ground and vehicle V moves straight in the direction of the arrow, RFID tags 40 are expected to be in a position where they are unlikely to come into contact with any of the tires.

[0037] This allows the discharge device 31 to scatter the RFID tags 40 in the middle of the road, preventing the RFID tags 40 from being crushed by the tires of vehicles passing behind.

[0038] The discharge device 31 stores the RFID tag 40 in a cylindrical container. The discharge port 321 is a hole in the container that is covered with a lid. The discharge device 31 opens the lid of the container under the control of the controller 34 and discharges the RFID tag 40.

[0039] Alternatively, the ejection device 31 may use air pressure to eject the RFID tag 40. In this case, the air pressure is controlled to a level that will not cause damage to the victim of an accident such as a hit-and-run even if the RFID tag 40 hits them.

[0040] The controller 34 may also identify the location of the hit-and-run victim based on the camera image, select one of multiple outlets so that the RFID tag 40 will not hit the victim when being discharged, and discharge the RFID tag 40 from the selected outlet.

[0041] The ejection device 31 may also store a plurality of RFID tags 40 and eject the RFID tags 40 in multiple batches.

[0042] Furthermore, the controller 34 may cause the ejection device 31 to eject a certain number of RFID tags 40 each time an impact is detected by the ECU 10. In this way, for example, if the vehicle V falls on a mountain road, the ejected RFID tags 40 indicate the path of the fall.

[0043] The controller 34 causes the ejection device 31 to eject the RFID tag 40 when the location of the vehicle V is other than the parking lot of the owner's home, an accident is detected, and communication between the vehicle V and the center is not possible. In this case, the location information of the vehicle V is obtained from the ECU 10 or a car navigation system provided in the vehicle V. The location of the parking lot of the home is specified in advance and stored in the memory 35.

[0044] This prevents the RFID tag 40 from being discarded in places where it is not necessary to leave evidence of an accident, such as a parking lot at home.

[0045] The controller 34 can leave a log indicating that the RFID tag 40 has been discharged at the center via the ECU 10. At this time, the controller 34 may leave the data stored in the RFID tag 40 at the center along with the log. However, the controller 34 may perform the process of leaving the log and data at the center after communication between the ECU 10 and the center is restored.

[0046] The flow of processing in the in-vehicle device 30 will be described with reference to Fig. 5. Fig. 5 is a flowchart showing the processing procedure of the in-vehicle device according to the embodiment. The processing shown in Fig. 5 is executed by the controller 34.

[0047] As shown in FIG. 5, first, the controller 34 starts the process when the ACC of the vehicle V is turned on (step S101).

[0048] The controller 34 acquires data from the sensor group 20 via the ECU 10 (step S102). The controller 34 stores the acquired data in the memory 35 (step S103).

[0049] The data acquired by the controller 34 from the sensor group 20 is data to be written to the RFID tag 40, and includes video, audio, acceleration, and the like.

[0050] The controller 34 repeats steps S102 and S103 until an accident is detected by the ECU 10 (step S104, No).

[0051] When the ECU 10 detects an accident (step S104, Yes), the controller 34 determines whether or not the vehicle V and the center can communicate with each other (step S105). If the vehicle V and the center can communicate with each other (step S105, Yes), the controller 34 ends the process. In this case, the ECU 10 can transmit information about the accident to the center, and therefore the discharge of the RFID tag 40 is omitted.

[0052] If the vehicle V and the center cannot communicate with each other (step S105, No), the controller 34 writes the data stored in the memory 35 to the RFID tag 40 (step S106). That is, the controller 34 controls the writing unit 331, the writing unit 332, and the writing unit 333 to write data to the RFID tag 40.

[0053] Thereafter, the controller 34 causes the discharge devices 311, 312, and 313 to discharge the RFID tag 40 (step S107). For example, the controller 34 operates an actuator provided in the discharge port 321 to open a lid, thereby dropping the RFID tag 40. Also, for example, the controller 34 operates a pump provided in the discharge port 321 to push out the RFID tag 40 by air pressure.

[0054] Further advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents. [Explanation of symbols]

[0055] V vehicle 10 ECU 20 Sensors 30 Onboard equipment 31, 311, 312, 313 Ejection device 34 Controller 35, 41a, 41b Memory 42a Lamp 43a battery 60FR, 60FL, 60RR, 60RL tires 321, 322, 323 outlet 331, 332, 333 Writing section

Claims

1. an ejection device that stores a storage medium that stores vehicle information; a controller for controlling the discharge device; Equipped with The controller When an accident is detected based on data from a sensor provided in the vehicle and communication between the vehicle and a communication destination is not possible, the ejection device is caused to eject the storage medium. In-vehicle device.

2. The storage medium is an RFID tag. The in-vehicle device according to claim 1 .

3. The storage medium includes a flashing lamp. The in-vehicle device according to claim 1 .

4. The storage medium is an oval disk. The in-vehicle device according to claim 1 .

5. The controller When the location of the vehicle is a location other than a predetermined parking lot at the owner's home, and an accident is detected based on data from a sensor provided in the vehicle, and communication between the vehicle and a communication destination is not possible, the ejection device is caused to eject the storage medium. The in-vehicle device according to claim 1 .

6. The ejection device has an ejection opening for ejecting the storage medium at a position that passes through the center of the bottom surface of the vehicle and overlaps with a line that extends in the front-rear direction of the vehicle. The in-vehicle device according to claim 1 .

7. The storage medium stores information identifying the owner of the vehicle, information identifying the vehicle, images captured by a camera installed in the vehicle, the speed of the vehicle, and the acceleration of the vehicle. The in-vehicle device according to claim 1 .

8. The controller causes the ejection device to eject the storage medium when an accident is detected based on an image captured by a camera provided in the vehicle and an audio collected by a microphone provided in the vehicle, and communication between the vehicle and a communication destination is not possible. The in-vehicle device according to claim 1 .

9. 1. An ejection method performed by an in-vehicle device having an ejection device that stores a storage medium that stores vehicle information, comprising: When an accident is detected based on data from a sensor provided in the vehicle and communication between the vehicle and a communication destination is not possible, the ejection device is caused to eject the storage medium. Discharge method.

Citation Information

Patent Citations

  • Accident vehicle specifying system and accident vehicle specifying method

    JP2006232029A