Hotspot power regulation

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077

HOTSPOT POWER REGULATION

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077

HOTSPOT POWER REGULATION

CROSS REFERENCE TO RELATED APPLICATIONS [0001] This application claims the priority of provisional applications 60/772,731 entitled Power Management of an Access Point filed February 13, 2006 and hereby incorporated by reference. Application 60/722,731 is incorporated herein by reference. This application is a continuation in part of application number 10/936,124 entitled Device Cradle filed September 8, 2004. Application 10/936,124 is incorporated herein by reference.

BACKGROUND

[0002] When internet access points are not in use, and imminent use is not likely, it is sometimes useful to lower power consumption, even at the loss of functionality and response time. The state of reduced power consumption is beneficial in general, but is especially useful when the access point and related hardware are battery powered, and therefore have a limited amount of power available.

DESCRIPTION OF THE DRAWINGS [0003] Figs. 1 and 2 illustrate an exemplary block diagrams of environments in which embodiments of the present invention can be implemented.

[0004] Figs. 3-6 are block diagrams showing physical and logical components of a personal hotspot according to an embodiment of the present invention.

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077

[0005] Fig. 7 is an exemplary flow diagram illustrating steps taken in performance of various embodiments of the present invention.

DETAILED DESCRIPTION

[0006] Introduction: Embodiments ofthe present invention allow a user to connect to the internet using a device such as an internet enabled cellular telephone. With a personal hotspot, multiple users of computing devices such as lap top computers, desktop computers, and personal digital assistants (PDAs) can access the internet simultaneously through the data capabilities of that cellular telephone. The combination of the personal hotspot and the internet enabled cellular telephone can provide an internetconnected wireless network anywhere that there is cellular data coverage. [0007] A personal hotspot and accompanying internet enabled cellular telephone may each be battery powered. Further, energy from the battery of one device may be used to power both. Various embodiments described below operate to selectively regulate the power made available to and consumed by each device.

[0008] Environment: Fig. 1 illustrates exemplary environment 1 in which various embodiments of the present invention may be implemented. Environment 1 includes personal hotspot 10 and client devices 12, 14, and 16 and local link 18. Personal hotspot 10, discussed in more detail later, represents generally a device capable or routing network communications between client devices 12, 14, and 16 and internet 26 via a data exchanger 20 . Client devices 12, 14, and 16 represent generally any computing devices capable of communicating with personal hotspot 10.

[0009] Local link 18 interconnects personal hotspot 10 and client devices 12, 14, 16. Local link 18 represents generally a cable, wireless, or remote link via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between devices 10, 12, 14, and 16. The path followed by link 18 between devices 10, 12, 14, and 1 in the schematic view of Fig. 1 represents the logical

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 communication path between these devices, not necessarily the physical path between the devices. Devices 10, 12, 14, and 16 can be connected at any point and the appropriate communication path established logically between the devices.

[0010] Environment 1 also includes data exchanger 20 and service provider 22. Data exchanger 20 represents generally and combination of hardware and/or programming that can be utilized by personal hotspot 10 to connect to a remote network such as the internet. While illustrated as an internet enabled cellular telephone, data exchanger 20 is not so limited. Other examples include but are not limited to DSL modems and cable modems. [0011] Service provider 22 represents generally any infrastructure configured to provide internet related data services to subscribers such as an owner of data exchanger 20. For example, where data exchanger 20 is an internet enabled cellular telephone, service provider 22 may be a cellular telephone service provider capable of providing voice and data services to subscribers allowing access to internet 26. Where data exchanger 22 is a DSL or cable modem, service provider 22 may be a more traditional internet service provider (ISP) providing data access to internet 26.

[0012] Remote link 24 interconnects data exchanger 20 and service provider 22 and represents generally any combination of a cable, wireless, or remote connection via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between data exchanger 20 and service provider 22.

Remote link 30 may represent an intranet, an internet, or a combination of both.

