In-vehicle GPS geo-fencing route planning, GPS proximity based advertising, infotainment system advertising and infotainment system picture or video emergency alert display

Static OEM hard-wired in-vehicle infotainment system method to capture and transmit vehicle route data for a defined geo-fenced area. Collects and transmits vehicle data to cloud server and maps geo-fenced area using GPS coordinates to produce report and vehicle route onto infotainment screen. Collective summery report and graphical display for all vehicles within a defined GPS Geo-Fenced area can also be displayed. Additional methodology includes GPS Proximity Based Advertising and Infotainment System Advertising. GPS Proximity Based Advertising defines radius around a GPS location, displaying advertisement when vehicle enters the radius. Infotainment System Advertising receives advertisement via software or firmware, onto the OEM hard-wired in-vehicle infotainment system memory. Additional methodology includes receiving and displaying emergency alert emanating from integrated public alert and warning system compliant common alert protocol alert origination tool onto static OEM hard-wired in-vehicle infotainment system, GUI to display an image, picture, video or hologram.

BACKGROUND

As vehicle Original Equipment Manufacturers (OEM) adopt hard-wired in-vehicle infotainment systems, the ability to more accurately collect, receive and transmit data becomes possible. One significant advantage of the collection, receipt and transmittal of data from the OEM equipment, including the OEM hard-wired in-vehicle infotainment system, is the ability to monitor vehicle speed, vehicle gear selection, including Park, Drive and Reverse, vehicle engine ON or OFF, vehicle GPS location and map of a defined grid using GPS latitude and longitude coordinates in decimal degrees or degrees minute seconds. Along with the increased possibilities for the collection and transmittal of more accurate data, comes the ability to transmit advertisements, both with and without using GPS location, onto the OEM hard-wired in-vehicle infotainment system. In addition to the advertising, the increased possibility to display an image, picture, video or hologram from an Integrated Public Alert and Warning System (IPAWS) directly onto the hard-wired in-vehicle infotainment system becomes possible.

Firmware or software specifically developed for an OEM hard-wired in-vehicle infotainment systems has not been developed and integrated into a vehicle, for the purposes of collecting vehicle traffic patterns for a defined GPS area, using OEM supplied in-vehicle modules like the body control module (BCM), powertrain control module (PCM) or transmission control module (TCM). Data to be transmitted from the vehicle over any combination of communication networks, including, but not limited to Local Interconnect Network (LIN), Local Area Network (LAN), High Speed CAN (HSCAN), Low Speed CAN (LSCAN), InfotainmentCAN (InfoCAN) or any other CAN bus network will include the time taken for a vehicle to enter or exit the defined GPS area, actual vehicle speed as the vehicle enters and remains in the defined GPS area, direction analytics for vehicle route measured by GPS latitude and longitude coordinates in decimal degrees or degrees minute seconds, duration vehicle remains in the defined GPS area, vehicle gear selection including Park, Drive and Reverse, vehicle engine ON or OFF.

Existing in-vehicle traffic monitoring systems use a vehicle's infotainment system wirelessly paired, via blue-tooth, to a peripheral device like a cellular phone. Crowdsourcing applications on the blue-tooth phone use cell tower triangulation to determine vehicle speed. Other traffic monitoring systems require both a control module to record vehicle speed and vector positioning, as well as a transmitter to send the data that is coupled to the vehicles GPS. In addition to the control module and transmitter, an external traffic monitoring system is required to be placed near the roadway.

This disclosure also relates to a method utilized for In-vehicle GPS Geo-Fencing Route Planning, used to monitor traffic flow within a defined GPS geo-fenced area, using a vehicles actual speed, as reported on the vehicle instrument control panel. OEM equipped communication networks and OEM hard-wired modules in conjunction with the GPS Coordinate Geo-Fencing Planning software provide a more accurate representation of speed, while not relying exclusively on continual cellular data transmissions or external transmissions.

Vehicles equipped with an OEM hard-wired in-vehicle infotainment system with GPS Geo-Fencing Route Planning can display actual and projected vehicle routes, within a defined geo-fenced area. Crowdsourcing vehicle data from vehicles equipped with In-vehicle GPS Geo-Fencing Route Planning firmware or software enables route projections. Route projections within a defined GPS geo-fenced area can be used to project routes based on historical or real-time data such as least congested parking areas or shortest walk into a destination.

