(19)
(11)EP 3 258 342 B1

(12)EUROPEAN PATENT SPECIFICATION

(45)Mention of the grant of the patent:
10.06.2020 Bulletin 2020/24

(21)Application number: 16749460.8

(22)Date of filing:  11.02.2016
(51)International Patent Classification (IPC): 
G06F 1/32(2019.01)
G06F 9/44(2018.01)
(86)International application number:
PCT/KR2016/001368
(87)International publication number:
WO 2016/129920 (18.08.2016 Gazette  2016/33)

(54)

METHOD FOR REDUCING BATTERY CONSUMPTION ON BASIS OF USER'S USAGE PATTERN AND APPARATUS THEREFOR

VERFAHREN ZUR REDUZIERUNG DES BATTERIEVERBRAUCHS AUF DER BASIS DES NUTZUNGSMUSTERS EINES BENUTZERS UND VORRICHTUNG DAFÜR

PROCÉDÉ POUR RÉDUIRE LA CONSOMMATION DE BATTERIE SUR LA BASE D'UN MODÈLE D'UTILISATION D'UN UTILISATEUR ET APPAREIL ASSOCIÉ


(84)Designated Contracting States:
AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

(30)Priority: 13.02.2015 KR 20150022718

(43)Date of publication of application:
20.12.2017 Bulletin 2017/51

(73)Proprietor: Samsung Electronics Co., Ltd.
Suwon-si, Gyeonggi-do 16677 (KR)

(72)Inventors:
  • UM, Tae-kwang
    Suwon-si Gyeonggi-do 16547 (KR)
  • KIM, Du-seok
    Yongin-si Gyeonggi-do 16941 (KR)
  • PARK, Hyun-cheol
    Suwon-si Gyeonggi-do 16546 (KR)
  • CHO, Ho-sik
    Suwon-si Gyeonggi-do 16509 (KR)
  • HWANG, Cheol-ju
    Yongin-si Gyeonggi-do 16846 (KR)

(74)Representative: Gulde & Partner 
Patent- und Rechtsanwaltskanzlei mbB Wallstraße 58/59
10179 Berlin
10179 Berlin (DE)


