CN105930207B

CN105930207B - Electronic device and application control method thereof

Info

Publication number: CN105930207B
Application number: CN201610113694.9A
Authority: CN
Inventors: 金炳旭; 金羲德; 金武永; 金学烈; 李镇求; 渔来镇; 李柱范
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2015-02-27
Filing date: 2016-02-29
Publication date: 2022-02-15
Anticipated expiration: 2036-02-29
Also published as: CN105930207A; AU2016224176B2; AU2016224176A1; KR102395868B1; KR20160105274A

Abstract

The present disclosure provides an electronic device and a method of controlling an application by the electronic device. The electronic device includes a memory configured to store a first application list including applications installed in the electronic device; and a processor configured to update the first application list and restrict operation of the application according to at least one of operation of the application, usage history of the application, and a user request.

Description

Electronic device and application control method thereof

Priority

This application claims priority of korean patent application nos. 10-2015-0028645 and 10-2015-0125851 filed on 27/2015 and 9/2015 and 4/2015, respectively, of the korean intellectual property office, the entire disclosures of each of which are incorporated herein by reference.

Technical Field

The present disclosure relates generally to methods and apparatus for controlling application operation.

Background

Electronic devices use a variety of applications. For example, an application executable by the electronic device may be executed in response to a user's request and may perform various instructions and functions. The application may also be run automatically or according to predetermined conditions.

An application may perform various operations using resources (e.g., power sources (e.g., batteries), networks, memory, processors, etc.) provided by the electronic device. Some applications may run as background operations, i.e., situations where the screen associated with the respective application is not displayed.

Further, some applications run when the electronic device is in an inactive state (e.g., a sleep state, a wait state, a low power operating state, etc.) or when a display of the electronic device is in an inactive state.

Disclosure of Invention

Aspects of the present disclosure are provided to address at least the above problems and/or disadvantages and to provide at least the advantages described below.

Accordingly, aspects of the present disclosure will provide an apparatus and method for performing service and resource management of an electronic device by controlling an application run through the electronic device according to various conditions.

According to an aspect of the present disclosure, an electronic device is provided. The electronic device includes a memory configured to store a first application list including applications installed in the electronic device; and a processor configured to update the first application list and restrict operation of the application according to at least one of operation of the application, usage history of the application, and a user request.

According to another aspect of the present disclosure, an application control method of an electronic device is provided. The application control method includes updating a first application list including applications installed in the electronic device according to at least one of an operation of the applications, a usage history of the applications, and a user request; and restricting operation of the applications included in the first application list.

According to another aspect of the present disclosure, an electronic device is provided. The electronic device comprises a display; a processor; and a memory storing instructions, wherein when at least a portion of the display is inactive, the instructions control the processor to disable execution of a function of the electronic device associated with operation of the application program when the instructions are executed, in accordance with operation of the application program capable of being executed by the electronic device.

According to another aspect of the present disclosure, an electronic device is provided. The electronic device comprises a display, a wireless communication circuit, a volatile memory and a processor; and a non-volatile memory storing software implementing an operating system and instructions, the software, when executed, controlling the processor to load and run at least a portion of the operating system on the volatile memory, load and run an application connected to the operating system on the volatile memory, monitor operation of the application running through operation of the portion of the operating system, and when the display is turned off, unload at least a portion of the application from the volatile memory according to at least a portion of a result of the monitoring of the operation through the portion of the operating system.

Drawings

The above and other aspects, features, and advantages of certain embodiments of the present disclosure will become more apparent from the following description taken in conjunction with the accompanying drawings in which:

FIG. 1 illustrates an electronic device according to an embodiment of the present disclosure;

FIGS. 2A and 2B illustrate an example of restricting application operation according to an embodiment of the present disclosure;

FIGS. 3A and 3B illustrate a user interface according to an embodiment of the present disclosure;

FIGS. 4A and 4B illustrate a user interface according to an embodiment of the present disclosure;

FIGS. 5A and 5B illustrate a user interface according to an embodiment of the present disclosure;

FIGS. 6A and 6B illustrate a user interface according to an embodiment of the present disclosure;

FIGS. 7A and 7B illustrate a user interface according to an embodiment of the present disclosure;

FIG. 8 illustrates a user interface according to an embodiment of the present disclosure;

fig. 9 is a flowchart illustrating an application control method of an electronic device according to an embodiment of the present disclosure;

fig. 10 is a flowchart illustrating an application control method of an electronic device according to an embodiment of the present disclosure;

FIG. 11 illustrates an operational limiting effect of an application according to an embodiment of the present disclosure;

FIG. 12 shows an electronic device according to an embodiment of the present disclosure; and

FIG. 13 shows program modules according to embodiments of the disclosure.

Throughout the drawings, it should be noted that the same reference numerals are used to describe the same or similar elements, features and structures.

Detailed Description

Hereinafter, various embodiments of the present disclosure will be described with reference to the accompanying drawings. However, the present disclosure is not intended to be limited to the specific embodiments, and it is to be understood that the present disclosure is intended to include all modifications and/or equivalents as well as alternatives within the scope and technical scope of the present disclosure. For example, various embodiments of the present disclosure may be modified and are illustrated in the accompanying drawings and described in the related detailed description.

In this document, the expressions "having", "may have", "include", "including", "may include" and "may include" indicate the presence of corresponding features (e.g. elements, functions, operations or components such as numerical values), and do not exclude the presence of additional features.

Moreover, the expression "a or B," "at least one of a or/and B," "one or more of a or/and B," and the like can include any and all combinations of one or more of the associated listed items. For example, the terms "a or B," "at least one of a and B," and "at least one of a or B" may refer to (1) the case where at least one a is included, (2) the case where at least one B is included, or (3) the case where at least one a and at least one B are included.

Expressions such as "first (1 st)", "second (2 nd)", "first (first)", "second (second)", etc. may refer to various elements regardless of the order and/or priority of the corresponding elements, but do not limit the corresponding elements. These types of expressions may be used to distinguish one element from another. For example, "first user device" and "second user device" represent user devices that are different from each other regardless of the order and/or priority of the respective elements. For example, a first element could be termed a second element, and vice-versa, without departing from the scope of the present disclosure.

When an element (e.g., a first element) is said to be coupled (operatively or communicatively) with/to another element (e.g., a second element), "/" (operatively or communicatively) to another element (e.g., a second element), or is said to be connected to another element (e.g., a second element), the first element may be directly coupled/directly coupled to the second element, or directly connected to the second element, or intervening elements (e.g., third elements) may be present therebetween. However, when a first element is said to be "directly coupled"/"directly coupled to" or "directly connected to" a second element, there may be no intervening elements between them.

As used herein, the expression "configured to" may be used, for example, as "adapted to", "having capability", "designed to", "adapted to", "manufactured to" or "capable", as the case may be. The term "configured to" does not mean "specially designed" using only hardware. Rather, the expression "a device is configured to" may mean that the device is "capable of" operating with another device or other means. For example, "a processor configured to perform A, B and C" may represent a general-purpose processor (e.g., a Central Processing Unit (CPU) or an application processor) that may perform the respective operations by running one or more software programs, which may include a special-purpose processor (e.g., an embedded processor) for performing the respective operations.

Unless otherwise specified, singular forms of words may include plural forms. Unless otherwise defined herein, all terms (including technical and scientific terms) used herein may have the same meaning as commonly understood by one of ordinary skill in the art. Furthermore, dictionary definitions and commonly used terms are to be understood as being conventional in the pertinent art and should not be interpreted in an idealized or overly formal sense unless expressly so defined herein. In some cases, even if a term is defined in the specification, the defined term should not be construed as excluding the embodiments of the present disclosure.

An electronic device according to an embodiment of the present disclosure may include a smart phone, a tablet Personal Computer (PC), a mobile phone, a video phone, an e-book reader, a desktop PC, a laptop PC, a notebook computer, a workstation, a server, a Personal Digital Assistant (PDA), a Portable Multimedia Player (PMP), a moving picture experts group (MPEG-1 or MPEG-2) audio layer 3(MP3) player, a mobile medical device, a camera, or a wearable device. Examples of wearable devices may include accessory-type wearable devices (e.g., watches, rings, wristbands, anklets, necklaces, glasses, contact lenses, or head-mounted devices (HMDs)), fabric or garment-integrated wearable devices (e.g., electronic garments), body-carried wearable devices (e.g., pads or tattoos), or implantable wearable devices (e.g., implantable circuits).

The electronic device may be an intelligent home appliance, such as a Television (TV), a Digital Versatile Disc (DVD) player, an audio device, a refrigerator, an air conditioner, a cleaner, an oven, a microwave oven, a washing machine, an air purifier, a set-top box, a home automation control panel, a security control panel, a TV box (e.g., Samsung)

Apple

Or Google

) A gaming machine (e.g.,

and

) An electronic dictionary, an electronic key, a camcorder, or an electronic photo frame.

Further, the electronic device may include a medical instrument (e.g., a variety of portable medical measurement devices (e.g., blood glucose monitoring devices, heart rate monitors, blood pressure meters, thermometers, etc.), Magnetic Resonance Angiography (MRA) devices, Magnetic Resonance Imaging (MRI) devices, Computed Tomography (CT) devices, scanners, ultrasound devices, etc.), navigation devices, Global Navigation Satellite Systems (GNSS), tachographs (EDR), Flight Data Recorders (FDR), vehicle entertainment devices, marine electronic measurement equipment (e.g., navigation systems, gyrocompasses), avionic devices, security devices, car stereos, industrial or home robots, Automated Teller Machines (ATMs), point of sale (POS) devices, or internet of things (IoT) devices (e.g., light bulbs, various sensors, electronic or gas meters, sprinkler devices, fire alarms, thermostats, etc.), Street lights, ovens, training equipment, hot water tanks, heaters, water heaters, etc.).

