Vehicle-based message control using cellular IP

Information

  • Patent Grant
  • 9478215
  • Patent Number
    9,478,215
  • Date Filed
    Friday, June 14, 2013
    11 years ago
  • Date Issued
    Tuesday, October 25, 2016
    8 years ago
Abstract
Architecture for playing back personal text-based messages such as email and voicemail over a vehicle-based media system. The user can use a cell phone that registers over a cellular network to an IMS (IP multimedia subsystem) to obtain an associated IP address. The personal messages are then converted into audio signals using a remote text-to-voice (TTV) converter and transmitted to the phone based on the IP address. The phone then transmits the audio signals to the vehicle media system for playback using an unlicensed wireless technology (e.g., Bluetooth, Wi-Fi, etc.). Other alternative embodiments include transmitting converted message directly to the media system, via a satellite channel, converting the messages via a TTV converter on the cell phone, and streaming the converted messages to the phone and/or the media system for playback.
Description
TECHNICAL FIELD

This invention relates to wireless communication systems, and more specifically, to the playback of text-based messages via an audio system.


BACKGROUND

The convergence of the IP-based services and cellular communications services has opened the door for providing services that heretofore were not available to the cellular user who seeks access to IP-based networks, as well as for IP users seeking access to services of the cellular networks. Wireless devices such as portable computers and smartphones can now access services on wired/wireless networks using IP technology. Such advances have served as a catalyst for a mobile society where workers can commute greater distances while maintaining connectivity to businesses or homes. For example, users can be seen talking on cell phones and operating computers as they travel from location to location. These activities, while troublesome, are yet to be regulated in any significant way.


In today's world of electronics, there can be many potential distractions to drivers while traveling. For example, drivers read email, respond to text messaging and/or attempt to listen to voicemail while driving. Conventional applications that attempted to address this growing problem employed FM modulators with small attached microphones to play voicemail, for example. However, there needs to be more hands-free, and hence, safer, mechanisms available for listening to email and other information while in a vehicle, whether the vehicle is moving or not.


SUMMARY

The following presents a simplified summary in order to provide a basic understanding of some aspects of the disclosed architecture. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.


The disclosed innovative architecture allows a user to receive personal messages (e.g., text-based) such as email and voicemail over a vehicle media system (e.g., radio). In one example, the vehicle user can listen to email and/or voicemail, and browse through such messages while the messages are being played over a car audio system.


In one embodiment, the user employs a cell phone that registers over the cellular network to an IMS (IP multimedia subsystem) to obtain an associated IP address. The personal messages are then converted into audio signals using a remote text-to-voice (TTV) converter and transmitted to the phone. The phone then transmits the audio signals to the vehicle media system for playback using an unlicensed wireless technology (e.g., Bluetooth, Wi-Fi, etc.).


In another embodiment, the user cell phone registers over the cellular network to the IMS entity to obtain an associated IP address. The personal messages are then converted into audio signals using the remote TTV converter and transmitted to the vehicle media system for playback based on the IP address associated with the cell phone. The user can then interact using the cell phone to browse other messages for download and playback.


In yet another embodiment, the user cell phone registers over the cellular network to the IMS entity to obtain an associated IP address. The personal messages are then input into the remote TTV converter and streamed therefrom over a direct bearer channel to the vehicle media system for playback based on the IP address associated with the cell phone. The user can then interact using the cell phone to browse other messages for download and playback.


In still another embodiment, the user cell phone registers over the cellular network to obtain an associated IP address. The requested text-based messages are then converted remotely and sent to a satellite system for further communication over a dedicated satellite channel to the vehicle (cell phone) associated with the IP address.


In another embodiment, the email and voicemail can be converted to an audio file format (e.g., MP3), sent to the cell phone, and therefrom, via an unlicensed wireless technology (e.g., short range communications) to a radio receiver that is already MP3-ready, for example.


To the accomplishment of the foregoing and related ends, certain illustrative aspects of the disclosed architecture are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles disclosed herein can be employed and is intended to include all such aspects and their equivalents. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 illustrates a communications system for receiving and playing personal messages in a vehicle in accordance with the disclosed architecture.



FIG. 2 illustrates an alternative system where the personal messages are received via a cell phone and thereafter communicated to the vehicle media system for presentation.



FIG. 3 illustrates an exemplary system that employs the architecture with the IMS system.



FIG. 4 illustrates an exemplary system that employs satellite communications to route the personal messages to the vehicle for presentation.



FIG. 5 illustrates an exemplary system that facilitates localized conversion of the messages in the phone.



FIG. 6 illustrates a methodology of presenting messages in a communications system.



FIG. 7 illustrates a methodology of converting the personal messages remotely before download and playback.



FIG. 8 illustrates a methodology of converting the personal messages locally after download.



FIG. 9 illustrates a methodology of employing a satellite system for playback via a vehicle-based audio system.



FIG. 10 illustrates a schematic block diagram of an exemplary multimode handset in accordance with an innovative aspect.





DETAILED DESCRIPTION

As required, detailed novel embodiments are disclosed herein. It must be understood that the disclosed embodiments are merely exemplary and may be embodied in various and alternative forms, and combinations thereof. As used herein, the word “exemplary” is used expansively to refer to embodiments that serve as an illustration, specimen, model or pattern. The figures are not necessarily to scale and some features may be exaggerated or minimized to show details of particular components. In other instances, well-known components, systems, materials or methods have not been described in detail in order to avoid obscuring the invention. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the invention.


Suitable wireless and radio frequency (RF) data transmission systems in which the disclosed invention can be implemented include, but are not limited to, networks utilizing time division multiple access (TDMA), frequency division multiple access (FDMA), wideband code division multiple access (WCDMA), orthogonal frequency division multiplexing (OFDM), wireless fidelity (Wi-Fi), and various other 2.5 and 3G (third generation) and above wireless communications systems. Examples of other suitable enabling bearers include universal mobile telecommunications system (UMTS), enhanced data rates for global evolution (EDGE), high speed downlink/uplink packet access (HSDPA/HSUPA), voice over Internet protocol (VoIP), and similar communications protocols.


