Frequency Modulation (FM) broadcasts transport content, such as music, news, sports, and the like. The FM broadcasts also transport Radio Data System (RDS) data that include data items, such as the time, station call letters, broadcast frequency, station content, song title, song artist, and advertisement text. FM radios decode and display the RDS data to accompany the playing of the audio content.
Vehicles are increasingly receiving computer and communication systems to provide hands-free control to the vehicle operator. The hands-free operation may include an audio control interface for the user, as well as, graphical displays and the like. For example, a user may use spoken commands to operate their phone while driving to place and answer calls in a hands-free manner.
Unfortunately, the FM radios and the vehicle control systems are not effectively and efficiently coordinated for an optimal user experience that enhances safety while allowing robust user interaction with an FM radio program.
A wireless communication system wirelessly receives a Frequency Modulation (FM) signal including audio data and Radio Data System (RDS) data. The wireless communication system audibly plays the audio data and graphically displays the RDS data from the FM signal. The wireless communication system detects action codes in the RDS data, and in response, initiates a wireless communication session with a wireless communication network. The wireless communication system also audibly captures user data. The wireless communication system then wirelessly transfers the captured user data for delivery to a server over the wireless communication session.
In operation, FM receiver 101 wirelessly receives Frequency Modulation (FM) signal 121 from FM transmitter 120. FM signal 121 includes both audio data and RDS data. FM receiver 101 decodes and transfers the audio data and the RDS data to processing system 104. Processing system 104 transfers the audio data and the RDS data to audio system 102. Audio system 102 audibly plays the audio data and graphically displays the RDS data. For example, audio system 102 may play a song from its speakers while identifying the FM station, artist, and song title on a graphic display.
Processing system 104 also processes the RDS data from FM signal 121 to detect one or more action codes. An action code comprises a data set that is distinguishable from other RDS data and that is associated with an instruction set within processing system 104. An exemplary action code might be the text sequence “!!34df!!sfb##$sd345.” The action codes may be relatively simple or have a complex syntax of code type, code task, security data, and the like. Processing system 104 maintains logic and data to authorize and translate the RDS action codes into executable computer instructions.
In response to detecting one or more action codes, processing system 104 initiates wireless communication session 131 with wireless communication network 130 through wireless transceiver 103. Processing system 104 also directs audio system 102 to capture spoken user data. In response, wireless transceiver 103 establishes communication session 131 with wireless communication network 130 and audio system 102 captures user data in the form of spoken audio. Processing system 104 then directs wireless transceiver 103 to transfer the captured user audio data to a server over wireless communication session 131. In some cases, processing system 104 processes the RDS data to identify source and/or destination Internet Protocol (IP) addresses for an IP message containing the spoken user data. Communication session 131 uses a wireless communication protocol, such as Long Term Evolution (LTE), Evolution-Data Optimized (EVDO), High Speed Packet Access (HSPA), Wireless Fidelity (Wi-Fi), or some other wireless format.
Although there are various uses for communication system 100, some examples allow a broadcast FM radio station to interact safely with the operator of a vehicle by prompting listeners of the FM broadcast and initiating contemporaneous audio-capture and wireless transfer of their spoken user responses. For example, a radio DJ may request traffic reports in their FM broadcast signal from drivers who can safely and dynamically respond with live audio feedback. Note that various security features, such as biometric user validation and FM frequency screening, could be implemented as desired.
Wireless communication system 100 also processes the RDS data from FM signal 121 to detect one or more action codes (204). There could be many different actions codes that trigger various actions. In response to detecting particular action codes (205), wireless communication system 100 initiates wireless communication session 131 with wireless communication network 130 (206) and captures spoken user data (207). Wireless communication system 100 then transfers the captured user data to a server over wireless communication session 131 (208).
In operation, FM receiver 301 wirelessly receives FM signal 321 from FM transmitter 320. FM signal 321 includes both audio data and RDS data. FM receiver 301 decodes and transfers the audio data and the RDS data to processing system 304. Processing system 304 transfers the audio data to audio system 302 and transfers the RDS data to touch display 305. Audio system 302 audibly plays the audio data and touch display 305 graphically displays the RDS data. For example, audio system 302 may play a song from its speakers while touch display 305 graphically presents the FM station, artist, and song title.
Processing system 304 also processes the RDS data from FM signal 321 to detect action codes. An action code is distinguishable from other RDS data and is associated with an instruction set in processing system 304. In response to one action code, processing system 304 directs wireless transceiver 303 to establish wireless communication session 331 with wireless communication network 330. In response to that action code or another, processing system 304 directs audio system 302 to capture spoken user data. In response to these directions, wireless transceiver 303 establishes communication session 331 with wireless communication network 330 and audio system 302 captures user data in the form of spoken audio. Processing system 304 then directs wireless transceiver 303 to transfer the captured user audio data to a server over wireless communication session 331.
If the action codes are authorized (403), vehicle system 300 prompts the user to invoke RDS-based control and receives a positive user input (404). The prompt and response might be audible, graphic, touch-based, or the like in a manner suitable for a vehicle operator to handle.
In response to the positive user input (404), vehicle system 300 invokes the vehicle control interface to capture spoken user data (405). In response to the positive user input (404), vehicle system 300 also registers with the wireless communication network and obtains an Internet Protocol (IP) address for the user (406). Vehicle system 300 also translates information from the RDS data into a destination IP address (407). The information may be call letters, frequency, text strings, action codes, and the like that system 300 converts into an associated domain name using an internal data structure. Vehicle system 300 may access a Domain Name Service (DNS) over the wireless communication session to translate the domain name into the destination IP address.
Vehicle communication and control system 300 then transfers the user audio data in IP packets using the user (source) IP address and the destination IP address to wireless communication network 330 for subsequent delivery to a remote server (408).
FM receiver 501 comprises communication components, such as antennas, filters, amplifiers, signal processing circuitry, memory, software, and the like. FM receiver 501 demodulates FM signals including both audio and RDS data.
Wireless transceiver system 502 comprises communication components, such as antennas, filters, amplifiers, signal processing circuitry, and the like. Wireless transceiver system 502 communicates over wireless communication networks as described herein.
Audio system 507 comprises speakers, microphones, and associated components to interact audibly with the user.
Graphical display system 508 comprises a touch-screen, lights, and associated components to graphically and tactilely interact with the user.
Processing circuitry 504 comprises circuit boards that hold integrated circuitry and associated electronics. Storage system 505 comprises non-transitory, machine-readable, data storage media, such as flash drives, disc drives, memory circuitry, and the like. Software 506 comprises machine-readable instructions that control the operation of processing circuitry 504 when executed. Software 506 includes modules 511-513 and may also include operating systems, applications, utilities, databases, and the like. All or portions of software 506 may be externally stored on one or more storage media, such as flash drives, discs, servers, and the like.
When executed by processing circuitry 504, RDS data module 511 directs circuitry 504 to display RDS data, detect action codes in the RDS data, and translate the actions codes into executable processing instructions. When executed by processing circuitry 504, audio control module 512 directs circuitry 504 to audibly interact with the user to obtain spoken audio, permissions, and other user instructions. When executed by processing circuitry 504, network interface module 513 directs circuitry 504 to initiate wireless communication sessions and perform wireless IP communications.
The above description and associated figures teach the best mode of the invention. The following claims specify the scope of the invention. Note that some aspects of the best mode may not fall within the scope of the invention as specified by the claims. Those skilled in the art will appreciate that the features described above can be combined in various ways to form multiple variations of the invention. As a result, the invention is not limited to the specific embodiments described above, but only by the following claims and their equivalents.
Number | Name | Date | Kind |
---|---|---|---|
6628928 | Crosby et al. | Sep 2003 | B1 |
8310985 | Harb | Nov 2012 | B2 |
20060141962 | Forbes et al. | Jun 2006 | A1 |
20090239557 | Kadakia et al. | Sep 2009 | A1 |
Number | Date | Country |
---|---|---|
1100031 | May 2001 | EP |