The electronic device may also include furniture, portions of a building/structure, a circuit board, an electronic signature receiving device, a projector, or a variety of measuring instruments (e.g., a water meter, an electricity meter, a gas meter, or a wavelength meter, etc.).

Electronic devices according to various embodiments of the present disclosure may be flexible electronic devices.

Additionally, the electronic device may be a combination of one or more of the above devices.

Furthermore, the electronic device according to the embodiments of the present disclosure is not limited to the above-described devices, and may include a new electronic device developed according to a new technology.

Herein, the term "user" may refer to a person using an electronic device, or may refer to a device using an electronic device (e.g., an artificial intelligence electronic device).

Fig. 1 illustrates an electronic device according to an embodiment of the present disclosure.

Referring to fig. 1, the electronic device 100 includes a communication module 110, a memory 120, an input module 130, a time management module 140, a battery 150, a display 160, and a control module 170.

The communication module 110 may communicate with the external electronic device 200 or the push server 300. For example, the communication module 110 may include a Radio Frequency (RF) module, a cellular module, a wireless-fidelity (Wi-Fi) module, a bluetooth module, a Global Positioning System (GPS) module (or GNSS module), or a Near Field Communication (NFC) module. The electronic device 100 may be connected to, for example, a network (e.g., an internet network or a mobile communication network) through at least one of the above-described modules and may communicate with the external electronic device 200 through the network. Alternatively, the electronic device 100 may be directly connected with the external electronic device 200 and communicate with the external electronic device 200.

The communication module 110 may communicate with the push server 300.

The push server 300 provides a push service. For example, a push service may refer to an information transfer service in which the push server 300 initiates a request for transferring information. For example, the push server 300 may transmit predetermined data to a client device (e.g., the electronic device 100) although there is no request initiated by the client device. The client device may process the received data, such as by an application, and provide (e.g., display) the received data to the user.

If the application uses the push service, the communication module 110 may register information about the application or the electronic device 100 in the push server 300 under the control of the control module 170. For example, the communication module 110 may transmit the user identification information (or the device identification information) to the push server 300. Upon receiving the user identification information, the push server 300 may generate registration information (e.g., a registration Identifier (ID)) regarding the push service according to the received user identification information and may transmit the generated registration information to the electronic device 100. If information about an application or the electronic device 100 is registered in the push server 300, the communication module 110 may receive push data associated with various applications from the push server 300.

The memory 120 may store instructions or data associated with at least another component included in the electronic device 100. The memory 120 includes a first memory 121 and a second memory 123. For example, the first memory 121 may be a volatile memory (e.g., a Random Access Memory (RAM)). The first memory 121 may store instructions or data associated with the operation of the application. For example, if a specific application is executed, the first memory 121 may temporarily store some of data of the executed application (e.g., data associated with the execution of the application).

The second memory 123 may be a non-volatile memory (e.g., a flash memory, a Secure Digital (SD) card, etc.). The second memory 123 may store software or programs. For example, the second memory 123 may store a kernel, middleware, an Application Programming Interface (API), or an application (or application program).

The second memory 123 may store an application list including at least some of the applications installed in the electronic device 100 (or executable by the electronic device 100). For example, when a new application is added to or deleted from the application list, the application list stored in the second memory 123 may be updated. The attributes of the applications included in the application list may be changed.

TABLE 1

Table 1 shows an example of an application list. Referring to table 1, the application list includes an application name item (e.g., application), an application operation type item (e.g., type), a last run item (e.g., last run), a notification detection item (e.g., notification detection), and an application status item (e.g., status).

The application operation type item may include information on whether the application uses the push service and/or information on whether the application performs a predetermined operation periodically or non-periodically.

The application may set a timer and perform a predetermined operation after a certain time has elapsed. For example, an application that periodically performs a predetermined operation may have a period timer attribute. As another example, an application that performs a predetermined operation non-periodically may have a non-periodic timer attribute.

The notification detection item may indicate whether the user, another application, or an external electronic device responds to a notification associated with the application. The notification detection item may include information about the likelihood that the user will verify the notification. The notification detection item may include information about the time taken until the user responds to the notification associated with the application. The notification detection item may include information about the location (e.g., home, office, etc.) where the user responded to the notification associated with the application, and/or information about the date and time (e.g., day and time) that the user responded to the notification associated with the application.

The application state item may classify and represent the operating state of the current application as one or more operating states. For example, the application state item may include information on whether the current application is allowed to operate or restricted from operating and/or information on whether the application is in a 'normal' state, a 'frozen' state, and a 'semi-frozen' state. The 'normal' state may be a state in which the application is allowed to operate. The 'frozen' state may be a state in which the application is prohibited from at least some of the operations of the application. The 'semi-frozen' state may be a state in which the operation of the application is not prohibited, but the operation cycle is postponed or the number of operations is reduced. In the 'frozen' state, the application may be inhibited from running except in response to a request from a user.

The application state item may be determined when the application is registered in the application list. For example, if an application is registered in the application list, the application may be determined to be one of a 'normal' state, a 'semi-frozen' state, and a 'frozen' state.

A predetermined event for an application registered in the application list may occur or the application may be changed to another state by a user request.

Referring again to fig. 1, the input module 130 may receive an instruction from a user or another external device. The input module 130 may include a touch sensor panel that senses a touch operation of a user and/or a pen sensor panel (e.g., a digitizer) that senses a pen operation of the user. The input module 130 may include a motion sensor to recognize a user's motion and/or a voice sensor to recognize a user's voice.

The input module 130 may receive a user instruction for selecting whether to use a function that restricts the operation of the application. The input module 130 may receive a user instruction for adding a specific application on the application list or deleting a specific application from the application list. The input module 130 may receive a condition (or reference setting) for limiting the operation of the applications included in the application list. For example, the condition may include at least one of a location of the electronic device 100, a time, a user, a remaining capacity of the battery 150, a rate of consumption of the battery 150, or a wireless communication usage (e.g., cellular data usage).

The time management module 140 may manage time information. For example, the time management module 140 may count time and store information about year/month/day/hour/minute/second in the memory 120. The time management module 140 may include a Real Time Clock (RTC) circuit.

The time management module 140 may set a timer. For example, the time management module 140 may set a timer periodically or non-periodically according to a request of an application. If the predetermined time is reached, the time management module 140 may notify the control module 170 that the timer has expired. If the predetermined time is reached, the control module 170 may control the operation of the application associated with the corresponding timer.

The battery 150 may power the electronic device 100 and/or power each component included in the electronic device 100 to perform a function.

The display 160 may display a user interface. For example, the display 160 may display a user interface for adding or deleting a particular application to or from a list of applications. The user may add or delete one or more applications to or from the list of applications through a user interface displayed on the display 160.

The display 160 may display a user interface for changing the state of the applications included in the application list. For example, the user may change the state of the specific application from a 'normal' state to a 'frozen' state, may change the state of the specific application from a 'frozen' state to a 'normal' state, or may change the state of the specific application from a 'normal' state to a 'semi-frozen' state through a user interface displayed on the display 160.

The display 160 may display a user interface including information about at least some of the applications included in the application list. For example, the user interface may include a drain rate of the battery 150 caused by the application or an amount of power of the battery 150 consumed by the application.

Applications may be limited in their operation.

The display 160 may display icons of applications installed in the electronic device 100. The application icon may be changed and displayed according to whether the operation of the application is restricted.

The control module 170 may control the overall operation of the electronic device 100. For example, the control module 170 may control each of the communication module 110, the memory 120, the input module 130, the time management module 140, the battery 150, and the display 160 to control the operation of the application.

The control module 170 may include at least one processor. The control module 170 (e.g., application processor) may be implemented with a System On Chip (SOC) including a CPU, a Graphics Processing Unit (GPU), a memory, and the like.

The control module 170 may include an active mode (or awake mode) and an inactive mode (or sleep mode). In the active mode, the control module 170 executes an application or performs a specific operation by executing the application or according to a state in which the control module 170 can perform the specific operation. The control module 170 may run an application in the active mode and may provide a variety of services to the user, for example, a Social Network Service (SNS), an instant messaging service, and a game service.

In the sleep mode, the control module 170 does not perform any operation or may not perform any operation.

The control module 170 may enter the sleep mode if certain conditions are met in the active mode. For example, if the user does not input a user instruction during a predetermined time, the control module 170 may enter a sleep mode. The control module 170 may deactivate the display 160 (e.g., may power down the display 160) before entering the sleep mode and before the sleep mode may be entered.

The control module 170 may identify a trigger for entering the active mode from the sleep mode. If a trigger signal for entering the active mode from the sleep mode is received, the control module 170 may enter the active mode and perform an operation. For example, if there is a touch on the touch sensor panel, a hardware key input, an output from a predetermined sensor, voice recognition of a specific word, and/or a gesture (motion) of a specific pattern input in the sleep mode, the control module 170 may enter the active mode and may perform an operation according to a user instruction.