This disclosure also relates to the data collection and transmittal method from the In-vehicle GPS Geo-Fencing Route Planning System. Data will be stored or sent via OEM equipped hardware and existing OEM equipped communication networks including over any combination of communication networks, including, but not limited to LIN, LAN, HSCAN, LSCAN, InfoCAN or any other CAN bus network. The OEM hard-wired in-vehicle infotainment system will be used to in-conjunction with other vehicle modules to collect and transmit vehicle data such as vehicle speed, vehicle camera(s), vehicle object detection sensors, vehicle cardinal directions (North, South, East and West) or time duration of vehicle idling. More accurate depiction of vehicle traffic patterns for a defined GPS area are possible using the In-vehicle Traffic and In-vehicle GPS Geo-Fencing Route Planning Software. Additions such as time taken for a vehicle to enter or exit the defined GPS area, visual inspection of road surface conditions including pot-holes, visual of obstacle obstructions, speed of the vehicle within the defined GPS area, route of the vehicle in the defined GPS area and duration a vehicle once it enters the defined GPS area is now possible.

This disclosure also relates to GPS Proximity Based Advertising. GPS Proximity Based Advertising recognizes a vehicles GPS coordinates relative to a defined GPS coordinate grid and as a result will produce virtual advertising onto an OEM hard-wired in-vehicle infotainment system. When a vehicle nears or enters the defined GPS coordinate grid, a localized advertisement will appear on the Graphic User Interface (GUI) of the OEM hard-wired in-vehicle infotainment system. Advertisements can include any and all displays, including, but not limited to pin-points on navigation maps that display local attractions including parks, restaurants, grocery stores, hospitals, schools, etc. Navigation based advertisements will include interactive one-touch directions, restaurant menus, audio, video or text displays.

This disclosure also relates to non-GPS Proximity Based Advertising or an Infotainment System Advertising method able to transmit and receive audio or video advertisements directly onto the OEM equipped hardware, while using OEM communication networks, to an OEM in-vehicle infotainment system or GPS screen. Using the OEM communication networks, including, but not limited to LIN, LAN, HSCAN, LSCAN, InfoCAN or any other CAN bus network, advertisements will be sent from a cloud-based server to the vehicles Satellite, GPS, Cellular, PCS or Wi-Fi antenna, where the advertisement will be processed either by a gateway module (GWM) or directly onto the OEM hard-wired in-vehicle infotainment system for display. The Infotainment System Advertising method introduces the ability to display advertised content received from the OEM equipped Satellite, GPS, Cellular, PCS or Wi-Fi antenna, translated through the GWM, if equipped, and displayed onto the OEM hard-wired in-vehicle infotainment system.

This disclosure also relates to firmware or software included on the OEM hard-wired in-vehicle infotainment system capable of displaying an IPAWS visual alert, image, picture, video or hologram, originating from an IPAWS compliant CAP Alert Origination Tool, transmitted via an Alert Disseminator. According to the National Center for Missing and Exploited Children's 2015 Annual AMBER Alert Report, the most common reason for an AMBER Alert success story is an individual or law enforcement recognizing the vehicle from the alert at 42 percent (n=21) followed by the abductor hearing the alert and releasing the child at 20 percent (n=10). By providing a visual alert, image, picture, video or 2D and 3D hologram of the suspect, victim, vehicle, license plate, etc., directly onto an OEM hard-wired in-vehicle infotainment system will increase the percentage of victims found alive and reduce the time in finding them. Both law enforcement and private citizens will cognitively recognize the vehicle, suspect or missing person from the OEM hard-wired in-vehicle infotainment system GUI, which will prevent abductors from traveling greater distances and aid in a safe recovery.

