Vehicle safety system and method

Abstract

The invention provides a vehicle safety system and method. A vehicle is disclosed having a vehicle camera, a detection unit, and a processor. The vehicle camera may be configured to capture a video feed in a camera field of view. The detection unit may be configured to measure vibrations caused by malicious events associated with the vehicle. The processor may be configured to obtain a trigger signal and activate the detection unit in response to obtaining the trigger signal. The processor may obtain an input from the detection unit in response to activating the detection unit, and detect a malicious event associated with the vehicle based on the input. The processor may also control vehicle camera operation in response to detecting the malicious event.

Description

Technical Field

[0001] This disclosure relates to vehicles, and more specifically to vehicle safety systems and methods for detecting and capturing malicious events. Background Technology

[0002] Many modern vehicles have various security features to detect and resolve potential threats associated with the vehicle. Additionally, many vehicles have security features that can be used to capture malicious events when the vehicle may be powered down or parked. For example, when a vehicle may be powered down or parked, its cameras can record video data and store it in the vehicle's memory. When the vehicle owner notices malicious activity / events associated with the vehicle, the owner can access and review the stored video recordings to understand the cause of the malicious event and / or identify the malicious user who may have caused it.

[0003] However, in some cases, vehicles may not be able to effectively capture the details of such events. Therefore, a system and method are needed to effectively capture data associated with malicious activities / events. Summary of the Invention

[0004] This disclosure describes a system and method for detecting malicious activities / events associated with a vehicle and controlling the operation of a vehicle camera based on the detection. Specifically, when the system detects a malicious event, it can cause the vehicle camera to record a video feed associated with the malicious event and store the video feed in the vehicle's memory.

[0005] In some aspects, to detect malicious events, the system can obtain input from the vehicle's microphone and detect malicious events based on the input obtained from the microphone. In other aspects, the system can detect even minor malicious events, such as scratching paint with a key, rubbing or touching the vehicle's exterior surface with a hand, or another vehicle colliding with a door, by using the input obtained from the microphone. The microphone can be configured to detect vibrations that may be caused by a malicious event, and the system can use the information associated with the detected vibrations to determine that a malicious event may have occurred. The microphone can be located anywhere on the vehicle. In an exemplary aspect, the microphone can be located on an exterior surface / part of the vehicle, such as on the B-pillar, door, etc.

[0006] In some respects, the system can detect malicious events when the sound pressure level associated with the measured vibration may exceed a threshold. Additionally, the system can be configured to identify the type of malicious event (e.g., scratching a vehicle with a key) based on input obtained from the microphone. Specifically, the system can obtain the sound pressure level (SPL) associated with the measured vibration and can apply one or more filters (such as high-pass and low-pass filters) to distinguish different malicious events.

[0007] In some aspects, the system can activate a microphone to detect vibrations associated with the aforementioned malicious events when predetermined conditions are met. For example, the system can activate a microphone when one or more vehicle sensors (such as radio detection and ranging (radar) sensors, optical detection and ranging (LiDAR) sensors, one or more ultrasonic sensors, etc.) detect movement near the vehicle (e.g., movement of people). The microphone can monitor vibrations in response to the system activating the microphone.

[0008] In some respects, in addition to the microphone, the vehicle may also include an accelerometer, which can be configured to detect large malicious events (e.g., vehicle tilting). The system can detect a malicious event when the force measured by the accelerometer exceeds a threshold force value.

[0009] This disclosure discloses a system and method for facilitating the detection of even minor malicious events associated with a vehicle, such as scratching the vehicle with a key. Furthermore, the system only allows the vehicle camera to store video feeds in the vehicle's memory when malicious activity is detected, and otherwise does not, thereby facilitating the storage of relevant video feeds and saving memory space. These and other advantages of this disclosure are provided in detail herein. Attached Figure Description

[0010] Specific embodiments are illustrated with reference to the accompanying drawings. The same reference numerals may be used to indicate similar or identical items. Various embodiments may utilize elements and / or components other than those shown in the drawings, and some elements and / or components may not be present in various embodiments. Elements and / or components in the drawings are not necessarily drawn to scale. Throughout this disclosure, singular and plural terms may be used interchangeably, depending on the context.

[0011] Figure 1 An example environment in which the techniques and structures for providing the systems and methods disclosed herein can be implemented is described.

[0012] Figure 2 A block diagram of an example system for detecting malicious activity and controlling the operation of vehicle components, according to this disclosure, is depicted.

[0013] Figure 3 A flowchart is depicted for a first example method for detecting malicious activity and controlling the operation of vehicle components according to this disclosure.

[0014] Figure 4A and Figure 4B The graphical results obtained from the detection unit according to this disclosure are depicted.

[0015] Figure 5A flowchart is depicted for a second example method for detecting malicious activity and controlling the operation of vehicle components according to this disclosure. Detailed Implementation

[0016] The present disclosure will be described more fully below with reference to the accompanying drawings, which illustrate exemplary embodiments of the present disclosure and are not intended to be limiting.

