WO2020036291A1 - Methods and systems for managing navigation of modes of operation of applications in a device - Google Patents

Methods and systems for managing navigation of modes of operation of applications in a device Download PDF

Info

Publication number
WO2020036291A1
WO2020036291A1 PCT/KR2019/005777 KR2019005777W WO2020036291A1 WO 2020036291 A1 WO2020036291 A1 WO 2020036291A1 KR 2019005777 W KR2019005777 W KR 2019005777W WO 2020036291 A1 WO2020036291 A1 WO 2020036291A1
Authority
WO
WIPO (PCT)
Prior art keywords
application
mode
applications
power saving
soc
Prior art date
Application number
PCT/KR2019/005777
Other languages
French (fr)
Inventor
Tarun Jindal
Original Assignee
Samsung Electronics Co., Ltd.
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 Samsung Electronics Co., Ltd. filed Critical Samsung Electronics Co., Ltd.
Publication of WO2020036291A1 publication Critical patent/WO2020036291A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3206—Monitoring of events, devices or parameters that trigger a change in power modality
    • G06F1/3212—Monitoring battery levels, e.g. power saving mode being initiated when battery voltage goes below a certain level
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/48—Program initiating; Program switching, e.g. by interrupt
    • G06F9/4806—Task transfer initiation or dispatching
    • G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
    • G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
    • G06F9/4893—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues taking into account power or heat criteria
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26—Power supply means, e.g. regulation thereof
    • G06F1/32—Means for saving power
    • G06F1/3203—Power management, i.e. event-based initiation of a power-saving mode
    • G06F1/3234—Power saving characterised by the action undertaken
    • G06F1/325—Power saving in peripheral device
    • G06F1/3265—Power saving in display device
    • 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
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • Embodiments herein relate to power management in devices, and more particularly to methods and systems for managing navigation of a power saving mode in which applications present on a device can operate.
  • devices can operate in a power saving mode automatically (on detecting that the energy available in the battery is lower than a threshold) or manually.
  • the device operating in the power saving mode can perform a static power optimization, wherein applications in the device can be detected and put to sleep or disabled based on pre-defined criteria. Examples of the criteria can be significant memory usage and power consumption, running in background for a considerable period, depleting battery charge, and so on.
  • the static power optimization can be performed primarily for prolonging the charge cycle of the battery.
  • resources allocated to the applications are withdrawn. If the user initiates the applications again, the resources are reallocated for enabling the applications. Frequent allocation and deallocation can lead to greater power consumption.
  • the devices can also switch to a power saving mode, wherein all, but the most important, applications are disabled.
  • the classification of importance is generally fixed or can be varied by user intervention. This can cause inconvenience if a user indents to use an application in the power saving mode which is not classified as important. In this circumstance, the user needs to either disable the low power mode, such that the intended application can be enabled and used; or manually classify the intended application as important so that the application is not disabled in the power saving mode.
  • FIG. 1 depicts an example, wherein a device operating in a power saving mode allows enablement of a minimum number of applications.
  • the device can either switch to the power saving mode automatically or the user can trigger the power saving mode.
  • the device can display six applications, viz., App1-App6, which are enabled for usage.
  • the enabled applications have been classified as important by the device or by the user. The classification is fixed and if the user intends to use an application apart from App1-App6, the user needs to disable the power saving mode. Else, if the user intends to use the application in the power saving mode, then the user needs to manually classify the application as important.
  • FIG. 2 depicts manual selection of applications to be disabled in the power saving mode.
  • the user can manually navigate to the power saving menu of the device for selecting the applications that are to be disabled in the power saving mode.
  • the user can select the applications (user selects App1, App3 and App 4) that the user intends to disable when the device operates in the power saving mode.
  • the selected applications i.e., App1, App3 and App 4 are disabled.
  • the principal object of the embodiments herein is to disclose methods and systems for managing navigation of power saving modes, in which applications in a device can operate, based on mined contextual data associated with the applications and power available in the device.
  • Another object of the embodiments herein is to enable or disable the applications automatically based on the mined contextual data associated with the applications.
  • Another object of the embodiments herein is to perform instant optimization of hardware and software performance during the enablement and disablement of the applications.
  • Another object of the embodiments herein is to display User Interface (UI) for the applications, using a low power processor, supporting limited functionalities.
  • UI User Interface
  • Another object of the embodiments herein is to distribute activities, which are triggered by the applications, for execution by other devices capable of executing the activities, wherein the device triggering the activities and the other devices can be a part of an Internet of Things (IoT) environment.
  • IoT Internet of Things
  • embodiments herein provide methods and systems for managing navigation of power saving modes, in which applications in a device can operate.
  • Embodiments herein allow the applications to operate in one of the power saving modes, viz., an activated mode, a standby mode, or a disabled mode.
  • the embodiments allow the applications to navigate through the different power saving modes of operation based on contextual data, mined from the applications, and power available in the battery of the device.
  • the applications operating in the activated mode can be displayed on the device.
  • the contextual data associated with the applications can be mined in the background.
  • hardware performance of the device can be optimized. If power available in the device is low, UIs (for applications operating in the activated mode) with limited functionality are displayed; and tasks triggered by the applications operating in the activated mode and the standby mode can be distributed to other devices in the vicinity of the device.
  • Embodiments herein disclose methods and systems for managing navigation of power saving modes, in which applications in a device can operate.
  • the power saving modes in which the applications can operate at a particular time are, viz., an activated mode, a standby mode, and a disabled mode.
  • the embodiments include mining contextual data associated with the applications in the background.
  • the contextual data can include application usage pattern, access time, location of usage, application data, genre of application, and so on.
  • the embodiments include navigating through the power saving modes, in which each of the applications are operating based on the mined contextual data associated with the applications and power available in the device. For example, an application operating in the activated mode can be made to operate in the standby mode or the disabled mode. In the activated mode, an application can be enabled, and in the disabled mode, the application can be disabled.
  • the applications can be run using a low power processor when the device is in the power saving mode.
  • the embodiments include displaying a User Interface (UI) which provides limited functionalities in comparison with a UI displayed when the application is run using an application processor.
  • UI User Interface
  • the device can distribute activities that are triggered by the applications to other devices that are part of an Internet of Things (IoT) environment.
  • IoT Internet of Things
  • the device can detect other devices in the IoT environment that are capable of and have adequate power to perform the activity and can provide instructions to the other detected devices to perform the activity. This can minimize the power requirement load of the device.
  • FIG. 1 depicts an example, wherein a device operating in a power saving mode allows enablement of a minimum number of applications
  • FIG. 2 depicts manual selection of applications to be disabled in the power saving mode
  • FIG. 3 depicts various units of a device for managing navigation of power saving modes, in which applications in the device can operate, according to embodiments as disclosed herein;
  • FIG. 4 is a flowchart depicting a method for managing navigation of power saving modes, in which applications in the device can operate, according to embodiments as disclosed herein;
  • FIG. 5 depicts an example timeline, within which a sports application navigates from a disabled mode to an activated mode and vice-versa, according to embodiments as disclosed herein;
  • FIGS. 6a and 6b is an example use case scenario depicting enablement and disablement of applications based on location of the device, according to embodiments as disclosed herein;
  • FIG. 7 depicts an example timeline during which the applications in the device are enabled, according to embodiments as disclosed herein;
  • FIGS. 8a and 8b is an example use case scenario depicting navigation of the operating mode of applications in the device based on application data, according to embodiments as disclosed herein;
  • FIGS. 9a and 9b is an example use case scenario depicting enablement of applications in the device based on application genre, according to embodiments as disclosed herein;
  • FIG. 10 depicts a User Interface (UI) of an application providing limited functionalities based on state of charge of a battery of the device, according to embodiments as disclosed herein;
  • FIG. 11 depicts an example distribution of tasks/activities, triggered by applications, to other devices based on the state of charge of the battery of the device, according to embodiments as disclosed herein.
  • FIGS. 3 through 11 where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
  • FIG. 3 depicts various units of a device 300 for managing navigation of power saving modes, in which applications in the device 300 can operate, according to embodiments as disclosed herein.
  • the device 300 includes an application mode manager 301, a display 302, a processor 303, and a communication interface 304.
  • Examples of the device 300 can be, but not limited to, a smart phone, a mobile phone, an IoT device, a wearable device, a vehicle infotainment system, a computer, a laptop, a tablet, and so on.
  • the application mode manager 301 can determine whether the device is in a power saving mode.
  • the application mode manager 301 can facilitate the applications in the device 300 to navigate through different operating modes.
  • the power saving modes in which the applications can operate can be an activated mode, a standby mode, and a disabled mode.
  • the applications can operate in one of the power saving modes at a particular instant. In the activated mode the applications can operate in both foreground and background. In the standby mode, the applications can be put to sleep. In the disabled mode, the applications cannot be launched as long as the device 300 is in the power saving mode.
  • the application mode manager 301 can mine contextual data associated with the applications in background.
  • the contextual data associated with at least one application can be mined by obtaining information using background context based services.
  • the mining can involve identifying usage pattern of the applications, access time, location of usage, inter-relationship between application data of the different applications, type of data and importance of the data of the applications, genre of the applications, and so on.
  • the information can be transformed into a comprehensible structure to form the contextual data.
  • the application mode manager 301 can allow the applications in the device 300 to operate in either of the activated mode, standby mode, or disabled mode. If an application is operating in the activated mode, it can be understood that the application is enabled. Conversely, if an application is operating in the disabled mode, it can be understood that the application is disabled.
  • the application mode manager 301 can be a part of an Artificial Intelligence (AI) engine in the device 300.
  • AI Artificial Intelligence
  • the application mode manager 301 can optimize hardware and software performance when applications can be enabled or disabled.
  • the optimization can include adjusting Central Processing Unit (CPU) frequency; User Interface (UI) rendering of the at least one application by the processor 303; managing operation of the processor 303, access to cores of the CPU, and touch activation on the display 302; varying screen resolution; and so on.
  • CPU Central Processing Unit
  • UI User Interface
  • the Central Processing Unit (CPU) frequency or resolution can be decreased.
  • the Central Processing Unit (CPU) frequency and/or resolution can be increased.
  • the application mode manager 301 can prioritize applications that can operate in the activated mode. If the device 300 is unable to perform the activities triggered by the applications operating in the activated mode, the application mode manager 301 can navigate the mode of operation, of a predefined number of applications with lower priorities, from the activated mode to the standby mode or the disabled mode. Based on the number of applications (with higher priority) operating in the activated mode, the hardware and software performance can be optimized.
  • the application mode manager 301 can request other devices to perform tasks or activities that are triggered by the applications, if the device 300 is operating in the power saving mode. The request can be issued if the device 300 is unable to perform the activities triggered by the applications due to insufficient power in the battery and/or the other devices have the capability and have sufficient power to perform the activities triggered by the applications.
  • the device 300 can detect presence of the other devices that are in the vicinity of the device 300 or in an IoT environment in which the device 300 is present.
  • the communication interface 304 can detect the presence of the other devices.
  • the communication between the device 300 and the other devices can be established using examples means such as, but not limited to, Wireless Fidelity (Wi-Fi), Bluetooth, Infrared, Ultra Wideband Communication (UWC), and so on.
  • the display 302 can display the applications that are currently in the activated mode.
  • the applications in the standby mode and the disabled mode may not be displayed.
  • the applications can be in a sleep state.
  • the applications operating in the standby mode and the disabled mode may not contribute to power consumption, may not operate in the background, and may not utilize memory of the device 300.
  • the applications operating in the standby mode and the disabled mode may contribute to minimal power consumption, may utilize memory of the device 300 minimally, and so on.
  • the processor 303 can manage UI rendering for the applications based on whether the device 300 is operating in power saving mode.
  • the display 302 can render original UIs or UIs with limited functionality for the applications. If the device is in operating in the low power mode and if an application needs to be in the activated mode, the processor 303 can allow the display 302 to render an UI of the application with limited functionalities.
  • the rendered UI can control the number of APIs of each of the applications that can be triggered in background. The APIs that are triggered may be specific to display requirement. On the other hand, if the device 300 is operating in normal mode, the processor 303 can allow the display 302 to render the original UI of the application.
  • FIG. 3 shows exemplary units of the device 300, but it is to be understood that other embodiments are not limited thereon.
  • the device 300 may include less or more number of units.
  • the labels or names of the units are used only for illustrative purpose and does not limit the scope of the invention.
  • One or more units can be combined together to perform same or substantially similar function in the device 300.
  • FIG. 4 is a flowchart 400 depicting a method for managing navigation of power saving modes, in which applications in the device 300 can operate, according to embodiments as disclosed herein.
  • the embodiments include mining contextual data associated with at least one application installed in the device 300.
  • the contextual data associated with at least one application can be mined using context based services.
  • the mined data can include the usage pattern of the at least one application, access periods (time of the day or specific days when the at least one application is used), location of usage (location of the device 300 when the at least one application is used), inter-relationship between application data (association of data of one application with another application), content (data type of each of the at least one application and importance of data of the at least one application), genre of the at least one application, and so on.
  • the mining of contextual data associated with the at least one application can be performed in the background over a period of time.
  • the embodiments include determining that the device 300 is operating in a power saving mode.
  • the embodiments include managing mode of operation of the at least one application based on the contextual data associated with the at least one application and power available in the device 300 (State of Charge (SoC) of the battery of the device 300).
  • the operating mode can be either of activated mode, standby mode and disabled mode.
  • the mode of operation of an application can either remain same or may vary based on the contextual data associated with the application. In an example, (after determining that the device 300 is operating in the power saving mode) a first application may be allowed to operate in the activated mode, while a second application may be allowed to operate in the standby mode. Based on the contextual data, after a period of time, the first application may be disabled and the second application can be allowed to operate in the standby mode.
  • the embodiments include navigating the mode of operation of the applications in the device 300.
  • an application if an application is allowed to operate in the activated mode, the application is enabled.
  • the applications that are allowed to operate in the activated mode can be accessed by the user, as the applications that are operating in the activated mode are displayed on the device 300.
  • the user can trigger actions using the application through a UI of the application.
  • the rendered UI may either allow the user to explore all options provided by the application to trigger actions, or allow the user to explore limited functionalities of the application.
  • the device 300 can request other devices to perform at least one operation triggered by at least one application operating in the activated mode.
  • the embodiments include detecting the other devices in the vicinity of the device 300, or in an IoT environment.
  • the applications can be assigned with priorities. If the state of charge of the battery is low, applications assigned with lower priorities can be disabled or allowed to operate in the standby mode, and the applications assigned with higher priorities can be allowed to operate in the activated mode.
  • the embodiments include optimizing the hardware and software performance of the device 300 based on the mode of operation of the at least one application, SoC of the battery of the device 300, and the contextual data associated with the at least one application.
  • the CPU frequency can be increased.
  • an application initially operating in the activated mode can be disabled (allowed to operate in the disabled mode). Thereafter, the CPU frequency can be decreased and resolution can be reduced. Therefore, based on the modes of operation through which the at least one application navigates; the embodiments include optimizing the hardware and software performance.
  • the various actions in the flowchart 400 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
  • FIG. 5 depicts an example timeline, within which a sports application navigates from the disabled mode to the activated mode and vice-versa, according to embodiments as disclosed herein.
  • the sports application (labeled as S) installed in the device 300 is in the disabled mode.
  • the embodiments include determining that a sporting event is going to take place at 8:00 PM and terminate at 11:00 PM.
  • the embodiments include enabling the sports application.
  • the sports application begins to operate in the activated mode and an icon of the sports application can be displayed. When a user clicks on the icon, a UI of the sports application can be rendered.
  • the device 300 can start receiving updates and notifications associated with the sports event when the sports application is operating in the activated mode (from 7:50 PM).
  • the sports application may operate in the activated mode after conclusion of the sporting event at 11:00 PM for receive any concluding notifications relevant to the sporting event.
  • the embodiments include disabling the sports application and the sports application begins to operate in the disabled mode. Once the sports application is disabled, the icon of the sports application disappears from the display 302.
  • the device 300 can determine after 11:30 PM that the user had stopped using the sports application.
  • the device 300 can mine the usage pattern of the sports application and disable the sports application.
  • FIGS. 6a and 6b is an example use case scenario depicting enablement and disablement of applications based on location of the device 300, according to embodiments as disclosed herein.
  • six applications viz., App1-App6, are displayed on the device 300.
  • the device 300 can enable, put on standby, or disable applications in the device 300.
  • the applications can be enabling based on future usage requirement, user preference importance, necessity, and so on.
  • the embodiments include detecting that a user of the device 300 is travelling based on frequent updates in location of the device 300. As the user is travelling, the embodiments include enabling social media applications (labeled as S), music applications (labeled as M), transportation applications (labeled as T), and so on.
  • the enabled applications can operate in the activated mode. As depicted in FIG. 6b, the enabled applications can be displayed in place of some of the applications (amongst App1-App6) that are disabled to display the newly enabled applications. The disabled applications can operate in the disabled mode.
  • FIG. 7 depicts an example timeline during which the applications in the device 300 are enabled, according to embodiments as disclosed herein.
  • the embodiments include automatically navigating through the modes of operation of the applications based on mined contextual data associated with the applications. As depicted in FIG. 7, based on usage pattern (usage of applications at particular times) and relationship between application data of different applications, the embodiments can enable, put on standby, or disable applications in the device 300.
  • transportation applications (labeled as T) are enabled. After enablement, the transportation applications can operate in the activated mode.
  • the enablement of the transportation applications at 7:00 PM can be based on contextual data.
  • the contextual data is mined by monitoring for a period of time the usage of the transportation applications at approximately 7:00 PM.
  • the device 300 can assume that the user is likely to travel at around 7:00 PM and enable the transportation applications.
  • social media applications (labeled as S) and music applications (labeled as M) can be enabled.
  • the device 300 can detect usage of the social media applications and music applications while the user travels.
  • sports and entertainment applications (labeled as E) can be enabled and at 8:30 PM, food delivery applications (labeled as F) can be enabled.
  • the enablement of these applications can be based on usage of the corresponding applications at the specific times.
  • FIGS. 8a and 8b is an example use case scenario depicting navigation of the operating mode of applications in the device 300 based on application data, according to embodiments as disclosed herein.
  • FIG. 8a consider that the user makes a movie ticket purchase using a movie ticket booking application. The movie is scheduled at 7:30 PM at a particular date (6 th Feb 2019). The device can extract (mine for future) contextual data regarding the booked ticket and the movie schedule and use the extracted contextual data to enable applications that can facilitate the user to reach a theatre where the movie is being screened.
  • the device 300 can enable the transportation applications, which may have been operating in the disabled mode. The transportation applications operate in the activated mode at 7:00 PM.
  • FIGS. 9a and 9b is an example use case scenario depicting enablement of applications in the device 300 based on application genre, according to embodiments as disclosed herein.
  • the user intending to book a ride.
  • the user can select a transportation application to book the ride.
  • fares for booking the ride using the transportation application are higher than usual.
  • the embodiments can determine a contextual data, i.e., information that the fare for booking the ride using the transportation application is higher than usual. In such situations, as depicted in FIG.
  • the embodiments include enabling applications of similar genre, i.e., transportation applications (labeled as T1 and T2), which facilitate the user to compare the fares of the different transportation applications and book the ride using the transportation application offering a cheaper fare.
  • the enabled applications T1 and T2 may have been operating in the disabled mode.
  • the embodiments can enable T1 and T2. Thereafter, T1 and T2 can operate in the activated mode.
  • FIG. 10 depicts a UI of an application providing limited functionalities based on state of charge of a battery of the device 300, according to embodiments as disclosed herein.
  • the embodiments include managing rendering of UIs for applications in the device 300 based on the state of charge of the battery of the device 300.
  • the rendered UIs can either allow the user to explore all the functionalities of the applications, or allow the user to explore only limited functionalities offered by the applications.
  • the rendered UIs can control the number of APIs of each of the applications that can be triggered in background.
  • the APIs that are triggered may be specific to display requirement.
  • the embodiments can render an UI, as depicted in FIG. 10, using which the user can access limited functionalities provided by a transportation application. If the state of charge of the battery is normal or high, the embodiments can render the original UI of the transportation application.
  • FIG. 11 depicts an example distribution of tasks/activities, triggered by applications, to other devices based on the state of charge of the battery of the device 300, according to embodiments as disclosed herein. If the state of charge of the battery is low or insufficient to perform the activities or functions triggered by the user through the applications, then the embodiments include requesting other devices, viz., 1101-1105, to perform the activities or functions triggered by the applications in the device 300. The embodiments include detecting the devices 1101-1105 that are in the vicinity of the device 300 or in an IoT environment in which the device 300 is present.
  • the request can be issued if the device 300 is unable to perform the activities due to insufficient power in the battery, and the devices 1101-1105 have capability and have sufficient power to perform the activities triggered by the applications.
  • the embodiments include detecting a speaker (considering 1101 is a speaker) capable of playing music and ensuring that the speaker 1101 is having sufficient power to play music. This can prolong the battery charge cycle as the power consumption of the device 300 will be reduced.
  • the embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements.
  • the network elements shown in FIG. 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
  • the device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein.
  • the method embodiments described herein could be implemented partly in hardware and partly in software.
  • the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.

