WO2011004221A1 - Procédé et appareil pour une gestion de puissance d'application - Google Patents

Procédé et appareil pour une gestion de puissance d'application Download PDF

Info

Publication number
WO2011004221A1
WO2011004221A1 PCT/IB2009/052980 IB2009052980W WO2011004221A1 WO 2011004221 A1 WO2011004221 A1 WO 2011004221A1 IB 2009052980 W IB2009052980 W IB 2009052980W WO 2011004221 A1 WO2011004221 A1 WO 2011004221A1
Authority
WO
WIPO (PCT)
Prior art keywords
power management
given application
application
management application
schedule
Prior art date
Application number
PCT/IB2009/052980
Other languages
English (en)
Inventor
Kristian Lappalainen
Original Assignee
Nokia Corporation
Nokia Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Corporation, Nokia Inc. filed Critical Nokia Corporation
Priority to PCT/IB2009/052980 priority Critical patent/WO2011004221A1/fr
Publication of WO2011004221A1 publication Critical patent/WO2011004221A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0212—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave
    • H04W52/0216—Power saving arrangements in terminal devices managed by the network, e.g. network or access point is master and terminal is slave using a pre-established activity schedule, e.g. traffic indication frame
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0251—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity
    • H04W52/0258—Power saving arrangements in terminal devices using monitoring of local events, e.g. events related to user activity controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • Embodiments of the present invention relate generally to wireless communications, and, more particularly, relate to a method and apparatus for scheduling the implementation of applications such that reduced power consumption may be obtained.
  • Example methods and example apparatuses are described that provide for application power management.
  • many wireless communications devices implement applications that utilize repetitive radio transmissions for application maintenance.
  • the repetitive radio transmissions may be transmissions intended to maintain an open connection (e.g., keep- alive messages), transmissions to request data updates, or the like. Due to the repetitive radio transmissions, the associated applications may have relatively high power consumption.
  • a power management application schedule is generated indicating times and dates when an associated application is scheduled to be active, and times and dates when the associated application is scheduled to be inactive.
  • the power management application schedule is accessed and a determination is made as to whether permission to implement the associated application should be granted based on the schedule.
  • the repetitive radio transmissions are halted, thereby avoiding increased energy consumption and extending the charge-life of a battery.
  • One example embodiment is a method for application power management.
  • the example method includes accessing a power management application schedule.
  • the power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the given application may be configured to facilitate a performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the example method also includes determining whether to permit activation of the given application based on the power management application schedule.
  • An additional example embodiment is an apparatus configured for application power management.
  • the example apparatus comprises at least one processor and at least one memory including computer program code.
  • the at least one memory and the computer program code may be configured to, with the at least one processor, cause the example apparatus to perform various functionality.
  • the example apparatus is caused to perform accessing a power management application schedule.
  • the power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the given application may be configured to facilitate a performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the example apparatus is also caused to perform determining whether to permit activation of the given application based on the power management application schedule.
  • the example computer program product comprises at least one computer-readable storage medium having executable computer-readable program code instructions stored therein.
  • the computer-readable program code instructions of the example computer program product are for causing an apparatus to perform accessing a power management application schedule.
  • the power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the given application may be configured to facilitate a performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the computer-readable program code instructions are also for causing the apparatus to perform determining whether to permit activation of the given application based on the power management application schedule.
  • the example apparatus includes means for accessing a power management application schedule.
  • the power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the given application may be configured to facilitate a performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the example apparatus also includes means for determining whether to permit activation of the given application based on the power management application schedule.
  • FIG. 1 illustrates a system for application power management according to various example embodiments of the present invention
  • FIG. 2 illustrates an example user interface for application power management according to various example embodiments of the present invention
  • FIG. 3 illustrates an example apparatus configured to perform application power management according to various example embodiments of the present invention
  • FIG. 4 illustrates an example mobile terminal configured to perform application power management according to various example embodiments of the present invention.
  • FIG. 5 illustrates an example method for application power management according to various example embodiments of the present invention.
  • circuitry refers to all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and/or digital circuitry); (b) to combinations of circuits and software (and/or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s)/software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessors), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and/or firmware.
  • circuitry would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in server, a cellular network device, or other network device.
  • FIG. 1 illustrates an example system in accordance with various example embodiments of the present invention.
  • the example system includes an application server 100, User Equipment (UE) 101 , and a communications network 102.
  • the application server 100 may be any type of computing device that supports the operation of an application that may be implemented by the UE 101.
  • the application server 100 may be configured to communicate with the UE 101 via the network 102.
  • the network 102 may be any type of communications network that includes a portion that supports wireless communications with the UE 101.
  • the UE 101 may be any type of wireless communications device.
  • the UE 101 is a mobile terminal.
  • the UE 101 may be configured to implement various applications (e.g., software applications) that utilize communications between the application server 100 and the UE 101 to maintain the applications.
  • Maintenance of an application may include requesting and retrieving data, such as updates, from the application server 100, sending a data packet or other indication to the application server 100 to maintain an open and healthy connection for use by the application, or the like.
  • Example applications include email applications that request, via a radio transmission, email updates from the application server 100; instant message applications that check for new messages on the application server 100 via radio transmissions, Voice over Internet Protocol (VoIP) applications that maintain an open connection for VoIP calls via, periodic or non-periodic, radio transmissions, other applications that maintain an open connection through the use of repetitive radio transmissions, and the like.
  • VoIP Voice over Internet Protocol
  • the example applications referenced above, as well as other applications implemented by the UE 101 may direct and/or facilitate the transmission of repetitive radio transmissions to support and maintain the applications.
  • the applications may direct and/or facilitate the transmission of the repetitive radio transmissions while the applications are being implemented by the UE 101 (e.g., while the applications are active).
  • the repetitive radio transmissions need not be implemented when the associated applications are not being implemented by the UE 101 (e.g., while the applications are inactive).
  • the UE 101 is configured to assess which applications are utilizing a connection (e.g., a packet data connection, WiFi connection, or the like), and if all applications for the connection are inactive, the UE 101 may also close the connection.
  • a connection e.g., a packet data connection, WiFi connection, or the like
  • the repetitive radio transmissions may be keep-alive messages for maintaining a connection with a destination device, such as the application server 100.
  • the keep-alive messages may be initiated by the UE 101 , or the keep- alive messages may be responses to messages received by a network device, such as the application server 100.
  • the keep-alive messages may ensure that the UE 101 and/or the application server 100 continue to be present within the network and the connection between the devices is maintained.
  • the UE 101 may be configured to transmit a keep-alive data packet to maintain a connection, when no data packet has been transmitted via the connection for a threshold period of time.
  • a keep-alive message may be transmitted at the transport layer and the keep-alive message may be implemented via Transmission Control Protocol (TCP).
  • TCP Transmission Control Protocol
  • a keep-alive message may be configured to probe a device at another end of a connection when the connection is idle for a threshold period of time.
  • the keep-alive message may elicit a response from the device at the other end of connection (e.g., the application server 100) indicating that the connection has been maintained and has not, for example, timed out.
  • An example application that may utilize keep-alive messaging is a VoIP application.
  • the repetitive radio transmissions directed and/or facilitated by the applications may be requests for information from a destination device, such as the application server 100.
  • a destination device such as the application server 100.
  • an email application may regularly, or irregularly based on some criteria, direct the transmission of a request to the application server 100 to determine whether new emails have been received by the application server 100.
  • the application server 100 may reply with content associated with the new emails.
  • the UE 101 implementing, for example, an email application, may send repetitive requests to the application server 100 to check for new email or other data updates.
  • each of the repetitive radio transmissions implemented by the UE 101 consumes energy and reduces battery charge. Therefore, according to some example embodiments, as a result of the repetitive radio transmissions, battery charge durations may be reduced and additional charging of the battery may be required. Further, if the applications remain active indefinitely (e.g., the applications are always on when the UE 101 is powered up), the repetitive radio transmissions may be performed at times when a user does not require the applications to be maintained (e.g., when the user is asleep).
  • a power management application schedule is provided that indicates periods of time when an application is scheduled, for example by a user, to be active and inactive.
  • the power management application schedule may be accessed by the UE 101 , via a processor, and the processor may determine, based on the power management application schedule, whether execution of the application is permitted (e.g., the current time is within a scheduled active period) or disabled (e.g., the current time is within a scheduled inactive period).
  • the UE 101 and/or a processor of the UE 101 may regularly, or irregularly, access a power management application schedule to determine when an application should be disabled and/or implemented.
  • the UE 101 and/or the processor of the UE 101 may direct or facilitate the implementation of a synchronization operation (e.g., email synchronization) to bring the UE 101 up-to-date.
  • a synchronization operation e.g., email synchronization
  • the associated application may be implemented and the repetitive radio transmission may commence.
  • the associated application may be disabled and the repetitive radio transmissions may cease.
  • example embodiments of the present invention prevent the applications from directing and/or facilitating the transmission of repetitive radio transmissions, thereby reducing energy consumption, extending battery charge life, reducing battery charge times, and improving the user experience. For example, if an inactive period for an application is defined for eight hours of a day, then one third of the power consumption attributed to the application's repetitive radio transmissions may be saved.
  • the application server 100 may be configured to handle some or all communications for the UE 101. For example, VoIP calls may be sent to a voicemail service on the application server 100, and/or email received while the email application of the UE 101 is in an inactive period may be stored on the application server 100 until email synchronization occurs when an active period begins.
  • the application server 100 may be configured to determine that an application of the UE 101 is not active, and, in response, handle and/or store communications for the UE 101 at the server.
  • the UE 101 may notify the application server 100 that an application is inactive and direct the application server 100 to handle incoming communications until an activation notification is received from the UE 101 , or a predefined time has elapsed.
  • the notifications may include an indication of a handling policy for incoming communications for the UE 101.
  • the handling policy may indicate whether the application server is to handle the incoming
  • FIG. 2 illustrates an example user interface 110 for power management application scheduling.
  • the example user interface 110 may be implemented on a display of the UE 101.
  • the user interface 110 may include a power management application schedule 130 for a particular application.
  • the user interface 110 depicts the power management application schedule 130 for an Application #1 120. While the user interface 110 depicts a single power management application schedule 130, the UE 101 may support any number of applications having respective power management application schedules.
  • the power management application schedule 103 may be one of a collection of schedules for the applications of the UE 101.
  • each power management application schedule may be application specific.
  • the power management application schedule 130 includes one or more active periods and one or more inactive periods. As depicted in FIG. 2, the crosshatched areas indicate periods when Application #1 is off or inactive, and the non-crosshatched areas indicate periods when the Application #1 is on or active.
  • the active and inactive periods may be populated in various manners. For example, the active and inactive periods may be user defined.
  • a user may use navigation keys of the UE 101 to navigate through the matrix of the power management application schedule 130, and use the softkey "select" 140 to toggle an area to be an inactive period or an active period.
  • portions of the power management application schedule 130 may be accessed by scrolling using a navigation key.
  • the active and inactive periods may be derived from event entries included in a calendar application.
  • a user may define an event entry for a vacation event or a meeting.
  • the UE 101 and/or a processor of the UE 101 may be configured to identify the vacation event and set active periods and inactive periods in a power management application schedule accordingly.
  • the power management application schedule may span any number of days and time, and is not limited to a weekly schedule as depicted in FIG. 2.
  • the power management application schedule may be stored local to the UE 101 on memory included within the UE 101. However, in some example embodiments, the power management application schedule may be stored remote from the UE 101 (e.g., at the application server 100) in a manner that is accessible to the UE 101. Further, the power management application schedule may be stored at the application server 100 or elsewhere, and the UE 101 may access the power application schedule via, for example, a browser to define the active and inactive periods. The application server 100 may define the active and inactive periods to be stored in the power management application schedule based on information that has been provided by a user or other information accessible to the application server 100.
  • FIGs. 3 and 4 illustrate example apparatus embodiments of the present invention configured to perform the various functionalities described herein.
  • FIG. 3 depicts an example apparatus that is configured to perform various functionalities from the perspective of a UE (e.g., UE 101) as described with respect to FIG. 1 and as generally described herein.
  • FIG. 4 depicts an example UE apparatus in the form of a mobile terminal configured to perform various
  • FIG. 3 and 4 may also be configured to perform example methods of the present invention, such as those described with respect to FIG. 5.
  • the apparatus 200 may, be embodied as, or included as a component of, a communications device with wired or wireless communications capabilities.
  • the apparatus 200 may be configured to operate in accordance with the functionality of a UE as described herein.
  • the apparatus 200 may be part of a communications device (e.g., access point 100 or UE 101), such as a stationary or a mobile terminal.
  • a communications device e.g., access point 100 or UE 101
  • the apparatus 200 may be part of an access point (e.g., a base station, wireless router, or the like), a computer, a server, a device that supports network communications, or the like.
  • the apparatus 200 may be a mobile computer, mobile telephone, a portable digital assistant (PDA), a pager, a mobile television, a gaming device, a mobile computer, a laptop computer, a camera, a video recorder, an audio/video player, a radio, and/or a global positioning system (GPS) device, any combination of the aforementioned, or the like. Regardless of the type of communications device, apparatus 200 may also include computing capabilities.
  • the example apparatus 200 includes or is otherwise in communication with a processor
  • the processor 205 may be embodied as various means for implementing the various functionalities of example embodiments of the present invention including, for example, a microprocessor, a coprocessor, a controller, a special-purpose integrated circuit such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), or a hardware accelerator, processing circuitry or the like.
  • processor 205 may be representative of a plurality of processors, or one or more multiple core processors, operating in concert.
  • the processor 205 may be comprised of a plurality of transistors, logic gates, a clock (e.g., oscillator), other circuitry, and the like to facilitate performance of the functionality described herein.
  • the processor 205 may, but need not, include one or more accompanying digital signal processors.
  • the processor 205 is configured to execute instructions stored in the memory device 210 or instructions otherwise accessible to the processor 205.
  • the processor 205 may be configured to operate such that the processor causes the apparatus 200 to perform various functionalities described herein.
  • the processor 205 may be an entity capable of performing operations according to embodiments of the present invention while configured accordingly.
  • the processor 205 is specifically configured hardware for conducting the operations described herein.
  • the instructions specifically configure the processor 205 to perform the algorithms and operations described herein.
  • the processor 205 is a processor of a specific device (e.g., a mobile terminal) configured for employing example embodiments of the present invention by further configuration of the processor 205 via executed instructions for performing the algorithms, methods, and operations described herein.
  • a specific device e.g., a mobile terminal
  • the memory device 210 may be one or more computer-readable storage media that may include volatile and/or non-volatile memory.
  • the memory device 210 includes Random Access Memory (RAM) including dynamic and/or static RAM, on-chip or off- chip cache memory, and/or the like.
  • RAM Random Access Memory
  • memory device 210 may include non-volatile memory, which may be embedded and/or removable, and may include, for example, read-only memory, flash memory, magnetic storage devices (e.g., hard disks, floppy disk drives, magnetic tape, etc.), optical disc drives and/or media, non-volatile random access memory (NVRAM), and/or the like.
  • Memory device 210 may include a cache area for temporary storage of data. In this regard, some or all of memory device 210 may be included within the processor 205.
  • the memory device 210 may be configured to store information, data, applications, computer-readable program code instructions, and/or the like for enabling the processor 205 and the example apparatus 200 to carry out various functions in accordance with example embodiments of the present invention described herein.
  • the memory device 210 could be configured to buffer input data for processing by the processor 205.
  • the memory device 210 may be configured to store instructions for execution by the processor 205.
  • the I/O interface 206 may be any device, circuitry, or means embodied in hardware, software, or a combination of hardware and software that is configured to interface the processor 205 with other circuitry or devices, such as the communications interface 220 and the user interface 215.
  • the processor 205 may interface with the memory 210 via the I/O interface 206.
  • the I/O interface 206 may be configured to convert signals and data into a form that may be interpreted by the processor 205.
  • the I/O interface 206 may also perform buffering of inputs and outputs to support the operation of the processor 205.
  • the processor 205 and the I/O interface 206 may be combined onto a single chip or integrated circuit configured to perform, or cause the apparatus 200 to perform, various functionalities of the present invention.
  • the communication interface 215 may be any device or means embodied in either hardware, a computer program product, or a combination of hardware and a computer program product that is configured to receive and/or transmit data from/to a network 225 and/or any other device or module in communication with the example apparatus 200.
  • Processor 205 may also be configured to facilitate communications via the communications interface by, for example, controlling hardware included within the communications interface 215.
  • the communication interface 215 may include, for example, one or more antennas, a transmitter, a receiver, a transceiver and/or supporting hardware, including, for example, a processor for enabling communications.
  • the example apparatus 200 may communicate with various other network entities in a device-to-device fashion and/or via indirect communications via a base station, access point, server, gateway, router, or the like.
  • the communications interface 215 may be configured to provide for communications in accordance with any wired or wireless communication standard.
  • the communications interface 215 may be configured to support communications in multiple antenna environments, such as multiple input multiple output (MIMO) environments. Further, the communications interface 215 may be configured to support orthogonal frequency division multiplexed (OFDM) signaling.
  • MIMO multiple input multiple output
  • OFDM orthogonal frequency division multiplexed
  • the communications interface 215 may be configured to communicate in accordance with various techniques, such as, second-generation (2G) wireless communication protocols, IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), IS-95 (code division multiple access (CDMA)), third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and time division-synchronous CDMA (TD- SCDMA), 3.9 generation (3.9G) wireless communication protocols, such as Evolved Universal Terrestrial Radio Access Network (E-UTRAN), with fourth-generation (4G) wireless communication protocols, international mobile telecommunications advanced (IMT-Advanced) protocols, Long Term Evolution (LTE) protocols including LTE-advanced, or the like.
  • 2G wireless communication protocols IS-136 (time division multiple access (TDMA)), GSM (global system for mobile communication), IS-95 (code division multiple access (CDMA)
  • third-generation (3G) wireless communication protocols such as Universal Mobile T
  • communications interface 215 may be configured to provide for communications in accordance with techniques such as, for example, radio frequency (RF), infrared (IrDA) or any of a number of different wireless networking techniques, including WLAN techniques such as IEEE 802.11 (e.g., 802.11a, 802.11 b, 802.11g, 802.11 n, etc.), wireless local area network (WLAN) protocols, world interoperability for microwave access (WiMAX) techniques such as IEEE 802.16, and/or wireless Personal Area Network (WPAN) techniques such as IEEE 802.15, BlueTooth (BT), low power versions of BT, ultra wideband (UWB), Wibree, Zigbee and/or the like.
  • the communications interface 215 may also be configured to support communications at the network layer, possibly via Internet Protocol (IP).
  • IP Internet Protocol
  • the user interface 220 may be in communication with the processor 205 to receive user input via the user interface 220 and/or to present output to a user as, for example, audible, visual, mechanical or other output indications.
  • the user interface 220 may include, for example, a keyboard, a mouse, a joystick, a display (e.g., a touch screen display), a microphone, a speaker, or other input/output mechanisms.
  • the processor 205 may comprise, or be in communication with, user interface circuitry configured to control at least some functions of one or more elements of the user interface.
  • the processor 205 and/or user interface circuitry may be configured to control one or more functions of one or more elements of the user interface through computer program instructions (e.g., software and/or firmware) stored on a memory accessible to the processor 205 (e.g., volatile memory, non-volatile memory, and/or the like).
  • the user interface circuitry is configured to facilitate user control of at least some functions of the apparatus 200 through the use of a display and configured to respond to user inputs.
  • the processor 205 may also comprise, or be in communication with, display circuitry configured to display at least a portion of a user interface, the display and the display circuitry configured to facilitate user control of at least some functions of the apparatus 200.
  • the scheduling manager 230 and/or the schedule analyzer 235 of example apparatus 200 may be any means or device embodied, partially or wholly, in hardware, a computer program product, or a combination of hardware and a computer program product, such as processor 205 implementing stored instructions to configure the example apparatus 200, or a hardware configured processor 205, that is configured to carry out the functions of the scheduling manager 230 and/or the schedule analyzer 235 as described herein.
  • the processor 205 includes, or controls, the scheduling manager 230 and/or the schedule analyzer 235.
  • the scheduling manager 230 and/or the schedule analyzer 235 may be, partially or wholly, embodied as processors similar to, but separate from processor 205.
  • the scheduling manager 230 and/or the schedule analyzer 235 may be in communication with the processor 205.
  • the scheduling manager 230 and/or the schedule analyzer 235 may, partially or wholly, reside on differing apparatuses such that some or all of the functionality of the scheduling manager 230 and/or the schedule analyzer 235 may be performed by a first apparatus, and the remainder of the functionality of the scheduling manager 230 and/or the schedule analyzer 235 may be performed by one or more other apparatuses.
  • the apparatus 200 and the processor 205 may be configured to perform the following functionality via the scheduling manager 230.
  • the scheduling manager 230 may be configured to access a power management application schedule stored, for example, in the memory 210 or at a location otherwise accessible to the apparatus 200 and the processor 205.
  • a power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the power management application schedule may be one schedule within a collection of schedules for respective applications.
  • the power management application schedule was generated based on event entries in a calendar application.
  • the given application associated with the power management application schedule may be configured to facilitate the performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the apparatus 200 and/or the processor 205 may be configured to execute the given application, and the given application may be configured to interface with the communications interface 220 to facilitate performance of the repetitive radio transmissions.
  • the repetitive radio transmissions may be keep-alive messages for maintaining a connection between the apparatus 200 and a destination device (e.g., application server 100).
  • a destination device e.g., application server 100
  • at least one of the repetitive radio transmissions is a keep-alive transmission of a data packet via a connection when no data packet has been transmitted via the connection for a threshold period of time.
  • the repetitive radio transmissions request data updates from a destination device (e.g., application server 100).
  • a destination device e.g., application server 100.
  • the apparatus 200 and the processor 205 may be configured to perform the following functionality via the schedule analyzer 235.
  • the schedule analyzer 235 may be configured to determine whether to permit activation of a given application based on a power management application schedule.
  • the schedule analyzer 235 is further configured to facilitate the implementation and/or execution of the given application in response to determining that a current time is within the active period.
  • the schedule analyzer 235 may also be configured to facilitate the performance of the repetitive radio transmissions in response to determining that a current time is within the active period.
  • the schedule analyzer 235 may also be configured to facilitate the implementation and/or execution of a synchronization operation for the given application in response to determining that a current time is within the active period, and facilitate the performance of the repetitive radio transmissions in response to determining that a current time is within the active period. According to some example embodiments, the schedule analyzer 235 may also be configured to disable or otherwise prevent implementation of the given application in response to determining that a current time is within the inactive period and disable or otherwise prevent implementation of the performance of the repetitive radio transmissions in response to determining that a current time is within the inactive period.
  • the example apparatus of FIG. 3 is a mobile terminal 10 configured to communicate within a wireless network, such as a cellular network,
  • the mobile terminal 10 may be configured to perform the functionality of UE 101 and/or apparatus 200 as described herein. More specifically, the mobile terminal 10 may be caused to perform the functionality of the scheduling manager 230 and/or the schedule analyzer 235 via the processor 20.
  • processor 20 may be an integrated circuit or chip configured similar to the processor 205 together with, for example, the I/O interface 206.
  • volatile memory 40 and non-volatile memory 42 may be configured to support the operation of the processor 20 as computer readable storage media.
  • the mobile terminal 10 may further include an antenna 12, a transmitter 14, and a receiver 16, which may be included as parts of a communications interface of the mobile terminal 10.
  • the speaker 24, the microphone 26, the display 28, and the keypad 30 may be included as parts of a user interface.
  • FIG. 5 illustrates flowcharts of example systems, methods, and/or computer program products according to example embodiments of the invention. It will be understood that each block or operation of the flowcharts, and/or combinations of blocks or operations in the flowcharts, can be implemented by various means. Means for implementing the blocks or operations of the flowcharts, combinations of the blocks or operations in the flowchart, or other functionality of example embodiments of the present invention described herein may include hardware, and/or a computer program product including a computer-readable storage medium having one or more computer program code instructions, program instructions, or executable computer-readable program code instructions stored therein.
  • program code instructions may be stored on a memory device, such as memory device 210, of an example apparatus, such as example apparatus 200, and executed by a processor, such as the processor 205.
  • any such program code instructions may be loaded onto a computer or other programmable apparatus (e.g., processor 205, memory device 210, or the like) from a computer-readable storage medium to produce a particular machine, such that the particular machine becomes a means for implementing the functions specified in the flowcharts' block(s) or operation(s).
  • These program code instructions may also be stored in a computer-readable storage medium that can direct a computer, a processor, or other programmable apparatus to function in a particular manner to thereby generate a particular machine or particular article of manufacture.
  • the instructions stored in the computer-readable storage medium may produce an article of manufacture, where the article of manufacture becomes a means for implementing the functions specified in the flowcharts' block(s) or operation(s).
  • the program code instructions may be retrieved from a computer- readable storage medium and loaded into a computer, processor, or other programmable apparatus to configure the computer, processor, or other programmable apparatus to execute operations to be performed on or by the computer, processor, or other programmable apparatus.
  • Retrieval, loading, and execution of the program code instructions may be performed sequentially such that one instruction is retrieved, loaded, and executed at a time. In some example embodiments, retrieval, loading and/or execution may be performed in parallel such that multiple instructions are retrieved, loaded, and/or executed together.
  • Execution of the program code instructions may produce a computer-implemented process such that the instructions executed by the computer, processor, or other programmable apparatus provide operations for implementing the functions specified in the flowcharts' block(s) or operation(s).
  • execution of instructions associated with the blocks or operations of the flowchart by a processor, or storage of instructions associated with the blocks or operations of the flowcharts in a computer-readable storage medium support combinations of operations for performing the specified functions. It will also be understood that one or more blocks or operations of the flowcharts, and combinations of blocks or operations in the flowcharts, may be implemented by special purpose hardware-based computer systems and/or processors which perform the specified functions, or combinations of special purpose hardware and program code instructions.
  • FIG. 5 depicts one or more flowcharts of example methods for application power management.
  • An example method includes accessing a power management application schedule at 400.
  • a power management application schedule may include an indication of an active period for a given application and an indication of an inactive period for the given application.
  • the power management application schedule being one schedule within a collection of schedules for respective applications.
  • the power management application schedule was generated based on event entries in a calendar application.
  • the given application associated with the power management application schedule may be configured to facilitate the performance of repetitive radio transmissions to a destination device to maintain the given application.
  • the repetitive radio transmissions may be keep-alive messages for maintaining a connection with a destination device (e.g., application server 100).
  • at least one of the repetitive radio transmissions is a keep-alive transmission of a data packet via a connection when no data packet has been transmitted via the connection for a threshold period of time.
  • the repetitive radio transmissions request data updates from a destination device (e.g., application server 100).
  • the example method also includes determining whether to permit activation of a given application based on a power management application schedule. According to some example embodiments, determining whether to permit activation of a given application includes facilitating the implementation and/or execution of the given application in response to determining that a current time is within the active period. Further, determining whether to permit activation of a given application may also include facilitating the performance of the repetitive radio
  • determining whether to permit activation of a given application includes facilitating the implementation and/or execution of a synchronization operation for the given application in response to determining that a current time is within the active period, and facilitating the performance of the repetitive radio transmissions in response to determining that a current time is within the active period.
  • determining whether to permit activation of a given application includes disabling or otherwise preventing implementation of the given application in response to determining that a current time is within the inactive period, and disabling or otherwise preventing implementation of the performance of the repetitive radio transmissions in response to determining that a current time is within the inactive period.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Abstract

L'invention porte sur divers procédés pour une gestion de puissance d'application. Un procédé à titre d'exemple comprend l'accès à un programme d'application de gestion de puissance. Le programme d'application de gestion de puissance peut comprendre une indication d'une période active pour une application donnée et une indication d'une période inactive pour l'application donnée. L'application donnée peut être configurée pour faciliter une performance de transmissions radio répétitives à un dispositif de destination pour maintenir l'application donnée. Le procédé à titre d'exemple peut également comprendre la détermination du point de savoir si ou non permettre une activation de l'application donnée sur la base du programme d'application de gestion de puissance. Des procédés similaires et apparentés à titre d'exemple et des appareils à titre d'exemple sont également divulgués.
PCT/IB2009/052980 2009-07-08 2009-07-08 Procédé et appareil pour une gestion de puissance d'application WO2011004221A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2009/052980 WO2011004221A1 (fr) 2009-07-08 2009-07-08 Procédé et appareil pour une gestion de puissance d'application

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2009/052980 WO2011004221A1 (fr) 2009-07-08 2009-07-08 Procédé et appareil pour une gestion de puissance d'application

Publications (1)

Publication Number Publication Date
WO2011004221A1 true WO2011004221A1 (fr) 2011-01-13

Family

ID=42012052

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2009/052980 WO2011004221A1 (fr) 2009-07-08 2009-07-08 Procédé et appareil pour une gestion de puissance d'application

Country Status (1)

Country Link
WO (1) WO2011004221A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109923498A (zh) * 2016-11-18 2019-06-21 Ati科技无限责任公司 用于电力性能管理的应用剖析

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1622278A2 (fr) * 2004-07-26 2006-02-01 Microsoft Corporation Procédé de gestion de la puissance pour un dispositif de réception de données diffusées
US20080070642A1 (en) * 2006-09-18 2008-03-20 Motorola, Inc. Method and system for consolidating power saving classes
EP1978765A1 (fr) * 2007-04-02 2008-10-08 BRITISH TELECOMMUNICATIONS public limited company Plan de gestion d'énergie pour des dispositifs de communication mobiles
WO2009053522A1 (fr) * 2007-10-23 2009-04-30 Teliasonera Ab Motifs de messagerie optimisés

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1622278A2 (fr) * 2004-07-26 2006-02-01 Microsoft Corporation Procédé de gestion de la puissance pour un dispositif de réception de données diffusées
US20080070642A1 (en) * 2006-09-18 2008-03-20 Motorola, Inc. Method and system for consolidating power saving classes
EP1978765A1 (fr) * 2007-04-02 2008-10-08 BRITISH TELECOMMUNICATIONS public limited company Plan de gestion d'énergie pour des dispositifs de communication mobiles
WO2009053522A1 (fr) * 2007-10-23 2009-04-30 Teliasonera Ab Motifs de messagerie optimisés

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109923498A (zh) * 2016-11-18 2019-06-21 Ati科技无限责任公司 用于电力性能管理的应用剖析
CN109923498B (zh) * 2016-11-18 2023-08-15 Ati科技无限责任公司 用于电力性能管理的应用剖析

Similar Documents

Publication Publication Date Title
EP2517086B1 (fr) Procédé et appareil permettant de gérer de l'énergie par le biais d'un sous-système
US10206074B2 (en) Remote access to a mobile communication device over a wireless local area network (WLAN)
US8020025B2 (en) Power saving scheduler for timed events
US7836446B2 (en) Conflict management program, storage medium for conflict management program storage, conflict management method, and electronic apparatus for terminal devices
US8494478B1 (en) Mobile phone as computer backup including power management
US20110269476A1 (en) System and method for dynamically managing connections using a coverage database
WO2018000358A1 (fr) Procédé et dispositif mobile destinés au balayage d'un réseau wi-fi
US20140203944A1 (en) Communications device having battery monitoring capabilities and performing pre-scheduled events
US20130194993A1 (en) Packet transmission method and apparatus of mobile terminal
CN102823320A (zh) 用于移动设备上的电源管理的装置和方法
US9125005B2 (en) Method and apparatus for providing mobile services outside of cellular coverage
US8806028B2 (en) System and method for accessing data and applications on a host when the host is in a dormant state
JP2011082756A (ja) 情報閲覧システム
WO2019128588A1 (fr) Procédé et appareil de traitement de processus, dispositif électronique et support d'informations lisible par ordinateur
US8363589B2 (en) Method and apparatus for generating and utilizing communications shortcuts
CN104955133A (zh) 用于管理网络连线的移动设备和方法以及存储介质
WO2019128569A1 (fr) Procédé et appareil pour geler une application et support de stockage et terminal
WO2010029414A1 (fr) Procédé et appareil de transfert de données
KR20060124235A (ko) 복수의 이동 통신 단말기들간에 일정을 상호 공유하기 위한방법 및 그 시스템
US20140237475A1 (en) Sleep/wake with suppression and donated importance
WO2011004221A1 (fr) Procédé et appareil pour une gestion de puissance d'application
WO2015033225A2 (fr) Rappels de temps de communication basés sur des messages textes
WO2019128570A1 (fr) Appareil et procédé de gel d'une application et support de stockage et terminal
EP2760188B1 (fr) Dispositif de communication ayant des capacités de surveillance de batterie et effectuant des événements préprogrammés
WO2011004219A1 (fr) Procédé et appareil de planification de téléchargements

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09786553

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09786553

Country of ref document: EP

Kind code of ref document: A1