In some embodiments, upon identifying that a geographical location of the intersection is associated with a content item, the system causes the presentation of the content item via an entertainment device of the vehicle. For example, the system causes the advertisement for the baseball game to be presented on the device 218 in the vehicle. In some embodiments, the device 218 that presents the content item may be associated with the vehicle, for example, an interactive entertainment device attached to the vehicle. In some embodiments, the device that presents the content item may be within the vehicle, for example, a mobile phone. In some embodiments, the device that presents the content item may be the device providing navigation to the vehicle through the predicted path. In some embodiments, the device that presents the content item may be a second device different from the device providing navigation to the vehicle through the predicted path. In the illustrative example, while vehicle 208 remains at intersection 204, a content item 218 (e.g., promotion for the baseball game, “Yankees vs. Red Sox are playing now, join us!!!”) is presented on the entertainment device.

FIG. 3 depicts exemplary systems, servers and related hardware for providing dynamic in-vehicle content based on the predicted path of the vehicle and the merchants within a threshold distance of an intersection, in accordance with some embodiments of the disclosure. FIG. 3 shows a generalized embodiment of an illustrative system 300 in which user equipment device 118 of FIG. 1 and the system 100 of FIG. 1 can be implemented. System 100 includes an array of intersections (e.g., 302a, 302b, 302c, 302d . . . 302n) associated with content sources (e.g., 304a, 304b, 304c, 304d . . . 304n) with each content source being associated with a content item (e.g., 303a, 303b, 303c, 303d . . . 303n). The content sources (e.g., 304a, 304b, 304c, 304d . . . 304n) may be coupled to storage device 306, server 308 and a vehicle 310. The vehicle 310 can communicate bidirectionally with other systems outside of the vehicle. Communications with the content sources (e.g., 304a, 304b, 304c, 304d . . . 304n) and storage device 306 may be exchanged over one or more communications paths but are shown as a single path in FIG. 3 to avoid overcomplicating the drawing.

The array of intersections (e.g., 302a, 302b, 302c, 302d . . . 302n) may include a plurality of intersections dispersed around the country associated with merchants in close proximity to the content sources (e.g., 304a, 304b, 304c, 304d . . . 304n). The intersections 302 may be coupled to content sources (e.g., 304a, 304b, 304c, 304d . . . 304n) that associate content items (e.g., 303a, 303b, 303c, 303d . . . 303n) with content sources (e.g., 304a, 304b, 304c, 304d . . . 304n) and deliver them to the storage device 306. The content items are connected to the server 308 for processing for content item recognition and geographical origin determination. The content items are processed through an automated content recognition. The automated content recognition can store, allocate based on content recognition and process for the presentation of the content items. The server 308 may be a collection of servers connected to the storage device for improved processing. The vehicle includes a user interface 312 and an antenna 314 that communicate with the storage device 306. All of the communication between the antennas, collectors, servers and vehicle may be through one or more networks including the Internet, a mobile phone network, mobile voice or data network (e.g., a 4G, 5G or LTE network), or other types of communications network or combinations of communications networks for in-vehicle use.

FIG. 4 depicts exemplary devices and related hardware for providing dynamic in-vehicle content based on the predicted path of the vehicle, in accordance with some embodiments of the disclosure. A user or occupant in a vehicle may access content and the vehicle content interface application (and its display screens described above and below) from one or more of their user equipment devices. FIG. 4 shows a generalized embodiment of illustrative user equipment device 400. More specific implementations of user equipment devices are discussed above in connection with FIG. 3. User equipment device 400 may receive content and data via input/output (I/O) path 416. I/O path 416 may provide content (e.g., broadcast programming, on-demand programming, Internet content, content available over a local area network (LAN) or wide area network (WAN), and/or other content) and data to control circuitry 412, which includes processing circuitry 410 and storage 414. Control circuitry 412 may be used to send and receive commands, requests, and other suitable data using I/O path 416.

Control circuitry 412 may be based on any suitable processing circuitry such as processing circuitry 410. As referred to herein, processing circuitry should be understood to mean circuitry based on one or more microprocessors, microcontrollers, digital signal processors, programmable logic devices, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc., and may include a multi-core processor (e.g., dual-core, quad-core, hexa-core, or any suitable number of cores) or supercomputer. In some embodiments, processing circuitry may be distributed across multiple separate processors or processing units. In some embodiments, control circuitry 412 executes instructions for a vehicle content interface application stored in memory (i.e., storage 414). Specifically, control circuitry 412 may be instructed by the vehicle content interface application to perform the functions discussed above and below. For example, the vehicle content interface application may provide instructions to control circuitry 412 to generate the audio content display. In some implementations, any action performed by control circuitry 412 may be based on instructions received from the vehicle content interface application.

