Proximity-based vehicle tagging

Abstract

To provide a system for tagging vehicles.SOLUTION: A system for tagging vehicles generally includes vehicles with vehicle identification modules with user input processing modules configured to receive start communication including a data set including both of target vehicle identification data and target vehicle state information. The system comprises a vehicle position database including identification information of a plurality of potential target vehicles. The system comprises a server with a server verification module configured to perform query against the vehicle position database for the identification information of the plurality of potential target vehicles to specify a target vehicle among the plurality of potential target vehicles in the vehicle position database on the basis of the target vehicle identification data. The server further comprises a receiver determination module configured to analyze the target vehicle state information to determine at least one target information receiver and to transmit a notification signal to the at least one target information receiver.SELECTED DRAWING: Figure 5

Description

[Technical field]

[0001] The present disclosure relates generally to vehicle-to-server communication, and more particularly, to vehicle-to-server communication for identifying and locating other vehicles. [Background technology]

[0002] Vehicle operators have limited ability to communicate emergency messages to the appropriate authorities in real time to tag / identify other vehicles. Faster, safer, and more reliable communication methods are needed to tag vehicles that may need to be monitored for any reason. For example, the ability to notify authorities of the presence of a broken-down vehicle, a dangerous driver, or a polite driver would allow the appropriate authorities to respond in less time if a response is required. Many existing systems require the communicating driver to divert attention from driving to communicate a message, which can lead to unsafe road conditions and an increase in vehicle accidents. In addition, many existing systems lack the ability to easily locate tagged vehicles based on the location of the communicating vehicle. This can lead to delayed response times and increased injury to vehicle occupants in an emergency. Therefore, it is desirable to enable vehicle operators to communicate in real time with authorities and other vehicle operators on the road to tag / identify vehicles that may need to be monitored for any reason and / or that may need assistance. What is needed, therefore, is an apparatus, system, and / or method that addresses one or more of the above-mentioned problems and / or one or more other problems. Summary of the Invention

[0003] The present disclosure provides a system and method for exchanging information between a vehicle and a cloud to identify reckless, dangerous, or broken-down vehicles and report such vehicles to appropriate authorities. A universal system for tagging vehicles includes a vehicle with a vehicle identification module. The vehicle identification module includes a user input processing module configured to receive an initiation communication including a data set. The data set includes both target vehicle identification data and target vehicle status information. The vehicle identification module further includes a transmitter configured to transmit the data set. The system further includes a vehicle location database including identification information of a plurality of potential target vehicles. The system further includes a server with a server verification module. The server verification module is configured to receive the data set from the transmitter of the vehicle identification module. The server verification module is further configured to query the vehicle location database for identification information of the plurality of potential target vehicles. The server verification module is further configured to identify a target vehicle of the plurality of potential target vehicles in the vehicle location database based on the target vehicle identification data. The server further includes a recipient determination module. The recipient determination module is configured to analyze the target vehicle status information to determine at least one target information recipient. The recipient determination module is further configured to transmit a notification signal to at least one targeted information recipient.

[0004] A further universal system for vehicle tagging includes a vehicle with a user input processing module configured to receive an initiation communication including a first data set. The first data set includes target vehicle identification data. The system further includes a vehicle location database including identification information of a plurality of potential target vehicles. The system further includes a server with a server verification module. The server verification module is configured to receive identification information of the plurality of potential target vehicles in the vehicle location database. The server verification module is further configured to identify a target vehicle among the plurality of potential target vehicles. The target vehicle is associated with the first data set. The server verification module is further configured to verify the first data set by comparing the received target vehicle identification data in the first data set with the identification information of the target vehicle received from the vehicle location database. The server further includes a recipient determination module. The recipient determination module is configured to analyze the first data set to determine at least one target information recipient. The recipient determination module is further configured to transmit a notification signal to the at least one target information recipient.

[0005] A generic method for vehicle tagging includes receiving an initiation communication including a first data set at a user interface of the vehicle. The first data set includes both target vehicle identification data and target vehicle status information. The method further includes transmitting the first data set to a server verification module of a server. The method further includes querying, by the server verification module, a vehicle location database including identification information of a plurality of potential target vehicles. The method further includes identifying, by the server verification module, a target vehicle of the plurality of potential target vehicles. The target vehicle is associated with the first data set. The method further includes determining, based on the first data set, at least one target information recipient of the plurality of target information recipients to which information based on the target vehicle status information is to be transmitted. The method further includes transmitting, by the recipient determination module, a notification signal to the at least one target information recipient. [Brief description of the drawings]

[0006] [Figure 1] FIG. 1 is a schematic diagram of a tagging system in accordance with one or more embodiments of the present disclosure. [Diagram 2] FIG. 2 shows a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. [Diagram 3] FIG. 3 shows a schematic diagram of a system in operation according to one or more embodiments of the present disclosure. [Figure 4] FIG. 4 shows a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. [Diagram 5] FIG. 5 is a flow chart diagram of a method of operation of the system of FIGS. 1-4 in accordance with one or more embodiments of the present disclosure. [Figure 6] FIG. 6 shows a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] For the purposes of promoting an understanding of the principles of the invention, reference will be made to specific implementations or embodiments illustrated in the drawings, and specific terminology will be used to describe the specific implementations or embodiments. It will nevertheless be understood that no limitation of the scope of the invention is intended thereby. Any changes and further modifications in the implementations described, and any further applications of the principles of the invention as described herein, will normally occur to those skilled in the art to which the invention pertains.

[0008] This disclosure describes a communication system for tagging other vehicles, in which a driver of a vehicle on a roadway tags another vehicle on the roadway that is near the driver. When tagging another vehicle, the driver identifies the other vehicle and shares information about the other vehicle (e.g., identification data and status information) with a recipient of the information. For example, the driver can (1) inform a fire engine that the vehicle is broken down on the side of the road, (2) inform a fleet vehicle command center that a fleet vehicle driver is driving well and courteously, or (3) inform a police vehicle that a driver is driving erratically and dangerously. When the driver shares information about the tagged vehicle with a recipient, the shared information also includes the location of the tagged vehicle.

[0009] FIG. 1 is a schematic diagram of a tagging system according to one or more embodiments of the present disclosure. In at least one such embodiment, as shown in FIG. 1, the system is generally referred to by reference number 100 and includes a vehicle 110, a vehicle 120, a cloud server 150, a vehicle location database 160, and an external recipient 170 (which may be an information recipient). In some examples, the vehicle location database 160 includes one or more potential target vehicles, which are discussed in more detail below. The tagging system 100 optionally includes additional vehicles, such as a vehicle 130 and a vehicle 140, as shown in FIG. 1. In addition, the tagging system 100 optionally includes additional vehicle location databases. In the embodiment of FIG. 1, each of the vehicles 110, 120, 130, and 140 is an automobile. 1 are depicted as passenger cars, it should be understood that the vehicles 110, 120, 130, 140 may be any other suitable type of motor vehicle (e.g., pickup truck, semi-truck, fleet vehicle, etc.). The vehicle 110 includes a human machine interface (HMI) 112 (which may be a user interface), a vehicle identification module 114, and vehicle sensors 116. The HMI 112 is operably coupled to the vehicle identification module 114 and configured to communicate with the vehicle identification module 114. The vehicle sensors 116 are also operably coupled to the vehicle identification module 114 and configured to communicate with the vehicle identification module 114. The vehicle identification module 114 is operably coupled to the cloud server 150 and configured to communicate with the cloud server 150. Additionally, vehicle 120 is operably coupled to and configured to communicate with vehicle location database 160, which is itself operably coupled to and configured to communicate with cloud server 150. Cloud server 150 is operably coupled to and configured to communicate with at least one targeted information recipient 170.The targeted information recipient 170 may be, include, or be a portion of various information recipients, as described in more detail below. Thus, as used herein, reference number 170 (without the subscripts a, b, c, d, or e) may refer to one or a combination of information recipients 170a-e. For example, the targeted information recipient 170 may include an ambulance 170a, a fire engine 170b, a police car 170c, a fleet management facility 170d, and an auto dealership 170e. The cloud server 150 is configured to transmit signals to one or more of the information recipients 170, as described in more detail below. Some implementations employ wireless signal transmission, while other implementations utilize wired signal transmission. The ambulance 170a includes a receiver 172a operably coupled to the cloud server 150 and / or another vehicle (e.g., any of the vehicles 110, 120, 130, 140) and configured to receive signals from the cloud server 150 and / or another vehicle. The fire engine 170b includes a receiver 172b operably coupled to the cloud server 150 and / or another vehicle (e.g., any of the vehicles 110, 120, 130, 140) and configured to receive signals from the cloud server 150 and / or another vehicle. The police car 170c includes a receiver 172c operably coupled to the cloud server 150 and / or another vehicle (e.g., any of the vehicles 110, 120, 130, 140) and configured to receive signals from the cloud server 150 and / or another vehicle.