Existing OEM hard-wired in-vehicle infotainment systems are currently limited to displaying only emergency broadcast text messages originating from radio transmissions. The Infotainment System Picture or Video Emergency Alert Display introduces a system to display a visual alert in the form of an image, picture, video or hologram onto an OEM hard-wired in-vehicle infotainment system. The Infotainment System Picture or Video Emergency Alert Display is activated when an Alerting Authority transmits an IPAWS visual alert or image, picture, video or hologram onto an OEM hard-wired in-vehicle infotainment system from a CAP Origination Tool and transmitted via an Alert Disseminator. An Alert Disseminator then transmits the visual alert multimedia file extension to the vehicle antenna(s), where the visual alert multimedia file is transmitted, via a hard-wired connection to the OEM hard-wired GWM. The GWM then transmits the visual alert multimedia file via a LIN, LAN, HSCAN, LSCAN, InfoCAN or any other CAN bus network to the OEM in-vehicle infotainment system. Firmware and or software included with the Infotainment System Picture or Video Emergency Alert Display will process the visual alert multimedia file for display onto the OEM hard-wired in-vehicle infotainment system.

SUMMARY

The In-vehicle Geo-Fencing Route Planning application will collect actual in-vehicle GPS coordinates using the GPS coordinates as measured from the vehicle's GWM, once the vehicle enters into a pre-defined GPS coordinate area. The movement of the vehicle, defined by the GPS coordinates within the pre-defined area, will be collected and sent at a set time interval via an OEM hard-wired Satellite, GPS, Cellular, PCS or Wi-Fi antenna. Individual GPS coordinate information within the pre-defined area will be transmitted to a cloud-base server. The cloud-based server will collect the GPS data from a multitude of individual vehicles and compress the collective data for mapping and predictive route patterns within the defined GPS area. Information from the compressed file will include a GUI of individual vehicle routes displayed onto a navigation map, as well as hard data including time spent in the defined GPS area, time vehicle spent parked in the defined GPS area, time in Reverse in the defined GPS area and time spent in Drive or other forward moving gear and speed of the vehicle.

This disclosure also relates to GPS Proximity Based Advertising, a method to directly display an interactive web-advertisement, including but not limited to a map of advertised locations, display phone numbers for single touch dialing, display advertised symbols, play audio recordings, play video and audio recordings, display emojis or generate a hyperlink to internet enabled content onto a stationary OEM hard-wired in-vehicle infotainment system. GPS Proximity Based Advertisements display advertised content onto the OEM hard-wired in-vehicle infotainment system by defining a perimeter or geo-fence using firmware or software loaded onto the GWM, OEM hard-wired in-vehicle infotainment system. As the vehicle enters into the defined GPS perimeter, the advertised content will be displayed onto either the navigation map or any other GUI included with the OEM hard-wired in-vehicle infotainment system. The pre-defined GPS perimeter is stored onto the OEM hard-wired GWM, OEM hard-wired in-vehicle infotainment system or stored on a cloud-based server. Advertised content will only initiate once the vehicle GPS coordinates, as received from the OEM equipped Satellite, GPS, Cellular, PCS or Wi-Fi antenna enters into the defined GPS area.

This disclosure also relates to any other method used to directly display an interactive web-advertisement, including, but not limited to a map of advertised locations, phone number display for single touch dialing, advertised symbol display, play audio recordings, play video and audio recordings, display emojis or generate a hyperlink to internet enabled content onto a stationary OEM hard-wired in-vehicle infotainment system. Advertisements for display onto the OEM hard-wired in-vehicle infotainment system will be transmitted out from a cloud server or mobile switching center, to a satellite, GPS, cellular tower, PCS or Wi-Fi transmitter, then out to the vehicle's antenna and processed through the OEM equipped communication network system to the GWM, but also capable of transmitting directly onto the OEM hard-wired in-vehicle infotainment system.

This disclosure also relates to any method used to display an image, picture or video file onto a static OEM hard-wired in-vehicle infotainment system sent from an IPAWS visual alert emanating from a Common Alert Protocol (CAP) Alert Origination Tool via an Alert Disseminator(s). The Infotainment System Picture or Video Emergency Alert Display System runs firmware or software, which is downloaded directly onto the memory of an OEM hard-wired in-vehicle infotainment system, capable of recognizing the IPAWS visual alert multimedia file transmitted from a satellite, Wi-Fi or cellular tower. The Infotainment System Picture or Video Emergency Alert Display application then executes a unique protocol to validate the IPAWS video alert multimedia file. If validated as an IPAWS visual alert, then a second protocol will be run to recognize the video alert multimedia file. If the OEM hard-wired in-vehicle infotainment system recognizes the visual alert multimedia file, a subroutine runs, opening up a compatible multimedia player to start the display of the IPAWS visual alert.

DETAILED DESCRIPTION