In client/server-based embodiments, control circuitry 412 may include communications circuitry suitable for communicating with a content application server or other networks or servers. The instructions for carrying out the above-mentioned functionality may be stored on the content application server. Communications circuitry may include a cable modem, an integrated-services digital network (ISDN) modem, a digital subscriber line (DSL) modem, a telephone modem, Ethernet card, or a wireless modem for communications with other equipment, or any other suitable communications circuitry. Such communications may involve the Internet or any other suitable communications networks or paths (which are described in more detail in connection with FIG. 5). In some embodiments, an antenna 408 is provided in the user equipment device 400. The antenna 408 may be used for communication with the network of antennas. In addition, communications circuitry may include circuitry that enables peer-to-peer communication of user equipment devices, or communication of user equipment devices in locations remote from each other (described in more detail below).

Memory may be an electronic storage device provided as storage 414 that is part of control circuitry 412. As referred to herein, the phrase “electronic storage device” or “storage device” should be understood to mean any device for storing electronic data, computer software, or firmware, such as random-access memory, read-only memory, hard drives, optical drives, digital video disc (DVD) recorders, compact disc (CD) recorders, BLU-RAY disc (BD) recorders, BLU-RAY 3D disc recorders, digital video recorders (DVR, sometimes called a personal video recorder, or PVR), solid state devices, quantum storage devices, gaming consoles, gaming media, or any other suitable fixed or removable storage devices, and/or any combination of the same. Storage 414 may be used to store various types of content described herein as well as content data and content application data that are described above. Nonvolatile memory may also be used (e.g., to launch a boot-up routine and other instructions). Cloud-based storage may be used to supplement storage 414 or instead of storage 414.

Control circuitry 412 may include video generating circuitry and tuning circuitry, such as one or more analog tuners, one or more MPEG-2 decoders or other digital decoding circuitry, high-definition tuners, or any other suitable tuning or video circuits or combinations of such circuits. Encoding circuitry (e.g., for converting over-the-air, analog, or digital signals to MPEG signals for storage) may also be provided. Control circuitry 412 may also include scaler circuitry for upconverting and down-converting content into the preferred output format of the user equipment device 400. Control Circuitry 412 may also include digital-to-analog converter circuitry and analog-to-digital converter circuitry for converting between digital and analog signals. The tuning and encoding circuitry may be used by the user equipment device to receive and to display, play, or record content. In some embodiments, the control circuitry may include an HD antenna.

In one embodiment, speakers 406 may be provided as integrated with other elements of user equipment device 400 or may be stand-alone units. The audio and other content displayed on display 404 may be played through speakers 406. In some embodiments, the audio may be distributed to a receiver (not shown), which processes and outputs the audio via speakers 406.

In some embodiments, a sensor (not shown) is provided in the user equipment device 400. The sensor may be used to monitor, identify, and determine vehicle status data. For example, the vehicle content interface application may receive vehicle status data from the sensor or any other vehicle status data (e.g., global positioning data of the vehicle, driving condition of the vehicle, etc.) received from any other vehicular circuitry and/or component that describes the status of the vehicle.

The vehicle content interface application may be implemented using any suitable architecture. For example, it may be a stand-alone application wholly implemented on user equipment device 400. In such an approach, instructions of the application are stored locally (e.g., in storage 414), and data for use by the application is downloaded on a periodic basis (e.g., from an out-of-band feed, from an Internet resource, or using another suitable approach). Control circuitry 412 may retrieve instructions of the application from storage 414 and process the instructions to generate any of the displays discussed herein. Based on the processed instructions, control circuitry 412 may determine what action to perform when input is received from input interface 402. For example, the movement of a cursor on an audio user interface element may be indicated by the processed instructions when input interface 402 indicates that a user interface 118 was selected.