[0010] Like vehicle 110, vehicle 120 includes a human machine interface (HMI) 122, a vehicle identification module 124, and vehicle sensors 126. HMI 122 is operably coupled to vehicle identification module 124 and configured to communicate with vehicle identification module 124. Vehicle sensors 126 are also operably coupled to vehicle identification module 124 and configured to communicate with vehicle identification module 124. Vehicle identification module 124 is operably coupled to cloud server 150 and configured to communicate with cloud server 150. Vehicle 130 includes a human machine interface (HMI) 132, a vehicle identification module 134, and vehicle sensors 136. HMI 132 is operably coupled to vehicle identification module 134 and configured to communicate with vehicle identification module 134. Vehicle sensors 136 are also operably coupled to vehicle identification module 134 and configured to communicate with vehicle identification module 134. The vehicle identification module 134 is operably coupled to the cloud server 150 and configured to communicate with the cloud server 150. The vehicle 140 includes a human machine interface (HMI) 142, a vehicle identification module 144, and vehicle sensors 146. The HMI 142 is operably coupled to the vehicle identification module 144 and configured to communicate with the vehicle identification module 144. The vehicle sensors 146 are also operably coupled to the vehicle identification module 144 and configured to communicate with the vehicle identification module 144. The vehicle identification module 144 is operably coupled to the cloud server 150 and configured to communicate with the cloud server 150.

[0011] Each vehicle identification module 114, 124, 134, 144 is configured to communicate with one or more of the other respective vehicle identification modules via vehicle-to-vehicle (V2V) communications. For example, vehicle identification module 124 may send signals to and receive signals from vehicle identification module 114, as described in more detail below. Additionally, although only vehicle identification module 124 is shown in FIG. 1 as being in communication with vehicle location database 160, it should be understood that one or more of the other vehicle identification modules 114, 134, 144 may also be in communication with vehicle location database 160.

[0012] FIG. 2 illustrates a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. In at least one such embodiment, as shown in FIG. 2, the apparatus is generally referred to by reference number 200 and includes components of the vehicle 110, which are given the same reference numbers. In the embodiment shown in FIG. 2, the vehicle 110 includes a GPS receiver 210, a clock 220, and a microphone 230. In other embodiments, the microphone 230 may be included as a component of the HMI 112. In additional embodiments, the vehicle 110 and / or the HMI 112 may include multiple microphones 230. Similarly, in other embodiments, the GPS receiver 210 may be included as a component of the HMI 112. In the embodiment shown in FIG. 2, the vehicle identification module 114 includes a receiver 113, a sensor processing module 115, a user input processing module 117, and a transmitter 119. In some embodiments, the transmitter 119 and the receiver 113 are integrated into a transceiver capable of both transmitting and receiving wireless signals. The receiver 113 is operably coupled to one or more of the vehicle sensors 116, the sensor processing module 115, the user input processing module 117, the transmitter 119, the GPS receiver 210, the clock 220, the microphone 230, and the HMI 112 and is configured to communicate with one or more of them.

[0013] The HMI 112, which is operably coupled to and configured to communicate with the vehicle identification module 114, includes a display device 240, an input / output (I / O) device 242, and a Bluetooth® communication device 244. The I / O device 242 may be in the form of a communication port (e.g., a USB port), a touch panel display device, a software key associated with the dashboard, a steering wheel, and / or other similar components of the vehicle 110. The display device 240 may be, include, or be part of a plurality of display devices configured to present visual output to a user. For example, in some embodiments, the display device 240 may include one or any combination of a central display device associated with the dashboard of the vehicle 110, an instrument cluster display device associated with the instrument cluster of the vehicle 110, and a head-up display device associated with the dashboard and windshield of the vehicle 110. Thus, as used herein, the reference number 240 may refer to one or a combination of said display devices.

[0014] The vehicle sensor 116 coupled to and configured to communicate with the vehicle identification module 114 may be, include, or be part of, for example, a plurality of vehicle cameras. In some embodiments, the vehicle sensor 116 may include one or any combination of a front camera associated with a front portion of the vehicle 110 (e.g., the front bumper 110a), a rear camera associated with a rear portion of the vehicle 110 (e.g., the rear bumper 110b), a side camera associated with a right side portion 110c of the vehicle 110, a side camera associated with a left side portion 110d of the vehicle 110, and any other camera disposed on the vehicle 110. Thus, as used herein, the reference number 116 may refer to one or a combination of the vehicle cameras. In some embodiments, the vehicle sensor 116 includes any other sensor (e.g., an RFD sensor, a Bluetooth sensor, etc.) capable of identifying and / or communicating with another vehicle.

[0015] In some embodiments, the vehicle sensor 116 is configured to transmit data to the receiver 113 of the vehicle identification module 114. In some embodiments, the vehicle sensor 116 transmits data to the receiver 113 at a set cyclic time period. For example, the vehicle sensor 116 may transmit data to the receiver 113 at a transmission frequency that may range from 10 times per second to once every 10 seconds. In some examples, the transmission frequency may be approximately 10 times per second, approximately 5 times per second, approximately once per second, approximately once every 5 seconds, or any other suitable time interval. The transmission frequencies given herein are for illustrative purposes only, and other embodiments may include more frequent or less frequent transmissions. For example, in some implementations, the transmission frequency may be faster than 10 times per second or slower than once every 5 seconds. In some embodiments, for example, when the vehicle sensor 116 includes one or more vehicle cameras, the data transmitted from the vehicle sensor 116 to the receiver 113 includes images captured by each of the one or more vehicle cameras of the vehicle sensor 116. In such an example, the vehicle sensors 116 may capture images of the external environment around the vehicle 110 as the vehicle 110 travels along a road.

[0016] In some embodiments, data (e.g., image data) transmitted by the vehicle sensors 116 is received by the sensor processing module 115. The data may be received by the sensor processing module 115 directly from the vehicle sensors 116, or the data may be received by the sensor processing module 115 indirectly from the vehicle sensors 116 via the receiver 113. In some examples, the sensor processing module 115 includes an image processor and / or an image processing module. In some embodiments, the sensor processing module 115 is configured to read the data received from the vehicle sensors 116, analyze the data, process the data, and output the processed data to the transmitter 119. In some embodiments, the transmitter 119 then transmits the data to the cloud server 150, which will be described in more detail below.

[0017] In some embodiments, the GPS receiver 210 is operably coupled to the receiver 113 of the vehicle identification module 114 and configured to communicate with the receiver 113 of the vehicle identification module 114. The GPS receiver 210 is configured to record vehicle position data and transmit the vehicle position data to the receiver 113. The receiver 113 is configured to communicate with the transmitter 119. For example, the receiver 113 outputs the vehicle position data to the transmitter 119. In some embodiments, the transmitter 119 then transmits the vehicle position data to the cloud server 150, which is described in more detail below. In some embodiments, each of the vehicles 110, 120, 130, 140 is configured to communicate with one or more of the vehicles 110, 120, 130, 140 via vehicle-to-vehicle (V2V) communication, as described above. In such embodiments, the vehicle 120 is configured to communicate, for example, the GPS location of the vehicle 120 to the vehicle 110. The transmitter 119 of the vehicle identification module 114 may then transmit the GPS location of the vehicle 120 to the server 150 .