Reference is now made to the drawings, wherein like reference numerals are used to refer to like elements throughout.


Referring initially to the drawings, FIG. 1 illustrates a communications system 100 for receiving and playing personal messages in a vehicle in accordance with the disclosed architecture. The system 100 includes a media system 102 of a vehicle 104 for presenting audio information via an audio output element 106 (e.g., a speaker), and a communications component 108 (e.g., wireless radio receiver or transceiver subsystem) for receiving IP-based personal messages (e.g., voicemail, email, etc.) from an IP-based messaging system 110 for presentation via the media system 102. Although depicted as separate from the media system 102, the communications component 108 can be designed as an integral part of the vehicle media system 102. For example, the communications component 108 can be an IP-addressable (or capable) receiving device or subsystem designed as part of the media system 102 to receive addressable data packets that are only transmitted to and received by a single user personal system (e.g., the vehicle media system 112).


In operation, a user can receive personal messages to be played by the vehicle media system 102. For example, an email message can be initially delivered to the messaging system 110 as a text message, converted into an audio format (e.g., MP3), transmitted to the communications component 108 of the vehicle 104, and then played by the media system 102. Alternatively, or in combination therewith, the messaging system 110 can include a text-to-voice (TTV) converter subsystem (not shown) for converting text messages (e.g., email, SMS, etc.) into voice for playback on the media system 102.


In one implementation, the messaging system 110 begins streaming the voice file to the communications component 108 as the voice file is being converted from text by the TTV converter. Alternatively, the messaging system 110 receives a trigger signal (e.g., from a cellular system) that causes the TTV subsystem to begin converting the stored messages from the user account and then sending the converted audio (or voice) files to the communications component 108 ultimately for playback by the vehicle media system 112.


Note that as used herein, the term “vehicle” includes any transportation mechanism such as an automobile, truck, vessel, water craft, aircraft, and motorized or un-motorized transport system, for example.


In another implementation, the user account can include stored voicemail messages which may already be in a suitable audio format (e.g., MP3, WAV, etc.) for transmission to the communications component 108. If not, the voicemail messages can be routed through the TTV converter for conversion into a suitable audio format for playback by the vehicle media system 112.


As illustrated, the messaging system 110 communicates the personal message directly to the vehicle communications component 108. In other words, the personal messages can be transmitted via RF signals using a satellite system (not shown). Alternatively, or in combination therewith, the messaging system 110 can be an IP-based cellular communications system for communicating a converted message to the communications component 108. For example, the communications component 108 can register with an IP multimedia subsystem (IMS) entity of a cellular network to receive the personal messages as IP-based packets. Given the nature of data packets and associated communications medium, it is also possible to encrypt the personal messages as a means of providing security against unauthorized access of the personal messages during the communications process.


It is also within contemplation of the subject architecture that the vehicle media system 112 can receive and output multimedia content via a display such that the vehicle user can view the personal message separately or in combination with hearing the audio playback.



FIG. 2 illustrates an alternative system 200 where the personal messages are received via a cell phone 202 and thereafter communicated to the vehicle media system 112 for presentation. Here, the IP-based messaging system 110 (e.g., IMS-based) is associated with a cellular network 204 (e.g., UMTS). The cell phone 202 registers with an IMS entity 206 of the messaging system 110 to receive the personal messages. The messages can be converted from TTV using a remote TTV converter 208 associated with the messaging system 110. A converted message is received into the phone 202 from the network 204, and thereafter, communicated to the communications component 108 when the phone 202 is in sufficient radio range of the communications component 108 of the vehicle 104. The communications component 108 receives the messages wirelessly from the cell phone 202. The cell phone 202 communicates the messages to the media system 102 (through the communications component 108) via unlicensed wireless radio frequency (RF) signals (e.g., Bluetooth™, Wi-Fi, etc.). The messages can be encrypted from the cell phone 202 to the communications component 108, and then decrypted by the communications component 108 for playback by the media system 102 as audio output.


The phone user does not need to receive the audio output while the vehicle 104 is moving. Moreover, the phone 202 does not need to be inside the vehicle 104. All that is required is that the phone 202 be within the radio range of the communications component 108 based on the particular wireless technology (e.g., Bluetooth) employed for communications between the phone 202 and the communications component 108. Thus, the user can listen to the message(s) while parked and standing outside the vehicle 104. Additionally, the connection between the phone 202 and the communications component 108 can be via a cable or wire rather than wireless, or used in combination with the wireless connection.



FIG. 3 illustrates an exemplary system 300 that employs the architecture with the IMS system 206. The phone 202 registers with the IMS entity 206 via a cellular network (not shown). A confirmation is then sent from the IMS entity 206 back to the phone 202. The IMS entity 206 then registers to the TTV converter 208 via a 3rd party registration process. The converter 208 responds to the IMS 206 with a confirmation message. The phone 202 then subscribes to the IMS entity 206, which entity 206 then subscribes to the converter 208. The converter 208 responds to the IMS entity 206 with a subscribe notify message. The IMS 206 then sends a subscribe notify message to the phone 202.


The system 300 includes a home subscriber server (HSS) 302 that can be employed to store and serve user (or subscriber) profiles (e.g., preferences, accounts, etc.), perform authentication and authorization functions, and physical location information about the user. The HSS 302 provides the interface between the IMS entity 206 and a text and voice component 304. The HSS 302 stores the text and/or voice data received from the component 304, and serves the data into the IMS entity 206 for conversion, where desired. In support thereof, if text data is served up from the HSS 302 for communication to the phone 202, the text data is passed to the TTV converter 208 for conversion, and then back to the IMS 206 for IP communication to the phone 202. As previously indicated, this can be communicated to the phone 202 wirelessly via the cellular network and/or a satellite system. Similar, a voice file from the component 304 that is stored on the HSS 302 can be accessed by the IMS 206 or pushed to the IMS 206 from the HSS 302 for conversion (if needed) and communications to the phone 202.


