Patent Grant
9870028
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.
The foregoing is a non-limiting summary of the invention, which is defined by the attached claims.
The accompanying drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component that is illustrated in various FIG. is represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:
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
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
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
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
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
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
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.
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
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
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,
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.
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
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
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
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
Turning to
In the embodiment illustrated in
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
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
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
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,
It should be recognized that the system configuration illustrated in
Dock 532 differs from dock 230 (
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
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, 2321 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
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.
In the example illustrated in
Accordingly, the process of
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
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.
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
The computing environment may execute computer-executable instructions, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
With reference to
Computer 810 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 810 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 810. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
The system memory 830 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 831 and random access memory (RAM) 832. A basic input/output system 833 (BIOS), containing the basic routines that help to transfer information between elements within computer 810, such as during start-up, is typically stored in ROM 831. RAM 832 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 820. By way of example, and not limitation,
The computer 810 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
The computer 810 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 880. The remote computer 880 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 810, although only a memory storage device 881 has been illustrated in
When used in a LAN networking environment, the computer 810 is connected to the LAN 871 through a network interface or adapter 870. When used in a WAN networking environment, the computer 810 typically includes a modem 872 or other means for establishing communications over the WAN 873, such as the Internet. The modem 872, which may be internal or external, may be connected to the system bus 821 via the user input interface 860, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 810, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
Having thus described several aspects of at least one embodiment of this invention, it is to be appreciated that various alterations, modifications, and improvements will readily occur to those skilled in the art.
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.
Such alterations, modifications, and improvements are intended to be part of this disclosure, and are intended to be within the spirit and scope of the invention. Accordingly, the foregoing description and drawings are by way of example only.
The above-described embodiments of the present invention can be implemented in any of numerous ways. For example, the embodiments may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers. Such processors may be implemented as integrated circuits, with one or more processors in an integrated circuit component. Though, a processor may be implemented using circuitry in any suitable format.
Further, it should be appreciated that a computer may be embodied in any of a number of forms, such as a rack-mounted computer, a desktop computer, a laptop computer, or a tablet computer. Additionally, a computer may be embedded in a device not generally regarded as a computer but with suitable processing capabilities, including a Personal Digital Assistant (PDA), a smart phone or any other suitable portable or fixed electronic device.
Also, a computer may have one or more input and output devices. These devices can be used, among other things, to present a user interface. Examples of output devices that can be used to provide a user interface include printers or display screens for visual presentation of output and speakers or other sound generating devices for audible presentation of output. Examples of input devices that can be used for a user interface include keyboards, and pointing devices, such as mice, touch pads, and digitizing tablets. As another example, a computer may receive input information through speech recognition or in other audible format.
Such computers may be interconnected by one or more networks in any suitable form, including as a local area network or a wide area network, such as an enterprise network or the Internet. Such networks may be based on any suitable technology and may operate according to any suitable protocol and may include wireless networks, wired networks or fiber optic networks.
Also, the various methods or processes outlined herein may be coded as software that is executable on one or more processors that employ any one of a variety of operating systems or platforms. Additionally, such software may be written using any of a number of suitable programming languages and/or programming or scripting tools, and also may be compiled as executable machine language code or intermediate code that is executed on a framework or virtual machine.
In this respect, the invention may be embodied as a computer readable storage medium (or multiple computer readable media) (e.g., a computer memory, one or more floppy discs, compact discs (CD), optical discs, digital video disks (DVD), magnetic tapes, flash memories, circuit configurations in Field Programmable Gate Arrays or other semiconductor devices, or other non-transitory, tangible computer storage medium) encoded with one or more programs that, when executed on one or more computers or other processors, perform methods that implement the various embodiments of the invention discussed above. The computer readable storage medium or media can be transportable, such that the program or programs stored thereon can be loaded onto one or more different computers or other processors to implement various aspects of the present invention as discussed above. As used herein, the term “non-transitory computer-readable storage medium” encompasses only a computer-readable medium that can be considered to be a manufacture (i.e., article of manufacture) or a machine. Alternatively or additionally, the invention may be embodied as a computer readable medium other than a computer-readable storage medium, such as a propagating signal.
The terms “program” or “software” are used herein in a generic sense to refer to any type of computer code or set of computer-executable instructions that can be employed to program a computer or other processor to implement various aspects of the present invention as discussed above. Additionally, it should be appreciated that according to one aspect of this embodiment, one or more computer programs that when executed perform methods of the present invention need not reside on a single computer or processor, but may be distributed in a modular fashion amongst a number of different computers or processors to implement various aspects of the present invention.
Computer-executable instructions may be in many forms, such as program modules, executed by one or more computers or other devices. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. Typically the functionality of the program modules may be combined or distributed as desired in various embodiments.
Also, data structures may be stored in computer-readable media in any suitable form. For simplicity of illustration, data structures may be shown to have fields that are related through location in the data structure. Such relationships may likewise be achieved by assigning storage for the fields with locations in a computer-readable medium that conveys relationship between the fields. However, any suitable mechanism may be used to establish a relationship between information in fields of a data structure, including through the use of pointers, tags or other mechanisms that establish relationship between data elements.
Various aspects of the present invention may be used alone, in combination, or in a variety of arrangements not specifically discussed in the embodiments described in the foregoing and is therefore not limited in its application to the details and arrangement of components set forth in the foregoing description or illustrated in the drawings. For example, aspects described in one embodiment may be combined in any manner with aspects described in other embodiments.
Also, the invention may be embodied as a method, of which an example has been provided. The acts performed as part of the method may be ordered in any suitable way. Accordingly, embodiments may be constructed in which acts are performed in an order different than illustrated, which may include performing some acts simultaneously, even though shown as sequential acts in illustrative embodiments.
Use of ordinal terms such as “first,” “second,” “third,” etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed, but are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term) to distinguish the claim elements.
Also, the phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” or “having,” “containing,” “involving,” and variations thereof herein, is meant to encompass the items listed thereafter and equivalents thereof as well as additional items.
This application is a continuation of U.S. patent application Ser. No. 12/960,753, filed Dec. 6, 2010, entitled “UNIVERSAL DOCK FOR CONTEXT SENSITIVE COMPUTING DEVICE,” now U.S. Pat. No. 9,542,203, issued Jan. 10, 2017. The entirety of this afore-mentioned application is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4949299 | Pickett | Aug 1990 | A |
| 5574964 | Hamlin | Nov 1996 | A |
| 5682382 | Shepard | Oct 1997 | A |
| 5689825 | Averbuch et al. | Nov 1997 | A |
| 5729682 | Marquis et al. | Mar 1998 | A |
| 5963915 | Kirsch | Oct 1999 | A |
| 5966441 | Calamera | Oct 1999 | A |
| 6288749 | Freadman | Sep 2001 | B1 |
| 6317490 | Cameron et al. | Nov 2001 | B1 |
| 6338046 | Saari et al. | Jan 2002 | B1 |
| 6343205 | Threadgill et al. | Jan 2002 | B1 |
| 6553060 | Souissi et al. | Apr 2003 | B2 |
| 6628965 | Larosa et al. | Sep 2003 | B1 |
| 6665709 | Barron | Dec 2003 | B1 |
| 6711617 | Bantz et al. | Mar 2004 | B1 |
| 6789228 | Merril et al. | Sep 2004 | B1 |
| 6823379 | Heckel et al. | Nov 2004 | B1 |
| 7020472 | Schmidt | Mar 2006 | B2 |
| 7027808 | Wesby | Apr 2006 | B2 |
| 7058696 | Phillips et al. | Jun 2006 | B1 |
| 7107009 | Sairanen et al. | Sep 2006 | B2 |
| 7110843 | Pagnano et al. | Sep 2006 | B2 |
| 7177288 | Mooney et al. | Feb 2007 | B2 |
| 7194278 | Cook | Mar 2007 | B1 |
| 7274911 | Li | Sep 2007 | B2 |
| 7280978 | Joao | Oct 2007 | B1 |
| 7290132 | Aboba et al. | Oct 2007 | B2 |
| 7349342 | Carpenter et al. | Mar 2008 | B2 |
| 7400253 | Cohen | Jul 2008 | B2 |
| 7412534 | Tsang et al. | Aug 2008 | B2 |
| 7454191 | Dawson et al. | Nov 2008 | B2 |
| 7460253 | Osada | Dec 2008 | B2 |
| 7461253 | Braskich et al. | Dec 2008 | B2 |
| 7496637 | Han et al. | Feb 2009 | B2 |
| 7512401 | Muhonen et al. | Mar 2009 | B2 |
| 7558604 | Narayanaswami et al. | Jul 2009 | B2 |
| 7562129 | Lee et al. | Jul 2009 | B1 |
| 7577125 | Abhishek et al. | Aug 2009 | B2 |
| 7580678 | Byman-Kivivuori et al. | Aug 2009 | B2 |
| 7584296 | Sun et al. | Sep 2009 | B2 |
| 7589693 | Locke | Sep 2009 | B2 |
| 7640213 | Reunert et al. | Dec 2009 | B2 |
| 7721093 | Sundararajan | May 2010 | B2 |
| 7729689 | Chakraborty et al. | Jun 2010 | B2 |
| 7751317 | Toyama et al. | Jul 2010 | B2 |
| 7769394 | Zhu | Aug 2010 | B1 |
| 7783019 | Mahone et al. | Aug 2010 | B2 |
| 7792920 | Istvan et al. | Sep 2010 | B2 |
| 7925739 | Kocho et al. | Apr 2011 | B2 |
| 7962854 | Vance et al. | Jun 2011 | B2 |
| 7991770 | Covell et al. | Aug 2011 | B2 |
| 8014415 | Alapuranen | Sep 2011 | B2 |
| 8095111 | Henry, Jr. et al. | Jan 2012 | B2 |
| 8098803 | Croak et al. | Jan 2012 | B1 |
| 8204013 | Lewis | Jun 2012 | B2 |
| 8239516 | Huslak et al. | Aug 2012 | B2 |
| 8254878 | Howard et al. | Aug 2012 | B2 |
| 8254992 | Ashenbrenner et al. | Aug 2012 | B1 |
| 8260998 | Ganesh et al. | Sep 2012 | B2 |
| 8285250 | Rubin et al. | Oct 2012 | B2 |
| 8323040 | Prest | Dec 2012 | B2 |
| 8326958 | Raleigh | Dec 2012 | B1 |
| 8375328 | Koh et al. | Feb 2013 | B2 |
| 8397982 | Slaby et al. | Mar 2013 | B2 |
| 8437736 | Rubin et al. | May 2013 | B2 |
| 8479225 | Covell et al. | Jul 2013 | B2 |
| 8493931 | Nix | Jul 2013 | B1 |
| 8565928 | Venkatakrishnan et al. | Oct 2013 | B2 |
| 8577329 | Momtahan et al. | Nov 2013 | B2 |
| 8589991 | Hassan et al. | Nov 2013 | B2 |
| 8606911 | Raleigh et al. | Dec 2013 | B2 |
| 8621097 | Venkatakrishnan et al. | Dec 2013 | B2 |
| 8633616 | Soar | Jan 2014 | B2 |
| 8659565 | Sirpal et al. | Feb 2014 | B2 |
| 8700641 | Covell et al. | Apr 2014 | B2 |
| 8792429 | Hassan et al. | Jul 2014 | B2 |
| 8813201 | Lambert et al. | Aug 2014 | B2 |
| 8892691 | Pantos et al. | Nov 2014 | B2 |
| 8971841 | Menezes et al. | Mar 2015 | B2 |
| 8977731 | Venkatakrishnan et al. | Mar 2015 | B2 |
| 8984628 | Mahaffey et al. | Mar 2015 | B2 |
| 9008610 | Menezes et al. | Apr 2015 | B2 |
| 9009828 | Ramsey et al. | Apr 2015 | B1 |
| 9148238 | Dureau | Sep 2015 | B2 |
| 9178652 | Hassan et al. | Nov 2015 | B2 |
| 9237366 | Schaffer et al. | Jan 2016 | B2 |
| 9392462 | Raleigh et al. | Jul 2016 | B2 |
| 9450995 | Hassan et al. | Sep 2016 | B2 |
| 9596220 | Hassan et al. | Mar 2017 | B2 |
| 20010021950 | Hawley et al. | Sep 2001 | A1 |
| 20010037399 | Eylon et al. | Nov 2001 | A1 |
| 20010042124 | Barron | Nov 2001 | A1 |
| 20010046298 | Terada et al. | Nov 2001 | A1 |
| 20010052052 | Peng | Dec 2001 | A1 |
| 20020067268 | Lee et al. | Jun 2002 | A1 |
| 20020116485 | Black et al. | Aug 2002 | A1 |
| 20020120935 | Huber et al. | Aug 2002 | A1 |
| 20020143819 | Han et al. | Oct 2002 | A1 |
| 20020154751 | Thompson et al. | Oct 2002 | A1 |
| 20020156876 | Hartman et al. | Oct 2002 | A1 |
| 20020183038 | Comstock et al. | Dec 2002 | A1 |
| 20030142651 | Matta et al. | Jul 2003 | A1 |
| 20030187992 | Steenfeldt et al. | Oct 2003 | A1 |
| 20030231586 | Chheda | Dec 2003 | A1 |
| 20040002305 | Byman-Kivivuori et al. | Jan 2004 | A1 |
| 20040002326 | Maher | Jan 2004 | A1 |
| 20040006606 | Marotta et al. | Jan 2004 | A1 |
| 20040049576 | Schweitzer et al. | Mar 2004 | A1 |
| 20040061716 | Cheung et al. | Apr 2004 | A1 |
| 20040128363 | Yamagami et al. | Jul 2004 | A1 |
| 20040174395 | Liu | Sep 2004 | A1 |
| 20040198374 | Bajikar | Oct 2004 | A1 |
| 20040203815 | Shoemake et al. | Oct 2004 | A1 |
| 20040205154 | Dalton et al. | Oct 2004 | A1 |
| 20040210320 | Pandya | Oct 2004 | A1 |
| 20040260630 | Benco et al. | Dec 2004 | A1 |
| 20050028208 | Ellis et al. | Feb 2005 | A1 |
| 20050071319 | Kelley et al. | Mar 2005 | A1 |
| 20050083975 | Macri | Apr 2005 | A1 |
| 20050085222 | Przybilski et al. | Apr 2005 | A1 |
| 20050097248 | Kelley | May 2005 | A1 |
| 20050105632 | Catreux-Erces et al. | May 2005 | A1 |
| 20050135235 | Maruyama et al. | Jun 2005 | A1 |
| 20050136886 | Aamio et al. | Jun 2005 | A1 |
| 20050136920 | Rink et al. | Jun 2005 | A1 |
| 20050159179 | Sainton et al. | Jul 2005 | A1 |
| 20050177715 | Somin et al. | Aug 2005 | A1 |
| 20050198238 | Sim et al. | Sep 2005 | A1 |
| 20050221844 | Trethewey et al. | Oct 2005 | A1 |
| 20050223226 | Sundararajan | Oct 2005 | A1 |
| 20050229246 | Rajagopal et al. | Oct 2005 | A1 |
| 20050249266 | Brown et al. | Nov 2005 | A1 |
| 20060015904 | Marcus | Jan 2006 | A1 |
| 20060041916 | Mcquaide | Feb 2006 | A1 |
| 20060059462 | Yamamoto | Mar 2006 | A1 |
| 20060107036 | Randle et al. | May 2006 | A1 |
| 20060143027 | Jagannathan et al. | Jun 2006 | A1 |
| 20060145815 | Lanzieri et al. | Jul 2006 | A1 |
| 20060171304 | Hill et al. | Aug 2006 | A1 |
| 20060200678 | Yamada et al. | Sep 2006 | A1 |
| 20060239208 | Roberts et al. | Oct 2006 | A1 |
| 20060290519 | Boate et al. | Dec 2006 | A1 |
| 20060294112 | Mandato et al. | Dec 2006 | A1 |
| 20070054616 | Culbert | Mar 2007 | A1 |
| 20070057793 | Alden | Mar 2007 | A1 |
| 20070064604 | Chen et al. | Mar 2007 | A1 |
| 20070124485 | Frost et al. | May 2007 | A1 |
| 20070124756 | Covell et al. | May 2007 | A1 |
| 20070153695 | Gholmieh et al. | Jul 2007 | A1 |
| 20070153729 | Alapuranen | Jul 2007 | A1 |
| 20070161411 | Liao et al. | Jul 2007 | A1 |
| 20070171915 | Toyama et al. | Jul 2007 | A1 |
| 20070192735 | Lehto et al. | Aug 2007 | A1 |
| 20070207750 | Brown et al. | Sep 2007 | A1 |
| 20070223398 | Luo et al. | Sep 2007 | A1 |
| 20070225831 | Sakurada | Sep 2007 | A1 |
| 20070248179 | Hassan et al. | Oct 2007 | A1 |
| 20070254628 | Rybak | Nov 2007 | A1 |
| 20070271525 | Han et al. | Nov 2007 | A1 |
| 20070274488 | Callaghan | Nov 2007 | A1 |
| 20070280332 | Srikanteswara et al. | Dec 2007 | A1 |
| 20070280481 | Eastlake et al. | Dec 2007 | A1 |
| 20080002658 | Soliman | Jan 2008 | A1 |
| 20080016338 | Sun | Jan 2008 | A1 |
| 20080031155 | Korus et al. | Feb 2008 | A1 |
| 20080055399 | Woodworth et al. | Mar 2008 | A1 |
| 20080055423 | Ying et al. | Mar 2008 | A1 |
| 20080063204 | Braskich et al. | Mar 2008 | A1 |
| 20080065238 | Igoe | Mar 2008 | A1 |
| 20080081597 | Cole | Apr 2008 | A1 |
| 20080104170 | Ananthanarayanan | May 2008 | A1 |
| 20080130519 | Bahl et al. | Jun 2008 | A1 |
| 20080130639 | Costa-Requena et al. | Jun 2008 | A1 |
| 20080132201 | Karlberg | Jun 2008 | A1 |
| 20080152098 | Paryzek et al. | Jun 2008 | A1 |
| 20080195861 | Salomone | Aug 2008 | A1 |
| 20080197802 | Onishi et al. | Aug 2008 | A1 |
| 20080207119 | Chang | Aug 2008 | A1 |
| 20080207128 | Mikko | Aug 2008 | A1 |
| 20080227384 | Placzek et al. | Sep 2008 | A1 |
| 20080252419 | Batchelor | Oct 2008 | A1 |
| 20080275993 | Mohammed et al. | Nov 2008 | A1 |
| 20080293375 | Swanburg | Nov 2008 | A1 |
| 20080293419 | Somasundaram et al. | Nov 2008 | A1 |
| 20080311952 | Sugiyama | Dec 2008 | A1 |
| 20080319857 | Dobbins et al. | Dec 2008 | A1 |
| 20090011738 | Sasakura | Jan 2009 | A1 |
| 20090013175 | Elliott | Jan 2009 | A1 |
| 20090039828 | Jakubowski | Feb 2009 | A1 |
| 20090045913 | Nelson et al. | Feb 2009 | A1 |
| 20090055266 | Brody et al. | Feb 2009 | A1 |
| 20090089885 | Noble et al. | Apr 2009 | A1 |
| 20090100080 | Toms et al. | Apr 2009 | A1 |
| 20090103481 | Mahajan et al. | Apr 2009 | A1 |
| 20090106542 | Dubs et al. | Apr 2009 | A1 |
| 20090111378 | Sheynman et al. | Apr 2009 | A1 |
| 20090138715 | Kiao et al. | May 2009 | A1 |
| 20090144622 | Evans et al. | Jun 2009 | A1 |
| 20090154343 | Fitch et al. | Jun 2009 | A1 |
| 20090158394 | Oh et al. | Jun 2009 | A1 |
| 20090170431 | Pering et al. | Jul 2009 | A1 |
| 20090196180 | Bahl et al. | Aug 2009 | A1 |
| 20090210940 | Dean | Aug 2009 | A1 |
| 20090249322 | Sugiyama et al. | Oct 2009 | A1 |
| 20090303902 | Liu et al. | Dec 2009 | A1 |
| 20090319663 | Giles et al. | Dec 2009 | A1 |
| 20100049971 | Oh | Feb 2010 | A1 |
| 20100056124 | Keating et al. | Mar 2010 | A1 |
| 20100081473 | Chatterjee et al. | Apr 2010 | A1 |
| 20100091965 | Ma et al. | Apr 2010 | A1 |
| 20100097830 | Wang | Apr 2010 | A1 |
| 20100100637 | Bowra et al. | Apr 2010 | A1 |
| 20100103850 | Gossain et al. | Apr 2010 | A1 |
| 20100104078 | Henry, Jr. et al. | Apr 2010 | A1 |
| 20100110890 | Rainer et al. | May 2010 | A1 |
| 20100111033 | Erceg et al. | May 2010 | A1 |
| 20100115278 | Shen et al. | May 2010 | A1 |
| 20100121744 | Belz et al. | May 2010 | A1 |
| 20100123598 | Brodersen et al. | May 2010 | A1 |
| 20100123834 | Brodersen et al. | May 2010 | A1 |
| 20100144274 | Mcdowall et al. | Jun 2010 | A1 |
| 20100153762 | Radulescu et al. | Jun 2010 | A1 |
| 20100157167 | Lawther et al. | Jun 2010 | A1 |
| 20100175101 | Devictor et al. | Jul 2010 | A1 |
| 20100186066 | Pollard | Jul 2010 | A1 |
| 20100191576 | Raleigh | Jul 2010 | A1 |
| 20100191847 | Raleigh | Jul 2010 | A1 |
| 20100195580 | Samarasooriya et al. | Aug 2010 | A1 |
| 20100198952 | Kneckt et al. | Aug 2010 | A1 |
| 20100220856 | Kruys et al. | Sep 2010 | A1 |
| 20100226253 | Bugenhagen | Sep 2010 | A1 |
| 20100232332 | Abdel-Kader | Sep 2010 | A1 |
| 20100248599 | Voigt et al. | Sep 2010 | A1 |
| 20100257251 | Mooring et al. | Oct 2010 | A1 |
| 20100284316 | Sampathkumar | Nov 2010 | A1 |
| 20100302005 | Popovski | Dec 2010 | A1 |
| 20100333032 | Lau et al. | Dec 2010 | A1 |
| 20110010433 | Wilburn et al. | Jan 2011 | A1 |
| 20110107388 | Lee et al. | May 2011 | A1 |
| 20110145581 | Malhotra et al. | Jun 2011 | A1 |
| 20110149806 | Verma et al. | Jun 2011 | A1 |
| 20110176463 | Cowan et al. | Jul 2011 | A1 |
| 20110188391 | Sella et al. | Aug 2011 | A1 |
| 20110188419 | Filoso et al. | Aug 2011 | A1 |
| 20110188420 | Filoso et al. | Aug 2011 | A1 |
| 20110202189 | Venkatakrishnan et al. | Aug 2011 | A1 |
| 20110230209 | Kilian | Sep 2011 | A1 |
| 20110238498 | Hassan et al. | Sep 2011 | A1 |
| 20110261001 | Liu | Oct 2011 | A1 |
| 20110274020 | Filoso et al. | Nov 2011 | A1 |
| 20110275316 | Suumaeki et al. | Nov 2011 | A1 |
| 20110280413 | Wu et al. | Nov 2011 | A1 |
| 20110293095 | Ben Ayed | Dec 2011 | A1 |
| 20110320963 | Wong | Dec 2011 | A1 |
| 20110321126 | Maniatopoulos | Dec 2011 | A1 |
| 20120101952 | Raleigh et al. | Apr 2012 | A1 |
| 20120139690 | Gupta et al. | Jun 2012 | A1 |
| 20120144083 | Hassan et al. | Jun 2012 | A1 |
| 20120147268 | Hassan et al. | Jun 2012 | A1 |
| 20120147274 | Hassan et al. | Jun 2012 | A1 |
| 20120147825 | Hassan et al. | Jun 2012 | A1 |
| 20120155643 | Hassan et al. | Jun 2012 | A1 |
| 20120157038 | Menezes et al. | Jun 2012 | A1 |
| 20120158839 | Hassan et al. | Jun 2012 | A1 |
| 20120158947 | Hassan et al. | Jun 2012 | A1 |
| 20120158981 | Desai et al. | Jun 2012 | A1 |
| 20120178429 | Camps Mur et al. | Jul 2012 | A1 |
| 20120197792 | Raleigh | Aug 2012 | A1 |
| 20130033800 | Bartnik et al. | Feb 2013 | A1 |
| 20130097422 | Salomone | Apr 2013 | A1 |
| 20130182614 | Kumar et al. | Jul 2013 | A1 |
| 20130211893 | Bryant et al. | Aug 2013 | A1 |
| 20130322846 | Ferren et al. | Dec 2013 | A1 |
| 20140328251 | Hassan et al. | Nov 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1571341 | Jan 2005 | CN |
| 1592210 | Mar 2005 | CN |
| 1607780 | Apr 2005 | CN |
| 1677975 | Oct 2005 | CN |
| 1929424 | Mar 2007 | CN |
| 1960474 | May 2007 | CN |
| 101021774 | Aug 2007 | CN |
| 101044718 | Sep 2007 | CN |
| 101075820 | Nov 2007 | CN |
| 101094140 | Dec 2007 | CN |
| 101137960 | Mar 2008 | CN |
| 101147308 | Mar 2008 | CN |
| 101179359 | May 2008 | CN |
| 101288063 | Oct 2008 | CN |
| 101657828 | Feb 2010 | CN |
| 1662920 | Apr 2010 | CN |
| 101841637 | Sep 2010 | CN |
| 101867623 | Oct 2010 | CN |
| 2256663 | Dec 2010 | EP |
| 2418809 | Apr 2006 | GB |
| 2001160927 | Jun 2001 | JP |
| 2005004089 | Jan 2005 | JP |
| 2005295286 | Oct 2005 | JP |
| 2005341094 | Dec 2005 | JP |
| 2006050216 | Feb 2006 | JP |
| 2007527156 | Sep 2007 | JP |
| 2008032979 | Apr 2008 | KR |
| 20100038089 | Apr 2010 | KR |
| 0147248 | Jun 2001 | WO |
| 0154342 | Jul 2001 | WO |
| 2004003801 | Jan 2004 | WO |
| 2006131077 | Dec 2006 | WO |
| 2008021855 | Feb 2008 | WO |
| 2008089854 | Jul 2008 | WO |
| 2008127507 | Oct 2008 | WO |
| 2009046869 | Apr 2009 | WO |
| 2010044599 | Apr 2010 | WO |
| 2010132296 | Nov 2010 | WO |
| Entry |
|---|
| Final Office Action dated Nov. 13, 2012 in U.S. Appl. No. 12/748,829, 42 pages. |
| Final Office Action dated Nov. 15, 2010 in U.S. Appl. No. 11/726,862, 21 pages. |
| Final Office Action dated Dec. 26, 2013 in U.S. Appl. No. 12/967,638, 34 pages. |
| Final Office Action dated Dec. 4, 2014 in U.S. Appl. No. 12/960,730, 22 pages. |
| Final Office Action dated Dec. 5, 2014 in U.S. Appl. No. 12/970,069, 21 pages. |
| Final Office Action dated Feb. 11, 2014 in U.S. Appl. No. 12/970,069, 26 pages. |
| Final Office Action dated Feb. 15, 2013 in U.S. Appl. No. 12/967,761, 28 pages. |
| Final Office Action dated Feb. 15, 2013 in U.S. Appl. No. 12/970,069, 23 pages. |
| Final Office Action dated Mar. 11, 2016 in U.S. Appl. No. 12/960,753, 17 pages. |
| Final Office Action dated Mar. 28, 2013 in U.S. Appl. No. 12/967,638, 22 pages. |
| Final Office Action dated Jun. 9, 2016 in U.S. Appl. No. 14/600,477, 9 pages. |
| Final Office Action dated Jul. 12, 2016 in U.S. Appl. No. 14/981,271, 10 pages. |
| Final Office Action dated Jul. 13, 2015 in U.S. Appl. No. 14/318,380, 8 pages. |
| Final Office Action dated Sep. 15, 2011 in U.S. Appl. No. 11/726,862, 24 pages. |
| Final Office Action dated Sep. 20, 2012 in U.S. Appl. No. 11/726,862, 35 pages. |
| Final Office Action dated Sep. 23, 2013 in U.S. Appl. No. 12/970,034, 22 pages. |
| Guide to IEEE 802.11i: Establishing Robust Security Networks;Published Date: Jun. 2006; 155 pages. |
| Haas, Robert et al., “Cost-and Quality-of-Service-Aware Network-Service Deployment,” 2001, 6 pages. |
| 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. |
| 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. |
| Hassan, Amer, “Cognitive Use of Multiple Regulatory Domains”; U.S. Appl. No. 15/233,348, filed Aug. 10, 2016; 57 pages including Preliminary Amendment filed Sep. 21, 2016. |
| 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. |
| 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. |
| 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. |
| How Do You Use a Laptop as a TV Remote Control?; Published Date: Jul. 15, 2008; 6 pages. |
| International Search Report dated Jul. 24, 2012 in PCT Application No. PCT/US2011/065691, Filing Date: Dec. 17, 2011, 11 pages. |
| International Search Report dated Sep. 5, 2012 in PCT Application No. PCT/US2011/065692, Filing Date: Dec. 17, 2011, 8 pages. |
| International Search Report; dated Aug. 31, 2012; Application No. PCT/US2011/064753; Filed Date: Dec. 14, 2011, pp. 8. |
| International Search Report; dated Jul. 31, 2012; Application No. PCT/US2011/065285; Filed Date: Dec. 15, 2011, pp. 9. |
| 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. |
| Kitson, Fred., “Mobile Media Making it a Reality”, In Proceedings of Mobile Computing, vol. 3, Issue 4, Jun. 7, 2005, 17 pages. |
| Klym, et al., “The Evolution of RFID Networks: The Potential for Disruptive Innovation”, In White Paper, Mar. 2006, 20 pages. |
| Lun, Desmond S. et al., “Network Coding with a Cost Criterion,” MIT LIDS Technical Report P-2584, Apr. 2004, 18 pages. |
| Manage Subscription Products & Automate Recurring Billing Operations; Copyright 2008-2009; Retrieved Date: Jan. 12, 2010, 1 page. |
| Manifest Permission; Published Date: Jul. 21, 2004; 19 pages. |
| Meinrath et al.; “Unlicensed ‘White Space Device’ Operations on the TV Band and the Myth of Harmful Interferences”, Mar. 2008, 13 pages. |
| Meinrath et al.; ““White Space Devices” & the Myths of Harmful Interference”, 11 N.Y.U.J. Legis&Pub. Policy 495, 2008, 24 pages. |
| Menezes, Pascal; “Operating System Supporting Cost Aware Applications”; U.S. Appl. No. 13/844,932, filed Mar. 16, 2013; 57 pages. |
| Menezes, Pascal; “Operating System Supporting Cost Aware Applications”; U.S. Appl. No. 14/318,380, filed Mar. 16, 2013; 56 pages. |
| 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. |
| Menezes, Pascal; “Operating System Supporting Cost Aware Applications”; U.S. Appl. No. 15/098,321, filed Apr. 14, 2016; 57 pages. |
| MIST: Cellular Data Network Measurement for Mobile Applications; Published Date: Apr. 24, 2006; 9 pages. |
| Mobile Internet Usage Measurements—Case Finland; Published Date: Apr. 24, 2006; 140 pages. |
| Mohammed, “Web Service for User and Subscription Data Storage”, U.S. Appl. No. 13/772,275, filed Feb. 20. 2013, 49 pages. |
| Motorola, “TV White Space Position Paper,” 2008, 10 pages. |
| Non-Final Office Action dated Jan. 21, 2016 in U.S. Appl. No. 14/863,290, 7 pages. |
| Non-Final Office Action dated Jan. 4, 2013 in U.S. Appl. No. 12/960,730, 14 pages. |
| Non-Final Office Action dated Oct. 2, 2012 in U.S. Appl. No. 12/967,638, 33 pages. |
| Non-Final Office Action dated Oct. 16, 2012 in U.S. Appl. No. 12/970,069, 23 pages. |
| Non-Final Office Action dated Oct. 2, 2014 in U.S. Appl. No. 14/318,380, 5 pages. |
| “International Preliminary Report on Patentability Issued in PCT Application No. PCT/US11/65691”, dated Jun. 18, 2013, 5 Pages. |
| “International Search Report”, dated Aug. 14, 2012, Application No. PCT/US2011/065276, Filed Date: Dec. 15, 2011, pp. 9. |
| “International Search Report”, dated Jul. 12, 2012, Application No. PCT/US2011/063207, Filing Date: Dec. 4, 2011, pp. 9. |
| “International Search Report”, dated Jun. 22, 2012, Application No. PCT/US2011/063340, Filed Date: Dec. 5, 2011, pp. 9. |
| “Notice of Allowance Issued in Chinese Patent Application No. 201110423031.4”, Mailed Date: Jan. 23, 2015, 3 Pages. |
| “Notice of Allowance Issued in Chinese Patent Application No. 201110426179.3”, Mailed Date: Nov. 4, 2014, 3 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/970,069” Mailed Date: Dec. 8, 2015, 3 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/970,069” dated Nov. 12, 2015, 3 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/970,069”, dated Jan. 29, 2016, 4 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/970,069”, dated May 15, 2015, 4 Pages. |
| “Office Action and Search Report Issued in Chinese Patent Application No. 201110400472.2”, dated Oct. 27, 2014, 14 Pages. |
| “Office Action Received in Australia Patent Application No. 2011343700”, dated Jul. 24, 2015, 2 Pages. |
| “Omnidrive”, 2006, retrieved Oct. 26, 2006, 2 pages. |
| “Xdrive”, 2006, retrieved Oct. 26, 2006, 2 pages. |
| “Second Office Action Issued in Chinese Patent Application No. 201110408217.2”, dated May 23, 2014, Filed Date: Dec. 9, 2011, 8 Pages including partial translation. |
| 02 Network Scraps Unlimited Data for Smartphones; Published Date: Jun. 10, 2010; 2 pages. |
| 802.11 Fast BSS Transition (FT) Part 1 of 2; Published Date: Aug. 21, 2007, 5 pages. |
| A New Location Technique for the Active Office—Published Date: 1997, http://citeseerx.ist.nsu.edu/viewdoc/download?doi=10.1.1.20.5052&rep=repl&type=pdf. |
| Advisory Action mailed Jan. 2, 2013 in U.S. Appl. No. 11/726,862, 3 pages. |
| Araujo, Joao Taveira et al., “Towards Cost-Aware Multipath Routing,” AIMS 2009, LNCS 5637, 2009, pp. 207-210. |
| 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. |
| 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. |
| 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. |
| Chinese Office Action dated Jan. 6, 2014 in CN Patent App. No. 201110423068.7, 8 pages including ,concise explanation of relevance and partial translation. |
| Chinese Office Action dated Jan. 7, 2015 in CN Patent App. No. 201110400433.2, 10 pages including partial translation. |
| Chinese Office Action dated Nov. 20, 2013 in CN Patent App. No. 201110423001.3, 18 pages including translation. |
| Chinese Office Action dated Dec. 4, 2013 in CN Patent App. No. 201110408217.2, 12 pages, including Concise Explanation of Relevance and/or partial translation. |
| Chinese Office Action dated Dec. 4, 2013 in CN Patent App. No. 201110423031.4, 26 pages including translation. |
| Chinese Office Action dated Feb. 17, 2014 in CN Patent App. No. 201110400433.2, 12 pages including partial translation. |
| Chinese Office Action dated Feb. 27, 2014 in CN Patent App. No. 201110400472.2, 13 pages including Concise Explanation of Relevance and partial translation. |
| Chinese Office Action dated Jul. 11, 2014 in CN Patent App. No. 201110423031.4, 13 pages, including partial translation and/or concise explanation of relevance. |
| Chinese Office Action dated Jul. 13, 2015 in CN Patent App. No. 201110400433.2, 3 pages. |
| Chinese Office Action dated Aug. 5, 2014 in CN Patent App. No. 201110426179.3, 6 pages, including partial translation. |
| Chinese Office Action dated Sep. 2, 2014 in CN Patent App. No. 201110408217.2, 6 pages, including partial translation. |
| Chinese Office Action dated Sep. 4, 2014 in CN Patent App. No. 201110423001.3, 6 pages, including partial translation. |
| Chinese Office Action dated Sep. 9, 2014 in CN Patent App. No. 201110400433.2, 13 pages including partial translation. |
| Choi, Jongmyung., “RFID Context-aware Systems”, In Proceedings of Sustainable Radio Frequency Identification Solutions, Feb. 1, 2010, pp. 307-331. |
| Cisco Systems, Inc., “802.11 n Wireless Technology Overview,” 2007, 7 pages. |
| Creating Customized Web Experiences with Windows Media Player 9 Series; Published Date: Nov. 2002; 4 pages. |
| CRTDH; An Efficient Key Agreement Scheme for Secure Group Communications in Wireless Ad Hoc Networks; Published Date: 2005, 5 pages. |
| 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. |
| 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. |
| Extended European Search Report dated May 20, 2014 in EP Patent App. No. 11847426.1 , 8 pages. |
| Extended European Search Report dated Jun. 8, 2015 in EP Patent App. No. 11849551.4, 6 pages. |
| Final Office Action dated Jan. 11, 2016 in U.S. Appl. No. 12/970,034, 25 pages. |
| Final Office Action dated Jan. 16, 2015 in U.S. Appl. No. 12/960,753, 12 pages. |
| Final Office Action dated Jan. 28, 2015 in U.S. Appl. No. 12/970,034, 24 pages. |
| Final Office Action dated Jan. 9, 2015 in U.S. Appl. No. 14/318,380, 8 pages. |
| Final Office Action dated Oct. 25, 2013 in U.S. Appl. No. 12/972,104, 10 pages. |
| Final Office Action dated Oct. 6, 2014 in U.S. Appl. No. 12/972,104, 10 pages. |
| Non-Final Office Action dated Oct. 26, 2012 in U.S. Appl. No. 12/967,761, 24 pages. |
| Non-Final Office Action dated Oct. 27, 2014 in U.S. Appl. No. 13/772,275, 14 pages. |
| Non-Final Office Action dated Nov. 6, 2013 in U.S. Appl. No. 12/960,730, 16 pages. |
| Non-Final Office Action dated Nov. 8, 2013 in U.S. Appl. No. 13/844,932, 6 pages. |
| Non-Final Office Action dated Dec. 7, 2016 in U.S. Appl. No. 14/981,271, 5 pages. |
| Non-Final Office Action dated Feb. 1, 2016 in U.S. Appl. No. 14/981,271, 8 pages. |
| Non-Final Office Action dated Feb. 26, 2016 in U.S. Appl. No. 14/600,477, 10 pages. |
| Non-Final Office Action dated Feb. 28, 2014 in U.S. Appl. No. 12/970,159, 22 pages. |
| Non-Final Office Action dated Mar. 31, 2015 in U.S. Appl. No. 14/318,380, 7 pages. |
| Non-Final Office Action dated Apr. 11, 2013 in U.S. Appl. No. 12/972,104, 15 pages. |
| Non-Final Office Action dated Apr. 14, 2011 in U.S. Appl. No. 11/726,862, 22 pages. |
| Non-Final Office Action dated Apr. 23, 2015 in U.S. Appl. No. 14/458,203, 10 pages. |
| Non-Final Office Action dated Apr. 5, 2012 in U.S. Appl. No. 11/726,862, 23 pages. |
| Non-Final Office Action dated May 23, 2014 in U.S. Appl. No. 12/748,829, 30 pages. |
| Non-Final Office Action dated May 23, 2014 in U.S. Appl. No. 12/960,730, 18 pages. |
| Non-Final Office Action dated May 30, 2013 in U.S. Appl. No. 12/970,034, 22 pages. |
| Non-Final Office Action dated Jun. 10, 2015 in U.S. Appl. No. 12/972,104, 10 pages. |
| Non-Final Office Action dated Jun. 18, 2014 in U.S. Appl. No. 12/960,753, 12 pages. |
| Non-Final Office Action dated Jun. 20, 2014 in U.S. Appl. No. 12/972,104, 10 pages. |
| Non-Final Office Action dated Jun. 23, 2010 in U.S. Appl. No. 11/726,862, 16 pages. |
| Non-Final Office Action dated Jun. 30, 2015 in U.S. Appl. No. 12/970,034, 26 pages. |
| Non-Final Office Action dated Jun. 9, 2014 in U.S. Appl. No. 12/970,069, 20 pages. |
| Non-Final Office Action dated Jul. 18, 2014 in U.S. Appl. No. 12/970,034, 24 pages. |
| Non-Final Office Action dated Jul. 29, 2016 in U.S. Appl. No. 14/993,786, 16 pages. |
| Non-Final Office Action dated Aug. 14, 2015 in U.S. Appl. No. 12/960,753, 16 pages. |
| Non-Final Office Action dated Aug. 14, 2013 in U.S. Appl. No. 12/967,638, 30 pages. |
| Non-Final Office Action dated Aug. 16, 2013 in U.S. Appl. No. 12/970,069, 26 pages. |
| Non-Final Office Action dated Aug. 18, 2016 in U.S. Appl. No. 12/972,104, 13 pages. |
| Non-Final Office Action dated Aug. 5, 2014 in U.S. Appl. No. 13/844,932, 7 pages. |
| Non-Final Office Action dated Aug. 9, 2012 in U.S. Appl. No. 12/748,829, 29 pages. |
| Non-Final Office Action dated Sep. 24, 2012 in U.S. Appl. No. 12/964,492, 10 pages. |
| Non-Final Office Action dated Sep. 29, 2014 in U.S. Appl. No. 12/748,829, 30 pages. |
| Non-Final Office Action dated Sep. 4, 2015 in U.S. Appl. No. 14/318,380, 6 pages. |
| Non-Final Office Action dated Sep. 6, 2012 in U.S. Appl. No. 12/972,230, 10 pages. |
| Notice of Acceptance dated Oct. 16, 2015 in AU Pat. App. No. 2011343943, 2 pages. |
| Notice of Allowance dated May 24, 2016 in JP Pat. App. No. 2013-544714, 3 pages. |
| Notice of Allowance dated Jul. 1, 2016 in RU Pat. App. No. 2013127235, 12 Pages w/o English Translation. |
| Notice of Allowance dated Sep. 2, 2016 in U.S. Appl. No. 12/960,753, 9 pages. |
| Notice of Allowance dated Jan. 7, 2016 in U.S. Appl. No. 14/318,380, 8 pages. |
| Notice of Allowance dated Oct. 19, 2015 in U.S. Appl. No. 13/772,275, 8 pages. |
| Notice of Allowance dated Oct. 27, 2016 in U.S. Appl. No. 14/600,477, 8 pages. |
| Notice of Allowance dated Oct. 28, 2015 in U.S. Appl. No. 14/333,386, 12 pages. |
| Notice of Allowance dated Oct. 8, 2015 in U.S. Appl. No. 12/970,069, 9 pages. |
| Notice of Allowance dated Nov. 12, 2014 in U.S. Appl. No. 13/844,932, 8 pages. |
| Notice of Allowance dated Nov. 20, 2012 in U.S. Appl. No. 12/972,230, 9 pages. |
| Notice of Allowance dated Dec. 26, 2013 in U.S. Appl. No. 12/972,230, 8 pages. |
| Notice of Allowance dated Feb. 19, 2014 in U.S. Appl. No. 13/844,932, 8 pages. |
| Notice of Allowance dated Mar. 10, 2014 in U.S. Appl. No. 12/972,230, 8 pages. |
| Notice of Allowance dated Mar. 20, 2013 in U.S. Appl. No. 12/964,492, 9 pages. |
| Notice of Allowance dated Mar. 20, 2015 in U.S. Appl. No. 12/970,069, 11 pages. |
| Notice of Allowance dated Mar. 25, 2013 in U.S. Appl. No. 12/972,230, 8 pages. |
| Notice of Allowance dated Mar. 4, 2013 in U.S. Appl. No. 12/972,230, 7 pages. |
| Notice of Allowance dated Mar. 6, 2014 in U.S. Appl. No. 12/967,638, 11 pages. |
| Notice of Allowance dated Apr. 2, 2014 in U.S. Appl. No. 12/964,492, 9 pages. |
| Notice of Allowance dated May 23, 2016 in U.S. Appl. No. 14/863,290, 12 pages. |
| Notice of Allowance dated May 24, 2016 in JP Patent Application No. 2013-544714, 4 pages. |
| Notice of Allowance dated May 7, 2014 in U.S. Appl. No. 13/844,932, 7 pages. |
| Notice of Allowance dated Jun. 24, 2015 in U.S. Appl. No. 14/458,203, 11 pages. |
| Notice of Allowance dated Jun. 27, 2014 in U.S. Appl. No. 12/970,159, 8 pages. |
| Notice of Allowance dated Jun. 28, 2016 in JP Patent Application No. 2013-544795, 3 pages. |
| Notice of Allowance dated Jun. 8, 2015 in U.S. Appl. No. 13/772,275, 8 pages. |
| Notice of Allowance dated Jul. 12, 2013 in U.S. Appl. No. 12/967,761, 12 pages. |
| Notice of Allowance dated Jul. 24, 2014 in U.S. Appl. No. 12/972,230, 7 pages. |
| Notice of Allowance dated Aug. 20, 2014 in U.S. Appl. No. 12/964,492, 13 pages. |
| Notice of Allowance dated Sep. 17, 2014 in U.S. Appl. No. 12/972,230, 7 pages. |
| Notice of Allowance dated Sep. 3, 2014 in U.S. Appl. No. 12/970,159, 9 pages. |
| Office Action dated Oct. 26, 2015 in JP Pat. App. No. 2013-543239, 13 pages including translation. |
| Office Action dated Nov. 16, 2015 in JP Pat. App. No. 2013-544795, 9 Pages. |
| Office Action dated Nov. 24, 2015 in RU Pat. App. No. 2013127235, 4 Pages w/o English Translation. |
| Office Action dated Apr. 13, 2015 in CN Pat. App. No. 201110400472.04, 14 pages, including partial translation and/or concise explanation of relevance. |
| Office Action dated Aug. 13, 2015 in AU Pat. App. No. 2011343943, 5 pages. |
| Office Action dated Aug. 28, 2015 in JP Pat. App. No. 2013-544714, 5 pages including translation. |
| Office Action dated Apr. 1, 2014 in CN Pat. App. No. 201110423001.3, 8 pages, including partial translation. |
| Office Action dated Apr. 3, 2014 in CN Pat. App. No. 201110417153.2, 15 pages, including partial translation and/or concise explanation of relevance. |
| Office Action dated Aug. 14, 2015 in CN Pat. App. No. 201110417226.8, 6 pages, including partial translation. |
| Office Action dated Dec. 15, 2014 in CN Pat. App. No. 201110417153.2, 8 pages, including partial translation. |
| Office Action dated Feb. 3, 2015 in CN Pat. App. No. 201110417226.8, 7 pages, including partial translation and/or concise explanation of relevance. |
| Office Action dated Jun. 5, 2014 in CN Pat. App. No. 201110417226.8, 14 pages, including partial translation and/or concise explanation of relevance. |
| Pawar, Pravin et al. “Towards Location based QoS-Aware Network Selection Mechanism for the Nomadic Mobile Services,” Dec. 5, 2009, 5 pages. |
| 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. |
| Shared Spectrum, Inc., “Our Technology,” Nov. 2010, 2 pages. |
| Shih, Eugene et al.; Wake on Wireless: An Event Driven Energy Saving; Published Date: Sep. 23-26, 2002; 12 pages. |
| Sridhar, T.; Wi-Fi, Bluetooth and WiMAX; The Internet Protocol Journal, vol. 11, No. 4; Retrieved Date: Sep. 30, 2010, 9 pages. |
| Subscription Management; Copyright 2009; Retrieved Date: Jan. 12, 2010; 2 pages. |
| Symbian Foundation Peer-to-Peer WiFi Inititative (WiFi Direct); Published Date: Sep. 10, 2010, 11 pages. |
| Texas Instruments, MSP430 Ultra-Low-Power MCUs and TI-RFid Devices, 2 pages, 2009. |
| T-mobile “Unlimited” Data Usage; Published Date: Mar. 9, 2010; 6 pages. |
| Torres Service Management Platform; Retrieved Date: Jan. 12, 2010; 2 pages. |
| VAS Subscription Manager; Retrieved Date: Jan. 12, 2010; 1 page. |
| Wi-Fi Alliance: FAQs; Published Date: 2010; 19 pages. |
| Wi-Fi Certified Wi-Fi Direct, Personal, Portable Wi-Fi Technology; Oct. 2010, 14 pages. |
| WinLIRC; Published Date: Mar. 17, 2008; 5 pages. |
| Wireless PC to TV; Retrieved Date: Sep. 9, 2010; 2 pages. |
| Wood, “Kowari: A Platform for Semantic Web Storage and Analysis”, May 27, 2005, 16 pages. |
| Yuan, Y. et al., “Allocating Dynamic Time-Spectrum Blocks in Cognitive Radio Networks,” Sep. 9-14, 2007, 10 pages. |
| Examiner's Answer dated Dec. 27, 2016 in U.S. Appl. No. 12/970,034, 4 pages. |
| Non-Final Office Action dated Apr. 14, 2017 in U.S. Appl. No. 15/098,321, 16 pages. |
| Final Office Action dated Feb. 10, 2017 in U.S. Appl. No. 14/993,786, 14 pages. |
| Non-Final Office Action dated Feb. 10, 2017 in U.S. Appl. No. 15/233,348, 7 pages. |
| European Office Action dated Feb. 13, 2017 in EP Patent App. No. 11847426.1, 7 pages. |
| Final Office Action dated Feb. 2, 2017 in U.S. Appl. No. 12/972,104, 16 pages. |
| Hassan, Amer, “Secure Protocol for Peer-To-Peer Network”; U.S. Appl. No. 15/409,383, filed Jan. 18, 2017; 61 pages including Preliminary Amendment filed Feb. 2, 2017. |
| Final Office Action dated Jun. 20, 2016 in U.S. Appl. No. 14/981,271, 9 pages. |
| Notice of Allowance dated Jun. 19, 2017 in U.S. Appl. No. 15/233,348, 11 pages. |
| Non-Final Office Action dated Aug. 1, 2017 in U.S. Appl. No. 15/409,383, 11 pages. |
| “Notice of Allowance Issued in Chinese Patent Application No. 201110400472.2”, dated Oct. 22, 2015, 4 Pages. |
| “Supplementary Search Report Issued in European Patent Application No. 11848261.1”, dated May 24, 2017, 8 Pages. |
| Notice of Allowance dated Jun. 23, 2017 in U.S. Appl. No. 14/993,786, 9 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170115696 A1 | Apr 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12960753 | Dec 2010 | US |
| Child | 15399728 | US |