[0018] In some embodiments, the clock 220 is operably coupled to the receiver 113 of the vehicle identification module 114 and configured to communicate with the receiver 113 of the vehicle identification module 114. In some embodiments, the clock 220 records the time when each image is captured by the vehicle sensor 116. In other embodiments, the clock 220 records the time when each image is transmitted from the vehicle sensor 116 to the receiver 113 or to the sensor processing module 115. The recorded time may be attached to each data transmission as a timestamp. In some embodiments, the clock 220 is configured to transmit the timestamp information to the receiver 113. The receiver 113 is configured to output the timestamp information to the transmitter 119. In some embodiments, the transmitter 119 then transmits the timestamp information to the cloud server 150, which will be described in more detail below.

[0019] In some embodiments, the microphone 230 is operably coupled to the receiver 113 of the vehicle identification module 114 and configured to communicate with the receiver 113 of the vehicle identification module 114. In some embodiments, the microphone 230 may be, include, or be part of a plurality of microphones located throughout the interior of the vehicle 110. The microphone 230 is configured to receive input from one or more occupants of the vehicle 110 (e.g., the driver and / or one or more passengers). In some embodiments, the input from the vehicle occupants received by the microphone 230 is voice input, which is described in more detail below. The voice input may include an initiating communication. For example, the driver of the vehicle 110 may speak commands and / or information into the microphone 230. In some embodiments, the microphone 230 may be included as a component of the human machine interface (HMI) 112. In some embodiments, the initiating communication includes a data set including target vehicle identification data and target vehicle status information, which is described in more detail below. In some embodiments, the target vehicle identification data may include one or more of color, make, model, type (e.g., truck, sedan, SUV, etc.), license plate number, bumper sticker, decal, advertisement, or any other similar identifying feature, as discussed in more detail below. In some examples, the target vehicle status information includes information regarding the status of the vehicle (e.g., broken down, on fire, stranded, etc.), information regarding the driving ability of the driver of the target vehicle (e.g., erratic driving, dangerous driving, careful driving, safe driving, etc.), or any other similar information about the target vehicle, as discussed in more detail below.

[0020] FIG. 3 illustrates a schematic diagram of a system in operation according to one or more embodiments of the present disclosure. In at least one such embodiment, as shown in FIG. 3, the system is generally referred to by reference number 300 and includes components of tagging system 100, which are given the same reference numbers. In the embodiment shown in FIG. 3, in addition to the system having certain components of tagging system 100, the cloud server 150 of system 300 includes a server validation module 310 and a recipient determination module 320. In the embodiment shown in FIG. 3, the server validation module 310 includes a receiver 312, a transmitter 314, a memory 316, and a processor 318. In some embodiments, the transmitter 314 and the receiver 312 are integrated into a transceiver capable of both transmitting and receiving wireless or wired signals. The receiver 312 is operably coupled to and configured to communicate with one or more of the HMI 112 (see FIG. 2), the sensor processing module 115 (see FIG. 2), the user input processing module 117 (see FIG. 2), the transmitter 314, and the vehicle location database 160. In the embodiment shown in FIG. 3, the recipient determination module 320 includes a receiver 322, a processor 324, a recipient database 326, and a transmitter 328. In some embodiments, the transmitter 328 and the receiver 322 are integrated into a transceiver capable of both transmitting and receiving wireless or wired signals. The receiver 322 is operably coupled to and configured to communicate with one or more of the HMI 112, the transmitter 119, and the transmitter 314 of the server verification module 310.

[0021] In some embodiments, the memory 316 is operably coupled to the receiver 312 and configured to communicate with the receiver 312. In some embodiments, the receiver 312 is configured to receive one or more data transmissions from the transmitter 119 of the vehicle identification module 114 carried by the vehicle 110. In some other embodiments, the receiver 312 is configured to receive data transmissions from the vehicle location database 160 in addition to or instead of the data transmissions received from the transmitter 119, which will be discussed in more detail below. The receiver 312 is configured to output each of the one or more data transmissions to the memory 316, which stores each of the one or more data transmissions for a set period of time before discarding them. In some embodiments, the data transmissions are stored in the past records 317. In some examples, the set period of time for which the memory 316 stores the data transmissions includes 1 minute, 2 minutes, 5 minutes, 10 minutes, or any other suitable period of time that may be less than 1 minute or more than 10 minutes. Therefore, in some embodiments, the memory 316 maintains a historical record 317 of all data transmissions received by the receiver 312 from the transmitter 119. The historical record may be short, in some embodiments, about 30 minutes or less. In some embodiments, the historical data stored in the historical record 317 of the memory 316 is used by the processor 318 to validate data processed by the sensor processing module 115 and / or the user input processing module 117, as will be discussed in more detail below.