The system 300 can also include an email component 306 (e.g., an email server) that processes email, but which can also route email to the TTV converter 208 for conversion and transmission indirectly through the IMS 206 to the phone 202, and/or directly (via transfer pathway 308) from the TTV component 208 to the phone 202 (bypassing the IMS 206). In other words, text can be sent to the converter 208 for conversion and communication to the phone 202 as streaming audio over a direct bearer channel (e.g., the pathway 308).



FIG. 4 illustrates an exemplary system 400 that employs satellite communications to route the personal messages to the vehicle 104 for presentation. Here, the phone 202 initiates and completes IMS registration to the IMS entity 206 of the cellular network 204, over a first wireless link 402. As before, the IMS 206 completes the registration process through to the converter 208. The phone 202 can now receive converted text as audio (as well as unconverted data that does not require reformatting) over the first link 402 for wireless transmission of a second link 404 to the communications component 108 for processing and playback by the media system 102. Alternatively, the IMS registration process also assigns a dedicated satellite radio channel based on the IP address (or other unique identifier) assigned to the phone 202. The converted text (or messages) can then be communicated to a satellite 406 via a third link 408, and then communicated to the phone 202 of the vehicle 104 via a fourth link 410. The phone 202 then communicates the voice data to the vehicle media system 112 for output as audio. Here, the satellite radio channel can be tied to the IP address of the user. Based on this relationship, the user's family could attach to the IP address and satellite channel to gain the benefit of the conversion capabilities. Moreover, this further allows each user to essentially have a dedicated satellite channel.



FIG. 5 illustrates an exemplary system 500 that facilitates localized conversion of the messages in the phone 202. Here, the phone 202 includes a TTV converter subsystem 502 for converting text, email, or other similar types of messages into audio (e.g., voice). The system 500 provides the remote TTV converter 208 for those handsets that do not have the local converter 502 capability.


In operation, text, voicemail, email, or other types of personal messages can be received from the text/voice component 304 and/or the email component 306 into the messaging system 110. Based on IMS registration, the raw text, voice, email, or other messages can be routed to the registered phone 202, and processed internally into audio data for output by the vehicle media system 112. Use of the remote converter 208 or the local converter 502 can be selectable based on the system 500 capabilities. For example, it is to be appreciated that local conversion can be a processor-intensive operation such that it may be preferred to convert the messages remotely first, and then simply forward the converted files from the phone 202 to the vehicle media system 112 for playback.


It should be understood that the subject architecture is not limited to cell phones, but also applies to portable devices that have mobile capabilities, such as portable computers, for example. In other words, the vehicle user can register a portable computer to the IMS entity 206 and TTV converter 208, and have email converted, downloaded, and wirelessly transmitted from the portable computer to the communications component 108 for playback by the vehicle media system 112.



FIG. 6 illustrates a methodology of presenting messages in a communications system. While, for purposes of simplicity of explanation, the one or more methodologies shown herein, for example, in the form of a flow chart or flow diagram, are shown and described as a series of acts, it is to be understood and appreciated that the subject innovation is not limited by the order of acts, as some acts may, in accordance therewith, occur in a different order and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the innovation.


At 600, a vehicle-based media system 112 is received for playing content in a vehicle 104 via an audio subsystem. At 602, registration is to an IP system 110 via a cellular network 204 for an associated IP address. At 604, the cellular network 204 is accessed to download personal messages for playback based on the IP address. At 606, the audio signals associated with the personal messages are played via the media system 102.



FIG. 7 illustrates a methodology of converting the personal messages remotely before download and playback. At 700, a vehicle-based media system 112 is received for playing content in a vehicle 104 via an audio subsystem. At 702, a cell phone 202 is brought into communications range of the media system 102 in accordance with an unlicensed wireless technology. At 704, the cell phone 202 registers to an IP system 110 (e.g., IMS 206) via the cellular network 204 to be associated with an IP address. At 706, a remote TTV converter 208 is registered with the IP system 110 and IP address for conversion processing. At 708, the personal messages are converted into audio signals and downloaded to the cell phone 202. At 710, the audio signals are transmitted from the phone 202 to the media system 102 via the unlicensed wireless network. At 712, the audio signals are played back via the vehicle media system 112.



FIG. 8 illustrates a methodology of converting the personal messages locally after download. At 800, a vehicle-based media system 112 is received for playing content in a vehicle 104 via an audio subsystem. At 802, a cell phone 202 is brought into communications range of the media system 102 in accordance with an unlicensed wireless technology. At 804, the cell phone 202 registers to an IP system 110 (e.g., IMS 206) via the cellular network 204 to be associated with an IP address. At 806, the personal messages are downloaded to the cell phone 202. At 808, the personal messages are converted into audio signals using a phone-based TTV converter 502. At 810, the audio signals are transmitted from the phone 202 to the media system 102 via the unlicensed wireless network. At 812, the audio signals are played back via the vehicle media system 112.



FIG. 9 illustrates a methodology of employing a satellite system for playback via a vehicle-based audio system 112. At 900, a vehicle-based media system 112 is received for playing content in a vehicle 104 via an audio subsystem. At 902, a cell phone 202 is brought into communications range of the media system 102 in accordance with an unlicensed wireless technology. At 904, the cell phone 202 registers to an IP system 110 (e.g., IMS 206) via the cellular network 204 to be associated with an IP address. At 906, a remote TTV converter 208 is registered with the IP system 110 and IP address for conversion processing. At 908, the personal messages are converted into audio signals and transmitted to a satellite system. At 910, the audio signals are transmitted to the media system 102 for playback over a dedicated satellite channel based on the IP address.


As used in this application, the terms “component” and “system” are intended to refer to hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer or mobile terminal (cell phone).



FIG. 10 illustrates a schematic block diagram of an exemplary multimode handset 1000 in accordance with an innovative aspect. In order to provide additional context for various aspects thereof, FIG. 10 and the following are intended to provide a brief, general description of a suitable environment in which the various aspects of the innovation can be implemented. While the description includes a general context of computer-executable instructions, those skilled in the art will recognize that the innovation also can be implemented in combination with other program modules and/or as a combination of hardware and software.