[0017] Figure 1 An example environment 100 is depicted in which the techniques and structures for providing the systems and methods disclosed herein can be implemented. Environment 100 may include a vehicle 102, which may take the form of any passenger or commercial vehicle, such as a car, work vehicle, crossover, van, minivan, truck, taxi, bus, etc. Furthermore, vehicle 102 may be a manually driven vehicle and / or configured to operate in a fully autonomous (driverless) mode and / or a partially autonomous mode. In some aspects, vehicle 102 may include a traction battery or battery pack (“vehicle battery”, not shown) that can provide energy for vehicle propulsion. In other aspects, vehicle 102 may include any other powertrain system, such as a gasoline engine. Although Figure 1 Four-wheeled vehicles are described, but this disclosure can also be applied to two-wheeled vehicles, such as electric bicycles, scooters, motorcycles, etc.

[0018] In some respects, vehicle 102 may include a safety unit (in Figure 2 The security unit (shown as security unit 214) can be configured to detect malicious events associated with vehicle 102 when vehicle 102 may lose power or when the vehicle engine may shut down, and control the operation of vehicle components based on the detection. Malicious events can be "minor impact" events, such as a person 104 scratching the vehicle with a key, a hand rubbing or touching the exterior surface of the vehicle, or another vehicle colliding with a door.

[0019] In some respects, vehicle 102 may include a microphone (in...) Figure 2 The microphone (shown as microphone 238) can be configured to measure vibrations (e.g., acoustic vibrations) caused by a malicious event. The microphone can be designed as a vibration transducer. In some aspects, the microphone can be disposed on an exterior surface / part of the vehicle. For example, the microphone can be disposed on a large, flat surface, such as a body panel or door panel. In an exemplary aspect, the microphone can be disposed on a B-pillar trim panel or door skin. In some aspects, vehicle 102 may include a plurality of microphones disposed on an exterior surface / part of the vehicle.

[0020] A security unit or "unit" can be configured to receive input from a microphone and detect malicious events based on that input. Specifically, the unit can receive a sound pressure level (SPL) or signal associated with vibrations measured from the microphone and determine whether the SPL is greater than a threshold. When the SPL is likely to be greater than the threshold, the unit can detect a malicious event associated with vehicle 102. In response to determining a malicious event, the unit can control the operation of vehicle components. Specifically, the unit can control the operation of a vehicle camera (e.g., an exterior vehicle camera) such that the vehicle camera can capture images / videos associated with the malicious event. For example, the unit can transmit a command to the vehicle camera to record a video feed associated with the malicious activity / event and store the video feed in the vehicle's memory (in... Figure 2 The video feed is stored in memory 252 (as shown in the diagram). When the vehicle owner notices / observes any instance associated with vehicle 102 (e.g., scratching the vehicle with a key), the vehicle owner can retrieve the video feed from the vehicle's memory to view the details. For example, the vehicle owner can identify the person 104 who may have performed the action of scratching the vehicle with a key by analyzing the stored video.

[0021] Those skilled in the art will understand that in some cases, to save memory space, vehicle cameras may not typically store video feeds in vehicle memory when vehicle 102 may lose power. The security element described in this disclosure enables the vehicle camera to store video feeds associated with a malicious event when the element detects such an event (rather than otherwise). In this way, the element ensures that the owner has access to important video feeds that can help the owner identify individuals 104 who may have caused the malicious event, while ensuring that memory space is not unnecessarily consumed by video feeds that may be unrelated to the malicious event (and therefore may not necessarily be useful to the owner).

[0022] In another aspect, the unit can apply one or more filters to the SPL obtained from the microphone and detect the type of malicious event in response to the application of the filters. In other words, the unit can apply filters to distinguish the type of malicious event and identify the type of malicious event that may have occurred on vehicle 102. For example, the unit can apply a low-pass filter (e.g., a 200Hz low-pass filter) and / or a high-pass filter (e.g., a 2000Hz high-pass filter) to the SPL to detect whether the malicious event was caused by person 104 scratching the vehicle with a key, rubbing or touching the exterior surface of the vehicle with their hand, or another vehicle colliding with a door. In some aspects, in response to identifying the type of malicious event, the unit can tag video feeds when storing them. The tag can be associated with the type of malicious event. Tagging video feeds can facilitate vehicle owners in easily identifying relevant video feeds and details associated with malicious events.

[0023] As described above, the unit detects malicious events based on input obtained from the microphone. However, in some aspects, the unit may activate the microphone before obtaining input from it. In some aspects, when vehicle 102 may lose power, vehicle 102 may move the microphone to a low-power state to conserve vehicle energy. The unit may activate or "wake up" the microphone (so that the microphone can capture the aforementioned input) when predetermined conditions are met or when the unit receives a trigger signal. In some aspects, predetermined conditions may be met or a trigger signal may be received when the vehicle detection unit detects movement near vehicle 102. The vehicle detection unit may be, for example, a vehicle camera, a radio detection and ranging (radar) sensor, a light detection and ranging (LiDAR) sensor, an ultrasonic sensor, etc.

[0024] In response to the microphone being activated, the microphone can capture input associated with a malicious event, as described above. In this way, vehicle 102 ensures that vehicle energy is not unnecessarily consumed and that the microphone is activated only upon receiving a trigger signal.

[0025] The following text combines Figure 2 Describe additional vehicle details.

[0026] Vehicle 102 shall implement and / or perform the operations described herein in accordance with the owner's manual and safety guidelines. Additionally, any action taken by the vehicle owner based on recommendations or notices provided by vehicle 102 shall comply with all rules specific to the location (e.g., federal, state, national, city, etc.) and operation of vehicle 102. Any recommendations or notices provided by vehicle 102 shall be considered advice and shall be followed only in accordance with any rules specific to the location and operation of vehicle 102.

[0027] Figure 2 A block diagram of an example system 200 for detecting malicious activity and controlling the operation of vehicle components according to this disclosure is depicted. (The explanation follows...) Figure 2 At that time, will refer to Figure 3 . Figure 3 A flowchart is depicted for a first example method 300 for detecting malicious activity and controlling the operation of vehicle components according to this disclosure.

[0028] System 200 may include a vehicle 202, a user device 204, and one or more servers 206 that are communicatively coupled to each other via one or more networks 208. Vehicle 202 may be associated with the above. Figure 1 The vehicle 102 described is identical. User device 204 may be associated with the vehicle owner / user and may include, but is not limited to, a mobile phone, laptop computer, computer, tablet computer, wearable device, or any other similar device with communication capabilities. Server 206 may be part of a cloud-based computing infrastructure and may be associated with and / or include a Telematics Service Delivery Network (SDN), which provides services to vehicle 202 and other vehicles that may be part of a vehicle fleet. Figure 2 (Not shown) provides digital data services. In another aspect, server 206 may receive information captured by vehicle 202 (e.g., images captured by vehicle cameras) and store the received information in a server database. If needed, vehicle users can retrieve the stored information from server 206 via user device 204 or vehicle components (e.g., infotainment system 246, described below).

[0029] Network 208 illustrates example communication infrastructure in which connected devices discussed in various embodiments of this disclosure can communicate. Network 208 may be and / or include the Internet, a private network, a public network, or other configurations operating using any one or more known communication protocols such as, for example, Transmission Control Protocol / Internet Protocol (TCP / IP). Bluetooth Low Energy (BLE), Wi-Fi based on the IEEE standard 802.11, Ultra Wideband (UWB), and cellular technologies such as Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), High Speed ​​Packet Access (HSPDA), Long Term Evolution (LTE), Global System for Mobile Communications (GSM), and 5G are just a few examples.

