Wireless multimedia handset
Summary by NHIP
Multi-Band Wireless Handset
The device supports simultaneous operation across two wireless systems using distinct antenna subsets for each. It enables instant hotspot functionality by routing local-area traffic through one antenna group while wide-area traffic uses another.
Claim Score by NHIP
Abstract
A wireless multimedia handset can include one or more of wireless system support, a platform to handset features, and multiple features. The multiple features may include, by way of example but not limitation, multiple-antennae, multimedia storage with advanced search capability, a high fidelity sound system, peer-to-peer networking capability, seamless handoff capability, instant hotspot capability, and ultra low power operation such that the handset is capable of operation without recharging by operating solely on solar cells.

Term
1.4 yearsleft in the term
Expires 24 February 2028, including 450 days of term adjustment.
- Priority
- Filed
- Granted
- Today
- Expires
1 claim: 1 independent, 0 dependent
- 1Broadest claimClaim Score 14, narrow(NHIP)A wireless handset device comprising:a multiple-input multiple-output (MIMO) radio frequency (RF) system including a multi-band radio and a plurality of multi-band antennae, wherein simultaneous operation with a first wireless system and a second wireless system at the same frequency is supported, and further wherein simultaneous operation over different frequencies is supported by the multi-band radio;a plurality of wireless interfaces, wherein, in operation, a first one or more of the wireless interfaces are used to operate in a first wireless system and a second one or more of the wireless interfaces are used to operate in a second wireless system, and wherein operation in the first wireless system and the second wireless system is simultaneous by using a first subset of the plurality of multi-band antennae for the first wireless system and a second subset of the plurality of multi-band antennae for the second wireless system;and wherein further the plurality of wireless interfaces include a wide-area wireless interface and local-area wireless interface, enabling the device to act as an instant hotspot by serving as an access point for local-area wireless network to connect to a wide-area wireless network by using the first subset of multi-band antennae for the local-area wireless network and the second subset of multi-band antennae for the wide-area wireless network;a peer-to-peer networking engine coupled to the wireless interfaces, wherein, in operation, the peer-to peer networking engine uses neighbor discovery and routing to connect to a peer-to-peer wireless network, and wherein the peer-to-peer wireless network is established based on a list of specific devices with which a user wishes to interact;a handoff engine coupled to the wireless interfaces, wherein, in operation, the handoff engine accomplishes seamless wireless handoffs from the first wireless system to the second wireless system by maintaining connections with both the first wireless system and the second wireless system until handoff is complete, wherein the handoff engine facilitates seamless handoff of a voice over IP (VoIP) application between the first wireless system and the second wireless system;and a power management engine to reduce power consumption in the wireless handset by using a power management algorithm, and multi-antennae power optimization, and shutting down non-essential functions and circuits: and an array of microphones, wherein a weight is assigned to each of a plurality of microphone inputs, depending on one or more performance criteria;and wherein a noise cancellation operation is performed based on the weights.
59 paragraphs in 5 sections, as filed
CROSS REFERENCE TO RELATED APPLICATIONS
p-0002This application claims priority to U.S. Provisional Application 60/741,672, entitled Multimedia Cell Platform filed Dec. 1, 2005, which is hereby incorporated by reference in its entirety.
BACKGROUND
p-0003Wireless handsets are common devices used in communication systems such as cell phones, PDAs, and VoIP phones. Such handsets typically include radio technology to access a given wireless system. For example, a cell phone handset must include wireless technology to access one of the cellular system standards, and a VoIP handset must include wireless technology that can access the Internet.
p-0004The foregoing examples of the related art and limitations related therewith are intended to be illustrative and not exclusive. Other limitations of the related art will become apparent to those of skill in the art upon a reading of the specification and a study of the drawings.
SUMMARY
p-0005The following embodiments and aspects thereof are described and illustrated in conjunction with systems, tools, and methods that are meant to be exemplary and illustrative, not limiting in scope. In various embodiments, one or more of the above-described problems have been reduced or eliminated, while other embodiments are directed to other improvements.
p-0006A wireless multimedia handset can include one or more of wireless system support, a platform to handset features, and multiple features. The wireless system support may include support for one or more of Wifi (802.11a/b/g/n), Wimax, 3G cellular, 2G cellular, GSM-EDGE, radio (e.g. AM/FM/XM), 802.15 (Bluetooth, UWB, and Zigbee) and GPS. The platform to handset features may include providing a platform such that common handset applications (such as a camera capability) as well as third party applications (such as gaming) can access one or more handset features. The multiple features may include, by way of example but not limitation, multiple-antennae, multimedia storage with advanced search capability, a high fidelity sound system, peer-to-peer networking capability, seamless handoff capability, instant hotspot capability, and ultra low power operation such that the handset is capable of operation without recharging by operating solely on solar cells.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0007Embodiments of the inventions are illustrated in the figures. However, the embodiments and figures are illustrative rather than limiting; they provide examples of the invention.
p-0008<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an example of a multimedia handset device that has ultra-low power requirements.
p-0009<figref idrefs="DRAWINGS">FIG. 2</figref> depicts examples of subsystems of a multimedia handset device.
p-0010<figref idrefs="DRAWINGS">FIG. 3</figref> depicts a conceptual diagram of a handset.
p-0011<figref idrefs="DRAWINGS">FIG. 4</figref> depicts a flowchart of an example of a method for operating a handset with speech recognition capabilities.
p-0012<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an example of a microphone array system <b>500</b> for a handset.
p-0013<figref idrefs="DRAWINGS">FIG. 6</figref> depicts an example of steering a microphone array towards a person that is speaking or towards multiple people speaking.
p-0014<figref idrefs="DRAWINGS">FIG. 7</figref> depicts a flowchart of an example of a method for locating a file or set of files.
p-0015<figref idrefs="DRAWINGS">FIG. 8</figref> depicts an example of details of a power management algorithm embodied in a computer-readable medium.
p-0016<figref idrefs="DRAWINGS">FIG. 9</figref> depicts a conceptual diagram of seamless handoff of a VoIP call between a cellular and Wifi system.
p-0017<figref idrefs="DRAWINGS">FIG. 10</figref> depicts peer-to-peer networking to establish direct or multihop connections with other wireless devices for real-time interaction and file exchange.
p-0018<figref idrefs="DRAWINGS">FIG. 11</figref> depicts a flowchart of an example of a method for neighbor discovery and joining a peer-to-peer network.
p-0019<figref idrefs="DRAWINGS">FIG. 12</figref> depicts a system that includes simultaneous operation over different frequencies.
DETAILED DESCRIPTION
p-0020In the following description, several specific details are presented to provide a thorough understanding of embodiments of the invention. One skilled in the relevant art will recognize, however, that the invention can be practiced without one or more of the specific details, or in combination with other components, etc. In other instances, well-known implementations or operations are not shown or described in detail to avoid obscuring aspects of various embodiments, of the invention.
p-0021<figref idrefs="DRAWINGS">FIG. 1</figref> depicts an example of a multimedia handset device <b>100</b> that has ultra-low power requirements. The device may be used in any applicable known or convenient wireless network, and may be used in conjunction with a wireless server, such as the wireless server described in U.S. application Ser. No. 11/607,815, filed concurrently herewith entitled WIRELESS MEDIA SERVER SYSTEM AND METHOD by Rezvani et al., and which is incorporated by reference. In the example of <figref idrefs="DRAWINGS">FIG. 1</figref>, the device <b>100</b> includes a peer-to-peer networking and handoff engine <b>102</b>, a user interface <b>104</b>, applications <b>106</b>, a power management engine <b>108</b>, an audio subsystem <b>110</b>, a VoiP module <b>112</b>, a GPS AM/FM/XM radio module <b>114</b>, a GSM/EDGE/3G and/or Wimax module <b>116</b>, a Wifi (802.11a/b/g/n) module <b>118</b>, an 802.15 (Bluetooth, Zigbee, UWB) module <b>120</b>, and an antennae algorithms module <b>122</b>. The user interface <b>104</b> includes a control pad or thumbwheel <b>124</b>, audio I/O <b>126</b>, and a display <b>128</b>. The audio subsystem <b>110</b> includes a microphone array processing engine <b>130</b>, a speech recognition engine <b>132</b>, a noise cancellation engine <b>134</b>, and an MP3 engine <b>136</b>.
p-0022In the example of <figref idrefs="DRAWINGS">FIG. 1</figref>, multiple wireless systems may be integrated into the device, including various cellular phone standards (3G/2G/GSM/Edge), different Wifi standards (802.11a/b/g/n), Wimax, 802.15 (Bluetooth, Zigbee, and/or UWB), and GPS. In an embodiment, the handset <b>100</b> has the capability to support Voice over IP (VoIP) through any of the interfaces that allow it to connect to the Internet. In addition, the handset <b>100</b> will have a peer-to-peer networking capability that will allow any handset within range of other wireless devices to self-configure with them into a multihop network. In an embodiment, seamless handoff of a given application (e.g. VoIP or music streaming) between different wireless interfaces is also supported.
p-0023In general, the handset <b>100</b> could be implemented as any device capable of receiving and using content. For example, the handset could include, by way of example but not limitation, a PDA, cell phone, smart phone, etc. Content may include audio files, multimedia files, software applications, or any other content that is capable of playback at a device. Strictly speaking, any given handset may not be able to play content, though for the purposes of this application, which is regarding handsets, content is assumed to be playable on the handset.
p-0024In an embodiment, the handset <b>100</b> can include one or more of multiple features such as multimedia storage with advanced search capability, a high fidelity sound system, peer-to-peer networking capability, and ultra low power operation such that the device is capable of operation without recharging by operating solely on solar cells. The handset can also support one or more wireless systems and provide a platform such that common handset applications (such as a camera capability) as well as third party applications (such as gaming) can access the device features.
p-0025As used herein, algorithmic descriptions within a computer memory are believed to most effectively convey the techniques to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of operations leading to a desired result. The operations are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.
p-0026It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
p-0027The algorithms and displays presented herein are not inherently related to any particular computer architecture. The techniques may be implemented using any known or convenient programming language, whether high level (e.g., C/C++) or low level (e.g., assembly language), and whether interpreted (e.g., Perl), compiled (e.g., C/C++), or Just-In-Time (JIT) compiled from bytecode (e.g., Java). Any known or convenient computer, regardless of architecture, should be capable of executing machine code compiled or otherwise assembled from any language into machine code that is compatible with the computer's architecture, including that of embedded systems, if applicable.
p-0028<figref idrefs="DRAWINGS">FIG. 2</figref> depicts examples of subsystems of a multimedia handset device <b>200</b>. In the example of <figref idrefs="DRAWINGS">FIG. 2</figref>, the device <b>200</b> includes a display <b>202</b>, a microprocessor <b>204</b>, memory <b>206</b>, a power module <b>208</b>, a keypad <b>210</b>, a baseband processor <b>212</b>, a SIM <b>214</b>, an audio module <b>216</b>, a multiple-input multiple-output (MIMO) radio frequency (RF) system <b>218</b>, and an antenna interface <b>220</b>. The power module <b>208</b> includes a battery/charger <b>222</b>, solar cells <b>224</b>, a power management engine <b>226</b>, and power supplies <b>228</b>. The audio module <b>216</b> includes a microphone array <b>230</b>, a speaker <b>232</b>, and a receiver <b>234</b>.
p-0029An antenna or array of antennae is used as part of the wireless system or subsystems; signals received from this antenna array are processed by an RF signaling block and a baseband block; power is supplied via DC power and/or through solar cell recharging; the device has memory and a USB interface; the user interface is via a display, keypad (or thumbwheel), and audio input/output from a microphone array.
p-0030<figref idrefs="DRAWINGS">FIG. 3</figref> depicts a conceptual diagram of a handset <b>300</b>. A front side <b>302</b> of the handset <b>300</b> includes a control pad <b>306</b>. A back side <b>304</b> of the handset <b>300</b> includes solar cells <b>308</b> and a speaker <b>310</b>. The solar cells can charge the battery from ambient light as well as solar light. Inside the device are the electronics for supporting the handset features (e.g. RF, analog, mixed-signal, and digital electronic circuitry, microprocessors, antennas, etc.). The user interface to the device may be through speech recognition of commands, through a control pad, and/or through another type of interface such as a thumbwheel for menu navigation.
p-0031<figref idrefs="DRAWINGS">FIG. 4</figref> depicts an example of a system <b>400</b> for providing speech recognition capabilities to a handset. In the example of <figref idrefs="DRAWINGS">FIG. 4</figref>, the system <b>400</b> includes a language model <b>402</b>. The language may include, by way of example but not limitation, a set of hidden Markov models (HMMs) for speech data. The language model may be enhanced through language training. For example, a one-time-per-language training could be used for 500 common words. Any known or convenient technique may be implemented for the purposes of initial (or later) language training. In addition to language training, user input can be used to augment the language model <b>402</b>. For example, a user could enter specific vocabulary, such as proper names, either one at a time, or captured as a user enters commands or speaks to a voice application.
p-0032In the example of <figref idrefs="DRAWINGS">FIG. 4</figref>, the system <b>400</b> includes a speech recognizer (HMM) <b>404</b>. The speech recognizer may embody on a computer-readable medium a speech recognition algorithm that uses the HMMs. The speech recognizer <b>404</b> will take as input a user's speech. In an embodiment, the speech recognizer <b>404</b> is designed and/or configured such that wireless interfaces and/or peer-to-peer networking capability can be used to provide additional input to the algorithm. Specifically, the speech recognizer <b>404</b> has the ability to use any of the available wireless interfaces and/or the peer-to-peer network to connect to another device such as a laptop, computer, or another handset to expand the vocabulary base, provide translation assistance, or access a more powerful speech recognition algorithm or set of HMMs.
p-0033In the example of <figref idrefs="DRAWINGS">FIG. 4</figref>, the speech recognizer <b>404</b> is coupled to a DSP frontend for feature extraction <b>406</b>, which receives an acoustic signal as input. Noise cancellation and beamforming algorithms can be designed relative to the speech recognition algorithm such that the feature extraction of the input speech is optimized (note that noise cancellation/beamforming algorithms designed independent of the speech recognition algorithms can degrade speech recognition performance by introducing undesired speech artifacts).
p-0034In the example of <figref idrefs="DRAWINGS">FIG. 4</figref>, the speech recognizer <b>404</b> is coupled to a dictionary translation assistance engine <b>408</b> via a wireless interface. Since a handset may not have as much power or storage as a laptop, if a laptop is nearby, it can be used to provide translation assistance. Any appropriately configured known or convenient device capable of communicating with the speech recognizer <b>404</b> should be able to provide dictionary translation assistance.
p-0035In the example of <figref idrefs="DRAWINGS">FIG. 4</figref>, the speech recognizer <b>404</b> may categorize recognized speech as either a command (e.g. dial a specific number) or a query (e.g. look for a particular content file). Both commands are provided to an index engine <b>410</b>. The index engine <b>410</b> may also make use of metadata, such as metadata that is extracted from, by way of example but not limitation, music files, video files, game files, contact info, and the like, or metadata that is entered by a user, such as personal photos. For commands the index engine <b>410</b> may or may not use the metadata to determine an appropriate course of action, then take the appropriate action to satisfy the command. For queries the index engine <b>410</b> may or may not use the metadata to generate search criteria that is (hopefully) sufficient to enable a search engine <b>412</b> to locate a desired content file, then take the appropriate action (such as playing the content file).
p-0036<figref idrefs="DRAWINGS">FIG. 5</figref> depicts an example of a microphone array system <b>500</b> for a handset. The handset will feature a high fidelity sound system for picking up voice signals by utilizing a microphone array coupled with a noise cancellation algorithm embodied in a computer-readable medium. In an embodiment, a microphone array <b>502</b> includes one ambient noise microphone <b>504</b> located on a part of the handset optimized for it to pick up background ambient noise, as well as additional microphone elements <b>506</b>-<b>1</b> to <b>506</b>-N (referred to collectively as microphone elements <b>506</b>) in different locations on the handset. Echo cancellation <b>508</b> is used for signals transmitted from the handset to remove echo effects. In an embodiment, antenna elements <b>510</b>-<b>1</b> to <b>510</b>-N (referred to collectively as antenna elements <b>510</b>) in the microphone array <b>502</b> have weights assigned to each antenna input. Different algorithms can be used to determine the weights, depending on the performance criteria, the number of antenna elements available and their nature, and the algorithm complexity. For example, the weights may be used to minimize ambient noise, to make the antenna array gain independent of frequency, to minimize the expected mean square distortion or error of the signal, or to steer the direction of the microphone array towards a person that is speaking or towards multiple people speaking, as shown in <figref idrefs="DRAWINGS">FIG. 6</figref>.
p-0037In an embodiment, the handset includes nonvolatile storage for multimedia data files, for example through a Flash RAM. There are many methods by which the multimedia data files may be loaded into the handset memory, for example via a wireless connection to the Internet, via a cellular telephone connection, via a satellite (e.g. XM or Sirius) or AM/FM radio receiver, via a USB high-speed data port, or via a wired or wireless connection to another device (e.g. a wireless connection to a computer, music server, video server, or digital camera). The library may be partitioned by media type, for example there may be one partition of the memory for photos, one for video clips, one for music, one for phone numbers, etc. File storage will include the capability to add “tags” to files. The tagging is done to facilitate searching based on tags that the user selects for each media type. For example, a music file might have a tag or tags such as file title, song title, artist, keywords, genre, album name, music sample or clip, etc. A video file might have a tag such as file title, video title, date, subject, location, artist, etc. A photo file might have a tag such as picture title, date, subject, location, etc.
p-0038In an embodiment, the handset includes intelligent software for searching multimedia files stored on the handset based on multiple search criteria and by the type of file of interest. Alternatively, a user can set up certain tags for all pictures taken under the given tagging criterion. For example, when using a cell phone with a camera, the user may define a certain tag or set of tags for all pictures being taken (e.g. “kids”, “spouse”, “vacation to Europe 2006”, etc.). The user need only enter this tag or set of tags once, and then change the tag or tags when a change is desired. When the picture is taken, the image will be stored in the memory of the handset with the associated tags attached to the file. Then, after this tagging process is set up, the user can tag all pictures without any additional manual inputs (e.g. typing or thumbwheel inputs). This is particularly useful for a handset since it is relatively hard to do manual entry for each new file on a small-sized device. The same concept can also used for tagging and searching for music on the handset, where a set of tags can be assigned to all music downloaded.
p-0039In an embodiment, a search engine (SE) may implement a search algorithm that has been embodied in a computer-readable medium. The algorithm may include a multistep process to locate a file or set of files of interest. This generalized search engine may re-use a number of similar functions for different kind of searches such as speech recognition, image recognition, and music recognition. The SE interacts with the user through the user interface, which for example can be a control pad, thumbwheel, or via voice. In the case of voice commands, the handset synthesizes a voice signal to query the user, and the user's voice commands are processed by a voice recognition engine and then sent to the SE. The noise cancellation and beamforming capabilities of the microphone array, shown in <figref idrefs="DRAWINGS">FIG. 5</figref>, can be combined with a speech recognition engine to improve its performance.
p-0040<figref idrefs="DRAWINGS">FIG. 7</figref> depicts a flowchart <b>700</b> of an example of a method for locating a file or set of files. This method and other methods are depicted as serially arranged modules. However, modules of the methods may be reordered, or arranged for parallel execution as appropriate. In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, a user first initiates a search by sending a command to the SE. The SE then queries the user as to what type of media is desired from a given list of types, which may include video, music, photos, etc. Determining the type of media requested will narrow the search space to a particular partition of the multimedia storage library. Once the file type is identified, the SE will have a set of search criteria associated with that type. The search engine can utilize the tags users input to label the files as well as other data associated with the files. For example, a search for a music file may be by user tag or tag fragment, file title, song title, album name, artist name, keywords, lyrics, a hummed tune, popularity, similarity to other music, genre, etc.
p-0041In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> begins at module <b>702</b> where a user inputs a request to initiate a search for one or more files. In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to module <b>704</b> where a search engine queries the user for a desired file type. In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to module <b>706</b> where the user inputs the type of file(s) desired. In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to module <b>708</b> where the search engine queries the user for search term(s) associated with the desired file type(s). In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to module <b>710</b> where the search engine scans a library for files matching the file type(s) and search term(s).
p-0042In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to decision point <b>712</b> where it is determined whether there are more than one matches. If not (<b>712</b>-N), then the flowchart <b>700</b> continues to module <b>714</b> where the search engine asks the user whether the search term(s) are to be changed. In the example of <figref idrefs="DRAWINGS">FIG. 7</figref>, the flowchart <b>700</b> continues to decision point <b>716</b> where it is determined whether the search term(s) is/are to be changed. If so (<b>716</b>-Y), then the flowchart <b>700</b> continues from module <b>710</b> as described previously. If not (<b>716</b>-N), then the flowchart <b>700</b> continues to module <b>718</b> where the search terminates and the flowchart <b>700</b> ends.
p-0043Returning once again to decision point <b>712</b>, if it is determined that there are more than one matches (<b>712</b>-Y), then the flowchart <b>700</b> continues to decision point <b>720</b> where it is determined whether there is more than one match. If not (<b>720</b>-N), then the flowchart <b>700</b> continues to module <b>722</b> where the matching file is sent over an appropriate user interface on the handset and the flowchart <b>700</b> ends. If, on the other hand, it is determined that there are more than one matches (<b>720</b>-Y), then the flowchart <b>700</b> continues to decision point <b>724</b> where it is determined whether the user requested more than one file. If so (<b>724</b>-Y), then the flowchart <b>700</b> continues to module <b>726</b> where the matching files are sent over an appropriate user interface on the handset, and the flowchart ends. If not (<b>724</b>-N), then the flowchart <b>700</b> continues from module <b>714</b> as described previously.
p-0044As shown in the example of <figref idrefs="DRAWINGS">FIG. 2</figref>, the handset has a power management algorithm, embodied in a computer-readable medium, that minimizes power consumption based on the usage of the handset. <figref idrefs="DRAWINGS">FIG. 8</figref> depicts an example of details of a power management algorithm embodied in a computer-readable medium. As shown in <figref idrefs="DRAWINGS">FIG. 8</figref>, components of the power management algorithm include managing power consumption associated with display, audio, memory, DSP, and/or processors to be minimized while supporting the applications in use; utilizing multiple antennas (MIMO) in the most efficient way to minimize the power consumption required for wireless transmission; shutting down certain nonessential device functionality, and turning off nonessential device circuitry.
p-0045In an embodiment, the handset is designed such that a certain application or set of applications that require relatively low power can be maintained for an indefinite time period under solar power alone, e.g., solar cells embedded in the device and aggressive power management will allow the device to support the given application(s) indefinitely without recharging by shutting down all nonessential functions except those associated with the specific application or applications. For example, the device may operate indefinitely without recharging in Wifi-only mode by shutting down all functions in the device (e.g. certain display features, memory access, audio processing, noise cancellation, and search algorithms) not associated with maintaining a low-rate Wifi connection to the Internet through one or more interfaces that support this connection (e.g. 802.11a/b/g/n); in voice-only mode the device may operate indefinitely without recharging by shutting down all functionality of the device not associated with making a voice call (e.g. certain display features, memory access, audio processing, noise cancellation, and search algorithms) through one or more interfaces that support such calls (e.g. 2G, 3G, GSM, VoIP over Wifi), etc.
p-0046In an embodiment, the handset supports simultaneous operation on the different wireless interfaces, i.e. simultaneous operation on at least two systems that may include Wifi (802.11a/b/g/n), Wimax, 3G cellular, 2G cellular, GSM-EDGE, radio (e.g. AM/FM/XM), 802.15 (Bluetooth, UWB, and Zigbee) and GPS. These systems often operate at different frequencies. Simultaneous operation over the same or different frequencies can be done, for example, by using some set of antennas for one system and using another set of antennas for another system. This is illustrated in <figref idrefs="DRAWINGS">FIG. 9</figref> for simultaneous operation over a cellular system and a Wifi system. Another mechanism to support this simultaneous multifrequency operation is time division. In addition to simultaneous operation, the handset can support seamless handoff between two systems. For example, the handset could switch a VoIP call from a wide-area wireless network such as Wimax or 3G to a local area network such as Wifi. <figref idrefs="DRAWINGS">FIG. 9</figref> depicts a conceptual diagram of seamless handoff of a VoIP call between a cellular and Wifi system.
p-0047<figref idrefs="DRAWINGS">FIG. 10</figref> depicts peer-to-peer networking to establish direct or multihop connections with other wireless devices for real-time interaction and file exchange. A peer-to-peer networking protocol can make use of all wireless interfaces that can establish a direct connection with other wireless devices. For example, it could use an 802.11a/b/g/n interface operating in peer-to-peer mode, an 802.15 interface, a proprietary peer-to-peer radio interface, and/or an infrared communication link. The user may select to establish peer-to-peer networks on all available interfaces simultaneously, on a subset of interfaces, or on a single interface based on a prioritized list of possible interfaces.
p-0048Alternatively, a peer-to-peer network may be established based on a list or set of lists of specific devices or user IDs that the user wishes to interact with. For example, a user may set up a list of gaming partners (or multiple lists, each associated with a different game or partner preferences), such that whenever a device or user associated with one of those partners is in range of the handset, the handset will establish a peer-to-peer connection with it on any interface that the two devices have in common. The lists could be exchanged between devices to establish a union of lists, so that if User A and User B are connected, and User C is on User A's gaming list but comes in range of User B, then User C will join the peer-to-peer gaming network.
p-0049There are two main components to the peer-to-peer networking protocol: neighbor discovery and routing. In neighbor discovery a handset determines which other devices it can establish a direct connection with. This may be done, for example, by setting aside a given control channel for neighbor discovery, where nodes that are already in the peer-to-peer network listen on the control channel for new nodes beginning the process of neighbor discovery.
p-0050<figref idrefs="DRAWINGS">FIG. 11</figref> depicts a flowchart <b>1100</b> of an example of a method for neighbor discovery and joining a peer-to-peer network. When a node first begins the process of neighbor discovery, it broadcasts a beacon identifying itself over a control channel set up for this purpose. Established nodes on the network periodically listen on the control channel for new nodes. If an established node on the network hears a broadcast beacon, it will establish a connection with the broadcasting node. The existing node will exchange information with the new node about the existing network to which it belongs, e.g. it may exchange the routing table it has for other nodes in the network with the new node. The neighboring node will also inform other nodes on the network about the existence of the new node, and that it can be reached via the neighboring node, e.g. by exchanging updated routing tables with the other nodes. At that point the new node becomes part of the network and activates the routing protocol to communicate with all nodes in the network.
p-0051In the example of <figref idrefs="DRAWINGS">FIG. 11</figref>, the flowchart <b>1100</b> starts at module <b>1102</b> where a new node broadcasts a request to join a peer-to-peer network. In the example of <figref idrefs="DRAWINGS">FIG. 11</figref>, the flowchart <b>1100</b> continues to decision point <b>1104</b> where it is determined whether a neighboring node hears the request to join. If it is determined that the request is not heard (<b>1104</b>-N), then the flowchart continues to module <b>1106</b> where the new node tries a different interface and/or waits for an implementation-specific amount of time before trying again, then the flowchart <b>1100</b> continues from <b>1102</b> as described previously. If, on the other hand, it is determined that a neighboring node hears the request to join (<b>1104</b>-Y), then the flowchart <b>1100</b> continues to module <b>1108</b>, where a neighboring node establishes a connection with the new node.
p-0052In the example of <figref idrefs="DRAWINGS">FIG. 11</figref>, the flowchart <b>1100</b> continues to module <b>1110</b> where the neighboring node exchanges information about the existing network with the new node. For example, the neighboring node may give the new node some or all of its routing table. In the example of <figref idrefs="DRAWINGS">FIG. 11</figref>, the flowchart <b>1100</b> continues to module <b>1112</b> where the neighboring node informs other nodes on the peer-to-peer network about the new node. In the example of <figref idrefs="DRAWINGS">FIG. 11</figref>, the flowchart <b>1100</b> continues to module <b>1114</b> where the new node becomes a part of the established network and enables routing to other nodes of the peer-to-peer network.
p-0053In an embodiment, a routing protocol will take advantage of link layer flexibility in establishing and utilizing single and multihop routes between nodes with the best possible end-to-end performance. The routing protocol will typically be based on least-cost end-to-end routing by assigning costs for each link used in an end-to-end route and computing the total cost based on these link costs. The cost function is designed to optimize end-to-end performance. For example, it may take into account the data rates, throughput, and/or delay associated with a given link in coming up with a cost of using that link. It may also adjust link layer parameters such as constellation size, code rate, transmit power, use of multiple antennas, etc., to reduce the cost of a link and thereby the cost of an end-to-end route.
p-0054In addition, for nodes with multiple antennas, multiple independent paths can be established between these nodes, and these independent paths can comprise separate links over which a link cost is computed. The routing protocol can also include multiple priorities associated with routing of each data packet depending on data priority, delay constraints, user priority, etc.
p-0055When the wireless interfaces in the handset include wide-area wireless nework technology such as cellular (e.g. GSM, EDGE, 3G) or Wimax as well as a local-area wireless network technology such as Wifi (e.g. 802.11a/b/g/n), the handset will have the capability to act as an instant hotspot by serving as an access point for the Wifi network to connect it to the wide-area wireless network backbone. Specifically, it can use one interface to connect to the wide-area network and another interface to connect to the local area network in the capacity of an access point for other Wifi devices. The wide-area network and local-area network will typically operate on different frequencies. The handset therefore must support simultaneous operation over different frequencies.
p-0056<figref idrefs="DRAWINGS">FIG. 12</figref> depicts a system <b>1200</b> that includes simultaneous operation over the same or different frequencies. This can be accomplished by, for example, using some set of antennas for the wide-area network and using another set of antennas for the local-area network. In the example of <figref idrefs="DRAWINGS">FIG. 12</figref>, the wide-area network is cellular and the local-area network is Wifi. Another mechanism to support simultaneous multifrequency operation is to have a multiband radio combined with multiband antennas. Yet another mechanism that may be used to support simultaneous operation is time-division.
p-0057The handset may be developed as an open architecture so that third party applications can utilize the handset capabilities of high-fidelity sound, large memory, advanced searching capabilities, peer-to-peer networking, and multiple wireless connections. The architecture of the handset may enable this by providing the appropriate subsystem and software interfaces.
p-0058As used herein, the term “embodiment” means an embodiment that serves to illustrate by way of example but not limitation.
p-0059It may be noted that in examples of content that include only music files, the music files are streamed. However, in alternative embodiments, music files could be downloaded and then played. The advantage of streaming is that a playback device can begin to play a music file before the music file has been received in its entirety. The same is true for multimedia streaming and software streaming.
p-0060It will be appreciated to those skilled in the art that the preceding examples and embodiments are exemplary and not limiting to the scope of the present invention. It is intended that all permutations, enhancements, equivalents, and improvements thereto that are apparent to those skilled in the art upon a reading of the specification and a study of the drawings are included within the true spirit and scope of the present invention. It is therefore intended that the following appended claims include all such modifications, permutations and equivalents as fall within the true spirit and scope of the present invention.
Contents5
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US9860813B2 | Cited by | United States of America | Applicant |
| US2011018083A1 | Cited by | United States of America | Pre-grant |
| US9761958B2 | Cited by | United States of America | Applicant |
| US9215745B1 | Cited by | United States of America | Applicant |
| US9794801B1 | Cited by | United States of America | Applicant |
| US8995459B1 | Cited by | United States of America | Applicant |
| US9142873B1 | Cited by | United States of America | Search report |
| US9197482B1 | Cited by | United States of America | Applicant |
| US9215754B2 | Cited by | United States of America | Applicant |
| US11381903B2 | Cited by | United States of America | Applicant |
| US9025581B2 | Cited by | United States of America | Applicant |
| US2012300682A1 | Cited by | United States of America | Pre-grant |
| US8787309B1 | Cited by | United States of America | Applicant |
| US10225764B2 | Cited by | United States of America | Applicant |
| US9083782B2 | Cited by | United States of America | Applicant |
| US9431702B2 | Cited by | United States of America | Search report |
| US8532700B2 | Cited by | United States of America | Search report |
| US8867744B1 | Cited by | United States of America | Applicant |
| US9930595B2 | Cited by | United States of America | Applicant |
| US8769176B1 | Cited by | United States of America | Search report |
| US10327186B2 | Cited by | United States of America | Applicant |
| US2011130167A1 | Cited by | United States of America | Pre-grant |
| US12225344B2 | Cited by | United States of America | Applicant |
| US9185618B1 | Cited by | United States of America | Applicant |
| US9184791B2 | Cited by | United States of America | Applicant |
| US10278105B2 | Cited by | United States of America | Applicant |
| DE102004026223A1 | Cites | Germany | Search report |
| US2001049262A1 | Cites | United States of America | Applicant |
| US2001051996A1 | Cites | United States of America | Applicant |
| US2002102950A1 | Cites | United States of America | Applicant |
| US2003023427A1 | Cites | United States of America | Applicant |
| US2004125776A1 | Cites | United States of America | Search report |
| US2005070225A1 | Cites | United States of America | Applicant |
| US2005090295A1 | Cites | United States of America | Applicant |
| US2005094592A1 | Cites | United States of America | Search report |
| US2005123004A1 | Cites | United States of America | Applicant |
| US2005130717A1 | Cites | United States of America | Applicant |
| US2005176466A1 | Cites | United States of America | Applicant |
| US2005226166A1 | Cites | United States of America | Applicant |
| US2005239498A1 | Cites | United States of America | Search report |
| JP2005348367A | Cites | Japan | Search report |
| US2006010272A1 | Cites | United States of America | Search report |
| US2006084439A1 | Cites | United States of America | Search report |
| US2006084469A1 | Cites | United States of America | Search report |
| US2006095331A1 | Cites | United States of America | Applicant |
| US2006103590A1 | Cites | United States of America | Applicant |
| US2006154699A1 | Cites | United States of America | Search report |
| US2006166674A1 | Cites | United States of America | Applicant |
| US2006193295A1 | Cites | United States of America | Search report |
| US2006193296A1 | Cites | United States of America | Search report |
| US2006268787A1 | Cites | United States of America | Applicant |
| US2007026853A1 | Cites | United States of America | Search report |
| US2007211703A1 | Cites | United States of America | Search report |
| US2007268190A1 | Cites | United States of America | Search report |
| US2008037477A1 | Cites | United States of America | Applicant |
| US2008043868A1 | Cites | United States of America | Search report |
| US2008201138A1 | Cites | United States of America | Applicant |
| US2008298450A1 | Cites | United States of America | Search report |
| US2009061879A9 | Cites | United States of America | Applicant |
| US2009091502A1 | Cites | United States of America | Search report |
| US6295453B1 | Cites | United States of America | Applicant |
| US6423892B1 | Cites | United States of America | Applicant |
| US6546264B1 | Cites | United States of America | Applicant |
| US6803511B2 | Cites | United States of America | Applicant |
| US6849794B1 | Cites | United States of America | Applicant |
| US6859436B2 | Cites | United States of America | Applicant |
| US6859463B1 | Cites | United States of America | Search report |
| US7130282B2 | Cites | United States of America | Applicant |
| US7130608B2 | Cites | United States of America | Applicant |
| US7342835B2 | Cites | United States of America | Search report |
| US7343173B2 | Cites | United States of America | Search report |
| US7512414B2 | Cites | United States of America | Applicant |
| US7515929B2 | Cites | United States of America | Search report |
| N. Ishikawa, T. Kato, H. Sumino, S. Murakami, J. Hjelm, "Jupiter: Peer-to-Peer Networking Platform over Heterogeneous Networks", Systemics, Cybernetics and Informatics, vol. 4, No. 5, pp. 55-61, Sep./Oct. 2006. | Non-patent | – | Search report |
| "WiMAX: The Business Case", 2004 WiMAX Forum. | Non-patent | – | Search report |
| Co-pending U.S. Appl. No. 11/607,815, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Non-Final Office Action Mailed Apr. 15, 2010 in Co-pending U.S. Appl. No. 11/607,815, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Final Office Action Mailed Nov. 9, 2009 in Co-pending U.S. Appl. No. 11/607,815, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Non-Final Office Action Mailed Mar. 31, 2009 in Co-pending U.S. Appl. No. 11/607,815, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Co-pending U.S. Appl. No. 11/607,431, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Final Office Action Mailed Sep. 4, 2009 in Co-pending U.S. Appl. No. 11/607,431, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Non-Final Office Action Mailed Apr. 15, 2009 in Co-pending U.S. Appl. No. 11/607,431, filed Dec. 1, 2006. | Non-patent | – | Applicant |
| Office Action mailed Nov. 24, 2010 from U.S. Appl. No. 11/607,815, filed Dec. 1, 2006. | Non-patent | – | Applicant |
4 members in 1 office; this record represents the family
Priority claims1
| Document | Office | Kind | Date |
|---|---|---|---|
| 74167205 | United States of America | P |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2007136446A1 | United States of America | A1 | |
| US2007165875A1 | United States of America | A1 | |
| US2007167187A1 | United States of America | A1 | |
| US8090374B2This record | United States of America | B2 |
104 transactions on the USPTO file
Allowed after 2 non-final rejections, 2 final rejections, 2 RCEs and 1 appeal.
- Non-final rejections
- 2
- Final rejections
- 2
- RCEs
- 2
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Payment of Maintenance Fee, 12th Year, Large EntityM1553 | M1553 | |
| Payment of Maintenance Fee, 8th Year, Large EntityM1552 | M1552 | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Correspondence Address ChangeC.AD | C.AD | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail-Petition Decision - DismissedMPTDI-1 | MPTDI-1 | |
| Petition Decision - DismissedPTDI-1 | PTDI-1 | |
| Petition EnteredPET. | PET. | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Electronic Information Disclosure StatementEIDS. | EIDS. | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Notice of Appeal FiledN/AP | N/AP | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail-Petition Decision - GrantedMP033 | MP033 | |
| Petition Decision - GrantedP033 | P033 | |
| Correspondence Address ChangeC.AD | C.AD | |
| Petition EnteredPET. | PET. | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Sent to Classification ContractorPGPC | PGPC | |
| Application Is Now CompleteCOMP | COMP | |
| Preliminary AmendmentA.PE | A.PE | |
| Payment of additional filing fee/PreexamFLFEE | FLFEE | |
| A statement by one or more inventors satisfying the requirement under 35 USC 115, Oath of the ApplicOATHDECL | OATHDECL | |
| Applicant has submitted new drawings to correct Corrected Papers problemsCORRDRW | CORRDRW | |
| Notice Mailed--Application Incomplete--Filing Date AssignedINCD | INCD | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Information Disclosure Statement consideredIDSC | IDSC |
19 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Maintenance fee paymentMAFP | MAFP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Fee payment procedurePAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication
- 08090374
- Application
- 60747506
Titles
- English
- Wireless multimedia handset
Patent term adjustment
- A delay
- +451 daysthe office missed an examination deadline
- B delay
- +82 dayspendency past three years
- Applicant delay
- −83 days
- Net adjustment
- 450 days
Classification
- CPC, 16
- H04W52/288
- H04M1/72403
- H04M1/2535
- H04M1/271
- H04M2250/02
- H04M2250/06
- H04M2250/64
- H04M2250/74
- H04W36/18
- H04W52/0229
- H04W52/0274
- G10L13/00
- G10L15/26
- Y02D30/70
- H04M1/72442
- H04M1/72412
- IPC, 1
- H04W36 00