Source: http://www.google.es/patents/US9542203
Timestamp: 2017-12-16 01:47:10
Document Index: 200063812

Matched Legal Cases: ['Application No. 201110423031', 'Application No. 201110426179', 'Application No. 201110400472', 'Application No. 2011343700', 'Application No. 201110408217', 'art 1', 'Application No. 201110426187', 'Application No. 201110426179', 'Application No. 2013', 'Application No. 2013']

Patente US9542203 - Universal dock for context sensitive computing device - Google Patentes
A dock for interacting with a computing device. The computing device configures itself for operations based on its context, which may be determined form the dock by reading a value from a tag on the dock. The computing device may use low power transmissions such that receiving a value from the tag provides...http://www.google.es/patents/US9542203?utm_source=gb-gplus-sharePatente US9542203 - Universal dock for context sensitive computing device
Número de publicación US9542203 B2
Número de solicitud US 12/960,753
También publicado como CN102567046A, CN102567046B, US20120144083, US20170115696
Número de publicación 12960753, 960753, US 9542203 B2, US 9542203B2, US-B2-9542203, US9542203 B2, US9542203B2
Inventores Amer A. Hassan, Yatharth Gupta, Ravi Rao, Billy R. Anders, JR.
Citas de patentes (293), Otras citas (190), Citada por (2), Clasificaciones (23), Eventos legales (2)
US 9542203 B2
A dock for interacting with a computing device. The computing device configures itself for operations based on its context, which may be determined form the dock by reading a value from a tag on the dock. The computing device may use low power transmissions such that receiving a value from the tag provides an indication of proximity to the dock. The value read provides an indication of a desired operation, and, in response to reading a value of the tag, the computing device may launch an application, pair with devices in the vicinity of the dock, or take other actions that configure the computing device. A universal dock, usable with computing devices of a plurality of form factors, may be implemented by providing an array of tags and, in some cases, a non-contact power supply.
1. A dock for a portable computing device, the dock comprising:
a support structure configured to receive the computing device in response to the computing device being placed on a support surface of the dock;
a plurality of tags configured to wirelessly transmit multiple values to the computing device, wherein the multiple values include tag identifiers that identify individual tags of the plurality of tags and an application identifier that indicates that an application having a corresponding application identity is to be executed by the computing device to automatically configure the computing device for use with the dock in response to a reading of the application identifier by the computing device, and wherein the application is associated with a location of the dock; and
a non-contact power supply configured to transfer power to the computing device when the computing device is placed on the support surface of the dock.
2. The dock of claim 1, wherein:
the dock comprises a two-dimensional array of tags disposed across the support surface; and
the plurality of tags comprise at least a portion of the array.
3. The dock of claim 2, wherein:
the two-dimensional array substantially covers the support surface.
4. The dock of claim 2, the non-contact power-supply is adjacent to the support surface.
5. The dock of claim 2, wherein:
each of the plurality of tags in the two-dimensional array is encoded with the same value.
6. The dock of claim 2, wherein:
each of the plurality of tags in the two-dimensional array is encoded with different values according to an error control code.
7. The dock of claim 5, wherein the plurality of tags comprise passive tags.
8. The dock of claim 1, wherein at least one of the plurality of tags comprises an active tag, the active tag comprising:
a controller, coupled to the radio, the controller configured for:
detecting, in a signal received by the radio, an indication of a computing device in the vicinity of the dock; and
in response to detecting the indication, controlling the radio to transmit at least one of the multiple values.
9. A method of operating a dock for a computing device, the method comprising:
supporting the computing device on a support surface of the dock;
receiving radiation from the computing device;
in response to receiving the radiation, emitting radiation from a plurality of tags, wherein the radiation from the a plurality of tags encode multiple values, the multiple values including values identifying individual tags of the plurality of tags, and a value indicating that an application with a corresponding identity is to be executed by the computing device to automatically configure the computing device for use with the dock in response to the computing device receiving the value, wherein the application is associated with a location of the dock; and
transferring power to the computing device using a non-contact power supply of the dock.
the emitted radiation has a power between 0.2 milliwatts and 1 milliwatt.
receiving radiation from the computing device comprises receiving a beacon; and
the emitted radiation also encodes another value indicative of at least one device in the vicinity of the dock for pairing with the computing device.
the at least one device includes a plurality of human interface devices.
the received radiation comprises a control packet comprising an information element;
the method further comprises analyzing the information element; and
the emitting radiation comprises emitting radiation in response to the analyzing determining that the information element identifies a service available from a device in the vicinity of the dock.
radiating power from the non-contact power-supply of the dock; and
charging a battery of the computing device from the power radiated from the non-contact power-supply.
15. A dock for a portable computing device, the dock comprising:
a support structure having a surface configured to receive the computing device; and
a plurality of tags, encoded with multiple values, the multiple values including tag identifiers that identify individual tags of the plurality of tags and the multiple values including an application identifier indicating that an application having a corresponding identifier is to be executed by the computing device to automatically configure the computing device for use with the dock in response to a reading of the application identifier by the computing device, the plurality of tags configured to wirelessly transmit the value to the computing device, wherein the operation is associated with a location of the dock; and
a non-contact power supply configured to wirelessly charge a battery of the computing device when the computing device is placed on the surface of the dock.
16. The dock of claim 15, wherein:
the non-contact power supply is configured for inductively coupling power to the computing device placed on the surface.
17. The dock of claim 15, wherein:
the non-contact power supply is configured for capacitively coupling power to the computing device placed on the surface.
18. The dock of claim 15, wherein:
the support structure comprises a member for holding the computing device against the surface with a screen of the computing device positioned with a predetermined orientation; and
the application identifier identifies a software application that, when executed, formats information for presentation on the screen in the orientation.
19. The dock of claim 15, wherein:
the support structure is configured for receiving a slate form factor computing device.
20. The dock of claim 19, wherein:
the dock is in combination with at least one wireless computer peripheral; and
the application identifier indicates to the computing device to perform a pairing ceremony with the at least one wireless computer peripheral.
Computing devices have become nearly ubiquitous and are used by people to perform many business and personal tasks. To support a wide range of functions, computing devices have been made smaller such that users can carry them from place to place. Smart phones, net books, laptop computers and slate computers are all examples of computing devices that have been designed to be carried by users.
Such computing devices may be programmed with applications that, when run, can control the computing device to perform many different operations. For example, a smart phone may run an application that provides route guidance or traffic data. A computer with a slate form factor may display pictures or serve as a game board.
An experience for a user of a portable computing device may be improved by equipping the computing device to configure itself based on its context. The computing device may use proximity-based communication to determine its location and a desired configuration for that location. Based on an ability to communicate with a tag using proximity-based communication, the computing device may determine that it is in close proximity to the tag. The tag may communicate to the computing device a value that may reveal to the computing device a desired operation for that location.
The computing device may then launch an application or take other action to configure itself. Such actions may include, for example, establishing communication with another device in the location. The specific actions taken, or specific action launched may be based on the value read from the tag.
To facilitate determination of a user intent to express a desired action associated with a location, a support structure may be provided to act as a dock into which a computing device may be placed. The dock may have a surface with one or tags positioned adjacent the surface such that a computing device placed on the surface may read a value from at least one of the tags.
The support structure may be configured to provide a universal dock usable with computing devices of any of a plurality of form factors. To provide a universal dock, an array of tags may be distributed across the surface of the support structure such that a proximity-based radio of a computing device placed on the surface will be close enough to at least one of the tags to read a value, regardless of the specific form factor of the computing device. In addition, the dock may be equipped with a non-contact power supply, for which a computing device may have a corresponding power pick-up component, such that a computing device placed on the dock may receive power without requiring the computing device to have a power connector that mates with a power connector on the dock.
FIG. 1 is a conceptual sketch of a context dependent computer configured to perform different operations in different contexts;
FIG. 2 is a schematic cross-section of a computing device capable of context dependent operation and an associated dock;
FIG. 3 is a schematic illustration of a value read from a tag;
FIG. 4 is a flowchart illustrating a method of operation of a context dependent computing device;
FIG. 5A is a schematic cross-section of an alternative embodiment of a computing device capable of for context dependent operation and an associated dock;
FIG. 5B is a top view of the dock, from the perspective of the line B-B, of FIG. 5A;
FIG. 6 is a schematic cross-section of a further alternative embodiment of a computing device capable of context dependent operation and an associated dock;
FIG. 7 is a flowchart of a process of operating a context dependent computing device and an associated dock according to some embodiments of the invention; and
FIG. 8 is a functional block diagram of components that may exist in a computing device, instead of or in addition to those illustrated in the foregoing figures.
The inventors have recognized and appreciated that an experience for a user of a portable computing device may be significantly enhanced by operating the computing device in a way that is context dependent. The context, and hence a desired operation of the computing device, may be determined based on the location of the computing device and actions from which intent of the user may be inferred. Such operation may be achieved with a computing device that can sense its position relative to locations that have been designated as being associated with a desired configuration of the computing device.
For example, a computing device placed on a nightstand in a bedroom may automatically configure itself as an alarm clock. The same computing device placed near a television may automatically configure itself to stream audio-video content for display on the television. In other instances, a computing device may sense its proximity to a desk in an office and attempt to form a wireless connection with a wireless keyboard and mouse. As yet another example, a computing device may sense that it is positioned on a table in a restaurant and download an application from the restaurant that displays menu options and receives an order from a user.
In some embodiments, the context of a computing device may be determined by reading values from tags using a proximity-based radio. The tags may be passive tags, responding the radiation emitted by the computing device. Though, active tags that respond to low level signals transmitted by the computing device may also be used. Regardless of the specific mechanism by which the tags operate, an ability for a computing device to read a tag signifies that the computing device is positioned close to the tag. The value read from the tag may additionally signify a desired action in that location. Accordingly, tags may be attached to locations in which a computer may be placed by a user as a signal of the user's content.
In some embodiments, the tags may be affixed to a support structure that positions the computing device in a desired orientation for its desired operation. Tags configured to transmit different values may be used with different types of support structures. For example, a support structure for a bedroom where the computing device is intended to operate as a clock may hold the computing device with its display vertically and may contain a tag that signifies that the computing device should configure itself as a clock. In contrast, a support structure in a location where the computing device is intended to operate as a game table may hold the computing device with its display horizontal and may contain a tag that signifies that the computing device should configure itself as a game table.
In addition to providing a place for affixing tags and, in some embodiments, orienting the computing device, a support structure may provide other functions. In some embodiments, a support structure may supply power to a computing device placed on the support structure. Power may be supplied through a non-contact power transfer mechanism, such as inductive or capacitive coupling. With such an approach, any computing device with a suitable non-contact power pick-up mechanism may obtain power when placed on the support structure. By appropriate positioning of tags, possibly in multiple locations over the support structure, any device placed on the support structure may also read a value from one of the tags. In this way, the support structure may act as a form of universal dock for a portable computing device.
A computing device placed on such a dock may configure itself automatically by selecting and launching an application based on a value read from at least one of the tags on the dock. Such a capability may be particularly desirable for a computing device with a slate form factor. Such devices are likely to be carried by uses from place to place, and the experience for those users may be greatly enhanced by configuring the computing device for operations based on context.
Turning to FIG. 1, an example of an environment in which a computing device that configures itself based on context is illustrated. FIG. 1 illustrates a user 20 with a portable computing device 30. In this example, computing device 30 is formatted with a slate form factor. Such a computing device may have a relatively large display 32. Display 32 may be touch-sensitive, providing a user interface with computing device 30. Though embodiments of the invention may be useful with a computing device having a slate form factor, the specific form factor of computing device 30 is not a limitation on the invention.
FIG. 1 illustrates that user 20 may interact with computing device 30 in multiple locations 10A, 10B, 10C and 10D. The nature of the interactions that user 20 desires to have with computing device 30 may be different in each of the locations. As an example, locations 10A, 10B, 10C and 10D may be locations within the home of user 20 where the user desires to have the computer configured for different operations. Location 10A may represent a location at which user 20 generally desires to interact with computing device 30 through its touch screen interface. In contrast, location 10B may represent a bedroom where user 20 would like computing device 30 to operate as an alarm clock. Location 10C, for example, may represent a home office where user 20 would like to use computing device 30 like a conventional desktop computer. Location 10D may represent a family room where user 20 would like for computing device 30 to be configured for playing a game.
Accordingly, each of the locations 10A, 10B, 10C and 10D is associated with a context. In this example, the context is defined both by location and user intent, representing the desired operation of computing device 30 in the location. In accordance with some embodiments of the invention, computing device 30 is adapted to identify its context and automatically configure itself for that context. For example, in location 10A, computing device 30 may present a user interface, such as may appear on a desktop of a conventional computer. In contrast, at location 10B, computing device 30 may execute an application that presents on display 32 a representation of a clock and may present a user interface through which a user may set or cancel an alarm. In location 10C, computing device 30 may form a connection with one or more peripherals through which the user 20 may control computing device 30 like a conventional desktop computer. In this example, location 10C includes a wireless keyboard 60 that may perform a paring ceremony with computing device 30 to form a connection between keyboard 60 and computing device 30. In this way, a user may type on keyboard 60 to provide input to computing device 30. Computing device 30 may also be programmed to form connections with different or additional peripherals. Though not illustrated in FIG. 1, location 10C may include a mouse and a printer, or other devices of the type conventionally used in a home office. In the context illustrated in FIG. 10C, computing device 30 may form connections with any or all of these devices to con itself to perform as a conventional desktop computer.
At location 10D, computing device 30 may configure itself so that it may be used by user 20, and possibly user 22 or other users, in playing a game. As an example, in location 10D, computing device 30 may launch an application that presents on display 32 game pieces 72A and 72B. The application launched in location 10D may perform other operations as part of the game played by user's 20 and 22. For example, such an application may receive input from either user 20 or 22 specifying moves to be made as part of the game, may keep score, may render graphics or other content as entertainment during the game or perform any other suitable operation.
Computing device 30 may use any suitable technique to determine its context such that it can then automatically select how to configure itself to perform operations desired by a user in that context. In the embodiment illustrated in FIG. 1, tags are used to indicate context. Each tag may be a device that can communicate information to computing device 30. This information, for example, may include at least one value that can directly or indirectly indicate a desired configuration of a computing device, such as computing device 30. The tags may be passive or active devices. An example of a passive device may be an RFID tag. As is known in the art, an RFID tag may absorb radiation of a particular frequency and re-radiated encoded with information. That information, in this example, may be a value indicating a desired configuration of the computing device. An example of an active tag may be a small semiconductor chip incorporating a radio and a microcontroller. The microcontroller may operate the transmitter, periodically or in response to an event, to transmit information that may indicate to a computing device a configuration desired.
Regardless of the nature of the tag, the tag may be configured for proximity-based communication. Proximity-based communication may limit the locations in which computing device 30 can access information from a tag. For example, when a radio within a computing device is configured to emit near-field radiation of the type to which an RFID tag will respond, the computing device generally must be within a few inches of the RFID tag to detect a response. In this way, an ability to read a value from the tag identifies the context of computing device 30 by indicating both a desired configuration of the computing device and that the computing device is positioned in a location where that configuration is desired.
In this example, proximity-based communication is achieved by using low power levels for at least a portion of the communication between computing device 30 and the tag. Even if active tags are used, proximity-based communication may be implemented by using relatively low power communication for at least a portion of the interaction between computing device 30 and the tag. Though, it should be appreciated that other techniques may be used to implement proximity-based communication. For example, visible light, infrared or other types of radiation that relies on line of sight may be used to implement a proximity-based radio. Also, a signal conveyed only when devices physically contact each other may serve as another form of proximity-based communication.
In the example of FIG. 1, tags are used to enable computing device 30 to identify different contexts corresponding with different locations 10B, 10C and 10D. Accordingly, FIG. 1 illustrates one or more tags in each of locations 10B, 10C and 10D. In location 10B, tags 52B1 and 52B2 are shown. In location 10C, tags 52C1 and 52C2 are shown. In location 10D, tags 52D1 and 52D2 are shown. The tags in each location may be encoded with values that identify a desired configuration of computing device 30 when in that location. In the example illustrated, each of the locations 10B, 10C and 10D contains multiple tags. In this embodiment, each of the tags at the same location may be encoded with the same value. In this way, even if computing device 30 is not precisely positioned relative to a single tag at that location, computing device 30 may nonetheless receive a value from at least one of the tags. Though, tags in different locations may be encoded with different values to signify to computing device 30 different contexts based on the values read from the tags.
No tag is explicitly shown in location 10A. The absence of a tag in this location may signal to computing device 30 that a default configuration is desired. The default configuration may entail presentation of a “desktop” as in a conventional computing device or may entail some other operating state based on user inputs.
Each of the tags may be positioned in a desired location in any suitable way. The specific approach used for positioning each tag may depend on its physical characteristics. For example, it is known that an RFID tag may be packaged in a wrapper with an adhesive surface that acts like a sticker. Though, it should be appreciated that any suitable mechanism for affixing a tag in a desired location may be used.
In the examples illustrated in FIG. 1, tags, such as tags 52B1, 52B2, 52C1 and 52C2, 52D1 and 52D2, may be imbedded in a structural component that acts as a support for computing device 30. Such a component may form a “dock” for computing device 30 when in a location where computing device 30 is desired to configure itself based on context. In the example of FIG. 1, docks 50B, 50C and 50D are illustrated in locations 10B, 10C and 10D, respectively. As shown, dock 50B contains multiple tags, of which tags 52B1 and 52B2 are illustrated. Similarly, dock 50C contains multiple tags, of which tags 52C1 and 52C2 are visible. Dock 50D also contains multiple tags, of which 52D1 and 52D2 are visible.
In this example, each of the docks 50B, 50C and 50D is shown schematically to be positioning computing device 30 in an orientation that is appropriate for intended operations in that location. For example, dock 50B is shown holding computing device 30 in an orientation in which user 20 may readily observe the clock on display 32. In location 10C, dock 50C is holding computing device 30 in an orientation, relative to a surface of a desk or table (not shown), in which user 20 may observe information presented on display 32 while using keyboard 60. In location 10D, dock 50D is holding computing device 30 in an orientation in which users 20 and 22 may view game pieces 72A and 72B on display 32 while playing a game.
Though not illustrated by the example of FIG. 1, any of the docks 50B, 50C or 50D may include features to aid in holding computing device 30 in a desired orientation. Such features may include tabs, shelves, clips, hooks or other positioning or holding mechanisms. The positioning or holding mechanisms may be specifically designed to conform to complementary features on computing device 30. Though, it is not necessary that a dock be specifically designed to receive a computing device of any particular size or shape. To the contrary, a dock may be configured to receive a computing device of any contemplated shape such that a universal dock may be provided.
Incorporation of multiple tags may facilitate construction of such a universal dock. Because low level radiation may be used to read a value from a tag, to enable computing device 30 to reliably determine context when placed in a dock, one of the tags should be close enough to an antenna of a radio within computing device 30 that senses and/or transmits radiation used in proximity-based communication. Having multiple tags in a dock, preferably positioned in a pattern across a surface against which computing device 30 will rest, can ensure that an antenna within computing device 30 used for proximity-based communication will be close enough to a tag to ensure reliable communication.
FIG. 1 also illustrates other capabilities that may be incorporated into a dock. As illustrated by dock 50C, a dock may be connected to a power source, such as outlet 56. The power source may be used to supply power to an active tag within the dock. Alternatively or additionally, the power source may be used to supply power for other purposes. As one example, a dock, such as dock 50C, may incorporate a power supply 54 that may be used to supply power to computing device 30 when placed on dock 50C.
Power may be coupled from power supply 54 to a power consuming portion of computing device 30 in any suitable way. In the embodiment illustrated, though, power supply 54 is a non-contact power supply, capable of radiating power for use by computing device 30. Computing device 30 may include a power pick up component to receive and use that power. Use of such a non-contact power supply may further facilitate use of dock 50C as a universal dock. Any computing device configured with a non-contact power pick up may receive power when placed in dock 50C without requiring a connector adapted to mate with a connector on power supply 54.
Turning to FIG. 2, additional details of computing device 30 are illustrated. FIG. 2 shows computing device 30 schematically in cross section. As shown, computing device 30 has a surface 220 that may be placed on a surface 222 of a dock 230. A radio 210, configured for proximity-based communications is positioned adjacent surface 220.
Dock 230 has a support structure, which may be made of metal, plastic or other suitable material. The support structure may contain tags, of which tags 232A and 232B are visible, or may provide attachment locations for such tags. As shown, the tags may be positioned adjacent surface 222. Though FIG. 2 shows only two such tags, tags 232A and 232B may form a portion of an array that extends in two dimensions across surface 222 such that, regardless of where adjacent surface 220 that radio 210 is positioned, radio 210 will be close enough to one of the tags to engage in proximity-based communication.
In this example, tags 232A and 232B are passive tags. Proximity-based communication may be performed using near field radiation 240. In operation, radio 210 may emit near field radiation 240 that may excite tag 232A. Tag 232A may reradiate near field radiation 240 modulated to represent information to be conveyed from tag 232A through radio 210 to processing circuitry within computing device 30.
In this example, tag 232A may be an RFID tag and radio 210 may be a near field radio that emits RF energy for reading an RFID tag as is known in the art. Though, any suitable proximity-based radio and compatible tag may be used.
In some embodiments, such as when computing device 30 emits radiation to excite a passive tag, it may be desirable to limit the period of time during which radiation, such as radiation 240, is emitted. Limiting the amount of time that radiation is emitted may reduce the drain of a battery in computing device 30. Accordingly, computing device 30 may be operated such that radio 210 is only triggered to emit radiation 240 when computing device 30 is likely in the proximity of a tag that may provide context information. Computing device 30 may utilize sensors 212 for this purpose.
Sensors 212 may be sensors specifically added to computing device 30 for the purpose of sensing conditions that would indicate proximity to a tag. Though, in some embodiments, sensors 212 may be sensors of the type conventionally incorporated in a portable computing device. For example, many portable computing devices include accelerometers. Such sensors may be incorporated in a computing device to detect an orientation of the computing device for purposes of configuring a display. Though, such sensors may be used for multiple other purposes, including to facilitate applications that provide route guidance or other motion-based applications.
In the example illustrated, computing device 30 may include CPU circuitry 214 that may execute operating system services and applications. Such circuitry may be programmed to control radio 210 based on the outputs of one or more sensors 212. In operation, CPU circuitry 214 may execute a program that monitors the outputs of sensors 212 to detect when computing device 30 is placed on a surface.
Such a detection may be based on sensing a parameter, including pressure or capacitance, that indicates contact with a surface. Alternatively or additionally, such a detection may be based on a detecting motion or acceleration of the computing device. In response to detecting such positioning of computing device 30, CPU circuitry 214 may enable radio 210 to emit radiation 240. Radio 210 may be controlled to emit radiation 240 to determine whether there is a tag in the proximity of radio 210. If a value can be read from a tag while radio 210 is emitting radiation 240, computing device 30 may determine that it is in a context in which it is intended to configure itself for the context indicated by the value read from the tag. If, after some period of time, which may be a fixed interval or a dynamically selected interval based on noise or other criteria, if no tag is detected, CPU circuitry 214 may turn off radio 210. This process of turning on radio 210 to detect a tag may be repeated each time the output of sensors 212 indicate a possibility of computing device 30 being placed against a surface that may contain a tag.
CPU circuitry 214 may be any suitable circuitry that controls the operation of computing device 30. CPU circuitry 214 may contain one or more hardware components acting as processors. These processors may be programmed to receive and process outputs of sensors 212, and to control radio 210. These processors may also be programmed to perform other actions, such as to receive a value that radio 210 reads from a tag. Any suitable response may be taken in response to reading a value from a tag. Such a response may include determining a desired configuration of computing device 30 based on the value read from the tag and then controlling computing device 30 to automatically assume that configuration.
Any suitable steps may be taken to configured computing device 30. Those steps may include adjusting operational parameters of any suitable hardware or software components within computing device 30. Alternatively or additionally, steps to configure computing device 30 may include establishing connections to one or more other devices. Those devices may be near the tag from which the value was read. Though, communication may be established in any suitable way. For example, FIG. 2 illustrates that computing device 30 may have a second radio 216. While radio 210 is configured for proximity-based communications, radio 216 may be configured for communication at a greater distance. For example, radio 216 may be a radio of the type used to communicate with a wireless LAN or wireless wWAN as are known in the art. Accordingly, a remote device to which a connection is established may be located virtually anywhere. In the example of FIG. 2, CPU circuitry 214 may be programmed to, in response to a value read from a tag, control radio 216 to connect to an external network 260 through an access point 250. External network 260, for example, may be the Internet such that, in response to a value read from a tag, computing device 30 may download information or software to configure computing device 30 from a server accessible over the Internet.
As a specific example, dock 230 may be attached to a table in a restaurant. When placed on dock 230, computing device 30 may read a value from a tag, such as tag 232A. CPU circuitry 214 may be programmed to identify that value as indicating that CPU circuitry 214 should download a program that configures computing device 30 to present a menu for the restaurant. Such a program may also configure computing device 30 to perform other operations desired in that context. For example, computing device 30 may be programmed to receive through a user interface user input reflecting an order for food from that restaurant. That program downloaded into computing device 30 in response to reading a value from a tag may further control computing device 30 to communicate the order information via radio 216 through access point 250 to a computer that can make the order information available to the restaurant. In this way, computing device 30 may perform operations appropriate for the context, which in this example is being placed on a table in a restaurant.
It should be appreciated that the specific configuration assumed by computing device 30 in response to reading a value of a tag may depend on the specific value read. FIG. 3 illustrates various types of information that may form a portion of a tag. One or more of these types of information may form a value read from a tag. In the example illustrated, value 310 includes multiple fields, such as fields 312, 314, 316, 318 and 320. Field 312 may contain information representing a type of tag. If a type field 312 is present in a value, that information may specify a type of operation desired for the computing device in the context. The type information may specify, for example, generally that the computing device 30 should configure itself as a media controller or should seek to pair with other devices near the tag. Such a field may be used for example, when computing device 30 is to configure itself to perform a generic operation. Other fields may be used to more specifically identify operations that are desired in a context.
As an example of a more specific value, field 314 may include an identification value for the tag. Tags may be assigned IDs in accordance with a scheme that ensures that tags have unique identifiers. CPU circuitry 214 may be programmed to associate specific actions with a specific tag identification read in a field 314.
As another example, field 316 may include an identification of an application to be executed in the context. CPU circuitry 214 may be programmed to respond to a tag containing an application ID such as in field 316 by launching an application having that application ID. That application may already be installed on computing device 30. In that scenario, upon identifying such an application, CPU circuitry 214 may access computer executable instructions stored in memory (not shown in FIG. 2) of computing device 30. Using known techniques, CPU circuitry 214 may then launch an application corresponding to those computer executable instructions.
Any suitable mechanism may be used to identify an application having an application ID as specified in the field 316. For example, CPU circuitry 214 may be programmed to search through a manifest, or other store of information, such as a registry, identifying software components installed on computing device 30. Upon detecting a software component with an identification matching the value in field 316, CPU circuitry 214 may launch that software component.
As another example of a mechanism for identifying an application to execute, value 310 may include a field 318 identifying a location where software defining that application may be accessed. In this example, the location from which the application can be obtained in indicated by an address of a location on a network from which computer executable instructions defining that application may be downloaded. In this example, the address on the network may be expressed as a URL for a web server.
In response to receiving a value 310 with a field 318, CPU circuitry 214 may engage a network interface that can communicate over the network from which the software defining the application can be obtained. That network interface may be a wireless network interface and may incorporate a radio different than the proximity-based radio 210 used to read a value from a tag. In the example of FIG. 2, upon reading a value 310 with a field 318 containing an application URL, CPU circuitry 214 may communicate through radio 216 to an access point 250. CPU circuitry 214 may then download software defining the application from network 260. Once downloaded, this application software may be launched by CPU circuitry 214, configuring computing device 30 to perform desired operations for the context in which value 310 was read from a tag.
Other information may be encoded in the value 310. That information may be used for purposes other than to identify an application to launch in the context. In the example of FIG. 3, value 310 includes a field 320. Field 320 includes information that may enhance the reliability of the information read from a tag. In this example, field 320 includes error correcting bits. To reduce errors during communication of the value, the information in value 310 may be encoded with an error correcting code, resulting in additional bits being added to value 310. Field 320 represents those additional error correction bits. Though, it should be appreciated that FIG. 3 is a conceptual illustration of error correction bits associated with value 310. In some embodiments, in which the total number of bits in value 310 may be increased through the use of an error correcting code, those bits may be dispersed throughout the value rather than appearing as a separately identifiable field.
Regardless of how those bits are encoded in value 310, upon receipt of value 310, CPU circuitry 314 may decode the value using the error correcting code, such that any errors introduced in transmission can be corrected. Use of error correcting coding may be beneficial in the application illustrated in which multiple tags may be positioned across surface 222. In that environment, radio 210 may be positioned closer to one of the tags than the others in the array. Nonetheless, radiation 240 emitted by radio 210 may reach other tags in the array, exciting those tags in addition to the closest tag. As a result, radio 210 may detect values from multiple tags. The values from the more distant tags may be weaker than the values from the nearest tag. Nonetheless, those values from the more distant tags will be out of phase with the value from the nearest tag, and have the potential to disrupt communication between radio 210 and the nearest tag. Using an error correcting code may reduce the chances of that disruption.
It should be appreciated that FIG. 3 provides an example of the types of information that may appear in a value read from a tag. In any given embodiment, a value may contain only one type of information or may contain a combination of types of information that is different than expressly illustrated in FIG. 3. The specific types of information in a value read from a tag are not critical to the invention.
Turning to FIG. 4, an exemplary method for operation of a computing device, such as computing device 30 (FIG. 2) is illustrated. In the example of FIG. 4, the process begins prior to the time that the computing device is placed on a dock. The process may begin with steps that enable the computing device to take a specific response in a detected context. In this example, the process begins at block 410 where applications are registered. Registration may allow the computing device to associate specific desired applications with specific context.
In the embodiment illustrated in FIG. 4, CPU circuitry 214 may have associated with it software defining a platform that automatically configures computing device 30 to perform desired operations based on context. That platform may accept registrations from software components loaded on computing device 30 that are intended to operate in specific context. Such registration may use techniques as are known in the art. For example, registration may include providing the platform with a call back mechanism such that the platform can invoke components of the application to perform desired operations when the context is detected.
In addition, the registration may identify in some way the context in which the application, or components of the application, are to be invoked. As one example, the registration process may entail providing to the platform a tag type or tag ID. When the platform receives a value, such as value 310 with a tag type in a field 312 or a tag ID in a field 314 matching the tag type or tag ID, respectively, provided upon registration, the platform may invoke the application or component associated with that value. Though, any suitable type of information may be provided upon registration that may allow a platform to determine a context in which a particular application or component is to be executed.
This registration may be performed at any suitable time. It may occur, for example, upon start up of computing device 30 or may occur at multiple times as different applications are installed on computing device 30. Though, it should be appreciated that registration at block 410 may not occur at all in some embodiments. For example, in embodiments in which a value 310 contains an application URL or other information that is sufficient for the platform to select an application to execute based on the context defined by the value read from the tag, no explicit registration step may be performed.
Regardless of whether and how registration occurs, the process may proceed to decision block 412. At decision block 412, a check may be made whether the computing device is possibly docked. The determination made a block 412 may be made in any suitable way that determines whether the computing devices in a location that may contain a tag. As described in connection with FIG. 3, this determination may be made based on the output of one or more sensors 212.
Regardless of how the determination is made, if, as a result of processing at decision block 412, it is determined that the computing device 30 is not docked, the process may loop back until a condition is detected in which the computing device may be docked. When that condition is detected, the process may proceed to block 420. At block 420, a component for proximity based communication, such as a near field radio, may be powered on such that any tag in the proximity of the computing device may be read. In this example, radio 210 may use near field RF radiation to energize a tag and may be powered on at block 420. Though, it should be appreciated that any suitable form of energy may be used for proximity-based communication in a proximity-based radio.
Regardless of the specific type of proximity-based radio used, the process may proceed to block 422 where a value may be read from a tag that is in close proximity to the computing device. A value may be read using a process as described above in connection with FIG. 2 or in any other suitable way. Though not expressly illustrated in FIG. 4, if no value can be read, the process may return to decision block 412.
Regardless of how the value is read, the process may proceed to block 424. Block 424 may begin a sub process in which the platform controls the computing device to configure itself to perform operations as desired within the context indicated by the value read at block 422. In this example, the configuration process involves pairing with nearby devices. This pairing may entail wireless communication between the computing device and one or more near by devices according to a predetermined protocol. That wireless communication may be performed by radio 210. Though, in some embodiments, a higher power radio, such as radio 216, may be used for pairing with nearby devices. As a specific example, the pairing may be performed using a BLUETOOTH® radio or a WI-FI DIRECT® radio.
The pairing may be directed towards any suitable device. In some embodiments, pairing at block 424 may entail discovering nearby devices by broadcasting messages according to the predetermined protocol. Alternatively, the value read at block 422 may contain information identifying a specific device or specific type of device for which pairing should be performed. For example, some predefined protocols for pairing devices support service discovery. A value read at block 422 may directly or indirectly identify a type of service to be acquired from a paired device such that processing at block 424 is conditional upon a device providing an indicated service being discovered.
The information read at block 422 may also direct the pairing operation performed at block 424 in other ways. As another example, a value read at block 422 may contain credentials, such as a PIN, that may be used in a pairing ceremony. Providing credential information in connection with a value read from a tag may both ensure that pairing is performed with a desired device for the context of computing device and may reduce the burden on the user of computing device 30. Though, in some embodiments, the predetermined protocol may support re-establishing communication with a device with which computing device 30 has previously paired without user interaction. For example, the WI-FI DIRECT® protocol supports re-establishing a pairing relationship with a device without further user interaction. Accordingly, there are multiple techniques that may be employed such that processing at block 424 does not require user interaction. Though, in some embodiments, user input may be desired to confirm the pairing, supply a PIN or otherwise direct processing at block 424 by providing input through a user interface to computing device 30.
Block 424 represents one type of processing that may be performed to configure a computing device for a specific context. Other processing may alternatively or additionally be performed. As a further example, block 426 illustrates a process step in which the platform identifies an application to execute in the context. Any suitable technique, including those described above in connection with FIG. 3, may be used at block 426 to identify an application based on a value read at block 422. Regardless of the manner in which the application is identified, processing may continue to block 428 where the platform may launch the identified application.
Once launched, the application may continue until it terminates or until the platform receives information that the computing device is no longer in the context for which the application was launched. Accordingly, FIG. 4 illustrates that the process proceeds to decision block 430 where a check is made whether the computing device has changed its position since it was determined at decision block 412 that the computing device has possibly been placed in a position in which it could be resting on a dock containing a tag. Any suitable technique may be used to determine a change in position at decision block 430. For example, an output of one or more sensors 212 indicating that the computing device 30 has moved or been separated from a surface against which it was previously resting may be used as an indication of a change in position at decision block 430. Regardless of the mechanism by which a change in position is detected, if no change is detected, the process may loop, allowing the launched application to continue to execute. In contrast, if the change in position is detected, the process may proceed to block 440. At block 440, the application launched at block 428 may be shut down. By ending the application at block 440, computing device 30 may be returned to its default state in which it is not configured for operation in any specific context. Though, any suitable action may be taken upon detecting that the computing device is no longer in a context for which an application was launched, including requesting input from the user or launching another application.
FIG. 4 illustrates that the process ends following block 440. However, in some embodiments all or portions of the process of FIG. 4 may be repeated while computing device 30 operates. For example, the processing may loop back from block 440 to decision block 412 where a further check may be made for an indication that the computing devices in proximity of additional tags that may indicate a context for which the computing device should be configured.
It should be recognized that the system configuration illustrated in FIG. 2 and the process illustrated in FIG. 4 are exemplary only and that other suitable configurations are possible. FIG. 5A illustrates one such suitable alternative configuration. FIG. 5A illustrates a computing device 530 that, like computing device 30 (FIG. 2) may have a slate form factor. Computing device 530 may contain a radio 210, sensors 212 and CPU circuitry 214 that may perform operations similar to those described in connection with FIG. 2. Those operations may include reading a value from an array of tags, which is schematically illustrated by tags 232A and 232B arrayed across a surface of a dock 532.
Dock 532 differs from dock 230 (FIG. 2) in that dock 532 contains a power supply 550. Power supply 550 may be used to transfer power from an AC source, such as outlet 56 (FIG. 1), to computing device 530. In this example, power supply 550 may be a non-contact power supply. For example, power supply 550 may use inductive or capacitive coupling to transfer power to computing device 530 when computing device 530 is placed on surface 522.
To receive the power transferred from power supply 550, computing device 530 may contain a power pick up component 540. Power pickup component 540 is, like radio 210, shown positioned adjacent a surface of computing device 530 that is intended to rest on dock 532. Such a configuration may enhance the rate of power transfer but is not a requirement of the invention. In this example, power supply 550 and power pickup 540 may be implemented using non-contact power transfer technology as is known in the art. Though, any suitable mechanism may be used to transfer power from dock 532 to computing device 530.
In the embodiment illustrated, power pickup 540 is coupled through charging circuit 542 to battery 544. Such a configuration allows battery 544 to be recharged while computing device 530 is placed against dock 532. Though, unlike a conventional computer docking station, no connectors are required on either computing device 530 or dock 532 to enable computing device 530 to charge while in the docking station. Accordingly, a computing device of arbitrary configuration may be placed on dock 532 to recharge battery 544.
To facilitate use of dock 532 by a computing device of an arbitrary configuration, dock 532 may contain a two dimensional array of tags such as tags 232A . . . 232J illustrated in FIG. 5B. FIG. 5B illustrates upper surface 522 of dock 532 from the perspective of the line B-B shown in FIG. 5A. As can be seen in FIG. 5B, the array of tags 232A . . . 232J substantially covers the surface 522 in a pattern that ensures that a proximity-based radio on a computing device placed against surface 522 will be close enough to one of the tags to reliably read a value from that tag. In this example, that two dimensional array is not regular to account for other components. Nonetheless, the tags have a distribution that covers surface 522. FIG. 5B illustrates one possible distribution of tags, but any suitable distribution may be used.
The spacing the tags in the array may be such that the distance between any point on that surface and the nearest tag is less than the distance over which proximity-based communication can be supported. For example, for a system using proximity-based communications designed to support communications over a distance of two inches or less, the tags may be positioned in an array in which tags are separated by a distance of four inches or less. Such a spacing of tags in the array may ensure that any point on the surface is spaced two inches or less from a tag. In this way, regardless of the configuration of computing device 530 and specifically where on the computing device an antenna for proximity-based communication is located, computing device 530 may reliably read a value from a tag when placed on such a dock.
In the embodiment illustrated, each of the tags 232A . . . 232J may have the same construction and may be programmed to supply the same value. With such a configuration, a computing device, such as computing device 530 may respond when placed on dock 532 in the same way, regardless of which of the tags 232A . . . 232J is closest to a radio sensing a value of a tag. Though, other embodiments are possible. For example, tags on the right side of surface 522 may be programmed with a value different than tags on the left side of surface 522. Such a configuration may result in a computing device placed in dock 532 responding differently based on the side of the dock on which the device is placed. As another example, tags, such as tags 232D, 232E, 232G and 232H, on the central portions of the surface 522 may be programmed with different values than tags, such as 232A, 232B, 232C, 232F, 232I and 232J, closer to the perimeter of surface 522. Such an embodiment may be useful when desired operations of computing device 530 differ depending on the size of computing device 530.
In the embodiment illustrated in FIG. 5B, dock 532 contains a single non contact power supply 550 located generally in the center of surface 522. Such a configuration may be useful in implementing a universal dock capable of supplying power to a computing device of arbitrary configuration placed on surface 522 when the overall dimensions of surface 522 are smaller than the distance over which power from power supply 550 can be adequately received by power pick up 540 or other similar components in a computing device that may be placed on surface 522. In other embodiments, multiple power supplies or multiple radiating components associated with a single power supply may be distributed across surface 522. Alternatively, constraints may be placed on a computing device intended to obtain power from dock 532. As an example, in order to obtain power, a device may be required to have a power pick up, such as power pick up 540, near the center of the device. Alternatively or additionally, computing devices may be designed with multiple power pick up components.
FIG. 6 illustrates a further alternative embodiment. As with dock 532, dock 632 is actively powered. Dock 632 includes a power cord for connection to an AC source of power. In addition to supplying power for a non-contact power supply 550, power input to dock 632 may power active components within the dock. In this example, dock 632 may contain a low power radio 634, which may act as a tag.
A controller 636 may be included in dock 632 to process information received by low power radio 634 and to control the timing and content of information transmitted by low power radio 634. In this example, low power radio 634 may transmit at a relatively low power level, such as −3 dBm or on the order of between 0.1 milliwatts and 1 milliwatts. At such low power levels, a standard radio for a computing device may only reliably receive information transmitted by low power radio 634 when in close proximity to the low power radio. In this way, low power radio 634 may allow radio 610 to act as a proximity-based radio in relation to information received from a low power radio 634.
Any suitable protocol may be used to allow dock 632 and computing device 630 to exchange information such that computing device 630 receives a value through low power radio 634 that indicates a context.
In this embodiment in which dock 632 is connected to a fixed source of power, low power radio 634 may transmit a signal that will initiate an interaction between computing device 630 and dock 632 that will result in computing device 630 receiving a tag value. In this scenario, though computing device 630 may incorporate sensors 212, outputs of those sensors need not be used to determine when to control radio 610 to transmit. Rather, radio 610 may be operated in a low power receive mode in which it can receive a signal transmitted by low power radio 634. Such a low power mode may be implemented simply by operating low power radio 610 with its transmitter powered off. Though, operating states in which the sensitivity of radio 610 is reduced in order to further save power may also be used.
Alternatively or additionally, low power operation of radio 610 may be achieved by reducing the time in which radio 610 is powered at all. For example, radio 610 may be normally powered off, but powered on for occasional brief intervals to detect whether computing device 630 is in the vicinity of a tag, which can be determined by attempting to receive a value transmitted by low power radio 634. Any suitable protocol may be used for radio 610 to scan for such a signal from a low power radio. For example, low power radio 634 may send a control packet, formatted as a beacon for example, at periodic intervals. Radio 610 may scan for such beacons on a periodic schedule, but for intervals long enough to detect a beacon quickly.
Once radio 610 detects the packet from low power radio 634, any suitable signals may be exchanged between computing device 630 and dock 632 to facilitate an exchange information. As one example, low power radio 634 may be controlled by controller 636 to transmit a value identifying devices in the vicinity of dock 632.
As one example of how such a signal may be used to communicate a tag value to computing device 630, controller 636 may control low power radio 634 to periodically transmit a beacon signal 654. When computing device 630 is close enough to dock 632 that hardware within radio 610 can detect such a signal, radio 610 may generate a control signal within computing device 630 to trigger CPU circuitry 214 to perform an operation, such as pairing with devices in the vicinity of dock 632. Transmission of a value may be formatted in any suitable way, for example as an information element in a control signal of a WI-FI protocol. For example, low power radio 634 may transmit a tag value as an information element in a beacon signal transmitted according to a WI-FI protocol. In this way, when radio 610 is in close proximity to low power radio 634 and CPU circuitry 214 is awake, the radio may detect the beacon 652, and that beacon may be processed by execution of controlling software within CPU circuitry 214. That processing may result in configuring computing device 630 for the context indicated by the value contained within the beacon. Configuring the computing device may include pairing with other devices, launching applications, or performing any other suitable steps.
Though, any suitable protocol may be used for a computing device placed near dock 632 to establish communication with dock 632 such that the computing device 630 may receive a tag value. FIG. 7 illustrates a process of operation of computing device 630 and dock 632 by which such a connection may be established to enable computing device 630 may determine context depended actions. The process may begin at any suitable time, such as when device 630 is powered on. Alternatively, the process may begin when sensors to 12 output an indication that computing device 630 has been placed against a surface or otherwise positioned such that it may be in proximity with a dock. Suppressing sending beacons, even low power beacons, until computing device 630 is detected to be in a position when it is likely placed in a dock may further save power on the computing device.
In the example illustrated in FIG. 7, computing device 630 may operate in a low power mode when computing device 630 is not actively performing operations for a user. In that low power mode, CPU circuitry 214 may be powered off. Radio 610 may operate in a low power mode in which it periodically emits a low power beacon and responds only to specific types of messages received.
Accordingly, the process of FIG. 7 begins at block 710 in this low power mode with radio 610 periodically sending a low power beacon. The low power beacon may be in a format that low power radio 634 may receive and controller 636 may process to identify that there is a device near dock 632 seeking a dock. The beacon may be formatted in accordance with the service discovery protocol as is known in the art or in any other suitable format. The beacon may identify generically the computing device 630 is seeking a dock, or the beacon may identify a specific type of dock, such as a dock associated with computer peripherals as illustrated in location 10C (FIG. 1).
Regardless of the format the beacon transmitted at block 710, the process may continue to decision block 712. At decision block 712, the process may branch depending on whether dock 632 detects a beacon representing a device seeking a dock. Dock 632 may detect the beacon from device 630 when device 630 is brought close enough to dock 632 such that the low power beacon may be received. As illustrated in FIG. 7, the process may loop back to block 710 if the dock 632 does not detect the beacon. As illustrated, device 630 may then send another low power beacon such that low power beacons are periodically sent. The period at which low power beacons are sent may be relatively long so as to conserve power on device 630.
When controller 636 detects a beacon, the process may continue to block 720. At block 720, controller 636 may command radio 634 to transmit a response, which may be in any suitable format, such as a control packet. That packet may be formatted with a value that may be used on computing device 630 to perform an operation, such as pairing with nearby devices.
CPU circuitry 214 may be programmed to respond to such a tag value by configuring itself to perform operations appropriate for the context associated with dock 632. Those operations may include any of the operations described above or any other suitable operation. Though, as a specific example, processing may proceed to block 722 where CPU circuitry may control radio 610 to pair with devices identified by the tag value. As a specific example, the tag value may identify human interface devices in the vicinity of dock 630. In this way, bringing the computing device into the vicinity of the dock may trigger the computing device to pair with human interface devices, automatically creating functionality that emulates functionality when a computer is physically coupled to a conventional dock with human interface devices wired to the dock.
FIG. 8 illustrates an example of a suitable computing system environment 800 on which the invention may be implemented. The computing system environment 800 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the invention. Neither should the computing environment 800 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 800.
The computer 810 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, FIG. 8 illustrates a hard disk drive 840 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 851 that reads from or writes to a removable, nonvolatile magnetic disk 852, and an optical disk drive 855 that reads from or writes to a removable, nonvolatile optical disk 856 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 841 is typically connected to the system bus 821 through a non-removable memory interface such as interface 840, and magnetic disk drive 851 and optical disk drive 855 are typically connected to the system bus 821 by a removable memory interface, such as interface 850.
For example, specific contexts and associated configurations have been described. These contexts and configurations should be understood to be exemplary and not limiting. There are many other possible contexts and configurations in which the techniques described above may be employed. For example, a tag may be affixed to a dashboard of a car such that when a computing device is placed on the dashboard, it operates as a GPS navigation system.
As another example, a dock may be constructed from a support structure specifically, configured to act as a dock. However, the support structure may serve other purposes. For example, the support structure may be a housing for a television set or may be a surface of a table in a restaurant modified to include components of a dock.
As another example, it is described that low power radio is placed near a surface of a computing device. In some embodiments, only an antenna for the radio may be positioned near the surface. Other components of the radio may be set back from the surface.
Moreover, it should be appreciated that examples of a support structure holding a tag have been provided for illustration only. Any suitable support structure may be used to hold a tag. Moreover, it is not necessary that the computing device be placed on a support structure for the system to operate as described above, The support structure may be an existing structure, such as a wall or a surface of an appliance. In these scenarios, simply bringing the computing device into the vicinity of the tag may be trigger a desired operation, such as launching an application.
Further, it was described that detecting a tag may cause a computing device to perform a context dependent operation. It should be appreciated that, in some embodiments, a dock may be regarded as a computing device and a computing device may have a surface supporting a tag. When the computing device is brought near the dock, the dock may respond in any of the ways described above.
Accordingly, it should be appreciated that either or both of the computing device and the dock may configure themselves based on a relative distance between them. As an example, upon detecting a computing device in close proximity, a dock may power on peripherals with which the computing device may attempt to pair.
US5682382 5 Sep 1995 28 Oct 1997 Massachusetts Institute Of Technology Scalable, self-organizing packet radio network having decentralized channel management providing collision-free packet transfer
US5966441 18 Nov 1996 12 Oct 1999 Apple Computer, Inc. Method and apparatus for creating a secure autonomous network entity of a network component system
US6343205 15 Mar 1999 29 Ene 2002 Motient Services Inc. Network operations center for mobile earth terminal satellite communications system
US6553060 28 Sep 2001 22 Abr 2003 Motorola, Inc. Method and apparatus for dynamic spectrum allocation
US6665709 27 Mar 2000 16 Dic 2003 Securit-E-Doc, Inc. Method, apparatus, and system for secure data transport
US7177288 28 Nov 2001 13 Feb 2007 Intel Corporation Simultaneous transmission and reception of signals in different frequency bands over a bus line
US7274911 6 Sep 2005 25 Sep 2007 Atheros Communications, Inc. System and method of conforming wireless devices to worldwide regulations
US7349342 17 Mar 2003 25 Mar 2008 International Business Machines Corporation Traffic metering in data networks
US7460253 24 Abr 2003 2 Dic 2008 Canon Kabushiki Kaisha Program storable image forming apparatus, control method, and control program
US7461253 20 Nov 2006 2 Dic 2008 Motorola, Inc. Method and apparatus for providing a key for secure communications
US7496637 12 Abr 2002 24 Feb 2009 Oracle International Corp. Web service syndication system
US7512401 4 Abr 2005 31 Mar 2009 Nokia Corporation Method and system for updating capabilities of a device
US7558604 25 Nov 2005 7 Jul 2009 Lenovo (Singapore) Pte. Ltd. Method and apparatus for remote discovery of client and access point settings in a wireless LAN
US7562129 15 Abr 1999 14 Jul 2009 Alcatel-Lucent Canada Inc. Subscription management system for data communication network
US7577125 8 Jul 2005 18 Ago 2009 Microsoft Corporation Direct wireless client to client communication
US7584296 5 Mar 2005 1 Sep 2009 Intel Corporation Asynchronous network stack operation in an operating system independent environment
US7589693 * 13 Ene 2006 15 Sep 2009 Honeywell International Inc. Method and apparatus for orienting a directional antenna
US7640213 26 Ago 2008 29 Dic 2009 Microsoft Corporation System and method providing rules driven subscription event processing
US7721093 2 Abr 2004 18 May 2010 Microsoft Corporation Authenticated exchange of public information using electronic mail
US7729689 13 Jul 2006 1 Jun 2010 International Business Machines Corporation Mobile wireless device adaptation based on abstracted contectual situation of user using near-field communications and information collectors
US7751317 26 Ene 2006 6 Jul 2010 Microsoft Corporation Cost-aware networking over heterogeneous data channels
US7769394 6 Oct 2006 3 Ago 2010 Sprint Communications Company L.P. System and method for location-based device control
US7925739 30 Dic 2005 12 Abr 2011 Cisco Technology, Inc. System and method for enforcing advertising policies using digital rights management
US7991770 27 Nov 2006 2 Ago 2011 Google Inc. Detecting repeating content in broadcast media
US8014415 30 Dic 2005 6 Sep 2011 Meshnetworks, Inc. Apparatus, system and method for communicating information in a wireless communication network
US8095111 30 Dic 2009 10 Ene 2012 At&T Mobility Ii Llc Methods for providing overdraft protection for post-paid communication service plans
US8098803 26 Sep 2005 17 Ene 2012 At&T Intellectual Property Ii, L.P. Method and apparatus for call gapping of wholesale customer traffic in a communication network
US8204013 28 Ene 2009 19 Jun 2012 Motorola Mobility, Inc. Method and device for detecting a GSM channel of interest
US8254878 26 Feb 2010 28 Ago 2012 Thl Holding Company, Llc Methods for use in conjunction with a handheld wireless communication device having an adjunct device coupled thereto
US8254992 8 Oct 2007 28 Ago 2012 Motion Computing, Inc. Wireless docking system and pairing protocol for multiple dock environments
US8285250 27 Oct 2011 9 Oct 2012 Google Inc. Mobile device-based bandwidth throttling
US8323040 * 5 Sep 2008 4 Dic 2012 Apple Inc. Docking station with moveable connector for hand-held electronic device
US8326958 2 Mar 2009 4 Dic 2012 Headwater Partners I, Llc Service activation tracking system
US8397982 * 17 Dic 2010 19 Mar 2013 Motorola Mobility Llc Method and device for recognition of docking stations
US8437736 13 Sep 2012 7 May 2013 Google Inc. Mobile device-based bandwidth throttling
US8479225 27 Nov 2006 2 Jul 2013 Google Inc. Social and interactive applications for mass media
US8493931 11 Sep 2009 23 Jul 2013 Google Inc. Efficient handover of media communications in heterogeneous IP networks using handover procedure rules and media handover relays
US8565928 3 Ene 2011 22 Oct 2013 General Electric Company Low cost and flexible energy management system and method for transmitting messages among a plurality of communication networks
US8589991 14 Dic 2010 19 Nov 2013 Microsoft Corporation Direct connection with side channel control
US8621097 3 Ene 2011 31 Dic 2013 General Electric Company Low cost and flexible energy management system
US8633616 * 27 Ene 2011 21 Ene 2014 Cynetic Designs Ltd. Modular pocket with inductive power and data
US8659565 * 28 Sep 2011 25 Feb 2014 Z124 Smartpad orientation
US8700641 1 Ago 2011 15 Abr 2014 Google Inc. Detecting repeating content in broadcast media
US8792429 14 Dic 2010 29 Jul 2014 Microsoft Corporation Direct connection with side channel control
US8813201 8 Jun 2010 19 Ago 2014 Marvell World Trader Ltd. Generating security material
US8892691 7 Abr 2011 18 Nov 2014 Apple Inc. Real-time or near real-time streaming
US8977731 3 Ene 2011 10 Mar 2015 Generay Electric Company Low cost and flexible energy management system providing user control arrangement in a plurality of modes
US9148238 10 May 2011 29 Sep 2015 Google Inc. Managing lifecycles of television gadgets and applications
US9178652 12 Ago 2014 3 Nov 2015 Microsoft Technology Licensing, Llc Cognitive use of multiple regulatory domains
US9237366 16 Abr 2010 12 Ene 2016 Google Technology Holdings LLC Method and apparatus for distribution of 3D television program materials
US20010021950 10 Jul 1998 13 Sep 2001 Michael Hawley Method and apparatus for controlling access to a computer network using tangible media
US20010037399 28 Dic 2000 1 Nov 2001 Dan Eylon Method and system for streaming software applications to a client
US20010042124 26 Ene 2001 15 Nov 2001 Barron Robert H. Web-based method, apparatus, and system for secure data storage
US20010046298 25 Jul 2001 29 Nov 2001 Yamaha Corporation Method and device for incorporating additional information into main information through electronic watermarking technique
US20010052052 1 Feb 2001 13 Dic 2001 Luosheng Peng Apparatus and methods for providing coordinated and personalized application and data management for resource-limited mobile devices
US20020156876 19 Ene 2001 24 Oct 2002 Hartman Robert Charles Managed services platform
US20030142651 25 Ene 2002 31 Jul 2003 Docomo Communications Laboratories Usa, Inc. Quality of service aware handoff trigger
US20030231586 10 Dic 2001 18 Dic 2003 Nortel Networks Limited System and method for maximizing capacity in a telecommunications system
US20040002305 19 Jun 2003 1 Ene 2004 Nokia Corporation System, apparatus, and method for effecting network connections via wireless devices using radio frequency identification
US20040049576 9 Jun 2003 11 Mar 2004 Limor Schweitzer Method and apparatus for session reconstruction
US20040174395 4 Mar 2003 9 Sep 2004 Jefferson Liu Tablet personal computer having functions of switching keyboards and display data
US20040203815 15 Abr 2003 14 Oct 2004 Texas Instruments Incorporated Wireless communications system using both licensed and unlicensed frequency bands
US20040260630 20 Jun 2003 23 Dic 2004 Benco David S. Network support for mobile service plan cumulative usage reports
US20050071319 30 Sep 2003 31 Mar 2005 International Business Machines Corporation Method, system, and storage medium for providing web-based electronic research and presentation functions via a document creation application
US20050083975 20 Oct 2003 21 Abr 2005 Macri Dean P. Using multiple communication links in conjunction with a media adapter
US20050085222 17 Oct 2003 21 Abr 2005 Nokia Corporation Software updating process for mobile devices
US20050097248 * 29 Oct 2003 5 May 2005 Kelley Brian H. System and method for establishing a communication between a peripheral device and a wireless device
US20050105632 10 Dic 2004 19 May 2005 Severine Catreux-Erces System and method for channel bonding in multiple antenna communication systems
US20050135235 28 Dic 2004 23 Jun 2005 Ryo Maruyama Communication apparatus, control method, program and computer readable information recording medium
US20050177715 9 Feb 2004 11 Ago 2005 Microsoft Corporation Method and system for managing identities in a peer-to-peer networking environment
US20050221844 31 Mar 2004 6 Oct 2005 Trethewey James R Method for configuration of notebook computer based on location
US20050223226 2 Abr 2004 6 Oct 2005 Microsoft Corporation Authenticated exchange of public information using electronic mail
US20050229246 31 Mar 2004 13 Oct 2005 Priya Rajagopal Programmable context aware firewall with integrated intrusion detection system
US20060015904 16 Jun 2005 19 Ene 2006 Dwight Marcus Method and apparatus for creation, distribution, assembly and verification of media
US20060041916 4 Dic 2004 23 Feb 2006 Mcquaide Arnold Jr Personal multi-modal control and communications system
US20060059462 15 Sep 2005 16 Mar 2006 Canon Kabushiki Kaisha Embedded device, control method therefor, program for implementing the control method, and storage medium storing the program
US20060143027 23 Dic 2004 29 Jun 2006 Srinivasan Jagannathan Network usage analysis system using subscriber and pricing information to minimize customer churn and method
US20060145815 13 May 2005 6 Jul 2006 Valerio Lanzieri System and method for relaying RFID data
US20060171304 11 Abr 2005 3 Ago 2006 Hill David R WLAN background scanning
US20060200678 16 Feb 2006 7 Sep 2006 Oki Electric Industry Co., Ltd. Wireless access point apparatus and method of establishing secure wireless links
US20060239208 2 Jun 2005 26 Oct 2006 Microsoft Corporation Wireless device discovery and configuration
US20060294112 15 Oct 2003 28 Dic 2006 Davide Mandato Specification of a software architecture for capability and quality-of-service negotiations and session establishment for distributed multimedia applications
US20070057793 * 21 Ago 2006 15 Mar 2007 Alden Ray M Contact array RFID readable input substrates and processes
US20070124485 30 Nov 2005 31 May 2007 Microsoft Corporation Computer system implementing quality of service policy
US20070153695 29 Dic 2005 5 Jul 2007 Ralph Gholmieh Method and apparatus for communication network congestion control
US20070153729 30 Dic 2005 5 Jul 2007 Alapuranen Pertti O Apparatus, system and method for communicating information in a wireless communication network
US20070161411 14 Mar 2007 12 Jul 2007 Siemens Technology-To-Business Center, Llc On-demand service performance upgrade for wireless network
US20070171915 26 Ene 2006 26 Jul 2007 Microsoft Corporation Cost-aware networking over heterogeneous data channels
US20070192735 25 May 2006 16 Ago 2007 Julia Lehto Mobile communication terminal and method therefore
US20070207750 5 Ene 2007 6 Sep 2007 Brown David L Integrated Power Management of a Client Device Via System Time Slot Assignment
US20070223398 21 Ene 2005 27 Sep 2007 Lenovo (Beijing) Limited Method for Implementing Grouping Devices and Interacting Among Grouped Devices
US20070225831 21 Mar 2007 27 Sep 2007 Yamaha Corporation Electronic apparatus and computer-readable medium containing program for implementing control method thereof
US20070248179 25 Abr 2006 25 Oct 2007 Microsoft Corporation Variable OFDM subchannel coding and modulation
US20070254628 27 Abr 2006 1 Nov 2007 Research In Motion Limited Method, apparatus and system for monitoring and controlling wireless resource usage
US20070271525 21 Dic 2006 22 Nov 2007 Samsung Electronics C. Ltd. Display method and system for portable device using external display device
US20070274488 12 May 2006 29 Nov 2007 Microsoft Corporation Communication device auto negotiate reconnect
US20070280332 30 Dic 2006 6 Dic 2007 Srikathyayani Srikanteswara Systems and Techniques for Radio Frequency Environment Awareness and Adaptation
US20080002658 8 Mar 2007 3 Ene 2008 Soliman Samir S System and method for high speed local connectivity between local devices
US20080016338 17 Jul 2007 17 Ene 2008 Sheng Sun System and method for secure wireless multi-hop network formation
US20080055399 1 Nov 2006 6 Mar 2008 Woodworth Brian R Audiovisual data transport protocol
US20080055423 30 Ago 2006 6 Mar 2008 Sbc Knowledge Ventures, Lp System and method of security monitoring
US20080063204 7 Sep 2006 13 Mar 2008 Motorola, Inc. Method and system for secure processing of authentication key material in an ad hoc wireless network
US20080065238 11 Jun 2007 13 Mar 2008 Technology, Patents & Licensing, Inc. Presentation of Still Image Data on Display Devices Using a Wireless Home Entertainment Hub
US20080081597 29 Sep 2006 3 Abr 2008 Cole Terry L Connection manager with prompter for service subscription
US20080104170 31 Oct 2006 1 May 2008 Microsoft Corporation Collaborative Networks for Parallel Downloads of Content
US20080130519 29 Ago 2007 5 Jun 2008 Microsoft Corporation Media Access Control (MAC) Protocol for Cognitive Wireless Networks
US20080132201 30 Nov 2006 5 Jun 2008 Johan Karlberg Methods, devices and computer program products for tracking usage of a network by a plurality of users of a mobile phone
US20080152098 20 Dic 2006 26 Jun 2008 Nortel Networks Limited Automatic Configuration of Telecommunication Station Sets
US20080195861 9 Feb 2007 14 Ago 2008 Research In Motion Limited Method and system for authenticating peer devices using eap
US20080197802 15 Feb 2008 21 Ago 2008 Seiko Epson Corporation Power transmission control device, power reception control device, non-contact power transmission system, power transmission device, power reception device, and electronic instrument
US20080207119 28 Feb 2007 28 Ago 2008 Futurewei Technologies, Inc. Waveform modulated wireless rural area network (wran) systems and modulation and multiple access techniques for wireless communication systems
US20080207128 19 Abr 2005 28 Ago 2008 Saarisalo Mikko Method, Device and System for Controlling Application Launching in a Mobile Terminal Device
US20080227384 8 Jun 2007 18 Sep 2008 Acetrax Operations Ag Wireless pc to audio visual link assembly for a motion video distribution system
US20080252419 * 11 Abr 2007 16 Oct 2008 Batchelor Michael D Wireless access control system and method
US20080275993 21 Mar 2007 6 Nov 2008 Microsoft Corporation Web service for user and subscription data storage
US20080293375 25 May 2007 27 Nov 2008 Cingular Wireless Ii, Llc Intelligent Information Control Repository
US20080293419 28 Abr 2008 27 Nov 2008 Interdigital Technology Corporation MOBILITY PROCEDURES AND DIFFERENTIATED CHARGING IN HOME NODE-Bs
US20080311952 13 Jun 2007 18 Dic 2008 Edward Masami Sugiyama Local broadcast channel selection control for mobile handset
US20080319857 2 May 2008 25 Dic 2008 Ellacoya Networks, Inc. Managing content resources
US20090011738 10 Sep 2008 8 Ene 2009 Akihiro Sasakura Mobile communication apparatus
US20090013175 15 Sep 2008 8 Ene 2009 Brig Barnum Elliott Method and apparatus for controlling the flow of data across a network interface
US20090039828 8 Ago 2007 12 Feb 2009 Daniel Benjamin Jakubowski Wireless charging of electronic devices
US20090045913 16 Ago 2007 19 Feb 2009 Farpointe Data, Inc., A California Corporation System and method for interrogation radio-frequency identification
US20090055266 22 May 2008 26 Feb 2009 Brody Edward Subscription promotion and management system and method
US20090089885 24 Sep 2008 2 Abr 2009 Finisar Corporation Radio frequency identifiers for providing user access to computing resources
US20090100080 19 Sep 2008 16 Abr 2009 Yann Toms Device for automatic indexing of content
US20090103481 19 Oct 2007 23 Abr 2009 Microsoft Corporation Maintaining multiple, simultaneous wireless network connections using a single radio
US20090106542 18 Oct 2007 23 Abr 2009 Lenovo (Singpore) Pte.Ltd. Autonomic computer configuration based on location
US20090111378 31 Oct 2007 30 Abr 2009 Motorola, Inc. Devices and methods for content sharing
US20090138715 24 Nov 2008 28 May 2009 University Of Massachusetts Wireless network security using randomness
US20090144622 29 Nov 2007 4 Jun 2009 Cisco Technology, Inc. On-Board Vehicle Computer System
US20090154343 12 Dic 2007 18 Jun 2009 Synapsanse Corporation Apparatus and method for adapting to failures in gateway devices in mesh networks
US20090158394 14 Ago 2008 18 Jun 2009 Electronics And Telecommunication Research Institute Super peer based peer-to-peer network system and peer authentication method thereof
US20090170431 31 Dic 2007 2 Jul 2009 Trevor Pering Device, system, and method of establishing multiple wireless connections
US20090196180 2 Abr 2008 6 Ago 2009 Microsoft Corporation Dynamic Time-Spectrum Block Allocation for Cognitive Radio Networks
US20090210940 23 Ene 2009 20 Ago 2009 Intermec Ip Corp. System and method of using rfid tag proximity to grant security access to a computer
US20090303902 25 Abr 2005 10 Dic 2009 Hang Liu Multicast mesh routing protocol
US20090319663 23 Jun 2008 24 Dic 2009 Michael Jason Giles Apparatus and methods for providing service discovery over alternate transports
US20100049971 18 Ago 2009 25 Feb 2010 Samsung Electronics Co., Ltd. Apparatus and Method for Using Secure Removable Media (SRM) in Digital Rights Management
US20100056124 4 Sep 2008 4 Mar 2010 Virginia Walker Keating System and method of providing mode changes to wireless devices
US20100091965 11 Dic 2009 15 Abr 2010 Huawei Technologies Co., Ltd. Service subscription method, system and server
US20100100637 24 Dic 2009 22 Abr 2010 Microsoft Corporation Dynamically Balancing User Experiences in a Multi-User Computing System
US20100103850 23 Oct 2008 29 Abr 2010 Motorola, Inc. Method and apparatus for channel selection in a wireless communication system
US20100104078 30 Dic 2009 29 Abr 2010 Henry Jr Coulter C Methods for Providing Overdraft Protection for Post-Paid Communication Service Plans
US20100111033 4 Nov 2008 6 May 2010 Broadcom Corporation Multiservice communication device with dedicated control channel
US20100115278 26 Ene 2009 6 May 2010 Microsoft Corporation Support of multiple pre-shared keys in access point
US20100121744 7 Nov 2008 13 May 2010 At&T Intellectual Property I, L.P. Usage data monitoring and communication between multiple devices
US20100123598 10 Mar 2009 20 May 2010 Apple Inc. System and Method for Capturing Remote Control Device Command Signals
US20100144274 10 Dic 2009 10 Jun 2010 Nokia Corporation Systems, Methods, and Apparatuses for Determining Proximity Between Computing Apparatuses
US20100153762 17 Nov 2009 17 Jun 2010 Qualcomm Incorporated Method and apparatus for adaptive bluetooth low power discovery and wake up
US20100157167 19 Dic 2008 24 Jun 2010 Lawther Joel S Display system and remote control for use therewith
US20100175101 30 Mar 2009 8 Jul 2010 Novafora, Inc. Content Distribution Systems and Methods
US20100186066 20 Ene 2009 22 Jul 2010 Pollard Stephen M Methods and systems for facilitating personal data propagation
US20100191576 2 Mar 2009 29 Jul 2010 Gregory G. Raleigh Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US20100191847 2 Mar 2009 29 Jul 2010 Gregory G. Raleigh Simplified service network architecture
US20100195580 30 Ene 2009 5 Ago 2010 Wi-Lan Inc. Wireless local area network using tv white space spectrum and long term evolution system architecture
US20100198952 30 Ene 2009 5 Ago 2010 Nokia Corporation Method for WALN network and device role activation
US20100220856 28 Abr 2009 2 Sep 2010 Johannes Petrus Kruys Private pairwise key management for groups
US20100226253 13 May 2010 9 Sep 2010 Embarq Holdings Company, Llc System and method for tracking a line rate utilization
US20100232332 27 May 2010 16 Sep 2010 Research In Motion Limited Methods And Apparatus For Reducing Power Consumption During Network Scanning Operations With Adverse Battery Conditions
US20100248599 10 Jun 2010 30 Sep 2010 Mike Voigt Guard for an electric machine tool, electric machine tool, and system comprising a guard and electric machine tool
US20100257251 1 Abr 2009 7 Oct 2010 Pillar Ventures, Llc File sharing between devices
US20100284316 26 Jun 2009 11 Nov 2010 Atheros Communications, Inc. Dynamic energy saving mechanism for access points
US20100302005 22 Oct 2008 2 Dic 2010 Petar Popovski Embedded rfid recorder in short-range wireless devices
US20100333032 30 Jun 2009 30 Dic 2010 Rovi Technologies Corporation Systems and methods for providing interactive media guidance on a wireless communications device
US20110010433 10 Jul 2009 13 Ene 2011 Microsoft Corporation Targeted presentation and delivery of themes
US20110149806 22 Dic 2010 23 Jun 2011 Samsung Electronics Co., Ltd. Method and apparatus for service discovery in wi-fi direct network
US20110176463 15 Ene 2010 21 Jul 2011 Atheros Communications, Inc. Managing power states in network communications
US20110188391 27 Ene 2011 4 Ago 2011 Texas Instruments Incorporated INTERRELATED WiFi AND USB PROTOCOLS AND OTHER APPLICATION FRAMEWORK PROCESSES, CIRCUITS AND SYSTEMS
US20110188419 29 Ene 2010 4 Ago 2011 Digi International Inc. Mesh network node service in a sleeping mesh network
US20110188420 29 Ene 2010 4 Ago 2011 Digi International Inc. I/o driven node commissioning in a sleeping mesh network
US20110202189 3 Ene 2011 18 Ago 2011 General Electric Company Low cost and flexible energy management system providing user control arrangement in a plurality of modes
US20110238498 29 Mar 2010 29 Sep 2011 Microsoft Corporation Service stage for subscription management
US20110261001 * 23 Abr 2010 27 Oct 2011 Jin Liu Apparatus and method for impact resistant touchscreen display module
US20110274020 6 May 2010 10 Nov 2011 Digi International Inc. Wireless mesh network controller synchronization
US20110275316 10 May 2010 10 Nov 2011 Nokia Corporation Device to device connection setup using near-field communication
US20110280413 13 May 2010 17 Nov 2011 Wi-Lan, Inc. System and Method For Protecting Transmissions of Wireless Microphones Operating in Television Band White Space
US20110293095 22 Ago 2011 1 Dic 2011 Mourad Ben Ayed Systems for intelligent authentication based on proximity
US20110320963 28 Jun 2010 29 Dic 2011 Rovi Technologies Corporation Systems and methods for controlling multiple user access to media devices in a connected platform environment
US20110321126 23 May 2011 29 Dic 2011 Nanoradio Hellas A.E. Method for wireless communication and wireless transmit/receive unit
US20120101952 4 Oct 2011 26 Abr 2012 Raleigh Gregory G System and Method for Providing User Notifications
US20120139690 6 Dic 2010 7 Jun 2012 Microsoft Corporation Context dependent computer operation
US20120147268 14 Dic 2010 14 Jun 2012 Microsoft Corporation Direct connection with side channel control
US20120147274 9 Dic 2010 14 Jun 2012 Microsoft Corporation Cognitive use of multiple regulatory domains
US20120147825 14 Dic 2010 14 Jun 2012 Microsoft Corporation Direct connection with side channel control
US20120155643 16 Dic 2010 21 Jun 2012 Microsoft Corporation Secure protocol for peer-to-peer network
US20120157038 17 Dic 2010 21 Jun 2012 Microsoft Corporation Operating system supporting cost aware applications
US20120158839 16 Dic 2010 21 Jun 2012 Microsoft Corporation Wireless network interface with infrastructure and direct modes
US20120158947 17 Dic 2010 21 Jun 2012 Microsoft Corporation Operating system supporting cost aware applications
US20120158981 16 Dic 2010 21 Jun 2012 Microsoft Corporation Fast join of peer to peer group with power saving mode
US20120178429 28 Jun 2010 12 Jul 2012 Nec Europe Ltd. Method for operating a wireless terminal as an access point and wireless terminal
US20120197792 12 Abr 2012 2 Ago 2012 Raleigh Gregory G Verifiable Service Policy Implementation for Intermediate Networking Devices
US20130033800 * 3 Ago 2011 7 Feb 2013 Research In Motion Limited Electronic device including predicted frequency error estimation of a voltage controlled oscillator and related methods
US20130097422 3 Dic 2012 18 Abr 2013 Research In Motion Limited Method and system for authenticating peer devices using eap
US20130182614 7 Mar 2013 18 Jul 2013 Qualcomm Incorporated Peer-to-peer communication in ad hoc wireless network
US20130211893 * 15 Mar 2013 15 Ago 2013 Ttn Holdings, Llc Systems and methods for automated rfid based commerce rewards
US20130322846 25 Ago 2011 5 Dic 2013 Bran Ferren Intelligent remote control system
US20140328251 16 Jul 2014 6 Nov 2014 Microsoft Corporation Direct connection with side channel control
CN1571341A 23 Abr 2004 26 Ene 2005 上海金诺网络安全技术发展股份有限公司 A control and charging method used for network value added service
CN1592210A 6 Sep 2004 9 Mar 2005 阿尔卡特公司 Device for processing the measurements of parameters and/or of traffic stream
CN1607780A 16 Oct 2003 20 Abr 2005 上海富邦信息技术有限公司 Wireless audio-video conversion transmitting-receiving system and method thereof
CN1662920B 24 Jun 2003 7 Abr 2010 诺基亚公司 System, apparatus, and method for effecting network connections via wireless devices using radio frequency identification
CN1677975A 2 Mar 2005 5 Oct 2005 微软公司 Authenticated exchange of public information using electronic mail
CN1929424A 6 Sep 2006 14 Mar 2007 日本电气株式会社 Method of evaluating channel bandwidth utilization ratio, wireless communication system
CN1960474A 17 Nov 2006 9 May 2007 四川大学 Method for realizing new IPTV service terminal
CN101021774A 14 Feb 2007 22 Ago 2007 三星电子株式会社 计算机系统及其控制方法
CN101044718A 26 Oct 2005 26 Sep 2007 德雷格医疗系统股份有限公司 Automatic wireless pan/lan switching
CN101075820A 23 Ene 2007 21 Nov 2007 三星电子株式会社 Display method and system for portable device using external display device
CN101094140A 10 May 2007 26 Dic 2007 国际商业机器公司 System and device of automatic data storage database
CN101137960A 4 Mar 2005 5 Mar 2008 美商内数位科技公司 Mobility enabled system architecture software architecture and application programing interface
CN101147308A 25 Oct 2006 19 Mar 2008 翰林Postech株式会社 Non-contact charger available of wireless data and power transmission, charging battery-pack and mobile divice using non-contact charger
CN101179359A 8 Nov 2007 14 May 2008 索尼株式会社 Wireless communication system, and apparatus and method for wireless communication
CN101288063A 20 Abr 2006 15 Oct 2008 微软公司 Wireless device discovery and configuration
CN101657828A 19 Feb 2008 24 Feb 2010 惠普开发有限公司 Wireless access control system and method
CN101841637A 19 Mar 2009 22 Sep 2010 华为技术有限公司 Method for interacting with set-top box and corresponding device
CN101867623A 15 Jul 2010 20 Oct 2010 上海交通大学 Peer-to-peer network service primitive system
EP2256663B1 19 May 2010 26 Ago 2015 Compagnie Industrielle et Financière d'Ingénierie "Ingenico" Activation of a contactless device by a capacitive device
GB2418809A Título no disponible
JP2001160927A Título no disponible
JP2005004089A Título no disponible
JP2005295286A Título no disponible
JP2005341094A Título no disponible
JP2006050216A Título no disponible
JP2007527156A Título no disponible
KR2008032979A Título no disponible
KR20100038089A Título no disponible
WO2001047248A Título no disponible
WO2001054342A Título no disponible
WO2004003801A1 24 Jun 2003 8 Ene 2004 Nokia Corporation System, apparatus, and method for effecting network connections via wireless devices using radio frequency identification
WO2006131077A1 8 Jun 2006 14 Dic 2006 Huawei Technologies Co., Ltd. Download update method for software/firmware of terminal equipment
WO2008021855A3 8 Ago 2007 28 Ago 2008 Motorola Inc Ad-hoc network key management
WO2008089854A1 16 Jul 2007 31 Jul 2008 Sony Ericsson Mobile Communications Ab Systems, device and method for controlling a mobile device by means of rfid tags
WO2008127507A1 19 Feb 2008 23 Oct 2008 Hewlett-Packard Development Company, L.P. Wireless access control system and method
WO2009046869A1 23 Sep 2008 16 Abr 2009 Nokia Siemens Networks S.P.A. Method and systems for qos-aware flow control in communication networks, corresponding network and computer program product
WO2010044599A2 14 Oct 2009 22 Abr 2010 Lg Electronics Inc. Method and apparatus for establishing direct link in wireless local area network system
WO2010132296A1 7 May 2010 18 Nov 2010 Qualcomm Incorporated System and method for resolving conflicts between air interfaces in a wireless communication system
1 "International Preliminary Report on Patentability Issued in PCT Application No. PCT/US11/65691", Mailed Date: Jun. 18, 2013, 5 Pages.
2 "International Search Report", Mailed Date: Aug. 14, 2012, Application No. PCT/US2011/065276, Filed Date: Dec. 15, 2011, pp. 9.
3 "International Search Report", Mailed Date: Jul. 12, 2012, Application No. PCT/US2011/063207, Filing Date: Dec. 4, 2011, pp. 9.
4 "International Search Report", Mailed Date: Jun. 22, 2012, Application No. PCT/US2011/063340, Filed Date: Dec. 5, 2011, pp. 9.
5 "Notice of Allowance Issued in Chinese Patent Application No. 201110423031.4", Mailed Date: Jan. 23, 2015, 3 Pages.
6 "Notice of Allowance Issued in Chinese Patent Application No. 201110426179.3", Mailed Date: Nov. 4, 2014, 3 Pages.
7 "Notice of Allowance Issued in U.S. Appl. No. 12/970,069" Mailed Date: Dec. 8, 2015, 3 Pages.
8 "Notice of Allowance Issued in U.S. Appl. No. 12/970,069" Mailed Date: Nov. 12, 2015, 3 Pages.
9 "Notice of Allowance Issued in U.S. Appl. No. 12/970,069", Mailed Date: Jan. 29, 2016, 4 Pages.
10 "Notice of Allowance Issued in U.S. Appl. No. 12/970,069", Mailed Date: May 15, 2015, 4 Pages.
11 "Office Action and Search Report Issued in Chinese Patent Application No. 201110400472.2", Mailed Date: Oct. 27, 2014, 14 Pages.
12 "Office Action Received in Australia Patent Application No. 2011343700", Mailed Date: Jul. 24, 2015, 2 Pages.
13 "Omnidrive", 2006, retrieved Oct. 26, 2006, 2 pages.
14 "Second Office Action Issued in Chinese Patent Application No. 201110408217.2", Mailed Date: May 23, 2014, Filed Date: Dec. 9, 2011, 8 Pages including partial translation.
15 "Xdrive", 2006, retrieved Oct. 26, 2006, 2 pages.
16 02 Network Scraps Unlimited Data for Smartphones; Published Date: Jun. 10, 2010; 2 pages.
17 802.11 Fast Bss Transition (FT) Part 1 of 2; Published Date: Aug. 21, 2007, 5 pages.
18 A New Location Technique for the Active Office-Published Date: 1997 http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.20.5052&rep=rep1&type=pdf.
19 Advisory Action mailed Jan. 2, 2013 in U.S. Appl. No. 11/726,862, 3 pages.
20 Araujo, Joao Taveira et al., "Towards Cost-Aware Multipath Routing," AIMS 2009, LNCS 5637, 2009, pp. 207-210.
21 Butler, Kevin R.B. et al.; Leveraging Identity-Based Cryptography for Node ID Assignment in Structured P2P Systems; IEEE Transactions on Parallel and Distributed Systems; vol. 20, No. 12; Dec. 2009; pp. 1803-1815.
22 Chinese Office Action dispatched Dec. 4, 2013 in CN Patent Application No. 201110426187.8, 8 pages including Concise Explanation of Relevance and/or partial translation.
23 Chinese Office Action dispatched Feb. 28, 2014 in CN Patent Application No. 201110426179.3, 9 pages including Concise Explanation of Relevance and/or partial translation.
24 Chinese Office Action mailed Aug. 5, 2014 in CN Patent App. No. 201110426179.3, 6 pages, including partial translation.
25 Chinese Office Action mailed Dec. 4, 2013 in CN Patent App. No. 201110408217.2,, 12 pages, including Concise Explanation of Relevance and/or partial translation.
26 Chinese Office Action mailed Dec. 4, 2013 in CN Patent App. No. 201110423031.4, 26 pages including translation.
27 Chinese Office Action mailed Feb. 17, 2014 in CN Patent App. No. 201110400433.2, 12 pages including partial translation.
28 Chinese Office Action mailed Feb. 27, 2014 in CN Patent App. No. 201110400472.2, 13 pages including Concise Explanation of Relevance and partial translation.
29 Chinese Office Action mailed Jan. 6, 2013 in CN Patent App. No. 201110423068.7, 8 pages including concise explanation of relevance and partial translation.
30 Chinese Office Action mailed Jan. 7, 2015 in CN Patent App. No. 201110400433.2, 10 pages including partial translation.
31 Chinese Office Action mailed Jul. 11, 2014 in CN Patent App. No. 201110423031.4, 13 pages including partial translation and/or concise explanation of relevance.
32 Chinese Office Action mailed Jul. 13, 2015 in CN Patent App. No. 201110400433.2, 3 pages.
33 Chinese Office Action mailed Nov. 20, 2013 in CN Patent App. No. 201110423001.3, 18 pages including translation.
34 Chinese Office Action mailed Sep. 2, 2013 in CN Patent App. No. 201110408217.2, 6 pages, including partial translation.
35 Chinese Office Action mailed Sep. 2, 2014 in CN Patent App. No. 201110408217.2, 6 pages, including partial translation.
36 Chinese Office Action mailed Sep. 4, 2014 in CN Patent App. No. 201110423001.3, 6 pages, including partial translation.
37 Chinese Office Action mailed Sep. 9, 2014 in CN Patent App. No. 201110400433.2, 13 pages including partial translation.
38 Choi, Jongmyung., "RFID Context-aware Systems", In Proceedings of Sustainable Radio Frequency Identification Solutions, Feb. 1, 2010, pp. 307-331.
39 Cisco Systems, Inc., "802.11 n Wireless Technology Overview," 2007, 7 pages.
40 Creating Customized Web Experiences with Windows Media Player 9 Series; Published Date: Nov. 2002; 1 page.
41 CRTDH; An Efficient Key Agreement Scheme for Secure Group Communications in Wireless Ad Hoc Networks; Published Date: 2005, 5 pages.
42 Currie, et al., "Experimental Evaluation of Read Performance for RFID-based Mobile Sensor Data Gathering Applications", In Proceedings of the 7th International Conference on Mobile and Ubiquitous Multimedia, Dec. 3, 2008, pp. 92-95.
43 Desai, Mitesh, K.; "Fast Join of Peer to Peer Group With Power Saving Mode"; U.S. Appl. No. 14/975,818, filed Dec. 20, 2015; 56 pages including Preliminary Amendment filed Dec. 29, 2015.
44 Extended European Search Report dated Jun. 8, 2015 in EP Patent App. No. 11849551.4, 6 pages.
45 Extended European Search Report dated May 20, 2014 in EP Patent App. No. 11847426.1, 8 pages.
46 Final Office Action mailed Dec. 26, 2013 in U.S. Appl. No. 12/967,638, 34 pages.
47 Final Office Action mailed Dec. 4, 2014 in U.S. Appl. No. 12/960,730, 22 pages.
48 Final Office Action mailed Dec. 5, 2014 in U.S. Appl. No. 12/970,069, 21 pages.
49 Final Office Action mailed Feb. 11, 2014 in U.S. Appl. No. 12/970,069, 26 pages.
50 Final Office Action mailed Feb. 15, 2013 in U.S. Appl. No. 12/967,761, 28 pages.
51 Final Office Action mailed Feb. 15, 2013 in U.S. Appl. No. 12/970,069, 23 pages.
52 Final Office Action mailed Jan. 11, 2016 in U.S. Appl. No. 12/970,034, 25 pages.
53 Final Office Action mailed Jan. 28, 2015 in U.S. Appl. No. 12/970,034, 24 pages.
54 Final Office Action mailed Jan. 9, 2015 in U.S. Appl. No. 14/318,380, 8 pages.
55 Final Office Action mailed Jul. 12, 2016 in U.S. Appl. No. 14/981,271, 10 pages.
56 Final Office Action mailed Jul. 13, 2015 in U.S. Appl. No. 14/318,380, 8 pages.
57 Final Office Action mailed Jun. 9, 2016 in U.S. Appl. No. 14/600,477, 9 pages.
58 Final Office Action mailed Mar. 28, 2013 in U.S. Appl. No. 12/967,638, 22 pages.
59 Final Office Action mailed Nov. 13, 2012 in U.S. Appl. No. 12/748,829, 42 pages.
60 Final Office Action mailed Nov. 15, 2010 in U.S. Appl. No. 11/726,862, 21 pages.
61 Final Office Action mailed Oct. 25, 2013 in U.S. Appl. No. 12/972,104, 10 pages.
62 Final Office Action mailed Oct. 6, 2014 in U.S. Appl. No. 12/972,104, 10 pages.
63 Final Office Action mailed Sep. 15, 2011 in U.S. Appl. No. 11/726,862, 24 pages.
64 Final Office Action mailed Sep. 20, 2012 in U.S. Appl. No. 11/726,862, 35 pages.
65 Final Office Action mailed Sep. 23, 2013 in U.S. Appl. No. 12/970,034, 22 pages.
66 Guide to IEEE 802.11i: Establishing Robust Security Networks;Published Date: Jun. 2006; 155 pages.
67 Haas, Robert et al., "Cost-and Quality-of-Service-Aware Network-Service Deployment," 2001, 6 pages.
68 Hassan, Amer, "Direct Connection With Side Channel Control"; U.S. Appl. No. 14/993,786, filed Jan. 12, 2016; 64 pages including Preliminary Amendment filed Jan. 13, 2016.
69 Hassan, Amer; "Cognitive Use of Multiple Regulatory Domains"; U.S. Appl. No. 14/458,203, filed Aug. 12, 2014; 58 pages including Preliminary Amendment filed Oct. 9, 2014.
70 Hassan, Amer; "Cognitive Use of Multiple Regulatory Domains"; U.S. Appl. No. 14/863,290, filed Sep. 23, 2015; 57 pages including Preliminary Amendment filed Nov. 1, 2015.
71 Hassan, Amer; "Direct Connection With Side Channel Control"; U.S. Appl. No. 14/333,386, filed Jul. 16, 2014, 65 pages including Preliminary Amendment filed Sep. 26, 2014.
72 Hassan, Amer; "Secure Protocol for Peer-To-Peer Network"; U.S. Appl. No. 14/600,477, filed Jan. 20, 2015; 62 pages including Preliminary Amendment filed May 8, 2014.
73 How Do You Use a Laptop As a TV Remote Control?; Published Date: Jul. 15, 2008; 6 pages.
74 International Search Report mailed Jul. 24, 2012 in PCT Application No. PCT/US2011/065691, Filing Date: Dec. 17, 2011, 11 pages.
75 International Search Report mailed Sep. 5, 2012 in PCT Application No. PCT/US2011/065692, Filing Date: Dec. 17, 2011, 8 pages.
76 International Search Report; Mailed Date: Aug. 31, 2012; Application No. PCT/US2011/064753; Filed Date: Dec. 14, 2011, pp. 8.
77 International Search Report; Mailed Date: Jul. 31, 2012; Application No. PCT/US2011/065285; Filed Date: Dec. 15, 2011, pp. 9.
78 Kaasinen, et al., "Ambient Functionality-Use Cases", In Proceedings of the 2005 joint conference on Smart objects and ambient intelligence: innovative context-aware services: usages and technologies, Oct. 12, 2005, 6 pages.
79 Kitson, Fred., "Mobile Media Making it a Reality", In Proceedings of Mobile Computing, vol. 3, Issue 4, Jun. 7, 2005, 17 pages.
80 Klym, et al., "The Evolution of RFID Networks: The Potential for Disruptive Innovation", In White Paper, Mar. 2006, 20 pages.
81 Lun, Desmond S. et al., "Network Coding with a Cost Criterion," MIT LIDS Technical Report P-2584, Apr. 2004, 18 pages.
82 Manage Subscription Products & Automate Recurring Billing Operations; Copyright 2008-2009; Retrieved Date: Jan. 12, 2010, 1 page.
83 Manifest Permission; Published Date: Jul. 21, 2004; 19 pages.
84 Meinrath et al.; "Unlicensed 'White Space Device' Operations on the TV Band and the Myth of Harmful Interferences", Mar. 2008, 13 pages.
85 Meinrath et al.; "White Space Devices & The Myths of Harmful Interference", 11 N.Y.U.J. Legis&Pub. Policy 495, 2008, 24 pages.
86 Menezes, Pascal; "Operating System Supporting Cost Aware Applications"; U.S. Appl. No. 13/844,932, filed Mar. 16, 2013; 57 pages.
87 Menezes, Pascal; "Operating System Supporting Cost Aware Applications"; U.S. Appl. No. 14/318,380, filed Mar. 16, 2013; 56 pages.
88 Menezes, Pascal; "Operating System Supporting Cost Aware Applications"; U.S. Appl. No. 14/981,271, filed Dec. 28, 2016; 63 pages including Preliminary Amendment filed Jan. 20, 2016.
89 Menezes, Pascal; "Operating System Supporting Cost Aware Applications"; U.S. Appl. No. 15/098,321, filed Apr. 14, 2016; 57 pages.
90 Mist: Cellular Data Network Measurement for Mobile Applications; Published Date: Apr. 24, 2006; 9 pages.
91 Mobile Internet Usage Measurements-Case Finland; Published Date: Apr. 24, 2006; 140 pages.
92 Mohammed, "Web Service for User and Subscription Data Storage", U.S. Appl. No. 13/772,275, filed Feb. 20, 2013, 49 pages.
93 Motorola, "TV White Space Position Paper," 2008, 10 pages.
94 Non-Final Office Action mailed Apr. 11, 2013 in U.S. Appl. No. 12/972,104, 15 pages.
95 Non-Final Office Action mailed Apr. 14, 2011 in U.S. Appl. No. 11/726,862, 22 pages.
96 Non-Final Office Action mailed Apr. 23, 2015 in U.S. Appl. No. 14/458,203, 10 pages.
97 Non-Final Office Action mailed Apr. 5, 2012 in U.S. Appl. No. 11/726,862, 23 pages.
98 Non-Final Office Action mailed Aug. 14, 2013 in U.S. Appl. No. 12/967,638, 30 pages.
99 Non-Final Office Action mailed Aug. 16, 2013 in U.S. Appl. No. 12/970,069, 26 pages.
100 Non-Final Office Action mailed Aug. 18, 2016 in U.S. Appl. No. 12/972,104, 13 pages.
101 Non-Final Office Action mailed Aug. 5, 2014 in U.S. Appl. No. 13/844,932, 7 pages.
102 Non-Final Office Action mailed Aug. 9, 2012 in U.S. Appl. No. 12/748,829, 29 pages.
103 Non-Final Office Action mailed Feb. 1, 2016 in U.S. Appl. No. 14/981,271, 8 pages.
104 Non-Final Office Action mailed Feb. 26, 2016 in U.S. Appl. No. 14/600,477, 10 pages.
105 Non-Final Office Action mailed Feb. 28, 2014 in U.S. Appl. No. 12/970,159, 22 pages.
106 Non-Final Office Action mailed Jan. 21, 2016 in US. Appl. No. 14/863,290, 7 pages.
107 Non-Final Office Action mailed Jan. 4, 2013 in U.S. Appl. No. 12/960,730, 14 pages.
108 Non-Final Office Action mailed Jul. 18, 2014 in U.S. Appl. No. 12/970,034, 24 pages.
109 Non-Final Office Action mailed Jul. 29, 2016 in U.S. Appl. No. 14/993,786, 16 pages.
110 Non-Final Office Action mailed Jun. 10, 2015 in U.S. Appl. No. 12/972,104, 10 pages.
111 Non-Final Office Action mailed Jun. 20, 2014 in U.S. Appl. No. 12/972,104, 10 pages.
112 Non-Final Office Action mailed Jun. 23, 2010 in U.S. Appl. No. 11/726,862, 16 pages.
113 Non-Final Office Action mailed Jun. 30, 2015 in U.S. Appl. No. 12/970,034, 26 pages.
114 Non-Final Office Action mailed Jun. 9, 2014 in U.S. Appl. No. 12/970,069, 20 pages.
115 Non-Final Office Action mailed Mar. 31, 2015 in U.S. Appl. No. 14/318,380, 7 pages.
116 Non-Final Office Action mailed May 23, 2014 in U.S. Appl. No. 12/748,829, 30 pages.
117 Non-Final Office Action mailed May 23, 2014 in U.S. Appl. No. 12/960,730, 18 pages.
118 Non-Final Office Action mailed May 30, 2013 in U.S. Appl. No. 12/970,034, 22 pages.
119 Non-Final Office Action mailed Nov. 6, 2013 in U.S. Appl. No. 12/960,730, 16 pages.
120 Non-Final Office Action mailed Nov. 8, 2013 in U.S. Appl. No. 13/844,932, 6 pages.
121 Non-Final Office Action mailed Oct. 16, 2012 in U.S. Appl. No. 12/970,069, 23 pages.
122 Non-Final Office Action mailed Oct. 2, 2012 in U.S. Appl. No. 12/967,638, 33 pages.
123 Non-Final Office Action mailed Oct. 2, 2014 in U.S. Appl. No. 14/318,380, 5 pages.
124 Non-Final Office Action mailed Oct. 26, 2012 in U.S. Appl. No. 12/967,761, 24 pages.
125 Non-Final Office Action mailed Oct. 27, 2014 in U.S. Appl. No. 13/772,275, 14 pages.
126 Non-Final Office Action mailed Sep. 24, 2012 in U.S. Appl. No. 12/964,492, 10 pages.
127 Non-Final Office Action mailed Sep. 29, 2014 in U.S. Appl. No. 12/748,829, 30 pages.
128 Non-Final Office Action mailed Sep. 4, 2015 in U.S. Appl. No. 14/318,380, 6 pages.
129 Non-Final Office Action mailed Sep. 6, 2012 in U.S. Appl. No. 12/972,230, 10 pages.
130 Notice of Acceptance dated Oct. 16, 2015 in AU Pat. App. No. 2011343943, 2 pages.
131 Notice of Allowance dated Jul. 1, 2016 in RU Pat. App. No. 2013127235, 12 pages w/o English Translation.
132 Notice of Allowance dated May 24, 2016 in JP Pat. App. No. 2013-544714, 3 pages.
133 Notice of Allowance mailed Apr. 2, 2014 in U.S. Appl. No. 12/964,492, 9 pages.
134 Notice of Allowance mailed Aug. 20, 2014 in U.S. Appl. No. 12/964,492, 13 pages.
135 Notice of Allowance mailed Dec. 26, 2013 in U.S. Appl. No. 12/972,230, 8 pages.
136 Notice of Allowance mailed Feb. 19, 2014 in U.S. Appl. No. 13/844,932, 8 pages.
137 Notice of Allowance mailed Jan. 7, 2016 in U.S. Appl. No. 14/318,380, 8 pages.
138 Notice of Allowance mailed Jul. 12, 2013 in U.S. Appl. No. 12/967,761, 12 pages.
139 Notice of Allowance mailed Jul. 24, 2014 in U.S. Appl. No. 12/972,230, 7 pages.
140 Notice of Allowance mailed Jun. 24, 2015 in U.S. Appl. No. 14/458,203, 11 pages.
141 Notice of Allowance mailed Jun. 27, 2014 in U.S. Appl. No. 12/970,159, 8 pages.
142 Notice of Allowance mailed Jun. 28, 2016 in JP Patent Application No. 2013-544795, 3 pages.
143 Notice of Allowance mailed Jun. 8, 2015 in U.S. Appl. No. 13/772,275, 8 pages.
144 Notice of Allowance mailed Mar. 10, 2014 in U.S. Appl. No. 12/972,230, 8 pages.
145 Notice of Allowance mailed Mar. 20, 2013 in U.S. Appl. No. 12/964,492, 9 pages.
146 Notice of Allowance mailed Mar. 20, 2015 in U.S. Appl. No. 12/970,069, 11 pages.
147 Notice of Allowance mailed Mar. 25, 2013 in U.S. Appl. No. 12/972,230, 8 pages.
148 Notice of Allowance mailed Mar. 4, 2013 in U.S. Appl. No. 12/972,230, 7 pages.
149 Notice of Allowance mailed Mar. 6, 2014 in U.S. Appl. No. 12/967,638, 11 pages.
150 Notice of Allowance mailed May 23, 2016 in U.S. Appl. No. 14/863,290, 12 pages.
151 Notice of Allowance mailed May 24, 2016 in JP Patent Application No. 2013-544714, 4 pages.
152 Notice of Allowance mailed May 7, 2014 in U.S. Appl. No. 13/844,932, 7 pages.
153 Notice of Allowance mailed Nov. 12, 2014 in U.S. Appl. No. 13/844,932, 8 pages.
154 Notice of Allowance mailed Nov. 20, 2012 in U.S. Appl. No. 12/972,230, 9 pages.
155 Notice of Allowance mailed Oct. 19, 2015 in U.S. Appl. No. 13/772,275, 8 pages.
156 Notice of Allowance mailed Oct. 27, 2016 in U.S. Appl. No. 14/600,477, 8 pages.
157 Notice of Allowance mailed Oct. 28, 2015 in U.S. Appl. No. 14/333,386, 12 pages.
158 Notice of Allowance mailed Oct. 8, 2015 in U.S. Appl. No. 12/970,069, 9 pages.
159 Notice of Allowance mailed Sep. 17, 2014 in U.S. Appl. No. 12/972,230, 7 pages.
160 Notice of Allowance mailed Sep. 3, 2014 in U.S. Appl. No. 12/970,159, 9 pages.
161 Office Action dated Apr. 1, 2014 in CN Pat. App. No. 201110423001.3, 8 pages, including partial translation.
162 Office Action dated Apr. 13, 2015 in CN Pat. App. No. 201110400472.04, 14 pages, including partial translation and/or concise explanation of relevance.
163 Office Action dated Apr. 3, 2014 in CN Pat. App. No. 201110417153.2, 15 pages, including partial translation and/or concise explanation of relevance.
164 Office Action dated Aug. 13, 2015 in AU Pat. App. No. 2011343943, 5 pages.
165 Office Action dated Aug. 14, 2015 in CN Pat. App. No. 201110417226.8, 6 pages, including partial translation.
166 Office Action dated Aug. 28, 2015 in JP Pat. App. No. 2013-544714, 5 pages including translation.
167 Office Action dated Dec. 15, 2014 in CN Pat. App. No. 201110417153.2, 8 pages, including partial translation.
168 Office Action dated Feb. 3, 2015 in CN Pat. App. No. 201110417226.8, 7 pages, including partial translation and/or concise explanation of relevance.
169 Office Action dated Jun. 5, 2014 in CN Pat. App. No. 201110417226.8, 14 pages, including partial translation and/or concise explanation of relevance.
170 Office Action dated Nov. 16, 2015 in JP Pat. App. No. 2013-544795, 9 Pages.
171 Office Action dated Nov. 24, 2015 in RU Pat. App. No. 2013127235, 4 Pages w/o English Translation.
172 Office Action dated Oct. 26, 2015 in JP Pat. App. No. 2013-543239, 13 pages including translation.
173 Pawar, Pravin et al. "Towards Location based QoS-Aware Network Selection Mechanism for the Nomadic Mobile Services," Dec. 5, 2009, 5 pages.
174 Roduner, et al., "Operating Appliances with Mobile Phones-Strengths and Limits of a Universal Interaction Device", In Proceedings of the 5th international conference on Pervasive computing, May 13, 2007, 18 pages.
175 Shared Spectrum, Inc., "Our Technology," Nov. 2010, 2 pages.
176 Shih, Eugene et al.; Wake on Wireless: An Event Driven Energy Saving; Published Date: Sep. 23-26, 2002; 12 pages.
177 Sridhar, T.; Wi-Fi, Bluetooth and WiMAX; The Internet Protocol Journal, vol. 11, No. 4; Retrieved Date: Sep. 30, 2010, 9 pages.
178 Subscription Management; Copyright 2009; Retrieved Date: Jan. 12, 2010; 2 pages.
179 Symbian Foundation Peer-to-Peer WiFi Inititative (WiFi Direct); Published Date: Sep. 10, 2010, 11 pages.
180 * Texas Instruments, MSP430 Ultra-Low-Power MCUs and TI-RFid Devices, 2009.
181 T-mobile "Unlimited" Data Usage; Published Date: Mar. 9, 2010; 6 pages.
182 Torres Service Management Platform; Retrieved Date: Jan. 12, 2010; 2 pages.
183 VAS Subscription Manager; Retrieved Date: Jan. 12, 2010; 1 page.
184 Wi-Fi Alliance: FAQs; Published Date: 2010; 19 pages.
185 Wi-Fi Certified Wi-Fi Direct Personal Portable Wi-Fi Technology, Oct. 2010 pp. 1-14.
186 Wi-Fi Certified Wi-Fi Direct, Personal, Portable Wi-Fi Technology; Oct. 2010, 14 pages.
187 WinLIRC; Published Date: Mar. 17, 2008; 5 pages.
188 Wireless PC to TV; Retrieved Date: Sep. 9, 2010; 2 pages.
189 Wood, "Kowari: A Platform for Semantic Web Storage and Analysis", May 27, 2005, 16 pages.
190 Yuan, Y. et al., "Allocating Dynamic Time-Spectrum Blocks in Cognitive Radio Networks," Sep. 9-14, 2007, 10 pages.
Clasificación internacional G06F13/00, G06K17/00, G06F9/445, H04W84/12, G06F1/30, G06K7/00, H04W12/04, H04M1/02, G06F1/26, G06F13/40, G06F1/16, H04W84/18
Clasificación cooperativa G06F13/4081, G06F9/445, G06F1/1632, H04M1/0254, H04W84/12, G06F1/1626, G06F1/30, G06K7/00, G06F13/409, G06F13/00, G06F1/26
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HASSAN, AMER A.;GUPTA, YATHARTH;RAO, RAVI;AND OTHERS;SIGNING DATES FROM 20101129 TO 20101203;REEL/FRAME:025958/0352