In some embodiments, the vehicle content interface application is a client/server-based application. Data for use by a thick or thin client implemented on user equipment device 400 is retrieved on-demand by issuing requests to a server remote to the user equipment device 400. In one example of a client/server-based content application, control circuitry 412 runs a web browser that interprets web pages provided by a remote server. For example, the remote server may store the instructions for the application in a storage device. The remote server may process the stored instructions using circuitry (e.g., control circuitry 412) and generate the displays discussed above and below. The client device may receive the displays generated by the remote server and may display the content of the displays locally on user equipment device 400. This way, the processing of the instructions is performed remotely by the server while the resulting displays are provided locally on user equipment device 400. User equipment device 400 may receive inputs from the user or occupant of the vehicle via input interface 402 and transmit those inputs to the remote server for processing and generating the corresponding displays. For example, user equipment device 400 may transmit, via antenna 408, communication to the remote server, indicating that a user interface element was selected via input interface 402. The remote server may process instructions in accordance with that input and generate a display of content identifiers associated with the selected user interface element as described in greater detail with reference to FIGS. 6 and 7. The generated display is then transmitted to user equipment device 400 for presentation to the user or occupant of the vehicle.

In some embodiments, the vehicle content interface application is downloaded and interpreted or otherwise run by an interpreter or virtual machine (run by control circuitry 412). In some embodiments, the vehicle content interface application may be encoded in the ETV Binary Interchange Format (EBIF), received by control circuitry 412 as part of a suitable feed, and interpreted by a user agent running on control circuitry 412. For example, the vehicle content interface application may be an EBIF application. In some embodiments, the vehicle content interface application may be defined by a series of JAVA-based files that are received and run by a local virtual machine or other suitable middleware executed by control circuitry 412. In some of such embodiments (e.g., those employing MPEG-2 or other digital media encoding schemes), the vehicle content interface application may be, for example, encoded and transmitted in an MPEG-2 object carousel with the MPEG audio of a program.

User equipment device 400 of FIG. 4 can be implemented in system 500 of FIG. 5 as vehicle media equipment 514, vehicle computer equipment 518, wireless user communications device 522 or any other type of user equipment suitable for accessing content, such as a non-portable gaming machine. For simplicity, these devices may be referred to herein collectively as user equipment or user equipment devices and may be substantially similar to user equipment devices described above. User equipment devices, on which a vehicle content interface application may be implemented, may function as stand-alone devices or may be part of a network of devices. Various network configurations of devices may be implemented and are discussed in more detail below.

FIG. 5 depicts exemplary systems, servers and related hardware for providing dynamic in-vehicle content based on the predicted path of the vehicle, in accordance with some embodiments of the disclosure. A user equipment device utilizing at least some of the system features described above in connection with FIG. 5 may not be classified solely as vehicle media equipment 514, vehicle computer equipment 516, or a wireless user communications device 522. For example, vehicle media equipment 514 may, like some vehicle computer equipment 516, be Internet-enabled, allowing for access to Internet content, while wireless user computer equipment 522 may, like some vehicle media equipment 514, include a tuner allowing for access to media programming. The vehicle content interface application may have the same layout on various types of user equipment or may be tailored to the display capabilities of the user equipment. For example, on wireless user computer equipment 516, the vehicle content interface application may be provided as a website accessed by a web browser. In another example, the vehicle content interface application may be scaled down for wireless user communications devices 522.

The user equipment devices may be coupled to communications network 510. Communications network 510 may be one or more networks including the Internet, a mobile phone network, mobile voice or data network (e.g., a 4G, 5G or LTE network), cable network, public switched telephone network, or other types of communications network or combinations of communications networks.

System 500 includes content source 502 and vehicle content interface data source 504 coupled to communications network 510. Communications with the content source 502 and the data source 504 may be exchanged over one or more communications paths but are shown as a single path in FIG. 5 to avoid overcomplicating the drawing. Although communications between sources 502 and 504 with user equipment devices 514, 516, and 522 are shown through communications network 510, in some embodiments, sources 502 and 504 may communicate directly with user equipment devices 514, 516, and 522.

Content source 502 may include one or more types of content distribution equipment including a media distribution facility, satellite distribution facility, programming sources, intermediate distribution facilities and/or servers, Internet providers, on-demand media servers, and other content providers. Vehicle content interface data source 504 may provide content data, such as the audio described above. Vehicle content interface application data may be provided to the user equipment devices using any suitable approach. In some embodiments, vehicle content interface data from vehicle content interface data source 504 may be provided to users' equipment using a client/server approach. For example, a user equipment device may pull content data from a server, or a server may present the content data to a user equipment device. Data source 504 may provide user equipment devices 514, 516 and 522 the vehicle content interface application itself or software updates for the vehicle content interface application.

