Vehicle-based identification and response to unwanted entities

By utilizing vehicle lights and sensors, combined with ultraviolet light and image processing technology, unwanted entities inside or outside the vehicle can be detected and processed, solving the problem of difficult detection and processing in existing technologies and achieving efficient real-time security measures.

CN123061291APending Publication Date: 2026-11-10FORD GLOBAL TECH LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610540295.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-07
Filing Date
2026-04-22
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing technologies struggle to effectively detect and handle unwanted entities (such as snakes, scorpions, and other harmful organisms) inside or near a vehicle, causing inconvenience to users.

Method used

By utilizing existing vehicle components such as lights and sensors, and through ultraviolet or deep blue light illumination and image processing technology, unwanted entities inside or outside the vehicle can be detected, and corresponding remedial measures can be provided through artificial intelligence.

Benefits of technology

It enables efficient detection and handling of unwanted entities inside or outside vehicles, providing real-time notifications and guidance to ensure user safety.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123061291A_ABST
    Figure CN123061291A_ABST
Patent Text Reader

Abstract

This invention provides "vehicle-based identification and response to unwanted entities." A vehicle is disclosed, comprising a vehicle camera, headlights, and a processor. The vehicle camera can capture images of the vehicle interior or vicinity. The headlights can illuminate unwanted entities inside or near the vehicle. The processor can activate the headlights to detect the presence of unwanted entities inside or near the vehicle, and receives input from the vehicle camera in response to activating the headlights. The processor can detect the presence of unwanted entities inside or near the vehicle based on the input, and perform a predetermined action based on the detection.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to vehicles, and more specifically to vehicle-based identification and response to unwanted entities inside or near a vehicle. Background Technology

[0002] In some regions and / or warmer climates, harmful creatures such as snakes or other small animals may enter a vehicle when the doors are kept open or when the doors are opened and closed. The presence of such animals can cause inconvenience to vehicle users. Summary of the Invention

[0003] This disclosure describes a system and method for detecting the presence of unwanted entities inside or outside a vehicle (e.g., near or around the vehicle). Unwanted entities may be any harmful organisms or any potentially disturbing or unwelcome animals that may cause discomfort to a user (e.g., a driver or other vehicle occupant). Unwanted entities may include, for example, scorpions, snakes, rodents, bats, rattlesnakes, harmful plants, or plants or trees known to have thorns / poison vine / oak / campfire remnants (such as pallet wood known to contain nails).

[0004] It is understood that the aforementioned unwanted entities may fluoresce when exposed to ultraviolet (UV) light (especially UV A) or deep blue light. To detect the presence of unwanted entities inside or near a vehicle, the system can perform scans (e.g., internal and / or external scans) using existing vehicle components (e.g., headlights, vehicle sensors / cameras, etc.). In some aspects, the system can perform internal scans to detect the presence of unwanted entities inside the vehicle and external scans to detect the presence of unwanted entities outside and near the vehicle.

[0005] The system can perform internal scans continuously or under certain conditions. For example, the system can perform internal scans when doors or windows are opened and closed. In another case, the system can perform internal scans continuously when a window remains open. Similarly, the system can perform external scans when the vehicle is stopped or when the vehicle is in parking mode. In another aspect, the system can perform internal and / or external scans based on requests / inputs obtained from the user. The system can obtain user requests / inputs via a vehicle human-machine interface (HMI) or user device.

[0006] To perform a scan (e.g., an internal scan and / or an external scan), the system may first activate lights in the interior and / or exterior of the vehicle to illuminate unwanted entities (if present) inside and / or near the vehicle. In response to the activation of the lights, the system acquires input / images from a vehicle camera. Based on the acquired input / images, the system can detect the presence of unwanted entities inside or near the vehicle and perform predetermined remedial actions based on the detection.

[0007] As part of a planned remedial action, the system may output a notification to the user via an HMI and / or user device indicating the presence of an unwanted entity inside or outside the vehicle. The system may also identify and indicate the location of the unwanted entity in the notification. Furthermore, the system may characterize and identify the type of the unwanted entity and indicate that type in the notification. In some aspects, the notification may be an audible notification in the form of voice, tone, ringtone, etc.

[0008] In another aspect, when the system detects an unwanted entity near the vehicle, it can allow the user (driver and / or other passengers) to open the door with a double pull. Furthermore, the system can selectively activate one or more lights to indicate / illuminate the location of the unwanted entity. Additionally, the system can use artificial intelligence (AI) to provide the user with guidance on how to handle the unwanted entity and move it away from the vehicle (e.g., if an unwanted entity is detected inside the vehicle). Moreover, if the user is affected by the unwanted entity in some way (e.g., bitten), the system can provide guidance to the user.

[0009] This disclosure discloses a system that can automatically detect the presence of unwanted entities inside or near a vehicle using existing components of the vehicle. The system can also provide guidance to a user to effectively handle unwanted entities (e.g., when the unwanted entity is present inside the vehicle). The system can further provide guidance to the user when the user and / or vehicle occupants are affected by the unwanted entity in any way. Additionally, the system can selectively activate vehicle components to perform scans to appropriately utilize the vehicle's resources.