(56)References cited: : 
WO-A1-2008/110877
WO-A1-2013/130214
US-A1- 2012 280 917
US-A1- 2012 315 960
WO-A1-2012/036324
US-A1- 2011 177 847
US-A1- 2012 315 960
US-A1- 2013 222 285
  
      
    Note: Within nine months from the publication of the mention of the grant of the European patent, any person may give notice to the European Patent Office of opposition to the European patent granted. Notice of opposition shall be filed in a written reasoned statement. It shall not be deemed to have been filed until the opposition fee has been paid. (Art. 99(1) European Patent Convention).


    Description

    [Technical Field]



    [0001] The present disclosure relates to methods and apparatuses for improving efficiency of power consumption of a battery of a device, based on a use pattern of a user with respect to the device.

    [Background Art]



    [0002] Recently, functions of a device have become increasingly complex and diverse and thus, power consumption of the device is increased, whereas a size of the device is reduced. Also, the number of portable devices has increased, whereas a size of a battery in each device is decreased. Therefore, there is an increasing demand for improving efficiency of power consumption of a battery of a device.

    [0003] In order to reduce power consumption of a battery, a low-power hardware chipset may be used or an operating voltage of a device may be decreased. Also, hardware of the device may be integrated in the form of a system on chip (SoC). However, since these physical attempts have limitations in reducing the power consumption, it is required to reduce the power consumption by intelligently controlling operations of the device by using a difference between a use pattern of the device of a user and a use pattern of another device of another user.

    [0004] US 2012/0315960 A1 discloses to switch on or off components of an electronic device , i.e. manage power consumption in the portable electronic device, based on usage pattern of a user.

    [0005] WO 2013/130214 A1 discloses as well managing power consumption of an electronic device based on the usage context of the electronic device. Furthermore, the device determines the probability (likelihood) that the device remains in a standby state based on context usage data to perform a power saving action.

    [Disclosure]


    [Technical Problem]



    [0006] Provided are methods and apparatuses for improving efficiency of power consumption of a battery of a device, based on a use pattern of a user with respect to the device.

    [Technical Solution]



    [0007] According to an aspect of an exemplary embodiment, a device includes a user input unit configured to receive a user input from a user; an output unit configured to output information, based on the user input; and a controller configured to, when the user input is not received, determine whether or not an out-focus status, in which the user does not use the device, has started, to determine, when it is determined that the out-focus status has started, a period in which the out-focus status is to be maintained, based on information about a probability of the out-focus status according to a context of the device, and to stop, when the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, an operation of an application executed in the device.

    [Description of Drawings]



    [0008] 

    FIG. 1 is a diagram illustrating a method of efficiently controlling power consumption of a battery of a device, based on a period in which an out-focus status of the device is to be maintained, according to an exemplary embodiment;

    FIG. 2 illustrates a flowchart of a method of controlling an operation of an application, based on an out-focus probability, the method being performed by the device, according to an exemplary embodiment;

    FIG. 3 illustrates a flowchart of a method of resuming a stopped operation of an application, based on an end of an out-focus status, the method being performed by the device, according to an exemplary embodiment;

    FIGS. 4a and 4b illustrate diagrams in relation to a method of determining that an out-focus status has started, the method being performed by the device, according to exemplary embodiments;

    FIG. 5 illustrates a table related to a method of determining an end of an out-focus status, the method being performed by the device, according to an exemplary embodiment;

    FIG. 6 illustrates a flowchart of a method of determining an out-focus probability, based on device use pattern information of a user, the method being performed by the device, according to an exemplary embodiment;

    FIG. 7 illustrates device use pattern information of a user, according to an exemplary embodiment;

    FIG. 8 illustrates the device in relation to a method of displaying an out-focus status according to a context of the device, the method being performed by the device, according to an exemplary embodiment;

    FIG. 9 illustrates a graph related to a method of determining out-focus probabilities according to time, the method being performed by the device, according to an exemplary embodiment;

    FIG. 10a illustrates a graph related to a method of determining an out-focus probability according to a location, the method being performed by the device, according to an exemplary embodiment;

    FIG. 10b illustrates a graph related to a method of determining an out-focus probability according to a transportation type, the method being performed by the device, according to an exemplary embodiment;

    FIGS. 11a through 11d illustrate graphs related to a method of calculating an out-focus probability according to a status of the device or a surrounding environment of the device, the method being performed by the device, according to exemplary embodiments;

    FIGS. 12a and 12b illustrate diagrams related to a method of calculating an order of execution probabilities of applications according to a context, the method being performed by the device, according to exemplary embodiments;

    FIG. 13 illustrates a flowchart of a method of determining a period in which an out-focus status is to be maintained, based on out-focus probabilities according to time, the method being performed by the device, according to an exemplary embodiment;

    FIG. 14 illustrates a flowchart of a method of determining reliability of a period in which an out-focus status is to be maintained, based on an out-focus probability according to a context, the method being performed by the device, according to an exemplary embodiment;

    FIG. 15 illustrates a diagram related to a method of determining a period in which an out-focus status is to be maintained, based on out-focus probabilities according to time, the method being performed by the device, according to an exemplary embodiment;

    FIG. 16a illustrates a diagram related to a method of adjusting reliability by considering an out-focus probability at a location where an out-focus status has started, according to an exemplary embodiment;

    FIG. 16b illustrates a diagram related to a method of adjusting reliability by considering an out-focus probability corresponding to a status of the device when an out-focus status has started, according to an exemplary embodiment;

    FIG. 17a illustrates a flowchart of a method of re-determining reliability of a period in which an out-focus status is to be maintained, since a status value of a context of the device is changed, the method being performed by the device, according to an exemplary embodiment;

    FIGS. 17b and 17c illustrate diagrams related to a method of re-determining reliability of a period in which an out-focus status is to be maintained, since a status value of a context of the device is changed, the method being performed by the device, according to exemplary embodiments;

    FIG. 18 illustrates a flowchart of a method of stopping an operation of an application executed in the device, based on a period in which an out-focus status is to be maintained and reliability of the period, the method being performed by the device, according to an exemplary embodiment;

    FIG. 19 illustrates a table related to a method of controlling an operation of a background application, the method being performed by the device having an out-focus status, according to an exemplary embodiment;

    FIG. 20 illustrates a table related to a method of stopping an operation of an application, according to reliability of a period in which an out-focus status is to be maintained, the method being performed by the device, according to an exemplary embodiment;

    FIG. 21 illustrates a graph related to a method of controlling data exchange of an application, based on out-focus probabilities according to time, the method being performed by the device, according to an exemplary embodiment;

    FIGS. 22a and 22b illustrate diagrams related to a method of controlling an event when the event occurs during an out-focus status period, the method being performed by the device, according to an exemplary embodiment;

    FIG. 23 illustrates the device in relation to a method of displaying identification information of an application, based on an execution probability of the application according to a context of the device, the method being performed by the device, according to an exemplary embodiment;

    FIGS. 24a and 24b illustrate the device in relation to a method of providing a user interface for controlling an operation of an application based on a use pattern of a user, the method being performed by the device, according to exemplary embodiments;

    FIG. 25 illustrates a block diagram of the device, according to an exemplary embodiment; and

    FIG. 26 illustrates a block diagram of the device, according to another exemplary embodiment.


    [Best Mode]



    [0009] According to an aspect of an exemplary embodiment, a device includes a user input unit configured to receive a user input from a user; an output unit configured to output information, based on the user input; and a controller configured to, when the user input is not received, determine whether or not an out-focus status, in which the user does not use the device, has started, to determine, when it is determined that the out-focus status has started, a period in which the out-focus status is to be maintained, based on information about a probability of the out-focus status according to a context of the device, and to stop, when the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, an operation of an application executed in the device.

    [0010] The out-focus status, in which the user does not use the device, may indicate, since the user input is not received, at least one of a status in which the output unit does not output the information and a status in which the user does not receive the information output from the output unit.

    [0011] The context of the device may include at least one of a time, a location of the device, a status of the device, and an environment surrounding the location of the device.

    [0012] After the operation of the application is stopped, the user input unit may be further configured to receive the user input from the user, and when the user input is received from the user, the controller may be further configured to resume the stopped operation of the application.

    [0013] The output unit may include a display unit configured to display the information, and when the user input is not received for a preset time period, the controller may be further configured to inactivate the display unit, and when the display unit is inactivated, the controller may be further configured to determine that the out-focus status has started.

    [0014] The device may further include a communicator configured to receive a call connection request from a server, and when the call connection request is received, the output unit may be further configured to output information indicating reception of the call connection request, and when a user input for confirming the call connection request in response to the output information is not received, the controller may be further configured to determine that the out-focus status has started.

    [0015] The controller may be further configured to determine the period in which the out-focus status is to be maintained, based on a value of a probability of the out-focus status corresponding to a time period after the out-focus status has started, wherein the value of the probability is obtained from among information about probabilities of the out-focus status according to time.

    [0016] The controller may be further configured to determine reliability of the period in which the out-focus status is to be maintained, based on information about the probability of the out-focus status according to the context of the device, and when the reliability of the period in which the out-focus status is to be maintained is equal to or greater than a reference, the controller may be further configured to stop the operation of the application executed in the device.

    [0017] The information about the probability of the out-focus status according to the context of the device may include information about probabilities of the out-focus status according to locations of the device, and the controller may be further configured to determine the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a location of the device when the out-focus status has started, wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the locations of the device.

    [0018] The information about the probability of the out-focus status according to the context of the device may include information about probabilities of the out-focus status according to statuses of the device, and the controller may be further configured to determine the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a status of the device when the out-focus status has started, wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the statuses of the device.

    [0019] The device may further include a communicator configured to exchange data about the application with the server, even if the user input is not received, and when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller may be further configured to control the communicator to stop exchanging the data.

    [0020] Even if information about an event is received from a server, when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller may be further configured not to request the communicator to output information indicating reception of the event.

    [0021] The device may further include a communicator configured to receive updated data with respect to the application from a server, even if the user input is not received, and when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller may be further configured to control the communicator not to receive the updated data from the server.

    [0022] According to an aspect of another exemplary embodiment, a power managing method includes determining, when a user input is not received from a user, whether or not an out-focus status, in which the user does not use a device, has started; determining, when it is determined that the out-focus status has started, a period in which the out-focus status is to be maintained, based on information about a probability of the out-focus status according to a context of the device; and stopping, when the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, an operation of an application executed in the device.

    [0023] The power managing method may further include, after the operation of the application is stopped, receiving the user input from the user; and when the user input is received from the user, resuming the stopped operation of the application.

    [0024] The determining of the out-focus status may include, when the user input is not received for a preset time period, inactivating a screen of the device; and when the screen is inactivated, determining that the out-focus status has started.

    [0025] The power managing method may further include, when a call connection request is received from a server, outputting information indicating reception of the call connection request, and when a user input for confirming the call connection request in response to the output information is not received, the determining of the out-focus status may include determining that the out-focus status has started.

    [0026] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the stopping of the operation of the application may include determining reliability of the period in which the out-focus status is to be maintained, based on the information about the probability of the out-focus status according to the context of the device; and when the reliability of the period in which the out-focus status is to be maintained is equal to or greater than a reference, stopping the operation of the application executed in the device.

    [0027] The context of the device may include locations of the device, and the determining of the reliability of the period may include determining the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a location of the device when the out-focus status has started, wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the locations of the device.

    [0028] The context of the device may include statuses of the device, and the determining of the reliability of the period may include determining the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a status of the device when the out-focus status has started, wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the statuses of the device.

    [0029] The power managing method may further include exchanging data about the application with the server, even if the user input is not received, and when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the stopping of the operation of the application may include stopping exchanging the data.

    [0030] The power managing method may further include receiving information about an event form a server, and when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the stopping of the operation of the application may include not outputting information indicating reception of the event.

    [0031] The power managing method may further include receiving updated data with respect to the application from a server, even if the user input is not received, and when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the stopping of the operation of the application may include stopping receiving the updated data.

    [0032] The invention is defined in the appended independent claims.

    [Mode for Invention]



    [0033] Hereinafter, terms that are used in the specification will be briefly described, and the inventive concept will be described in detail.

    [0034] All terms including descriptive or technical terms which are used herein should be construed as having meanings that are obvious to one of ordinary skill in the art. However, the terms may have different meanings according to an intention of one of ordinary skill in the art, precedent cases, or the appearance of new technologies. Also, some terms may be arbitrarily selected by the applicant, and in this case, the meaning of the selected terms will be described in detail in the detailed description of the inventive concept. Thus, the terms used herein have to be defined based on the meaning of the terms together with the description throughout the specification.

    [0035] Also, when a part "includes" or "comprises" an element, unless there is a particular description contrary thereto, the part can further include other elements, not excluding the other elements. In the following description, terms such as "unit" and "module" indicate a unit for processing at least one function or operation, wherein the unit and the block may be embodied as hardware or software or embodied by combining hardware and software.

    [0036] Throughout the specification, the term "out-focus status" may mean a status in which a user does not use a device. For example, the out-focus status may indicate a status in which the device does not output information, according to non-reception of a user input. Also, the out-focus status may indicate a status in which, even if the device outputs information, the user does not receive the output information. In an exemplary embodiment, the term "out-focus status" may be referred to as "non-use status" or "out-of-coverage status".

    [0037] Throughout the specification, the term "context of a device" may correspond to information indicating a status of the device. For example, the context of the device may include, but is not limited to, a time, a location of the device, a status of the device, and a surrounding environment of the device.

    [0038] One or more embodiments will now be described more fully with reference to the accompanying drawings. However, the one or more embodiments may be embodied in many different forms, and should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the one or more embodiments to those of ordinary skill in the art. In the following description, well-known functions or constructions are not described in detail since they would obscure the one or more embodiments with unnecessary detail, and also, throughout the specification, like reference numerals in the drawings denote like elements.

    [0039] As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items. Expressions such as "at least one of," when preceding a list of elements, modify the entire list of elements and do not modify the individual elements of the list.

    [0040] FIG. 1 is a diagram illustrating a method of efficiently controlling power consumption of a battery of a device 100, based on a period in which an out-focus status of the device 100 is to be maintained, according to an exemplary embodiment.

    [0041] Referring to FIG. 1, the device 100 may calculate a probability of a user having an out-focus status with respect to the device 100, and may improve efficiency of power consumption of a battery of the device 100, based on the calculated probability with respect to the out-focus status.

    [0042] The out-focus status may mean a status in which the user does not use the device 100. Also, throughout the specification, a probability of the out-focus status may be referred to as an out-focus probability.

    [0043] The device 100 may determine a start or end of the out-focus status. For example, when a user input is not received and thus a screen of the device 100 is turned off, the device 100 may determine that the out-focus status has started. As another example, when a strength of a short-distance wireless signal between the device 100 and a wearable device becomes equal to or less than a reference strength, the device 100 may determine that the out-focus status has started.

    [0044] When the device 100 determines that the out-focus status has been started, the device 100 may determine a period in which the out-focus status is to be maintained, and reliability of the period, based on an out-focus probability according to a context of the device 100. The context of the device 100 may include, but is not limited to, a time, a location of the device 100, a status of the device 100, and a surrounding environment of the device 100.

    [0045] The out-focus probability according to the context of the device 100 may be previously calculated by the device 100. For example, based on device use pattern information of the user during a preset time period, the device 100 may calculate the out-focus probability according to the time, a place of the device 100, the status of the device 100, or the surrounding environment of the device 100.

    [0046] When the context of the device 100 is changed, the device 100 may determine a period in which an out-focus status is to be maintained, and reliability of the period, based on an out-focus probability corresponding to a changed context.

    [0047] Based on the period in which the out-focus status is to be maintained, and the reliability of the period in which the out-focus status is to be maintained, the device 100 may stop an operation of an executed application and thus may improve efficiency of the power consumption.

    [0048] For example, in a case where the period in which the out-focus status is to be maintained is equal to or greater than a reference time, and the reliability is equal to or greater than a reference value, the device 100 may stop data exchange between an external server and a background processor of the device 100 and thus may reduce the power consumption of the battery. As another example, the device 100 may block an update of an application and thus may reduce the power consumption of the battery. As another example, even if the device 100 receives push data from an external server, the device 100 may not notify the user and thus may reduce the power consumption of the battery.

    [0049] As another example, the device 100 may recommend the user for an application having a high execution number of times, based on an execution number of times of applications according to the context of the device 100. Accordingly, the device 100 may decrease a user's touch input to execute an application and thus may reduce the power consumption of the battery.

    [0050] FIG. 2 illustrates a flowchart of a method of controlling an operation of an application, based on an out-focus probability, the method being performed by the device 100, according to an exemplary embodiment.

    [0051] In operation S210, when a user input is not received from a user, the device 100 may determine whether an out-focus status in which the user does not use the device 100 has started.

    [0052] When the user input is not received from the user for a preset time period, the device 100 may inactivate a display unit (not shown) of the device 100. When the display unit of the device 100 is inactivated, i.e., when a screen of the device 100 is turned off, the device 100 may determine that the out-focus status has started. In an exemplary embodiment, when an operation mode of the device 100 is changed to a sleep mode or a power saving mode, the device 100 may determine that the out-focus status has started.

    [0053] While an image or sound to notify the user about reception of a call connection request is output, if a user input for call connection is not received, the device 100 may determine that the out-focus status has started.

    [0054] After an image or sound to notify the user about reception of a message is output, if a user input for checking the message is not received within a preset time period, the device 100 may determine that the out-focus status has started.

    [0055] While the device 100 communicates with a wearable device, if a strength of a short-distance wireless signal between the device 100 and the wearable device becomes equal to or less than a reference strength, the device 100 may determine that the out-focus status has started.

    [0056] In operation S220, since the device 100 determined that the out-focus status started, the device 100 may determine a period in which the out-focus status is to be maintained, based on information about a probability of the out-focus status according to a context of the device 100.

    [0057] The context of the device 100 may include, but is not limited to, a time, a location of the device 100, a status of the device 100, and a surrounding environment of the device 100.

    [0058] For example, based on an out-focus probability according to the time, the device 100 may calculate the period in which the out-focus status is to be maintained from a start of the out-focus status.

    [0059] In operation S230, when the calculated period in which the out-focus status is to be maintained is equal to or greater than a reference time period, the device 100 may stop an operation of an application that is executed in the device 100.

    [0060] Based on the out-focus probability of the period in which the out-focus status is to be maintained from the start of the out-focus status, the device 100 may determine reliability of the period in which the out-focus status is to be maintained. Only when the determined reliability of the period in which the out-focus status is to be maintained is equal to or greater than a reference, the device 100 may stop the operation of the application that is executed in the device 100.

    [0061] In this case, the device 100 may further consider an out-focus probability with respect to a location of the device 100 at the start of the out-focus status, and may determine the reliability of the period in which the out-focus status is to be maintained.

    [0062] In this case, the device 100 may further consider an out-focus probability with respect to a status of the device 100 at the start of the out-focus status, and may determine the reliability of the period in which the out-focus status is to be maintained.

    [0063] When the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, the device 100 may stop data exchange between a server and a background application of the device 100 and thus may improve efficiency of power consumption of a battery of the device 100.

    [0064] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, even if an event occurs in the device 100, the device 100 may not output information of the event and thus may improve the efficiency of the power consumption.

    [0065] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the device 100 may not receive updated data from the server and thus may improve the efficiency of the power consumption.

    [0066] Based on information about an application use pattern of the user, the device 100 may adjust a position, a shape, a size, or a color of an icon of an application according to a context of the device 100, and thus may allow the application, which is frequently used according to the context of the device 100, to be easily found than an application that is not frequently used. Accordingly, an image conversion required to select an application is decreased, so that the efficiency of the power consumption of the battery of the device 100 may be improved.

    [0067] FIG. 3 illustrates a flowchart of a method of resuming a stopped operation of an application, based on an end of an out-focus status, the method being performed by the device 100, according to an exemplary embodiment.

    [0068] In operation S310, after the operation of the application is stopped, the device 100 may receive a user input from a user.

    [0069] For example, the device 100 may inactivate a screen in the out-focus status, and while the screen is inactivated, the device 100 may receive a user input for pressing a key to activate the screen.

    [0070] In operation S320, when the user input is received, the device 100 may resume the stopped operation of the application.

    [0071] When the user input is received in the out-focus status, the device 100 may cancel the out-focus status and may resume the stopped operation of the application.

    [0072] For example, the device 100 may resume stopped data exchange between a server and a background application of the device 100. The device 100 may output event information that was not output. The device 100 may receive, from the server, updated data that was not received, and may update an application by using the updated data.

    [0073] FIG. 4a illustrates a table related to a method of determining that an out-focus status has started, the method being performed by the device 100, according to an exemplary embodiment.

    [0074] Referring to FIG. 4a, the device 100 may determine the out-focus status, based on a predefined operation of the device 100 and a user's reaction with respect to the predefined operation of the device 100.

    [0075] For example, when the device 100 receives a user input for turning off a screen when the screen of the device 100 is turned on, the device 100 may turn off the screen. When the device 100 does not receive a user input for a preset time period, the device 100 may turn off the screen. Since the screen is turned off, the device 100 may determine that the out-focus status has started.

    [0076] In an exemplary embodiment, when an operation mode of the device 100 is changed to a sleep mode, the device 100 may determine that the out-focus status has started. The sleep mode may indicate a mode during which operations of the device 100 are temporally stopped. For example, during the sleep mode, the device 100 may store, in a random-access memory (RAM), a machine state (e.g., a register value, a stack pointer value, etc.) indicating an operating status of the device 100, may supply, to the RAM, a power sufficient only to retain data in the RAM, may block a power supply to other physical configurations of the device 100, and thus may temporally stop the device 100. In some embodiments, the sleep mode may be referred to as a power saving mode. When the device 100 receives the user input for turning off the screen or does not receive the user input for the preset time period, the device 100 may change the operation mode of the device 100 to the sleep mode.

    [0077] As another example, when the device 100 receives a call connection request from a telephone network server, the device 100 may output an image or sound to notify the user about reception of the call connection request. In this regard, when a user input for call connection is not received and thus the call connection request is refused, the device 100 may determine that the out-focus status has started.

    [0078] For example, when a push message is received from a server, the device 100 may output an image or sound to notify the user about reception of the push message. When a user input for checking the push message is not received, the device 100 may determine that the out-focus status has started.

    [0079] As another example, when the user wears a wearable device such as a watch and uses both the device 100 and the watch, the device 100 may communicate with the wearable device via short-distance communication. As illustrated in FIG. 4B, when the user becomes distant from the device 100, a strength (e.g., a received signal strength indicator (RSSI)) of a short-distance wireless signal between the device 100 and a wearable device 410 may be decreased. When the strength of the short-distance wireless signal between the device 100 and the wearable device 410 becomes equal to or less than a reference strength, the device 100 may determine that the out-focus status has started. In a case where the user becomes distant from the device 100 and thus Bluetooth pairing between the device 100 and the wearable device 410 is discontinued, the device 100 may determine that the out-focus status has started.

    [0080] When the screen is turned off, a call is missed, or a message is missed, the device 100 may determine the out-focus status by further considering a type of an application executed in the device 100.

    [0081] When the screen is turned off, the call is missed, or the message is missed, if an application for outputting data such as music or a moving picture is executed in the device 100, the device 100 may not determine that the out-focus status has started but may determine that an in-focus status in which the user uses the device 100 is maintained. When an application for exchanging data between an external device and the device 100 is executed, wherein the exchange, e.g., tethering or data exchange with a personal computer (PC), is performed due to manipulation by the user, the device 100 may determine that the in-focus status is maintained.

    [0082] FIG. 5 illustrates a table related to a method of determining an end of an out-focus status, the method being performed by the device 100, according to an exemplary embodiment.

    [0083] Referring to FIG. 5, when the device 100 receives a user input by using a sensor in the device 100, the device 100 may determine that the out-focus status has been ended. The sensor in the device 100 may include, but is not limited to, a button key, a touch key, an operation sensor, a posture sensor, a motion sensor, or the like.

    [0084] In an exemplary embodiment, even if the device 100 receives a first input by using the sensor in the device 100, if a second input is not received for a preset time period from when the first input is received, the device 100 may not determine that the out-focus status has been ended but may determine that the out-focus status is maintained. Accordingly, even if the button key or the touch key is pressed regardless of a user's intention since the device 100 is inside a pocket or a bag, the device 100 may not determine that the out-focus status has been ended but may determine that the out-focus status is maintained.

    [0085] In a case where an application is executed in the device 100 and thus information is output, if a strength of a short-distance wireless signal between the device 100 and a wearable device is decreased and then is increased, the device 100 may determine that the out-focus status has started and then is ended again.

    [0086] FIG. 6 illustrates a flowchart of a method of determining an out-focus probability, based on device use pattern information of a user, the method being performed by the device 100, according to an exemplary embodiment.

    [0087] In operation S610, the device 100 may store the device use pattern information of the user.

    [0088] As illustrated in FIG. 7, the device use pattern information may include a location of the device 100 according to time, a status of the device 100, and an environment surrounding the location of the device 100. Also, the device use pattern information may include one or more pieces of identification information of applications and entry paths of the applications that are executed according to time. The device use pattern information may include information about a user's reaction with respect to an event output from the device 100.

    [0089] The device 100 may store locations of the device 100 according to time. For example, the device 100 may periodically obtain location information of the device 100 by using a global positioning system (GPS) sensor in the device 100. The device 100 may store the obtained location information in correspondence to a time when the location information is obtained.

    [0090] The device 100 may store one or more pieces of information about the status of the device 100 according to time. The information about the status of the device 100 may include, but is not limited to, information about whether or not earphones are connected, information about a type of a wearable device connected to the device 100, information about a type of a wireless network connected to the device 100, information about an internet protocol (IP) address of an access point that connects the device 100 and the wireless network, information about minute-by-minute power consumption of a battery of the device 100, and information about whether or not the battery of the device 100 is being charged. When the status of the device 100 is changed, the device 100 may store a changed status in correspondence to a time of the changed status.

    [0091] The device 100 may store a time-based change of the environment that surrounds the location of the device 100. For example, the device 100 may obtain an illuminance level or a noise level around the device 100 by using an illuminance sensor or a noise sensor in the device 100. Since the device 100 obtains information about a change of the environment, the device 100 may store the obtained information about the change in correspondence to a time when the information is obtained.

    [0092] The device 100 may store execution information of an application. For example, when execution of the application is started or is ended, the device 100 may store whether or not the application is started or is ended in correspondence to a start time or an end time.

    [0093] The device 100 may store a user's reaction with respect to a message reception notice or a call connection request notice.

    [0094] In an exemplary embodiment, the device 100 may determine whether an out-focus status has started or has been ended, and may store the out-focus status in correspondence to every start time or every end time of the out-focus status.

    [0095] In operation S620, the device 100 may calculate, based on the device use pattern information of the user, an out-focus probability and an application execution probability according to a context of the device 100.

    [0096] The device 100 may obtain pre-stored out-focus status information according to time. Also, the device 100 may determine a status, in which an application is not executed, as an out-focus status in which the user does not use the device 100, and thus may obtain out-focus status information by referring to a pre-stored execution time of the application.

    [0097] The device 100 may calculate the out-focus probability, based on one or more pieces of out-focus status information during a preset period.

    [0098] For example, the device 100 may determine the out-focus probability in a unit of a reference time of 0 a.m. through 24 p.m., based on one or more pieces of out-focus status information during recent days. The reference time may be, but is not limited to, 5 minutes, 10 minutes, 30 minutes, or 1 hour.

    [0099] The device 100 may determine out-focus probabilities corresponding to days of the week, respectively. The device 100 may determine an out-focus probability corresponding to weekdays or a weekend.

    [0100] The device 100 may determine an out-focus probability according to a location. For example, the device 100 may obtain a value calculated by adding a value of an out-focus status according to the location to a value of a time period of the out-focus status at the same location during a preset period. The device 100 may divide the obtained value by a time period during which the device 100 is located at the same location during the preset period, and thus may determine the out-focus probability at the same location.

    [0101] The device 100 may determine an out-focus probability according to a transportation type. For example, the device 100 may obtain a value calculated by adding a value of an out-focus status according to the transportation type to a value of a time period of the out-focus status in the same transportation type during a preset period. The device 100 may divide the obtained value by a time period during which the device 100 is located in the same transportation type during the preset period, and thus may determine the out-focus probability in the same transportation type.

    [0102] Also, the device 100 may determine an out-focus probability according to a change in a status of the device 100. For example, the device 100 may determine an out-focus probability with respect to a wearable device, based on a value of an out-focus status according to the wearable device connected to the device 100.

    [0103] The device 100 may determine an out-focus probability according to a change in an environment around the device 100. For example, the device 100 may determine an out-focus probability according to a noise level, based on a value of the out-focus probability according to the noise level.

    [0104] The device 100 may autonomously calculate an out-focus probability, or may transmit, to a pattern calculation server, information about a time, a location, a status of the device 100, and an environment surrounding the location of the device 100, and may receive the out-focus probability from the pattern calculation server. In this case, based on use pattern information of the user which is received from the device 100, the pattern calculation server may calculate the out-focus probability according to a change in the environment surrounding the location of the device 100.

    [0105] The device 100 may calculate an execution probability of each of applications according to a context of the device 100. The context may include, but is not limited to, a time, a location of the device 100, a status of the device 100, and a surrounding environment of the device 100.

    [0106] For example, the device 100 may divide a total time periods in which a web browser is executed in the subway during a preset period by a total time periods in which all applications are executed in the subway during the preset period, and thus may calculate an execution probability of the web browser with respect to the subway.

    [0107] As another example, the device 100 may divide the number of times a game application is executed when a type of a network connected to the device 100 is Wi-Fi by the number of times all applications are executed when the type of the network connected to the device 100 is Wi-Fi, and thus may calculate an execution probability of the game application with respect to Wi-Fi.

    [0108] The device 100 may calculate a user's reaction probability with respect to an event based on the context. The device 100 may consider the calculated user's reaction probability with respect to the event based on the context, and may calculate an out-focus probability with respect to the context.

    [0109] For example, when the number of times a call is missed or a message is not checked during an out-focus status in a particular time zone is greater than in other time zones, the device 100 may set an out-focus probability in the particular time zone to be higher than out-focus probabilities in other time zones.

    [0110] The device 100 may determine, based on calculated execution probabilities of applications according to the context, an order of an execution probability of an application among the applications according to the context.

    [0111] The device 100 may calculate hourly power consumption of the battery with respect to a particular application. The device 100 may calculate hourly power consumption of the battery with respect to the context.

    [0112] FIG. 7 illustrates device use pattern information of a user, according to an exemplary embodiment.

    [0113] Referring to FIG. 7, the device 100 may store the use pattern information of the user.

    [0114] The device 100 may calculate latitudes and longitudes of the device 100 which are changed according to movement of the device 100. In this case, the device 100 may also store times where the latitudes and longitudes are obtained.

    [0115] In an exemplary embodiment, the device 100 may store an IP address of an access point that connects the device 100 to a network. The device 100 may recognize a place, based on the stored IP address, and may store an out-focus status according to the identified place.

    [0116] The device 100 may store information about a status of the device 100 according to time. The status of the device 100 may include, but is not limited to, connection or disconnection of earphones, a type of a wearable device connected to the device 100, a network allowing communication between the device 100 and an external device, or power consumption of a battery of the device 100.

    [0117] When the device 100 and the wearable device are connected to each other, the device 100 may receive identification information of the wearable device from the wearable device. The device 100 may determine the type of the wearable device, based on the received identification information of the wearable device.

    [0118] Whenever a preset status of the device 100 is changed, the device 100 may store a time and the changed status. For example, when earphones are connected or are disconnected, when the wearable device is connected or is disconnected, when the network connected to the device 100 is changed, or when the power consumption of the battery is changed exceeding a reference range, the device 100 may store the changed status and the time of the change.

    [0119] The device 100 may store information about a surrounding environment of the device 100 according to time. The surrounding environment of the device 100 may include, but is not limited to, illuminance or noise.

    [0120] The device 100 may store application execution information according to time. The application execution information may include, but is not limited to, identification information of an application that is executed or is ended, time information about when the application is executed or is ended, and information about an entry path when the application is executed.

    [0121] The device 100 may store information of a user's reaction with respect to an event. The event may include, but is not limited to, a message reception notice, a call connection request notice, an alarm notice, a schedule notice, or the like.

    [0122] In an exemplary embodiment, the device 100 may determine whether an out-focus status has started or has been ended, and whenever the out-focus status starts or is ended, the device 100 may store a start or an end of the out-focus status in correspondence to time.

    [0123] FIG. 8 illustrates the device 100 in relation to a method of displaying an out-focus status according to a context of the device 100, the method being performed by the device 100, according to an exemplary embodiment.

    [0124] Referring to FIG. 8, the device 100 may provide an out-focus status according to time.

    [0125] For example, when the device 100 receives a user input for selecting a menu to display an out-focus status, the device 100 may display an image 810 indicating the out-focus status according to time.

    [0126] The out-focus status according to time may include, but is not limited to, an out-focus status detected on a particular date, an average out-focus status of a particular day, an average out-focus status during a particular period, an average out-focus status during weekdays, or an average out-focus status during a weekend.

    [0127] FIG. 9 illustrates a graph related to a method of determining out-focus probabilities according to time, the method being performed by the device 100, according to an exemplary embodiment.

    [0128] Referring to FIG. 9, the device 100 may calculate out-focus probabilities according to time of 0 a.m. through 24 p.m. on each of Monday through Sunday.

    [0129] For example, the device 100 may determine an out-focus probability in a unit of a reference time of 0 a.m. through 24 p.m., based on information about an out-focus status on recent Mondays.

    [0130] For example, the device 100 may divide total time periods of out-focus statuses between 22:00 to 22:10 for 30 Mondays by 300 minutes (10 minutes x 30) that is a total time, and thus may determine an out-focus probability between 22:00 to 22:10 on Monday.

    [0131] The device 100 may calculate the out-focus probabilities according to time on each of Monday through Sunday or may calculate an out-focus probability during weekdays or a weekend.

    [0132] FIG. 10a illustrates a graph related to a method of determining an out-focus probability according to a location, the method being performed by the device 100, according to an exemplary embodiment.

    [0133] Referring to FIG. 10a, the device 100 may calculate an out-focus probability in a particular location or a particular movement path.

    [0134] The device 100 may determine a place where the device 100 is located for a certain period of time, based on location information according to time with respect to the device 100. For example, the device 100 may determine a staying time period of the device 100 in each place, and when an average value of a staying time period of the device 100 in a particular place is equal to or greater than a reference time period, the device 100 may determine the particular place as a place where the device 100 is mainly located. Accordingly, the device 100 may recognize a location such as a user's residence, workplace, or class room. For example, the device 100 may recognize a place where the device 100 is located, based on an IP address of an access point that connects the device 100 to a network.

    [0135] The device 100 may recognize a movement path where the device 100 is mainly moved, based on location information according to time with respect to the device 100. For example, the device 100 may determine a movement path where the device 100 is moved, based on the location information according to time, and when the number of using the determined movement path is equal to or greater than a reference number, the device 100 may determine the determined movement path as a path where the device 100 is mainly moved. In this case, even if the path is one connected movement path, the device 100 may determine the path as different movement paths according to movement speeds.

    [0136] After the place where the device 100 is mainly located, and the main movement path of the device 100 are determined, the device 100 may calculate an out-focus probability in a particular location and a particular movement path.

    [0137] For example, the device 100 may divide a total time period of an out-focus status in the particular location by a total staying time period with respect to the particular location, and thus may calculate the out-focus probability in the particular location. The device 100 may divide a total time period of an out-focus status in the particular movement path by a total staying time period with respect to the particular movement path, and thus may calculate the out-focus probability in the particular movement path.

    [0138] FIG. 10b illustrates a graph related to a method of determining an out-focus probability according to a transportation type, the method being performed by the device 100, according to an exemplary embodiment.

    [0139] Referring to FIG. 10, the device 100 may calculate the out-focus probability according to the transportation type.

    [0140] For example, the device 100 may recognize the transportation type, based on location information according to time. For example, when the location information according to time with respect to the device 100 is similar to a pre-stored movement path via the subway, the device 100 may determine that a user having the device 100 moved via the subway. When the location information according to time with respect to the device 100 is similar to a pre-stored movement pattern via a bus, the device 100 may determine that the user having the device 100 moved via the bus. The movement pattern via the bus may be a pattern of stopping for several seconds at each of predefined bus stops.

    [0141] When the location information according to time with respect to the device 100 indicates a pre-stored pattern of moving along a road, the device 100 may determine that the user having the device 100 moved via a vehicle.

    [0142] When the transportation type that is mainly used is determined, the device 100 may calculate the out-focus probability with respect to a particular transportation type.

    [0143] For example, the device 100 may divide a total time period of an out-focus status with respect to the particular transportation type by a total time period of using the particular transportation type, and thus may calculate the out-focus probability with respect to the particular transportation type.

    [0144] FIGS. 11a through 11d illustrate graphs related to a method of calculating an out-focus probability according to a status of the device 100 or a surrounding environment of the device 100, the method being performed by the device 100, according to exemplary embodiments.

    [0145] Referring to FIG. 11a, the device 100 may calculate an out-focus probability about when a battery of the device 100 is being charged or is not charged, based on information about an out-focus status with respect to whether or not the battery is charged.

    [0146] Referring to FIG. 11b, the device 100 may calculate an out-focus probability with respect to an entry path of an application, based on information about an out-focus status according to the entry path. For example, the entry path may include an entry path through an event notice or a direct entry path by a user.

    [0147] Referring to FIG. 11c, the device 100 may calculate an out-focus probability with respect to a type of a network, based on information about an out-focus status according to the type of the network.

    [0148] Referring to FIG. 11d, the device 100 may calculate an out-focus probability with respect to a type or identification information of a wearable device connected to the device 100, based on information about an out-focus status according to the type or identification information of the wearable device.

    [0149] FIGS. 12a and 12b illustrate diagrams related to a method of calculating an order of execution probabilities of applications according to a context, the method being performed by the device 100, according to exemplary embodiments.

    [0150] Referring to FIG. 12a, the device 100 may calculate the order of the execution probabilities of the applications according to time, based on device use pattern information of a user.

    [0151] For example, the device 100 may divide a total time period in which a web browser is executed from 18 p.m. through 18:30 p.m. during a preset period by a total time period in which all applications are executed during the same time, and thus may calculate an execution probability of the web browser from 18 p.m. through 18:30 p.m.

    [0152] When the execution probabilities of the applications installed in the device 100 are calculated, the device 100 may calculate an order of an application to be executed during a particular time, based on the calculated execution probabilities of the applications with respect to the particular time.

    [0153] Referring to FIG. 12b, the device 100 may calculate an order of application execution probabilities according to a place, based on the device use pattern information of the user.

    [0154] For example, the device 100 may divide a total time period in which a game application is executed in home during a preset period by a total time period in which all applications are executed in home during the preset period, and thus may calculate a possibility of execution of the game application in home.

    [0155] When the execution probabilities of the applications installed in the device 100 are calculated, the device 100 may calculate the order of the application to be executed at the particular place, based on the calculated execution probabilities of the applications with respect to the particular place.

    [0156] FIG. 13 illustrates a flowchart of a method of determining a period in which an out-focus status is to be maintained, based on out-focus probabilities according to time, the method being performed by the device 100, according to an exemplary embodiment.

    [0157] In operation S1310, the device 100 may determine, based on the out-focus probabilities according to time, whether or not an out-focus probability when an out-focus status starts is equal to or greater than a threshold value.

    [0158] For example, the threshold value may be 75 % and is not limited thereto.

    [0159] In operation S1320, if the out-focus probability when the out-focus status starts is equal to or greater than the threshold value, the device 100 may detect a point of time when the out-focus probability becomes less than the threshold value after the out-focus status starts.

    [0160] If the out-focus probability when the out-focus status starts is equal to or greater than the threshold value, the device 100 may detect a point of time when the out-focus probability initially becomes less than the threshold value after the out-focus status starts.

    [0161] In operation S1330, the device 100 may determine a period from when the out-focus status starts to when the out-focus probability becomes less than the threshold value, as the period in which the out-focus status is to be maintained.

    [0162] In an exemplary embodiment, if the out-focus probability when the out-focus status starts is equal to or greater than the threshold value, the device 100 may detect a particular point of time when an average value of out-focus probabilities from when the out-focus status starts to the particular point of time becomes equal to or greater than a preset threshold value, and may determine a period from when the out-focus status starts to the detected particular point of time, as the period in which the out-focus status is to be maintained.

    [0163] FIG. 14 illustrates a flowchart of a method of determining reliability of a period in which an out-focus status is to be maintained, based on an out-focus probability according to a context, the method being performed by the device 100, according to an exemplary embodiment.

    [0164] In operation S1410, the device 100 may determine reliability of a period in which an out-focus status is to be maintained, based on an out-focus probability of a period from when the out-focus status has started to when the out-focus status is to be maintained.

    [0165] For example, the device 100 may determine the reliability of the period in which the out-focus status is to be maintained, based on an average value of out-focus probabilities of the period from when the out-focus status has started to when the out-focus status is maintained.

    [0166] In operation S1420, the device 100 may adjust the reliability of the period in which the out-focus status is to be maintained, based on an out-focus probability corresponding to a location of the device 100.

    [0167] The device 100 may determine the location of the device 100 when the out-focus status has started. The device 100 may obtain an out-focus probability corresponding to the determined location, based on the out-focus probability according to the location.

    [0168] The device 100 may adjust the reliability of the period in which the out-focus status is to be maintained, based on the out-focus probability corresponding to the location.

    [0169] In operation S1430, the device 100 may adjust the reliability of the period in which the out-focus status is to be maintained, based on an out-focus probability corresponding to a status of the device 100.

    [0170] The device 100 may determine the status of the device 100 when the out-focus status has started. The device 100 may obtain an out-focus probability corresponding to the determined status, based on the out-focus probability according to the status. The device 100 may adjust the reliability of the period in which the out-focus status is to be maintained, based on the out-focus probability corresponding to the status.

    [0171] In FIG. 14, the time, the location of the device 100, and the status of the device 100 are described as parameters to be considered so as to determine the reliability of the period in which the out-focus status is to be maintained. However, the device 100 may consider another context of the device 100 other than the parameters and may determine the reliability of the period in which the out-focus status is to be maintained.

    [0172] For example, according to status values of contexts of the device 100, the device 100 may determine a context among the contexts, whose difference between its status value and the out-focus probability is equal to or greater than a reference, as a parameter to determine the reliability of the period in which the out-focus status is to be maintained.

    [0173] The device 100 may vary a weight of the contexts and may determine the reliability of the period in which the out-focus status is to be maintained. For example, according to the status values of the contexts of the device 100, the greater a difference between a value of the out-focus probability and a status value of a context among the contexts is, the greater the weight added by the device 100 to the context.

    [0174] In an exemplary embodiment, when an out-focus probability according to a context of the device 100 when the out-focus status has started is within a reference range, the device 100 may not consider, in calculating the reliability, the context whose out-focus probability is within the reference range. For example, the reference range may be between 45 % through 55 %.

    [0175] For example, when an out-focus probability at a particular location is between 45 % through 55 %, a probability whether or not the user uses the device 100 at the particular location may be considered as meaningless data, thus, the device 100 may not consider the context whose out-focus probability is within the reference range.

    [0176] FIG. 15 illustrates a diagram related to a method of determining a period in which an out-focus status is to be maintained, based on out-focus probabilities according to time, the method being performed by the device 100, according to an exemplary embodiment.

    [0177] Referring to FIG. 15, the device 100 may determine the period in which the out-focus status is to be maintained, based on the out-focus probabilities according to time.

    [0178] For example, when a time when the out-focus status has started is 9:30 a.m., the device 100 may obtain an out-focus probability corresponding to 9:30 a.m., based on the out-focus probabilities according to time.

    [0179] When the out-focus probability corresponding to 9:30 a.m. is 90 %, the device 100 may determine whether or not 90 % is equal to or greater than a threshold value. If the threshold value is 75 %, the device 100 may determine that the out-focus probability corresponding to 9:30 a.m. is equal to or greater than the threshold value.

    [0180] When the device 100 determines that the out-focus probability corresponding to 9:30 a.m. is equal to or greater than the threshold value, the device 100 may detect a point of time when an out-focus probability among out-focus probabilities of time periods after 9:30 a.m. initially becomes less than the threshold value. Referring to FIG. 15, the point of time when the out-focus probability among the out-focus probabilities of the time periods after 9:30 a.m. initially becomes less than 75 % that is the threshold value may be 11:50 a.m.

    [0181] Since the point of time when the out-focus probability initially becomes less than the threshold value is detected, the device 100 may determine a time period of 2 hours and 20 minutes from 9:30 a.m. when the out-focus status has started to 11:50 a.m. when the out-focus probability initially becomes less than the threshold value, as the period in which the out-focus status is to be maintained.

    [0182] The device 100 may determine, as reliability of the period of the out-focus status, an average value of out-focus probabilities corresponding to the period in which the out-focus status is to be maintained. Referring to FIG. 15, the device 100 may determine 80% that is an average value of out-focus probabilities from 9:30 a.m. to 11:50 a.m., as reliability of the time period of 2 hours and 20 minutes.

    [0183] When a threshold value of preset reliability is 70 %, the device 100 may determine that the device 100 will have an out-focus status during the time period of 2 hours and 20 minutes.

    [0184] FIG. 16a illustrates a diagram related to a method of adjusting reliability by considering an out-focus probability at a location where an out-focus status has started, according to an exemplary embodiment.

    [0185] Referring to FIG. 16a, the device 100 may adjust the reliability by considering the out-focus probability at the location where the out-focus status has started.

    [0186] The device 100 may determine that the location where the out-focus status has started is a movement path 1, based on latitude and longitude information of the location where the out-focus status has started. The device 100 may also determine that the location where the out-focus status has started is the movement path 1, based on an IP address of an access point that connects the device 100 to a network.

    [0187] Based on the out-focus probability according to the location, the device 100 may obtain an out-focus probability at the movement path 1. When the out-focus probability in a place 1 is 10 %, the device 100 may determine 30 % as the reliability of the time period of 2 hours and 20 minutes by averaging or weight-averaging 80 % and 10 %, wherein 80 % is the reliability of the period in which the out-focus status is to be maintained, which is determined with reference to FIG. 15, and 10 % is the out-focus probability in the place 1.

    [0188] If the reliability for which a location is further considered drops below 30 %, the device 100 may not determine that the out-focus status will be maintained during the time period of 2 hours and 20 minutes.

    [0189] FIG. 16b illustrates a diagram related to a method of adjusting reliability by considering an out-focus probability corresponding to a status of the device 100 when an out-focus status has started, according to an exemplary embodiment.

    [0190] Referring to FIG. 16b, the device 100 may adjust the reliability by considering an out-focus probability corresponding to a wearable device connected to the device 100 when the out-focus status has started.

    [0191] For example, the out-focus probability may be 30 % when the wearable device is not connected to the device 100, the out-focus probability may be 85 % when a watch is connected to the device 100, and the out-focus probability may be 90 % when glasses are connected to the device 100.

    [0192] When the device 100 determines that the out-focus status has started, the device 100 may obtain identification information of the wearable device connected to the device 100. The device 100 may also obtain an out-focus probability corresponding to the obtained identification information of the wearable device.

    [0193] In a case where the identification information of the wearable device connected to the device 100 indicates the watch, and the out-focus probability corresponding to the watch is 85 %, the device 100 may determine 70 % as the reliability of the time period of 2 hours and 20 minutes by averaging or weight-averaging 80 %, 10 %, and 85 %, wherein 80 % is the reliability of the period in which the out-focus status is to be maintained, which is determined with reference to FIG. 15, 10 % is the out-focus probability in the place 1 shown in FIG. 16a, and 85 % is the out-focus probability corresponding to the watch.

    [0194] If the reliability for which the identification information of the wearable device is further considered increases up to 70 %, the device 100 may determine that the out-focus status will be maintained during the time period of 2 hours and 20 minutes.

    [0195] FIG. 17a illustrates a flowchart of a method of re-determining reliability of a period in which an out-focus status is to be maintained, since a status value of a context of the device 100 is changed, the method being performed by the device 100, according to an exemplary embodiment.

    [0196] In operation S1710, the device 100 having the out-focus status may determine whether or not a location of the device 100, a status of the device 100, or a surrounding environment of the device 100 is changed.

    [0197] For example, the device 100 may determine whether earphones are connected or disconnected, the location of the device 100 is changed and thus exceeds a reference range, or illuminance surrounding the device 100 is changed and thus exceeds a reference range.

    [0198] In operation S1720, when the device 100 determines that the status value of the context of the device 100 has been changed, the device 100 may re-determine, based on a changed status value, reliability of the period in which the out-focus status is to be maintained.

    [0199] For example, when the device 100 determines that the location of the device 100 is changed and thus exceeds the reference range, or determines that a wearable device that has been connected to the device 100 is disconnected, the device 100 may re-determine the reliability of the period in which the out-focus status is to be maintained, based on an out-focus probability at a changed location or an out-focus probability when the wearable device is not connected.

    [0200] FIGS. 17b and 17c illustrate diagrams related to a method of re-determining reliability of a period in which an out-focus status is to be maintained, since a status value of a context of the device 100 is changed, the method being performed by the device 100, according to exemplary embodiments.

    [0201] Referring to FIG. 17b, when the device 100 determines that the out-focus status has started at 5:10 a.m., the device 100 may determine, based on information about out-focus probabilities according to time, a time period from 5:10 a.m. to 5:55 a.m., as the period in which the out-focus status is to be maintained.

    [0202] In this case, the device 100 may calculate reliability of the period in which the out-focus status is to be maintained, based on an out-focus probability corresponding to the period in which the out-focus status is to be maintained, and based on a transportation type when the out-focus status has started.

    [0203] For example, based on 75 % that is an average value of out-focus probabilities corresponding to the time period from 5:10 a.m. to 5:55 a.m., and 90 % that is an out-focus probability corresponding to a walk that is the transportation type when the out-focus status has started, the device 100 may determine 80 % as the reliability of the period in which the out-focus status is to be maintained.

    [0204] When the reliability of the period in which the out-focus status is to be maintained is equal to or greater than a threshold value, the device 100 may stop an operation of an application that is executed in the device 100.

    [0205] Referring to FIG. 17c, if the transportation type is changed from the walk to the subway, the device 100 may re-determine, when the transportation type is changed to the subway, the reliability of the period in which the out-focus status is to be maintained.

    [0206] When a location of the device 100 is changed, the device 100 may determine a transportation type, based on the location and a movement speed of the device 100. When the transportation type is changed, the device 100 may re-determine, based on an out-focus probability corresponding to a changed transportation type, the reliability of the period in which the out-focus status is to be maintained.

    [0207] For example, after the operation of the application is stopped, and while the out-focus status is maintained, if the transportation type is changed from the walk to the subway, the device 100 may change the reliability of the period, in which the out-focus status is to be maintained, to 30 %, based on 20 % that is an out-focus probability corresponding to the subway.

    [0208] When the reliability of the period in which the out-focus status is to be maintained is changed to 30 %, the device 100 may resume the stopped operation of the application.

    [0209] Therefore, when the location, the status, or the surrounding environment of the device 100 is changed, the device 100 may improve efficiency of power consumption of a battery of the device 100, based on the changed information.

    [0210] FIG. 18 illustrates a flowchart of a method of stopping an operation of an application executed in the device 100, based on a period in which an out-focus status is to be maintained and reliability of the period, the method being performed by the device 100, according to an exemplary embodiment.

    [0211] In operation S1810, when the device 100 does not receive a user input from a user, the device 100 may determine whether or not an out-focus status in which the user does not use the device 100 has started. Operation S1810 may be described with reference to FIGS. 4a through 5.

    [0212] In operation S1820, when the device 100 determines that the out-focus status has started, the device 100 may determine the period in which the out-focus status is to be maintained and the reliability of the period, based on information about an out-focus probability according to a context of the device 100. Operation S1820 may be described with reference to FIGS. 6 through 17c.

    [0213] In operation S1830, when the period in which the out-focus status is to be maintained and the reliability of the period are equal to or greater than a reference, the device 100 may stop the operation of the application executed in the device 100.

    [0214] When the period in which the out-focus status is to be maintained is equal to or greater than a reference time period, the device 100 may stop the operation of the application executed in the device 100.

    [0215] For example, when a background application that exchanges data with a server is executed in the device 100 without the user input, the device 100 may stop the data exchange between the background application and the server.

    [0216] In this case, if a plurality of background applications are executed in the device 100, the device 100 may sequentially stop background applications which are less used among the plurality of background applications. If the period in which the out-focus status is to be maintained is increased or the reliability of the period is increased, the number of background applications whose operations are stopped by the device 100 may also be increased.

    [0217] For example, in a case where, if a preset event occurs, event information indicating the occurrence of the event is output, even if the event occurs, the device 100 may not output the event information.

    [0218] In this case, the device 100 may not output only event information of an event that is from among a plurality of events and whose importance is equal to or less than a preset reference.

    [0219] The device 100 may determine an event not to be output according to the reliability of the period in which the out-focus status is to be maintained, and may not output only event information of the determined event. The event not to be output according to the reliability of the period in which the out-focus status is to be maintained may be preset in the device 100. For example, when the reliability of the period in which the out-focus status is to be maintained is set high, the device 100 may not output an event with high importance.

    [0220] For example, in a case where an application is updated, without a user input, based on updated data received from a server, the device 100 may not receive the updated data from the server. In this case, the device 100 may not receive updated data for only an application whose number of times of use is equal to or less than a reference.

    [0221] Based on information about an application use pattern of the user, the device 100 may adjust a position, a shape, a size, or a color of an icon of an application according to the context of the device 100, and thus may allow the application, which is frequently used according to the context of the device 100, to be easily found than an application that is not frequently used.

    [0222] FIG. 19 illustrates a table related to a method of controlling an operation of a background application, the method being performed by the device 100 having an out-focus status, according to an exemplary embodiment.

    [0223] Referring to FIG. 19, the device 100 may control data exchange of the background application, based on a period in which the out-focus status is to be maintained.

    [0224] The background application may indicate an application that continuously performs a particular function in the device 100 but whose execution is not recognizable by a user.

    [0225] The background application may be one application or may be a module that forms one application. When the background application is the module that forms one application, the background application may be referred to as a background process or a background service.

    [0226] For example, the background application may include, but is not limited to, a module configured to periodically monitor particular data via a network, a module configured to periodically receive a rich site summary (RSS) feed from an external server via the network and to parse received Extensible Mark-up Language (XML) data, a module in a social network application configured to periodically exchange data with a server, a module in a location tracking application configured to periodically receive data from a GPS satellite, and a module in a motion recognition application configured to periodically sense a motion of the user.

    [0227] The period in which the out-focus status is to be maintained, which is calculated based on the out-focus status according to the context of the device 100, is equal to or greater than 30 minutes, the device 100 may not limit the data exchange of the background application.

    [0228] When the period in which the out-focus status is to be maintained is equal to or greater than 30 minutes, the device 100 may set, as a mode 1, a data exchange control mode of the background application, may not receive data of the background application for 5 minutes, and may repeat an operation of receiving and transmitting data for next 1 minute.

    [0229] When the period in which the out-focus status is to be maintained is equal to or greater than 5 hours, the device 100 may set, as a mode 2, the data exchange control mode of the background application, may not receive data of the background application for 25 minutes, and may repeat an operation of receiving and transmitting data for next 5 minutes.

    [0230] When the device 100 receives a user input during the period in which the out-focus status is supposed to be maintained, and thus the out-focus status is ended, the device 100 may resume the stopped data exchange.

    [0231] Accordingly, as the period in which the out-focus status is to be maintained is increased, the number of times the data exchange is performed per hour is decreased, and thus, the device 100 may improve efficiency of power consumption of a battery of the device 100.

    [0232] FIG. 20 illustrates a table related to a method of stopping an operation of an application, according to reliability of a period in which an out-focus status is to be maintained, the method being performed by the device 100, according to an exemplary embodiment.

    [0233] Referring to FIG. 20, the device 100 may adjust a range of the application whose operation is to be stopped, according to the reliability of the period in which the out-focus status is to be maintained.

    [0234] For example, when the reliability of the period in which the out-focus status is to be maintained is between 60 % through 70 %, the device 100 may stop data exchange or update of an application whose number of times of execution is between 0 % through 20 %. When the reliability of the period in which the out-focus status is to be maintained is between 70 % through 80 %, the device 100 may stop data exchange or update of an application whose number of times of execution is between 0 % through 50 %. When the reliability of the period in which the out-focus status is to be maintained is between 80 % through 99 %, the device 100 may stop data exchange or update of an application whose number of times of execution is between 0 % through 80 %.

    [0235] Accordingly, when the reliability of the period in which the out-focus status is to be maintained is increased, the number of applications whose operations are stopped by the device 100 is also increased, so that the device 100 may improve efficiency of power consumption of a battery of the device 100.

    [0236] In an exemplary embodiment, the device 100 may adjust, according to a state of a battery of the device 100, a range of an application for which data exchange and update are to be limited. For example, when a remaining power of the battery is high, the device 100 may stop data exchange or update of an application whose number of times of execution is within a range of 0 through 20 %. When a remaining power of the battery is middle, the device 100 may stop data exchange or update of an application whose number of times of execution is within a range of 0 through 50 %. When a remaining power of the battery is low, the device 100 may stop data exchange or update of an application whose number of times of execution is within a range of 0 through 80 %. When the battery of the device 100 is being charged, the device 100 may not stop data exchange or update of an application.

    [0237] Accordingly, the lower the remaining power of the battery of the device 100 is, the more the hourly power consumption of the battery is reduced. For example, while a data exchange cycle of an e-mail is set short, if a remaining power of the battery is low, the device 100 may not receive e-mails, and then when the remaining power of the battery becomes equal to or greater than a preset reference, the device 100 may receive e-mails from a mail server.

    [0238] FIG. 21 illustrates a graph related to a method of controlling data exchange of an application, based on out-focus probabilities according to time, the method being performed by the device 100, according to an exemplary embodiment.

    [0239] Referring to FIG. 21, the device 100 may resume a stopped operation of an application before an end of a period in which an out-focus status is to be maintained.

    [0240] For example, when the out-focus status starts, the device 100 may determine the period in which the out-focus status is to be maintained, and may stop data exchange of a background application during the period. After the data exchange of the background application is stopped, the device 100 may calculate a time of the end of the period in which the out-focus status is to be maintained. The device 100 may resume the stopped operation of the application before the end of the period in which the out-focus status is to be maintained. For example, when the time of the end of the period in which the out-focus status is to be maintained is 5:50 p.m., the device 100 may resume the stopped operation of the application at 5:45 p.m.

    [0241] In this case, before the end of the period in which the out-focus status is to be maintained, the device 100 may consider another context such as a location of the device 100, a status of the device 100, or a surrounding environment of the device 100 and thus may determine whether or not to resume the stopped operation of the application.

    [0242] For example, when an out-focus probability corresponding to the location of the device 100, an out-focus probability corresponding to the status of the device 100, and an out-focus probability corresponding to the surrounding environment of the device 100 are considered at 5:45 p.m., if the out-focus probabilities are equal to or greater than a reference, the device 100 may not resume the stopped operation of the application and may stop the operation of the application until the device 100 receives a user input or the location, the status, or the surrounding environment is changed.

    [0243] Based on an application execution probability according to a context of the device 100, the device 100 may resume only an operation of a particular application.

    [0244] For example, after the end of the period in which the out-focus status is to be maintained, if a probability that a game application is to be executed is equal to or greater than a reference, the device 100 may resume only data exchange and updating with respect to the game application.

    [0245] For example, at 5 minutes before the end of the period in which the out-focus status is to be maintained, the device may obtain an execution probability of an application corresponding to the location of the device 100. In a case where an execution probability of the game application is highest at 5 minutes before the end of the period in which the out-focus status is to be maintained, the device 100 may resume only the data exchange and the updating with respect to the game application.

    [0246] FIGS. 22a and 22B illustrate diagrams related to a method of controlling an event when the event occurs during an out-focus status, the method being performed by the device 100, according to an exemplary embodiment.

    [0247] Referring to FIG. 22a, when the event occurs, if a period in which an out-focus status is to be maintained is equal to or greater than a reference time period, or when the event occurs, if a probability of the out-focus status is equal to or greater than a reference value, the device 100 may not display information about the event on a screen.

    [0248] For example, when the device 100 receives push data from a push server in which identification information of the device 100 was registered, the device 100 may generate an event indicating reception of the push data. In this regard, when the event occurs, if the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, or when the event occurs, if a probability of the out-focus status is equal to or greater than the reference value, the device 100 may not display information about the generated event. The push data may include, but is not limited to, a text message, an e-mail, or a chat message.

    [0249] For example, when a user set an alarm or a schedule in the device 100, the device 100 may generate an alarm event or a schedule event at a set time. In this regard, when the alarm event or the schedule event occurs, if the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, or when the alarm event or the schedule event occurs, if a probability of the out-focus status is equal to or greater than the reference value, the device 100 may not output information about the alarm event or the schedule event.

    [0250] Referring to FIG. 22B, during the out-focus status shown in FIG. 22a, if the device 100 receives a user input for cancelling the out-focus status, the device 100 may output event information that was not output.

    [0251] The user input for cancelling the out-focus status may correspond to an input for touching a screen of the device 100 or pressing a preset button key of the device 100 in a lock status of the device 100.

    [0252] When the user input for cancelling the out-focus status is received, the device 100 may output the event information by using an output method that was preset in correspondence to an event. For example, when a method of outputting a text message is set in such a manner that content of the text message is displayed on the screen and a vibration notice is output to indicate reception of the text message, the device 100 may display content of a message on the screen and may generate a vibration.

    [0253] Accordingly, during the out-focus status, when the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, or when the event occurs, if the probability of the out-focus status is equal to or greater than the reference value, the device 100 may not output the event information and thus may increase efficiency of power consumption of a battery of the device 100.

    [0254] FIG. 23 illustrates the device 100 in relation to a method of displaying identification information of an application, based on an execution probability of the application according to a context of the device 100, the method being performed by the device 100, according to an exemplary embodiment.

    [0255] Referring to FIG. 23, the device 100 may display a plurality of pieces of identification information of applications, based on execution probabilities of the applications according to the context, in order to allow applications having higher execution probabilities to be more easily accessible.

    [0256] The device 100 may allow the applications having higher execution probabilities to be displayed upward or leftward on the screen. For example, when execution probabilities of a plurality of applications installed in the device 100 are high in an order of a web browser 2310, a social networking service (SNS) application 2320, a game application 2330, a text application 2340, and a bank application 2350, the device 100 may display icons on an edge screen, which is always accessible to a user, in an order of the web browser 2310, the SNS application 2320, the game application 2330, the text application 2340, and the bank application 2350.

    [0257] The device 100 may allow identification information of an application having a high execution probability to be displayed with a high brightness or a high chroma. The device 100 may allow the identification information of the application having the high execution probability to be further largely displayed. The device 100 may allow the identification information of the application having the high execution probability to be displayed with an intuitional form, and may allow identification information of an application having a low execution probability to be displayed with an unusual form.

    [0258] When a status value of the context of the device 100 is changed, the device 100 may obtain execution probabilities of applications corresponding to a changed status value, and may display the applications, based on the obtained execution probabilities of the applications, so that the higher the execution probabilities are, the easier the accessibility with respect to the applications is.

    [0259] For example, when a location of the device 100 is changed, the device 100 may obtain execution probabilities of the applications at a changed location, and may display the applications, based on the obtained execution probabilities of the applications, so that the higher the execution probabilities are, the easier the accessibility with respect to the applications is.

    [0260] FIGS. 24a and 24b illustrate the device 100 in relation to a method of providing a user interface for controlling an operation of an application based on a use pattern of a user, the method being performed by the device 100, according to exemplary embodiments.

    [0261] Referring to FIG. 24a, the device 100 may provide a menu for controlling the operation of the application based on the use pattern of the user.

    [0262] When the device 100 receives a user input for selecting the menu for controlling the operation of the application based on the use pattern of the user, the device 100 may display a check-box button 2410 to select whether to execute a function for controlling the operation of the application based on the use pattern of the user.

    [0263] Referring to FIG. 24b, when the device 100 receives a user input for selecting the check-box button 2410 shown in FIG. 24a, the device 100 may display a selection window 2420 including a description indicating that the operation of the application may be limited.

    [0264] When the device 100 receives a user input for selecting a confirm button on the selection window 2420, the device 100 may stop the operation of the application based on the use pattern of the user, and thus may increase efficiency of power consumption of a battery of the device 100.

    [0265] FIG. 25 illustrates a block diagram of the device 100, according to an exemplary embodiment.

    [0266] Referring to FIG. 25, the device 100 may include a user input unit 145, a communicator 130, a display unit 110, and a controller 170. However, not all elements shown in FIG. 25 are necessary elements. That is, the device 100 may be embodied with more or less elements than the elements shown in FIG. 25.

    [0267] The user input unit 145 may receive an input from a user.

    [0268] The user input unit 145 may receive a user input from the user after an operation of an application is stopped during an out-focus status.

    [0269] The communicator 130 may exchange data with a peripheral device or a server.

    [0270] The communicator 130 may exchange data of a background application with the server. Accordingly, even if a user input is not received, the communicator 130 may exchange data with respect to an application with the server.

    [0271] The communicator 130 may receive updated data with respect to the application from the server. Therefore, even if a user input is not received, the communicator 130 may receive the updated data with respect to the application from the server.

    [0272] The communicator 130 may receive a call connection request from a telephone network server.

    [0273] The display unit 110 may display information.

    [0274] When the call connection request is received, the display unit 110 may output information indicating reception of the call connection request.

    [0275] The controller 170 may control a configuration of the device 100 including the user input unit 145, the communicator 130, and the display unit 110.

    [0276] When a user input is not received, the controller 170 may determine whether an out-focus status in which the user does not use the device 100 has started.

    [0277] For example, when the user input is not received during at least a preset time period, the controller 170 may inactivate the display unit 110. When the display unit 110 is inactivated, the controller 170 may determine that the out-focus status has started.

    [0278] For example, when a user input for confirming the call connection request in response to output event information is not received, the controller 170 may determine that the out-focus status has started.

    [0279] When the controller 170 determines that the out-focus status has started, the controller 170 may determine a period in which the out-focus status is to be maintained, based on a probability of the out-focus status according to a context of the device 100.

    [0280] For example, the controller 170 may determine the period in which the out-focus status is to be maintained, based on a value of a probability of the out-focus status corresponding to a time period after the out-focus status has started, wherein the value of the probability is from among information about out-focus probabilities according to time.

    [0281] When the determined period in which the out-focus status is to be maintained is equal to or greater than a reference time period, the controller 170 may stop an operation of an application executed in the device 100.

    [0282] The controller 170 may determine reliability of the period in which the out-focus status is to be maintained, based on information about a device use pattern of the user, and when the reliability of the period in which the out-focus status is to be maintained is equal to or greater than a reference, the controller 170 may stop the operation of the application executed in the device 100.

    [0283] For example, the controller 170 may determine the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a location of the device 100 when the out-focus status has started, wherein the probability value is from among information about probabilities of the out-focus status according to locations of the device 100.

    [0284] As another example, the controller 170 may determine the reliability of the period in which the out-focus status is to be maintained, based on a probability value corresponding to a status of the device 100 when the out-focus status has started, wherein the probability value is from among information about probabilities of the out-focus status according to statuses of the device 100.

    [0285] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller 170 may control the communicator 130 to stop data exchange of the background application.

    [0286] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller 170 may control the communicator 130 not to receive updated data with respect to the application from the server.

    [0287] When the period in which the out-focus status is to be maintained is equal to or greater than the reference time period, even if information about an event is received from the server, the controller 170 may not request the display unit 110 to output information indicating reception of the event.

    [0288] When a user input is received from the user, the controller 170 may resume the stopped operation of the application.

    [0289] The device 100 may include an output unit. The output unit may output information to a user. For example, the output unit may include the display unit 110 or a speaker 160 shown in FIG. 26.

    [0290] FIG. 26 illustrates a block diagram of the device 100, according to another exemplary embodiment.

    [0291] A configuration of the device 100 may be applied to various types of a device such as a mobile phone, a tablet PC, a personal digital assistant (PDA), an MP3 player, a kiosk, an electronic photoframe, a navigation device, a digital television (TV), a smart watch, a wristwatch, or a wearable device such as smart glasses, head-mounted display (HMD), or the like.

    [0292] Referring to FIG. 26, the device 100 may include the communicator 130, the user input unit 145, the display unit 110, and the controller 170, and may further include at least one of a memory 120, a GPS chip 125, a video processor 135, an audio processor 140, a microphone 150, an image-capturing unit 155, a speaker 160, and a motion detector 165.

    [0293] The display unit 110 may include a display panel 111 and a controller (not shown) that controls the display panel 111. The display panel 111 may be embodied as various displays including a liquid crystal display (LCD) display, an organic light-emitting diode (OLED) display, an active matrix OLED (AMOLED) display, a plasma display panel (PDP), or the like. The display panel 111 may be formed to be flexible, transparent, and/or wearable. The display panel 111 may be combined with a touch panel 147 of the user input unit 145, and thus may be provided as a touchscreen (not shown). For example, the touchscreen may include an integrated module having a stack structure containing the display panel 111 and the touch panel 147.

    [0294] The memory 120 may include at least one of an internal memory (not shown) and an external memory (not shown).

    [0295] The internal memory may include at least one of a volatile memory (e.g., a dynamic random-access memory (DRAM), a static RAM (SRAM), a synchronous dynamic RAM (SDRAM), etc.), a non-volatile memory (e.g., a one-time programmable read-only memory (OTPROM), a programmable ROM (PROM), an erasable and programmable ROM (EPROM), an electrically erasable and programmable ROM (EEPROM), a mask ROM, a flash ROM, etc.), a hard disk drive (HDD), and a solid-state drive (SSD). According to the present exemplary embodiment, the controller 170 may load a command or data, which is received from at least one of the non-volatile memory and another element, to the volatile memory, and may process the command or the data. Also, the controller 170 may store, in the non-volatile memory, data that is received from or is generated by another element.

    [0296] The external memory may include at least one of a compact flash (CF) memory, a secure digital (SD) memory, a micro secure digital (micro-SD) memory, a mini secure digital (mini-SD) memory, an extreme digital (xD) memory, and a memory stick.

    [0297] The memory 120 may store various programs and data used in operations of the device 100. For example, the memory 120 may temporarily or semi-permanently store a portion of contents to be displayed on a lock screen.

    [0298] The controller 170 may control the display unit 110 to display a portion of contents which is stored in the memory 120. In other words, the controller 170 may display, on the display unit 110, the portion of the contents which is stored in the memory 120. Alternatively, when a user's gesture is performed in a region of the display unit 110, the controller 170 may perform a control operation that corresponds to the user's gesture.

    [0299] The controller 170 may include at least one of a Random Access Memory (RAM) 171, a read-only memory (ROM) 172, a central processing unit (CPU) 173, a Graphics Processing Unit (GPU) 174, and a bus 175. The RAM 171, the ROM 172, the CPU 173, and the GPU 174 may be connected to each other via the bus 175.

    [0300] The CPU 173 accesses the memory 120, and performs a booting operation by using an operating system (O/S) stored in the memory 120. Also, the CPU 173 performs various operations by using the various programs, a plurality of items of content, a plurality of items of data, etc. which are stored in the memory 120.

    [0301] The ROM 172 stores a command set for booting up a system. For example, when a turn-on command is input to the device 100, and power is supplied to the device 100, the CPU 173 may copy the operating system stored in the memory 120 to the RAM 171, according to the command stored in the ROM 172, may execute the operating system, and thus may boot up the system. When the booting operation is completed, the CPU 173 copies the various programs stored in the memory 120 to the RAM 171, and performs the various operations by executing the programs copied to the RAM 171. When the device 100 is booted up, the GPU 174 displays a user interface screen in a region of the display unit 110. In more detail, the GPU 174 may generate a screen that displays an electronic document including various objects such as content, an icon, a menu, or the like. The GPU 174 calculates coordinate values of the objects that are to be displayed according to a layout of the user interface screen, and calculates attribute values of shapes, sizes, or colors of the objects. Then, the GPU 174 may generate user interface screens with various layouts including the objects based on the calculated attribute values. The user interface screen generated by the GPU 174 may be provided to the display unit 110 and thus may be displayed in areas of the display unit 110.

    [0302] The GPS chip 125 may receive a GPS signal from a GPS satellite and may calculate a current position of the device 100. In a case where a navigation program is used or a current position of the user is required, the controller 170 may calculate a position of the user by using the GPS chip 125.

    [0303] The communicator 130 may communicate with various external devices according to various types of communication methods. The communicator 130 may include at least one of a Wi-Fi chip 131, a Bluetooth chip 132, a wireless communication chip 133, and a Near field communication (NFC) chip 134. The controller 170 may communicate with the various external devices by using the communicator 130.

    [0304] The Wi-Fi chip 131 and the Bluetooth chip 132 may perform communication by using Wi-Fi and Bluetooth, respectively. If the Wi-Fi chip 131 or the Bluetooth chip 132 is used, the Wi-Fi chip 131 or the Bluetooth chip 132 may first transmit and receive various types of connection information including a service set identification (SSID), a session key, or the like, may establish a connection for communication by using the connection information, and then may transmit and receive various types of information. The wireless communication chip 133 may indicate a chip that performs communication according to various communication standards such as the Institute of Electrical and Electronics Engineers (IEEE), ZigBee, 3rd generation (3G), 3rd Generation Partnership Project (3GPP), LTE, or the like. The NFC chip 134 indicates a chip that operates in using NFC by using a 13.56 MHz band from among various radio frequency-identification (RF-ID) frequency bands such as 135 kHz, 13.56 MHz, 433 MHz, 860 through 960 MHz, 2.45 GHz, or the like.

    [0305] The video processor 135 may process video data included in content received by using the communicator 130 or may process video data included in content stored in the memory 120. The video processor 135 may perform various image processing such as decoding, scaling, noise filtering, frame rate conversion, resolution conversion, or the like on the video data.

    [0306] The audio processor 140 may process audio data included in content received by using the communicator 130 or may process audio data included in content stored in the memory 120. The audio processor 140 may perform various processing such as decoding, amplification, noise filtering, or the like on the audio data.

    [0307] When a reproducing program for multimedia content is executed, the controller 170 may reproduce the multimedia content by driving the video processor 135 and the audio processor 140. The speaker 160 may output audio data generated in the audio processor 140.

    [0308] The user input unit 145 may receive an input of various instructions from a user. The user input unit 145 may include at least one of a key 146, a touch panel 147, and a pen recognizing panel 148.

    [0309] The key 146 may be of various types such as a mechanical button, a wheel, or the like that may be formed in a front portion, a side portion, a rear portion, etc., of an external surface of a body of the device 100.

    [0310] The touch panel 147 may sense a touch input by the user and may output a value of a touch event that corresponds to a signal generated by the sensed touch input. When the touch panel 147 is combined with the display panel 111 and thus is formed as a touchscreen, the touchscreen may be configured as a capacitive touchscreen, a resistive touchscreen, or a piezoelectric touchscreen by using various types of touch sensors. The capacitive touchscreen may calculate touch coordinates by sensing a small amount of electricity generated when a body part of the user touches the surface of the capacitive touchscreen, which is coated with a dielectric material. The resistive touchscreen may include two embedded electrode plates and may calculate touch coordinates by sensing a flow of current that occurs when the user touches the resistive touchscreen which causes upper and lower plates of a touched point to contact each other. The touch event that occurs on the touchscreen may be mainly generated by a finger of a person but may also be generated by an object formed of a conductive material capable of changing capacitance.

    [0311] The pen recognizing panel 148 may sense a proximity input or a touch input of a touch pen (e.g., a stylus pen or a digitizer pen) which is performed by a user, and may output a sensed pen proximity event or a sensed pen touch event. The pen recognizing panel 148 may be an electromagnetic resonance (EMR)-type pen recognizing panel, and may sense the touch input or the proximity input according to changes in a strength of an electromagnetic field, which occur when the touch pen approaches or touches the touchscreen. In more detail, the pen recognizing panel 148 may include an electromagnetic induction coil sensor (not shown) having a grid structure, and an electric signal processor (not shown) for sequentially providing an alternating current (AC) signal having a predetermined frequency to each loop coil of the electromagnetic induction coil sensor. When a pen having an internal resonance circuit is positioned near a loop coil of the pen recognizing panel 148, a magnetic field transmitted from the loop coil generates a current in the resonance circuit in the pen, based on mutual electrostatic induction. Due to the current, an induction field is generated from a coil forming the resonance circuit in the pen, and the pen recognizing panel 148 detects the induction field from the loop coil capable of receiving a signal, and thus senses the touch input or the proximity input by the pen. The pen recognizing panel 148 may be arranged to occupy a preset area below the display panel 111, e.g., may have a size capable of covering a display region of the display panel 111.

    [0312] The microphone 150 may receive an input of a user's voice or other sound and may convert the user's voice or other sound to audio data. The controller 170 may use the user's voice, which is input via the microphone 150, in a call-related operation or may convert the user's voice to the audio data and may store the audio data in the memory 120.

    [0313] The image-capturing unit 155 may capture a still image or a moving picture according to a control by the user. The image-capturing unit 155 may be plural in number and include a front camera, a rear camera, or the like.

    [0314] If the image-capturing unit 155 and the microphone 150 are formed, the controller 170 may perform a control operation according to a user's voice input via the microphone 150 or a user's motion recognized by the image-capturing unit 155. For example, the device 100 may operate in a motion control mode or a voice control mode. If the device 100 operates in the motion control mode, the controller 170 may activate the image-capturing unit 155 and may capture an image of the user, may trace a change in motions of the user, and may perform a control operation corresponding thereto. If the device 100 operates in the voice control mode (i.e., a voice recognition mode), the controller 170 may analyze a user's voice input via the microphone 150, and may perform a control operation according to the analyzed user's voice.

    [0315] The motion detector 165 may detect movement of a body of the device 100. The device 100 may rotate or may tilt in various directions. Here, the motion detector 165 may detect a movement characteristic such as a rotation direction, a rotation angle, a tilted angle, or the like by using at least one of various sensors including a magnetic sensor, a gyroscope sensor, an acceleration sensor, etc.

    [0316] Although not illustrated in FIG. 26, the present exemplary embodiment may further include a universal serial bus (USB) port for connecting the device 100 and a USB connector, various external input ports including a headset, a mouse, a LAN, etc. for connection with various external terminals, a digital multimedia broadcasting (DMB) chip for receiving and processing a DMB signal, various sensors, or the like.

    [0317] Names of the elements of the device 100 may be changed. Also, the device 100 according to the present exemplary embodiment may be embodied by including at least one of the elements, or may be embodied with more or less elements than the elements.

    [0318] The one or more exemplary embodiments may be embodied as computer readable code/instructions on a recording medium, e.g., a program module to be executed in computers, which include computer-readable commands. The computer storage medium may include any usable medium that may be accessed by computers, volatile and non-volatile medium, and detachable and non-detachable medium. Also, the computer storage medium may include a computer storage medium and a communication medium. The computer storage medium includes all volatile and non-volatile media, and detachable and non-detachable media which are technically implemented to store information including computer readable commands, data structures, program modules or other data. The communication medium includes computer-readable commands, a data structure, a program module, other data as modulation-type data signals such as carrier signals, or other transmission mechanism, and includes other information transmission mediums.

    [0319] It should be understood that the exemplary embodiments described herein should be considered in a descriptive sense only and not for purposes of limitation. Descriptions of features or aspects within each embodiment should typically be considered as available for other similar features or aspects in other embodiments. For example, configuring elements that are singular forms may be executed in a distributed fashion, and also, configuring elements that are distributed may be combined and then executed.

    [0320] While one or more exemplary embodiments have been described with reference to the figures, it will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the scope as defined by the following claims.


    Claims

    1. A device (100) comprising:

    a user input unit (145) configured to receive a user input from a user;

    an output unit configured to output information, based on the user input; and

    a controller (170) configured to:

    determine, when the user input is not received, whether an out-focus status in which the user does not use the device (100) has started,

    characterised in that the controller is further configured to determine, when it is determined that the out-focus status has started, an expected period in which the out-focus status is to be maintained since when the out-focus status has started, based on information about a probability of the out-focus status according to a context of the device (100), and

    in response to the expected period in which the out-focus status is to be maintained is equal to or greater than a reference time period, stop an operation of an application executed in the device (100) from when the out-focus status has started.


     
    2. The device (100) of claim 1, wherein the out-focus status in which the user does not use the device (100) indicates at least one of a status in which the output unit does not output the information or a status in which the user does not receive the information output from the output unit.
     
    3. The device (100) of claim 1, wherein the context of the device (100) comprises at least one of a time, a location of the device (100), a status of the device (100), or an environment surrounding the location of the device (100).
     
    4. The device (100) of claim 1,
    wherein, after the application is stopped, the user input unit (145) is further configured to receive the user input from the user, and
    wherein, when the user input is received from the user, the controller (170) is further configured to resume the stopped application.
     
    5. The device (100) of claim 1,
    wherein the output unit comprises a display unit (110) configured to display the information,
    wherein, when the user input is not received for a preset time period, the controller (170) is further configured to inactivate the display unit (110), and
    wherein, when the display unit (110) is inactivated, the controller (170) is further configured to determine that the out-focus status has started.
     
    6. The device (100) of claim 1, further comprising:

    a communicator (130) configured to receive a call connection request from a server,

    wherein, when the call connection request is received, the output unit is further configured to output information indicating reception of the call connection request, and

    wherein, when a user input for confirming the call connection request in response to the output information is not received, the controller (170) is further configured to determine that the out-focus status has started.


     
    7. The device (100) of claim 6, wherein the controller (170) is further configured to:

    determine the expected period in which the out-focus status is to be maintained, based on a value of a probability of the out-focus status corresponding to a time period after the out-focus status has started,

    wherein the value of the probability is obtained from among information about probabilities of the out-focus status according to time.


     
    8. The device (100) of claim 1,
    wherein the controller (170) is further configured to determine, by calculation, a reliability of the expected period in which the out-focus status is to be maintained based on information about the probability of the out-focus status according to the context of the device (100) by averaging values of out-focus probabilities corresponding to a particular time period, and
    wherein, when the reliability of the expected period in which the out-focus status is to be maintained is equal to or greater than a reference, the controller (170) is further configured to stop the application executed in the device (100).
     
    9. The device (100) of claim 8,
    wherein the information about the probability of the out-focus status according to the context of the device (100) comprises information about probabilities of the out-focus status according to locations of the device (100),
    wherein the controller (170) is further configured to determine the reliability of the expected period in which the out-focus status is to be maintained based on a probability value corresponding to a location of the device (100) when the out-focus status has started, and
    wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the locations of the device (100).
     
    10. The device (100) of claim 8,
    wherein the information about the probability of the out-focus status according to the context of the device (100) comprises information about probabilities of the out-focus status according to statuses of the device (100),
    wherein the controller (170) is further configured to determine the reliability of the expected period in which the out-focus status is to be maintained based on a probability value corresponding to a status of the device (100) when the out-focus status has started, and
    wherein the probability value is obtained from among the information about the probabilities of the out-focus status according to the statuses of the device (100).
     
    11. The device (100) of claim 1, further comprising:

    a communicator (130) configured to exchange data about the application with the server, even if the user input is not received,

    wherein, when the expected period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller (170) is further configured to control the communicator (130) to stop exchanging the data.


     
    12. The device (100) of claim 1, wherein, even if information about an event is received from a server, the controller (170) is further configured not to request the communicator (130) to output information indicating reception of the event when the expected period in which the out-focus status is to be maintained is equal to or greater than the reference time period.
     
    13. The device (100) of claim 1, further comprising:

    a communicator (130) configured to receive updated data with respect to the application from a server even if the user input is not received,

    wherein, when the expected period in which the out-focus status is to be maintained is equal to or greater than the reference time period, the controller (170) is further configured to control the communicator (130) not to receive the updated data from the server.


     
    14. A method of managing power comprising:

    determining, when a user input is not received from a user, whether an out-focus status in which the user does not use a device (100) has started;

    characterised by determining, when it is determined that the out-focus status has started, an expected period in which the out-focus status is to be maintained since when the out-focus status has started, based on information about a probability of the out-focus status according to a context of the device (100); and

    in response to the expected period in which the out-focus status is to be maintained is equal to or greater than a reference time period, stop an operation of an application executed in the device (100) from when the out-focus status has started.


     
    15. A non-transitory computer-readable recording medium having recorded thereon a program for executing the method according to claim 14.
     


    Ansprüche

    1. Vorrichtung (100), umfassend:

    eine Benutzereingabeeinheit (145), die dazu ausgestaltet ist, eine Benutzereingabe von einem Benutzer zu empfangen;

    eine Ausgabeeinheit, die dazu ausgestaltet ist, basierend auf der Benutzereingabe Informationen auszugeben; und

    eine Steuerung (170), zu Folgendem ausgestaltet ist:

    Bestimmen - wenn die Benutzereingabe nicht empfangen wird - ob ein Nicht-im-Fokus-Status, in dem der Benutzer die Vorrichtung (100) nicht verwendet, begonnen hat,

    dadurch gekennzeichnet, dass die Steuerung ferner für Folgendes ausgestaltet ist:

    Bestimmen - wenn bestimmt wird, dass der Nicht-im-Fokus-Status begonnen hat - eines erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, ab dem Beginn des Nicht-im-Fokus-Status basierend auf Informationen über eine Wahrscheinlichkeit des Nicht-im-Fokus-Status gemäß einem Kontext der Vorrichtung (100) und

    in Reaktion darauf, dass der erwartete Zeitraum, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder länger als ein Referenzzeitraum ist, Stoppen eines Betriebs einer Anwendung, die in der Vorrichtung (100) ausgeführt wird, ab dem Beginn des Nicht-im-Fokus-Status.


     
    2. Vorrichtung (100) nach Anspruch 1, wobei der Nicht-im-Fokus-Status, in dem der Benutzer die Vorrichtung (100) nicht verwendet, wenigstens eines aus einem Status, in dem die Ausgabeeinheit die Informationen nicht ausgibt, oder einem Status, in dem der Benutzer die von der Ausgabeeinheit ausgegebenen Informationen nicht empfängt, anzeigt.
     
    3. Vorrichtung (100) nach Anspruch 1, wobei der Kontext der Vorrichtung (100) wenigstens eines aus einer Zeit, einem Standort der Vorrichtung (100), einem Status der Vorrichtung (100) oder einem Umfeld, das den Standort der Vorrichtung (100) umgibt, umfasst.
     
    4. Vorrichtung (100) nach Anspruch 1,
    wobei, nachdem die Anwendung gestoppt wird, die Benutzereingabeeinheit (145) ferner dazu ausgestaltet ist, die Benutzereingabe von dem Benutzer zu empfangen, und
    wobei, wenn die Benutzereingabe von dem Benutzer empfangen wird, die Steuerung (170) ferner dazu ausgestaltet ist, die gestoppte Anwendung wieder aufzunehmen.
     
    5. Vorrichtung (100) nach Anspruch 1,
    wobei die Ausgabeeinheit eine Anzeigeeinheit (110) umfasst, die dazu ausgestaltet ist, die Informationen anzuzeigen,
    wobei, wenn die Benutzereingabe über einen voreingestellten Zeitraum nicht empfangen wird, die Steuerung (170) ferner dazu ausgestaltet ist, die Anzeigeeinheit (110) zu inaktivieren, und
    wobei, wenn die Anzeigeeinheit (110) inaktiviert wird, die Steuerung (170) ferner dazu ausgestaltet ist zu bestimmen, dass der Nicht-im-Fokus-Status begonnen hat.
     
    6. Vorrichtung (100) nach Anspruch 1, ferner umfassend:

    eine Kommunikationseinrichtung (130), die dazu ausgestaltet ist, eine Anrufverbindungsanforderung von einem Server zu empfangen,

    wobei, wenn die Anrufverbindungsanforderung empfangen wird, die Ausgabeeinheit ferner dazu ausgestaltet ist, Informationen auszugeben, die einen Empfang der Anrufverbindungsanforderung anzeigen, und

    wobei, wenn eine Benutzereingabe zum Bestätigen der Anrufverbindungsanforderung in Reaktion auf die ausgegebenen Informationen nicht empfangen wird, die Steuerung (170) ferner dazu ausgestaltet ist zu bestimmen, dass der Nicht-im-Fokus-Status begonnen hat.


     
    7. Vorrichtung (100) nach Anspruch 6, wobei die Steuerung (170) ferner zu Folgendem ausgestaltet ist:

    Bestimmen des erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, basierend auf einem Wert einer Wahrscheinlichkeit des Nicht-im-Fokus-Status, der einem Zeitraum nach dem Beginn des Nicht-im-Fokus-Status entspricht,

    wobei der Wert der Wahrscheinlichkeit aus Informationen über Wahrscheinlichkeiten des Nicht-im-Fokus-Status gemäß der Zeit erhalten wird.


     
    8. Vorrichtung (100) nach Anspruch 1,
    wobei die Steuerung (170) ferner dazu ausgestaltet ist, durch Berechnung - basierend auf Informationen über die Wahrscheinlichkeit des Nicht-im-Fokus-Status gemäß dem Kontext der Vorrichtung (100) durch Mitteln von Werten von Nicht-im-Fokus-Wahrscheinlichkeiten, die einem bestimmten Zeitraum entsprechen - eine Zuverlässigkeit des erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, zu bestimmen, und
    wobei, wenn die Zuverlässigkeit des erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder höher als eine Referenz ist, die Steuerung (170) ferner dazu ausgestaltet ist, die in der Vorrichtung (100) ausgeführte Anwendung zu stoppen.
     
    9. Vorrichtung (100) nach Anspruch 8,
    wobei die Informationen über die Wahrscheinlichkeit des Nicht-im-Fokus-Status gemäß dem Kontext der Vorrichtung (100) Informationen über Wahrscheinlichkeiten des Nicht-im-Fokus-Status gemäß Standorten der Vorrichtung (100) umfasst,
    wobei die Steuerung (170) ferner dazu ausgestaltet ist, die Zuverlässigkeit des erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, basierend auf einem Wahrscheinlichkeitswert zu bestimmen, der einem Standort der Vorrichtung (100) zum Beginn des Nicht-im-Fokus-Status entspricht, und
    wobei der Wahrscheinlichkeitswert aus den Informationen über die Wahrscheinlichkeiten des Nicht-im-Fokus-Status gemäß den Standorten der Vorrichtung (100) erhalten wird.
     
    10.  Vorrichtung (100) nach Anspruch 8,
    wobei die Informationen über die Wahrscheinlichkeit des Nicht-im-Fokus-Status gemäß dem Kontext der Vorrichtung (100) Informationen über Wahrscheinlichkeiten des Nicht-im-Fokus-Status gemäß Status der Vorrichtung (100) umfasst,
    wobei die Steuerung (170) ferner dazu ausgestaltet ist, die Zuverlässigkeit des erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, basierend auf einem Wahrscheinlichkeitswert zu bestimmen, der einem Status der Vorrichtung (100) zum Beginn des Nicht-im-Fokus-Status entspricht, und
    wobei der Wahrscheinlichkeitswert aus den Informationen über die Wahrscheinlichkeiten des Nicht-im-Fokus-Status gemäß den Status der Vorrichtung (100) erhalten wird.
     
    11. Vorrichtung (100) nach Anspruch 1, ferner umfassend:

    eine Kommunikationseinrichtung (130), die dazu ausgestaltet ist, auch dann Daten über die Anwendung mit dem Server auszutauschen, wenn die Benutzereingabe nicht empfangen wird,

    wobei, wenn der erwartete Zeitraum, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder länger als der Referenzzeitraum ist, die Steuerung (170) ferner dazu ausgestaltet ist, die Kommunikationseinrichtung (130) dahingehend zu steuern, das Austauschen der Daten zu stoppen.


     
    12. Vorrichtung (100) nach Anspruch 1, wobei, auch wenn Informationen über ein Ereignis von einem Server empfangen werden, die Steuerung (170) ferner dazu ausgestaltet ist, die Kommunikationseinrichtung (130) nicht aufzufordern, Informationen auszugeben, die einen Empfang des Ereignisses anzeigen, wenn der erwartete Zeitraum, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder länger als der Referenzzeitraum ist.
     
    13. Vorrichtung (100) nach Anspruch 1, ferner umfassend:

    eine Kommunikationseinrichtung (130), die dazu ausgestaltet ist, auch wenn die Benutzereingabe nicht empfangen wird, aktualisierte Daten bezüglich der Anwendung von einem Server zu empfangen,

    wobei, wenn der erwartete Zeitraum, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder länger als der Referenzzeitraum ist, die Steuerung (170) ferner dazu ausgestaltet ist, die Kommunikationseinrichtung (130) dahingehend zu steuern, die aktualisierten Daten nicht von dem Server zu empfangen.


     
    14. Verfahren zum Energiemanagement, umfassend:

    Bestimmen - wenn eine Benutzereingabe nicht von einem Benutzer empfangen wird - ob ein Nicht-im-Fokus-Status, in dem der Benutzer eine Vorrichtung (100) nicht verwendet, begonnen hat;

    gekennzeichnet durch

    Bestimmen - wenn bestimmt wird, dass der Nicht-im-Fokus-Status begonnen hat - eines erwarteten Zeitraums, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, ab dem Beginn des Nicht-im-Fokus-Status basierend auf Informationen über eine Wahrscheinlichkeit des Nicht-im-Fokus-Status gemäß einem Kontext der Vorrichtung (100); und

    in Reaktion darauf, dass der erwartete Zeitraum, in dem der Nicht-im-Fokus-Status aufrechtzuerhalten ist, gleich oder länger als ein Referenzzeitraum ist, Stoppen eines Betriebs einer Anwendung, die in der Vorrichtung (100) ausgeführt wird, ab dem Beginn des Nicht-im-Fokus-Status.


     
    15. Nichtflüchtiges computerlesbares Aufzeichnungsmedium, auf dem ein Programm zum Ausführen des Verfahrens nach Anspruch 14 aufgezeichnet ist.
     


    Revendications

    1. Dispositif (100) comprenant :

    une unité d'entrée d'utilisateur (145) conçue pour recevoir une entrée d'utilisateur d'un utilisateur ;

    une unité de sortie conçue pour sortir des informations, basé sur l'entrée d'utilisateur ; et

    un contrôleur (170) conçu pour :

    déterminer, lorsque l'entrée d'utilisateur n'est pas reçue, si un statut d'absence pour lequel l'utilisateur n'utilise pas le dispositif (100) a commencé,

    caractérisé en ce que le contrôleur est conçu en outre pour

    déterminer, lorsqu'il a été déterminé que le statut d'absence a commencé, une période prévue pour laquelle le statut d'absence doit être maintenu depuis l'instant où le statut d'absence a commencé, basé sur des informations relatives à une probabilité du statut d'absence en fonction d'un contexte du dispositif (100), et

    arrêter une opération d'une application exécutée sur le dispositif (100) à partir de l'instant où le statut d'absence a commencé, en réponse au fait que la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à un intervalle de temps de référence.


     
    2. Dispositif (100) selon la revendication 1, le statut d'absence pour lequel l'utilisateur n'utilise pas le dispositif (100) indiquant au moins un statut parmi un statut pour lequel l'unité de sortie ne sort pas les informations et un statut pour lequel l'utilisateur ne reçoit pas les informations sorties par l'unité de sortie.
     
    3. Dispositif (100) selon la revendication 1, le contexte du dispositif (100) comprenant au moins un élément parmi un instant, un emplacement du dispositif (100), un statut du dispositif (100) et un environnement autour de l'emplacement du dispositif (100).
     
    4. Dispositif (100) selon la revendication 1,
    l'unité d'entrée d'utilisateur (145) étant conçue en outre pour recevoir l'entrée d'utilisateur de l'utilisateur après que l'application est arrêtée, et
    le contrôleur (170) étant en outre conçu pour relancer l'application arrêtée, lorsque l'entrée de l'utilisateur est reçue de l'utilisateur.
     
    5.  Dispositif (100) selon la revendication 1,
    l'unité de sortie comprenant une unité d'affichage (110) conçue pour afficher les informations,
    le contrôleur (170) étant en outre conçu pour désactiver l'unité d'affichage (110), lorsque l'entrée d'utilisateur n'est pas reçue pendant un intervalle de temps prédéfini, et
    le contrôleur (170) étant en outre conçu pour déterminer que le statut d'absence a commencé, lorsque l'unité d'affichage (110) est désactivée.
     
    6. Dispositif (100) selon la revendication 1, comprenant en outre :

    un communicateur (130) conçu pour recevoir une demande de connexion d'appel par un serveur,

    l'unité de sortie étant en outre conçue pour sortir des informations indiquant la réception de la demande de connexion d'appel, lorsque la demande de connexion d'appel est reçue, et

    le contrôleur (170) étant en outre conçu pour déterminer que le statut d'absence a commencé, lorsqu'une entrée d'utilisateur pour confirmer la demande de connexion d'appel en réponse aux informations de sortie n'est pas reçue.


     
    7. Dispositif (100) selon la revendication 6, le contrôleur (170) étant configuré en outre pour :
    déterminer la période prévue pour laquelle le statut d'absence doit être maintenu, basé sur une valeur d'une probabilité du statut d'absence correspondant à un intervalle de temps après que le statut d'absence a commencé,
    la valeur de la probabilité étant obtenue à l'aide d'informations sur les probabilités du statut d'absence en fonction du temps.
     
    8. Dispositif (100) selon la revendication 1,
    le contrôleur (170) étant en outre conçu pour déterminer, par le calcul, une fiabilité de la période prévue pour laquelle le statut d'absence doit être maintenu, basé sur les informations relatives à la probabilité du statut d'absence en fonction du contexte du dispositif (100), en faisant la moyenne des valeurs des probabilités d'absence correspondant à un intervalle de temps particulier, et le contrôleur (170) étant en outre conçu pour arrêter l'application exécutée sur le dispositif (100), lorsque la fiabilité de la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à une référence.
     
    9. Dispositif (100) selon la revendication 8,
    les informations relatives à la probabilité du statut d'absence en fonction du contexte du dispositif (100) comprenant des informations sur les probabilités du statut d'absence en fonction des emplacements du dispositif (100),
    le contrôleur (170) étant en outre conçu pour déterminer la fiabilité de la période prévue pour laquelle le statut d'absence doit être maintenu, basé sur une valeur de probabilité correspondant à un emplacement du dispositif (100), lorsque le statut d'absence a commencé, et la valeur de la probabilité étant obtenue à l'aide d'informations sur les probabilités du statut d'absence en fonction des emplacements du dispositif (100).
     
    10. Dispositif (100) selon la revendication 8,
    les informations relatives à la probabilité du statut d'absence en fonction du contexte du dispositif (100) comprenant des informations sur les probabilités du statut d'absence en fonction des statuts du dispositif (100),
    le contrôleur (170) étant en outre conçu pour déterminer la fiabilité de la période prévue pour laquelle le statut d'absence doit être maintenu, basé une valeur de probabilité correspondant à un statut du dispositif (100), lorsque le statut d'absence a commencé, et la valeur de probabilité étant obtenue à l'aide des informations sur les probabilités du statut d'absence en fonction des statuts du dispositif (100).
     
    11. Dispositif (100) selon la revendication 1, comprenant en outre :

    un communicateur (130) conçu pour échanger des données sur l'application sur le serveur, même si l'entrée d'utilisateur n'est pas reçue,

    le contrôleur (170) étant en outre conçu pour commander au communicateur (130) d'arrêter d'échanger les données, lorsque la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à l'intervalle de temps de référence.


     
    12. Dispositif (100) selon la revendication 1, le contrôleur (170) étant en outre conçu pour ne pas demander au communicateur (130) de sortir des informations indiquant la réception de l'événement, lorsque la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à l'intervalle de temps de référence, même si des informations sur un événement sont reçues par un serveur.
     
    13. Dispositif (100) selon la revendication 1, comprenant en outre :
    un communicateur (130) conçu pour recevoir d'un serveur des données mises à jour relatives à l'application, même si l'entrée d'utilisateur n'est pas reçue,
    le contrôleur (170) étant en outre conçu pour commander au communicateur (130) de ne pas recevoir les données mises à jour du serveur, lorsque la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à l'intervalle de temps de référence.
     
    14. Procédé de gestion d'énergie, comprenant :

    déterminer si un statut d'absence pour lequel l'utilisateur n'utilise pas un dispositif (100) a commencé, lorsqu'une entrée d'utilisateur n'est pas reçue de l'utilisateur ;

    caractérisé par

    la détermination, lorsqu'il a été déterminé que le statut d'absence a commencé, d'une période prévue pour laquelle le statut d'absence doit être maintenu depuis l'instant où le statut d'absence a commencé, basé sur des informations relatives à une probabilité du statut d'absence en fonction d'un contexte du dispositif (100) ; et

    l'arrêt d'une opération d'une application exécutée sur le dispositif (100) à partir de l'instant où le statut d'absence a commencé, en réponse au fait que la période prévue pour laquelle le statut d'absence doit être maintenu est supérieure ou égale à un intervalle de temps de référence.


     
    15. Support d'enregistrement non transitoire lisible par ordinateur sur lequel est enregistré un programme pour exécuter le procédé selon la revendication 14.
     




    Drawing




























































































    Cited references

    REFERENCES CITED IN THE DESCRIPTION



    This list of references cited by the applicant is for the reader's convenience only. It does not form part of the European patent document. Even though great care has been taken in compiling the references, errors or omissions cannot be excluded and the EPO disclaims all liability in this regard.

    Patent documents cited in the description