Abstract

Methods and systems for managing mode of operation of applications in a device operating in a power saving mode are disclosed. Embodiments allow the applications to operate in one of the power saving modes, viz., an activated mode, a standby mode, or a disabled mode. The embodiments allow the applications to navigate through the different power saving modes based on contextual data mined from the applications and power available in the device. The applications operating in the activated mode are displayed. The contextual data associated with the applications are mined in background. Based on the mode of operation of the applications, hardware performance of the device is optimized. If power available is low, UIs (for applications operating in the activated mode) with limited functionality are displayed; and tasks triggered by the applications, operating in the activated mode and the standby mode, are distributed to other devices close to the device.

Description

METHODS AND SYSTEMS FOR MANAGING NAVIGATION OF MODES OF OPERATION OF APPLICATIONS IN A DEVICE
Embodiments herein relate to power management in devices, and more particularly to methods and systems for managing navigation of a power saving mode in which applications present on a device can operate.
Currently, devices can operate in a power saving mode automatically (on detecting that the energy available in the battery is lower than a threshold) or manually. The device operating in the power saving mode can perform a static power optimization, wherein applications in the device can be detected and put to sleep or disabled based on pre-defined criteria. Examples of the criteria can be significant memory usage and power consumption, running in background for a considerable period, depleting battery charge, and so on. The static power optimization can be performed primarily for prolonging the charge cycle of the battery.
When one or more applications are disabled when in the power saving mode, resources allocated to the applications are withdrawn. If the user initiates the applications again, the resources are reallocated for enabling the applications. Frequent allocation and deallocation can lead to greater power consumption.
The devices can also switch to a power saving mode, wherein all, but the most important, applications are disabled. The classification of importance is generally fixed or can be varied by user intervention. This can cause inconvenience if a user indents to use an application in the power saving mode which is not classified as important. In this circumstance, the user needs to either disable the low power mode, such that the intended application can be enabled and used; or manually classify the intended application as important so that the application is not disabled in the power saving mode.
FIG. 1 depicts an example, wherein a device operating in a power saving mode allows enablement of a minimum number of applications. Consider that the power available in the battery of the device is less than a threshold level. The device can either switch to the power saving mode automatically or the user can trigger the power saving mode. As depicted, in FIG. 1, the device can display six applications, viz., App1-App6, which are enabled for usage. The enabled applications have been classified as important by the device or by the user. The classification is fixed and if the user intends to use an application apart from App1-App6, the user needs to disable the power saving mode. Else, if the user intends to use the application in the power saving mode, then the user needs to manually classify the application as important.
FIG. 2 depicts manual selection of applications to be disabled in the power saving mode. As depicted in FIG. 2, the user can manually navigate to the power saving menu of the device for selecting the applications that are to be disabled in the power saving mode. The user can select the applications (user selects App1, App3 and App 4) that the user intends to disable when the device operates in the power saving mode. When it is detected that the power available in the battery of the device is less than the threshold level, or if the user sets the device in the power saving mode, the selected applications, i.e., App1, App3 and App 4, are disabled.
The principal object of the embodiments herein is to disclose methods and systems for managing navigation of power saving modes, in which applications in a device can operate, based on mined contextual data associated with the applications and power available in the device.
Another object of the embodiments herein is to enable or disable the applications automatically based on the mined contextual data associated with the applications.
Another object of the embodiments herein is to perform instant optimization of hardware and software performance during the enablement and disablement of the applications.
Another object of the embodiments herein is to display User Interface (UI) for the applications, using a low power processor, supporting limited functionalities.
Another object of the embodiments herein is to distribute activities, which are triggered by the applications, for execution by other devices capable of executing the activities, wherein the device triggering the activities and the other devices can be a part of an Internet of Things (IoT) environment.
Accordingly, embodiments herein provide methods and systems for managing navigation of power saving modes, in which applications in a device can operate. Embodiments herein allow the applications to operate in one of the power saving modes, viz., an activated mode, a standby mode, or a disabled mode. The embodiments allow the applications to navigate through the different power saving modes of operation based on contextual data, mined from the applications, and power available in the battery of the device. The applications operating in the activated mode can be displayed on the device. The contextual data associated with the applications can be mined in the background. Based on the mode of operation of the applications, hardware performance of the device can be optimized. If power available in the device is low, UIs (for applications operating in the activated mode) with limited functionality are displayed; and tasks triggered by the applications operating in the activated mode and the standby mode can be distributed to other devices in the vicinity of the device.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
Embodiments herein disclose methods and systems for managing navigation of power saving modes, in which applications in a device can operate. The power saving modes, in which the applications can operate at a particular time are, viz., an activated mode, a standby mode, and a disabled mode. The embodiments include mining contextual data associated with the applications in the background. The contextual data can include application usage pattern, access time, location of usage, application data, genre of application, and so on. The embodiments include navigating through the power saving modes, in which each of the applications are operating based on the mined contextual data associated with the applications and power available in the device. For example, an application operating in the activated mode can be made to operate in the standby mode or the disabled mode. In the activated mode, an application can be enabled, and in the disabled mode, the application can be disabled.
In an embodiment, the applications can be run using a low power processor when the device is in the power saving mode. When the applications are run using the low power processor, the embodiments include displaying a User Interface (UI) which provides limited functionalities in comparison with a UI displayed when the application is run using an application processor.
In an embodiment, the device can distribute activities that are triggered by the applications to other devices that are part of an Internet of Things (IoT) environment. When the device is in power saving mode and an activity is triggered by an application in the device, then the device can detect other devices in the IoT environment that are capable of and have adequate power to perform the activity and can provide instructions to the other detected devices to perform the activity. This can minimize the power requirement load of the device.
Embodiments herein are illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
FIG. 1 depicts an example, wherein a device operating in a power saving mode allows enablement of a minimum number of applications;
FIG. 2 depicts manual selection of applications to be disabled in the power saving mode;
FIG. 3 depicts various units of a device for managing navigation of power saving modes, in which applications in the device can operate, according to embodiments as disclosed herein;
FIG. 4 is a flowchart depicting a method for managing navigation of power saving modes, in which applications in the device can operate, according to embodiments as disclosed herein;
FIG. 5 depicts an example timeline, within which a sports application navigates from a disabled mode to an activated mode and vice-versa, according to embodiments as disclosed herein;
FIGS. 6a and 6b is an example use case scenario depicting enablement and disablement of applications based on location of the device, according to embodiments as disclosed herein;
FIG. 7 depicts an example timeline during which the applications in the device are enabled, according to embodiments as disclosed herein;
FIGS. 8a and 8b is an example use case scenario depicting navigation of the operating mode of applications in the device based on application data, according to embodiments as disclosed herein;
FIGS. 9a and 9b is an example use case scenario depicting enablement of applications in the device based on application genre, according to embodiments as disclosed herein;
FIG. 10 depicts a User Interface (UI) of an application providing limited functionalities based on state of charge of a battery of the device, according to embodiments as disclosed herein; and
FIG. 11 depicts an example distribution of tasks/activities, triggered by applications, to other devices based on the state of charge of the battery of the device, according to embodiments as disclosed herein.
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
Referring now to the drawings, and more particularly to FIGS. 3 through 11, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
FIG. 3 depicts various units of a device 300 for managing navigation of power saving modes, in which applications in the device 300 can operate, according to embodiments as disclosed herein. As depicted in FIG. 3, the device 300 includes an application mode manager 301, a display 302, a processor 303, and a communication interface 304. Examples of the device 300 can be, but not limited to, a smart phone, a mobile phone, an IoT device, a wearable device, a vehicle infotainment system, a computer, a laptop, a tablet, and so on.
The application mode manager 301 can determine whether the device is in a power saving mode. The application mode manager 301 can facilitate the applications in the device 300 to navigate through different operating modes. The power saving modes in which the applications can operate can be an activated mode, a standby mode, and a disabled mode. The applications can operate in one of the power saving modes at a particular instant. In the activated mode the applications can operate in both foreground and background. In the standby mode, the applications can be put to sleep. In the disabled mode, the applications cannot be launched as long as the device 300 is in the power saving mode.
The application mode manager 301 can mine contextual data associated with the applications in background. The contextual data associated with at least one application can be mined by obtaining information using background context based services. The mining can involve identifying usage pattern of the applications, access time, location of usage, inter-relationship between application data of the different applications, type of data and importance of the data of the applications, genre of the applications, and so on. The information can be transformed into a comprehensible structure to form the contextual data. Based on the mined contextual data, the application mode manager 301 can allow the applications in the device 300 to operate in either of the activated mode, standby mode, or disabled mode. If an application is operating in the activated mode, it can be understood that the application is enabled. Conversely, if an application is operating in the disabled mode, it can be understood that the application is disabled.
In an embodiment, the application mode manager 301 can be a part of an Artificial Intelligence (AI) engine in the device 300.
The application mode manager 301 can optimize hardware and software performance when applications can be enabled or disabled. The optimization can include adjusting Central Processing Unit (CPU) frequency; User Interface (UI) rendering of the at least one application by the processor 303; managing operation of the processor 303, access to cores of the CPU, and touch activation on the display 302; varying screen resolution; and so on. In an example, if the mode of operation of an application is navigated to the disabled mode, then the Central Processing Unit (CPU) frequency or resolution can be decreased. Similarly, if the mode of operation of an application is navigated to the activated mode, the Central Processing Unit (CPU) frequency and/or resolution can be increased.
In an embodiment, the application mode manager 301 can prioritize applications that can operate in the activated mode. If the device 300 is unable to perform the activities triggered by the applications operating in the activated mode, the application mode manager 301 can navigate the mode of operation, of a predefined number of applications with lower priorities, from the activated mode to the standby mode or the disabled mode. Based on the number of applications (with higher priority) operating in the activated mode, the hardware and software performance can be optimized.
The application mode manager 301 can request other devices to perform tasks or activities that are triggered by the applications, if the device 300 is operating in the power saving mode. The request can be issued if the device 300 is unable to perform the activities triggered by the applications due to insufficient power in the battery and/or the other devices have the capability and have sufficient power to perform the activities triggered by the applications. The device 300 can detect presence of the other devices that are in the vicinity of the device 300 or in an IoT environment in which the device 300 is present. The communication interface 304 can detect the presence of the other devices. The communication between the device 300 and the other devices can be established using examples means such as, but not limited to, Wireless Fidelity (Wi-Fi), Bluetooth, Infrared, Ultra Wideband Communication (UWC), and so on.
The display 302 can display the applications that are currently in the activated mode. The applications in the standby mode and the disabled mode may not be displayed. In the standby mode, the applications can be in a sleep state. In an embodiment herein, the applications operating in the standby mode and the disabled mode may not contribute to power consumption, may not operate in the background, and may not utilize memory of the device 300. In an embodiment herein, the applications operating in the standby mode and the disabled mode may contribute to minimal power consumption, may utilize memory of the device 300 minimally, and so on.
The processor 303 can manage UI rendering for the applications based on whether the device 300 is operating in power saving mode. The display 302 can render original UIs or UIs with limited functionality for the applications. If the device is in operating in the low power mode and if an application needs to be in the activated mode, the processor 303 can allow the display 302 to render an UI of the application with limited functionalities. The rendered UI can control the number of APIs of each of the applications that can be triggered in background. The APIs that are triggered may be specific to display requirement. On the other hand, if the device 300 is operating in normal mode, the processor 303 can allow the display 302 to render the original UI of the application.
FIG. 3 shows exemplary units of the device 300, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the device 300 may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the invention. One or more units can be combined together to perform same or substantially similar function in the device 300.
FIG. 4 is a flowchart 400 depicting a method for managing navigation of power saving modes, in which applications in the device 300 can operate, according to embodiments as disclosed herein. At step 401, the embodiments include mining contextual data associated with at least one application installed in the device 300. The contextual data associated with at least one application can be mined using context based services. The mined data can include the usage pattern of the at least one application, access periods (time of the day or specific days when the at least one application is used), location of usage (location of the device 300 when the at least one application is used), inter-relationship between application data (association of data of one application with another application), content (data type of each of the at least one application and importance of data of the at least one application), genre of the at least one application, and so on. The mining of contextual data associated with the at least one application can be performed in the background over a period of time.
At step 402, the embodiments include determining that the device 300 is operating in a power saving mode. At step 403, the embodiments include managing mode of operation of the at least one application based on the contextual data associated with the at least one application and power available in the device 300 (State of Charge (SoC) of the battery of the device 300). The operating mode can be either of activated mode, standby mode and disabled mode. The mode of operation of an application can either remain same or may vary based on the contextual data associated with the application. In an example, (after determining that the device 300 is operating in the power saving mode) a first application may be allowed to operate in the activated mode, while a second application may be allowed to operate in the standby mode. Based on the contextual data, after a period of time, the first application may be disabled and the second application can be allowed to operate in the standby mode. Thus, the embodiments include navigating the mode of operation of the applications in the device 300.
In an embodiment, if an application is allowed to operate in the activated mode, the application is enabled. The applications that are allowed to operate in the activated mode can be accessed by the user, as the applications that are operating in the activated mode are displayed on the device 300. The user can trigger actions using the application through a UI of the application.
In an embodiment, based on the state of charge of a battery (battery level) of the device 300, the rendered UI may either allow the user to explore all options provided by the application to trigger actions, or allow the user to explore limited functionalities of the application.
In an embodiment, based on the state of charge of the battery of the device 300, the device 300 can request other devices to perform at least one operation triggered by at least one application operating in the activated mode. The embodiments include detecting the other devices in the vicinity of the device 300, or in an IoT environment.
In an embodiment, the applications can be assigned with priorities. If the state of charge of the battery is low, applications assigned with lower priorities can be disabled or allowed to operate in the standby mode, and the applications assigned with higher priorities can be allowed to operate in the activated mode.
At step 404, the embodiments include optimizing the hardware and software performance of the device 300 based on the mode of operation of the at least one application, SoC of the battery of the device 300, and the contextual data associated with the at least one application. In an example, if an application is allowed to operate in the activated mode, the CPU frequency can be increased. In another example, on detecting that the device 300 is operating in the power saving mode, an application initially operating in the activated mode can be disabled (allowed to operate in the disabled mode). Thereafter, the CPU frequency can be decreased and resolution can be reduced. Therefore, based on the modes of operation through which the at least one application navigates; the embodiments include optimizing the hardware and software performance.
The various actions in the flowchart 400 may be performed in the order presented, in a different order, or simultaneously. Further, in some embodiments, some actions listed in FIG. 4 may be omitted.
FIG. 5 depicts an example timeline, within which a sports application navigates from the disabled mode to the activated mode and vice-versa, according to embodiments as disclosed herein. As depicted in FIG. 5, consider that the sports application (labeled as S) installed in the device 300 is in the disabled mode. Based on application data mined from a news application in the background, the embodiments include determining that a sporting event is going to take place at 8:00 PM and terminate at 11:00 PM.
At 7:50 PM, the embodiments include enabling the sports application. The sports application begins to operate in the activated mode and an icon of the sports application can be displayed. When a user clicks on the icon, a UI of the sports application can be rendered. The device 300 can start receiving updates and notifications associated with the sports event when the sports application is operating in the activated mode (from 7:50 PM). The sports application may operate in the activated mode after conclusion of the sporting event at 11:00 PM for receive any concluding notifications relevant to the sporting event. At 11:30 PM, the embodiments include disabling the sports application and the sports application begins to operate in the disabled mode. Once the sports application is disabled, the icon of the sports application disappears from the display 302.
In an embodiment, the device 300 can determine after 11:30 PM that the user had stopped using the sports application. The device 300 can mine the usage pattern of the sports application and disable the sports application.
FIGS. 6a and 6b is an example use case scenario depicting enablement and disablement of applications based on location of the device 300, according to embodiments as disclosed herein. As depicted in FIG. 6a, six applications, viz., App1-App6, are displayed on the device 300. Based on mined contextual data associated with all the applications, such as location of the device 300 and usage of particular applications at particular times, the device 300 can enable, put on standby, or disable applications in the device 300. The applications can be enabling based on future usage requirement, user preference importance, necessity, and so on.
The embodiments include detecting that a user of the device 300 is travelling based on frequent updates in location of the device 300. As the user is travelling, the embodiments include enabling social media applications (labeled as S), music applications (labeled as M), transportation applications (labeled as T), and so on. The enabled applications can operate in the activated mode. As depicted in FIG. 6b, the enabled applications can be displayed in place of some of the applications (amongst App1-App6) that are disabled to display the newly enabled applications. The disabled applications can operate in the disabled mode.
FIG. 7 depicts an example timeline during which the applications in the device 300 are enabled, according to embodiments as disclosed herein. The embodiments include automatically navigating through the modes of operation of the applications based on mined contextual data associated with the applications. As depicted in FIG. 7, based on usage pattern (usage of applications at particular times) and relationship between application data of different applications, the embodiments can enable, put on standby, or disable applications in the device 300.
Consider that at 7:00 PM, transportation applications (labeled as T) are enabled. After enablement, the transportation applications can operate in the activated mode. The enablement of the transportation applications at 7:00 PM can be based on contextual data. The contextual data is mined by monitoring for a period of time the usage of the transportation applications at approximately 7:00 PM. The device 300 can assume that the user is likely to travel at around 7:00 PM and enable the transportation applications. At 7:15 PM, social media applications (labeled as S) and music applications (labeled as M) can be enabled. The device 300 can detect usage of the social media applications and music applications while the user travels. Similarly, at 8:00 PM, sports and entertainment applications (labeled as E) can be enabled and at 8:30 PM, food delivery applications (labeled as F) can be enabled. The enablement of these applications can be based on usage of the corresponding applications at the specific times.
FIGS. 8a and 8b is an example use case scenario depicting navigation of the operating mode of applications in the device 300 based on application data, according to embodiments as disclosed herein. As depicted in FIG. 8a, consider that the user makes a movie ticket purchase using a movie ticket booking application. The movie is scheduled at 7:30 PM at a particular date (6th Feb 2019). The device can extract (mine for future) contextual data regarding the booked ticket and the movie schedule and use the extracted contextual data to enable applications that can facilitate the user to reach a theatre where the movie is being screened. As depicted in FIG. 8b, at 7:00 PM on the particular day, the device 300 can enable the transportation applications, which may have been operating in the disabled mode. The transportation applications operate in the activated mode at 7:00 PM.
FIGS. 9a and 9b is an example use case scenario depicting enablement of applications in the device 300 based on application genre, according to embodiments as disclosed herein. Consider that the user intending to book a ride. The user can select a transportation application to book the ride. As depicted in FIG. 9a, fares for booking the ride using the transportation application are higher than usual. The embodiments can determine a contextual data, i.e., information that the fare for booking the ride using the transportation application is higher than usual. In such situations, as depicted in FIG. 9b, the embodiments include enabling applications of similar genre, i.e., transportation applications (labeled as T1 and T2), which facilitate the user to compare the fares of the different transportation applications and book the ride using the transportation application offering a cheaper fare. The enabled applications T1 and T2 may have been operating in the disabled mode. After obtaining contextual data (higher fares) from the transportation application currently used by the user, the embodiments can enable T1 and T2. Thereafter, T1 and T2 can operate in the activated mode.
FIG. 10 depicts a UI of an application providing limited functionalities based on state of charge of a battery of the device 300, according to embodiments as disclosed herein. The embodiments include managing rendering of UIs for applications in the device 300 based on the state of charge of the battery of the device 300. The rendered UIs can either allow the user to explore all the functionalities of the applications, or allow the user to explore only limited functionalities offered by the applications. The rendered UIs can control the number of APIs of each of the applications that can be triggered in background. The APIs that are triggered may be specific to display requirement.
If the state of charge of the battery is low and if a transportation application needs to operate in the activated mode, the embodiments can render an UI, as depicted in FIG. 10, using which the user can access limited functionalities provided by a transportation application. If the state of charge of the battery is normal or high, the embodiments can render the original UI of the transportation application.
FIG. 11 depicts an example distribution of tasks/activities, triggered by applications, to other devices based on the state of charge of the battery of the device 300, according to embodiments as disclosed herein. If the state of charge of the battery is low or insufficient to perform the activities or functions triggered by the user through the applications, then the embodiments include requesting other devices, viz., 1101-1105, to perform the activities or functions triggered by the applications in the device 300. The embodiments include detecting the devices 1101-1105 that are in the vicinity of the device 300 or in an IoT environment in which the device 300 is present. The request can be issued if the device 300 is unable to perform the activities due to insufficient power in the battery, and the devices 1101-1105 have capability and have sufficient power to perform the activities triggered by the applications. In an example, if it is required to play music, the embodiments include detecting a speaker (considering 1101 is a speaker) capable of playing music and ensuring that the speaker 1101 is having sufficient power to play music. This can prolong the battery charge cycle as the power consumption of the device 300 will be reduced.
The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in FIG. 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
The embodiments disclosed herein describe methods and systems for managing navigation of power saving modes in which applications in the device 300 can operate. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment through or together with a software program written in e.g. Very high speed integrated circuit Hardware Description Language (VHDL) another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.
The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