Generally, applications (e.g., program modules) can include routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the inventive methods can be practiced with other system configurations, including single-processor or multiprocessor systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.


The handset 1000 (e.g., a cell phone) can typically include a variety of computer-readable media. Computer-readable media can be any available media accessed by the handset systems and includes volatile and non-volatile media, removable and non-removable media. By way of example, and not limitation, computer-readable media can comprise device storage media and communication media. Storage media includes volatile and/or non-volatile, removable and/or non-removable media implemented in any method or technology for the storage of information such as computer-readable instructions, data structures, program modules or other data. Storage media can include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital video disc (DVD) or other optical disk storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the handset systems.


The handset 1000 includes a processor 1002 for controlling and processing onboard operations and functions. A memory 1004 interfaces to the processor 1002 for the storage of data and one or more applications 1006 (e.g., a video player software, user feedback component software, etc.). The applications 1006 can also include a user interface (UI) application 1008 that operates with a client 1010 (e.g., operating system) to facilitate user interaction with handset functionality and data, for example, answering/initiating calls, entering/deleting data, configuring settings, address book manipulation, multimode interaction, etc. The applications 1006 can include other applications 1012 that came installed with the handset 1000 and/or can be installed as add-ons or plug-ins to the client 1010 and/or UI 1008, for example, or for other purposes (e.g., processor, firmware, etc.).


The other applications 1012 can include voice recognition of predetermined voice commands that facilitate user control, call voice processing, voice recording, messaging, email processing, video processing, image processing, music play, as well as subsystems or components described infra. Some of the applications 1006 can be stored in the memory 1004 and/or in a firmware 1014, and executed by the processor 1002 from either or both the memory 1004 or/and the firmware 1014. The firmware 1014 can also store code for execution in power-up initialization and control during normal operation of the handset 1000.


A communications component 1016 can interface to the processor 1002 to facilitate wired/wireless communications with external systems, for example, cellular networks, VoIP (voice-over-IP) networks, local wireless networks or personal wireless networks such as Wi-Fi, Wi-Max, and so on. Here, the communications component 1016 can also include a multimode communications subsystem for providing cellular communications via different cellular technologies. For example, a first cellular transceiver 1018 (e.g., GSM) can be one mode and an Nth transceiver 1020 can provide cellular communications via an Nth cellular network (e.g., UMTS), where N is a positive integer. The communications component 1016 can also include a transceiver 1022 for unlicensed communications (e.g., Wi-Fi, Wi-Max, Bluetooth, etc.) for corresponding communications. The communications component 1016 can also facilitate communications reception from terrestrial radio networks (e.g., broadcast), digital satellite radio networks, and Internet-based radio services networks.


The handset 1000 can process IP data traffic via the communications component 1016 to accommodate IP traffic from an IP network such as, for example, the Internet, a corporate intranet, a home broadband network, a personal area network, etc., via an ISP or broadband cable provider. Thus, VoIP traffic can be utilized by the handset 1000 and IP-based multimedia content can be received in an encoded and/or decoded format.


The handset 1000 includes a display 1024 for displaying multimedia that include text, images, video, telephony functions (e.g., a Caller ID function), setup functions, menus, etc. The display 1024 can also accommodate the presentation of multimedia content (e.g., music metadata, messages, wallpaper, graphics, etc.).


An input/output (I/O) interface 1026 can be provided for serial/parallel I/O of data and/or signals (e.g., USB, and/or IEEE 1394) via a hardwire connection, and other I/O devices (e.g., a keyboard, keypad, mouse, interface tether, stylus pen, touch screen, etc.). The I/O interface 1026 can be utilized for updating and/or troubleshooting the handset 1000, for example.


Audio capabilities can be provided via an audio I/O component 1028, which can include a speaker for the output of audio signals related to, for example, indication that the user pressed the proper key or key combination to initiate the user feedback signal, call signals, music, etc. The audio I/O component 1028 also facilitates the input of audio signals via a microphone to record data and/or telephony voice data, and for inputting voice signals for telephone conversations.


The handset 1000 can include a slot interface 1030 for accommodating a subscriber identity system 1032 that can accommodate a SIM or universal SIM (USIM), and interfacing the subscriber identity system 1032 with the processor 1002. However, it is to be appreciated that the subscriber identity system 1032 can be manufactured into the handset 1000, and updated by downloading data and software thereinto.


An image capture and processing system 1034 (e.g., a camera) can be provided for decoding encoded image content. Additionally, as indicated, photos can be obtained via an associated image capture subsystem of the image system 1034. The handset 1000 can also include a video component 1036 for processing video content received and, for recording and transmitting video content.


Optionally, a geolocation component 1038 (e.g., GPS-global positioning system) facilitates receiving geolocation signals (e.g., from satellites via the communications component 1016) that define the location of the handset 1000. Alternatively, or in combination therewith, the geolocation component 1038 can facilitate triangulation processing for locating the handset 1000.


The handset 1000 also includes a power source 1040 in the form of batteries and/or an AC power subsystem, which power source 1040 can interface to an external power system or charging equipment (not shown) via a power I/O component 1042.


The handset 1000 can also include a TTV converter component 1044 for local conversion of text-based messages (e.g., email) into voice (or audio) files. The voice files can then be communicated via the handset communications component 1016 to the vehicle media system 112 for audio playback.


Wi-Fi networks can operate in the unlicensed 2.4 and 5 GHz radio bands. IEEE 802.11 applies to generally to wireless LANs and provides 1 or 2 Mbps transmission in the 2.4 GHz band using either frequency hopping spread spectrum (FHSS) or direct sequence spread spectrum (DSSS). IEEE 802.11a is an extension to IEEE 802.11 that applies to wireless LANs and provides up to 54 Mbps in the 5 GHz band. IEEE 802.11a uses an orthogonal frequency division multiplexing (OFDM) encoding scheme rather than FHSS or DSSS. IEEE 802.11b (also referred to as 802.11 High Rate DSSS or Wi-Fi) is an extension to 802.11 that applies to wireless LANs and provides 11 Mbps transmission (with a fallback to 5.5, 2 and 1 Mbps) in the 2.4 GHz band. IEEE 802.11g applies to wireless LANs and provides 20+ Mbps in the 2.4 GHz band. Products can contain more than one band (e.g., dual band), so the networks can provide real-world performance similar to the basic 10BaseT wire Ethernet networks used in many offices.