FIG. 6 depicts an illustrative example of a vehicle featuring a content display for providing dynamic in-vehicle content, in accordance with some embodiments of the present disclosure. In one embodiment, user equipment may refer to components incorporated into, coupled to, or accessible by a vehicle such as vehicle 600 in FIG. 6. The vehicle 600 is equipped with a vehicle content interface application that may be used to enable/disable content options. For example, an occupant in vehicle 600 may use vehicle content interface component 602 to access content in the vehicle 600. In some embodiments, the vehicle content interface component 602 may be an audio system incorporated into vehicle 600 or user equipment used to access such content while using vehicle 600. Further, as depicted in FIG. 6, the vehicle content interface component 602 may present content in response to the vehicle being within a threshold distance of the intersection 604.

FIG. 7 depicts an illustrative example of an in-vehicle content interface application for dynamic in-vehicle content, in accordance with some embodiments of the present disclosure. As discussed above, in some embodiments, a user or occupant of the vehicle 600 may select the user interface 700 via a user interface 118 (FIG. 1) and 218 (FIG. 2) incorporated into or accompanying the vehicle content interface component 702. The vehicle content interface component 702 may be inserted into the user interface 700 in response to the vehicle being within a threshold distance of the intersection 604. Upon determining that the vehicle is within a threshold distance of the intersection 604, the user interface 118 may display a content item 702 with a promotion 704 “New York Yankees vs Boston Red Sox” on the display screen 700 as shown in FIG. 7. For the duration of the user or occupant of the vehicle remaining within a threshold distance of the intersection 604, one of the content items is presented via the user interface (e.g., vehicle entertainment device 700 (FIG. 7) incorporated into or accompanying the vehicle.

As discussed above, in some embodiments, to provide dynamic in-vehicle content, a user interface 118 is displayed on the screen of the vehicle content interface component 702. In one example, an occupant in the vehicle 600 may provide an instruction for a destination, resulting in the system generating a predicted path incorporated into or accompanying the vehicle content interface component 702 by direct input into the user interface. Upon the user's selection of the destination, predicted paths may be displayed on the display screen 700 along with merchants (e.g., content sources) associated with intersections along the predicted paths. When the user selects one of the predicted paths via the user interface (e.g., user input interface 118 (FIG. 1)) incorporated into or accompanying the vehicle content interface component 702, the selected predicted path may include identifiers that correspond to the content type displayed on the screen. For example, the user selects a predicted path and, as the user drives along the predicted path, is prompted with an advertisement upon entering a threshold distance of an intersection. The content items may include information about content type and the geographical origin corresponding to each other. In some embodiments, the content items presented on display may provide a selectable option to navigate to the content source.

FIG. 8 is a flowchart of a detailed illustrative process for providing dynamic in-vehicle content based on the predicted path of the vehicle, in accordance with some embodiments of the disclosure. As shown in FIG. 8, in accordance with some embodiments, a process 800 may be executed by processing circuitry 400 of a vehicle (FIG. 4). It should be noted that process 800 or any step thereof could be performed on, or provided by, the system of FIGS. 4 and 5 or any of the devices shown in FIGS. 1, 2, 6 and 7. In addition, one or more of process 800 may be incorporated into or combined with one or more other steps described herein (e.g., incorporated into steps of process 900). For example, process 800 may be executed by control circuitry 412 (FIG. 4) as instructed by a vehicle content interface application implemented on a user device in order to present a content item based on the vehicle being within a threshold distance of an intersection location based on vehicle's geographical location. Also, one or more steps of process 800 may be incorporated into or combined with one or more steps of any other process or embodiment.

At step 802, the system predicts the path of the vehicle. For example, the occupant of the vehicle has entered a destination, and, based on the geographical location, the system identifies a predicted path of the vehicle. In some embodiments, the vehicle's geographical location, the weather conditions, and the destination of the vehicle may be received and processed individually, or, in some embodiments, a set of environmental data may be identified for analysis based on criteria such as user preferences, for example, for the predicted path. In some embodiments, the system may access the metadata associated with the user's historical transactions. For example, every transaction the user makes is stored in a database including the location, time, date, type of order, restaurant and any other suitable information. The predicted path may be selected to travel along a merchant's location that the user has previously purchased content from based on the transaction history. In some embodiments, the predicted path may be any path traveled by the vehicle that may be altered.

At 804, the system identifies an intersection along the predicted path of the vehicle, for example, an intersection on the map that will likely result in the occupant of the vehicle stopping and result in availability to focus on some entertainment device. In some embodiments, the system may identify intersection points on the map that cause a slowdown for the vehicle. For example, the system searches for intersections that cause a delay (and, for example, occur at the same or similar time and include the same or similar route). In some embodiments, the intersections may be identified based on historical transactions including a time of the day and the day of the week.

At 806, the system determines whether the vehicle is decelerating along the predicted path within a threshold distance of the intersection. For example, as the vehicle approaches the intersection on the map, along the predicted path, the vehicle reduces speed. Based on sensors in the vehicle, the system may detect that the vehicle is slowing down. To determine that the vehicle is decelerating towards the location of the intersection, the system may evaluate the GPS coordinates for the vehicle, the user's mobile device or any other suitable device for tracking GPS and the motion of said devices. The threshold distance of the intersection may be preselected by the content source, or the vehicle or set as a default distance, (e.g., 500 feet or 1000 feet from the intersection). The threshold distance may be selected based on preference and/or based on the merchant. If the system determines that the vehicle is decelerating along the predicted path within a threshold distance of the intersection (“Yes” at 806), then, at 808, the system determines whether a geographical location of the intersection is associated with a content item. This occurs without the user's input. If, on the other hand, the system determines that the vehicle is not decelerating within a threshold distance of the intersection (“No” at 806), then 802 may be repeated.

At 808, the system determines whether a geographical location of the intersection is associated with a content item. For example, does a merchant (e.g., Starbuck) near the intersection on the map have an advertisement that would be suitable for presenting in a vehicle device. If the system determines that a geographical location of the intersection is associated with a content item (“Yes” at 808), then, at 810, the system causes presentation of the content item via an entertainment device of the vehicle. For example, an audio promotion for a business may play via the speakers in the vehicle. In another example, an audio promotion for a business may play via the display in the vehicle. This occurs without the user's input. If, on the other hand, the system determines that a geographical location of the intersection is not associated with a content item (“No” at 808), then 802 may be repeated.

FIG. 9 is a flowchart of another detailed illustrative process for providing alternate dynamic in-vehicle content based on vehicle environment data and user data, in accordance with some embodiments of the disclosure. As shown in FIG. 9, in accordance with some embodiments, a process 900 may be executed by processing circuitry 400 of a vehicle (FIG. 4). It should be noted that process 900 or any step thereof could be performed on, or provided by, the system of FIGS. 4 and 5 or any of the devices shown in FIGS. 1, 2, 6 and 7. In addition, one or more of process 900 may be incorporated into or combined with one or more other steps described herein (e.g., incorporated into steps of process 800). For example, process 900 may be executed by control circuitry 412 (FIG. 4) as instructed by a vehicle content interface application implemented on a user device in order to present a content item based on the vehicle being within a threshold distance of an intersection location based on the vehicle's geographical location. Also, one or more steps of process 900 may be incorporated into or combined with one or more steps of any other process or embodiment herein.

At step 902, the system captures vehicle environmental data for the vehicle. The system may capture the vehicle's geographical location, the traffic conditions, or the weather conditions; the destination of the vehicle may be received and processed individually, or, in some embodiments, a set of environmental data may be identified for analysis based on criteria such as user preferences, for example, for the predicted path. In some embodiments, the system may access the metadata associated with the user's historical transactions. For example, every transaction the user makes is stored in a database including the location, time, date, type of order, restaurant and any other suitable information.

At 904, the system identifies user attention data. The system may employ cameras and microphones in the vehicle along with the vehicle's data to identify the users or occupant's attention data, including monitoring biometric data from wearable sensors. Based on said user attention data the system may determine where they are able to focus on the entertainment devices in the vehicle. For example, the occupant's attention factors may consider the historical traffic data with in-vehicle sensors to identify the road conditions (e.g., potholes, number of people on sidewalks, number of cars, etc.), movements of a user, such as head movements, eye movements, hand motions, other suitable user movements, and patterns of any such movements.