Claims (27)

  1. A method for managing power saving mode of operation for applications in a device (300), the method comprising:
    detecting that the device (300) is operating in a power saving mode;
    mining, by the device (300), contextual data associated with at least one application; and
    managing, by the device (300), availability of at least one application based on the mined contextual data and State of Charge (SoC) of a battery in the device (300), wherein the at least one application operates in a power saving mode when available.
  2. The method, as claimed in claim 1, wherein the power saving mode of operation is one of an activated mode, a standby mode, and a disabled mode, wherein the at least one application operating in the activated mode is displayed.
  3. The method, as claimed in claim 1, wherein the at least one application operates in the activated mode when available.
  4. The method, as claimed in claim 1, wherein the contextual data associated with the at least one application comprises: pattern of usage of the at least one application, location of device (300) during usage of the at least one application, access time of the at least one application, application data of the at least one application, importance of data of the at least one application, pending activity of the at least one application, and genre of the at least one application.
  5. The method, as claimed in claim 1, wherein the method further comprises optimizing hardware performance of the device (300) based on the mined contextual data, the SoC of the battery and the power saving mode of operation of the at least one application, wherein the optimization comprises managing Central Processing Unit (CPU) frequency, rendering of the at least one application by a processor (303), operation of the processor (303), access to cores of the CPU, touch activation on the display (302), and screen resolution.
  6. The method, as claimed in claim 1, wherein the method further comprises:
    determining that the SoC of the battery of the device (300) is less than a threshold SoC;
    identifying at least one feature of the at least one application based on the mined contextual data; and
    rendering, on the display (302), by the processor (303), a User Interface (UI), for the at least one application operating in the activated mode, with the at least one identified feature.
  7. The method, as claimed in claim 1, wherein the method further comprises:
    determining that the SoC of the battery of the device (300) is less than the threshold SoC;
    detecting, by a communication interface (304), at least one other device (1101-1105) in vicinity of the device (300) capable of performing at least one activity triggered by the at least one application operating in one of the activated mode and the standby mode; and
    requesting, by the application mode manager (301), the at least one other device (1101-1105) to perform the at least one activity.
  8. The method, as claimed in claim 7, wherein the capability is determined based on at least one of: viability of the at least one other device (1101-1105) and availability of power in the at least one other device (1101-1105).
  9. The method, as claimed in claim 1, wherein the method further comprises:
    assigning, by the application mode manager (301), a priority to each of the at least one application;
    determining that the SoC of the battery of the device (300) is less than a threshold SoC; and
    managing, by the application mode manager (301), the navigation of power saving mode of operation of the at least one application based on the assigned priority.
  10. A device (300) for managing power saving mode of operation for applications in the device (300), the device (300) configured to:
    detect that the device (300) is operating in a power saving mode;
    mine, by an application mode manager (301), contextual data associated with at least one application; and
    manage, by the device (300), availability of the at least one application based on the mined contextual data and State of Charge (SoC) of a battery in the device (300), wherein the at least one application operates in a power saving mode when available.
  11. The device (300), as claimed in claim 10, wherein the power saving mode of operation is one of an activated mode, a standby mode, and a disabled mode, wherein the at least one application operating in the activated mode is displayed.
  12. The device (300), as claimed in claim 10, wherein the at least one application operates in the activated mode when available.
  13. The device (300), as claimed in claim 10, wherein the contextual data associated with the at least one application comprises: pattern of usage of the at least one application, location of device (300) during usage of the at least one application, access time of the at least one application, application data of the at least one application, importance of data of the at least one application, pending activity of the at least one application, and genre of the at least one application.
  14. The device (300), as claimed in claim 10, wherein the device (300) is further configured to optimize hardware performance of the device (300) based on the mined contextual data, the SoC of the battery and the power saving mode of operation of the at least one application, wherein the optimization comprises managing Central Processing Unit (CPU) frequency, rendering of the at least one application by a processor (303), operation of the processor (303), access to cores of the CPU, touch activation on the display (302), and screen resolution.
  15. The device (300), as claimed in claim 10, wherein the device (300) is further configured to:
    determine that the SoC of the battery of the device (300) is less than a threshold SoC;
    identify at least one feature of the at least one application based on the mined contextual data; and
    render, on the display (302), by the processor (303), a User Interface (UI), for the at least one application operating in the activated mode, with the at least one identified feature.
  16. The device (300), as claimed in claim 10, wherein the device (300) is further configured to:
    determine that the SoC of the battery of the device (300) is less than the threshold SoC;
    detect, by a communication interface (304), at least one other device (1101-1105) in vicinity of the device (300) capable of performing at least one activity triggered by the at least one application operating in one of the activated mode and the standby mode; and
    request, by the application mode manager (301), the at least one other device (1101-1105) to perform the at least one activity.
  17. The device (300), as claimed in claim 16, wherein the capability is determined based on at least one of: viability of the at least one other device (1101-1105) and availability of power in the at least one other device (1101-1105).
  18. The device (300), as claimed in claim 10, wherein the device (300) is further configured to:
    assign, by the application mode manager (301), a priority to each of the at least one application;
    determine that the SoC of the battery of the device (300) is less than a threshold SoC; and
    manage, by the application mode manager (301), the navigation of power saving mode of operation of the at least one application based on the assigned priority.
  19. A method for managing navigation of power saving mode of operation for applications in a device (300), the method comprising:
    detecting that the device (300) is operating in a power saving mode;
    mining, by the device (300), contextual data associated with at least one application; and
    navigating, by the device (300), across power saving modes of operation by the at least one application based on the mined contextual data and State of Charge (SoC) of a battery in the device (300).
  20. The method, as claimed in claim 19, wherein the power saving mode of operation is one of an activated mode, a standby mode, and a disabled mode.
  21. The method, as claimed in claim 20, wherein the method further comprises displaying, by a display (302), at least one application operating in the activated mode.
  22. The method, as claimed in claim 19, wherein the contextual data associated with the at least one application comprises: pattern of usage of the at least one application, location of device (300) during usage of the at least one application, access time of the at least one application, application data of the at least one application, importance of data of the at least one application, pending activity of the at least one application, and genre of the at least one application.
  23. The method, as claimed in claim 19, wherein the method further comprises optimizing hardware performance of the device (300) based on the mined contextual data, the SoC of the battery and the power saving mode of operation of the at least one application, wherein the optimization comprises managing Central Processing Unit (CPU) frequency, rendering of the at least one application by a processor (303), operation of the processor (303), access to cores of the CPU, touch activation on the display (302), and screen resolution.
  24. The method, as claimed in claim 21, wherein the method further comprises:
    determining that the SoC of the battery of the device (300) is less than a threshold SoC;
    identifying at least one feature of the at least one application based on the mined contextual data; and
    rendering, on the display (302), by the processor (303), a User Interface (UI), for the at least one application operating in the activated mode, with the at least one identified feature.
  25. The method, as claimed in claim 21, wherein the method further comprises:
    determining that the SoC of the battery of the device (300) is less than the threshold SoC;
    detecting, by a communication interface (304), at least one other device (1101-1105) in vicinity of the device (300) capable of performing at least one activity triggered by the at least one application operating in one of the activated mode and the standby mode; and
    requesting, by the application mode manager (301), the at least one other device (1101-1105) to perform the at least one activity.
  26. The method, as claimed in claim 25, wherein the capability is determined based on at least one of: viability of the at least one other device (1101-1105) and availability of power in the at least one other device (1101-1105).
  27. The method, as claimed in claim 19, wherein the method further comprises:
    assigning, by the application mode manager (301), a priority to each of the at least one application;
    determining that the SoC of the battery of the device (300) is less than a threshold SoC; and
    managing, by the application mode manager (301), the navigation of power saving mode of operation of the at least one application based on the assigned priority.
