The present disclosure is related generally to mobile-device power usage and, more particularly, to a system and method for enhancing mobile-device power conservation through network selection.
Mobile wireless communication devices such as cellular and other wireless phones, tablets, watches, and so on are ubiquitous in large part because of their mobility. Certainly such devices have extensive capabilities, and these capabilities seem to be constantly increasing. However, a large stationary system will almost always have a greater computing capability than a small mobile device. Thus, the primary benefit of mobile devices remains their mobility.
In this connection, the usable mobility of such devices is directly related to the extent to which wireless communications are available. The availability of wireless communications is sometimes referred to as coverage. An absence of coverage can cause dropped calls, failures to load media or applications, missed messages, and so on. However, not only does coverage affect connectivity, it also directly impacts the power cost of communications. For example, in an area of poor coverage due to a distant base station, the power cost of transmitting over the required distance may be much greater than the power cost would be if the base station were closer.
The present disclosure is directed to a system that may conserve device battery resources by strategic coverage tracking and network selection. However, it should be appreciated that any such benefit is not necessarily a limitation on the scope of the disclosed principles or of the attached claims, except to the extent expressly noted in the claims. Additionally, the discussion of technology in this Background section is merely reflective of inventor observations or considerations and is not intended to be admitted or assumed prior art as to the discussed details. Moreover, the identification of the desirability of a certain course of action is the inventors' observation, not an art-recognized desirability.
While the appended claims set forth the features of the present techniques with particularity, these techniques, together with their objects and advantages, may be best understood from the following detailed description taken in conjunction with the accompanying drawings of which:
Before presenting a detailed discussion of embodiments of the disclosed principles, an overview of certain embodiments is given to aid the reader in approaching the later discussion. As noted above, the quality of wireless connectivity available to a mobile device can affect the power required of the device to engage in wireless communications. To accommodate varying coverage conditions, a wireless device may investigate to determine whether a wireless communication mode different from the one currently being used by the device offers better coverage. If so, the device may switch and start using this alternative communication mode.
The alternative mode may represent an entirely different communication technology. For example, a local WiFi network may provide better connectivity than a cellular network that a mobile device is currently using. Alternatively, the alternative mode may include a different provider of the same technology. For example, a new cellular provider may provide better coverage at the current location than the current cellular provider.
However, searching for better communications modes and frequently switching among communications modes are both energy-intensive processes that consume substantial amounts of battery power on the device. To minimize this power drain, a coverage map may be used to eliminate the need to investigate alternative modes in real time. By noting its own geographical location (e.g., by means of a Global Positioning System (“GPS”)) and then referencing an appropriate coverage map, a device is able to select a best communication mode for its present location. The device can then switch to that mode without expending the power to search for alternative modes.
Alternatively, the coverage map can reveal that the mode currently used by the device, though of less than optimal quality, is no worse than the alternatives. This again saves the device from expending the power that would have been needed to independently investigate other available modes in real time, and the device does not switch modes.
In an embodiment of the disclosed principles, coverage maps are generated and provided that take into direct consideration the power needs of different types of devices with different capabilities in different stages of power use. For example, a device that is low on power can consult such a map to determine, given its current battery level, its communications needs, and its current geographic location, what communication mode it should be using. Herein, this type of coverage map is sometimes referred to as a “power-drain map.”
In an embodiment, wireless devices collect information to create the coverage map and share collected information with a map server. The coverage map includes information specific to a type of communication device and to each communication mode usable by that type of device in a further embodiment. If a particular communication mode is usable by a device but has been disabled, then the coverage map, as presented to this device, can be altered to remove references to the disabled mode. Alternatively, the user is alerted that this currently disabled mode is preferable to other enabled modes, such that the user may consider enabling this mode.
When a device uses the power-drain map (whether earlier created by itself or retrieved from a map server), it can consult the map informed by its current battery level and communications needs and then apply an appropriate remedy. For example, it might be advisable based on the power-drain map to search for an alternative communication mode. Alternatively, the power-drain map may indicate that no alternative communication mode is viable at this location. The power-drain map may even guide the user of the device to a nearby location with better connectivity or further communication-mode options.
In extreme cases, consulting with the map may lead the device (or its user) to consider turning off data transmission or even all transmission (i.e., by going into airplane mode). On the other hand, the current connectivity may be so good relative to upcoming locations that the device is advised to take advantage of the current connectivity by preemptively downloading as much data as possible before the device leaves the present area of good connectivity.
Regarding the comparison of upcoming locations to the device's current locations, in an embodiment, the device's predicted future location is taken into account when generating current guidance for device communication and connectivity behavior. In one aspect of this behavior, the device's predicted path can be compared against the coverage map to take preemptive action as needed. The preemptive download when in a location having good connectivity is an example of this.
Having considered a high level overview of the disclosed principles and turning now to a more detailed discussion in conjunction with the attached figures, techniques of the present disclosure are illustrated as being implemented in a suitable environment. The following description is based on embodiments of the disclosed principles and should not be taken as limiting the claims with regard to alternative embodiments that are not explicitly described herein. Thus, for example, while
The schematic diagram of
In the illustrated embodiment, the components of the user device 110 include a display screen 120, applications 130, a processor 140, a memory 150, one or more input components 160 such as speech- and text-input facilities, and one or more output components 170 such as text- and audible-output facilities, e.g., one or more speakers.
The one or more input components 160 of the device 110 also include a sensor or system that measures or monitors a condition associated with wireless network connectivity or power drain. The condition may be, for example, power drain per unit time, power drain per unit data during transmission or receipt of data, and the like, sensed parameters such as device orientation relative to the earth, and relative to the user (e.g., pocket location or hand grip), and communication network parameters such as transmission frequency, band or channel grouping, bandwidth allocation, and modulation format. Similarly, the device 110 also includes a sensor configured for determining location of the device such as a GPS module and associated circuitry and software.
The processor 140 can be any of a microprocessor, microcomputer, application-specific integrated circuit, or the like. For example, the processor 140 can be implemented by one or more microprocessors or controllers from any desired family or manufacturer. Similarly, the memory 150 may reside on the same integrated circuit as the processor 140. Additionally or alternatively, the memory 150 may be accessed via a network, e.g., via cloud-based storage. The memory 150 may include a random-access memory. Additionally or alternatively, the memory 150 may include a read-only memory (i.e., a hard drive, flash memory, or any other desired type of memory device).
The information that is stored by the memory 150 can include program code associated with one or more operating systems or applications as well as informational data, e.g., program parameters, process data, etc. The operating system and applications are typically implemented via executable instructions stored in a non-transitory computer-readable medium (e.g., memory 150) to control basic functions of the electronic device 110. Such functions may include, for example, interaction among various internal components and storage and retrieval of applications and data to and from the memory 150.
The illustrated device 110 also includes a network interface module 180 to provide wireless communications to and from the device 110. The network interface module 180 may include multiple communications interfaces, e.g., for cellular, WiFi, broadband, and other communications. A power supply 190, such as a battery, is included for providing power to the device 110 and its components. In an embodiment, all or some of the internal components communicate with one another by way of one or more shared or dedicated internal communication links 195, such as an internal bus.
Further with respect to the applications, these typically utilize the operating system to provide more specific functionality, such as file-system service and handling of protected and unprotected data stored in the memory 150. Although many applications may govern standard or required functionality of the user device 110, in many cases applications govern optional or specialized functionality, which can be provided, in some cases, by third-party vendors unrelated to the device manufacturer.
Finally, with respect to informational data, e.g., program parameters and process data, this non-executable information can be referenced, manipulated, or written by the operating system or an application. Such informational data can include, for example, data that are preprogrammed into the device during manufacture, data that are created by the device, or any of a variety of types of information that are uploaded to, downloaded from, or otherwise accessed at servers or other devices with which the device 110 is in communication during its ongoing operation.
In an embodiment, the device 110 is programmed such that the processor 140 and memory 150 interact with the other components of the device 110 to perform a variety of functions. The processor 140 may include or implement various modules and execute programs for initiating different activities such as launching an application, transferring data, and toggling through various graphical user-interface objects (e.g., toggling through various icons that are linked to executable applications).
As noted above in overview, a mobile communication device such as a mobile phone operating in accordance with an embodiment of the disclosed principles can operate with greater energy efficiency by using a power-drain map. In particular, the device may use the map to more efficiently select communication modes and optionally to predict future communication modes and modify device communication behavior accordingly.
Before describing the process flows involved in these techniques, an example network environment is described for common reference later. In particular, the simplified network diagram of
The methodology used to predict the device's motion may include any suitable prediction technique, including techniques based on known routes (e.g., learned user routes or known roads), device long-term history, device trajectory, user-calendar data, and so on.
The illustrated network environment 200 includes network 205, network 206, and network 207. In the example, the coverage areas of all three networks 205, 206, 207 overlap. Moreover, the coverage area of network 207 is entirely contained within the coverage area of network 206 in the illustrated example. As the device 201 traverses the overall area, it is first within the coverage areas of networks 205 and 206, moves into the coverage area of network 207, and then moves out of all coverage areas except that of network 206.
Given this progression, a series of example power-drain map entries is shown in
Having predicted the illustrated path and retrieved at least the illustrated power-drain map entries, the mobile device 201 may choose to modify its behavior to most efficiently utilize its remaining power. For example, the device 201 (e.g., using a network selection and connection utilization application or routine run by the device processor) may decide to delay a power-intensive download at position 202. Instead, the device may connect to network 207 once at position 203 and execute the needed download or downloads.
In an embodiment, network 207 is of a type that the device 201 supports but that is currently (at position 202) disabled on the device 201. Upon predicting the illustrated path, retrieving the illustrated power-drain map entries, and determining that a download in position 203 will be more power efficient than a download at position 202, the mobile device 201 may enable the network type associated with network 207.
Alternatively, the device 201 may request that the user enable the network type associated with network 207. However, if the device battery level is high, then the device 201 may opt for a less efficient immediate download in the interest of eliminating any delay in the user experience. Thus, the device battery level is also a consideration in determining what remedy to effectuate based on the map data. Other options, alternatives, and variations will become apparent.
In yet another alternative embodiment, if a particular communication mode is usable by a device but has been disabled, then the coverage map, as presented to this device, is altered to remove data for the disabled mode.
The coverage map data such as those shown in
When a device uses a power-drain map (whether earlier created by itself or retrieved from a map server), it can consult the map informed by its current battery level and communications needs and then apply an appropriate remedy. For example, it might be advisable based on the power-drain map to search for an alternative communication mode. Alternatively, the power-drain map may indicate that no alternative communication mode is viable at this location. The power-drain map may even guide the user of the device to a nearby location with better connectivity or to further communication mode options.
In extreme cases, consulting with the map may lead the device (or its user) to consider turning off data transmission or even all transmission (i.e., by going into airplane mode). On the other hand, the current connectivity may be so good relative to upcoming locations that the device is advised to take advantage of the current connectivity by preemptively downloading as much data as possible before the device leaves the present area of good connectivity, similar to the delayed download discussed above.
Regarding the comparison of upcoming locations to the device's current locations, in an embodiment, the device's predicted future location is taken into account when generating current guidance for device communication and connectivity behavior. In one aspect of this behavior, the device's predicted path can be compared against the coverage map to take preemptive action as needed. The preemptive download when in a location having good connectivity is an example of this.
The flowchart of
The device determines its geographical location at stage 402. In an embodiment, this step is accomplished via GPS, although it will be appreciated that other methodologies such as WiFi localization may be used.
The device accesses the map data associated with its determined current position at stage 403. In keeping with the foregoing discussion, the map data may show condition data associated with the particular device and the determined position, e.g., an expected power drain associated with each available mode of communication. Modes of communication may include one or more cellular connections, one or more WiFi connections, or one or more other types of connections. Condition data may also include present or predicted network condition data such as operating channel or band and modulation format. Condition data may also include sensor data or conditions inferred from sensor data such as the device orientation with respect to the earth or the device position relative to the body of the user or a user grip. At stage 404, the device determines its remaining battery power, also referred to as battery-charge level.
Based on the map data and optionally on the current battery-charge level of the device, the device chooses and implements a course of action in stage 405. Although certain types of actions were discussed above, a more extensive though not exhaustive listing of options includes altering an interval of scanning for communications modes usable by the device, turning roaming off, disabling switching of communications modes by the device, switching to a different communications mode usable by the device, altering public land mobile network preference thresholds, turning off data reception, preemptively downloading data, and turning on airplane mode. Furthermore, options may include informing the user of potentially advantageous changes in device orientation, position, or grip.
Although the process 400 is described as taking place at the device, it will be appreciated that the process 400 may be executed partially or entirely elsewhere. For example, the map server may execute some or all of the process 400, with the understanding that the device may need to supply its location or data usable to determine its location.
As noted above, device-path prediction is used as an additional factor in an embodiment of the disclosed principles to determine a course of action for the device. A flowchart of an example process 500 in accordance with such an embodiment is shown in
The device determines its geographical location at stage 502, e.g., via GPS or other suitable methodology. At stage 503, the device predicts its future path within a certain frame of time or distance. For example, the prediction may be executed for a period of ten minutes or a distance of a quarter mile.
The path prediction may be based on any suitable factors, including, for example, current location of the device, current direction of movement of the device, a geographical map, observations of past behavior of the device, observations of past behavior of a user of the device, stored preferences, observations of a plurality of devices, observations of a plurality of users of devices, a time of day, and a current weather condition. Moreover, the prediction may actually be received from a device distinct from, and perhaps remote from, the wireless communications device itself.
The device accesses the map data associated with its determined current and predicted positions at stage 504. As with the prior embodiment, the device may determine its remaining battery power at stage 505. Based on the map data and optionally the current battery-charge level of the device, the device chooses a path of action in stage 506, choosing and implementing a remedy. Unlike the non-predictive case, options in the predictive case include time-shifting options.
Although the process 500 is described as taking place at the device, it will be appreciated that the process 500 may be executed partially or entirely elsewhere. For example, the map server may execute some or all of the process 500, with the understanding that the device may need to supply its location or data usable to determine its location.
As noted above, the power-drain map may be created by the device or the map server. In the latter case, the map server receives an association of a measured condition (wireless network connectivity or power drain for example) and a geographical location from a wireless communications device. The server progressively builds the power-drain map comprising the associated measured condition and location. The condition may relate to a communication mode usable by the wireless communications device. The condition may relate to the device orientation relative to the earth. The condition may also relate to the device orientation or position relative to a user.
In an embodiment, the map includes conditions and locations for each of a plurality of communication modes usable by wireless communications devices. The map may also include information associated with a model of the wireless communication device. For example, a power-drain model may be applied assuming a linear discharge of the device battery with increasing drain. Similarly, a more complex model may assume additional resistive losses with increased drain.
Although the map server architecture is not critical, in an embodiment, the map server includes a communications interface configured to receive the association of a measured condition and a geographical location, as well as a processor configured to build the map comprising the associated measured condition and geographical location.
In view of the many possible embodiments to which the principles of the present disclosure may be applied, it should be recognized that the embodiments described herein with respect to the drawing figures are meant to be illustrative only and should not be taken as limiting the scope of the claims. Therefore, the techniques as described herein contemplate all such embodiments as may come within the scope of the following claims and equivalents thereof.
This application is a continuation of and claims priority to U.S. patent application Ser. No. 14/457,190, filed on Aug. 12, 2014, which, in turn, claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Patent Application 61/916,473, filed on Dec. 16, 2013, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
2499663 | Medlar | Mar 1950 | A |
2529038 | Medlar et al. | Nov 1950 | A |
2563234 | Godshalk et al. | Aug 1951 | A |
2627060 | Berg | Jan 1953 | A |
2637836 | Kendall et al. | May 1953 | A |
3678363 | Ringle | Jul 1972 | A |
4061956 | Brown et al. | Dec 1977 | A |
4082097 | Mann et al. | Apr 1978 | A |
4629965 | Fallon et al. | Dec 1986 | A |
4649333 | Moore | Mar 1987 | A |
4692682 | Lane et al. | Sep 1987 | A |
4712055 | Houser, Jr. | Dec 1987 | A |
4727306 | Misak et al. | Feb 1988 | A |
4745349 | Palanisamy et al. | May 1988 | A |
5012176 | LaForge | Apr 1991 | A |
5136231 | Faulk | Aug 1992 | A |
5166596 | Goedken | Nov 1992 | A |
5172044 | Sasaki et al. | Dec 1992 | A |
5179335 | Nor | Jan 1993 | A |
5185566 | Goedken | Feb 1993 | A |
5363031 | Miller et al. | Nov 1994 | A |
5481175 | Qualich et al. | Jan 1996 | A |
5504416 | Holloway et al. | Apr 1996 | A |
5523667 | Feldstein | Jun 1996 | A |
5600230 | Dunstan | Feb 1997 | A |
5640059 | Kammiller et al. | Jun 1997 | A |
5656920 | Cherng et al. | Aug 1997 | A |
5731694 | Wilcox et al. | Mar 1998 | A |
5736834 | Kuno | Apr 1998 | A |
5804944 | Alberkrack et al. | Sep 1998 | A |
5815389 | Plow et al. | Sep 1998 | A |
5900718 | Tsenter | May 1999 | A |
6094033 | Ding et al. | Jul 2000 | A |
6144186 | Thadiwe et al. | Nov 2000 | A |
6236189 | Franke | May 2001 | B1 |
6275006 | Kolke et al. | Aug 2001 | B1 |
6298233 | Souissi | Oct 2001 | B1 |
6330455 | Ichihara | Dec 2001 | B1 |
6470003 | Smith et al. | Oct 2002 | B1 |
6495992 | Pavlovic | Dec 2002 | B1 |
6639462 | Luu | Oct 2003 | B1 |
6771051 | Oglesbee et al. | Aug 2004 | B2 |
6803746 | Aker et al. | Oct 2004 | B2 |
6850040 | Xiong et al. | Feb 2005 | B2 |
6917182 | Burton et al. | Jul 2005 | B2 |
6927555 | Johnson | Aug 2005 | B2 |
7146139 | Nevermann | Dec 2006 | B2 |
7151411 | Martin et al. | Dec 2006 | B2 |
7158804 | Kumaran et al. | Jan 2007 | B2 |
7170341 | Conrad et al. | Jan 2007 | B2 |
7301308 | Aker et al. | Nov 2007 | B2 |
7549177 | Diefenbaugh et al. | Jun 2009 | B2 |
7724194 | Black et al. | May 2010 | B2 |
8013674 | Drogi et al. | Sep 2011 | B2 |
8054039 | Bauerle et al. | Nov 2011 | B2 |
8155081 | Mater et al. | Apr 2012 | B1 |
8204446 | Scheer et al. | Jun 2012 | B2 |
8232685 | Perper et al. | Jul 2012 | B2 |
8269467 | Li et al. | Sep 2012 | B2 |
8278871 | Kallmyer | Oct 2012 | B2 |
8288994 | Jakes et al. | Oct 2012 | B2 |
8427011 | Jung et al. | Apr 2013 | B2 |
8436492 | Jung et al. | May 2013 | B2 |
8538428 | Bartlett | Sep 2013 | B2 |
8552593 | Jung et al. | Oct 2013 | B2 |
8552693 | Paryani | Oct 2013 | B2 |
8592065 | Bhardwaj et al. | Nov 2013 | B2 |
8624546 | Jung et al. | Jan 2014 | B2 |
8643342 | Mehta et al. | Feb 2014 | B2 |
8754614 | Paryani et al. | Jun 2014 | B2 |
8760010 | Jung et al. | Jun 2014 | B2 |
8805764 | Rhines et al. | Aug 2014 | B1 |
9246454 | Schirmann et al. | Jan 2016 | B2 |
9356461 | Howard et al. | May 2016 | B2 |
9419457 | Robinson et al. | Aug 2016 | B2 |
9438293 | Slater et al. | Sep 2016 | B2 |
9472965 | Nilles | Oct 2016 | B2 |
9491706 | Thorson et al. | Nov 2016 | B2 |
9596653 | Black et al. | Mar 2017 | B2 |
9847661 | Nilles | Dec 2017 | B2 |
20010017602 | Hieb | Aug 2001 | A1 |
20030085684 | Tsukamoto et al. | May 2003 | A1 |
20030189417 | Dias et al. | Oct 2003 | A1 |
20030228875 | Alapuranen | Dec 2003 | A1 |
20030228891 | Kobayashi et al. | Dec 2003 | A1 |
20040075494 | Klomsdorf et al. | Apr 2004 | A1 |
20040117330 | Ehlers et al. | Jun 2004 | A1 |
20040176125 | Lee | Sep 2004 | A1 |
20040222769 | Al-Anbuky et al. | Nov 2004 | A1 |
20040257040 | Xiong et al. | Dec 2004 | A1 |
20050017677 | Burton et al. | Jan 2005 | A1 |
20050030094 | Conrad et al. | Feb 2005 | A1 |
20050046387 | Aker et al. | Mar 2005 | A1 |
20050168193 | Xiong et al. | Aug 2005 | A1 |
20050253561 | Tibbs | Nov 2005 | A1 |
20060028176 | Tang et al. | Feb 2006 | A1 |
20060158156 | Gamboa | Jul 2006 | A1 |
20060269835 | Song | Nov 2006 | A1 |
20070069735 | Graf et al. | Mar 2007 | A1 |
20070188139 | Hussain et al. | Aug 2007 | A1 |
20080074084 | Lee et al. | Mar 2008 | A1 |
20080154624 | O'Neil | Jun 2008 | A1 |
20080197711 | Kato et al. | Aug 2008 | A1 |
20080211455 | Park et al. | Sep 2008 | A1 |
20080303480 | Prutchi et al. | Dec 2008 | A1 |
20090102294 | Hodges et al. | Apr 2009 | A1 |
20090131074 | Minier | May 2009 | A1 |
20090206797 | Chueh et al. | Aug 2009 | A1 |
20090295226 | Hodges et al. | Dec 2009 | A1 |
20090305121 | Yoon et al. | Dec 2009 | A1 |
20100033138 | Alger et al. | Feb 2010 | A1 |
20100085010 | Suzuki et al. | Apr 2010 | A1 |
20100127666 | Ball | May 2010 | A1 |
20100127889 | Vogel et al. | May 2010 | A1 |
20100156355 | Bauerle et al. | Jun 2010 | A1 |
20100198423 | Hirst | Aug 2010 | A1 |
20100198713 | Forbes et al. | Aug 2010 | A1 |
20100225272 | Kirby et al. | Sep 2010 | A1 |
20100233989 | Constien et al. | Sep 2010 | A1 |
20100266066 | Takahashi | Oct 2010 | A1 |
20100283691 | Su et al. | Nov 2010 | A1 |
20110012562 | Paryani | Jan 2011 | A1 |
20110018346 | Dixon | Jan 2011 | A1 |
20110037439 | Bhardwaj et al. | Feb 2011 | A1 |
20110070848 | Reddy | Mar 2011 | A1 |
20110071597 | Aghassian | Mar 2011 | A1 |
20110090126 | Szini et al. | Apr 2011 | A1 |
20110119005 | Majima et al. | May 2011 | A1 |
20110121836 | Kim et al. | May 2011 | A1 |
20110140538 | Jung et al. | Jun 2011 | A1 |
20110151942 | Hanley et al. | Jun 2011 | A1 |
20110156661 | Mehta et al. | Jun 2011 | A1 |
20110222469 | Ali et al. | Sep 2011 | A1 |
20110275369 | Bartlett et al. | Nov 2011 | A1 |
20110291619 | Asakura | Dec 2011 | A1 |
20110316475 | Jung et al. | Dec 2011 | A1 |
20120021800 | Wilson et al. | Jan 2012 | A1 |
20120032646 | Lee | Feb 2012 | A1 |
20120071195 | Chakraborty et al. | Mar 2012 | A1 |
20120146576 | Partovi | Jun 2012 | A1 |
20120147801 | Ho et al. | Jun 2012 | A1 |
20120210325 | de Lind van Wijngaarden et al. | Aug 2012 | A1 |
20120213172 | Kim et al. | Aug 2012 | A1 |
20120235636 | Partovi | Sep 2012 | A1 |
20120242906 | Shintani et al. | Sep 2012 | A1 |
20130020862 | Miller | Jan 2013 | A1 |
20130069658 | Rich et al. | Mar 2013 | A1 |
20130121194 | Heshmati | May 2013 | A1 |
20130122827 | Ali et al. | May 2013 | A1 |
20130169348 | Shi | Jul 2013 | A1 |
20130237254 | Papakipos et al. | Sep 2013 | A1 |
20130249479 | Partovi | Sep 2013 | A1 |
20130257359 | Sakai et al. | Oct 2013 | A1 |
20140018077 | Zhong | Jan 2014 | A1 |
20140068288 | Robinson et al. | Mar 2014 | A1 |
20140070761 | Labbe et al. | Mar 2014 | A1 |
20140070762 | Jenwatanavet et al. | Mar 2014 | A1 |
20140084856 | Howard et al. | Mar 2014 | A1 |
20140092243 | Ichikawa | Apr 2014 | A1 |
20140097671 | Nakamura et al. | Apr 2014 | A1 |
20140176067 | Suzuki et al. | Jun 2014 | A1 |
20140232330 | Robertson et al. | Aug 2014 | A1 |
20140253023 | Paryani | Sep 2014 | A1 |
20140266462 | Schirmann et al. | Sep 2014 | A1 |
20140274188 | Thorson et al. | Sep 2014 | A1 |
20150063181 | Haro et al. | Mar 2015 | A1 |
20150064528 | Liu et al. | Mar 2015 | A1 |
20150079933 | Smith | Mar 2015 | A1 |
20150092676 | Periyalwar et al. | Apr 2015 | A1 |
20150170496 | King | Jun 2015 | A1 |
20150234054 | Lennen | Aug 2015 | A1 |
20150236800 | Tipton et al. | Aug 2015 | A1 |
20150349372 | Maleki et al. | Dec 2015 | A1 |
20150358851 | Toda | Dec 2015 | A1 |
20150379533 | Alberth et al. | Dec 2015 | A1 |
20160043752 | Slater et al. | Feb 2016 | A1 |
20160072326 | Nilles | Mar 2016 | A1 |
20160100364 | Bitar | Apr 2016 | A1 |
20170033584 | Nilles | Feb 2017 | A1 |
Number | Date | Country |
---|---|---|
10118189 | Nov 2002 | DE |
1298809 | Apr 2003 | EP |
1505725 | Jul 2009 | EP |
2077682 | Jul 2009 | EP |
2222371 | May 2011 | EP |
2595269 | May 2013 | EP |
H09247852 | Sep 1997 | JP |
2003333200 | Nov 2003 | JP |
WO-9306682 | Apr 1993 | WO |
WO-2011084367 | Jul 2011 | WO |
WO-2011090769 | Jul 2011 | WO |
WO-2013152149 | Oct 2013 | WO |
Entry |
---|
“Non-Final Office Action”, U.S. Appl. No. 14/293,182, dated May 4, 2017, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 15/295,929, dated Jun. 2, 2017, 7 pages. |
“3GTPP TS 36.213 V9.3.0 3rd Generation Partnership Project Technical Speficiation Group Radio Access Network”, Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures (Release 9), Sep. 2010, 80 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 13/625,976, dated May 4, 2016, 2 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 14/457,190, dated Nov. 14, 2016, 2 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 14/479,679, dated Aug. 3, 2016, 2 pages. |
“Corrected Notice of Allowance”, U.S. Appl. No. 14/479,679, dated Sep. 21, 2016, 2 pages. |
“Ex Parte Quayle Action”, U.S. Appl. No. 13/625,976, Dec. 11, 2015, 11 pages. |
“Ex Parte Quayle Action”, U.S. Appl. No. 14/108,544, Apr. 23, 2015, 8 pages. |
“Ex Parte Quayle Action”, U.S. Appl. No. 14/451,950, Aug. 4, 2015, 7 pages. |
“Final Office Action”, U.S. Appl. No. 13/477,609, Jul. 31, 2015, 11 pages. |
“Final Office Action”, U.S. Appl. No. 13/625,976, dated Jun. 5, 2015, 40 pages. |
“Final Office Action”, U.S. Appl. No. 13/798,682, dated Jul. 30, 2015, 12 pages. |
“Final Office Action”, U.S. Appl. No. 14/293,182, dated Sep. 22, 2016, 9 pages. |
“Final Office Action”, U.S. Appl. No. 14/457,190, dated Mar. 3, 2016, 33 pages. |
“First Choice Power”, http://www.firstchoicepower.com/plans-services/electricity-plans/variable-rate-electricity-plans.aspx—Retrieved on May 18, 2012, 1 page. |
“Foreign Office Action”, EP Application No. 13726055.0, dated Nov. 23, 2016, 4 pages. |
“How Does Prepaid Electricity Work”, http://www.mxenergy.com/does-prepaid-electricity-work-a-19.html—Retrieved on Jan. 15, 2012, 3 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2013/054623, dated Apr. 9, 2015, 12 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2013/060170, dated Mar. 24, 2015, 6 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2013/042042, dated Mar. 10, 2015, 8 pages. |
“International Preliminary Report on Patentability”, Application No. PCT/US2014/014994, dated Sep. 15, 2015, 8 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2014/070384, dated Mar. 13, 2015, 12 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2014/014994, dated Mar. 21, 2014, 12 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2013/054623, dated May 14, 2014, 14 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2013/040242, dated Oct. 4, 2013, 14 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2014/018479, dated Jul. 22, 2014, 17 pages. |
“International Search Report and the Written Opinion”, Application No. PCT/US2013/060170, dated Dec. 5, 2013, 8 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/477,609, dated Dec. 3, 2014, 7 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/477,609, dated Dec. 14, 2015, 9 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/621,857, dated Nov. 14, 2014, 5 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/625,976, dated Feb. 5, 2015, 38 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/798,682, dated Feb. 17, 2015, 10 pages. |
“Non-Final Office Action”, U.S. Appl. No. 13/798,682, dated Dec. 4, 2015, 13 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/293,182, dated May 20, 2016, 10 pages. |
“Non-Final Office Action”, U.S. Appl. No. 14/457,190, dated Sep. 18, 2015, 25 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/477,609, dated Apr. 11, 2016, 5 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/621,857, dated Jan. 26, 2015, 7 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/621,857, dated May 11, 2015, 5 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/625,976, dated Mar. 3, 2016, 8 pages. |
“Notice of Allowance”, U.S. Appl. No. 13/798,682, dated Jun. 20, 2016, 10 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/108,544, dated Oct. 15, 2015, 6 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/451,950, dated Jan. 15, 2016, 5 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/451,950, dated Apr. 22, 2016, 5 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/457,190, dated Oct. 31, 2016, 8 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/479,679, dated Jun. 21, 2016, 9 pages. |
“Restriction Requirement”, U.S. Appl. No. 13/621,857, dated Aug. 18, 2014, 7 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/477,609, dated Jun. 16, 2016, 2 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 13/625,976, dated Mar. 24, 2016, 5 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/451,950, dated Jan. 29, 2016, 2 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/451,950, dated Jun. 10, 2016, 2 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/451,950, dated Aug. 3, 2016, 2 pages. |
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/457,190, dated Feb. 13, 2017, 2 pages. |
“Your Choice Your Plan”, GreyStone Power Corporation, http://www.greystonepower.com/UploadedFiles/pdf/prepaid%20brochure.pdf—Retrieved on Jun. 4, 2012, 2 pages. |
Park,“Energy Maps for Large-scale, Mobile Wireless Networks”, IEEE International Conference on Communications, 2007, Jun. 24, 2007, 6 pages. |
“Notice of Allowance”, U.S. Appl. No. 15/295,929, dated Aug. 16, 2017, 9 pages. |
“Notice of Allowance”, U.S. Appl. No. 14/293,182, dated Nov. 7, 2017, 10 pages. |
Number | Date | Country | |
---|---|---|---|
20170188309 A1 | Jun 2017 | US |
Number | Date | Country | |
---|---|---|---|
61916473 | Dec 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14457190 | Aug 2014 | US |
Child | 15454579 | US |