Pertaining to systems for Geo-Fencing Route Planning, Infotainment System Advertising and Infotainment System Picture or Video Emergency Alert Display onto an OEM hard-wired in-vehicle infotainment system are now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects. It may be evident, however, that such aspect(s) may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more aspects. Further, it is to be understood that functionality that is described as being carried out by certain system components may be performed by multiple components. Similarly, for instance, a component may be configured to perform functionality that is described as being carried out by multiple components.

As used herein, the term “infotainment system” and “in-vehicle infotainment system” is intended to encompass an OEM hard-wired in-vehicle touchscreen module, vehicle radio coupled to an in-vehicle touchscreen, a vehicle radio coupled to an in-vehicle LCD or LED screen, an audio and video control module coupled to an in-vehicle LCD or LED screen or an in-vehicle holographic display or touch interface. Additionally, as used herein, the term “exemplary” is intended to mean serving as an illustration or example of something, and is not intended to indicate a preference.

With reference toFIG. 1, an exemplary system100that facilitates graphical display of a GPS Geo-Fencing Route Plan onto the GPS navigation interface101of an OEM hard-wired in-vehicle infotainment system, used to display vehicle positioning is illustrated. GPS navigation interface101receives signal102from the OEM hard-wired in-vehicle infotainment system110.

The network120includes firmware122and software124for download onto one or more of the embodiments in the OEM hard-wired in-vehicle infotainment system110. Function of network120will include a method to recognize and store the defined geo-fencing area from the GPS latitude and longitude coordinates in decimal degrees or degrees minute seconds.

The network130, independent of the OEM hard-wired in-vehicle infotainment system110, includes a Powertrain Control Module (PCM)132, Body Control Module (BCM)134and Transmission Control Module (TCM)136. Function of network130will recognize when vehicle engine is On or Off, speed of vehicle and transmission gear (Park, Drive, Neutral, First, Second, etc.). In one embodiment, the PCM132communicates directly to the OEM hard-wired in-vehicle infotainment system110. In another embodiment, the BCM134communicates directly to the OEM hard-wired in-vehicle infotainment system110via signal137. In yet another embodiment TCM136communicates directly to the OEM hard-wired in-vehicle infotainment system110via signal137. In yet another embodiment the PCM132communicates to the BCM134and both or one of the modules communicates back to the OEM hard-wired in-vehicle infotainment system110via signal137. In yet another embodiment the TCM136communicates to the BCM134. In yet another embodiment, both the PCM132, BCM134and TCM136communicate directly to each other. In yet another embodiment the PCM132and TCM136communicate directly to each other.

Signal119received from the OEM hard-wired in-vehicle infotainment system110is processed from the Gateway Module (GWM)140, if equipped. If not equipped, the GWM140is bypassed.

Antenna150includes any embodiment of a singular or plurality of in-vehicle antenna(s) including GPS, Cellular, PCS, WI-FI or Satellite. Antenna150transmits and receives data for any and all embodiments included from the OEM hard-wired in-vehicle infotainment system110and networks120,130and140via signal141if equipped with a GWM140, if not equipped with a GWM140signal119transmits directly from the Antenna150to the OEM hard-wired in-vehicle infotainment system110.

The network160includes an exemplary system that facilitates a method to transmit or receive data into the vehicles antenna(s)150via signal151. The network160includes an array of transmitters including a Satellite162, Wi-Fi164and Cell Tower166. In one embodiment the data from network160will be transmitted or received from a Satellite transmitter162directly onto the vehicle Antenna150via signal151. In another embodiment the data from network160will be transmitted or received from external Wi-Fi transmitter164directly onto the vehicle Antenna150via signal151. In yet another embodiment the data from network160will be transmitted or received from Cell Tower166directly to a vehicle Antenna150via signal151. In yet another embodiment the data from network160will be transmitted or received in conjunction with a plurality of transmitters or receivers including Satellite Antenna162, external Wi-Fi Antenna164and Cell Tower166directly to the vehicle Antenna150via signal151.

Cloud server170is an external remote device responsible for transmitting to and receiving data from network160via signal161. Cloud server170collects data and in one embodiment compresses that data, included from networks100,110,120,130,140,150and160. Data to be available on the server includes, but not limited to, all information relating to capturing vehicle data.