[0013] In the embodiment illustrated in environment 1, device link 28 interconnects personal hotspot 10 and data exchanger 20. Device link 28 represents generally any combination of a cable, wireless, or remote connection via a telecommunication link, an infrared link, a radio frequency link, or any other connector or system that provides electronic communication between devices 10 and 20. As examples, device link 28

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 may incorporate a physical USB cable or radio waves carrying Bluetooth communications.

[0014] Communication between client devices 12, 14, and 16 and internet 26 is dependent upon personal hotspot 10. Personal hotspot 10, as discussed below with respect to Figures 3-6, includes components capable of power regulation for personal hotspot 10 and data exchanger 20.

[0015] Fig. 2 illustrates another exemplary environment 2 in which various embodiments of the present invention may be implemented. In the example of Fig. 2, data exchanger 20 (not shown) and personal hotspot 10 are incorporated within the same device. Device link 32 (shown in Fig. 1) is eliminated and replaced with internal connections. In such a scenario, data exchanger may take the form of a card such as a PCMCIA card that can be inserted into a slot provided by personal hotspot 10. Alternatively, data exchanger 20 may be fully integrated into personal hotspot 10

[0016] Personal Hotspot: Fig. 3 is a block diagram illustrating physical and logical components of personal hotspot 10. As described above, personal hotspot 10 represents generally any combination of hardware and/or programming capable functioning as a router for directing network communications between client devices and the internet via a data exchanger such as an internet enabled cellular telephone, DSL modem, or cable modem.

[0017] In the example of Fig. 3 personal hotspot 10 includes local network interface 30 and data exchanger interface 32. Local network interface 30 represents generally any combination of hardware and/or program instructions capable of supplying a communication interface between personal hotspot 10 and client devices 12, 14, and 16 shown in Figures 1 and 2. Data exchanger interface 32 represents any combination of hardware and/or programming enabling data to be communicated between personal hotspot 10 and a data exchanger 20 shown in Figs 1. For example, interfaces 30 and 32 may include a transceiver operable to exchange network communications utilizing a wireless protocol such as ultrawideband

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 (UWB), Bluetooth, or 802.11. Alternatively, interfaces 30 and 32 may include physical ports or other physical connection points enabling wired communication.

[0018] Personal hotspot 10 also includes connector 34, router 36, web server 38, power manager 40, and power supply 42. Power supply 42 represents generally any hardware capable of supplying power to personal hotspot 10. Power supply 42, for example, could be a battery or a transformer capable of converting household current into a form useable by personal hotspot 10. Personal hotspot 10 may in turn utilize power supply 42 to power data exchanger 20 via data exchanger interface 32. For example, data exchanger interface may be a wired USB interface such that personal hotspot 10 serves as the master device and data exchanger serves as a USB client device. In this manner, data exchanger interface 32 can provide a typical five volt USB power supply to data exchanger 20. In other embodiments, personal hotspot 10 might serve as a USB client device with data exchanger 20 serving as the master. In this scenario, data exchanger 20 may supply power to personal hotspot 10. In other embodiments, each device may be capable of powering the other.

[0019] Connector 34 represents generally any combination of hardware and/or programming for sending a signal to data exchanger 20 to connect to establish a data connection with service provider 22 so that access can be made to internet 26. For example, where a data exchanger 20 is a cellular telephone, connector 34 may send a signal causing the cellular telephone to establish such a data link with service provider 22.

[0020] Router 36 represents generally any combination of hardware and/or programming for routing network communication received through network interface 30 to be transmitted by data exchanger 20 to internet 26. Router 36 is also responsible for routing inbound network communications received from internet 26 and directed via network interface 30 to a specified client device 12, 14, or 16. Outbound and inbound network communications, for example can be an IP (internet Protocol) packets directed to a target on

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 internet 26 or to a particular network device 12, 14, or 16 on a local area network.