Various embodiments of the present disclosure, described herein with reference to a sleep mode as an example, may also be performed in a state where the display 160 is inactive or other modes (e.g., sleep mode) in which the electronic device (e.g., electronic device 100) operates at low power.

When the control module 170 is in the sleep mode, the application may request the control module 170 to perform a specific operation. Accordingly, the control module 170 may operate in an active mode to perform operations requested by the application. If the corresponding operation is completed, the control module 170 may operate in the sleep mode again.

If the control module 170 is in the sleep mode, is woken up and performs an operation in response to a request of an application, there may be a period of time in which the amount of consumed current temporarily increases. The operation requested by the application may include unnecessary or selective operations for running the application as well as necessary operations. For example, while receiving data through the push server 300, the messaging application may transmit keep-alive messages to the application server and may maintain a connection with the application server. Alternatively, the application using the positioning information may set a timer in the time management module 140, may periodically verify the location of the electronic device 100, and may transmit the verified location to the application server.

If the control module 170 discontinuously or insufficiently maintains the sleep mode state due to unnecessary or selective operation of the application, the amount of power of the battery 150 consumed by the application may be significantly increased. In particular, when more applications are installed in the electronic device 100, there is a greater possibility that the wake-up operation of the control module 170 will frequently occur. Therefore, the usable time of the battery 150 may be reduced.

The control module 170 may control the application in the sleep mode state to prevent the battery 150 from being consumed by the application due to unnecessary or selective operation of the application.

The control of the application may include a restriction (prohibition or delay) of at least some of the operations of the application. In addition, the limits of at least some of the operations may be maintained until a predetermined operation release event occurs (e.g., until an application is run according to a user request) or until a request to release the operation limits is received from the user. For example, the operation restriction may be maintained before the user requests the release of the operation restriction regardless of the sleep mode or the active mode.

The control module 170 may control the application according to the inactivation of the display 160 regardless of whether the control module 170 is in the sleep mode. In addition, the control module 170 may control the application for a certain period of time after the display 160 is activated.

The control module 170 includes an application list management module 171 and an application control module 173.

The application list management module 171 may generate and manage a list for applications corresponding to a predetermined condition among applications installed in the electronic device. The application list management module 171 may include an application installed in another electronic device in an application list in which some functions may be performed by the electronic device.

The application list management module 171 may generate an application list and may store the generated application list in the memory 120. For example, the application list management module 171 may store the application list in a nonvolatile memory (e.g., the second memory 123). Accordingly, although the electronic device 100 is restarted, the application list management module 171 may use the application list stored before the electronic device 100 is restarted without change.

The application list management module 171 may generate an application list according to at least one of an operation of an application, a usage record of the application, or a user request, and may store the generated application list in the memory 120.

The application list management module 171 may update the application list stored in the memory 120 according to at least one of an operation of the application, a usage record of the application, or a user request. For example, the application list management module 171 may add a new application to the application list or may delete some of the applications included in the application list. As another example, the application list management module 171 may change information about the applications registered in the application list (for example, information included in an application operation type item, a last run item, a notification detection item, or an application state item).

The application list management module 171 may add an application, which has executed a registration procedure to the push server 300, to the application list, or may change the state of a previously added application.

If a push service is required, the application may register information associated with the corresponding application or electronic device 100 in the push server 300. Although the application registered in the push server 300 is not executed or although the control module 170 is in the sleep mode, the application may receive data through the push server 300.

The application list management module 171 may add an application that sets a timer in the time management module 140 to perform a predetermined operation to the application list, or may change the state of a previously added application. For example, the application list management module 171 may add an application that sets a periodic timer (e.g., a timer that repeats at a predetermined time interval) in the time management module 140 to the application list. As another example, the application list management module 171 may add, to the application list, an application in which a timer is set during a predetermined time in the time management module 140 a predetermined number of times or more.

The application list management module 171 may verify a usage record of the application, may add an application determined not to be used at a predetermined level or higher (e.g., a predetermined number of times or more, or a predetermined time or more) during a predetermined time to the application list, or may change the state of a previously added application.

The application list management module 171 may add applications determined not to be used at a predetermined level or higher during a predetermined time (e.g., five days, one week, or one month) to the application list.

The application list management module 171 may determine that the application is not used at a predetermined level or higher in consideration of the state of the application. For example, the application list management module 171 may change the state of an application in a 'normal' state, which is determined not to be used at a predetermined level or higher during a predetermined time (e.g., three days), to a 'semi-frozen' state. Alternatively, the application list management module 171 may change the state of the application in the 'semi-frozen' state, which is determined not to be used at the predetermined level or higher during a predetermined time (e.g., two days), to the 'frozen' state.

The application list management module 171 may classify the operation of the application according to the operation form and may determine whether to use the application according to the classified operation. For example, the operation of the application may include a first operation performed when information corresponding to the operation of the application (or an operation state of the application) is displayed on the display 160 after the user runs the application, a second operation performed when the information corresponding to the operation of the application is not displayed on the display 160, and a third operation for providing information associated with the application to another application according to a request of the other application. If the operation is performed by an application, the application list management module 171 may determine whether the operation performed corresponds to any of the classified operations.

The application list management module 171 may accumulate points corresponding to each operation, and may determine that the application is used if the accumulated points reach a predetermined level. The application list management module 171 may set the prefabrication level in different ways according to the type of application.

The application list management module 171 may provide a different percentage (or a different weight value) for each operation, and may determine whether to use the application. For example, the application list management module 171 may provide 0.8 (or 80%) to the first operation, 0.1 (or 10%) to the second operation, and 0.1 (or 10%) to the third operation.

The application list management module 171 may set the weight value provided to each operation in different ways according to the type of application. For example, for a first application, the application list management module 171 may provide a weight value of 0.8 to the first operation, a weight value of 0.1 to the second operation, and a weight value of 0.1 to the third operation. For the second application, the application list management module 171 may provide a weight value of 0.9 to the first operation, a weight value of 0.1 to the second operation, and a weight value of 0 to the third operation. In other words, the application list management module 171 may disregard the third operation and may determine whether to use the second application.

Alternatively, for a third application, the application list management module 171 may provide a weight value of 1 to the first operation and a weight value of 0 to the second operation and the third operation. In other words, the application list management module 171 may determine whether to use the third application in consideration of only the first operation.

The application list management module 171 may determine whether the user authenticates the notification associated with the application. For example, the application list management module 171 may determine the likelihood that the user will verify the notification associated with the application, and may add an application having a predetermined value or less to the application list, or may change the state of a previously added application. The application list management module 171 may add applications having a probability of 20% or less (or 50% or less) to the application list. The application list management module 171 may change the state of the application having a probability of 50% or less from the 'normal' state to the 'semi-frozen' state. The application list management module 171 may change the state of the application having a probability of 20% or less from the 'semi-frozen' state to the 'frozen' state.

If a user response associated with the notification is not received during a predetermined time (e.g., five days), the application list management module 171 may add the corresponding application to the application list, or may change the state of the previously added application (e.g., may change the state from a 'normal' state to a 'frozen') state.

The application list management module 171 may delete applications, which are performed (or used) a predetermined number of times or more (e.g., seven times or more) during a predetermined time (e.g., one week) among the applications included in the application list, from the application list, or may change the state of a previously added application (e.g., may change the state from a 'frozen' state or a 'semi-frozen' state to a 'normal' state).

The application list management module 171 may delete, from the application list, applications whose likelihood that the user will authenticate the applications is a predetermined value or more (e.g., 50% or more) among the applications included in the application list, or may change the state of the previously added applications. For example, if the user responds to the notification for the applications included in the application list, the application list management module 171 may delete the corresponding applications from the application list.

The application list management module 171 may add a specific application to the application list, may delete a specific application from the application list, or may change the state of the applications included in the application list, according to a user request.

The application control module 173 may control the operation of the applications included in the application list.

For one or more applications included in the application list, the application control module 173 may limit (or disable or delay) at least some of the operations performed by the corresponding application if a predetermined event occurs (e.g., if entering a sleep mode).

The application control module 173 may restrict at least some of the operations performed by the application according to the state of the application included in the application list. For example, the application control module 173 may restrict operation of applications in a 'frozen' state. Alternatively, the application control module 173 may delay the operation cycle of the application in the 'semi-frozen' state, or may reduce the number of times the application operates.

If the control module 170 enters the sleep mode, the application control module 173 may restrict (or ignore) at least some operations associated with applications having the 'freeze' attribute. For example, if the state of the application that sets the timer is represented as the 'freeze' attribute, although the time setting in the timer is reached while the control module 170 is in the sleep mode, the application control module 173 may control the application not to perform the operation performed when the time setting in the timer is reached. For example, the application control module 173 may restrict operations associated with communication among operations associated with applications having a 'freeze' attribute. For example, the application control module 173 may wait without immediately performing an operation requested by an application having a 'semi-frozen' attribute, and may process the operations together every predetermined period (e.g., 30 minutes).

For applications registered in the application list, the application control module 173 may control at least some of the operations associated with the communication. The communication may include long range communications such as cellular communications and local area communications such as Wi-Fi communications or bluetooth communications. For example, the application control module 173 may restrict operations using the communication module when the control module 170 is in the sleep mode. For example, if the state of an application using a push service is represented as a 'freeze' attribute, the application control module 173 may allow an operation associated with the push service or an operation according to a user request, and may restrict other operations after the control module 170 enters a sleep mode.