Compressed data file180is a summary of information collected from data available on Networks100,110,120,130,140,150,160and170via signal171. Compressed data file180can be configured to query out any and all data available obtained from networks100,110,120,130,140,150,160and170. Geo-Fencing Route Planning GPS perimeters are uploaded onto the Server170and can be changed over-the-air with vehicle software or firmware re-flashing. When changes occur to GPS perimeters, i.e. perimeters deleted, added or modified, the subsequent changes to the Compressed File180will be made accordingly.

Referring now toFIG. 2, a summary of vehicle event data200as displayed onto the OEM hard-wired in-vehicle infotainment system110as outputted from Compressed File180. Data exported from the server for this embodiment is Time of Day201as recognized on network160, vehicle Gear202as recognized by network130, vehicle Speed203as recognized by network130, vehicle Engine (On/Off)204as recognized by network130, Cardinal Directions205collected in including Latitude206in decimal degrees or degrees minute seconds and Longitude in decimal degrees or degrees minute seconds207as interpreted by the OEM hard-wired in-vehicle infotainment system110as received by the vehicle Antenna150. Altitude208, measured in feet or meters, as recognized by the OEM hard-wired in-vehicle infotainment system110as received by the vehicle Antenna150. Time Duration in Gear209records the time duration a vehicle is in a set gear (Park, Drive, Neutral, First, Second, Third, etc.) as interpreted from network130.

Referring now toFIG. 3, a mockup of an OEM hard-wired in-vehicle infotainment system110GUI display of a GPS Geo-Fenced area with individual route path300is detailed. Area highlighted demonstrates a visual boundary of a geo-fenced area301where data is to be collected for the Geo-Fencing Route Planning System. Geo-fenced area301is defined by latitude decimal degrees or degrees minute seconds and longitude in decimal degrees or degrees minute seconds302. Geo-fenced area is modified and updated by modifying network120by a firmware122or software124update, which is uploaded onto the Cloud Server170, sent to network160including any embodiment of transmitters including Satellite162, Wi-Fi164or Cell Tower166and interpreted by the OEM hard-wired in-vehicle infotainment system110or GWM140. Vehicle route path303is graphically displayed onto a GUI that outlines the path of individual vehicle on route through the defined geo-fenced area301.

Referring now toFIG. 4, a mockup of an OEM hard-wired in-vehicle infotainment system110GUI display of a GPS Geo-Fenced area with current crowdsourced vehicle route mapping400is detailed. Area highlighted demonstrates a visual boundary of a geo-fenced area401where data is to be collected for the Geo-Fencing Route Planning System. In the upper right-hand corner of the in-vehicle infotainment system GUI includes text indicating the current day and date402. Below the day and date402is a text display of the current time403. By means of crowdsourcing individual vehicle data, similarly equipped with the in-vehicle infotainment Geo-Fencing Route Planning System, actual individual vehicle route data can be collectively transmitted back to an individual in-vehicle infotainment system for visual display on a GUI404.

Referring now toFIG. 5, a mockup of an OEM hard-wired in-vehicle infotainment system110GUI display of a GPS Geo-Fenced area with historical crowdsourced data, identifying the parked vehicle occupation spaces500for predictive parking avoidance aid and vehicle route planning is displayed. Area highlighted demonstrates a visual boundary of a geo-fenced area501, where data is to be collected for the Geo-Fencing Route Planning System. In the upper right-hand corner of the in-vehicle infotainment system GUI includes text indicating the current day and date402as transmitted by network160. Below the day and date402is a text display of the current time403as transmitted by network160.

By means of crowdsourcing individual vehicle data, processed and transmitted in the cloud server170, similarly equipped vehicles with the OEM hard-wired in-vehicle infotainment Geo-Fencing Route Planning System can utilize historical data, obtained from OEM modules collected at specific time and date intervals. Historical trends for vehicles identified from OEM modules to be in ‘Park’, is graphically displayed via color coded indicators representing the likely hood the vehicle space will be occupied at the given day and date402and current time403as transmitted by network160. In one embodiment, color coded indicators are displayed by a Green, Yellow and Red overlay502onto the GUI of an individual vehicle's OEM hard-wired in-vehicle infotainment system110.