[0022] In some embodiments, the processor 324 is operably coupled to and configured to communicate with the receiver 322, the recipient database 326, and the transmitter 328. In some embodiments, the processor 324 is configured to read and analyze one or more data transmissions received from the receiver 322. The processor 324 is further configured to analyze the recipient database 326 to determine, for each received data transmission, which one or more recipients in the recipient database 326 should receive the data transmission. This process is described in more detail below. After the processor 324 determines the appropriate recipient to receive the data transmission, the transmitter 328 transmits the data transmission to the appropriate recipient. In the embodiment shown in FIG. 3, which is merely for illustrative purposes and is not intended to be limiting, the processor 324 has determined that the appropriate recipient is the fleet vehicle management facility 170d (see FIG. 1). In this example, after such a determination is made, the transmitter 328 of the recipient determination module 320 transmits a signal, which may be a notification signal, to the fleet vehicle management facility 170d. In some embodiments, the notification signal includes location information of the tagged / identified vehicle (e.g., a target vehicle) and information regarding the status of the tagged / identified vehicle (e.g., the vehicle is broken down, the vehicle's tail lights are out, the driver of the vehicle is a good driver, etc.), as discussed in more detail below.

[0023] 4 shows a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. In at least one such embodiment, as shown in FIG. 4, the apparatus is generally referred to by reference numeral 400 and includes components of system 300, which are given the same reference numerals. In the embodiment shown in FIG. 4, in addition to the apparatus 400 having certain components of system 300, a recipient database 326 of the apparatus 400 includes a number of potential recipients. The recipients in the recipient database 326 are each configured to receive a signal from a transmitter 328. In some examples, the potential recipients in the recipient database 326 include an ambulance 326a (similar to ambulance 176a), a fire engine 326b (similar to fire engine 176b), a police car 326c (similar to police car 176c), a fleet management facility 326d (similar to fleet management facility 176d), a car dealership 326e (similar to car dealership 176e), a hospital 326f, an emergency contact 326g for the driver of the vehicle 110, an insurance company 326h, and a Department of Motor Vehicles (DMV) 326i. As discussed above and in more detail below, the processor 324 is configured to analyze the recipient database 326 to determine, for each received data transmission, which one or more recipients in the recipient database 326 should receive a notification signal based on each received data transmission. In some embodiments, each received data transmission pertains to a tagged / identified vehicle, which is discussed in more detail below. After the processor 324 determines the appropriate recipient to receive the notification signal, the transmitter 328 transmits the notification signal to the appropriate recipient. In some examples, the transmitter 328 may transmit the notification signal to one or more recipients. For example, the transmitter 328 may transmit the notification signal to an ambulance 326a, a fire engine 326b, a police car 326c, and a hospital 326f. In other examples, the transmitter 328 may transmit the notification signal only to the police car 326c.

[0024] 5 is a flow chart diagram of a method of operation of the tagging system 100 of FIGS. 1-4 in accordance with one or more embodiments of the present disclosure. The method is performed in response to the vehicle identification module 114 receiving input from at least one of: (1) one or more occupants of the vehicle 110 (e.g., the driver and / or one or more passengers); or (2) the vehicle sensors 116.

[0025] In some embodiments, as described above, a driver of a vehicle (e.g., vehicle 110) tags another vehicle (e.g., vehicle 120) on the road near vehicle 110. When tagging the other vehicle, vehicle 110 receives information from the driver of vehicle 110, including the identification data and status information of the other vehicle. Vehicle 110 transmits this identification data and status information to a server. The server receives the information, analyzes the information, and determines a target recipient (which may be a targeted information recipient) to whom the status information should be sent. It is the purpose of the server to validate the received information before sending the status information to the targeted recipient. This helps to reduce the number of false reports sent to potential targeted recipients. To this end, the server compares the information received from vehicle 110 to a database of information of several other vehicles to determine whether there is a match. If there is a match, the server transmits the status information of the other vehicle (e.g., vehicle 120) to the determined targeted recipient. The server also transmits the location of the other vehicle to the determined targeted recipient so that the targeted recipient can take appropriate action if necessary.

[0026] 5, the method is generally referred to by reference numeral 500 and includes receiving 510 an initiation communication including a first data set including both target vehicle identification data and target vehicle state information. In some embodiments, the initiation communication is received by a receiver 113 of the vehicle identification module 114. The receiver 113 may then output the initiation communication to the sensor processing module 115 and / or the user input processing module 117 for further analysis and processing.

[0027] In some embodiments, the initiating communication includes one or more of a voice input, a touch input (e.g., the driver may select an option on a touch panel of the HMI 112, the driver may press a button on the dashboard of the vehicle 110, the driver may press a button on the steering wheel of the vehicle 110, etc.), a visual input (e.g., the HMI 112 may determine where the driver is looking on the screen of the HMI 112), or any other similar input. In some embodiments, the initiating communication includes a combination of one or more of the above inputs. For example, the driver of the vehicle 110 may press a button on the steering wheel to activate the microphone 230, after which the driver may speak identification information, such as an identification feature, of another vehicle (e.g., the vehicle 120 (see FIG. 1 ), which may be a target vehicle). In some embodiments, the first data set includes, for example, identification information of the vehicle 120. In such embodiments, as described above, the initiating communication and / or the identification information includes identification data of the vehicle 120 (which may be target vehicle identification data) and status information of the vehicle 120 (which may be target vehicle status information). In some embodiments, the identification information in the first data set is information identified by the driver of vehicle 110 and / or one or more passengers of vehicle 110. The target vehicle identification data may include one or more of the following: color, make, model, type (e.g., truck, sedan, SUV, etc.), license plate number, bumper sticker, decal, advertisement, or any other similar identifying feature. In some embodiments, each vehicle is associated with a unique set of identification information. For example, each of vehicles 110, 120, 130, 140 is associated with a respective set of identification information.

[0028] In embodiments where the driver of vehicle 110 interacts with a touch panel of HMI 112, the touch panel may display all vehicles currently in the vicinity of vehicle 110. The vicinity of vehicle 110 includes the external environment surrounding vehicle 110. In some embodiments, vehicles in the vicinity of vehicle 110 may include one or more vehicles in the immediate vicinity of vehicle 110, one or more vehicles within 500 feet (about 152 meters) of vehicle 110, or one or more vehicles within any other suitable distance of vehicle 110, which may be greater than 500 feet (about 152 meters) of vehicle 110. The touch panel may display the surrounding vehicles (e.g., vehicles 120, 130, 140) with separate icons that identify each vehicle by type and color. In some embodiments, the icons may also include the make, model, and / or any other identifying characteristics of each vehicle. In other examples, the touch panel may display the surrounding vehicles in a list that does not include pictorial icons. In the list of surrounding vehicles, each vehicle may be identified by one or more of color, type, make, model, or any other identifying characteristic. For example, one of the vehicles may be listed as a "blue Toyota RAV4®."

[0029] In some embodiments, the driver of the vehicle 110 may press a picture icon or a phrase in the list to identify one or more of the surrounding vehicles as target vehicles. In other embodiments, the driver of the vehicle 110 may gaze at one or more of the icons or phrases in the list to identify one or more of the surrounding vehicles as target vehicles. In some embodiments, the vehicle 110 is operable in an autonomous mode. In such embodiments, it may be easier for the driver of the vehicle 110 to identify a target vehicle using touch and / or visual input, as described above. In further embodiments, the driver of the vehicle 110 may identify one or more of the surrounding vehicles of the vehicle 110 by speaking the identification information of the target vehicle, as described above. The microphone 230 (see FIG. 2) of the vehicle 110 identifies and records the driver's voice when the driver is speaking.

[0030] In some embodiments, as described above, the vehicle sensor 116 is configured to capture images of objects, such as vehicles (e.g., vehicle 120), that are in the vicinity of the vehicle 110. In some embodiments, the vehicle sensor 116 transmits each captured image to the sensor processing module 115 of the vehicle identification module 114. In some examples, a GPS location and a timestamp of the vehicle 110 are transmitted with each captured image. In some embodiments, the GPS location information indicates the location of the vehicle 110 at the moment each image was captured. In some examples, the timestamp information indicates the time each image was captured. In some embodiments, the sensor processing module 115 is configured to analyze each image to determine identification information (e.g., target vehicle identification data) of each vehicle (e.g., vehicle 120) included in each captured image. The target vehicle identification data may include one or more of color, make, model, type (e.g., truck, sedan, SUV, etc.), license plate number, bumper sticker, decal, advertisement, or any other similar identifying feature. In some embodiments, after the sensor processing module 115 processes each received image, the vehicle identification module 114 transmits each processed image, as well as GPS location information and timestamps corresponding to each processed image, to the server verification module 310. The processed images and corresponding GPS location information and timestamps may be stored in an historical record 317 in the memory 316 of the server verification module 310. Thus, in some embodiments, the memory 316 maintains an historical record 317 of all data transmissions received from the vehicle identification module 114. In some examples, the data transmissions include the processed images, the GPS location and timestamps corresponding to each processed image, target vehicle identification data, and target vehicle status information, as described in more detail below.

[0031] During or after receiving the initiation communication at step 520, the first data set is transmitted to the server verification module 310 of the server 150. In some embodiments, the initiation communication is transmitted by the transmitter 119 of the vehicle identification module 114. At step 530, the first data set is received by the server verification module 310. In some embodiments, the initiation communication is received by the receiver 312 of the server verification module 310.

[0032] Before, during, or after receiving the initiation communication at step 540, the server verification module 310 queries the vehicle location database 160. In some embodiments, the vehicle location database 160 includes an identification of at least one vehicle, such as vehicle 120, which may be a target vehicle and / or a potential target vehicle. In some embodiments, the vehicle location database 160 includes an identification of a plurality of potential target vehicles, which may include each vehicle connected to the server 150. Each of the potential target vehicles may also transmit a GPS location corresponding to each of the potential target vehicles to the vehicle location database 160. In some embodiments, each of the potential target vehicles, such as vehicle 120, transmits a GPS location to the vehicle location database 160 every 30 seconds, every minute, every two minutes, every five minutes, or any other suitable time interval that may be sooner than every 30 seconds or longer than every five minutes. Thus, in some embodiments, the vehicle location database 160 includes a current location, or an approximate current location, of each of the potential target vehicles within the tagging system 100 (see FIG. 1 ).

[0033] In some embodiments, as described above, the tagging system 100 may include more than one vehicle location database 160. For example, the tagging system 100 may include one vehicle location database 160 corresponding to one or more providers (e.g., an internet service provider, a wireless communication system provider, etc.). In such embodiments, the server validation module 310 may query each vehicle location database 160.

[0034] In some embodiments, the identification information is received by the receiver 312 of the server verification module 310. In some examples, the processor 318 of the server verification module 310 receives the identification information for each vehicle in the vehicle location database 160. The processor 318 parses the identification information received from the vehicle location database 160. Further, the processor 318 compares the parsed identification information to the identification information received from the vehicle identification module 114 of the vehicle 110 (e.g., the received identification information in the first data set).

[0035] In some embodiments, the server validation module 310 reduces the amount of identification information to be parsed before parsing the identification information received from the vehicle location database 160. In such an embodiment, the processor 318 of the server validation module 310 queries the vehicle location database 160 to determine which vehicles were near the vehicle 110 at the time indicated by the timestamp of the initiating communication received by the vehicle identification module 114. The processor 318 uses the GPS location of the vehicle 110 in the initiating communication to make a query to the vehicle location database 160. In some embodiments, the query returns a subset of the identification information that is a subset of the total amount of identification information present in the vehicle location database 160. The processor 318 may parse the subset of the identification information and may compare the parsed identification information to the identification information received from the vehicle identification module 114 of the vehicle 110 (e.g., the identification information received in the first data set).

[0036] During or after querying vehicle location database 160 in step 550, a target vehicle (e.g., vehicle 120) of the plurality of potential target vehicles is identified by server verification module 310, the target vehicle being associated with the first data set. In some embodiments, server verification module 310 determines which identification information of the vehicle in vehicle location database 160 matches the identification information received from vehicle identification module 114 of vehicle 110. In some embodiments, if there is a match, server verification module 310 stops parsing the identification information in vehicle location database 160. In various examples, server verification module 310 determines the location of vehicle 120 based on the identification information associated with vehicle 120, including, for example, GPS position data for vehicle 120.

[0037] In some embodiments, after the server verification module 310 determines that there is a match, the server verification module 310 augments the location information of the vehicle 120. This allows the server verification module 310 to verify the location of the vehicle 120, which helps the server verification module 310 reduce the occurrence of false reports by the driver and / or passengers of the vehicle 110 (e.g., helps reduce the occurrence of false initiation communications, false first data sets, false notification signals, etc.). In some embodiments, the server verification module 310 augments the location information of the vehicle 120 by comparing the identification information received from the vehicle identification module 114 with past identification information stored in the past records 317 of the memory 316. Thus, the server verification module 310 augments the location information received from the vehicle location database 160 by supplementing the identification information captured by the vehicle sensor 116. In such an example, the server verification module 310 determines whether the identification information of one or more vehicles in the vehicle location database 160 matches the identification information captured by the vehicle sensor 116. In some examples, if the server verification module 310 determines that there is a match, the server verification module 310 determines whether the GPS location and timestamp corresponding to the identification information obtained by the vehicle sensors 116 matches the GPS location and timestamp corresponding to the identification information received from the vehicle location database 160. In some examples, after the location information is verified by the server verification module 310, the identification information received from the vehicle identification module 114 is sent to the recipient determination module 320.

[0038] In some embodiments, the server verification module 310 augments the location information of the vehicle 120 by comparing the identification information received from the vehicle identification module 114 with the identification information received from one or more vehicles (e.g., vehicles 130, 140). Thus, the server verification module 310 augments the location information received from the vehicle 110 by supplementing the location information received from the vehicles 130 and 140. In such an example, the server verification module 310 determines whether the identification information received from the vehicle 110 matches the identification information received from one or both of the vehicles 130 and 140. In some examples, if the server verification module 310 determines that there is a match, the server verification module 310 determines whether the GPS location and timestamp corresponding to the identification information received from the vehicle 110 matches the GPS location and timestamp corresponding to the identification information received from one or both of the vehicles 130 and 140. In some examples, after the location information is verified by the server verification module 310, the identification information received from the vehicle identification module 114 is transmitted to the recipient determination module 320.

[0039] During or after identifying the target vehicle associated with the first data set in step 560, a target information recipient of the multiple targeted information recipients is identified. In some embodiments, the target information recipient is identified by the recipient determination module 320. In some embodiments, the identification information includes target vehicle status information, which may be, for example, a message including a notification about the target vehicle (e.g., vehicle 120). As described above, in some examples, the target vehicle status information includes information about the status of the vehicle (e.g., broken down, on fire, stranded, etc.), information about the driving ability of the driver of the target vehicle (e.g., erratic driving, dangerous driving, careful driving, safe driving, etc.), or any other similar information about the target vehicle. In some embodiments, the processor 324 of the recipient determination module 320 analyzes the target vehicle status information received by the vehicle identification module 114 of the vehicle 110 to determine what messages the driver and / or passenger of the vehicle 110 have included about the vehicle 120. In some non-limiting examples, as described above, the message may include a notification that the vehicle 120 is broken down on the side of the road, a notification that the tail lights of the vehicle 120 are out, a notification that the driver of the vehicle 120 is driving well, a notification that the driver of the vehicle 120 is driving recklessly, or any other similar notification. In some examples, the processor 324 of the recipient determination module 320 analyzes the target vehicle condition information and uses a rule-based algorithm to determine which one or more targeted information recipients 170 (see FIG. 1 ) should receive the target vehicle condition information. Thus, in some examples, the processor 324 determines / identifies the targeted information recipients 170.

[0040] In some embodiments, the processor 324 uses a language-based interpretation algorithm to determine the content of the message. In another embodiment, the language-based interpretation algorithm may be included in the user input processing module 117 of the vehicle identification module 114. In such an embodiment, the vehicle identification module 114 may send the processed message to the server 150. In other embodiments, both the processor 324 and the user input processing module 117 may each use a language-based interpretation algorithm to determine the content of the message. In further embodiments, the processor 324 may use a combination of rule-based algorithms and language-based interpretation algorithms to determine the content of the message.

[0041] During or after analysis of the first data set at step 570, a notification signal is transmitted to the targeted information recipient. In some embodiments, the notification signal is transmitted by the transmitter 328 of the recipient determination module 320. In some embodiments, based on the content of the targeted vehicle condition information, the processor 324 transmits the notification signal to at least one recipient in the recipient database 326. In various examples, the notification signal may include content of the targeted vehicle condition information received from the vehicle identification module 114. In other examples, the notification signal may include, for example, simply the location of the vehicle 120 and a notification instructing the recipient to go to the location of the vehicle 120.

[0042] In one non-limiting example, the target vehicle status information received from the vehicle identification module 114 includes a statement from the driver of the vehicle 110 that the vehicle 120 is on fire on the side of the road. In this example, the processor 324 of the recipient determination module 320 may determine that a notification signal should be sent to an ambulance (e.g., ambulance 326a), a fire engine (e.g., fire engine 326b), a police car (e.g., police car 326c), a hospital (e.g., hospital 326f), and an emergency contact (e.g., emergency contact 326g) of the driver of the vehicle 120.

[0043] In another non-limiting example, the target vehicle status information received from the vehicle identification module 114 includes a statement from the driver of the vehicle 110 that the driver of the vehicle 120 is driving proficiently and safely. In an example where the vehicle 120 is a fleet vehicle, the processor 324 of the recipient determination module 320 may determine that a notification signal should be sent to a fleet management facility (e.g., fleet management facility 326d).

[0044] FIG. 6 illustrates a schematic diagram of an apparatus according to one or more embodiments of the present disclosure. In FIG. 6, the apparatus is generally referred to by reference number 600 and includes components of the vehicle 110 and components of the apparatus 200, which are given the same reference numbers. That is, the apparatus 600 includes everything shown in FIG. 2, plus some additional components. In the embodiment illustrated in FIG. 6, in addition to the apparatus 600 having certain components of the apparatus 200, the vehicle 110 of the apparatus 600 includes a vehicle validation module 610 and a recipient determination module 620. In the embodiment illustrated in FIG. 6, the vehicle validation module 610 includes a receiver 612, a transmitter 614, a memory 616, and a processor 618. In some embodiments, the transmitter 614 and the receiver 612 are integrated into a transceiver capable of both transmitting and receiving wireless signals. The receiver 612 is operably coupled to and configured to communicate with one or more of the HMI 112, the sensor processing module 115, the user input processing module 117, the transmitter 119, the transmitter 614, and the vehicle location database 160. In the embodiment shown in FIG. 6, the recipient determination module 620 includes a receiver 622, a processor 624, a recipient database 626, and a transmitter 628. In some embodiments, the transmitter 628 and the receiver 622 are integrated into a transceiver capable of both transmitting and receiving wireless signals. The receiver 622 is operably coupled to and configured to communicate with one or more of the HMI 112, the transmitter 119, the transmitter 614, and the transmitter 628.

[0045] In some embodiments, the memory 616 is operably coupled to the receiver 612 and configured to communicate with the receiver 612. In some embodiments, the receiver 612 is configured to receive one or more data transmissions from the transmitter 119 of the vehicle identification module 114. In some other embodiments, the receiver 612 is configured to receive data transmissions from the vehicle location database 160 in addition to or instead of the data transmissions received from the transmitter 119, which will be discussed in more detail below. The receiver 612 is configured to output each of the one or more data transmissions to the memory 616, which stores each of the one or more data transmissions for a set period of time before discarding them. In some embodiments, the data transmissions are stored in a history record 617. In some examples, the set period of time for which the memory 616 stores the data transmissions includes 1 minute, 2 minutes, 5 minutes, 10 minutes, or any other suitable period of time that may be less than 1 minute or more than 10 minutes. The history record may be short, and in some embodiments, may be about 30 minutes or less. Therefore, in some embodiments, the memory 616 maintains a historical record 617 of all data transmissions received by the receiver 612 from the transmitter 119. In some embodiments, the historical data stored in the historical record 617 of the memory 616 is used by the processor 618 to validate data processed by the sensor processing module 115 and / or the user input processing module 117, as will be discussed in more detail below.

[0046] In some embodiments, the processor 624 is operably coupled to and configured to communicate with the receiver 622, the recipient database 626, and the transmitter 628. In some embodiments, the processor 624 is configured to read and analyze one or more data transmissions received from the receiver 622. The processor 624 is further configured to analyze the recipient database 626 to determine, for each received data transmission, which one or more recipients in the recipient database 626 should receive the data transmission, which may be, for example, a notification signal. This process is described in more detail below. After the processor 624 determines the appropriate recipients to receive the data transmission, the transmitter 628 transmits the data transmission to the appropriate recipients.

[0047] 5, in some alternative embodiments, after the sensor processing module 115 processes each received image, the vehicle identification module 114 transmits each processed image, as well as corresponding GPS location information and timestamps for each processed image, to the vehicle verification module 610. The processed images and corresponding GPS location information and timestamps may be stored in an historical record 617 in the memory 616 of the vehicle verification module 610. Thus, in some embodiments, the memory 616 maintains a historical record 617 of all data transmissions received from the vehicle identification module 114. In some examples, the data transmissions include the processed images, as well as corresponding GPS location information and timestamps for each processed image.

[0048] 5, in some alternative embodiments, the initiation communication is received by the vehicle validation module 610. In some embodiments, the initiation communication is received by the receiver 612 of the vehicle validation module 610.

[0049] As discussed above with respect to step 540 of FIG. 5, in some alternative embodiments, before, during, or after receiving the initiation communication at step 540, vehicle verification module 610 queries vehicle location database 160. In some embodiments, vehicle location database 160 includes an identification of at least one vehicle, such as vehicle 120, which may be a target vehicle and / or a potential target vehicle. In some embodiments, vehicle location database 160 includes an identification of a plurality of potential target vehicles, which may include each vehicle connected to server 150. Each of the potential target vehicles may also transmit a GPS location corresponding to each of the potential target vehicles to vehicle location database 160. In some embodiments, each of the potential target vehicles, such as vehicle 120, transmits a GPS location to vehicle location database 160 every 30 seconds, every minute, every two minutes, every five minutes, or any other suitable time interval, which may be sooner than every 30 seconds or longer than every five minutes. Therefore, in some embodiments, the vehicle location database 160 includes the current location, or approximate current location, of each of the potential target vehicles within the tagging system 100 (see FIG. 1).

[0050] In some embodiments, as described above, tagging system 100 may include more than one vehicle location database 160. For example, tagging system 100 may include one vehicle location database 160 corresponding to one or more providers (e.g., an internet service provider, a wireless communication system provider, etc.). In such embodiments, vehicle validation module 610 may query each vehicle location database 160.

[0051] In some embodiments, the identification information is received by receiver 612 of vehicle verification module 610. In some examples, processor 618 of vehicle verification module 610 receives the identification information for each vehicle in vehicle location database 160. Processor 618 parses the identification information received from vehicle location database 160. Further, processor 618 compares the parsed identification information to identification information received from vehicle identification module 114 of vehicle 110 (e.g., received identification information in the first data set).

[0052] In some embodiments, the vehicle verification module 610 reduces the amount of identification information to parse before parsing the identification information received from the vehicle location database 160. In such an embodiment, the processor 618 of the vehicle verification module 610 queries the vehicle location database 160 to determine which vehicles were near the vehicle 110 at the time indicated by the timestamp of the initiating communication received by the vehicle identification module 114. The processor 618 uses the GPS location of the vehicle 110 in the initiating communication to make a query to the vehicle location database 160. In some embodiments, the query returns a subset of the identification information that is a subset of the total amount of identification information present in the vehicle location database 160. The processor 618 may parse the subset of the identification information and may compare the parsed identification information to the identification information received from the vehicle identification module 114 of the vehicle 110 (e.g., the identification information received in the first data set).

[0053] 5, in some alternative embodiments, a target vehicle (e.g., vehicle 120) of the plurality of potential target vehicles is identified by vehicle verification module 610 during or after querying vehicle location database 160 in step 550, and the target vehicle is associated with a first data set. In some embodiments, vehicle verification module 610 determines which identification information of the vehicle in vehicle location database 160 matches the identification information received from vehicle identification module 114 of vehicle 110. In some embodiments, if there is a match, vehicle verification module 610 stops parsing the identification information in vehicle location database 160. In various examples, vehicle verification module 610 determines the location of vehicle 120 based on the identification information associated with vehicle 120, including, for example, GPS location data for vehicle 120.

[0054] In some embodiments, after the vehicle verification module 610 determines that there is a match, the vehicle verification module 610 augments the location information of the vehicle 120. This allows the vehicle verification module 610 to verify the location of the vehicle 120, which helps the vehicle verification module 610 reduce the occurrence of false reports by the driver and / or passengers of the vehicle 110 (e.g., helps reduce the occurrence of false initiation communications, false first data sets, false notification signals, etc.). In some embodiments, the vehicle verification module 610 augments the location information of the vehicle 120 by comparing the identification information received from the vehicle identification module 114 to past identification information stored in the past records 617 of the memory 616. Thus, the vehicle verification module 610 augments the location information received from the vehicle location database 160 by supplementing the identification information captured by the vehicle sensor 116. In such an example, the vehicle verification module 610 determines whether the identification information of one or more vehicles in the vehicle location database 160 matches the identification information captured by the vehicle sensor 116. In some examples, if the vehicle verification module 610 determines that there is a match, the vehicle verification module 610 determines whether the GPS location and timestamp corresponding to the identification information captured by the vehicle sensor 116 matches the GPS location and timestamp corresponding to the identification information received from the vehicle location database 160. In some examples, after the location information is verified by the vehicle verification module 610, the identification information received from the vehicle identification module 114 is sent to the recipient determination module 620.

[0055] In some embodiments, the vehicle verification module 610 augments the location information of the vehicle 120 by comparing the identification information received from the vehicle identification module 114 with the identification information received from one or more vehicles (e.g., vehicles 130, 140). Thus, the vehicle verification module 610 augments the location information received from the vehicle 110 by supplementing the location information received from the vehicles 130 and 140. In such an example, the vehicle verification module 610 determines whether the identification information received from the vehicle 110 matches the identification information received from one or both of the vehicles 130 and 140. In some examples, if the vehicle verification module 610 determines that there is a match, the vehicle verification module 610 determines whether the GPS location and timestamp corresponding to the identification information received from the vehicle 110 matches the GPS location and timestamp corresponding to the identification information received from one or both of the vehicles 130 and 140. In some examples, after the location information is verified by the vehicle verification module 610, the identification information received from the vehicle identification module 114 is transmitted to the recipient determination module 620.

[0056] As described above with respect to step 560 of FIG. 5, in some alternative embodiments, a target information recipient of the multiple targeted information recipients is identified during or after identifying the target vehicle associated with the first data set in step 560. In some embodiments, the target information recipient is identified by the recipient determination module 620. In some embodiments, the identification information includes target vehicle status information, which may be, for example, a message including a notification about the target vehicle (e.g., vehicle 120). As described above, in some examples, the target vehicle status information includes information about the status of the vehicle (e.g., broken down, burned, stranded, etc.), information about the driving ability of the driver of the target vehicle (e.g., erratic driving, dangerous driving, polite driving, safe driving, etc.), or any other similar information about the target vehicle. In some embodiments, the processor 624 of the recipient determination module 620 analyzes the target vehicle status information received by the vehicle identification module 114 of the vehicle 110 to determine what messages the driver and / or passenger of the vehicle 110 have included about the vehicle 120. In some non-limiting examples, as described above, the message may include a notification that the vehicle 120 is broken down on the side of the road, a notification that the tail lights of the vehicle 120 are out, a notification that the driver of the vehicle 120 is driving well, a notification that the driver of the vehicle 120 is driving recklessly, or any other similar notification. In some examples, the processor 624 of the recipient determination module 620 analyzes the target vehicle condition information and uses a rule-based algorithm to determine which one or more targeted information recipients 170 (see FIG. 1 ) should receive the target vehicle condition information. Thus, in some examples, the processor 624 determines / identifies the targeted information recipients 170.

[0057] In some embodiments, the processor 624 uses a language-based interpretation algorithm to determine the content of the message. In another embodiment, the language-based interpretation algorithm may be included in the user input processing module 117 of the vehicle identification module 114. In such an embodiment, the vehicle identification module 114 may send the processed message to the server 150. In other embodiments, both the processor 624 and the user input processing module 117 may each use a language-based interpretation algorithm to determine the content of the message. In further embodiments, the processor 624 may use a combination of rule-based algorithms and language-based interpretation algorithms to determine the content of the message.

[0058] 5, in some alternative embodiments, a notification signal is transmitted to the targeted information recipient during or after the first data set analysis at step 570. In some embodiments, the notification signal is transmitted by a transmitter 628 of the recipient determination module 620. In some embodiments, the processor 624 transmits the notification signal to at least one recipient in the recipient database 626 based on the content of the targeted vehicle state information. In various examples, the notification signal may include the content of the targeted vehicle state information received from the vehicle identification module 114. In other examples, the notification signal may include, for example, simply the location of the vehicle 120 and a notification instructing the recipient to go to the location of the vehicle 120.

[0059] In one non-limiting example, the target vehicle status information received from the vehicle identification module 114 includes a statement from the driver of the vehicle 110 that the vehicle 120 is on fire on the side of the road. In this example, the processor 624 of the recipient determination module 620 may determine that a notification signal should be sent to an ambulance (e.g., ambulance 326a), a fire engine (e.g., fire engine 326b), a police car (e.g., police car 326c), a hospital (e.g., hospital 326f), and an emergency contact (e.g., emergency contact 326g) of the driver of the vehicle 120.

[0060] In another non-limiting example, the target vehicle status information received from the vehicle identification module 114 includes a statement from the driver of the vehicle 110 that the driver of the vehicle 120 is driving proficiently and safely. In an example where the vehicle 120 is a fleet vehicle, the processor 624 of the recipient determination module 620 may determine that a notification signal should be sent to a fleet management facility (e.g., fleet management facility 326d).

[0061] In some embodiments, a computer system typically comprises at least hardware capable of executing machine-readable instructions and software that performs actions (typically machine-readable instructions) to produce a desired result, in some embodiments a computer system may include a mixture of hardware and software and computer subsystems.

[0062] In some embodiments, the hardware generally includes at least a processor-enabled platform, such as a client machine (also known as a personal computer or server), and a handheld processing device (e.g., a smart phone, tablet computer, personal digital assistant (PDA), or personal computing device (PCD)). In some embodiments, the hardware may include any physical device, such as memory or other data storage device, capable of storing machine-readable instructions. In some embodiments, other hardware forms include hardware subsystems, including transmission devices, such as modems, modem cards, ports, port cards, and the like.

[0063] In some embodiments, software includes any machine code stored on any memory medium, such as RAM, ROM, and other devices (e.g., floppy disk, flash memory, or CD-ROM). In some embodiments, software may include source code or object code. In some embodiments, software encompasses any set of instructions executable on a node, such as a client machine or a server.

[0064] In some embodiments, a combination of software and hardware may be used to provide enhanced functionality and performance to certain embodiments of the present disclosure. In one embodiment, software functionality may be embedded directly into a silicon chip. It should be understood, therefore, that combinations of hardware and software are also included within the scope of the definition of a computer system and are contemplated by this disclosure as possible equivalent structures and equivalent methods.

[0065] In some embodiments, the computer readable medium includes, for example, passive data storage devices such as random access memory (RAM) and semi-permanent data storage devices such as compact disk read only memory (CD-ROM). One or more embodiments of the present disclosure can be embodied in a computer's RAM to turn a standard computer into a new specialized computing device. In some embodiments, a data structure is a defined data organization that can enable an embodiment of the present disclosure. In one embodiment, a data structure can be an organization of data or an organization of executable code.

[0066] In some embodiments, any network, and / or one or more portions thereof, may be designed to function with any particular architecture. In one embodiment, one or more portions of any network may run on a single computer, a local area network, a client-server network, a wide area network, the Internet, and handheld and other portable wireless devices and networks.

[0067] In some embodiments, the database may be any standard or proprietary database software, such as Oracle®, Microsoft Access®, SyBase®, or DBase II. In some embodiments, the database may have fields, records, data, and other database elements that may be related via database specific software. In some embodiments, the data may be mapped. In some embodiments, mapping is the process of relating one data entry to another data entry. In one embodiment, data contained in a character file location may be mapped to a field in a second table. In some embodiments, the physical location of the database is not limited and the database may be distributed. In one embodiment, the database may be remote from the server and may be running on another platform. In one embodiment, the database may be accessible via the Internet. In some embodiments, more than one database may be implemented.

[0068] In some embodiments, instructions stored on a computer readable medium may be executed by one or more processors to cause the one or more processors to perform or implement all or a portion of the above-described operations of each of the above systems, methods, and / or any combination of the above systems and methods. In some embodiments, such processors may include any one or more processors that are part of the components of the above systems and / or any combination of the above systems, and such computer readable medium may be distributed among one or more components of the above systems. In some embodiments, such processors may execute instructions in connection with a virtual computer system. In some embodiments, such instructions may communicate directly with the one or more processors and / or may interact with one or more operating systems, middleware, firmware, other applications, and / or any combination thereof to cause the one or more processors to execute the instructions.

[0069] It is understood that changes can be made in the foregoing without departing from the scope of the present disclosure.

[0070] In some embodiments, elements and teachings of various embodiments may be combined in whole or in part in some or all of the embodiments. Additionally, one or more of the elements and teachings of various embodiments may be at least partially omitted and / or at least partially combined with one or more of the other elements and teachings of the various embodiments.

[0071] Any spatial references, such as "upper," "lower," "above," "below," "between," "bottom," "vertical," "horizontal," "angular," "upwards," "downwards," "side-to-side," "left-to-right," "right-to-left," "top-to-bottom," "bottom-to-top," "top," "bottom," "bottom-up," "top-down," etc., are for illustrative purposes only and do not limit the particular orientation or location of the structures described above.

[0072] In some embodiments, different steps, processes, and procedures are described as appearing distinct acts, but one or more of the steps, one or more of the processes, and / or one or more of the procedures may be performed in a different order, simultaneously, and / or sequentially. In some embodiments, the steps, processes, and / or procedures may be combined into one or more steps, processes, and / or procedures.

[0073] In some embodiments, one or more of the operational steps of each embodiment may be omitted. Furthermore, in some cases, some of the features of the present disclosure may be used without the corresponding use of other features. Furthermore, one or more of the above-described embodiments and / or variations may be combined in whole or in part with one or more of the other embodiments and / or variations described above.

[0074] Although certain embodiments have been described above in detail, the described embodiments are merely illustrative and not limiting, and those skilled in the art will appreciate that many other improvements, modifications, and / or substitutions are possible in the embodiments without substantially departing from the novel teachings and advantages of the present disclosure. Accordingly, all such improvements, modifications, and / or substitutions are intended to be included within the scope of the present disclosure as defined by the following claims. In the claims, any means-plus-function clause is intended to include structures described herein that perform the recited function, and is intended to include equivalent structures as well as structural equivalents. Moreover, it is the express intent of the Borrower not to invoke the sixth paragraph of 35 U.S.C. 112 against any limitation in any of the claims herein, except for limitations to claims that explicitly use the word "means" with the relevant function.

Claims

1. 1. A system for tagging a vehicle, comprising: a vehicle comprising: a vehicle identification module comprising a user input processing module configured to receive an initiation communication including a dataset including target vehicle identification data and target vehicle status information, the target vehicle status information including at least an operational defect of the target vehicle; a vehicle location database including identities of a plurality of potential target vehicles; A server, receiving the data set from a transmitter of the vehicle identification module; querying the vehicle location database for the identities of the plurality of potential target vehicles; identifying the target vehicle from the plurality of potential target vehicles in the vehicle location database based on the target vehicle identification data; a server validation module configured as follows: Analyzing the target vehicle condition information to determine at least one target information recipient; transmitting a notification signal to the at least one targeted information recipient; A recipient determination module configured to: A server comprising: A system comprising:

2. The identification information of the plurality of potential target vehicles in the vehicle location database, a location of at least one of the plurality of potential target vehicles; a timestamp indicating a time when the identification information of at least one potential target vehicle of the plurality of potential target vehicles was received by the vehicle location database; The system of claim 1 , comprising:

3. 2. The system of claim 1, wherein the target vehicle identification data includes at least one of a color of the target vehicle, a manufacturer of the target vehicle, a model of the target vehicle, a type of the target vehicle, a license plate number of the target vehicle, a bumper sticker of the target vehicle, or a decal of the target vehicle.

4. The vehicle is a vehicle sensor including at least one camera disposed on the vehicle, the at least one camera being configured to capture at least one image of an external environment surrounding the vehicle; The system of claim 1 further comprising:

5. The vehicle identification module includes: a sensor processing module comprising an image processor configured to analyze the at least one image of the external environment; The system of claim 4 further comprising:

6. The server verification module: a memory configured to store past identification information including identification information of the target vehicle photographed by a vehicle sensor; The system of claim 1 further comprising:

7. a second vehicle configured to transmit its identification to the vehicle location database for storage as an identification of at least one potential target vehicle; Further equipped with the plurality of potential target vehicles includes the second vehicle. The system of claim 1 .

8. The system of claim 7 , wherein the identification information of the second vehicle includes a location of the target vehicle.

9. The server verification module further comprises: validating the dataset by comparing the target vehicle identification data of the dataset with the identification information of the plurality of potential target vehicles received from the vehicle location database to determine whether there is a match between the target vehicle identification data received in the dataset and the second vehicle. The system of claim 8 , configured to:

10. the server verification module further comprising a memory configured to store past identification information; and validating the data set includes parsing the historical identification information to confirm the match between the received target vehicle identification data in the data set and the second vehicle. The system of claim 9.

11. 1. A system for tagging a vehicle, comprising: a vehicle comprising a user input processing module configured to receive an initiation communication including a first data set including target vehicle identification data and target vehicle status information, the target vehicle status information including at least an operational defect of the target vehicle; a vehicle location database including identities of a plurality of potential target vehicles; A server, receiving the identification information for the plurality of potential target vehicles in the vehicle location database; identifying a target vehicle associated with the first data set among the plurality of potential target vehicles; verifying the first data set by comparing the received target vehicle identification data in the first data set with identification information of the target vehicle received from the vehicle location database; a server validation module configured as follows: Analyzing the first data set to determine at least one targeted information recipient; transmitting a notification signal to the at least one targeted information recipient; A recipient determination module configured to: A server comprising: A system comprising:

12. A second vehicle, a second user input processing module configured to receive a second initiation communication including a second data set including an identification of the target vehicle; A second vehicle comprising: The system of claim 11 further comprising:

13. The server verification module further comprises: verifying the first data set by comparing the identification information of the target vehicle received in the first data set with the identification information of the target vehicle received in the second data set to determine if there is a match; The system of claim 12 configured to:

14. The identification information of the plurality of potential target vehicles in the vehicle location database, a location of at least one of the plurality of potential target vehicles; a timestamp indicating a time when the identification information of at least one of the plurality of potential target vehicles was received by the vehicle location database; The system of claim 11 , comprising:

15. 12. The system of claim 11, wherein the target vehicle identification data includes at least one of the following: a color of the target vehicle, a manufacturer of the target vehicle, a model of the target vehicle, a type of the target vehicle, a license plate number of the target vehicle, a bumper sticker of the target vehicle, or a decal of the target vehicle.

16. The vehicle is a vehicle sensor comprising at least one camera configured to take at least one image of an external environment surrounding the vehicle; Further equipped with The server verification module: a memory configured to store past identification information including identification information of the target vehicle photographed by the vehicle sensor; The system of claim 11 further comprising:

17. 1. A method for tagging a vehicle, comprising: receiving, at a user interface of the vehicle, an initiation communication including a first data set including both target vehicle identification data and target vehicle status information including at least operational defects of the target vehicle; sending the first data set to a server validation module of a server; conducting a query by said server verification module to a vehicle location database containing identities of a plurality of potential target vehicles; identifying, by the server verification module, a target vehicle associated with the first data set among the plurality of potential target vehicles; determining at least one target information recipient among a plurality of target information recipients based on the first data set, the at least one target information recipient being a recipient to which information based on the target vehicle state information is to be transmitted; sending a notification signal to the at least one targeted information recipient by a recipient determination module; A method comprising:

18. The identification information for the plurality of potential target vehicles includes: a location of at least one of the plurality of potential target vehicles; a timestamp indicating a time when the identification information of at least one of the plurality of potential target vehicles was received by the vehicle location database; 20. The method of claim 17, comprising:

19. capturing at least one image of an external environment surrounding the vehicle by a vehicle sensor of the vehicle; storing, by a memory of the server verification module, past identification information including identification information of the target vehicle captured by a vehicle sensor; 20. The method of claim 17, further comprising:

20. verifying, by the server verification module, the first data set by comparing the received identification information of the target vehicle in the first data set with the identification information of the target vehicle received from the vehicle location database to determine whether there is a match; Further comprising: Validating the first data set includes: parsing the past identification information to confirm the match between the identification information of the target vehicle received in the first data set and the identification information of the target vehicle received from the vehicle location database; 20. The method of claim 19, comprising:

Images