For applications registered in the application list, the application control module 173 may control at least some of the operations associated with the sensors.

If there are other applications providing the same function as that of the application registered in the application list, the application control module 173 may restrict an operation associated with at least one of the other applications. If an application providing the same function as that of the application included in the application list is installed in the electronic device 100, the application control module 173 may restrict the same operation as that of the application included in the application list among the operations of the installed application.

The application control module 173 may restrict the operation of the applications included in the application list if a predetermined time elapses after the control module 170 enters the sleep mode (or after the display 160 is turned off). For example, the application control module 173 may limit operation of the application at the same time the control module 170 enters the sleep mode (or nearly the same time as the control module 170 enters the sleep mode).

Alternatively, the application control module 173 may restrict the operation of the applications included in the application list if a predetermined time (e.g., about ten minutes) elapses after the control module 170 enters the sleep mode.

If the control module 170 enters a sleep mode (or if the display 160 is off), the application control module 173 may monitor the operation of the application. For example, after the control module 170 enters the sleep mode (or after the display 160 is turned off), the application control module 173 may verify whether the operation is performed by any application.

The application control module 173 may restrict the operation of other applications among the applications included in the application list, in addition to the applications executed within a predetermined time after the electronic device 100 enters the sleep mode.

Although fig. 1 illustrates the application list management module 171 and the application control module 173 as being included in the control module 170 of the electronic device 100, the present disclosure is not limited thereto. For example, at least one of the application list management module 171 or the application control module 173 may be configured with a different module or processor from the control module 170 of the electronic device 100.

The electronic device 100 can connect and communicate with an external electronic device 200. The external electronic device 200 may be a wearable device.

If the electronic device 100 is connected with the external electronic device 200, the electronic device 100 may verify an application list (e.g., a second application list) of applications that may be run in the external electronic device 200. For example, the electronic device 100 may receive an application list (e.g., a second application list) installed in the external electronic device 200 from the external electronic device 200.

The application control module 173 may compare an application list (e.g., a first application list) of the electronic device 100 and an application list (e.g., a second application) of the external electronic device 200 to identify the same application therein. The application control module 173 may restrict an operation of one of an application installed in the electronic device 100 and an application installed in the external electronic device 200 if the same application is located in the first application list and the second application list. For example, if the operation of an application installed in the external electronic device 200 is limited, the application control module 173 may control the communication module 110 to transmit a command for limiting the operation of a specific application to the external electronic device 200. Therefore, another one of the applications installed in the electronic device 100 and the same application installed in the external electronic device 200 can operate normally.

The application control module 173 may compare the first application list of the electronic device 100 and the second application list of the external electronic device 200 to determine whether there is another application providing the same function (or similar function). For example, if applications providing the same function are included in at least one of the first application list or the second application list, one of the electronic device 100 and the external electronic device 200 may restrict at least some of operations associated with the corresponding applications.

The application control module 173 may select the electronic device to limit the operation of the application according to the remaining capacity of the battery 150 of the electronic device 100 and the remaining capacity of the battery of the external electronic device 200. For example, the application control module 173 may limit the operation of an application installed in an electronic device in which the remaining capacity of a battery between the electronic device 100 and the external electronic device 200 is low. The application control module 173 may receive the remaining power of the battery of the external electronic device 200 from the external electronic device 200 through the communication module 110.

If at least one of the electronic device 100 or the external electronic device 200 is connected to a power supply device (e.g., a wired charger or a wireless charger), at least some of the restricted operations may be allowed.

When the electronic device 100 is connected with the external electronic device 200, the application control module 173 may restrict the operation of one of an application installed in the electronic device 100 and the same application installed in the external electronic device 200.

If the electronic apparatus 100 is connected with the external electronic apparatus 200, the application control module 173 may restrict the operation of one of the application installed in the electronic apparatus 100 and the application installed in the external electronic apparatus 200 regardless of whether an event for restricting the operation of the applications included in the first application list occurs. If the electronic device 100 is disconnected from the external electronic device 200, the application control module 173 may restrict the operation of the applications included in the first application list according to whether an event for restricting the operation of the applications included in the first application list occurs.

Fig. 2A and 2B illustrate examples of restricting application operations according to embodiments of the present disclosure.

The x-axis of each of the graphs shown in fig. 2A and 2B represents time and the y-axis represents the amount of current consumed by an electronic device (e.g., electronic device 100 in fig. 1).

Fig. 2A and 2B illustrate the amount of current consumed when the power supply (or screen) of a display (e.g., display 160 in fig. 1) is turned on (or in an active state), and the amount of current consumed when the power supply (or screen) of a display is turned off (or in an inactive state).

The display may be inactive (e.g., the screen of the display may be turned off) if the electronic device enters an inactive state or the control module (e.g., control module 170 in fig. 1) enters a sleep mode.

For example, if a predetermined time elapses before or after the control module enters the sleep mode, the control module may deactivate the display (e.g., may turn off the power or screen of the display).

The control module may enter a sleep mode, may periodically or intermittently transition to an awake mode, may perform predetermined operations, and may return to the sleep mode. In this case, the display may remain inactive.

After the application control module is awakened by a request of the application and the power of the display is turned off, if the application performs an operation, the amount of current consumed by the application may temporarily increase. For example, after the control module enters the sleep mode, the application control module may verify whether the operation is performed by any application during a predetermined time.

Referring to fig. 2A, after the power of the display is turned off (or after the control module enters the sleep mode), operations associated with application a and application B are performed during ten-minute intervals. Thus, the application list management module may, for example, designate the states of applications a and B as a 'normal' state, and may designate the state of application C as a 'frozen' state. The application control module may restrict operation of application C among applications A, B and C included in the application list during the sleep mode. If a request for operation associated with applications A and B having the 'normal' attribute is received, the application control module may change from the sleep mode to the awake mode, may perform the operation associated with applications A and B, and may return to the sleep mode thereafter.

Referring to fig. 2B, after the power of the display is turned off (or after the control module enters the sleep mode), no operation is performed by the application during a ten-minute interval. Thus, the application list management module may, for example, designate the state of applications a-C as a 'frozen' state. The application control module may restrict operation of the applications a to C included in the application list during the sleep mode.

If the electronic device enters the predetermined location (or if a predetermined time elapses after the electronic device enters the predetermined location), the application control module may restrict operation of at least some of the applications included in the application list (e.g., applications having a 'freeze' or 'semi-freeze' attribute). If there is an application set to restrict operations in a corresponding place among applications included in the application list, the application control module may restrict at least some operations associated with the corresponding application during, for example, a sleep mode. The application control module may determine the location of the electronic device using GPS information received through a GPS module, a base station, a Wi-Fi positioning system (WPS), beacon signals, and the like.

The application control module may restrict at least some of the operations of the applications included in the application list if the electronic device is connected with a predetermined external device (or if a predetermined time elapses after the electronic device is connected with the predetermined external device). For example, the application control module may limit operation when the control module is in a sleep mode. For example, if the electronic device is connected to an access point located in a particular space (e.g., a home or office), the application control module may restrict at least some operations associated with a predetermined application.

The application control module may allow an operation of the application included in the application list if the electronic device is disconnected from a predetermined external device.

The application control module may also restrict operation of at least some of the applications included in the application list. For example, the application control module may limit operation when the control module is in a sleep mode. For example, the application control module may restrict at least some operations associated with a predetermined application in a time zone (e.g., from 11p.m. to 8 a.m.) set by a user.

The application control module may limit operation of at least some of the applications included in the application list according to a remaining capacity of the battery. For example, the application control module may receive information about the remaining amount of battery power from the power management module. The application control module may restrict operation of at least some of the applications included in the application list if the remaining amount of the battery is a predetermined amount or less. For example, if the remaining charge of the battery is 20% or less (or 50% or less), the application control module may limit at least some operations associated with the predetermined application.

The application control module may verify the expected battery duration. Thus, the application control module may restrict at least some operations associated with the predetermined application. The expected battery duration may be a value estimated using the amount of current consumed by the electronic device or the current amount of current of the battery within a predetermined time range.

The application control module may prohibit the limitation of the operation of at least some of the applications included in the application list when the electronic device is connected to a power supply device (e.g., a wired charger or a wireless charger).

The application control module may restrict operation of at least some of the applications included in the application list according to network usage. For example, the application control module may restrict operation of at least some of the applications included in the application list if cellular data usage is a predetermined criterion or higher. For example, if cellular data usage exceeds a predetermined level, the application control module may restrict operations associated with the communication among operations associated with applications having a 'freeze' attribute.

The application control module may restrict operation of at least some of the applications included in the application list if a user request for restricting operation of a specific application is input. For example, the application control module may restrict another application associated with operation of the corresponding application or another function of the electronic device.

The application control module may end an application in a 'frozen' state among running applications. The application control module may end the application in the 'frozen' state if the display is turned off or if the electronic device is operating in a low power mode. After a predetermined time (e.g., ten minutes) has elapsed, the application control module may end the application in the 'frozen' state after the display is turned off or the electronic device begins operating in the low power mode. The application control module may delete data associated with an application running a 'frozen' state, for example, from the first memory 121 in fig. 1, and may end the corresponding application.

Fig. 3A and 3B illustrate a user interface according to an embodiment of the present disclosure.

Referring to fig. 3A and 3B, the display 360 displays a user interface for limiting the operation of applications included in the application list or releasing the operation limitation of the applications.