Referring now toFIG. 6, an exemplary system600that facilitates the transmission of both GPS Proximity Based and non-GPS Proximity Based Infotainment System Advertisements onto the OEM hard-wired in-vehicle infotainment system110GUI of Network601via signal102. Network601, in exemplary example is the GUI for an Over-The-Air (OTA) broadcast signal AM, FM, HD or Radio Data System (RDS)602that is regularly broadcast over airways transmitted via a licensed station's transmitter. Other exemplary examples of a GUI display for Network601include Satellite or XM radio603, a Short Wave or Digital Radio Mondiale (DRM)604, UHF or VHF Radio and Television605and GPS navigation map101. Network610inputs a signal611to the OEM hard-wired in-vehicle infotainment system110from a USB613, a Bluetooth device614, an audio input jack615, or a microphone616. The OEM hard-wired in-vehicle infotainment system110will transmit an advertisement onto the GUI of any of the embodiments included in network601. In one embodiment the OEM hard-wired in-vehicle infotainment system110receives signal119from the GWM140and processes the in-vehicle infotainment system advertisement recognition protocol included in network620including firmware622or software624. Signal141is received in-vehicle from Antenna150and supplied by signal151sent from a network of data transmitters160, including, but not limited to a Satellite162, Wi-Fi164or Cell Tower166. Cloud Server170, which defines the advertisement multimedia file to be transmitted, sends signal161onto network160for routing to the vehicle Antenna150.

Referring now toFIG. 7, a mockup of an OEM hard-wired in-vehicle infotainment system110for a GPS display700is illustrated. The GPS display710is comprised of a GPS icon720in the upper most left-hand portion of the display and a GPS navigation map. In one embodiment to display GPS Proximity Based Advertisements, a non-visible radius730, with radius center positioned on the address location of advertised location is to be recognized based on vehicle position as detailed in the GPS location as received from the Antenna150. In this embodiment advertisements including an icon or logo740, a hyperlink phone number760that when paired to the user's phone, via Bluetooth connection614, user will dial the advertised number with one-touch of the OEM hard-wired in-vehicle infotainment system110GUI. Also, in this embodiment is an advertised hyperlink to web-page770, that if vehicle is connected to internet via network160, the link will pull-up the advertised content when user selects the hyperlink770from the OEM hard-wired in-vehicle infotainment system110. In yet another embodiment of this display, video advertisements780will be appear on the OEM hard-wired in-vehicle infotainment system110GUI. Video advertisements will be stored locally on the memory or streamed live to the OEM hard-wired in-vehicle infotainment system110as processed from the GWM140, if equipped, and as received from the Antenna150from any of the embodiments capable of transmitting a multimedia video file included in network160.

Referring now toFIG. 8, a methodology that facilitates an OEM hard-wired In-Vehicle Infotainment Advertisement Recognition Protocol800. The methodology800begins by an Advertisement Broadcast Continuous Transmission802emanating from the transition from any of the embodiments including Satellite162, Wi-Fi164and Cell Tower166. The methodology then transitions to the OEM hard-wired in-vehicle infotainment system110Recognition Protocol800whereby the Vehicle GPS Coordinates are Recognized804. The methodology then transitions to the OEM hard-wired in-vehicle infotainment system110identifying the Geo-fenced perimeter nearby806. Upon recognizing the geo-fenced perimeter nearby806, the OEM hard-wired in-vehicle infotainment system110goes into a standby routine. Methodology transitions to identifying if the vehicle enters the GPS Geo-Fenced area808. Once the GPS coordinates as reported by the OEM hard-wired in-vehicle infotainment system110have entered the Geo-Fenced area808, the methodology transitions to allowing the Advert Transmission to begin810. The methodology transitions to the Protocol Start: File Format Recognized812, whereby a decision is made based on the processor recognizing the file format being transmitted. Methodology transitions to End Protocol: No Advertisement Displayed814, if the file format is not recognized. If the file format is recognized, the methodology transitions to a subroutine whereby the OEM hard-wired in-vehicle infotainment system110opens up a compatible media player816based on the file extension transmitted. The methodology transitions to the OEM hard-wired in-vehicle infotainment system110start displaying advert818.