[0030] Vehicle 202 may include multiple units, including but not limited to vehicle computer 210, vehicle control unit (VCU) 212, and safety unit 214. VCU 212 may include multiple electronic control units (ECUs) 216 configured to communicate with vehicle computer 210.

[0031] User device 204 can be connected to vehicle computer 210 and / or security unit 214 via network 208, said network can communicate via one or more wireless connections, and / or said user device can communicate via Near Field Communication (NFC) protocol. Protocols, Wi-Fi, Ultra-Wideband (UWB), and other possible data connectivity and sharing technologies can be used to directly connect to vehicle 202.

[0032] In some respects, according to this disclosure, the vehicle computer 210 and / or the security unit 214 can be installed anywhere within the vehicle 202. Furthermore, the vehicle computer 210 can operate as a functional part of the security unit 214. The vehicle computer 210 can be or include an electronic vehicle controller having one or more processors 218 and memory 220. Additionally, the security unit 214 can be separate from the vehicle computer 210 (e.g., Figure 2 (as shown), or it can be integrated as part of the car computer 210.

[0033] Processor 218 may be configured to communicate with one or more memory devices (e.g., memory 220 and / or memory 220) configured to communicate with a corresponding computing system. Figure 2 The processor 218 may communicate with one or more external databases (not shown). The processor 218 may utilize the memory 220 to store programs in code and / or store data for execution of aspects according to this disclosure. The memory 220 may be a non-transitory computer-readable medium or memory storing secure program code. The memory 220 may include any or a combination of volatile memory elements (e.g., dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), etc.) and may include any one or more non-volatile memory elements (e.g., erasable programmable read-only memory (EPROM), flash memory, electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), etc.).