The user interface may arrange and display the applications included in the application list according to a predetermined condition (e.g., a name of each of the applications, a recent usage time of each of the applications, a value of a user authentication notification, a state of each of the applications, or a battery power consumed by each of the applications). The user interface may include an object 10 for selecting each application.

In fig. 3A, the user interface shows an application (App 2) whose operation is restricted in a manner different from the manner in which the operations of the other applications (App 1, App 3, App 4, and App 5) are restricted (e.g., an application in a 'frozen' state). For example, the object of the application whose operation is restricted may display text different from the text of the object of the application whose operation is not restricted, and may display a shape, color, contrast, or the like different from the shape, color, contrast, or the like of the application whose operation is not restricted.

Using the object 10 included in the user interface, the user can restrict the operation of a specific application included in the application list and can release the operation restriction. For example, in fig. 3A, when the user selects the object 10 of App 1, the state of App 1 is changed to the "frozen" state as shown in fig. 3B, and the operation of the first application App 1 may be restricted. Furthermore, the text of the object 10 of the first application App 1 may change from the "normal" state to the "frozen" state, and the color and contrast of the object may be changed.

Fig. 4A and 4B illustrate a user interface according to an embodiment of the present disclosure.

Referring to fig. 4A and 4B, the control module displays a user interface including applications included in the application list on the display 460. The user interface provides a list of applications whose operations are restricted and a list of applications that are allowed to operate through different menus.

Referring to fig. 4A, the display 460 displays a list of applications whose operation is restricted. For example, if the user selects the 'freeze' tab, the display 460 displays a list of applications whose operation is restricted.

The display 460 displays, in separate areas, a list of applications (App 1 to App 11) whose operations are restricted according to predetermined conditions and a list of applications (App 12 to App 14) whose operations are restricted according to a user request (or user setting).

According to an event for releasing the operation restriction or a user request, the application whose operation is restricted may be moved to a list of applications whose operation is permitted or a list of applications whose operation is not set to be restricted/permitted. For example, if the user runs an application registered in the list of applications whose operation is restricted according to a predetermined condition, the application is moved from the list of applications whose operation is restricted to the list of applications whose operation is allowed or the list of applications whose operation is not set to be restricted/allowed.

Applications whose operation is restricted according to the user request may be moved to a list of applications that are allowed to operate according to the user request.

The user may select at least some of the applications whose operations are restricted according to a predetermined condition, and may set the selected applications to restrict their operations according to a user request. For example, if an application whose operation is restricted according to a predetermined condition is set as a restricted operation by the user, the application may move to a list of applications whose operation is restricted according to the user request.

Referring to fig. 4B, the display 460 displays a list of applications (App 15 to App 23) that are allowed to operate. For example, if the user selects the 'normal' tab, the display 460 displays a list of applications whose operation is not restricted.

The user may select at least some of the applications that are allowed to operate and may set the selected applications to restrict their operation. For example, on the user interface shown in fig. 4A, applications set by the user to restrict their operation may be moved to a list of applications whose operation is restricted according to the user setting.

Fig. 5A and 5B illustrate a user interface according to an embodiment of the present disclosure.

Referring to fig. 5A, the control module displays a user interface including applications included in the application list on the display 560. The user interface displays a list of applications whose operations are restricted and a list of applications whose operations are allowed on different areas.

The display 560 displays a list of applications whose operation is restricted according to a user request (e.g., 'always save energy'), a list of applications whose operation is restricted according to a predetermined condition (e.g., 'auto save energy'), and a list of applications whose operation is allowed (e.g., 'power save off').

If the user selects one of the applications included in the application list as shown in fig. 5A, the display 460 displays a user interface for changing the application list including the selected application as shown in fig. 5B. For example, the user interface is provided in the form of a pop-up window 15 and includes an object 17 for selecting a battery optimization option that places an application in one of a list of applications whose operation is restricted by a user (e.g., 'always'), a list of applications whose operation is restricted according to a predetermined condition (e.g., 'auto'), and a list of applications whose operation is allowed (e.g., 'close'). For example, the user may select one of the objects 17 and may change the list of applications that include the application.

Fig. 6A and 6B illustrate user interfaces according to various embodiments of the present disclosure.

Referring to fig. 6A and 6B, the user interface displayed on the display 660 includes application icons.

If the operation of the application is restricted, the application control module may control the display 660 to change and display the application icon displayed on the display 660.

For example, if the operation of the application is restricted, the application control module may control the display 660 to change the base icon of the application, e.g., display the color or contrast of the base icon of the application, synthesize and display the base icon as another image, or replace and display the base icon as another image. Alternatively, if the operation of the application is restricted, the application control module may change the display position of the application icon.

Referring to fig. 6A, among a plurality of applications, when the operation of the application is not limited, a basic icon 20 is provided.

Referring to fig. 6B, the display 660 changes the basic icon 20 of the application to the icon 25 surrounded by ice to represent that the operation of the application is restricted. For example, at least one of the shape, color, transparency, size, and/or location of the icon may be changed.

Fig. 7A and 7B illustrate a user interface according to an embodiment of the present disclosure.

Referring to fig. 7A and 7B, the application control module may notify the user of information indicating that the operation of the application is restricted or allowed before/after the operation of the application is restricted or the operation restriction is released. For example, the application control module may apply an ON/OFF effect (or a blinking effect) to an application icon displayed ON the display 760 during a specific time. Alternatively, the application control module may control the display 760 to display an object (e.g., a text object) for providing a notification that the operation restriction state of the application is changed.

Referring to fig. 7A, the display 760 displays an object 27 indicating that the operation restriction state of the application is changed.

Referring to fig. 7B, if the user selects the object 27, the display 760 displays a list of applications for controlling the operation restriction state to be changed (e.g., 'recent power saving') and an interface for controlling the operation states of the applications included in the list.

If the sleep mode is changed to the awake mode by a user or an application having the 'normal' attribute, the application control module may provide a notification (e.g., a visual output, an audible output, or a tactile output) associated with an operation requested by the application having the 'freeze' attribute.

FIG. 8 illustrates a user interface according to an embodiment of the present disclosure.

Referring to fig. 8, the display 860 displays information 30 through a user interface providing notification information, wherein the information 30 is related to an application whose operation is restricted. For example, the display 860 displays the name of an application whose operation is restricted and information on battery power consumed by the application.

A user interface (e.g., a status bar or a quick-select menu) providing notification information may be displayed on display 860 and may be hidden by touch gestures or voice instructions.

The application control module 173 may allow the application to operate if an event associated with the application whose operation is restricted occurs. According to an embodiment of the present disclosure, the event associated with the application whose operation is restricted may include an event generated by an external electronic device (e.g., an application server or an external electronic device). For example, the event associated with the application whose operation is restricted may be an event for receiving information (such as instant messages, emails, advertisements, news, and weather) from an external device.

If an event associated with an application in which the operation of the application is restricted in a state in which the operation of the application is restricted occurs, a notification of the occurrence of the event may not be provided to the user. According to an embodiment of the present disclosure, if an event associated with an application whose operation is restricted occurs, the application control module 173 may temporarily allow the operation of the application where the event occurs and may perform the operation associated with the event. For example, the application control module 173 may run an application in which an event occurs and may provide information about a message, an e-mail, an advertisement, news, etc., received from an external device in the form of a notification. If the operation associated with the event is completed, the application control module 173 may again restrict the operation of the application in which the event occurred.

Fig. 9 is a flowchart illustrating an application control method of an electronic device according to an embodiment of the present disclosure. For example, the method shown in fig. 9 may be performed by the electronic device 100 shown in fig. 1.

Optionally, at least some of the operations according to various embodiments of the present disclosure may be performed in an external electronic device (e.g., a server).

In addition, data associated with at least some of the operations according to various embodiments of the present disclosure may be stored in a server.

Referring to fig. 9, in step 910, the electronic device updates an application list.

For example, the electronic apparatus may generate an application list according to at least one of an operation of an application, a use history of the application, and a user setting, and may store the generated application list in the memory. Thereafter, the electronic device may update the application list stored in the memory according to at least one of an operation of the application, a usage record of the application, or a user request. For example, the electronic device may register and add new applications in the application list, or may delete some of the applications included in the application list. The electronic device may add the application, which has executed the registration program to the push server, to the application list.

The electronic device may verify the application usage record of the user and may add applications that are not used at the predetermined level or higher for a predetermined time period to the application list.

The electronic device can determine a likelihood that the user will verify a notification associated with the application and can add the application to the list of applications with a predetermined value or less.

The electronic device may delete applications that are run (or used) a predetermined number of times or more (e.g., seven times or more) during a predetermined time (e.g., one week) among the applications included in the application list.

The electronic device may delete an application having a probability of a predetermined value or more (e.g., 50% or more) from among the applications included in the application list.

The electronic device may add a specific application to the application list or may delete a specific application from the application list according to a user request.

In step 920, the electronic device determines whether a predetermined event has occurred.

For example, the electronic device may determine whether the control module enters a sleep mode, whether the display is turned off, whether the electronic device enters a predetermined place, or whether the electronic device is connected with a predetermined external electronic device.

For example, the electronic device may determine whether the current time corresponds to a time set by a user, may determine whether a remaining capacity of the battery is a predetermined value or less, or may determine whether a user request for limiting the operation of the application is input.

In step 920, if a predetermined event occurs, the electronic device restricts the operation of the applications included in the application list in step 930.

