This application is related to the following: U.S. Patent Application Publication No. 2010/0076576, published on Mar. 25, 2010, and entitled “Systems, Methods, and Devices for Providing Broadcast Media from a Selected Source”; U.S. Patent Application Publication No. 2010/0075695, published on Mar. 25, 2010, and entitled “Systems, Methods, and Devices for Retrieving Local Broadcast Source Presets”; and U.S. Patent Application Publication No. 2010/0075616, published on Mar. 25, 2010, and entitled “Systems, Methods, and Devices for Associating a Contact Identifier with a Broadcast Source.” The entire contents of the above-referenced application publications are incorporated herein by reference.
This invention relates to media devices having a broadcast radio receiver capable of receiving broadcast media along with broadcast media data and a transceiver capable of requesting and retrieving enhanced media data.
Traditional media devices, e.g., an MP3 player, typically connect with a headset to enable a user to listen to music. Other media devices may include a display that displays videos. Many types of media devices are portable and have compact form factors to enable efficient handling and use by a user. Certain media devices include a radio broadcast receiver capable of receiving amplitude modulated (AM), frequency modulated (FM), or satellite broadcast media. The media can typically include a song, video, news program, or radio show. Certain media devices, e.g., cellular telephones, include wireless transceivers capable of exchanging data with a public land mobile network (PLMN) or wireless data network that may be linked with the Internet or other data networks. Other media devices are capable of interfacing with personal area networks (PAN), wireless local area networks (WLAN), satellite data networks (SAN), and other data networks including, for example, Wi-fi (802.x) networks.
In addition to providing broadcast media (e.g., songs, video, television programs, and radio shows), certain broadcast media sources can supplement the broadcast media with broadcast media data. The broadcast media data can include media metadata (e.g., information about a particular song) or data about the broadcast source (e.g., the name of the broadcasting radio station).
The Radio Data System (RDS) is a communications standard developed by the European Broadcasting Union (EBU) that enables the transmission of small amounts of broadcast media data using FM radio broadcasts. RDS can send various types of broadcast media data including: time, track title, track artist, and station identification. RDS has been used in Europe and South America since the early 1990s.
The Radio Broadcast Data System (RBDS) is the name for the North American version of RDS, and is also often referred to simply as “RDS.” The North American and European versions are nearly identical. Both RDS versions use a 57 kHz sub carrier to carry broadcast media data at 1187.5 bits per second.
One problem with using existing broadcast radio systems is that the broadcast media data is relatively small which limits the amount, quality, and types of media data that can practically be transmitted to a media device. For example, Radio Text (RT) provided by RDS is limited to 64-character text data. Thus, RT media data is typically limited to radio station slogans, song titles, or artist names. RDS cannot support the transmission of significantly larger amounts of enhanced media data for, for example, detailed graphics or video-based data. Accordingly, there is a need to enable a media device to retrieve significantly greater amounts of enhanced media data.
Another problem with existing broadcast radio systems is that the broadcast media data is not specific to a particular target media device. The broadcast provider provides the broadcast media data as, for example, RDS data that is available to all radio receivers. Unfortunately, different radio receivers or different media devices may have different capabilities or features. Also, the user of a particular media device may have a preference for a particular type of media data. Accordingly, there is a need to enable a media device to retrieve certain types of enhanced media data based on the media device's capabilities and/or user's preferences.
The invention, in various embodiments, addresses deficiencies in the prior art by providing systems, methods and devices that enable a media device to retrieve enhanced media data based on broadcast media data received from a broadcast source.
In one aspect, a personal media device includes a broadcast receiver that receives broadcast media and broadcast media data from a broadcast source where the broadcast media data include a media identifier associated with the broadcast media. The personal media device includes a data transceiver that i) sends a retrieval request to a media server for enhanced media data where the retrieval request includes the media identifier and ii) receives the enhanced media data via a wireless data channel. The media device also includes a processor, in communication with the data transceiver, that performs a media device operation in response to the received enhanced media data.
The broadcast receiver may be a FM or AM radio receiver. The media may include a song or music. The broadcast media data may include RDS data. The RDS data may include the media identifier. The media identifier may include a track identifier. The track identifier may include a track title. The track identifier may include a numeric or alpha-numeric identifier. The track identifier may include a unique identifier.
The media may include, without limitation, a video, an image, audio, audio file, multimedia, movie, television data, satellite data, and any like broadcast data. The enhanced media data may include, without limitation, album art, an album image, an album video, song art, a song image, a song video, a ringtone, a ringtone offer, music, a music offer, artist information, artist concert information, artist trivia, song trivia, song-related information, broadcast source information, an advertisement, broadcast source contact information, promotional information, contact links to related information sources, and metadata associated with the media.
The media server may include, without limitation, a clearinghouse server and a broadcast source server. The clearinghouse server may include a database that stores the enhanced media data. The broadcast source server may include a database that stores the enhanced media data.
In one configuration, a media device operation includes, without limitation, displaying an image related to the track identifier, displaying a video related to the track identifier, displaying text related to the track identifier, displaying an advertisement, displaying a ringtone offer, displaying concert information, displaying a music offer, displaying album art, displaying metadata, and displaying a link to related information.
In another aspect, a clearinghouse system includes a data store for storing enhanced media data. The clearinghouse system includes a media server, in communications with the data store, that i) receives a retrieval request from a media device where the retrieval request includes a media identifier, ii) retrieves a portion of the enhanced media data from the data store where the portion of enhanced media data is associated with received media identifier, and iii) sends the portion of enhanced media data associated with the media identifier to the media device.
In a further aspect, an enhanced media data distribution system includes a clearinghouse server that i) assigns a unique media identifier to a media item, ii) stores enhanced media data associated with the media identifier, and iii) sends the enhanced media data to a media device in response to a retrieval request. The distribution system also includes a radio station server that receives the media identifier and a radio station transmitter that broadcasts the media item and associated media identifier.
In one configuration, the media device including a broadcast radio receiver that receives the media item and associated media identifier. The media device also includes a transceiver that sends a retrieval request including the media identifier to the clearinghouse server and receives the enhanced media data associated with the media identifier. The media device further includes a processor that performs a media device operation in response to the received enhanced media data.
The above and other objects and advantages of the present invention will be apparent upon consideration of the following detailed description, taken in conjunction with accompanying drawings, in which like reference characters refer to like parts throughout, and in which:
In one embodiment, the housing 102 includes a first housing portion 104 and a second housing portion 106 that are fastened together and/or to the frame sidewall 122 to encase various components of the media device 100. The housing 102 and its housing portions 104 and 106 may include polymer-based materials that are formed by, for example, injection molding to define the form factor of the media device 100. In one embodiment, the housing 102 surrounds and/or supports internal components such as, for example, a display 108, one or more circuit boards having integrated circuit components, internal radio frequency (RF) circuitry, an internal antenna, a speaker, a microphone, a hard drive, a processor, and other components. Further details regarding certain internal components are discussed herein with respect to
Personal computing devices and/or media devices of this type may include a touchscreen control, such as a Pronto made available by Royal Philips Electronics of the Netherlands or a GPS receiver made available by Garmin International, Inc. of Olathe, Kans. In certain embodiments, the display 108 includes a graphical user interface (GUI) to enable a user to interact with the device 100. The personal computing device 100 may also include an image sensor such as a camera capable of capturing photographic images and/or video images.
Media device 300 may take any form. For example, media device 300 may be a portable media player such as a portable music player. Media device 300 may also include, for example, a mobile telephone that may play downloaded media. Media may be downloaded directly to the media device 300 or may be downloaded to computer 308 and transferred to the media device 300 via communications channel 310.
The media device 300 may include a wireless communications device such as a cellular telephone, satellite telephone, cordless telephone, personal digital assistant (PDA), pager, portable computer, or any other device capable of wireless communications. In fact,
The media device 300 may also be integrated within the packaging of other devices or structures such as a vehicle, video game system, appliance, clothing, helmet, glasses, wearable apparel, stereo system, computer system, entertainment system, or other portable devices. In certain embodiments, the media device 300 may be docked or connected to a wireless (e.g., a wi-fi docking system)and/or radio enabling accessory system (e.g., AM/FM or satellite radio receiver) that provides the media device 300 with short-range communicating functionality and/or radio reception capability. Alternative types of media devices 300 may include, for example, a media player such as an iPod®, iPod® Nano, iPod® Shuffle, or Apple® iphone available by Apple Inc., of Cupertino, Calif., pocket-sized personal computers such as an iPAQ® Pocket PC available by Hewlett Packard Inc., of Palo Alto, Calif. and any other device capable of communicating wirelessly (with or without the aid of a wireless enabling accessory system).
In certain embodiments, the media device 300 may synchronize with, for example, a remote computing system or server, e.g., computer 308, to receive media (using either wireless or wireline communications paths). Wireless syncing enables the media device 300 to transmit and receive media and data without requiring a wired connection. Media may include, without limitation, sound or audio files, music, video, multi-media, and digital data, in streaming and/or discrete (e.g., files and packets) formats.
During synchronization, a host system, e.g., device 308, may provide media to a client system or software application embedded within the media device 300. In certain embodiments, media and/or data is “downloaded” to the media device 300. In other embodiments, the media device 300 is capable of uploading media to a remote host or other client system.
The headset 302 may be utilized to provide an audio functionality associated with media device 300. The headset 302 may include speakers 304 and 306 as well as a microphone.
Storage device 404 may store media (e.g., music and video files), software (e.g., for implanting functions on device 400), preference information (e.g., media playback preferences), lifestyle information (e.g., food preferences), personal information (e.g., information obtained by exercise monitoring equipment), transaction information (e.g., information such as credit card information), word processing information, personal productivity information, wireless connection information (e.g., information that may enable media device to establish wireless communication with another device), subscription information (e.g., information that keeps tracks of podcasts or television shows or other media that a user subscribes to), radio station broadcast source information, and any other suitable data. Storage device 404 may include one more storage mediums, including for example, a hard-drive, permanent memory such as ROM, semi-permanent memory such as RAM, or cache.
Memory 420 may include one or more different types of memory which may be used for performing device functions. For example, memory 420 may include cache, ROM, and/or RAM. Bus 418 may provide a data transfer path for transferring data to, from, or between at least storage device 404, memory 420, and processor 402. Coder/decoder (CODEC) 412 may be included to convert digital audio signals into an analog signals for driving the speaker 424 to produce sound including voice, music, and other like audio. The CODEC 412 may also convert audio inputs from the microphone 426 into digital audio signals. The CODEC 412 may include a video CODEC for processing digital and/or analog video signals.
User interface 406 may allow a user to interact with the media device 400. For example, the user interface 406 can take a variety of forms, such as a button, keypad, dial, a click wheel, or a touch screen. Communications circuitry 422 may include circuitry for wireless communication (e.g., short-range and/or long range communication). For example, the wireless communication circuitry may be Wi-Fi enabling circuitry that permits wireless communication according to one of the 802.1x standards. Other wireless network protocol standards could also be used, either in alternative to the identified protocols or in addition to the identified protocols.
Other network standards may include Bluetooth, the Global System for Mobile Communications (GSM), code division multiple access (CDMA), and long-term evolution (LTE) based wireless protocols. Communications circuitry 422 may also include circuitry that enables the media device 400 to be electrically coupled to another device (e.g., a computer or an accessory device) and communicate with that other device.
In one embodiment, the media device 400 may be a portable computing device dedicated to processing media such as audio and video. For example, the media device 400 may be a media device such as media player (e.g., MP3 player), a game player, a remote controller, a portable communication device, a remote ordering interface, an audio tour player, or other suitable media device. The media device 400 may be battery-operated and highly portable so as to allow a user to listen to music, play games or video, record video or take pictures, communicate with others, and/or control other devices. In addition, the media device 400 may be sized such that it fits relatively easily into a pocket or hand of the user. By being handheld, the media device 400 (or media devices 100, 200, and 300) is relatively small and easily handled and utilized by its user and thus may be taken practically anywhere the user travels.
The media device 400 may employ a location sensor 430 to enable the media device to determine its geographic location in support of location-based services and other services. The location sensor 430 may include a global position system (GPS) receiver. The location sensor 430 may include one or more radio receivers that perform radio doppler and/or triangulation sensing to determine the media device 400 location. In certain embodiments, the location sensor 430 may be integrated with the communications circuitry 422. In one embodiment, the location sensor 430 may include a data decoder such as decoder 434 that decodes a source identifier broadcast by a radio source (e.g., radio station identifier or cellular network system identifier (SID)).
The broadcast radio signal may be, without limitation, frequency modulated (FM) or amplitude modulated (AM). The interfaces 522 and 528 may operate in an AM frequency band of about 500-1500kHz. The interfaces 522 and 528 may operate in an FM and/or television frequency band of about 54-1600 MHz. The interfaces 522 and 528 may operate in any number of frequency bands such as, for example, a satellite frequency band. The radio station 504 may be associated with a radio station server 506 that includes a database 508 for storing media and/or media data. The radio station 524 may be associated with a radio station serve 512 that includes a database 514 for storing media and/or media data.
The PLMNs 530 and 542 may include a cellular telephone network. The PLMNs 530 and 542 may utilize a plurality of cellular radio towers 532, 538, 544, and 548 respectively. The media device 502 may exchange data and other communications with the PLMN 530 and/or 542 via a wireless communications channel 536 and/or 546 respectively. The media device 502 may exchange data and other communications with the AP 540 and/or AP 504 via a wireless communications channel 534 and 550 respectively. The clearinghouse media data server 516 may include a database 518 for storing media and/or media data.
PLMN networks are generally referred to as cellular networks because they employ a frequency re-use architecture in which wireless access channels are grouped into geographically-located cells and sectors. The size of each cell depends on the output power of the network base station (BS) transceiver, e.g., BS 602, associated with each cellular tower 532 and cell. Each access channel uses a certain frequency band in one geographic cell that is re-used in another cell, geographically separated from the first cell, by another access channel where the likelihood of interference is minimized.
These networks also use a centralized switch or server such as the mobile switching center (MSC) 604 to enable a wireless device to move from cell to cell while maintaining a persistent data connection. In the United States, cellular and Personal Communications Service (PCS) networks operate in the licensed commercial 800-900 Mhz and 1900-2100 Mhz ranges. Access data channels, however, may be bandwidth limited to 30 khz, 200 khz, or 1.24 Mhz depending on the wireless air interface standard used.
PLMN networks primarily provide voice communications while also providing relatively low rate data communications (e.g., 9.6-140 kbps). PLMN networks such as the Global System for Mobile Communications (GSM) and cdma2000 provide a Short Message Service (SMS) that enables telephone users to send relatively short, e.g., about 160 bytes, messages to other cellular telephones or to traditional electronic mail (e-mail) accounts within land-based IP networks.
A Short Message Server Center (SMSC) 606 typically coordinates with the MSC 604 to distribute SMS messages to cellular telephones and/or media devices 502. The SMSC may also interface with a wireless data server 608 to send SMS messages with destination addresses, e.g., e-mail addresses, external to the PLMN 600. The SMSC may include a mail server and/or other functionality to convert SMS messages to the proper e-mail format if necessary. Alternatively, the wireless data server may include a mail server such as a POP and/or Exchange server to facilitate the delivery of e-mail messages to and from the PLMN 600.
SMS messages may be transmitted over the air interface 120 via the traffic and/or control channels of the PLMN 600 network. While SMS messages are typically limited to about 160 bytes in length, longer text messages may be sent to or received by a media device 502. This may be performed by breaking a larger message into multiple SMS messages for delivery and then re-assembling the multiple SMS messages into the original message upon receipt. Multimedia message services (MMS) may also be employed having messages that include text, video, pictures, and audio.
Recently, PLMN providers have launched higher bandwidth data networks such as cdma2000 Evolution Data Only (EVDO) networks that provide up to 2 Mbps and Third Generation GSM (3GSM) networks that provide approximately 300 kbps data rates. These higher rate data services may employ point-to-point (PPP), simple IP and/or mobile IP (MIP) protocols to more efficiently interface with traditional IP networks such as network 510 and/or the Internet. The wireless data server 608 may function as a cdma2000 and/or GPRS Packet Data Server Node (PDSN), MIP Home Agent, MIP Foreign agent, wireless data gateway, and like systems to facilitate data communications with an external data network such as the network 510.
Using circuit-switched and/or packet-switched data services, the PLMN 600, 530, and 542 enable a media device 502 to act like a network interface to another data network such as the Internet. Thus, media device 502 may employ any of the applications and features of a standard workstation and/or home personal computer, subject to the processing speed, power, and memory constraints of a compact and mobile device. For example, the media device 502 may utilize a WWW browser employing HTML, WML, XML, and like markup languages to facilitate access to a remote web server, e.g., server 552, 506, 512, and/or 516, via the network 510. The media device 502 may utilize certain applications that enable the exchange of data with remote data servers connected to the network 510. Data may be transported to and from the network 510 via the wireless data server 608. In these instances, the wireless data server 608 exchanges data with the BS 602. The BS 602, in turn, transmits data to and/or receives data from the media device 502 via one or more data traffic channels on the air interface 536 or 546.
The wireless access network 700 includes an AP 540, a wireless LAN (WLAN) 702, router 704, and local area network (LAN) 706. The LAN may be connected to network 510 via one or more data networks. The WLAN 702 may be connected to the PSTN 552 via one or more network interfaces. The AP 540 may connect with one or more media devices 502. WLAN networks, such as WLAN 702, employ wireless APs 540 to communicate with multiple wireless devices, e.g., media device 502, simultaneously via a set of wireless access channels.
While the wireless access network 700 may not support SMS messaging as with the PLMN 600, the wireless access network 700 is capable of supporting relatively high data rate communications between a media device 502 and the network 510. Furthermore, the wireless access network 700 can support higher layer protocols such as TCP/IP, HTTP, and UDP, which enable the use of a web browser and other applications at the media device 502.
Returning to
As discussed previously, a media device 502 may include a broadcast radio receiver, e.g., radio receiver 432, that enables the media device 502 to receive media from a plurality of radio stations, e.g., radio station 504, within its vicinity. The media device 502 may include the capability to enable a user to configure a set of favorite radio stations and/or radio station frequencies so that the user can conveniently tune the broadcast radio receiver 432 to a favorite radio station.
In addition to the radio receiver 432, the media device 502 may include a data transceiver as part of its communications circuitry 422 to facilitate the exchange of data with a PLMN, e.g., PLMN 530, a wireless access network, e.g., via AP 540, or another like wireless data network. In certain embodiments, the media device 502 may utilize a data transceiver to supplement broadcast media and/or media data received from a radio station such as radio stations 504 and 524. In one embodiment, the media device 502 is capable of querying a clearinghouse media data server 516 via a wireless data network (e.g., PLMN or wireless access network) to obtain media and/or media data. A clearinghouse server 516 may include one or more data servers and systems that perform network-based services via, for example, the Internet. One example of a clearinghouse media data server 512 is the iTunes® music downloading service, made available by Apple Inc. of Cupertino, Calif. Media data may include metadata and/or data about or related to media. For example, media data may include an image such as album cover art related to a song. Media data may also include information related to a broadcast source of the media such as the name of a radio station playing a song. In certain embodiments, the media device 502 can retrieve media and/or media data from a radio station server 504 and/or its associated database 508, the clearinghouse server 516 and/or its associated database 518, a remote web server 552, and any other data source in communication with the network 510.
One problem with existing broadcast radio receivers is that the amount of media data broadcast along with the media is relatively limited in size, flexibility, and scope. For example, the RDS system provides a limited amount of information such as a song title, artist name, 64-character text, a station call sign, and other information. However, the available bandwidth is so limited as to prevent the distribution of much richer media data including, for example, a graphic image of album cover art related to a song. The present invention advantageously addresses this problem by enabling a media device 502 to access a data network to supplement the limited broadcast media data and/or obtain enhanced media data associated with the media being broadcast by a broadcast radio source.
The media device 800 may access one or more remote databases such as, without limitation, databases 508, 514, and 518, or other data sources such as server 552, to retrieve the enhanced media data. In certain embodiments, the broadcast media data may include a media identifier associated with a particular media item such as a song. The media identifier may include a unique identifier. The unique identifier may be numeric and/or alpha-numeric. The media identifier may include a track identifier. By employing a media identifier, the media device 800 may query a remote server and/or database to efficiently retrieve enhanced media data that is associated with the media identified by the media identifier.
Persons skilled in the art will appreciate that the various configurations described herein may be combined without departing from the present invention. It will also be recognized that the invention may take many forms other than those disclosed in this specification. Accordingly, it is emphasized that the invention is not limited to the disclosed methods, systems and apparatuses, but is intended to include variations to and modifications thereof which are within the spirit of the following claims.
Number | Name | Date | Kind |
---|---|---|---|
4476582 | Strauss et al. | Oct 1984 | A |
5341350 | Frank et al. | Aug 1994 | A |
5557541 | Schulhof et al. | Sep 1996 | A |
5616876 | Cluts | Apr 1997 | A |
5963916 | Kaplan | Oct 1999 | A |
5983073 | Ditzik | Nov 1999 | A |
6047054 | Bayless et al. | Apr 2000 | A |
6160551 | Naughton et al. | Dec 2000 | A |
6192340 | Abecassis | Feb 2001 | B1 |
6247130 | Fritsch | Jun 2001 | B1 |
6255961 | Van Ryzin et al. | Jul 2001 | B1 |
6259892 | Helferich | Jul 2001 | B1 |
6314094 | Boys | Nov 2001 | B1 |
6338044 | Cook et al. | Jan 2002 | B1 |
6339706 | Tillgren et al. | Jan 2002 | B1 |
6353637 | Mansour et al. | Mar 2002 | B1 |
6401085 | Gershman et al. | Jun 2002 | B1 |
6407750 | Gioscia et al. | Jun 2002 | B1 |
6408332 | Matsumoto et al. | Jun 2002 | B1 |
6418330 | Lee | Jul 2002 | B1 |
6487663 | Jaisimha et al. | Nov 2002 | B1 |
6510210 | Baughan | Jan 2003 | B1 |
6516466 | Jackson | Feb 2003 | B1 |
6526335 | Treyz et al. | Feb 2003 | B1 |
6559773 | Berry | May 2003 | B1 |
6587127 | Leeke et al. | Jul 2003 | B1 |
6609105 | Van Zoest et al. | Aug 2003 | B2 |
6658247 | Saito | Dec 2003 | B1 |
6728531 | Lee et al. | Apr 2004 | B1 |
6772212 | Lau et al. | Aug 2004 | B1 |
6823225 | Sass | Nov 2004 | B1 |
6845398 | Galensky et al. | Jan 2005 | B1 |
6901067 | Kalavade | May 2005 | B1 |
6907112 | Guedalia et al. | Jun 2005 | B1 |
6915272 | Zilliacus et al. | Jul 2005 | B1 |
6917923 | Dimenstein | Jul 2005 | B1 |
7065342 | Rolf | Jun 2006 | B1 |
7110714 | Kay et al. | Sep 2006 | B1 |
7187947 | White et al. | Mar 2007 | B1 |
7339993 | Brooks et al. | Mar 2008 | B1 |
7440772 | White et al. | Oct 2008 | B2 |
7444353 | Chen et al. | Oct 2008 | B1 |
7486926 | White et al. | Feb 2009 | B2 |
7634228 | White et al. | Dec 2009 | B2 |
8543095 | Brown et al. | Sep 2013 | B2 |
20020010759 | Hitson et al. | Jan 2002 | A1 |
20020046084 | Steele et al. | Apr 2002 | A1 |
20020049037 | Christensen et al. | Apr 2002 | A1 |
20020112187 | Dalton, Jr. et al. | Aug 2002 | A1 |
20020164973 | Janik et al. | Nov 2002 | A1 |
20020183059 | Noreen et al. | Dec 2002 | A1 |
20030013425 | Nee | Jan 2003 | A1 |
20040198279 | Anttila et al. | Oct 2004 | A1 |
20040198389 | Alcock et al. | Oct 2004 | A1 |
20050154599 | Kopra et al. | Jul 2005 | A1 |
20050208913 | Raisinghani et al. | Sep 2005 | A1 |
20060105781 | Ueda et al. | May 2006 | A1 |
20060184431 | Rosenberg et al. | Aug 2006 | A1 |
20060184960 | Horton et al. | Aug 2006 | A1 |
20070016922 | Koch | Jan 2007 | A1 |
20070208771 | Platt | Sep 2007 | A1 |
20070232225 | Kikuchi | Oct 2007 | A1 |
20080039037 | Kum | Feb 2008 | A1 |
20080133336 | Altman et al. | Jun 2008 | A1 |
20080139109 | Ewertz | Jun 2008 | A1 |
20080151888 | Ahmed | Jun 2008 | A1 |
20080160940 | Jendbro | Jul 2008 | A1 |
20080162358 | Patsiokas et al. | Jul 2008 | A1 |
20080268772 | Linnamaki et al. | Oct 2008 | A1 |
20080288378 | Berstis et al. | Nov 2008 | A1 |
20090005071 | Forstall et al. | Jan 2009 | A1 |
20090063975 | Bull et al. | Mar 2009 | A1 |
20090070370 | Cunningham et al. | Mar 2009 | A1 |
20090100068 | Gauba et al. | Apr 2009 | A1 |
20090124226 | Nakamura et al. | May 2009 | A1 |
20090125609 | Wood et al. | May 2009 | A1 |
20090158155 | Quinn et al. | Jun 2009 | A1 |
20090186629 | Soelberg et al. | Jul 2009 | A1 |
20090326949 | Douthitt et al. | Dec 2009 | A1 |
20100075593 | Lee et al. | Mar 2010 | A1 |
20100075616 | Haughay, Jr. et al. | Mar 2010 | A1 |
20100075695 | Haughay, Jr. et al. | Mar 2010 | A1 |
20110183603 | Malik | Jul 2011 | A1 |
20120079515 | Wang et al. | Mar 2012 | A1 |
Number | Date | Country |
---|---|---|
0744839 | Nov 1996 | EP |
0898378 | Feb 1999 | EP |
0918408 | May 1999 | EP |
8-006875 | Jan 1996 | JP |
11-164058 | Jun 1999 | JP |
11-242686 | Sep 1999 | JP |
11-317061 | Nov 1999 | JP |
1999-0073234 | Oct 1999 | KR |
WO00-19662 | May 2000 | WO |
0054462 | Sep 2000 | WO |
0070523 | Nov 2000 | WO |
2007144030 | Dec 2007 | WO |
WO2008-080006 | Jul 2008 | WO |
Entry |
---|
Orubeondo, “Trim AirCard 300 Eases Power Demands.” InfoWorld vol. 21, Issue 48, pp. 46 & 50, Nov. 29, 1999. |
“Sierra Wireless Announces First Cellular Network Interface Card for Notebook PCs; The AirCard 300 for Windows Changes the Way Notebook PC Users Make Wireless Connections.” Business Wire, Jun. 21, 1999 (http://findarticles.com/p/articles/mi—m0EIN/is—1999—June—21/ai—54937451/), retrieved Aug. 5, 2009. |
Cellular for Notebook PCs. CIO vol. 13, No. 1, Section 1, p. 90, Oct. 1, 1999. |
“Briefs: Sierra Wireless . . . ” NetworkWorld vol. 16, No. 34, p. 27, Aug. 23, 1999. |
“Specification of the Bluetooth System, vol. 1.” pp. 1-1080, Nov. 29, 1999. |
“Specification of the Bluetooth System, vol. 2.” pp. 1-438, Nov. 29, 1999. |
“Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.0.1 Release 1997)” pp. 1-56, Aug. 1998. |
“Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.1.0 Release 1997)” pp. 1-42, Oct. 1998. |
“Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.2.0 Release 1997)” pp. 1-42, May 1999. |
“Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 6.3.0 Release 1997)” pp. 1-42, Jul. 1999. |
“Digital Cellular Telecommunications System (Phase 2+); General Packet Radio Service (GPRS); Overall Description of the GPRS Radio Interface; Stage 2 (GSM 03.64 version 7.0.0 Release 1997)” pp. 1-41, Jul. 1999. |
Cai et al. “General Packet Radio Service in GSM.” IEEE Communications Magazine, Oct. 1997, pp. 122-131. |
“Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications.” IEEE Std 802.11-1997, pp. 1-445. |
Lind et al. “The Network Vehicle—A Glimpse into the Future of Mobile Multi-Media.” IEEE, pp. I21-1-I21-8, 1998. |
Nokia Quick Guide, Accessories Guide, pp. 1-31, 1999. |
Nokia 9110i User's Manual, pp. 1-190, 1999. |
Qualcomm QCP—1960™, Sprint PCS User Guide, pp. 1-76, Apr. 1999. |
Samsung Model SCH-3500, Sprint PCS User Guide, pp. 1-108, 1999. |
StarTAC, Sprint PCS User Guide, pp. 1-118, Mar. 1999. |
Visteon: for Your Listening Pleasure—Any Music, Any Time, Anwhere (http://www2.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/01-05-2000/0001107812&DATE ), originally retrieved Jan. 5, 2000. |
Pegoraro, “Music Factory; Retailers Struggle to Expand Listening Options Online.” Contra Costa Times, Mar. 19, 2000 Sunday Final Edition, Business Section, p. H01. |
EMusic.com Inc. Prospectus, Sep. 24, 1999, 85 pages. |
Pegoraro, “Logging on; Setting Sound Free From the CD.” The Washington Post, Mar. 3, 2000, Final Edition, Fast Forward Section, p. E01. |
Knudsen, “MP3 Linux Players.” Jul. 1, 1999, http://linuxjournal.com/article/3420, retrieved Jul. 16, 2010. |
Jeffrey, “Net Music Firms to Tap Public Market.” Billboard, Jul. 17, 1999, 2 pages. |
“Digital Download Provider Muscimaker.com Partners With Download Directory Listen.com; Offers Nearly 100,000 Downloadable Tracks Via the Online Directory.” PR Newswire, Financial News Section, Sep. 15, 1999, 3 pages. |
“Myplay, Inc. Launches Consumer Online Music Service; First in Industry to Focus on Ability to Centrally Store Music and Access it Via Multiple Devices; Company Secures Funding from Noted Venture Capital Firms.” PR Newswire, Entertainment, Television, and Culture Section, Oct. 13, 1999, 3 pages. |
“Myplay.com Launches Today; New Online Service Makes Downloading Digital Music Easy for Everyone; Sign Up for Free Virtual Locker Get Bonus Tracks From Artists Including Kid Rock, Chris Rock, Buckcherry. Easy Access to Your Music Collection for Download to Portable Music Players.” PR Newswire, Entertainment, Television, and Culture Section, Oct. 13, 1999, 2 pages. |
RealJukebox Plus Manual, 1999, pp. 1-83. |
RealPlayer™ Plus User Manual, 2000, pp. 1-118. |
RealPlayer Plus™ G2 Manual, 1998, pp. 1-81. |
SoundJam™ MP Digital Audio System User Guide, 1999, pp. 1-50. |
Number | Date | Country | |
---|---|---|---|
20100075593 A1 | Mar 2010 | US |