[0034] According to some aspects, VCU 212 can share a power bus with vehicle computer 210 and can be configured and / or programmed to operate in the vehicle system, connected servers (e.g., server 206), and other vehicles as part of a vehicle fleet. Figure 2Coordinating data between (not shown in the diagram). VCU 212 may include or communicate with any combination of ECUs 216, such as Body Control Module (BCM) 222, Engine Control Module (ECM) 224, Transmission Control Module (TCM) 226, Telematics Control Unit (TCU) 228, Driver Assist Technology (DAT) Controller 230, etc. VCU 212 may also include and / or communicate with a Vehicle Sensing System (VPS) 232, which can connect to and / or control one or more vehicle sensing systems 234. The vehicle sensing system 234 may include one or more vehicle sensors, including but not limited to radio detection and ranging (“radar”) sensors configured to use radio waves to detect and locate objects inside and outside the vehicle 202, seating area latch sensors, seating area sensors, light detection and ranging (“LiDAR”) sensors, ultrasonic sensors, door sensors, proximity sensors, temperature sensors, wheel sensors, ambient weather sensors, one or more vehicle cameras 236, steering wheel sensors, one or more microphones 238, accelerometers 240, etc. In some aspects, vehicle cameras 236 may be configured to capture images and videos (or video feeds) within the field of view of the respective camera. In some aspects, vehicle cameras 236 may include external vehicle cameras that can capture images / videos associated with malicious events that may occur on the vehicle 202 (this could allow the vehicle owner to know / view the identity of person 104, such as the face of person 104 performing an action of scratching the vehicle with a key). Microphone 238 (or audio transducer) can be configured to measure vibrations / audio sounds caused by malicious events (e.g., minor malicious events such as scratching the vehicle with a key, as described above). Accelerometer 240 can be configured to measure large forces (which may be applied to vehicle 202) to detect malicious events such as vehicle tilting (or other large malicious events). In another aspect, vehicle sensing system 234 can be configured to detect movement near vehicle 202. For example, vehicle camera 236, radar sensors, lidar sensors, ultrasonic sensors, etc., disposed in vehicle 202 can be configured to detect any movement near vehicle 202 (e.g., when a user, animal, or any object moves near vehicle 202).

[0035] In some respects, VCU 212 can control vehicle operation aspects and implement one or more instruction sets received from user device 204 and from one or more instruction sets stored in memory 220, including instructions that operate as part of security unit 214.

[0036] TCU 228 can be configured and / or programmed to provide vehicle connectivity to wireless computing systems on and outside the vehicle 202, and may include a navigation (NAV) receiver 242, a BLE module (BLEM) 244, a Wi-Fi transceiver, a UWB transceiver, and / or may be configured to connect the vehicle 202 to other systems (e.g., vehicle key fobs, etc.) for receiving and processing GPS signals. Figure 2 Other wireless transceivers (not shown in the image) for wireless communication (including cellular communication) between the computer and the module. Figure 2 (Not shown in the image). TCU 228 can be configured to communicate with ECU 216 via a bus.

[0037] ECU 216 can control various aspects of vehicle operation and communication using inputs from the human driver, inputs from the autonomous vehicle controller, inputs from the safety unit 214, and / or wireless signal inputs received from other connected devices (such as user device 204, server 206, etc.) via a wireless connection.