Referring now toFIG. 9, a mockup of an OEM hard-wired in-vehicle infotainment system110GUI900is illustrated. In one embodiment an IPAWS visual alert in the form of an image with a released Silver Alert910is displayed. IPAWS visual alert is transmitted to the Antenna150by an alert disseminator which receives the IPAWS visual alert multimedia file from an alert aggregator, which receives the IPAWS visual alert multimedia file from an alerting authority. The IPAWS visual alert multimedia file, in one embodiment, includes descriptive details in the form of an image with picture and text embedded into the image file that includes details such as, but not limited to, missing date, age missing, age now, sex, race, hair, eyes, height, weight, city from, county, narrative details or any other pertinent information included in the Silver Alert910.

Referring now toFIG. 10, a mockup of an in-vehicle infotainment system110GUI1000is illustrated. In one embodiment an IPAWS visual alert in the form of a live traffic video feed1010is displayed. IPAWS visual alert live traffic video feed1010is sent from an alert authority and distributed via an alert aggregator to an alert disseminator. Alert disseminator then transmits the IPAWS visual alert live traffic video feed1010to network160, whereby network160transmits to the Antenna150via signal151. The Antenna150then transmits the live multimedia data file to the GWM140via signal141. The GWM140then transmits signal119to an OEM hard-wired in-vehicle infotainment system110. Evacuation routes and natural disaster areas can be broadcast to safely warn occupants of impending danger by transmitting live video feeds, via a multimedia data file, from public traffic cameras.

Referring now toFIG. 11, an illustration of an exemplary computing device1100that can be used in accordance with the systems and methodologies disclosed herein is illustrated. The computing device1100includes memory1110which executes stored instructions for implanting functionality described as being carried out by one or more components discussed above. Data received from the system bus1120is processed by at least one processor1130that executes instructions that are stored in memory1110. Instructions for implementing functionality described as being carried out by one or more components discussed above or instructions for one or more of the methods described above that are carried out by either the software1140or firmware1150. Software1140or firmware1150may additionally include any combination of programmed applications as detailed herein. The computing device1100additionally includes a data storage1160that is accessible by the processor1130through the system bus1120. The data storage1160may include executable instructions. The computing device1100also includes an input interface1180that allows external devices to communicate with the computing device1100. For instance, the input interface1180may be used to receive instructions from an external computer device, from a user, etc. The computing device1100also includes an output interface1170that interfaces the computing device1100with one or more external devices. For example, the computing device1100may display video or images, etc. by way of the output interface1170.

It is contemplated that the external devices that communicate with the computing device1100via the input interface1180and the output interface1170can be included in an environment that provides substantially any type of user interface with which a user can interact. Examples of user interface types include graphical user interfaces, natural user interfaces, and so forth. For instance, a graphical user interface may accept input from a user employing input device(s) such as a keyboard, mouse, remote control, or the like and provide output on an output device such as a display. Further, a natural user interface may enable a user to interact with the computing device1100in a manner free from constraints imposed by input device such as keyboards, mice, remote controls, and the like. Rather, a natural user interface can rely on speech recognition, touch and stylus recognition, gesture recognition both on screen and adjacent in-vehicle Infotainment System110network601to the screen, air gestures, head and eye tracking, voice and speech, vision, touch, gestures, machine intelligence, and so forth.

Referring now toFIG. 12, a methodology1200that facilitates the transmission of a video or picture emanating from an IPAWS compliant CAP Origination Tool, directly onto the GUI of an OEM hard-wired in-vehicle infotainment system110. The methodology begins at1202, where an IPAWS compliant system transmits an IPAWS visual alert. The methodology then transitions to an IPAWS Visual Alert received by the Antenna150. The methodology then transitions to an OEM hard-wired in-vehicle infotainment system110Validating the IPAWS Visual Alert1206data file. The methodology transitions to End executable action1208, if the IPAWS visual alert can't be validated. If the OEM hard-wired in-vehicle Infotainment System110validates an IPAWS visual alert has been received, methodology will transition to IPAWS Visual Alert File Format Recognized1210. If the IPAWS visual alert file format is not recognized, the methodology transitions to an Error: Do not display IPAWS Visual Alert file1212. If the IPAWS Visual Alert file format is Recognized1210, a subroutine whereby the OEM hard-wired in-vehicle infotainment system110opens up a compatible media player1214, based on the multimedia file extension transmitted. The methodology then transitions to Start IPAWS Visual Alert1216.