[0021] Web server 38 represents generally any combination of hardware and/or programming capable of serving interfaces such as web pages to client devices 12, 14, and 16. Such web pages may include web pages that when displayed by a network device allows a user to provide or otherwise select settings related to the operation of personal hotspot 10.

[0022] Power manager 40, discussed in more detail below with respect to Fig. 4, represents generally any combination of hardware and/or programming capable of selectively regulating the power state of personal hotspot 10 and data exchanger 20. The power state of a given device relates to an operational mode of that device where that mode causes the device to consume a certain amount energy. This energy may be provided by power source 42 and a power source such as a battery integrated in data exchanger 20. In many cases, a full operational mode consumes the most energy while a “sleep” mode consumes the least except when the device is powered off.

[0023] Fig. 4 is a block diagram illustrating physical and logical components of power manager 40. In this example, power manager 40 is shown to include configuration data 44, user interface data 46, power monitor 48, activity monitor 50, and regulator 52.

[0024] Configuration data 42, discussed in more detail below with respect to Fig. 5, represents generally a collection of information used by power manager 40 to select and set the operational states for personal hotspot 10 and data exchanger 20. As discussed above, different operational states consume different levels of power. User interface data 46, discussed in more detail below with respect to Fig. 6, represents data used to present a client device with user interfaces such as web pages or other content that can be served to a client device. Such user interfaces can be informational or they can provide controls for selecting an operational state.

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077

[0025] Power monitor 48 represents generally any combination of hardware and/or programming capable of monitoring the power states of personal hotspot 10 and data exchanger 20. Power monitor 48 may record monitored power states in configuration data 44. The power state of a given device can indicate that it is functioning on battery power or on household current. If operating on battery power, the power state can indicate a remaining power level for that battery. For example, power monitor 48 may be responsible for monitoring battery levels for personal hotspot 10 and data exchanger 20. With respect to data exchanger 20, power monitor 40 may use data exchanger interface 32 (Fig. 3) to interrogate data exchanger 20 as to its battery level. Power monitor 48 may have access to a library of commands specific to data exchanger 20 that can be issued via device link 28 (Fig. 1 ). One or more of those commands may be for requesting data identifying whether or not the data exchanger is operating on battery power as well as a battery level. Low battery levels can indicate that personal hotspot 10 and data exchanger 20 can be placed in operational modes that require less power.

[0026] Activity monitor 50 represents generally any combination of hardware and/or programming capable of monitoring activity levels with respect to personal hotspot 10 and data exchanger 20. Activity monitor 50 may record monitored activity levels in configuration data 44. Referring back to Fig. 1, personal hotspot 10 is used to establish a private local network among client devices 12, 14, and 16. Activity monitor 50 may be responsible for monitoring activity levels in the form of local network communications between client devices 12, 14, and 16 and personal hotspot 10. In doing so, activity monitor may identify periods of inactivity with respect to the local private network. Such periods of inactivity may indicate that personal hotspot 10 can be placed in an operational mode that consumes less power. [0027] Activity monitor 50 may also be responsible for monitoring activity levels in the form of data communications passing to and from data exchanger 22 via remote link 24. This may be accomplished by monitoring

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 data communications passing between personal hotspot 10 and data exchanger 20 via device link 28. Alternatively, activity monitor 48 may have access to a library of commands specific to data exchanger 20 that can be issued via device link 28 (Fig. 1 ). One or more of those commands may be for requesting data identifying periods of activity or inactivity with respect to data communications via remote link 24. Periods of inactivity may indicate that data exchanger 20 can be placed in an operational mode that consumes less power.

[0028] Regulator 52 represents generally any combination of hardware and/or programming capable of regulating the power consumption of personal hotspot 10 and data exchanger 20. Regulator 52 does so by altering the operational states of those devices based on the power states and activity levels monitored by power monitor 48 and activity monitor 50 and recorded in configuration data 44.