[0038] The BCM 222 typically integrates sensors, vehicle performance indicators, and variable reactors associated with vehicle systems. It may also include processor-based power distribution circuitry that controls functions associated with the vehicle body, such as lights, windows, safety devices, cameras, audio systems, speakers, wipers, door locks and entry controls, and various comfort controls. The BCM 222 can also operate as a gateway for bus and network interfaces to communicate with remote ECUs ( Figure 2 Interact with (not shown in the image).

[0039] The DAT controller 230 can provide Level 1 to Level 3 automated driving and driver assistance functions, which may include features such as active parking assist, vehicle reversing assist, and adaptive cruise control. The DAT controller 230 can also provide aspects for user and environmental inputs that can be used for user authentication.

[0040] In some respects, the vehicle computer 210 can be connected to the infotainment system 246. The infotainment system 246 may include a touchscreen interface portion and may include voice recognition features, enabling it to identify users' biometric features based on facial recognition, voice recognition, fingerprint recognition, or other biometric methods. In other respects, the infotainment system 246 may also be configured to receive user commands / requests via the touchscreen interface portion and / or display notifications (including visual alerts), navigation maps, etc., on the touchscreen interface portion.

[0041] The computing system architecture of the automotive computer 210, VCU 212, and / or security unit 214 may omit certain computing modules. This should be readily understood. Figure 2The computing environment depicted herein is an example of possible implementations according to this disclosure and should therefore not be considered restrictive or exclusive.

[0042] Depending on some aspects, the safety unit 214 may be integrated with and / or performed as part of the ECU 216. Whether integrated with the vehicle computer 210 or the ECU 216, or operating as a separate computing system in the vehicle 202, the safety unit 214 may include a transceiver 248, a processor 250, and a computer-readable storage device 252 that are communicatively coupled to each other.

[0043] Transceiver 248 can be configured to receive information / input from one or more external devices or systems (e.g., user device 204, server 206, etc.) via network 208. Furthermore, transceiver 248 can transmit notifications (e.g., alarm / alarm signals) to external devices or systems. Additionally, transceiver 248 can be configured to receive information / input from vehicle components such as vehicle sensing system 234 (including vehicle camera 236, microphone 238, accelerometer 240, etc.), infotainment system 246, etc. Furthermore, transceiver 248 can transmit notifications (e.g., alarm / alarm signals) to vehicle components (such as infotainment system 246, BCM 222, etc.).

[0044] Processor 250 and memory 252 may be the same as or similar to processor 218 and memory 220, respectively. In some aspects, processor 250 may utilize memory 252 to store programs in code form and / or store data for execution of aspects according to this disclosure. Memory 252 may be a non-transitory computer-readable medium or memory for storing secure program code. In some aspects, memory 252 may additionally store information associated with vehicle 202 and one or more sensing inputs received from vehicle sensing system 234 (such as video feeds or images captured by vehicle camera 236).

[0045] During operation, when vehicle 202 may experience a power outage or when the vehicle ignition is turned off, processor 250 can maintain safety unit 214 in a low-power state or low-power mode, such as... Figure 3 As shown in step 302. In some aspects, processor 250 may maintain the safety unit 214 in a low-power mode until processor 250 receives / acquires a trigger signal (or when predetermined conditions can be met). In some aspects, processor 250 may acquire the trigger signal when vehicle sensing system 234 (e.g., radar sensor, lidar sensor, ultrasonic sensor, vehicle camera 236, etc.) detects motion near vehicle 202. For example, processor 250 may acquire the trigger signal from vehicle sensing system 234 when vehicle sensing system 234 detects that person 104 may be present near vehicle 202.

[0046] In response to a trigger signal received from the vehicle sensing system 234, the processor 250 may activate one or more vehicle components to capture information associated with one or more malicious events (associated with vehicle 202), such as... Figure 3 As shown in step 304. Activatable vehicle components may include, but are not limited to, vehicle camera 236, microphone 238, accelerometer 240, etc. In some aspects, processor 250 may transmit a wake-up signal to the vehicle component to activate it. In some aspects, when processor 250 receives a trigger signal, processor 250 may simultaneously transmit wake-up signals to all vehicle components. In other aspects, processor 250 may transmit wake-up signals to the vehicle components sequentially or selectively.

[0047] When a vehicle component receives a wake-up signal from processor 250, it can begin capturing information associated with a malicious event. For example, when microphone 238 receives a wake-up / activation signal, it can begin measuring / monitoring vibrations that may be caused by a malicious event. Furthermore, in response to being activated (or "wake up"), the vehicle component can continue capturing information associated with a malicious event for a predefined duration.

[0048] In response to activating a vehicle component, processor 250 can obtain input from the vehicle component and detect malicious events (e.g., a first malicious event) associated with vehicle 202 based on the obtained input. In some aspects, processor 250 can obtain input from microphone 238 (e.g., information associated with measured vibrations) and detect malicious events based on the obtained vibration information. Specifically, processor 250 can obtain the sound pressure level (SPL) or signal associated with the measured vibrations and compare the SPL with a threshold. Based on this comparison, processor 250 can determine whether the SPL is greater than the threshold (or whether microphone 238 has detected a large vibration, such as...). Figure 3 (See step 306). When processor 250 determines that SPL is greater than a threshold, processor 250 can detect that a malicious event may have occurred. In response to detecting a malicious event, processor 250 can control the operation of vehicle camera 236, such as... Figure 3 As shown in step 308. Specifically, when the processor 250 detects a malicious event, the processor 250 can cause the vehicle camera 236 to record a video feed associated with the malicious event (within the camera's field of view (FOV)) and store the video feed in the memory 252.

[0049] In another aspect, besides detecting a possible malicious event, processor 250 can also identify the type of malicious event based on the acquired SPL. For example, processor 250 can detect / identify whether a malicious event is personnel 104 scratching the vehicle with a key, rubbing or touching the vehicle's exterior surface with a hand, or another vehicle colliding with a door, etc. In some aspects, processor 250 can identify the type of malicious event (or distinguish different malicious events) by applying one or more filters to the SPL / signal associated with the measured vibration (measured by microphone 238). For example, processor 250 can apply a low-pass filter (e.g., a 200Hz low-pass filter) and / or a high-pass filter (e.g., a 2000Hz high-pass filter) to the SPL to detect whether the malicious event is personnel 104 scratching the vehicle with a key, rubbing or touching the vehicle's exterior surface with a hand, or another vehicle colliding with a door. In some aspects, in response to identifying the type of malicious event, processor 250 can tag the video feed when storing the video feed. The tag can be associated with the type of malicious event. Tagging video feeds can help vehicle owners easily identify relevant video feeds and details associated with malicious incidents.

[0050] In another aspect, processor 250 can obtain input from accelerometer 240 (after accelerometer 240 is activated) and detect another malicious event (or a second malicious event, such as vehicle tilting) based on the obtained input. For example, processor 250 can obtain information associated with a force detected by accelerometer 240 and compare the detected force with a threshold (or threshold force). Based on the comparison, processor 250 can determine whether the detected force is greater than the threshold (or whether accelerometer 240 has detected a large force, such as...). Figure 3 (as shown in step 310). When the processor 250 determines that the detected force is greater than a threshold, the processor 250 can detect a second malicious event. In response to the detection of the second malicious event, the processor 250 can control the operation of the vehicle camera 236, such as... Figure 3 Step 308 is shown and performed in the manner described above. Specifically, when the processor 250 detects a second malicious event, the processor 250 can cause the vehicle camera 236 to record a video feed associated with the malicious event (in the camera's field of view) and store the video feed in the memory 252.

[0051] In an additional or alternative aspect, processor 250 may obtain input from vehicle camera 236 and detect malicious events (e.g., a third malicious event, such as any suspicious behavior approaching vehicle 202) based on said input. For example, processor 250 may detect malicious events by analyzing images / videos captured by vehicle camera 236. In some aspects, the third malicious event may be the same as the first or second malicious event. In other aspects, the third malicious event may be different from the first or second malicious event. In this case, processor 250 may obtain one or more video feeds from vehicle camera 236 and perform one or more image processing algorithms (which may be pre-stored in memory 252) on the video feeds. Specifically, processor 250 may perform one or more artificial intelligence / machine learning (AI / ML) based image processing on the video feeds captured by vehicle camera 236 and determine / detect the third malicious event (e.g., a third malicious event) based on the AI / ML based image processing. Figure 3 (as shown in step 312). In response to the detection of a third malicious event, the processor 250 can control the operation of the vehicle camera 236, such as... Figure 3 Step 308 is shown and performed in the manner described above. Specifically, when the processor 250 detects a third malicious event, the processor 250 can cause the vehicle camera 236 to save the video feed in the memory 252. On the other hand, when the processor 250 does not detect a third malicious event, the processor 250 may not cause the vehicle camera 236 to save the video feed in the memory 252.

[0052] In some respects, the processor 250 can simultaneously receive input from all vehicle components and execute commands concurrently. Figure 3 Steps 306, 310, and 312. In other aspects, the processor 250 can sequentially or selectively obtain input from vehicle components and execute sequentially. Figure 3Steps 306, 310, and 312. For example, processor 250 may first obtain input from vehicle camera 236 and detect malicious events (e.g., first / second / third malicious events) based on the input obtained from vehicle camera 236. When processor 250 does not detect a malicious event using vehicle camera 236, processor 250 may then obtain input from microphone 238. Processor 250 may then detect malicious events based on the input obtained from microphone 238. When processor 250 does not detect a malicious event using microphone 238, processor 250 may obtain input from accelerometer 240 and then detect malicious events based on the input obtained from accelerometer 240. In some aspects, when processor 250 detects a malicious event from any of the aforementioned vehicle components, processor 250 may cause vehicle camera 236 to record and store the video feed in memory 252. On the other hand, when the processor 250 does not detect a malicious event from any of the vehicle components, the processor 250 may prevent the vehicle camera 236 from recording and / or storing video feeds in the memory 252, thereby saving / storing selective video feeds that may be needed to investigate the malicious event in the vehicle memory 252.

[0053] In an additional aspect, processor 250 may receive input from an ultrasonic transducer (as a supplement or alternative to microphone 238) to detect the aforementioned malicious events. In another aspect, processor 250 may be configured to output a voice message or alarm via vehicle speakers when processor 250 detects a malicious event. For example, processor 250 may output an alarm to occupant 104. In another aspect, processor 250 may control vehicle lights to warn occupant 104. In yet another aspect, processor 250 may be configured to output a notification indicating the occurrence of a malicious event to user device 204 via transceiver 248 in response to the detection of a malicious event. In some aspects, the notification may include a type of malicious event.

[0054] Figure 4A and Figure 4B Graphical results 402 and 404 obtained from a detection unit (e.g., microphone 238) according to this disclosure are depicted. Graphical result 402 is obtained when a low-pass (LP) filter is applied to the sound pressure level (SPL), and graphic result 404 is obtained when a high-pass (HP) filter is applied to the SPL.

[0055] Each of the graphical results includes an X-axis representing different malicious events that can be detected using microphone 238 (including friction, scratching paint with a key, collisions, etc., and ambient levels (when there is no contact)) and a Y-axis representing the sound pressure level in decibels (dB). Each result indicates the SPL captured by microphone 238 when microphone 238 is positioned at the B-pillar (which can detect airborne sound) (as shown in Figure 406) and when microphone 238 is positioned at the door (which can detect structure-borne sound) (as shown in Figure 408).

[0056] As described above, applying different filters to the SPL allows processor 250 to distinguish between scratching paint with a key, door collisions, and other minor incidents. In some aspects, processor 250 can apply a 200Hz low-pass filter to the signal / SPL and compare the SPL with a corresponding threshold (shown as potential trigger target 410 in Figure 4) for a malicious event associated with vehicle 202. Based on this comparison, processor 250 can isolate sound to detect malicious events. For example, when the SPL is greater than the threshold associated with a collision (or door collision), processor 250 can identify a collision as a malicious event type. Similarly, processor 250 can apply a 2000Hz high-pass filter to the signal / SPL and isolate sound to detect scratching paint with a key. For example, when processor 250 applies the 2000Hz high-pass filter, processor 250 can compare the SPL with a corresponding threshold (shown as potential trigger target 412 in Figure 4) for a malicious event associated with vehicle 202. Based on this comparison, processor 250 can isolate sound to detect a malicious event as scratching the vehicle with a key, as described above.

[0057] Figure 5 A flowchart of a second example method 500 for detecting malicious activity and controlling the operation of vehicle components according to this disclosure is depicted. Further description can be made with reference to the preceding figures. Figure 5 The following process is exemplary and is not limited to the steps described below. Furthermore, alternative embodiments may include more or fewer steps than shown or described herein, and may include these steps in an order different from that described in the following exemplary embodiments.

[0058] refer to Figure 5 At step 502, method 500 may begin. At step 504, method 500 may include receiving a trigger signal by processor 250. Processor 250 may receive the trigger signal when vehicle sensing system 234 detects movement near vehicle 202.

[0059] At step 506, method 500 may include activating a detection unit by processor 250 in response to receiving a trigger signal. The detection unit may be configured to measure vibrations caused by a malicious event. In some aspects, the detection unit may be a microphone 238. At step 508, method 500 may include receiving input from the detection unit by processor 250 in response to activating the detection unit.

[0060] At step 510, method 500 may include detecting malicious events by processor 250 based on input. For example, processor 250 may detect actions such as scratching a car door with a key, rubbing a hand on the exterior surface of the vehicle, or another vehicle colliding with the car door based on input obtained from microphone 238.

[0061] At step 512, method 500 may include operation of vehicle camera 236 controlled by processor 250 in response to the detection of a malicious event. For example, processor 250 may cause vehicle camera 236 to record a video feed within the camera's field of view (FOV) and store the video feed in memory 252. At step 514, method 500 may terminate.

[0062] In the foregoing disclosure, reference has been made to the accompanying drawings, which form a part of the foregoing disclosure, illustrating specific implementations in which the present disclosure may be practiced. It should be understood that other implementations and structural changes may be utilized without departing from the scope of the present disclosure. References to “an embodiment,” “embodiment,” “exemplary embodiment,” etc., in this specification indicate that the described embodiment may include specific features, structures, or characteristics, but each embodiment may not necessarily include said specific features, structures, or characteristics. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when features, structures, or characteristics are described in connection with embodiments, those skilled in the art will recognize such features, structures, or characteristics in conjunction with other embodiments, whether explicitly described or not.

[0063] Furthermore, where appropriate, the functions described herein may be performed by one or more of the following: hardware, software, firmware, digital components, or analog components. For example, one or more application-specific integrated circuits (ASICs) may be programmed to perform one or more of the systems and programs described herein. Certain terms are used throughout the specification and claims to refer to specific system components. As those skilled in the art will appreciate, components may be referred to by different names. This document is not intended to distinguish between components with different names but identical functions.

[0064] It should also be understood that the term "example" as used herein is intended to be non-exclusive and non-restrictive in nature. More specifically, the term "example" as used herein refers to one of several examples, and it should be understood that there is no undue emphasis or preference on the particular example described.

[0065] Computer-readable media (also known as processor-readable media) include any non-transitory (e.g., tangible) medium that contributes to providing data (e.g., instructions) that can be read by a computer (e.g., by the computer's processor). Such media can take many forms, including but not limited to non-volatile and volatile media. Computing devices may include computer-executable instructions, which can be executed by one or more computing devices (such as those listed above) and stored on a computer-readable medium.

[0066] Regarding the processes, systems, methods, heuristics, etc., described herein, it should be understood that although the steps of such processes, etc., are described as occurring in a certain ordered order, such processes can be practiced by performing the described steps in an order different from that described herein. It should also be understood that some steps may be performed simultaneously, other steps may be added, or some steps described herein may be omitted. In other words, the description of processes herein is provided for the purpose of illustrating various embodiments and should in no way be construed as limiting the claims.

[0067] Therefore, it should be understood that the above description is intended to be illustrative rather than restrictive. Many embodiments and applications beyond the examples provided will become apparent upon reading the above description. The scope should not be determined by reference to the above description, but rather by reference to the appended claims and the full scope of their equivalents. It is anticipated and expected that the techniques discussed herein will evolve in the future, and the disclosed systems and methods will be incorporated into such future embodiments. In conclusion, it should be understood that modifications and variations are possible with this application.

[0068] Unless explicitly indicated otherwise herein, all terms used in the claims are intended to be given their ordinary meaning as understood by one skilled in the art as described herein. Specifically, unless the claims explicitly limit the recitation to the contrary, the use of singular articles such as “a,” “the,” or “the” should be interpreted as one or more of the elements indicated by the recitation. Unless otherwise specifically stated or otherwise understood in the context of use, conditional language such as, in particular, “can,” “may,” “may,” or “may” is generally intended to express that some embodiments may include certain features, elements, and / or steps, while other embodiments may not include certain features, elements, and / or steps. Therefore, such conditional language is generally not intended to imply that one or more embodiments require each feature, element, and / or step in any way.

[0069] In one aspect of the invention, the method includes: applying one or more filters to the sound pressure level; and detecting a malicious event type in response to applying the one or more filters.

[0070] In one aspect of the invention, the malicious event type includes at least one of the following: scratching the car door with a key, rubbing the exterior surface of the vehicle with a hand, or another vehicle colliding with the car door.

[0071] In one aspect of the invention, controlling the operation of a vehicle camera includes controlling the vehicle camera to record a video feed within the camera's field of view and storing the video feed in a vehicle memory.

[0072] In one aspect of the invention, obtaining the trigger signal includes obtaining the trigger signal when the second detection unit detects movement near the vehicle.

[0073] According to the present invention, a non-transitory computer-readable storage medium is provided in a distributed computing system, the non-transitory computer-readable storage medium storing instructions that, when executed by a processor, cause the processor to: obtain a trigger signal; activate a detection unit in response to obtaining the trigger signal, wherein the detection unit is configured to measure vibrations caused by a malicious event associated with a vehicle; obtain input from the detection unit in response to activating the detection unit; detect the malicious event associated with the vehicle based on the input; and control the operation of a vehicle camera in response to detecting the malicious event, wherein the vehicle camera is configured to capture a video feed within the camera's field of view.

Claims

1. A vehicle comprising: A vehicle camera, configured to capture a video feed within the camera's field of view; A first detection unit is configured to measure vibrations caused by a malicious event associated with the vehicle. A processor, communicatively coupled to the vehicle camera and the first detection unit, wherein the processor is configured to: Receive trigger signal; The first detection unit is activated in response to receiving the trigger signal; In response to activating the first detection unit, input is obtained from the first detection unit; Based on the input, detect a first malicious event associated with the vehicle; as well as In response to the detection of the first malicious event, control the operation of the vehicle's camera.

2. The vehicle of claim 1, wherein the first detection unit includes a microphone.

3. The vehicle as claimed in claim 2, wherein the microphone is disposed on the outer surface of the vehicle.

4. The vehicle of claim 1, further comprising a second detection unit configured to detect movement in the vicinity of the vehicle.

5. The vehicle of claim 4, wherein the second detection unit comprises at least one of the following: a vehicle camera, a radio detection and ranging (radar) sensor, a light detection and ranging (LiDAR) sensor, or an ultrasonic sensor.

6. The vehicle of claim 4, wherein the processor is configured to obtain the trigger signal when the second detection unit detects the motion near the vehicle.

7. The vehicle of claim 1, wherein the processor is further configured to: The sound pressure level associated with the measured vibration is compared with a threshold. Based on the comparison, it is determined that the sound pressure level is greater than the threshold; and The first malicious event is detected in response to determining that the sound pressure level is greater than the threshold.

8. The vehicle of claim 7, wherein the processor is further configured to: Apply one or more filters to the sound pressure level; and In response to the application of one or more filters to detect malicious event types.

9. The vehicle of claim 8, wherein the malicious event type includes at least one of the following: scratching the door with a key, rubbing the exterior surface of the vehicle with a hand, or another vehicle colliding with the door.

10. The vehicle of claim 1, wherein the processor controls the vehicle camera by causing the vehicle camera to record the video feed within the camera's field of view and to store the video feed in the vehicle's memory.

11. The vehicle of claim 1, wherein the processor is further configured to: One or more video feeds are obtained from the vehicle's camera; Perform image processing on the one or more video feeds; Detecting a second malicious event based on the image processing; and The one or more video feeds are saved in response to the detection of the second malicious event.

12. The vehicle of claim 1, further comprising an accelerometer configured to measure forces applied to the vehicle.

13. The vehicle of claim 12, wherein the processor is further configured to: Input is obtained from the accelerometer; Detecting third malicious events based on the input; and In response to the detection of the third malicious event, control the operation of the vehicle camera.

14. A method comprising: The trigger signal is obtained from the processor; The processor activates a first detection unit in response to receiving the trigger signal, wherein the first detection unit is configured to measure vibrations caused by malicious events associated with the vehicle; The processor receives input from the first detection unit in response to activating the first detection unit; The processor detects malicious events associated with the vehicle based on the input; as well as The processor controls the operation of the vehicle camera in response to the detection of the malicious event, wherein the vehicle camera is configured to capture video feeds within the camera's field of view.

15. The method of claim 14, further comprising: The sound pressure level associated with the measured vibration is compared with a threshold. Based on the comparison, it is determined that the sound pressure level is greater than the threshold. as well as The malicious event is detected in response to determining that the sound pressure level is greater than the threshold.

Images