The law does not require and it is economically prohibitive to illustrate and teach every possible embodiment of the present claims. Hence, the above-described embodiments are merely exemplary illustrations of implementations set forth for a clear understanding of the principles of the invention. Variations, modifications, and combinations may be made to the above-described embodiments without departing from the scope of the claims. All such variations, modifications, and combinations are included herein by the scope of this disclosure and the following claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

Claims
  • 1. A method comprising: receiving, by a text-to-audio component, a registration request from an entity of an internet protocol multimedia system being distinct from and in communication with the text-to-audio component, the registration request being received by the text-to-audio component from the entity of the internet protocol multimedia system following the entity of the internet protocol multimedia system receiving a registration request from a mobile communication device and, in response, registering the mobile communication device with the entity of the internet protocol multimedia system by associating an internet protocol address with the mobile communication device, wherein the text-to-audio component is remote from the mobile communication device;in response to receiving the registration request from the entity of the internet protocol multimedia system, providing, by the text-to-audio component, a confirmation message to the entity of the internet protocol multimedia system to register the entity of the internet protocol multimedia system with the text-to-audio component;receiving, by the text-to-audio component, a text-based communication;converting, by the text-to-audio component, the text-based communication to an audio message; andtransmitting, by the text-to-audio component, to the mobile communication device, over a direct bearer channel between the text-to-audio component and the mobile communication device, the audio message.
  • 2. The method of claim 1, wherein the mobile communication device transmits, via a short range communication, the audio message to a vehicle media system for playback of the audio message by the vehicle media system.
  • 3. The method of claim 1, further comprising: receiving, from the entity of the internet protocol multimedia system, a subscribe request; andtransmitting, to the entity of the internet protocol multimedia system, a subscription notice confirming subscription associated with the text-to-audio component.
  • 4. A text-to-audio component comprising: a processor configured to perform operations comprising: receiving, a registration request from an entity of an internet protocol multimedia system being distinct from and in communication with the text-to-audio component, the registration request being received by the text-to-audio component from the entity of the internet protocol multimedia system following the entity of the internet protocol multimedia system receiving a registration request from a mobile communication device and, in response, registering the mobile communication device with the entity of the internet protocol multimedia system by associating an internet protocol address with the mobile communication device, wherein the text-to-audio component is remote from the mobile communication device;in response to receiving the registration request from the entity of the internet protocol multimedia system, providing a confirmation message to the entity of the internet protocol multimedia system to register the entity of the internet protocol multimedia system with the text-to-audio component;receiving a text-based communication;converting the text-based communication to an audio message; andtransmitting, to the mobile communication device, over a direct bearer channel between the text-to-audio component and the mobile communication device, the audio message.
  • 5. The text-to-audio component of claim 4, wherein the mobile communication device transmits, via a short range communication, the audio message to a vehicle media system for playback of the audio message by the vehicle media system.
  • 6. The text-to-audio component of claim 4, wherein the operations further comprise: receiving, from the entity of the internet protocol multimedia system, a subscribe request; andtransmitting, to the entity of the internet protocol multimedia system, a subscription notice confirming subscription associated with the text-to-audio component.
  • 7. A non-transitory computer-readable medium storing instructions that, when executed by a processor of a text-to-audio component, cause the processor to perform operations comprising: receiving a registration request from an entity of an internet protocol multimedia system being distinct from and in communication with the text-to-audio component, the registration request being received by the text-to-audio component from the entity of the internet protocol multimedia system following the entity of the internet protocol multimedia system receiving a registration request from a mobile communication device and, in response, registering the mobile communication device with the entity of the internet protocol multimedia system by associating an internet protocol address associated with the mobile communication device, wherein the text-to-audio component is remote from the mobile communication device;in response to receiving the registration request from the entity of the internet protocol multimedia system, providing a confirmation message to the entity of the internet protocol multimedia system to register the entity of the internet protocol multimedia system with the text-to-audio component;receiving a text-based communication from the internet protocol multimedia system;converting the text-based communication to an audio message; andtransmitting, to the mobile communication device, over a direct bearer channel between the text-to-audio component and the mobile communication device, the audio message.
  • 8. The non-transitory computer-readable medium of claim 7, wherein the mobile communication device transmits, via a short range communication, the audio message to a vehicle media system for playback of the audio message by the vehicle media system.
  • 9. The non-transitory computer-readable medium of claim 7, wherein the operations further comprise: receiving, from the entity of the internet protocol multimedia system, a subscribe request; andtransmitting, to the entity of the internet protocol multimedia system, a subscription notice confirming subscription of the text-to-audio component.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application No. 13/175,999, filed Jul. 5, 2011, now U.S. Pat. No. 8,467,721, which is a continuation of U.S. patent application No. 11/757,170, filed Jun. 1, 2007, now U.S. Pat. No. 7,986,914.