FIG. 13is a functional block diagram of an exemplary system1300that facilitates the transmission of an IPAWS visual alert1301in the form of an image, picture, video or hologram as received in a multimedia data file transmitted via signal1302, for display onto an OEM hard-wired in-vehicle infotainment system110. Methodology starts with the creation of an IPAWS visual alert multimedia file created with a compliant Common Alert Protocol (CAP) Alert Origination Tool by Alerting Authorities network1350, consisting of Local1352, State1353, Federal1334, Territorial1335and Tribal1336. Alerting Authorities1350transmits the IPAWS visual alert multimedia file via signal1351, to an IPAWS Open platform for emergency network Alert Aggregator/Gateway1340. Alert Aggregator/Gateway1340then transmits the IPAWS visual alert multimedia file via signal1341to Alert Disseminators IP distribution network1330, consisting of an Emergency Alert System1332, Wireless Emergency Alerts1333, NOAA1334, Internet Services1335, State/Local Unique Alerting1336and Future Technologies1337. Alert Disseminators IP distribution network1330then transmits the IPAWS visual alert multimedia file out via transmitters included within network160including Satellite162, Wi-Fi164and Cell Tower166.

Methodology continues to the vehicle following the IPAWS visual alert multimedia file being transmitted from signal151to the vehicle's Antenna(s)150, which includes any embodiment of a singular or plurality of in-vehicle antenna(s) including GPS, Cellular, PCS, WI-FI or Satellite. Antenna150then transmits the IPAWS visual alert data multimedia file via signal141to the GWM140. In-turn, the GWM140transmits the IPAWS visual alert data multimedia file via signal119to an OEM hard-wired in-vehicle infotainment system110. The OEM hard-wired in-vehicle infotainment system110is equipped with network1320, including Firmware1322or Software1324with the Infotainment System Picture or video Emergency Alert Display application. After the OEM hard-wired in-vehicle infotainment system110processes the IPAWS visual alert multimedia file, using any embodiment included with network1320, signal1302outputs the IPAWS visual alert multimedia file to the OEM hard-wired in-vehicle infotainment system110GUI for display of the IPAWS visual alert1301in file formats, including, but not limited to an image, picture, hologram or video.

Referring now toFIG. 14, a mockup of an OEM in-vehicle infotainment system holographic GUI1400is illustrated. In one embodiment an IPAWS visual alert in the form of a 3D hologram is displayed. Image of an OEM hard-wired in-vehicle infotainment system110holographic image, centered between the vehicle's gauge cluster1410is displayed. Included with the OEM hard-wired in-vehicle infotainment system110is a laser1420and spatial light modulator (SLM)1430used to display a holographic image. Spatial light modulator1430will display a 2D or 3D graphical image1440as received by signal119sent from an IPAWS visual alert. Along with the 2D or 3D image1440, holographic text1450in conjunction or independent of the image can be displayed in hologram form.

Plurality of in-vehicle communication networks pre-existing in vehicle including CAN bus networks designed with multiplex electrical wiring, allowing in-vehicle microcontrollers and modules to communicate between each other exist in a multitude of embodiments. Local Interconnect Network (LIN) operating on 1 Kbps to 20 Kbps. High Speed CAN (HSCAN) operating between 125 Kpbs and 500 Kbps. Low Speed CAN (MSCAN) operating between 40 Kbps and 125 Kbps. InfotainmentCAN (InfoCAN) and Local Area Network (LAN) operating from a transfer speed of both 40 Kbps to 125 Kbps or 125 Kbps to 500 Kbps, when paired to other in-vehicle microcontrollers or transfer speeds ranging from 1 Kbps to 11 Gbps on a cellular network or 11 Mbps to 7,000 Mbps operating on Wi-Fi, with speeds falling under Wi-Fi standards 802.11b, 802.11a, 802.11g, 802.11n or 802.11ac.

Embodiments of “Firmware” and “Software” have been displayed separately in methodology for the purposes of detailing the individual functionality of each application disclosed here-in, comprising the applications; “In-vehicle GPS Geo-Fencing Route Planning”, “GPS Proximity Based Advertising”, “Infotainment System Advertising” and “Infotainment System Picture or Video Emergency Alert Display”. It is further understood that embodiments of the disclosed network120,620and1320encompassing “Firmware”122,622and1322and “Software”124,624and1324may include functionality in-full or in-part of all disclosed applications.