PCT/KR2019/005777 2018-08-16 2019-05-14 Methods and systems for managing navigation of modes of operation of applications in a device WO2020036291A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201841030752 2018-08-16
IN201841030752 2019-04-26

Publications (1)

Publication Number Publication Date
WO2020036291A1 true WO2020036291A1 (en) 2020-02-20

Family

ID=69525963

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2019/005777 WO2020036291A1 (en) 2018-08-16 2019-05-14 Methods and systems for managing navigation of modes of operation of applications in a device

Country Status (1)

Country Link
WO (1) WO2020036291A1 (en)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1734436A1 (en) * 2005-06-16 2006-12-20 LG Electronics Inc. Automatically controlling processor mode of multi-core processor
US20120315960A1 (en) * 2011-06-07 2012-12-13 Lg Electronics Inc. Mobile terminal and battery power saving mode switching method thereof
WO2014077628A1 (en) * 2012-11-16 2014-05-22 Samsung Electronics Co., Ltd. Monitoring and managing processor activity in power save mode of portable electronic device
US20150261284A1 (en) * 2014-03-12 2015-09-17 Samsung Electronics Co., Ltd. Method and apparatus for saving power of portable electronic device
US20160187957A1 (en) * 2014-12-24 2016-06-30 Fu Tai Hua Industry (Shenzhen) Co., Ltd. Electronic device and method for saving power in the electronic device

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1734436A1 (en) * 2005-06-16 2006-12-20 LG Electronics Inc. Automatically controlling processor mode of multi-core processor
US20120315960A1 (en) * 2011-06-07 2012-12-13 Lg Electronics Inc. Mobile terminal and battery power saving mode switching method thereof
WO2014077628A1 (en) * 2012-11-16 2014-05-22 Samsung Electronics Co., Ltd. Monitoring and managing processor activity in power save mode of portable electronic device
US20150261284A1 (en) * 2014-03-12 2015-09-17 Samsung Electronics Co., Ltd. Method and apparatus for saving power of portable electronic device
US20160187957A1 (en) * 2014-12-24 2016-06-30 Fu Tai Hua Industry (Shenzhen) Co., Ltd. Electronic device and method for saving power in the electronic device