[0029] As examples, regulator 52 may examine configuration data 44 and cause personal hotspot 10 or data exchanger 20 to enter a sleep mode or to power off following a monitored period of inactivity that exceeds a predetermined threshold duration or when a power state falls below threshold level. Where data exchanger 20 is being powered by personal hotspot 10, regulator 52 may cause data exchanger 20 to enter a selfpowered mode when power state of personal hotspot 10 falls below a threshold level. Similarly, regulator 52 may cause personal hotspot 10 to power data exchanger 20 when a power state of personal hotspot 10 indicates that personal hotspot 10 is being powered by a household current. Regulator 52 may have access to a library of commands specific to data exchanger 20 that can be issued via device link 28 (Fig. 1 ). One or more of those commands may be for instructing data exchanger to alter its power source. Alternatively, regulator may simply instruct data exchanger interface 32 to power or not power data exchanger 20.

[0030] Regulator 52 may perform some of its responsibilities without user confirmation. Other actions may be taken based on a user selected option.

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077

For example, regulator 52 may determine that a particular predetermined threshold has been met. Following this determination, regulator 52 may cause web server 38 to access user interface data 46 and return content to a client device 12, 14, or 16. The returned content may include controls for selecting an action to be taken by regulator 52. Instead it may include informational content advising a user of an imminent action to be taken by regulator 52. For example, the returned content may warn the user that personal hotspot 10 or data exchanger 20 will be powered off unless the user takes steps to power one or both devices using household current. [0031] Fig. 5 is a block diagram illustrating the logical elements of configuration data 44. In the example of Fig. 5, configuration data 44 includes power state data 54, activity data 56, action data 58, and threshold data 60. Power state data 54 represents power state information monitored and recorded by power monitor 48. Activity data 56 represents activity level information monitored and recorded by activity monitor 50.

[0032] Action data 58 represents various power regulation actions to be taken by regulator 52 to regulate the operational states of personal hotspot 10 and data exchanger 20. Action data 58, for example, may include a series of records where each record identifying one or more power regulation actions to be taken by regulator 52. Such actions include altering operational states to reduce or increase the power made available to personal hotspot 10 and data exchanger 20. Other actions include causing user interfaces to be returned to a user.

[0033] Threshold data 60 represents predetermined threshold values corresponding to power state data 54 and activity data 56. For example, threshold data 60 may include a series of records where each record includes an entry identifying a threshold power state, an entry identifying a threshold activity level such as an inactivity duration, and an entry identifying a particular power regulation action record in action data 58. In this scenario, regulator 52 can identify a record in threshold data 60 whose predetermined threshold values are being met by the values recorded in

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 power state data 54 and activity data 56. For example, a given record may contain an entry specifying a power level and another entry identifying a period of inactivity. Upon identifying such a record in threshold data 60, regulator 52 identifies an associated action record in action data 68. That action record identifies a particular power regulation action. Such an action might involve increasing power, altering a power source, powering off, placing in a sleep mode, or causing a particular user interface to be communicated to a client device 12, 14, or 16. Regulator 52 can then implement the appropriate power regulation action.

[0034] Fig. 6 is a block diagram illustrating the logical elements of user interface data 44. In the example of Fig. 6, user interface data includes informational content 62, action content 64, and configuration content 66. Informational content 68 represents web pages or other content that can identify a current power state and activity level and any recommended actions to be taken by a user such as plugging personal hotspot 10 or data exchanger 20 into a wall socket.

[0035] Action content 64 represents web pages or other content having user accessible controls for specifying particular power regulation actions to be taken to alter the operational mode of personal hotspot 10 and data exchanger 20. Configuration content 72 represents web pages or other content used to update configuration data 44.