For example, if a predetermined time elapses after a predetermined event occurs, the electronic apparatus may restrict the operation of the applications included in the application list.

The electronic apparatus may restrict the operation of other applications included in the applications list, in addition to the application that performs the operation within a predetermined time after the electronic apparatus enters the sleep mode.

The electronic device may display an icon (or list) of applications that may be run by the electronic device on the display.

If the operation of the application is restricted, the electronic device may change and display the application icon displayed on the display.

Before/after the operation of the application is restricted or the operation restriction is released, the electronic apparatus may notify the user that the function restricting the operation of the application is changed. For example, the electronic device may control an application icon displayed ON the display to apply an ON/OFF (or blinking) effect for a specific time.

Fig. 10 is a flowchart illustrating an application control method of an electronic device according to an embodiment of the present disclosure. In particular, fig. 10 illustrates operations of a method performed after operations of an application are restricted (e.g., as described above with reference to fig. 9).

Referring to fig. 10, after the operation of the application is limited, the electronic device determines whether an event associated with the application whose operation is limited occurs in step 1010. For example, an event associated with an application whose operation is restricted may refer to an event generated by an external device (e.g., an application server or an external electronic device), rather than an event generated by an application installed in the electronic device. For example, the event associated with the application whose operation is restricted may also be an event in which the electronic device receives information (instant message, e-mail, advertisement, news, and weather) from an external device (e.g., the push server 300 in fig. 1).

In step 1020, the electronic device allows operation of the application in which the event occurred. For example, the electronic device may run an application where an event occurs.

In step 1030, the electronic device performs an operation associated with the event. For example, the electronic device may provide information about messages, emails, advertisements, news, and the like received from the external device in the form of a notification.

If the operation associated with the event is complete, the electronic device again restricts the operation of the application in which the event occurred in step 1040.

In addition, the application control method of the electronic device may include updating a first application list including at least one application installed in the electronic device according to at least one of an operation of the application, a usage history of the application, or a user request, and restricting an operation of at least one of the at least one application included in the first application list if a predetermined event occurs.

The updating of the first application list may include registering in the first application list at least one of the following applications: an application that provides a push service, an application that is set to perform a predetermined operation at least once during a predetermined time period, an application that is not used during a predetermined time, an application that has a predetermined likelihood or less of a user response to a notification associated with an application, or an application that has no user response to a notification associated with an application during a predetermined time.

The operations of the application may include a first operation performed when information corresponding to the operations of the application is displayed on the display, a second operation performed when the information corresponding to the operations of the application is not displayed on the display, and a third operation for providing information associated with the application to another application according to a request of the other application.

The updating of the first application list may include determining whether to use the application according to at least one of the first operation, the second operation, or the third operation.

Determining whether to use the application may include providing different weight values for the first operation, the second operation, and the third operation, and determining whether to use the application.

The limiting of the operation of the at least one application may include setting each of the applications included in the first application list to one of the following states: a first state to allow operation of the application according to a usage history of the application, a second state to reduce a number of times the application is operated, and a third state to restrict at least some of the operation of the application and to restrict operation of at least one application according to the state of the application.

Restricting operation of the at least one application may include changing a state setting in the application according to a user input and restricting operation of the at least one application according to the changed state of the application.

Limiting operation of the at least one application may include limiting operation of the at least one application based on at least one of whether the display is inactive, a current time, a current location of the electronic device, a remaining charge (or rate of battery drain) of a battery of the electronic device, or cellular data usage.

The application control method may further include receiving a second application list including at least one application installed in the external electronic device from the external electronic device, determining whether there are applications performing the same function by comparing the first application list and the second application list, and restricting an operation of the applications performing the same function in one of the electronic device and the external electronic device.

Fig. 11 illustrates an operation restriction effect of an application according to an embodiment of the present disclosure.

Referring to fig. 11, a first graph 40 and a second graph 50 show results of measuring an amount of data packets communicated from an electronic device (e.g., the electronic device 100 of fig. 1). The first graph 40 represents the amount of packets communicated as a function of time when the operation of the application is not limited, and the second graph 50 represents the amount of packets communicated as a function of time when the operation of the application is limited. The x-axis of each of the first graph 40 and the second graph 50 represents time, and the y-axis represents the amount of packets (in bytes). The y-axis may also correspond to the amount of current consumed.

Referring to the first and

second graphs

40 and 50, if an operation is performed according to a request of an application while the control module is in the sleep mode, a packet may be communicated. Comparing the first graph 40 and the second graph 50, the number of packets communicated in the second graph 50 (if the operation of the application is limited) is reduced more than in the first graph 40 (if the operation of the application is not limited).

In fig. 11, table 60 shows the results of current consumption for six hours when the display is turned off (or when the control mode is in the sleep mode) measured using a Galaxy Note 3(SM-N9005) device manufactured by Samsung Electronics co. The average currents are compared and if the operation of the application is not limited (no freezer applied (AppFreezer)), the average current is 26.833mA, if the operation of the application is limited (with AppFreezer), the average current is 16.454 mA. Therefore, 10.379mA of current per hour can be saved, and an effect of reducing current consumption of about 38.67% can be obtained.

According to an embodiment of the present disclosure, the electronic device may reduce current consumed by the application by limiting unnecessary or selective operations of the application when the display is turned off or when the control module enters the sleep mode. Accordingly, the usable time of the electronic device may be increased. The operational limits may be maintained regardless of whether the display is turned off or the control module enters a sleep mode before a predetermined release event occurs or before a user release request is input.

Fig. 12 illustrates an electronic device according to an embodiment of the present disclosure.

Referring to fig. 12, the electronic device 1201 includes an Application Processor (AP)1210, a communication module 1220, a Subscriber Identity Module (SIM) card 1224, a memory 1230, a sensor module 1240, an input device 1250, a display module 1260, an interface 1270, an audio module 1280, a camera module 1291, a power management module 1295, a battery 1296, an indicator 1297, and a motor 1298.

The application processor 1210 may drive, for example, an OS or an application program to control a plurality of hardware or software components connected to the application processor 1210, and may process and calculate various data. The application processor 1210 may be implemented in, for example, a SoC. The application processor 1210 may also include a GPU and/or an image signal processor. Application processor 1210 may include at least some of the components shown in fig. 12 (e.g., cellular module 1221). The application processor 1210 may load instructions or data received from at least one of the other components (e.g., the nonvolatile memory) into the volatile memory to process the data, and may store various data in the nonvolatile memory.

The communication module 1220 may have the same or similar configuration as the communication module 110 in fig. 1.

The communication module 1220 includes a cellular module 1221, a Wi-Fi module 1223, a Bluetooth (BT) module 1225, a GNSS module 1227 (e.g., a GPS module, a Glonass module, a Beidou module, or a Galileo module), an NFC module 1228, and an RF module 1229.

The cellular module 1221 may provide a voice call service, a video call service, a text message service, an internet service, etc. through a communication network. Cellular module 1221 may identify and authenticate electronic device 1201 in the communication network using SIM card 1224. Cellular module 1221 may perform at least a portion of the functionality that may be provided by application processor 1210. Cellular module 1221 may include a Communications Processor (CP).

The Wi-Fi module 1223, the BT module 1225, the GNSS module 1227, and/or the NFC module 1228 may include a processor for processing data transmitted and received through the corresponding modules. At least some (e.g., two or more) of the cellular module 1221, the Wi-Fi module 1223, the BT module 1225, the GNSS module 1227, and the NFC module 1228 may be included in one Integrated Chip (IC) or one IC package.

The RF module 1229 may transmit and receive communication signals (e.g., RF signals). The RF module 1229 may include a transceiver, a Power Amplifier Module (PAM), a frequency filter, a Low Noise Amplifier (LNA), an antenna, and the like. At least one of the cellular module 1221, the Wi-Fi module 1223, the BT module 1225, the GNSS module 1227, and the NFC module 1228 may transmit and receive RF signals through a separate RF module.

The SIM card 1224 may include a card including a SIM and/or an embedded SIM. The SIM card 1224 may include unique identification information, such as an Integrated Circuit Card Identifier (ICCID), or subscriber information, such as an International Mobile Subscriber Identity (IMSI).

Memory 1230 includes internal memory 1232 and external memory 1234. The internal memory 1232 may include at least one of volatile memory (e.g., Dynamic Random Access Memory (DRAM), static ram (sram), synchronous dynamic ram (sdram), etc.), non-volatile memory (e.g., one-time programmable read only memory (OTPROM), programmable ROM (prom), erasable and programmable ROM (eprom), electrically erasable and programmable ROM (eeprom), mask ROM, flash memory (e.g., NAND flash memory or NOR flash memory, etc.), a hard disk drive, and a Solid State Drive (SSD)).

External memory 1234 may also include a flash drive, Compact Flash (CF), Secure Digital (SD), micro SD, mini SD, extreme digital (xD), memory stick, and so forth. The external memory 1234 may be functionally and/or physically connected to the electronic device 1201 via a variety of interfaces.

The sensor module 1240 may measure a physical quantity or may detect an operation state of the electronic device 1201 and convert the measured or detected information into an electrical signal. The sensor modules 1240 include a gesture sensor 1240A, a gyroscope sensor 1240B, a pressure sensor 1240C, a magnetic sensor 1240D, an acceleration sensor 1240E, a grip sensor 1240F, a proximity sensor 1240G, a color sensor 1240H (e.g., a red, green, blue (RGB) sensor), a biological sensor 1240I, a temperature/humidity sensor 1240J, an illuminance sensor 1240K, and an Ultraviolet (UV) sensor 1240M.