Similar Documents

Publication Publication Date Title
US10467025B2 (en) Managing delivery of code and dependent data using application containers
US20210389973A1 (en) Electronic device and method for operating the same
CN107526640B (en) Resource management method, resource management device, mobile terminal and computer-readable storage medium
US9201693B2 (en) Quota-based resource management
US11385935B2 (en) Task scheduling method and electronic device for implementing same
EP3223151A1 (en) Hot-handover method and device for operating systems, and mobile terminal
CN107479951B (en) Process control method and device, storage medium and electronic equipment
CN111597042A (en) Service thread running method and device, storage medium and electronic equipment
US20190188030A1 (en) Terminal background application management method and apparatus
CN111158879A (en) System resource scheduling method, device, machine readable medium and system
US20100211680A1 (en) Apparatus and method to allocate limited resources
CN111475299A (en) Memory allocation method and device, storage medium and electronic equipment
WO2020036291A1 (en) Methods and systems for managing navigation of modes of operation of applications in a device
CN113495780A (en) Task scheduling method and device, storage medium and electronic equipment
WO2021077261A1 (en) Application program management method and apparatus, electronic device, and storage medium
CN111052083B (en) Method and apparatus for managing scheduling of services during startup
CN113495787A (en) Resource allocation method, device, storage medium and electronic equipment
CN114168355A (en) Application keep-alive method and electronic equipment
CN111459462A (en) Decentralized relock demotion
WO2022196997A1 (en) Method and electronic device for boosting graphics performance
CN116027878A (en) Power consumption adjustment method and electronic equipment
CN117632460A (en) Load adjusting method and terminal equipment
CN116089930A (en) Application management and control method, device and storage medium

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: 19850287

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: 19850287

Country of ref document: EP

Kind code of ref document: A1