[0036] Operation: The operation of embodiments of the present invention will now be described with reference to Fig. 7. Fig. 7 is an exemplary flow diagram that helps illustrate actions taken to regulate the power state of personal hotspot 10 and data exchanger 20. The actions include monitoring device activity levels and power states (steps 68 and 70). Step 68, for example, may be performed by activity monitor 50 while step 70 may be performed by power state monitor 48. Step 68 can involve recording the monitored activity levels such as inactivity durations for personal hotspot 10 and data exchanger 20 in configuration data 44. Step 70 can involve

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 recording the monitored power states for personal hotspot 10 and data exchanger 20 in configuration data 44.

[0037] The monitored power states and device activity levels are compared with predetermined threshold levels (step 72). As discussed the predetermined threshold levels can relate to a particular power state such as a battery level or power source. Predetermined threshold levels can also relate to durations of device inactivity for personal hotspot 10 and data exchanger 20. Step 72, for example, may be performed by regulator 52 which accesses configuration data 44 and compares recorded power states and activity levels with the threshold values in threshold data 60.

[0038] It is determined if a monitored device activity level and/or a monitored power state meet or meets a threshold value or values (step 74). Step 74 may be accomplished, by regulator 52 identifying a record in threshold data 60 that specifies threshold values being met by the activity levels and power states recorded in activity data 56 and power state data 54. If regulator 52 cannot identify such a record meaning that no thresholds are being met, the process repeats with step 68. If a threshold is being met, a power regulation action is identified (step 76). Continuing with the example, step 76 can involve regulator 52 identifying a power regulation action record in action data 58 that is associated with a threshold record whose threshold values are being met. From that identified action record, regulator 52 identifies the power regulation action.

[0039] The identified power regulation action is then initiated (step 78).

Step 78 can involve regulator 52 implementing a particular action with or without user interaction. Such actions can include altering the operational states of personal hotspot 10 and data exchanger 20. Alterations, as already discussed, can include increasing or reducing available power as wells as changing power sources for a given device. Alterations can include placing a device in a full operational mode, a limited operational mode, a sleep mode, powering off the device, or cause one device to start or stop powering the other. Other power regulation actions can include causing user

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 interfaces to be communicated to a client device 12, 14, or 16. Such user interfaces can be informational or can allow a user to select a particular action to be taken by regulator 52 to alter a power state of personal hotspot 10 or data exchanger 20.

[0040] Conclusion: The schematic diagrams of Figs. 1 and 2 illustrate exemplary environments in which embodiments of the present invention may be implemented. Implementation, however, is not limited to these environments. The diagrams of Figs. 3-6 show the architecture, functionality, and operation of various embodiments of the present invention. A number of the blocks are defined as programs. Each of those blocks may represent in whole or in part a module, segment, or portion of code that comprises one or more executable instructions to implement the specified logical function(s). Each block may represent a circuit or a number of interconnected circuits to implement the specified logical function(s).

[0041] Also, the present invention can be embodied in any computerreadable media for use by or in connection with an instruction execution system such as a computer/processor based system or an ASIC (Application Specific Integrated Circuit) or other system that can fetch or obtain the logic from computer-readable media and execute the instructions contained therein. Computer-readable media can be any media that can contain, store, or maintain programs and data for use by or in connection with the instruction execution system. Computer readable media can comprise any one of many physical media such as, for example, electronic, magnetic, optical, electromagnetic, or semiconductor media. More specific examples of suitable computer-readable media include, but are not limited to, a portable magnetic computer diskette such as floppy diskettes or hard drives, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory, or a portable compact disc.

[0042] Although the flow diagram of Fig. 7 shows a specific order of execution, the orders of execution may differ from that which is depicted.

For example, the order of execution of two or more blocks may be scrambled

CA 02642002 2008-08-08

WO 2007/095544

PCT/US2007/062077 relative to the order shown. Also, two or more blocks shown in succession may be executed concurrently or with partial concurrence. All such variations are within the scope of the present invention.

[0043] The present invention has been shown and described with reference to the foregoing exemplary embodiments. It is to be understood, however, that other forms, details and embodiments may be made without departing from the spirit and scope of the invention that is defined in the following claims.