Additionally or alternatively, the sensor module 1240 may also include electronic nose sensors, Electromyography (EMG) sensors, electroencephalography (EEG) sensors, Electrocardiogram (ECG) sensors, Infrared (IR) sensors, iris sensors, fingerprint sensors, and the like. The sensor module 1240 may also include sensor control circuitry for controlling one or more sensors included therein.

The electronic device 1201 may also include a processor configured to control the sensor module 1240 as part of the application processor 1210 or separate from the application processor 1210. For example, the electronic device 1201 may control the sensor module 1240 when the application processor 1210 is in a sleep state.

The input device 1250 includes a touch panel 1252, a (digital) pen sensor 1254, a key 1256, and an ultrasonic input unit 1258. The touch panel 1252 may recognize a touch input using at least one of a capacitance detection method, a resistance detection method, an infrared detection method, and an ultrasonic detection method. The touch panel 1252 may also include control circuitry. The touchpad 1252 may also include a tactile layer and may provide tactile feedback to a user.

The (digital) pen sensor 1254 may be part of the touchpad or may include a separate sheet for identification.

Keys 1256 may include physical buttons, optical keys, or a keypad.

The ultrasonic input unit 1258 may detect an ultrasonic signal generated by an input tool (e.g., via the microphone 1288) and may verify data corresponding to the detected ultrasonic signal.

The display 1260 includes a panel 1262, a hologram device 1264, and a projector 1266. The panel 1262 may comprise the same or similar configuration as the configuration of the display 160 shown in fig. 1. The panel 1262 may be flexible, transparent, or wearable.

The panel 1262 and touchpad 1252 may be integrated into one module.

The hologram device 1264 may display a stereoscopic image in space using interference of light.

The projector 1266 may project light onto a screen to display an image. The screen may be provided inside or outside the electronic device 1201.

The display 1260 may also include control circuitry for a control panel 1262, a hologram device 1264, and/or a projector 1266.

The interfaces 1270 include a high-definition multimedia interface (HDMI)1272, a Universal Serial Bus (USB)1274, an optical interface 1276, and a D subminiature 1278. Additionally or alternatively, interface 1270 may include a mobile high definition link (MHL) interface, an SD/multimedia card (MMC) interface, and/or an infrared data communication (IrDA) standard interface.

The audio module 1280 may convert sound and electrical signals in both directions. The audio module 1280 may process sound information input or output through, for example, a speaker 1282, a receiver 1284, an earphone 1286, a microphone 1288, and the like.

Camera module 1291 acquires still and moving images. Camera module 1291 may include one or more image sensors (e.g., front or rear sensors), lenses, an Image Signal Processor (ISP), and/or a flash (e.g., a Light Emitting Diode (LED) or xenon lamp).

Power management module 1295 may manage power for electronic device 1201. For example, the power management module 1295 may include a Power Management Integrated Circuit (PMIC), a charger IC, and/or a battery gauge. The PMIC may have a wired charging method and/or a wireless charging method. The wireless charging method may include a magnetic resonance method, a magnetic induction method, an electromagnetic method, and the like.

Additional circuitry for wireless charging may also be provided, such as coil loops, resonant circuits, rectifiers, and the like.

A battery gauge may measure the remaining charge of battery 1296 and the voltage, current, or temperature of battery 1296 when battery 1296 is charged.

Battery 1296 may comprise a rechargeable battery or a solar cell.

Indicator 1297 may display a particular state (e.g., activated state, message state, charged state, etc.) of electronic device 1201 or a portion of electronic device 1201 (e.g., application processor 1210).

The motor 1298 may convert the electrical signals to mechanical vibrations and may generate vibrations, haptic effects, or the like.

The electronic device 1201 may include a processing unit (e.g., GPU) for supporting mobile TV. The processing unit for supporting mobile TV may process media data according to different standards, such as a Digital Multimedia Broadcasting (DMB) standard, a Digital Video Broadcasting (DVB) standard, a media streaming standard, etc.

Each of the above-described elements of the electronic device 1201 may be configured with one or more components, and the name of the corresponding element may vary according to the type of the electronic device. Alternatively, electronic device 1201 may include at least one of the elements described above, some elements may be omitted from electronic device 1201, or other accessory elements may also be included in electronic device 1201. In addition, some of the elements of the electronic device 1201 may be combined with each other to form one entity, thereby making it possible to perform functions of the corresponding elements in the same manner as before the combination.

FIG. 13 shows program modules according to embodiments of the disclosure.

Referring to fig. 13, program modules 1310 may include an OS for controlling resources associated with an electronic device (e.g., electronic device 100 of fig. 1) and/or various applications running on the OS. Examples of the OS include

And the like.

Program modules 1310 include a kernel 1320, middleware 1330, APIs 1360, and applications 1370. At least a portion of the program modules 1310 may be preloaded in the electronic device or downloaded from an external electronic device.

The kernel 1320 includes a system resource manager 1321 and a device driver 1323.

The system resource manager 1321 may control, allocate, collect, etc., system resources. The system resource manager 1321 may include a process management unit, a memory management unit, a file system management unit, and the like.

The device drivers 1323 may include a display driver, a camera driver, a BT driver, a shared memory driver, a USB driver, a keypad driver, a Wi-Fi driver, an audio driver, an inter-process communication (IPC) driver.

The middleware 1330 may provide a function commonly used by the application 1370 and may provide various functions to the application 1370 through the API 1360 so that the application 1370 efficiently uses limited system resources in the electronic device. The middleware 1330 includes a runtime library 1335, an application manager 1341, a window manager 1342, a multimedia manager 1343, a resource manager 1344, a power manager 1345, a database manager 1346, a package manager 1347, a connectivity manager 1348, a notification manager 1349, a location manager 1350, a graphics manager 1351, a security manager 1352, an alarm manager 1353, a usage status (usages stats) manager 1354, and an LpNet manager 1355.

The runtime libraries 1335 may include library modules for use by a compiler to add new functionality through the programming language when the application 1370 is run. Runtime library 1335 may perform functions related to input and output management, storage management, and/or algorithmic functions.

The application manager 1341 may manage a lifecycle of at least one of the applications 1370.

The window manager 1342 may manage Graphical User Interface (GUI) resources used on a screen of the electronic device.

The multimedia manager 1343 may determine formats for reproducing a variety of media files and may encode or decode the media files using codecs corresponding to the corresponding formats.

The resource manager 1344 may manage source code for at least one of the applications 1370 and may manage resources for memory, storage space, and the like.

The power manager 1345 may operate with a basic input/output system (BIOS), may manage a battery or power supply, and may provide power information for operation of the electronic device.

The database manager 1346 may generate, search, or alter a database for use in at least one of the applications 1370.

The package manager 1347 may manage installation or update of applications distributed in the form of package files.

The connectivity manager 1348 may manage wireless connections, e.g., Wi-Fi connections, BT connections, etc.

The notification manager 1349 may display or notify events (e.g., message arrivals, appointments, and proximity notifications) by a method that does not disturb the user.

The location manager 1350 may manage location information of the electronic device.

The graphic manager 1351 may manage graphic effects to be provided to a user or a User Interface (UI) related to the graphic effects.

The security manager 1352 may provide security functions for system security, user authentication, and the like.

The alarm clock manager 1353 may provide an alarm clock function at a predetermined time.

The application 1370 may perform a desired function at a predetermined time or periodically using the alarm clock manager 1353.

The usages managers 1354 may manage information about when and how many times a user uses an application. For example, the usages managers 1354 may manage information for each of the available applications 1370, such as user accounts, run times, end times, operating times, available memory, available hardware, current consumption, and usage by the user (e.g., the likelihood that the user will verify a notification).

The LpNet manager 1355 can collect and analyze information about other managers including the application manager 1341, the package manager 1347, the location manager 1350, the alarm manager 1353, and the usages managers 1354, and can control applications. The results of the control application may be provided to the user. The usages managers 1354 may receive the user request through the smart manager 1385 and may send the received user request to the LpNet manager 1355. The LpNet manager 1355 may perform an operation corresponding to the user request. For example, the LpNet manager 1355 may obtain application run information from the application manager 1341, may obtain information for installed applications from the package manager 1347, and may obtain location information records from the location manager 1350. The LpNet manager 1355 can obtain information about the number of wakeups from the alarm manager 1353 and can obtain information about when and how many times the user used the application from the usages stats manager 1354. For example, the LpNet manager 1355 may determine an unused application from information collected from another manager (or other managers) and may restrict the operation of the application. Alternatively, an application executed by the user among the applications whose operations are restricted may release the operation restriction. For example, as shown in fig. 4B, the LpNet manager 1355 may notify a user of an application whose operation is restricted through the notification manager 1349. For example, LpNet manager 1355 may request application manager 1341 to prohibit application execution. Optionally, the application manager 1341 may prohibit the application restricted by the LpNet manager 1355 from running. For example, the LpNet manager 1355 may manage a list of applications whose operations are restricted according to information collected from another manager (or other manager), a list of applications whose operations are restricted by a user request received through the smart manager 1385, and other application lists. At least one of the application lists can be provided to the user through intelligent management 1385. The user may control the list of applications provided to the user through the interface of the intelligent manager 1385. The control signal may be sent to the LpNet manager 1355 to be processed.