[0010] These and other advantages of this disclosure are provided in detail herein. Attached Figure Description

[0011] 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.

[0012] Figure 1 A view of an example vehicle according to this disclosure is depicted.

[0013] Figure 2 A block diagram of a system according to this disclosure for detecting the presence of unwanted entities and performing remedial actions is depicted.

[0014] Figure 3 An example view depicts a parked vehicle and unwanted entities located near the vehicle, according to this disclosure.

[0015] Figure 4 A flowchart is depicted of an example method for detecting the presence of unwanted entities and performing remedial actions 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 A view of an example vehicle 100 according to this disclosure is depicted. Vehicle 100 can take the form of any passenger car or commercial vehicle, such as an automobile, work vehicle, crossover, truck, van, minivan, taxi, bus, etc. Vehicle 100 can be a manually driven vehicle or can be configured to operate in a partially / fully autonomous mode. Furthermore, vehicle 100 can include any powertrain system, such as a gasoline engine, one or more electric actuators, or a hybrid system.

[0018] Vehicle 100 may include multiple vehicle components, including but not limited to lights (in Figure 2 The image is shown as headlight 238) and one or more vehicle sensors (or sensor suites, in Figure 2 (Seen as vehicle sensing system 230). In some aspects, the vehicle sensor may be a vehicle camera, such as an interior vehicle camera and / or an exterior vehicle camera. The vehicle sensor (hereinafter referred to as the vehicle camera) may capture images of the interior of the vehicle 100 or the vicinity of the vehicle 100 (e.g., images of the area surrounding the vehicle). The interior vehicle camera may capture images of the interior parts of the vehicle, and the exterior vehicle camera may capture images of the exterior parts of the vehicle or the surrounding area.

[0019] The headlights may be located in the interior and / or exterior of the vehicle and may illuminate objects / people (including unwanted entities 102) located inside and / or outside the vehicle 100. Unwanted entities 102 may be any harmful organism / entity that may cause discomfort to the user 104 or any potentially disturbing or unwelcome animal. Unwanted entities 102 may include, for example, scorpions, snakes, rodents, bats, rattlesnakes, harmful plants, or plants or trees known to have thorns / poison vines / oak / campfire remnants (such as pallet wood known to contain nails).

[0020] Vehicle lights can facilitate the detection of unwanted entities 102 inside or near vehicle 100. In some respects, vehicle lights can emit ultraviolet (UV) light. In other respects, vehicle lights can emit blue light. It is understood that unwanted entities (such as the aforementioned unwanted entity 102) may fluoresce when exposed to UV (specifically, ultraviolet A) or deep blue light. Since vehicle lights include UV light and / or blue light, they can illuminate unwanted entities 102 inside or near vehicle 100 (if they are present inside or outside vehicle 100). This helps to accurately and efficiently detect unwanted entities 102 inside or near vehicle 100.

[0021] In some aspects, vehicle lights may include dual light-emitting diode (LED) LEDs or blue-white single LEDs. Dual LEDs may include two light-emitting diodes (LEDs) housed in a single unit, which can provide two different types of light. A blue-white single LED is an LED that appears white but is made using a blue LED core. As mentioned above, vehicle lights can be located in the interior and / or exterior of the vehicle. In the interior, vehicle lights may be located in the interior dome glove box, console lights, door lights (which typically turn on when the door is open), etc. In the exterior, vehicle lights may be located in door handles, headlights, license plates, reversing lights, and side marker lights, which may emit blue-white light, RGB light, UV light, or both.

[0022] Vehicle 100 may also include unwanted physical detection units (in Figure 2 The unwanted entity detection unit (shown as unwanted entity detection unit 210) can detect unwanted entities inside and / or near the vehicle 100. The unwanted entity detection unit (“unit”) can perform / activate an internal scan to detect unwanted entities 102 inside the vehicle 100, and can perform / activate an external scan to detect unwanted entities 102 near the vehicle 100 (or in the area surrounding the vehicle).

[0023] The unit can perform internal scans continuously or under certain conditions. For example, the unit can perform internal scans when a door or window is open or closed. In another case, the unit can perform internal scans continuously when a window remains open. Similarly, the unit can perform external scans when the vehicle 100 is stopped or when the vehicle 100 is in parking mode. In another aspect, the unit can perform internal and / or external scans based on user requests / inputs obtained from user 104. The unit can be performed via a vehicle human-machine interface (HMI) 106 or a user device (in... Figure 2 The diagram shows user device 201 receiving user requests / inputs. The user device can be, for example, a mobile phone, laptop computer, computer, tablet computer, or any other similar device with communication capabilities.

[0024] To perform internal and / or external scans, the unit can control the operation of the vehicle camera and headlights. In some aspects, to perform a scan, the unit can first activate the headlights in the interior and / or exterior of the vehicle to illuminate unwanted entities (if present) inside and / or near the vehicle 100. In response to activating the headlights, the unit can obtain input / images from the vehicle camera. Based on the input from the vehicle camera, the unit can detect the presence of unwanted entities inside or near the vehicle 100 and perform predetermined remedial actions based on the detection. As an example, to perform an internal scan to detect unwanted entity 102 inside the vehicle 100, the unit can activate the headlights in the interior of the vehicle and obtain an image from the vehicle's interior camera. As another example, to perform an external scan to detect unwanted entity 102 near the vehicle 100, the unit can activate the headlights in the exterior of the vehicle and obtain an image from the vehicle's exterior camera.

[0025] In some aspects, the unit can perform one or more image processing algorithms on the image captured by the vehicle camera to detect unwanted entities 102. For example, the unit can apply known filters (sharpening, Gaussian, Laplacian of Gaussian, Sobel, Pruitt, low-pass filtering to reduce noise, etc.) and implement region of interest analysis techniques to enhance the process of detecting unwanted entities 102.

[0026] In some aspects, to detect unwanted entity 102, the unit may first determine the presence of entities inside or near vehicle 100 based on input / images obtained from a vehicle camera. In response to determining the presence of an entity, the unit may compare the obtained image with data from a server (in...) Figure 2The unit associates information (e.g., pre-stored images, details, etc.) obtained by the server (202) or user 104 with multiple unwanted entities. Based on this association, the unit can determine that the entity is an unwanted entity 102. In this way, the unit can search for and identify potentially harmful creatures, such as snakes, scorpions, etc., that may pose a threat to the user in images obtained from the vehicle camera (e.g., by associating the obtained images with pre-stored images of multiple unwanted entities). In another aspect, the unit can search for and identify other creatures / entities that may cause discomfort to the user 104 in images obtained from the vehicle camera (e.g., specific plants that the user 104 may be allergic to). In an exemplary aspect, the unit can identify such other creatures / entities based on user input obtained via HMI 106 and / or user device.

[0027] In response to the detection of an unwanted entity 102, the unit can perform a predetermined remedial action. For example, the unit can output a notification 108 to the user 104 via the HMI 106 and / or user device, indicating the presence of an unwanted entity in (or near) the vehicle 100. The unit can also identify and indicate the location of the unwanted entity in the notification 108. For example, the unit can indicate in the notification 108 that the unwanted entity 102 exists in the footwell space (e.g., in the vehicle 100). Figure 1 (as shown). Similarly, the unit can indicate that unwanted entities 102 exist near (and outside) the vehicle 100, such as near the front passenger door. Additionally, the unit can characterize and identify the type of unwanted entity and indicate the type of unwanted entity in notification 108. The unit can identify the type of unwanted entity based on the association between images obtained from the vehicle camera and information associated with multiple unwanted entities obtained from a server. For example, the unit can indicate the presence of unwanted entities in the footwell (e.g., in the vehicle 100). Figure 1 A scorpion is present in the image shown.

[0028] In some aspects, the notification can be an audible notification in the form of voice, tone, ringtone, etc. In other aspects, when the unit detects an unwanted entity 102 near the vehicle 100, the unit can allow the user 104 (driver and / or other passenger) to open the door with a double pull (opening the door with a single pull may not be permitted). Furthermore, the unit can selectively activate vehicle lights to indicate / illuminate the location of the unwanted entity (e.g., via spotlighting, area lighting, etc.).

[0029] Additionally, the unit can use artificial intelligence (AI) to provide guidance to user 104 on dealing with unwanted entities 102. Furthermore, if user 104 (or any other vehicle passenger) is affected by an unwanted entity 102 in some way (e.g., bitten), the unit can provide guidance.

[0030] The following text combines Figure 2 Describe 100 details of another vehicle.

[0031] Vehicle 100 shall implement and / or perform the operations described herein in accordance with the owner's manual and safety guidelines. Furthermore, any actions taken by user 104 based on notifications provided by vehicle 100 shall comply with all rules specific to the location and operation of vehicle 100 (e.g., federal, state, national, city, etc.). Notifications provided by vehicle 100 shall be considered advice and shall be followed only in accordance with any rules specific to the location and operation of vehicle 100.

[0032] Figure 2 A block diagram of a system 200 for detecting the presence of unwanted entities and performing remedial actions, according to this disclosure, is depicted. In the description... Figure 2 At that time, will refer to Figure 3 .

[0033] System 200 may include a vehicle 100, a user device 201, and one or more servers 202 (or server 202) that can be communicatively coupled to each other via one or more networks 204. The user device 201 may be associated with the vehicle owner / user 104 and may be, for example, a mobile phone, laptop computer, computer, tablet computer, smartwatch, or any other similar device with communication capabilities. Server 202 may be part of a cloud-based computing infrastructure and may be associated with and / or include a Telematics Service Delivery Network (SDN), which delivers services to vehicle 100 and other vehicles that may be part of a vehicle fleet. Figure 2 (Not shown in the image) provides digital data services.

[0034] In some respects, server 202 can store multiple unwanted entities (e.g., combined with the above). Figure 1Information associated with the unwanted entity 102 described. For example, server 202 may store images and names of different unwanted entities, indications of whether the entity poses a threat to humans, characteristics associated with the entity (e.g., scorpions in a particular geographic location are generally non-venomous), typical locations where such entities are present, reasons why the entity is potentially harmful to humans, etc. Additionally, server 202 may store information associated with guidance or best practices on how to handle the unwanted entity 102 (e.g., a user may need gloves and / or a long object to guide the unwanted entity 102 outside vehicle 100), steps to take in the event of a user being affected by the unwanted entity 102 (e.g., being bitten), etc. When server 202 receives a request for information from vehicle 100, server 202 may transmit such information to vehicle 100.

[0035] Network 204 illustrates example communication infrastructure in which connected devices discussed in various embodiments of this disclosure may communicate. Network 204 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 Transmission Control Protocol / Internet Protocol (TCP / IP), Bluetooth, etc. ® 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, to name just a few.

[0036] Vehicle 100 may include multiple units, including but not limited to vehicle computer 206, vehicle control unit (VCU) 208, and unwanted entity detection unit 210 (or unit 210). VCU 208 may include multiple electronic control units (ECUs) 212 that communicate with vehicle computer 206.

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

[0038] Processor 214 can communicate with one or more memory devices (e.g., memory 216 and / or memory) of a corresponding computing system. Figure 2 The processor 214 may communicate with one or more external databases (not shown). The processor 214 may utilize the memory 216 to store programs in code form and / or store data to execute aspects of this disclosure. The memory 216 may be a non-transitory computer-readable medium or memory that stores unwanted entity detection program code. The memory 216 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.).

[0039] According to some aspects, VCU 208 can share a power bus with vehicle computer 206 and can be configured and / or programmed to coordinate the systems of vehicle 100, connected servers (e.g., server 202), user devices 201, and other vehicles operating as part of a vehicle fleet. Figure 2 Data between (not shown in the image). VCU 208 may include or communicate with any combination of ECUs 212, such as Body Control Module (BCM) 218, Engine Control Module (ECM) 220, Transmission Control Module (TCM) 222, Telematics Control Unit (TCU) 224, Driver Assist Technology (DAT) Controller 226, etc.

[0040] VCU 208 may also include and / or communicate with a vehicle perception system (VPS) 228, which has connectivity with and / or controls one or more vehicle sensing systems 230 (or “vehicle sensor units”). The vehicle sensing system 230 may include one or more vehicle sensors, including but not limited to radio detection and ranging (radar) sensors, seating area latch sensors, seating area sensors, light detection and ranging (LiDAR) sensors, door / window sensors (which can detect whether a door / window is open / closed), proximity sensors, temperature sensors, wheel sensors, ambient weather sensors, ambient light sensors, vehicle interior and exterior cameras, one or more rain sensors, humidity sensors, tire pressure sensors, ultrasonic sensors, one or more microphones, etc. The vehicle sensing system 230 may capture images of the area inside and around the vehicle 100 (or near the vehicle 100).

[0041] In some respects, VCU 208 can control vehicle operation aspects and implement one or more instruction sets received from user equipment 201, one or more instruction sets stored in memory 216, including instructions that operate as part of unit 210.

[0042] TCU 224 can provide vehicle connectivity to wireless computing systems on and outside the vehicle 100, and may include a navigation (NAV) receiver 232 for receiving and processing GPS signals, a BLE module (BLEM) 234, a Wi-Fi transceiver, a UWB transceiver, and / or other wireless transceivers that can be configured for wireless communication (including cellular communication) between the vehicle 100 and other systems (e.g., user device 201, key fob, NFC device, etc.), computers, and modules. Figure 2 (Not shown in the image). NAV receiver 232 can be configured to determine the real-time geographical location of the vehicle. TCU 224 can communicate with ECU 212 via a bus.

[0043] ECU 212 can use inputs from the human driver, inputs from the autonomous vehicle controller, inputs from unit 210, and / or wireless signal inputs received from other connected devices (such as user device 201, server 202, etc.) via wireless connection to control various aspects of vehicle operation and communication.

[0044] BCM 218 typically includes integration of sensors, vehicle performance indicators, and variable reactors associated with vehicle systems, and may include a processor-based power distribution circuitry that controls body components such as lights, windows, safety devices, cameras, fans, headlights, audio systems, speakers, wipers, door locks and entry controls, side mirrors, various comfort controls, and headlights 238 (in conjunction with the above). Figure 1 The BCM 218 can also function as a gateway for bus and network interfaces to communicate with remote ECUs (similar to the aforementioned headlights). Figure 2 Interact with (not shown in the image).

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

[0046] In some respects, the vehicle computer 206 can be connected to the infotainment system 236 (or the vehicle human-machine interface (HMI) 236). The HMI 236 can be combined with the above. Figure 1Similar to HMI 106, HMI 236 may include a touchscreen interface 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 aspects, HMI 236 may also receive user commands / inputs via the touchscreen interface and / or display notifications / recommendations, navigation maps, etc., on the touchscreen interface. Vehicle 100 may also include headlights 238, which can be combined with the above description. Figure 1 The headlights described are the same.

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

[0048] Depending on some aspects, unit 210 may be integrated with and / or performed as part of ECU 212. Unit 210 may include transceiver 240, processor 242, and computer-readable storage 244, whether it is integrated with vehicle computer 206 or ECU 212, or whether it operates as a stand-alone computing system in vehicle 100.

[0049] Transceiver 240 can receive information / input from one or more external devices or systems (e.g., user device 201, server 202, etc.) via network 204. For example, transceiver 240 can receive user input or requests from a user via user device 201 to perform internal and / or external scans (as described above). Figure 1 (As described above). Transceiver 240 can also receive input / information associated with unwanted entity 102 from server 202. Furthermore, transceiver 240 can transmit notifications / data / signals to external devices or systems.

[0050] Additionally, transceiver 240 can receive information / input from vehicle 100 components (such as HMI 236, VCU 208 (e.g., vehicle sensing system 230, etc.)). For example, transceiver 240 can receive user input or requests to perform internal and / or external scans from the user via HMI 236. Furthermore, transceiver 240 can transmit notification / command signals to vehicle 100 components (such as VCU 208, HMI 236, BCM 218, headlights 238, etc.).

[0051] Processor 242 and memory 244 may be the same as or similar to processor 214 and memory 216, respectively. In some aspects, processor 242 may utilize memory 244 to store programs in code form and / or store data for execution of aspects according to this disclosure. Memory 244 may be a non-transitory computer-readable medium or memory storing unwanted entity detection program code.

[0052] In operation, processor 242 may first obtain a trigger signal to detect the presence of any unwanted entity (e.g., unwanted entity 102) inside or near vehicle 100 (or in the area surrounding vehicle 100). In some aspects, processor 242 may obtain the trigger signal from user 104 via HMI 236 or user device 201. Alternatively or additionally, processor 242 may obtain the trigger signal from VCU 208 or based on input obtained from VCU 208 (e.g., based on input obtained from vehicle sensing system 230), as described below.

[0053] In some respects, processor 242 can obtain a first trigger signal to perform an internal scan to detect the presence of unwanted entities inside vehicle 100. When user 104 requests vehicle 100 to perform an internal scan, processor 242 can obtain the first trigger signal from user 104 via HMI 236 or user device 201. Alternatively or additionally, processor 242 can obtain the first trigger signal from VCU 208 when a door or window moves from a closed state to an open state, and vice versa (because the probability of unwanted entities entering vehicle 100 is high in such cases). In another respect, processor 242 can continuously perform internal scans while the window remains open.

[0054] Similarly, processor 242 can obtain a second trigger signal to perform an external scan to detect the presence of unwanted entities in or around vehicle 100. When user 104 requests vehicle 100 to perform an external scan, processor 242 can obtain the second trigger signal from user 104 via HMI 236 or user device 201. Alternatively or additionally, when vehicle 100 is stopped or when vehicle 100 is placed in parking mode, processor 242 can obtain the second trigger signal from VCU 208 (because the probability associated with user 104 leaving vehicle 100 is high in such cases). In such cases, processor 242 performs an external scan to check for the presence of any unwanted entities in or around vehicle 100 and whether to recommend that user 104 leave vehicle 100.

[0055] In response to receiving a trigger signal (e.g., a first trigger signal or a second trigger signal), processor 242 can initiate an internal scan or an external scan. To perform the scan (internal or external), processor 242 can control or activate the operation of the headlights 238 and the vehicle sensing system 230 (or vehicle sensors / cameras). In some aspects, to initiate a scan, processor 242 can first activate the headlights 238 to illuminate an unwanted entity (if it exists inside or outside the vehicle 100, as described above). Figure 1 This enables the processor 242 to efficiently detect the presence of unwanted entities inside or near the vehicle 100. The processor 242 may activate the headlights 238 in the interior of the vehicle in response to receiving a first trigger signal. Alternatively, the processor 242 may activate the headlights 238 in the exterior of the vehicle in response to receiving a second trigger signal.

[0056] In response to activating the headlights 238, the processor 242 can activate the vehicle sensing system 230 (or vehicle camera) so that the vehicle sensing system 230 can capture an image of the unwanted entity 102 illuminated by the headlights 238. In response to activating the vehicle sensing system 230, the processor 242 can obtain input / images from the vehicle sensing system 230. During an interior scan, when the processor 242 activates the headlights 238 in the interior of the vehicle, the processor 242 can activate the interior camera and obtain input from the interior camera. Similarly, during an exterior scan, when the processor 242 activates the headlights 238 in the exterior of the vehicle, the processor 242 can activate the exterior camera and obtain input from the exterior camera.

[0057] In response to acquiring input / images from the vehicle camera, processor 242 can detect the presence of unwanted entities inside or near vehicle 100 based on the acquired input / images. Processor 242 can detect the presence of unwanted entities inside vehicle 100 by using an interior scan (e.g., by using an interior vehicle camera and headlights 238 located in the interior portion of the vehicle). Similarly, processor 242 can detect the presence of unwanted entities near or outside vehicle 100 by using an exterior scan (e.g., by using an exterior vehicle camera and headlights 238 located in the exterior portion of the vehicle).

[0058] In addition to performing the scan as described above, processor 242 can also obtain information associated with multiple unwanted entities from server 202 by transmitting a request to server 202. Server 202 can receive the request and transmit the required input / information (including images of multiple unwanted entities and their corresponding names / types) to processor 242 via transceiver 240. In response to obtaining this information from server 202, processor 242 can compare / correlate the image captured by the vehicle camera with the image obtained from server 202. Processor 242 can detect the presence of unwanted entities in the image obtained from the vehicle camera (and thus detect their presence inside or outside vehicle 100) based on the comparison / correlation. For example, if the captured image substantially matches at least one image obtained from the server, processor 242 can determine that the unwanted entity (e.g., unwanted entity 102) may exist inside or outside vehicle 100.

[0059] In some respects, processor 242 can perform image processing on images acquired from the vehicle camera to detect the presence of unwanted entities. In other words, processor 242 can use image processing techniques to determine whether the images acquired from the vehicle camera depict any unwanted entities (by associating the images with those acquired from server 202, as described above). For example, processor 242 can apply known filters (sharpening, Gaussian, Laplacian of Gaussian, Sobel, Pruitt, low-pass filtering to reduce noise, etc.) and implement region of interest analysis techniques to further enhance the process of detecting unwanted entities 102 in the images acquired from the vehicle camera.

[0060] As described above, in order to detect unwanted entity 102, processor 242 can first determine the presence of entities inside or near vehicle 100 based on input / images obtained from vehicle cameras. In response to determining the presence of an entity, processor 242 can correlate the captured image with information obtained from server 202 (or user 104). Based on this correlation, processor 242 can determine that the entity is unwanted. In this way, processor 242 can search for and identify known harmful creatures that pose a threat to humans, such as snakes and scorpions, in images obtained from vehicle cameras based on information obtained from server 202. In other words, processor 242 can identify and characterize unwanted entity 102 based on information or input obtained from server 202. For example, processor 242 can determine that unwanted entity 102 is a snake that may pose a threat to user 104 based on information obtained from server 202. In another aspect, as described above... Figure 1The processor 242 can search for and identify other organisms in images acquired from the vehicle camera that may cause discomfort to the user 104 (e.g., based on user input obtained via HMI 106 and / or user device 201). In other words, the processor 242 can identify and characterize unwanted entities 102 based on input obtained from the user 104. In some aspects, the processor 242 can use artificial intelligence (AI) / machine learning (ML) models to characterize / identify unwanted entities in images acquired from the vehicle camera.

[0061] Additionally, processor 242 can determine the location of unwanted entities inside or outside the vehicle 100 based on images obtained from vehicle cameras. For example, processor 242 can determine that unwanted entity 102 exists in the vehicle's footwell space based on images obtained from vehicle cameras (e.g., based on vehicle cameras that have captured images of unwanted entities and / or the locations of vehicle components captured in the images other than unwanted entity 102). Similarly, processor 242 can determine that unwanted entity 102 exists on a tree located at the front of the vehicle (e.g., based on the location of a vehicle camera that has captured images of unwanted entities). For example, when processor 242 detects the presence of unwanted entities based on images obtained from the vehicle's front exterior camera, processor 242 can determine that unwanted entity 102 exists in the front of the vehicle.

[0062] As described above, processor 242 can perform one or more predetermined remedial actions in response to detecting the presence of an unwanted entity. In one exemplary aspect, processor 242 can output a first notification (in conjunction with the above) on HMI 236 or user device 201 in response to detecting the presence of an unwanted entity. Figure 1 The notification 108 indicates to user 104 that an unwanted entity 102 is present inside or near vehicle 100. Additionally, processor 242 can characterize and identify the type of the unwanted entity and indicate this type in the first notification. Processor 242 can identify the type of the unwanted entity based on the association between images obtained from vehicle cameras and information associated with multiple unwanted entities obtained from server 202 (or user 104). For example, when processor 242 detects a scorpion inside vehicle 100, processor 242 can output a notification that "scorpion" is present inside vehicle 100. Notification 108 can also provide additional information associated with the unwanted entity 102. For example, notification 108 can indicate the location of the unwanted entity, such as in the footwell, glove box, etc.

[0063] Similarly, when processor 242 detects that a snake is located on a tree in front of the vehicle, processor 242 can output a second notification 302 indicating that the snake is near vehicle 100, such as... Figure 3 As depicted in the image. Notification 302 may also provide additional information associated with the unwanted entity 102. For example, notification 302 may include the location of the snake, such as a tree located in front of a vehicle.

[0064] The aforementioned notifications (e.g., notification 108 and / or notification 302) may also include instructions on how to prevent interaction with the unwanted entity 102. For example, the notification may indicate that the snake is located near the front passenger door, so the user should not open the front passenger door and exit through it. Alternatively, the notification may suggest that the user 104 move to another location and then open the door.

[0065] In another aspect, as part of a pre-planned remedial action, processor 242 may use input or information obtained from server 202 associated with multiple unwanted entities and provide user 104 with guidance on how to handle the unwanted entity 102. For example, processor 242 may use the information obtained from server 202 associated with multiple unwanted entities to determine whether the effective way to handle the scorpion is to put on gloves and then remove the scorpion from the vehicle or to push the scorpion out using a long object / pole. Processor 242 may output such information via the aforementioned notification to help the user handle the situation and guide the unwanted entity 102 away from vehicle 100.

[0066] Processor 242 may also (via the aforementioned notification) provide information associated with potentially harmful situations that unwanted entity 102 may pose to user 104 and / or other passengers in vehicle 100. Processor 242 may identify such information by using input or information obtained from server 202 that is associated with multiple unwanted entities. Additionally, if user 104 (or any other vehicle passenger) is affected by unwanted entity 102 in any way (e.g., bitten), processor 242 may output a notification to provide instructions / guidance. Processor 242 may use AI to determine such relevant information for user 104 using information / input obtained from server 202.

[0067] In another aspect, as part of a predetermined remedial action, processor 242 may output a command to a speaker to issue an audible notification to user 104, indicating the presence of an unwanted entity inside or near vehicle 100. The audible notification may be in the form of voice, tone, ringtone, etc. In another aspect, as part of a predetermined remedial action, when processor 242 detects an unwanted entity 102 near vehicle 100, processor 242 may require a double pull to allow user 104 to open the door. In other words, when unwanted entity 102 is near vehicle 100, when processor 242 receives a double pull signal from user 104, processor 242 may enable user 104 to open the door, and in response to receiving the double pull signal, enable user 104 to open the door.

[0068] In another aspect, as part of a predetermined remedial action, processor 242 may determine the location of an unwanted entity inside or outside vehicle 100 based on images obtained from vehicle cameras, and selectively activate headlights 238 to indicate / illuminate the determined location so that user 104 can identify / view the location. In another aspect, as part of a predetermined remedial action, when an unwanted entity 102 is located near vehicle 100 and (e.g., via vehicle speakers / sound exciter) an alarm notification indicating the presence of an unwanted entity near vehicle 100 is output to another user, processor 242 may check for the presence of another user near vehicle 100 (based on images obtained from vehicle cameras). The notification may be in the form of voice, tone, ringtone, etc. Processor 242 may also selectively activate headlights 238 to illuminate the location of the unwanted entity to further indicate to another user (e.g., via spotlighting, via area lighting if another user is closer to the unwanted entity 102, etc.).

[0069] In another aspect, as part of a pre-planned remedial action, processor 242 can mark the location of unwanted entities, enabling other vehicle users traveling in the same geographic area to be aware of the unwanted entities' location. Processor 242 can also exchange images of the unwanted entities with other vehicle users via V2V or V2X communication. For example, a user might mark a nettle plant (a type of nettle) and geofence the location of the marked plant. Other vehicles in the group can use their HMIs to transmit the location of the found plant and utilize their camera suites to identify other examples of the same plant.

[0070] Figure 4 A flowchart depicts an example method 400 for detecting the presence of unwanted entities and performing remedial actions according to this disclosure. Further description can be made with reference to the preceding figures. Figure 4The 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 a different order than that described in the following example embodiments.

[0071] Method 400 begins at step 402. At step 404, method 400 may include activating the vehicle lights 238 by processor 242 to enable the detection of the presence of unwanted entities inside or near vehicle 100. At step 406, method 400 may include obtaining input from a vehicle camera by processor 242 in response to activating the vehicle lights 238. At step 408, method 400 may include detecting the presence of unwanted entities inside or near vehicle 100 by processor 242 based on the obtained input. At step 410, method 400 may include performing a predetermined remedial action by processor 242 based on the detection.

[0072] At step 412, method 400 can stop.

[0073] 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,” “example 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. Moreover, 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.

[0074] 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 understand, components may be referred to by different names. This document is not intended to distinguish between components with different names but identical functions.

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

[0076] 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. A computing device may include computer-executable instructions, wherein the instructions may be executable by one or more computing devices (such as those listed above) and stored on a computer-readable medium.

[0077] 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 a different order than 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.

[0078] 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. Future developments in the techniques discussed herein are anticipated and expected, and the disclosed systems and methods will be incorporated into such future embodiments. In conclusion, it should be understood that modifications and changes are possible with this application.

[0079] Unless expressly 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.

[0080] According to an embodiment, in order to perform a predetermined action, the processor outputs a second notification to provide guidance on processing unwanted entities.

[0081] According to an embodiment, in order to perform a predetermined action, when a vehicle user is affected by an unwanted entity, the processor outputs a third notification to provide guidance to the vehicle user.

[0082] According to an embodiment, in order to perform a predetermined action, the processor: when an unwanted entity is located near the vehicle, determines that a second user is near the vehicle based on input obtained from the vehicle camera; and outputs a fourth notification to the second user, wherein the fourth notification indicates that an unwanted entity is near the vehicle.

[0083] According to the present invention, a method includes: activating vehicle lights by a processor to enable the detection of the presence of an unwanted entity inside or near the vehicle, wherein the vehicle lights are configured to illuminate the unwanted entity inside or near the vehicle; receiving input from a vehicle camera by the processor in response to activating the vehicle lights, wherein the vehicle camera is configured to capture an image of the interior or vicinity of the vehicle; detecting the presence of the unwanted entity inside or near the vehicle by the processor based on the input; and performing a predetermined action by the processor based on the detection.

[0084] According to the present invention, a non-transitory computer-readable storage medium is provided having instructions stored thereon, which, when executed by a processor, cause the processor to: activate vehicle lights to enable the detection of the presence of unwanted entities inside or near the vehicle, wherein the vehicle lights are configured to illuminate unwanted entities inside or near the vehicle; obtain input from a vehicle camera in response to activating the vehicle lights, wherein the vehicle camera is configured to capture an image of the interior or vicinity of the vehicle; detect the presence of unwanted entities inside or near the vehicle based on the input; and perform a predetermined action based on the detection.

Claims

1. A vehicle comprising: A vehicle camera configured to capture images of the interior of the vehicle or the vicinity of the vehicle; Vehicle lights, which are configured to illuminate unwanted entities inside the vehicle or near the vehicle; as well as Processor, the processor being configured to: Activate the vehicle lights to enable the detection of the presence of unwanted entities inside or near the vehicle; Input is received from the vehicle camera in response to activating the vehicle lights; The presence of the unwanted entity inside or near the vehicle is detected based on the input; and Based on the detection, a predetermined action is performed.

2. The vehicle of claim 1, wherein the headlights are configured to emit ultraviolet (UV) light.

3. The vehicle of claim 1, wherein the headlights are configured to emit blue light.

4. The vehicle of claim 1, wherein the processor is further configured to: A first trigger signal is obtained to detect the presence of the unwanted entity inside the vehicle; and The vehicle lights in the interior of the vehicle are activated in response to receiving the first trigger signal.

5. The vehicle of claim 4, wherein when a door or window moves from a closed state to an open state, the processor obtains the first trigger signal from the vehicle control unit, or vice versa.

6. The vehicle of claim 4, wherein the processor obtains the first trigger from a vehicle human-machine interface (HMI) or user device.

7. The vehicle of claim 1, wherein the processor is further configured to: A second trigger signal is obtained to detect the presence of the unwanted entity near the vehicle; and The vehicle lights in the interior of the vehicle are activated in response to receiving the second trigger signal.

8. The vehicle of claim 7, wherein the processor receives the second trigger signal from the vehicle control unit when the vehicle is stopped or when the vehicle is placed in parking mode.

9. The vehicle of claim 7, wherein the processor obtains the second trigger signal from a vehicle human-machine interface (HMI) or user device.

10. The vehicle of claim 1, wherein, in order to perform the predetermined action, the processor outputs a first notification on a vehicle human-machine interface (HMI) or user device, and wherein the first notification indicates the presence of the unwanted entity inside or near the vehicle.

11. The vehicle of claim 1, wherein, in order to perform the predetermined action, the processor outputs instructions to emit an audible notification from a speaker of a vehicle user, and wherein the audible notification indicates the presence of the unwanted entity inside or near the vehicle.

12. The vehicle of claim 1, wherein, in order to perform the predetermined action, the processor: When the unwanted entity is near the vehicle, a double-pull signal to open the vehicle door is received from the vehicle user; and This enables the vehicle user to open the door in response to receiving the double pull signal.

13. The vehicle of claim 1, wherein, in order to perform the predetermined action, the processor: The location of the unwanted entity is determined based on the input obtained from the vehicle camera; and The vehicle lights are activated to indicate the location so that vehicle users can identify the location.

14. The vehicle of claim 1, wherein the processor is further configured to: The presence of entities inside or near the vehicle is determined based on the input obtained from the vehicle camera. In response to determining the existence of the entity, the input is associated with information obtained from the server or vehicle user that is linked to multiple unwanted entities; and The entity is determined to be the unwanted entity based on the association.

15. The vehicle of claim 14, wherein the processor is further configured to identify the type of the unwanted entity based on the association.