US Referenced Citations (353)
Number Name Date Kind
5991615 Coppinger et al. Nov 1999 A
6091956 Hollenberg Jul 2000 A
6154658 Caci Nov 2000 A
6243443 Low Jun 2001 B1
6253122 Razavi Jun 2001 B1
6330079 Dugan Dec 2001 B1
6360252 Rudy et al. Mar 2002 B1
6370449 Razavi Apr 2002 B1
6381535 Durocher et al. Apr 2002 B1
6430164 Jones Aug 2002 B1
6430604 Ogle et al. Aug 2002 B1
6459988 Fan et al. Oct 2002 B1
6507810 Razavi Jan 2003 B2
6529706 Mitchell Mar 2003 B1
6532418 Chun et al. Mar 2003 B2
6577637 Sieppi Jun 2003 B1
6654790 Ogle et al. Nov 2003 B2
6662163 Albayrak et al. Dec 2003 B1
6678612 Khawam Jan 2004 B1
6728531 Lee et al. Apr 2004 B1
6735435 Newell et al. May 2004 B2
6741841 Mitchell May 2004 B1
6757544 Rangarajan et al. Jun 2004 B2
6757722 Lonnfors et al. Jun 2004 B2
6763226 McZeal, Jr. Jul 2004 B1
6773344 Gabai et al. Aug 2004 B1
6807254 Guedalia et al. Oct 2004 B1
6826407 Helferich Nov 2004 B1
6850497 Sigler et al. Feb 2005 B1
6870914 Bossemeyer Mar 2005 B1
6870916 Henrikson Mar 2005 B2
6873905 Endo et al. Mar 2005 B2
6895238 Newell et al. May 2005 B2
6931255 Mekuria Aug 2005 B2
6940848 Liu Sep 2005 B1
6940954 Toebes Sep 2005 B1
6963633 Diede et al. Nov 2005 B1
6970703 Fuchs Nov 2005 B2
6970935 Maes Nov 2005 B1
6973387 Masclet et al. Dec 2005 B2
6981023 Hamilton et al. Dec 2005 B1
6981263 Zhang et al. Dec 2005 B1
6993347 Bodin et al. Jan 2006 B2
6996227 Albal et al. Feb 2006 B2
6999469 Chu et al. Feb 2006 B1
7006609 Cloutier et al. Feb 2006 B2
7027568 Simpson Apr 2006 B1
7027808 Wesby Apr 2006 B2
7039402 Gan et al. May 2006 B1
7043232 Pelaez et al. May 2006 B2
7049982 Sleboda et al. May 2006 B2
7069338 Popovich Jun 2006 B2
7099453 Crockett Aug 2006 B2
7113911 Hinde Sep 2006 B2
7127400 Koch Oct 2006 B2
7145898 Elliott Dec 2006 B1
7203721 Ben-Efraim Apr 2007 B1
7219123 Fiechter May 2007 B1
7228355 Dowling Jun 2007 B2
7239881 Lekutai Jul 2007 B2
7254417 Slemmer et al. Aug 2007 B2
7257426 Witkowski Aug 2007 B1
7260087 Bao Aug 2007 B2
7286857 Walker Oct 2007 B1
7289616 Punaganti Venkata et al. Oct 2007 B2
7289796 Kudoh Oct 2007 B2
7310329 Vieri et al. Dec 2007 B2
7319742 Levine Jan 2008 B2
7327832 Russell Feb 2008 B1
7346347 Struhsaker Mar 2008 B2
7346374 Witkowski et al. Mar 2008 B2
7415240 Slemmer et al. Aug 2008 B2
7427024 Gazdzinski et al. Sep 2008 B1
7440433 Rink Oct 2008 B2
7440556 Bear et al. Oct 2008 B2
7443971 Bear et al. Oct 2008 B2
7454203 Levitan Nov 2008 B2
7454346 Dodrill Nov 2008 B1
7457638 Dhillon Nov 2008 B2
7463890 Herz et al. Dec 2008 B2
7472068 Koch Dec 2008 B2
7487112 Barnes, Jr. Feb 2009 B2
7489946 Srinivasan et al. Feb 2009 B2
7496102 Chow Feb 2009 B2
7496516 Tessel et al. Feb 2009 B2
7499704 Bonner Mar 2009 B1
7512714 Eckert Mar 2009 B2
7519042 Gorday Apr 2009 B2
7545918 Edwards Jun 2009 B2
7554435 Tengler Jun 2009 B2
7561547 Brideglall Jul 2009 B2
7561963 Brice et al. Jul 2009 B2
7574821 Furem Aug 2009 B2
7577429 Bear et al. Aug 2009 B2
7578079 Furem Aug 2009 B2
7583659 Matsuhashi Sep 2009 B2
7599691 Mitchell Oct 2009 B1
7602895 Terry et al. Oct 2009 B2
7603433 Paterik Oct 2009 B1
7610619 Kastelewicz Oct 2009 B2
7646296 Ohki Jan 2010 B2
7649877 Vieri et al. Jan 2010 B2
7676368 Shizuka et al. Mar 2010 B2
7676405 Steelberg et al. Mar 2010 B2
7680254 Archer et al. Mar 2010 B2
7689253 Basir Mar 2010 B2
7701331 Tran Apr 2010 B2
7706511 Vieri et al. Apr 2010 B2
7707310 Thubert Apr 2010 B2
7720489 Engelhart, Sr. May 2010 B2
7734023 Bettis et al. Jun 2010 B2
7792053 Chow et al. Sep 2010 B1
7792906 Garcia-Martin et al. Sep 2010 B2
7796538 Chow et al. Sep 2010 B1
7796592 Stafford et al. Sep 2010 B2
7822612 Goodheart Oct 2010 B1
7844286 Sennett Nov 2010 B1
7895631 Stark Feb 2011 B1
7929670 Saleh et al. Apr 2011 B2
7933390 Bedingfield et al. Apr 2011 B2
7957744 Oesterling et al. Jun 2011 B2
7974646 Engelhart, Sr. Jul 2011 B2
7986914 Henry, Jr. Jul 2011 B1
7990964 O'Brien Aug 2011 B2
8015010 Basir Sep 2011 B2
8031644 Ahmavaara Oct 2011 B2
8046414 Kamdar Oct 2011 B2
8064909 Spinelli et al. Nov 2011 B2
8085741 Kiss et al. Dec 2011 B2
8090351 Klein Jan 2012 B2
8103508 Lord Jan 2012 B2
8139739 Wuthnow et al. Mar 2012 B2
8156005 Vieri Apr 2012 B2
8165077 Reddy Apr 2012 B2
8170537 Bort May 2012 B1
8249559 Meiss Aug 2012 B1
8320832 Kang Nov 2012 B2
8325905 Gregorat Dec 2012 B2
8351591 Kirchhoff Jan 2013 B2
8380158 McCulloch Feb 2013 B2
8391925 Khojastepour Mar 2013 B2
8467721 Henry et al. Jun 2013 B2
8504635 Benco Aug 2013 B2
8527013 Guba Sep 2013 B2
8577543 Basir Nov 2013 B2
8634033 Vanderwall Jan 2014 B2
8635069 Van Wagenen Jan 2014 B2
8682987 DeLaCruz Mar 2014 B2
8705527 Addepalli Apr 2014 B1
8718797 Addepalli et al. May 2014 B1
8781442 Link, II Jul 2014 B1
8798094 Wuthnow Aug 2014 B2
8804544 Linkola Aug 2014 B2
8825362 Kirsch Sep 2014 B2
8843066 Chutorash Sep 2014 B2
8843376 Cross, Jr. Sep 2014 B2
8856009 Basir Oct 2014 B2
8880047 Konicek Nov 2014 B2
8928495 Hassib Jan 2015 B2
8930177 Van Wagenen et al. Jan 2015 B2
8930193 Van Wagenen et al. Jan 2015 B2
8983383 Haskin Mar 2015 B1
20010033225 Razavi Oct 2001 A1
20010033639 Martin Oct 2001 A1
20010047260 Walker Nov 2001 A1
20020022453 Balog et al. Feb 2002 A1
20020030605 Roberts, Jr. Mar 2002 A1
20020049535 Rigo Apr 2002 A1
20020072367 Osafune Jun 2002 A1
20020087634 Ogle et al. Jul 2002 A1
20020128000 do Nascimento, Jr. Sep 2002 A1
20020142764 Newell et al. Oct 2002 A1
20030023443 Shizuka Jan 2003 A1
20030036844 Balasuriya Feb 2003 A1
20030050075 Rangarajan et al. Mar 2003 A1
20030059023 Crockett Mar 2003 A1
20030065805 Barnes, Jr. Apr 2003 A1
20030069934 Garcia-Martin Apr 2003 A1
20030076934 Albal et al. Apr 2003 A1
20030147534 Ablay et al. Aug 2003 A1
20030195814 Striemer Oct 2003 A1
20030220835 Barnes, Jr. Nov 2003 A1
20030228002 Tucker Dec 2003 A1
20040029569 Khan et al. Feb 2004 A1
20040030750 Moore et al. Feb 2004 A1
20040093299 Bodin et al. May 2004 A1
20040121729 Herndon et al. Jun 2004 A1
20040128129 Sherman Jul 2004 A1
20040148091 Masclet et al. Jul 2004 A1
20040153667 Kastelewicz Aug 2004 A1
20040185832 Prenzel Sep 2004 A1
20040185842 Spaur et al. Sep 2004 A1
20040190689 Benitez Pelaez et al. Sep 2004 A1
20040193420 Kennewick Sep 2004 A1
20040203634 Wang Oct 2004 A1
20040223599 Bear et al. Nov 2004 A1
20040224710 Koskelainen et al. Nov 2004 A1
20040240650 Bear et al. Dec 2004 A1
20040242198 Oyagi Dec 2004 A1
20040264655 Levine Dec 2004 A1
20040267531 Whynot et al. Dec 2004 A1
20050013419 Pelaez Jan 2005 A1
20050020250 Chaddha Jan 2005 A1
20050021339 Ruetschi Jan 2005 A1
20050038688 Collins Feb 2005 A1
20050038876 Chaudhuri Feb 2005 A1
20050058075 Gorday Mar 2005 A1
20050064883 Heck Mar 2005 A1
20050069101 Bear et al. Mar 2005 A1
20050085221 Sumcad Apr 2005 A1
20050105512 Myhre May 2005 A1
20050111644 Edwards May 2005 A1
20050113113 Reed May 2005 A1
20050136949 Barnes, Jr. Jun 2005 A1
20050141528 Matsuhashi Jun 2005 A1
20050143134 Harwood Jun 2005 A1
20050146445 Sleboda et al. Jul 2005 A1
20050170869 Slemmer et al. Aug 2005 A1
20050201533 Emam Sep 2005 A1
20050210101 Janik Sep 2005 A1
20050213790 Rhoads et al. Sep 2005 A1
20050233742 Karaoguz et al. Oct 2005 A1
20050250475 Slemmer Nov 2005 A1
20050266884 Marriott Dec 2005 A1
20050273330 Johnson Dec 2005 A1
20050282564 Yoo Dec 2005 A1
20050286475 Ahmavaara Dec 2005 A1
20060030298 Burton Feb 2006 A1
20060031364 Hamilton et al. Feb 2006 A1
20060034266 Harris et al. Feb 2006 A1
20060052113 Ophir Mar 2006 A1
20060067499 Oliveira Mar 2006 A1
20060069567 Tischer Mar 2006 A1
20060095331 O'Malley et al. May 2006 A1
20060101116 Rittman May 2006 A1
20060111948 Kivatinetz May 2006 A1
20060120351 Rajagopalan Jun 2006 A1
20060123053 Scannell, Jr. Jun 2006 A1
20060128364 Costa-Requena Jun 2006 A1
20060133582 McCulloch Jun 2006 A1
20060150152 Soini et al. Jul 2006 A1
20060168259 Spilotro et al. Jul 2006 A1
20060184456 de Janasz Aug 2006 A1
20060187900 Akbar Aug 2006 A1
20060187915 Caspi et al. Aug 2006 A1
20060189393 Edery Aug 2006 A1
20060195384 Bauer Aug 2006 A1
20060195540 Hamilton et al. Aug 2006 A1
20060223512 Runge Oct 2006 A1
20060233338 Punaganti Venkata Oct 2006 A1
20060248447 Makkonen Nov 2006 A1
20060251232 Wuthnow Nov 2006 A1
20060256948 Crockett Nov 2006 A1
20060258379 Oesterling Nov 2006 A1
20060258394 Dhillon et al. Nov 2006 A1
20060280165 Blumenschein Dec 2006 A1
20060281447 Lewis et al. Dec 2006 A1
20060286980 Hua Dec 2006 A1
20070024440 Moran Feb 2007 A1
20070027975 Tai Feb 2007 A1
20070032225 Konicek et al. Feb 2007 A1
20070042812 Basir Feb 2007 A1
20070043487 Krzystofczyk Feb 2007 A1
20070043687 Bodart et al. Feb 2007 A1
20070053346 Bettis et al. Mar 2007 A1
20070064743 Bettis et al. Mar 2007 A1
20070078720 Ravikumar Apr 2007 A1
20070082689 Talty et al. Apr 2007 A1
20070106795 Gilfix May 2007 A1
20070110038 Sakata May 2007 A1
20070112571 Thirugnana May 2007 A1
20070116222 Thelen May 2007 A1
20070118426 Barnes, Jr. May 2007 A1
20070123222 Cox May 2007 A1
20070124144 Johnson May 2007 A1
20070129108 Swanburg et al. Jun 2007 A1
20070140195 Kaftan Jun 2007 A1
20070143415 Daigle Jun 2007 A1
20070173266 Barnes, Jr. Jul 2007 A1
20070190944 Doan Aug 2007 A1
20070203735 Ashton Aug 2007 A1
20070203736 Ashton Aug 2007 A1
20070207782 Tran Sep 2007 A1
20070223523 Montpetit et al. Sep 2007 A1
20070239820 Zhong et al. Oct 2007 A1
20070270164 Maier et al. Nov 2007 A1
20070293272 Salmon Dec 2007 A1
20070294425 Sobti et al. Dec 2007 A1
20070299913 Griffin Dec 2007 A1
20080010355 Vieri et al. Jan 2008 A1
20080013712 Gopinath Jan 2008 A1
20080037741 Bear et al. Feb 2008 A1
20080051120 Vieri et al. Feb 2008 A1
20080057925 Ansari Mar 2008 A1
20080086564 Putman et al. Apr 2008 A1
20080090586 Engelhart Apr 2008 A1
20080101552 Khan May 2008 A1
20080109446 Wang May 2008 A1
20080117451 Wang May 2008 A1
20080117839 Raju et al. May 2008 A1
20080132279 Blumenthal Jun 2008 A1
20080140408 Basir Jun 2008 A1
20080155616 Logan et al. Jun 2008 A1
20080158018 Lau Jul 2008 A1
20080160963 Chi et al. Jul 2008 A1
20080161047 Witkowski et al. Jul 2008 A1
20080162637 Adamczyk et al. Jul 2008 A1
20080163372 Wang Jul 2008 A1
20080165767 Kubler et al. Jul 2008 A1
20080171533 Sharp Jul 2008 A1
20080172474 Larsson Jul 2008 A1
20080186927 Alam et al. Aug 2008 A1
20080200143 Qiu et al. Aug 2008 A1
20080205655 Wilkins et al. Aug 2008 A1
20080235024 Goldberg Sep 2008 A1
20080240385 Mikhailov Oct 2008 A1
20080249778 Barton et al. Oct 2008 A1
20080254795 Ratcliffe et al. Oct 2008 A1
20080259884 Nguyen Oct 2008 A1
20080259885 Faulkner et al. Oct 2008 A1
20080272934 Wang et al. Nov 2008 A1
20090006199 Wang Jan 2009 A1
20090006418 O'Malley Jan 2009 A1
20090037962 Benco et al. Feb 2009 A1
20090044006 Shim Feb 2009 A1
20090082928 Witkowski et al. Mar 2009 A1
20090119013 O'Malley May 2009 A1
20090144624 Barnes, Jr. Jun 2009 A1
20090156213 Spinelli et al. Jun 2009 A1
20090161631 Chow et al. Jun 2009 A1
20090198357 Logan et al. Aug 2009 A1
20090298474 George Dec 2009 A1
20090318084 McCarthy et al. Dec 2009 A1
20090318119 Basir Dec 2009 A1
20100011128 Paycher et al. Jan 2010 A1
20100014647 Subramaniam Jan 2010 A1
20100063935 Thomas et al. Mar 2010 A1
20100075640 Helferich Mar 2010 A1
20100076767 Vieri et al. Mar 2010 A1
20100076843 Ashton Mar 2010 A1
20100093320 Ha et al. Apr 2010 A1
20100137037 Basir Jun 2010 A1
20100159968 Ng Jun 2010 A1
20100190485 Engelhart, Sr. Jul 2010 A1
20110227698 Witkowski et al. Sep 2011 A1
20110263197 Henry et al. Oct 2011 A1
20110314169 Van Elburg et al. Dec 2011 A1
20120044908 Spinelli et al. Feb 2012 A1
20120179538 Hines Jul 2012 A1
20120303439 Flitcroft Nov 2012 A1
20130282375 Henry et al. Oct 2013 A1
20140122092 Goldstein May 2014 A1
20150024781 Konicek et al. Jan 2015 A1
Non-Patent Literature Citations (8)
Entry
Office Action mailed Oct. 29, 2009 in U.S. Appl. No. 11/757,170.
Office Action mailed May 11, 2010 in U.S. Appl. No. 11/757,170.
Advisory Action mailed Aug. 19, 2010 in U.S. Appl. No. 11/757,170.
Office Action mailed Nov. 16, 2010 in U.S. Appl. No. 11/757,170.
Notice of Allowance mailed Mar. 18, 2011 in U.S. Appl. No. 11/757,170.
Office Action mailed Apr. 25, 2012 in U.S. Appl. No. 13/175,999.
Office Action mailed Oct. 10, 2012 in U.S. Appl. No. 13/175,999.
Notice of Allowance mailed Feb. 14, 2013 in U.S. Appl. No. 13/175,999.
Related Publications (1)
Number Date Country
20130282375 A1 Oct 2013 US
Continuations (2)
Number Date Country
Parent 13175999 Jul 2011 US
Child 13917996 US
Parent 11757170 Jun 2007 US
Child 13175999 US