When the electronic device has a phone function, the middleware 1330 can also include a phone manager for managing a voice communication function or a video communication function of the electronic device.

Middleware 1330 can include a middleware module that configures a combination of the various functions of the components described above. Middleware 1330 may provide a module specifically designed according to the OS type to provide different functions. In addition, middleware 1330 can dynamically delete some old components or can add new components.

The API 1360 may include a set of API programming functions and may be provided to different components depending on the type of OS. For example, for

Or

An API set may be provided according to a platform. In addition, for

Two or more API sets may be provided according to a platform.

The applications 1370 include a home application 1371, a dialer application 1372, a short message service/multimedia message service (SMS/MMS) application 1373, an Instant Messaging (IM) application 1374, a browser application 1375, a camera application 1376, an alarm application 1377, an address book application 1378, a voice dialing application 1379, an email application 1380, a calendar application 1381, a media player application 1382, an album application 1383, a clock application 1384, and an intelligent manager 1385. In addition, the applications 1370 may include healthcare applications (e.g., applications for measuring exercise amount or blood glucose, etc.), or environmental information applications (e.g., applications for providing barometric pressure information, humidity information, temperature information, etc.).

The applications 1370 may also include an information exchange application for exchanging information between an electronic device (e.g., the electronic device 100 in fig. 1) and an external electronic device (e.g., the electronic device 200 in fig. 1). The information exchange application may include a notification relay application for transmitting specific information to the external electronic device, or a device management application for managing the external electronic device.

For example, the notification relay application may include functionality to send notification information generated by other applications of the electronic device (e.g., the SMS/MMS application 1343, the email application 1380, a healthcare application, an environmental information application, etc.) to the external electronic device. Further, the notification relay application may receive notification information from an external electronic device and may provide the received notification information to a user of the electronic device.

The device management application may manage (e.g., install, delete, or update) at least one of functions of the external electronic device communicating with the electronic device (e.g., a function of turning on/off the external electronic device itself (or a part of components) or a function of adjusting display brightness (or resolution)), an application operating in the external electronic device, or a service (e.g., a telephone service or a message service) provided from the external electronic device.

The applications 1370 may include applications preset according to attributes of the electronic device (e.g., a health card application of an ambulatory medical device).

The application 1370 may include an application received from an external electronic device (e.g., the external electronic device 200 or the push server device 300 in fig. 1).

The applications 1370 may include preloaded applications or third party applications that may be downloaded from a server.

Names of components of the program module 1310 may differ according to the type of OS.

The intelligent manager 1385 may provide a list of applications and an interface associated with the list of applications. For example, the application list may be an application list managed by the LpNet manager 1355, or a list generated by obtaining separate application information from the LpNet manager 1355. Further, the application list may be a list of applications whose operations are restricted by the LpNet manager 1355.

For example, the interface associated with the application list may be an interface for adjusting the application list. The user may restrict or may remove the operation restriction for a particular application through the interface. An interface associated with the application list may be determined to monitor an operation of the application registered in the application list, a usage history of the corresponding application, or a usage degree of a user.

At least a portion of program module 1310 may be implemented in software, firmware, hardware, or a combination of at least two or more of these. At least a portion of the program module 1310 may be implemented (e.g., run) by, for example, a processor (e.g., the control module 170 of fig. 1). At least a portion of the program modules 1310 may include modules, programs, routines, sets of instructions, processes, etc. for performing one or more functions.

The term "module" as used herein may mean, for example, a unit including one of hardware, software, and firmware, or a combination of two or more thereof. The term "module" may be used interchangeably with, for example, "unit," "logic block," "component," "circuit," and the like. A "module" may be a minimal unit that is an integrated component or part thereof, or may be a minimal unit that performs one or more functions or parts thereof. The "module" may be implemented mechanically or electronically. For example, a "module" may include at least one of an Application Specific Integrated Circuit (ASIC) chip, a Field Programmable Gate Array (FPGA), or a programmable logic device, currently known or to be developed in the future, for performing certain operations.

At least a portion of the apparatus (e.g., modules or functions) or method (e.g., operations) may be implemented with instructions, for example, stored in a computer-readable storage medium having programming modules. When the instructions are executed by a processor (e.g., control module 170 in fig. 1), the one or more processors may perform functions corresponding to the instructions. The computer-readable storage medium may be a memory, such as memory 120 in FIG. 1.

The computer-readable storage medium may include a hard disk, a floppy disk, a magnetic medium (e.g., magnetic tape), an optical medium (e.g., compact disc read only memory (CD-ROM) and Digital Versatile Disc (DVD)), a magneto-optical medium (e.g., floppy disk), a hardware device (e.g., ROM, Random Access Memory (RAM), flash memory, etc.), and so forth. Further, the program instructions may include machine code, which is compiled by a compiler, and may also include high-level language code, which may be executed by the computer using an interpreter or the like.

The hardware devices described above may be configured to operate as one or more software modules to perform operations according to various embodiments of the present disclosure, and vice versa.

Modules or program modules according to various embodiments of the present disclosure may include one or more of the above-described components, some of which may be omitted, or other additional components may also be included. Operations performed by modules, program modules, or other components may be performed by serial methods, parallel methods, iterative methods, or heuristic methods. Further, some operations may be performed in a different order or may be omitted, and other operations may be added.

According to embodiments of the present disclosure, an electronic device as described above may increase battery usable time by reducing current consumption caused by certain applications while the electronic device is operating.

While the present invention has been particularly shown and described with reference to certain embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the following claims and their equivalents.

Claims

1. An electronic device, comprising:

a memory configured to store a first application list including one or more applications installed in the electronic device; and

a processor configured to update the first application list by: determining a likelihood of a user noticing a notification that has been generated by an application, and when the likelihood is within a predetermined likelihood range, adding the application to the first list of applications, and

wherein the processor is further configured to control operation of the applications included in the first application list,

wherein the operation of controlling the application comprises one or more of: the method includes reducing a frequency with which the application performs a certain operation, reducing a number of times the application performs the certain operation, and prohibiting the application from performing the certain operation.

2. The electronic device of claim 1, wherein the processor is further configured to include on the first application list at least one of:

an application providing a push service is provided,

an application configured to perform an operation during a time period,

applications that will not be used during a time period, an

There is no application that responds to the user of the notification associated with the application during the time period.

3. The electronic device of claim 1, further comprising a display,

wherein the operation of the application comprises:

a first operation performed when information corresponding to an operation of the application is displayed on the display;

a second operation performed when information corresponding to an operation of the application is not displayed on the display; and

a third operation of providing information associated with another application to the other application according to a request of the other application, an

Wherein the processor is further configured to determine whether to use the application according to at least one of the first operation, the second operation, and the third operation.

4. The electronic device of claim 3, wherein the processor is further configured to provide a respective weight value for each of the first operation, the second operation, and the third operation, and to determine whether to use the application based on the weight values.

5. The electronic device of claim 1, wherein the processor is further configured to set the applications included in the first application list to one of the following states:

a first state allowing operation of the application according to a usage history of the application,

a second state reducing the number of times the application operates, an

A third state controlling at least one operation of the application, an

The processor is further configured to control operation of the application according to a setting state of the application.

6. The electronic device of claim 5, wherein the processor is further configured to change a setting state of the application according to a user input, and to control operation of the application according to the changed state of the application.

7. The electronic device of claim 1, further comprising a display,

wherein the processor is further configured to: when at least a portion of the display is inactive, then the processor controls operation of the application.

8. The electronic device of claim 1, wherein the processor is further configured to control operation of the application in accordance with at least one of:

at the present time of the day,

the current location of the electronic device is determined,

a remaining capacity of a battery of the electronic device, an

Cellular data usage.

9. The electronic device of claim 1, further comprising a communication module configured to communicate with an external electronic device,

wherein the processor is further configured to:

receiving a second application list including applications installed in the external electronic device from the external electronic device,

comparing the first application list and the second application list, an

Controlling an operation of an application performing the same function in one of the electronic device and the external electronic device when the application is identified to perform the same function by comparing the first application list and the second application list.

10. The electronic device of claim 9, wherein the processor is further configured to: when the processor is set to control the operation of the application installed in the external electronic device, the processor transmits a command for controlling the operation of the application installed in the external electronic device to the external electronic device through the communication module.

11. A method of application control by an electronic device, the method comprising:

updating a first application list comprising one or more applications installed in the electronic device by: by determining a likelihood that a user is aware of a notification that has been generated by an application, and adding the application to the first list of applications when the likelihood is within a predetermined range of likelihoods; and

controlling an operation of the applications included in the first application list,

12. The method of claim 11, wherein updating the first application list comprises including on the first application list at least one of:

an application providing a push service is provided,

an application configured to perform an operation during a time period,

applications that will not be used during a time period, an

13. The method of claim 11, wherein the operation of the application comprises:

a first operation performed when information corresponding to an operation of the application is displayed on a display;

Wherein the updating of the first application list comprises determining whether to use the application according to at least one of the first operation, the second operation, and the third operation.

14. The method of claim 13, wherein determining whether to use the application comprises:

providing a respective weight value for each of the first, second, and third operations; and

determining whether to use the application based on the weight value.

15. The method of claim 11, wherein controlling operation of the application comprises:

setting applications included in the first application list to one of the following states:

a second state reducing the number of times the application operates, an

A third state controlling at least one operation of the application; and

and controlling the operation of the application according to the set state of the application.