ES2748814T3 - Event selection based on user input and current context - Google Patents

Abstract

A method of displaying one or more of context-dependent past, current, and future events on a wearable device, wherein the method comprises: determining (804) a current context of a wearable device user based at least in part on sensors available in the portable device; capturing (806), using sensors available in the available laptop, at least one event; storing (808) the captured event (s) as part of multiple past, current, and future stored events; receiving (810) a rotation input on the portable device; selecting (818) one or more events based on the determined current context and rotation input; and providing (820) on the portable device a representation of at least one of the selected events of the multiple events; characterized by: responding to the reception of the rotation input, determining (816) a speed of the rotation input, determining a quantity and granularity of events to select based on the determined speed of the rotation input, and determining (814) a magnitude of the rotation input, wherein said selection is based on the determined current context, the determined quantity and granularity of the events to select and the determined magnitude of the rotation input.

Description

DESCRIPTION

Event selection based on user input and current context

Background

Various applications provide information on time-dependent events such as calendar applications and applications for making to-do lists. Those apps provide reminders for scheduled tasks or events, even in case of delay. However, these applications do not provide information about various events depending on the current context. Some existing systems allow you to configure some dates for display or a period during which a user wants events to be displayed. However, often a user may need to know about a past, current, or future task or event depending on the current context, and important events or tasks may be different depending on the user's different current contexts. In these respects at least, existing systems fail to provide context-based recovery of events and tasks and allow actions to be taken in this regard naturally. In US2015 / 0046828 A1, a method and system for contextualizing and presenting user data is described. The method includes collecting information comprising service activity data and sensor data from one or more electronic devices. The information is organized according to the time associated with the information collected. Content information and / or service information of possible interest is provided to the electronic devices or depending on the context of the user and / or the activity of the user. In one embodiment, the method may include filtering the organized information based on one or more selected filters. In one example, the user's context is determined based on location information, movement information, and / or user activity. Organized information can be presented in a particular chronological order on a graphic timeline. In an exemplary embodiment, the provision of content and / or services of possible interest comprises providing alerts, suggestions, events and / or communications to or to the electronic devices.

In WO2013 / 041345 A1, a method for context-based processing of interaction events in a communication network is described. The method includes extracting one or more context elements for each of multiple interaction events. Contextual elements can be extracted from interaction information associated with multiple interaction events.

Compendium

The invention relates to a method and a system as defined respectively in the appended independent claims 1 and 10. The examples in the description determine the current context of a user. The invention provides a method for displaying context dependent past, current and / or future events on a portable device as defined in claim 1, and a system as defined in the second independent claim.

This compendium is provided to introduce a selection of concepts in a simplified form that will be further described later in the detailed description. This compendium is not intended to identify the key or essential elements of the claimed subject matter, nor is its use intended to aid in determining the scope of the claimed subject matter.

Brief description of the drawings

Figure 1 is an example schematic diagram illustrating the concept of past, current and future events in the present context.

Figure 2 is an example schematic diagram illustrating some examples of past and future events. Figure 3 is an example schematic diagram illustrating a method of obtaining data in relation to a past event.

Figure 4 is an example schematic diagram illustrating a method of obtaining data in relation to a future event.

Figures 5A-5C are examples of schematic diagrams illustrating a method of obtaining data in relation to a past event as a function of an input angle.

Figures 6A-6C are examples of schematic diagrams illustrating a method of obtaining data regarding a future event as a function of an input angle.

Figure 7 is an example block diagram illustrating a mobile computing device as used in some examples of the present disclosure.

Figure 8 is an example of a flowchart illustrating a method of obtaining and displaying a selected event.

Figure 9 is an example of a flowchart illustrating a method of obtaining and displaying a selected event and taking action on it.

Figure 10 is an example of a flowchart illustrating another method of obtaining and displaying a selected event and taking action on it.

Figure 11A is an example schematic diagram illustrating how various events can be captured.

Figure 11B is an example schematic diagram illustrating an example decision method of where to store events.

Figures 12A-12C are examples of schematic diagrams illustrating an example of a method of recovering from a past event.

Figure 13 is an example schematic diagram illustrating an example of a past event retrieved based on a current context.

Figure 14 is an example schematic diagram illustrating an example of a different retrieved past event based on a different current context.

Corresponding reference characters indicate corresponding parts in all drawings.

Detailed description

With regard to the figures, the examples in the description allow data to be retrieved in relation to past, current and future events depending on the user's current context. In some examples, a mobile computing device associated with a user captures current events through the use of sensors and / or applications available on the mobile computing device as shown, for example, in Figure 11a. Furthermore, the mobile computing device also captures the user's current context in some examples. Captured events are stored in memory areas (eg, designated) for past events, current events, and future events based on the importance of events captured for past, current, or future moments as shown, for example, in Figure 11B. Data is retrieved in relation to events based on user input and current user context, which may be different in different contexts as shown, for example, in Figures 13 and 14.

Aspects of the description allow data to be provided to a user in relation to past, current or future events relevant to the user's current context rather than data that may not be relevant to the current context. Data retrieved based on the current context allows a user to take actions on a recovered event that better suits the user's current context and avoid providing data that may be out of date or belong to the very distant future and therefore are of little use in the present context. Therefore, the aspects of the description are applicable to all situations in which a present context is established and user inputs to obtain past or future events relevant to the current context are received, interpreted, displayed and / or undertaken actions from them.

The term "events" as described herein encompasses "tasks". Thus, although the operations and functionalities described refer to events, those same operations and functionalities are applicable to tasks alternatively or additionally.

In addition to events stored by applications such as calendar applications and to-do lists, other events are captured by sensors based on the user's context. An event generation engine component (see Figure 7, event generation engine component 741) generates events based on user context and these events are stored as past, current and future events as described herein memory.

Additionally, the description aspects provide a natural, intuitive, and in some examples, physical user interface that can be conveniently, simply, and intuitively manipulated without opening any calendar-based or to-do list-based application. Explore countless events or tasks to find an important event or task. In addition, the aspects of the description provide an improvement in the performance of interaction with the user and a reduction in the error rates since the most important event is recovered and presented to the user depending on the current context of the user. Additionally, in examples where a portable device is used, for example, a smart watch, such as a mobile computing device, the aspects of the description lead to a decrease in size and greater comfort of a device easy to observe and manipulate. without removing the device from a user pocket.

Turning now to Figure 1, an example schematic diagram illustrates the concept of past, present and future events in relation to a present context. These events include known past, present and future events as well as events generated by the event generation engine component 741 (eg, in real time). A user's current context is conceptually displayed by a circle 102 representing the current context as PRESENT 108. Past tense is conceptually displayed to the left of "PRESENT 108" and is represented as PAST 106. Future tense is conceptually displayed at the right side of "PRESENT 108" and is represented as FUTURE 112. To get data for a past event relative to the present context, the user, in one example, provides a counter-clockwise rotation input as shown schematically by an arrow counterclockwise curve 104. Examples of rotation inputs can be the rotation of a ring, a dial, a crown, some other part of a portable device and / or a smart watch worn by the user itself can be rotated relative to the user's wrist. Other forms of rotation inputs such as a gesture rotation input and a rotation touch input, tilt inputs, shake inputs, linear inputs or the like are within the scope of the description. To obtain data for a future event relative to the present context, the user, in one example, provides a clockwise rotation input as schematically shown by a curved clockwise arrow 110.

Referring to Figure 2, an example schematic diagram illustrates some examples of stored past and future event points. Events are represented as 202, 204, 206, 208, 210, 212, 214, 216, 218, 220, 222, 224, and 226. For example, an example of a past event might be PARKING CAR WITH TIME AND PLACE 204, self-generated by event generation engine component 741. Another example of past event may be NAME AND IMAGE OF A PERSON IN A CURRENT MEETING 212, recently recorded during the presentation of the participants in a current meeting. A further example of a past event may be an IMAGE OF A SLIDE PRESENTED AT A CURRENT MEETING 214, recently presented at the current meeting. Some examples of events are obtained based on the current context of the user, which is detected by the sensors (eg, intuiting where the user is and what names to repeat). If the user, while participating in a current meeting, forgets the name and face of a participant, they can retrieve it as a context-dependent past event, an example of which is shown in Figure 13. Similarly, when still If you are participating in the current meeting, the user may want to view a previously presented slide, and the slide image is displayed to the user as another context-dependent event as shown at 214 in Figure 2. However, if the user tries to retrieve a context-dependent past event when you have been directed to a car park at the end of an office workday, the event illustrated is PARKING CAR WITH TIME AND PLACE 204, as shown, for example, in Figure 14. In addition, an action such as a beep from the car can be taken to indicate its position based on the activation by the user of this task that is illustrated. ra through wireless communication between the user's device and the car.

Similarly, an example of a future event may be DAUGHTER'S BIRTHDAY PARTY 216. Another example of a future event may be BUYING MILK ON THE WAY HOME 218. Another example of a future event may be DAY AND TIME OF NEXT MEETING 224 Also, another example of a future event may be CALL JOHN AFTER MEETING 226. For example, if the user tries to retrieve a future event immediately after the current meeting, the first event displayed may be CALL JOHN AFTER MEETING. MEETING 226. In one example, the user can provide an additional input to trigger the CALL JOHN AFTER MEETING 226 task, and the action of calling John is taken. In another example, the task may not display but the action of calling John is automatically taken. In another example, the CALL TO JOHN AFTER MEETING 226 task is displayed and the action of calling John is automatically taken in the absence of additional user input. If the user continues to search for another related future event, NEXT MEETING DAY AND TIME 224 is displayed. Therefore, a very important event for a given context is displayed.

Continuing with other examples, a DAUGHTER BIRTHDAY PARTY 216 event and another BUY MILK ON THE ROAD HOME 218 event may be stored as future events. The event "DAUGHTER BIRTHDAY PARTY 216" may be relatively more distant than the event "BUY MILK ON THE ROAD HOME 218". Accordingly, if the user gives the command to display a major future event after the user has found his car as indicated herein, the event displayed is "BUY MILK ON THE ROAD HOME 218". Activating this task can present a map in the user's car, showing the store that sells the closest milk and the way to it from the user's current location.

Referring to Figure 3, an example schematic diagram illustrates a method of obtaining data in relation to a past event. A ring or dial 304 is rotated in a mobile computing device, eg, a portable smartwatch, counterclockwise 302 to obtain one or more context-dependent past events. A series of small bold arrows 306 symbolically illustrates the concept of MOVING BACKWARDS IN TIME as text 308 shows. The user's hand 310, in one example, can physically move the ring or dial 304 counterclockwise, or provide appropriate gesture input or touch input in other examples.

Referring to Figure 4, an example schematic diagram illustrates a method of obtaining data in relation to a future event. A ring or dial 304 is rotated in a mobile computing device, eg, a portable smart watch, clockwise 408 to obtain one or more future context dependent events.

A series of small bold arrows 404 symbolically shows the concept of MOVING FORWARD IN TIME as text 406 shows. The user's hand 310, in one example, can physically move the ring or dial 304 clockwise or provide proper gesture input or touch input in other examples.

As indicated above in connection with Figure 2, past, current and future events are stored in mobile computing device 702 and / or in other entities such as a server or cloud service 746 associated with mobile computing device 702. Stored events are events captured by sensors 706 and events that are part of 710 applications such as calendar applications or to-do lists. A sensor in mobile device 702 detects the direction, magnitude, and speed of rotation of the rotation input. Based on detecting the direction, magnitude, and speed of rotation of the rotation input and the current context, important past or future events are retrieved and presented to the user as indicated herein.

Figures 5A-5C are examples of schematic diagrams illustrating a method of obtaining data in relation to one or more context-dependent past events as a function of an input angle. In one example, ring or dial 304 is rotated counterclockwise as shown at 502 in Figure 5A or, in another example, a counterclockwise rotation input is provided by using suitable means such as a gestural input natural and the like. The data in relation to one or more past events is a function of the angle traversed by the input with respect to its initial position as shown, for example, at 506 as © ¹ in Figure 5B. The angle traversed can vary, for example, from © ¹ to © ⁿ shown at 508 in Figure 5C, where © ⁿ can have any value from a minimum initial value to k * n, where k can have any positive numerical value finite. For each increasing finite value of the angle traversed, a new past event is retrieved based on the present context. For example, if the minimum entry angle value for which a new event is retrieved is 0.028 radians (approximately 5 degrees), twice the minimum entry angle value (eg, 0.056 radians) may display a second context-dependent past event, in one example.

In another example, 0.056 radians can show the first and second recovered past events. Therefore, each predefined increment retrieves the corresponding context defined event or corresponding context dependent event in addition to the previously retrieved events. Any partial increment is ignored until the increment equals or exceeds the predefined increment value.

In some examples, the amount and granularity of the recovered events depend on the speed of the input. In those examples, the minimum increment value to get the next context dependent event itself depends on the speed of the input. For example, a higher input rate for the same total angle traversed can retrieve a larger number of events with a smaller spacing, while a slower input rate can retrieve a smaller number of events with a larger spacing between them. . For example, the highest input rate can be any value equal to or greater than n / 2 radians per second. Therefore, the higher the input rate, the greater the number of events retrieved for the same total input, as long as the input rate is equal to or greater than a predefined minimum value.

Similarly, for any value less than the predefined value, such as n / 2 radians per second, the lower the input speed, the lower the number of events retrieved for the same total input, as long as the input speed is less than the predefined minimum value.

In some examples, if the input speed is low, for example less than n / 2 radians per second, and the total input angle is greater than a predefined angle, such as for example n / 8 radians and less than another angle Predefined, such as for example n radians, retrieves a continuum of past events dependent on context and displays at intervals of equal spacing or based on their time records. The context-dependent continuum of past events can start with the event that would be retrieved if the input was the minimum predefined input angle and can end with the event that would be retrieved if the input was the maximum predefined input angle.

Figures 6A-6C are examples of schematic diagrams illustrating a method of obtaining data regarding one or more future context-dependent events as a function of an input angle. In one example, ring or dial 304 is rotated clockwise as shown at 602 in Figure 6A or, in another example, a clockwise rotation input is provided by using suitable means such as a gesture input , a touch input and the like. The data in relation to one or more past events is a function of the angle traversed by the input with respect to its initial position as shown, for example, at 606 as © ³ in Figure 6B. The angle traversed can vary, for example, from © ³ to © ^p shown in Figure 6C at 608, where © ^p can have any value from a minimum initial value to m * n, where m can have any positive numerical value finite. For each increasing finite value of the angle traversed, a new past event is retrieved based on the present context. For example, if the minimum entry angle value for which a new event is retrieved is 0.028 radians (approximately 5 degrees), twice the minimum entry angle value (eg, 0.056 radians) may display a second context-dependent future event, in a example.

In another example, 0.056 radians can show the first and second recovered future events. Therefore, each predefined increment retrieves the corresponding context dependent event or corresponding context dependent event in addition to the previously retrieved events. Any partial increment is ignored until the increment equals or exceeds the predefined increment value.

In some examples, the amount and granularity of the recovered events depend on the speed of the input. In those examples, the minimum increment value to get the next context dependent event itself depends on the speed of the input. For example, a higher input rate for the same total angle traversed can retrieve a larger number of events with a smaller spacing, while a slower input rate can retrieve a smaller number of events with a larger spacing between them. . For example, the highest input rate can be any value equal to or greater than n / 2 radians per second. Therefore, the higher the input rate, the greater the number of events retrieved for the same total input, as long as the input rate is equal to or greater than a predefined minimum value.

Similarly, for any input speed value less than the default value, such as n / 2 radians per second, the lower the input speed, the lower the number of events retrieved for the same total input, as long as the input speed is less than the predefined minimum value.

In some examples, if the input speed is low, for example less than n / 2 radians per second, and the total input angle is greater than a predefined angle, such as n / 8 radians and less than another predefined angle, Like n radians, a continuum of context-dependent future events is retrieved and displayed at equally spaced intervals or based on their time records. The continuum of future context-dependent events can start with the event that would be retrieved if the input was the minimum predefined input angle and may end with the event that would be retrieved if the input were the maximum predefined input angle.

Referring now to Figure 7, an example block diagram illustrates a mobile computing device 702 as used in some examples. In the example of Figure 7, the mobile computing device 702 associated with a user 742 represents a system for displaying and taking context-dependent past, current or future events. Mobile computing device 702 (eg, a portable device) represents any device that executes instructions (eg, as application programs and / or operating system functionalities) to implement the operations and functionalities associated with the mobile computing device. . Mobile computing device 702 can include any other portable device. In some examples, the mobile computing device 702 includes a mobile phone, a laptop, a tablet, a computing panel, a portable mini-computer, a video game device, and / or a portable media player. Mobile computing device 702 may also include less portable devices such as desktop personal computers, interactive terminals, dashboard-type devices, industrial control devices, wireless charging stations, and electric car charging stations. Additionally, mobile computing device 702 may represent a group of processing units or other computing devices. In some examples, mobile computing device 702 has at least one processor 704, memory area 748, and at least one user interface component 738. Processor 704 includes any number of processing units and is programmed to execute instructions executable by computer to implement aspects of the description. Instructions may be performed by processor 704 or by multiple processors running within the computing device, or may be performed by a processor external to the computing device. In some examples, processor 704 is programmed to execute instructions such as those illustrated in the figures (eg, Figures 8, 9, and 10).

In some examples, processor 704 represents an implementation of analogous techniques for performing the operations described herein. For example, operations can be performed by an analog computing device and / or a digital computing device.

The mobile computing device further has one or more computer readable media such as memory area 748. Memory area 748 includes any number of media associated with, or accessible by, mobile computing device 702. The area Memory 748 can be internal to mobile computing device 702 (as shown in Figure 7), external to mobile computing device 702 (not shown), or both (not shown). In some examples, memory area 748 includes read-only memory and / or memory wired with an analog computing device.

Memory area 748 stores, among other data, one or more applications 710. Applications 710, when run by processor 704, comply with functionality on mobile computing device 702. Examples of applications include mail application programs. , web browsers, calendar application programs, to-do list applications, voice recognition applications, address book application programs, messaging programs, media applications, web-based services location, search programs, and the like. Applications can communicate with counterparts of applications or services such as web services accessible through a network. For example, applications can represent downloaded client-side applications that correspond to server-side services running in a cloud.

Memory area 748 further stores environmental data 712, image data 714, audio data 716, location data 718, mobility data 720, calendar data 722, to-do list data 724 and context data 726. Stored data is part of multiple data from past, current and future events. Memory area 748 further stores one or more computer executable components. While the computer executable component (s) and various data are displayed as logically stored in memory area 748, some of this data and components may be physically stored elsewhere in mobile computing device 702 or other entities associated with mobile computing device 702. such as 746 cloud services.

Examples of components include an input magnitude determining component 728, an input direction determining component 730, an input speed determining component 732, a context determining component 734, an event selection component 736, a user interface component 738, an event triggering component 740 and an event generating engine component 741. The event generating engine component 741, when executed by processor 704 associated with mobile computing device 702, causes processor 704 to generate events based on user context. For example, events can be auto-generated by event generation engine component 741. Input magnitude determining component 728, when executed by processor 704, causes processor 704 to determine the magnitude of an input provided by a user 742. The input address determining component 730, when executed by processor 704, causes processor 704 to determine the address of the input. The input rate determining component 732, when executed by processor 704, causes processor 704 to determine the rate of the input. Context determination component 734, when executed by processor 704, causes processor 704 to determine the current context of the user in which the user input was provided. The event selection component, when executed by processor 704, causes processor 704 to select one or more events from multiple past, current, and future events based on the direction and magnitude determined by the rotation user input and the given current context, where past, current and future events include events generated by event generation engine component 741. Communication interface component 708 accesses multiple past, current and future events, as will be discussed later. Once selection of the event (s) is made from multiple past, current, and future events, the user interface component displays the selected events in a user interface on the mobile computing device 702. In some examples, displaying the Selected events includes displaying data associated with the selected events.

In some examples, event triggering component 740, when executed by processor 704, causes the processor to perform at least one suitable action indicated by the selected events consistent with the current context. In one example, the event trigger component 740 may cause the processor to take the appropriate action as indicated by the selected events without displaying the selected events. In another example, the event trigger component 740 may cause the processor to take the appropriate action as indicated by the selected events after the selected events have been displayed. In some examples, the event triggering component 740 may cause the processor to take the appropriate action as indicated by the events that are displayed after the user interface component 738 has received a user command to take the appropriate action in function of the displayed events and their associated data. In some other examples, the user interface component 738 may display one or more proposed actions corresponding to the selected events and the current context, and the event trigger component 740 may cause the processor to perform the proposed action or actions in a manner automatic, after a predefined time has elapsed after displaying the proposed actions without having received any additional user input.

The mobile computing device includes a communication interface component 708. In some examples, the communication interface component includes a network interface card and / or computer-executable instructions (eg, a controller) to operate the card network interface. Communication between the mobile computing device and other devices (eg, a cloud service or other servers) can occur through the use of any protocol or mechanism over any wired or wireless connection, including, for example, example, a cellular network or a broadband network. In some examples, the communications interface can operate with short-range communication technologies such as near-field communication (NFC) tags. Communication interface component 708, when executed by processor 704, causes processor 704 to access multiple past, current and future events stored in memory area 746 and / or stored in cloud services 746, where mobile computing device 702 is in communication with cloud services 746 over the internet 744.

The mobile computing device includes a user interface component 738. In some examples, the user interface component includes a graphics card for displaying data to the user and receiving data from the user. The user interface component may also include computer executable instructions (eg, a driver) to operate the graphics card. In addition, the user interface component may include a display (eg, a touch screen or natural user interface) and / or computer-executable instructions (eg, a controller) to operate the display. The user interface component 738 can use one or more of the following to provide user data or receive user data: speakers, a sound card, a vibration motor, touch detection hardware, gesture detection hardware, a module BLUETOOTH communication hardware, Global Positioning System (GPS) hardware, and one or more 706 sensors that are also used to capture events and contexts. Sensors can include accelerometers, gyroscopes, GPS receivers, proximity sensors, photoreceptor light sensors, 3D infrared cameras that include a depth sensor, two-dimensional RGB cameras, and multi-array microphones. For example, the user may enter commands or manipulate data by moving the mobile computing device 702 in a particular way, including tilting, shaking, and rotating the mobile computing device 702.

In some examples, the sensor (s) and other components of the mobile computing device 702 may comprise microelectromechanical systems (MEMS), which leads to a further decrease in size of the mobile computing device 702. The mobile computing device 702 may have other sensors that provide data describing the status of the mobile computing device 702.

Figures 8, 9 and 10 illustrate examples of flow diagrams to show and / or take action on selected tasks and / or events. While the operations shown in the flowcharts can be performed by mobile computing device 702, aspects of the description can be used with other entities that perform one or more of the operations shown in the flowcharts. For example, one or more operations can be performed by a mobile phone associated with the user. In some other examples, one or more operations may be performed by a remote server with respect to mobile computing device 702 although in communication with mobile computing device 702 and / or one or more operations may be performed by cloud services 746.

Referring now to Figure 8, an example flowchart illustrates a process for selecting and displaying on a user device some events from multiple past, current, and future events stored based on a user's current context. Processing begins at 802. At 804, the user's current context and / or the user's device is determined. For example, the location, surroundings, time of day, date, surroundings, environment, proximity to a group of people, the mode of movement, and a current status of the user's device (eg, display blocked from a mobile computing device) and the like can be determined by the mobile computing device 702. In 806, current events are captured by the use of sensors 706 and access to data associated with some of the 710 applications, eg data from calendar and to-do list data. In 808, captured events are stored as part of multiple past, current, and future events that may already be stored. Events are stored along with their associated data as n-tuples that form an n-tuple vector space. For example, events can be stored with their associated time stamps and contexts. If the event is a task, the event can be stored along with a scheduled time and date, and any data and / or objects to be used in the performance or activation of the tasks.

At 810, it is verified whether a user input has been received to select one or more events from the multiple stored past, current, and future events based on the current context determined. For example, the mobile computing device 702 can iteratively verify whether the user input has been received as shown by the arrow "NO" which returns to determining the current context in the absence of receipt of any user input. If a user input is received, for example, in the form of a ring or dial rotation, or a rotational gesture input or a rotation touch input, or a tilt input, the direction of the input is determined at 812 . For example, the mobile computing device 702 determines whether the direction of the rotation input is clockwise or counterclockwise. In some examples, the user input may be in the form of a tilt of the user device, where the tilt direction indicates the direction of the user input. For example, the tilt can be a tilt to the right-hand side or a tilt to the left-hand side. In 814, the angle of the user input is determined. For example, for a rotation user input, the angle may be the angle of rotation of the ring, dial, or other rotation input with respect to its initial position. Similarly, for example, for a tilt input, the tilt angle relative to the initial position can be determined. At 816, the rate of user input is determined.

At 818, one or more events are selected from the multiple stored past, current, and future events based on the direction, angle, and / or rate determined from the user input and based on the particular context. For example, if the direction of the rotation input is clockwise or the direction of the tilt input is clockwise, a subset of the future events of the n-tuple vector space is selected from the multiple past events. , current and future. The determined angle of the user input triggers the selection of a subset of the selected subset of future events. Alternatively or additionally, the user input rate determined can be used to select some future events from the selected subset of future events or some future events from the Selected subset of the subset of future events. A final selection of this selected subset or subset is made based on the current context determined. A heuristic algorithm can be used to determine important events for the selected subset or subset based on the current context determined.

It may be noted that while events may be captured as current events during the capture phase, when stored they may be part of past events or future events (eg car location may be shown as a future location when leaves a building). For example, during a meeting, when participants introduce themselves, these events are captured as current events with time stamps, associated image data, audio data, and other contextual data. However, as soon as a presentation by a particular participant ends, and the next participant begins to present, the data relative to the previous participant is stored as data from a past event.

Regarding the selection of past events, a process similar to the process indicated above is followed to select future events with the difference that, for example, an anticlockwise rotation input or left-hand side tilt input they trigger the selection of important past events.

At 820, at least part of the selected events can be displayed on a user interface of the user device. Alternatively and / or additionally, selected events may be presented on the user's device through other means (eg, through a loudspeaker).

Turning now to Figure 9, an example flowchart illustrates a method of obtaining and taking action on a selected event. The method begins at 902. At 904, the current context of the user and / or the user's device is determined.

At 906, it is verified whether a user input has been received to select one or more events from the multiple past, current, and future events based on the current context determined. For example, you can iteratively check whether the user input has been received as shown by the “NO” arrow that returns to the determination of the current context in the absence of receipt of any user input. If a user input is received, for example, in the form of a ring or dial rotation, or a rotational gesture input or a rotation touch input, or a tilt input, the direction of the input is determined at 908 . For example, the mobile computing device 702 determines whether the direction of the rotation input is clockwise or counterclockwise. In some examples, the user input may be in the form of a tilt of the user device, where the tilt direction indicates the direction of the user input. For example, the tilt can be a tilt to the right-hand side or a tilt to the left-hand side. At 910, the rate of user input is determined.

In 912, the angle of the user input is determined. For example, for a rotation user input, the angle may be the angle of rotation of the ring, dial, or other rotation input with respect to its initial position. Similarly, for example, for a tilt input, the tilt angle relative to the initial position can be determined.

At 914, the mobile computing device 702 verifies if the address of the user input is clockwise. In examples where the user input is a tilt from the user device, the mobile computing device 702 can verify if the direction of the tilt is to the right hand side. In these examples, it is assumed that the clockwise rotation input or the right hand tilt input causes recovery of future events. However, in other examples, a counter-clockwise rotation input or a right-hand tilt input can cause recovery of future events. The correspondence between the direction of rotation and the recovery of future or past events can be configured by the user.

If the direction of the rotation input is clockwise or the direction of the tilt input (in examples where the user input is in the form of a tilt of the user device) is to the right-hand side, selects one or more future events based on the angle of rotation and / or the speed of rotation of the user input at 916. In examples where the user input speed is used, alternatively or additionally, in the selection of the future event or events, the granularity and / or the quantity of the selected events may depend on the user input speed as indicated above.

If the direction of the rotation input is counterclockwise or the direction of the tilt input (in examples where the user input is in the form of the tilt of the user device) is to the left hand, one or plus future events based on the angle of rotation and / or the speed of rotation of the user input at 924. In examples where the user input speed is used, alternatively or additionally, in selecting the or past events, granularity and / or number of selected events may depend on user input rate as stated above.

In 920, actions are taken on at least one of the selected events. For example, for a selected future event, such as a planned visit to a cinema to see a movie, you can take the action of buying tickets online. In another example, for a late payment on a credit card account, recovered as a past event, you can take the action of paying online.

As shown by the dashed lines, optionally at 918, the selected event (s) may be displayed before action is taken on at least one of the selected events.

The process ends at 922.

Next, with respect to Figure 10, an example flowchart illustrates another method of obtaining and displaying a selected event. The method begins at 1002. At 1004, the current context of the user and / or the user's device is determined.

At 1006, it is verified whether a user input has been received to select one or more events from the multiple past, current, and future events based on the current context determined. For example, the mobile computing device 702 can iteratively verify whether the user input has been received as shown by the arrow "NO" which returns to determining the current context in the absence of receipt of any user input. If a user input is received, for example, in the form of a ring or dial rotation, or a rotational gesture input, or a rotation touch input, or a tilt input, the direction of the input is determined at 1008 . For example, the mobile computing device 702 determines whether the direction of the rotation input is clockwise or counterclockwise. In some examples, the user input may be in the form of a tilt of the user device, where the tilt direction indicates the direction of the user input. For example, the tilt can be a tilt to the right-hand side or a tilt to the left-hand side. In 1010, the speed of the user input is determined.

In 1012, the angle of the user input is determined. For example, for a rotation user input, the angle may be the angle of rotation of the ring, dial, or other rotation input with respect to its initial position. Similarly, for example, for a tilt input, the tilt angle relative to the initial position can be determined.

At 1014, the mobile computing device 702 verifies if the address of the user input is clockwise. In examples where the user input is a tilt from the user device, the mobile computing device 702 can verify if the direction of the tilt is to the right hand side. In these examples, it is assumed that the clockwise rotation input or the right hand tilt input causes recovery of future events. However, in other examples, a counter-clockwise rotation input or a right-hand tilt input can cause recovery of future events.

If the direction of the rotation input is clockwise or the direction of the tilt input (in examples where the user input is in the form of a tilt of the user device) is to the right-hand side, selects one or more future events based on the rotation angle and / or the rotation speed of the user input in 1016. In examples where the user input speed is used, alternatively or additionally, in the selection of the future event or events, the granularity and the number of the selected events may depend on the user input speed as indicated above.

If the direction of the rotation input is counterclockwise or the direction of the tilt input is to the left hand (in examples where the user input is in the form of a tilt of the user device), select one or plus past events depending on the angle of rotation and / or the speed of rotation of the user input in 1026. In examples where the user input speed is used, alternatively or additionally, in selecting the or past events, granularity and / or number of selected events may depend on user input rate as stated above.

At 1018, at least one of the selected event (s) is displayed in a user interface on the user device. The method ends in 1024.

However, at any point during the operations shown in Figure 10, if the user wants to quickly return to the present, they can provide a suitable input such as a reverse-rotation fast input, e.g. For example, in the case of turning clockwise, a rapid movement counterclockwise and vice versa. In addition, the user can shake their device to return to the present. Other methods can be used to quickly return to the present.

As shown with the dashed lines, optionally at 1020, the mobile computing device 702 can verify if any additional user input has been received to take action on one or more of the displayed events. If this option is followed, appropriate actions are taken on the displayed event (s) in 1022 according to the received additional user input, and the method ends in 1024. However, if no additional user input is received, the method it ends in 1024 without taking any action.

Referring now to Figure 11A, an example schematic diagram of an example situation illustrates some examples of events and / or contexts that can be captured. In 1102, events from a calendar application and events relating to people in a contact list or the like are displayed as events that can be captured. In 1104, a person event is displayed that is presented as an event that can be captured. In this example, the person's voice can be stored along with a photo of that person. A multi-array microphone not only captures the voice, but is also capable of detecting the direction of the voice source and allows an RGB camera to focus on the voice source to capture the photo and the 1126 smart watch that interpret the gestures in the photo as a person introducing himself. Such an event can be recorded as an image and audio and / or a speech recognition engine can recognize the audio, convert the audio to text, and add a comment to the image with the text.

The location of a user device is captured in 1106, by using, for example, a GPS receiver and / or other methods such as signals from multiple cellular base stations and / or multiple Wi-Fi hotspots and / or an application mapping. As noted above, the location can be one of the components of the user's context and / or the user's device. In 1108, sound cues are captured as part of context and events. For example, the voice of a person performing can be stored as an event, while another sound can provide an indication as to the environment and surroundings such as an opera house, theater, cinema, shopping mall, a classroom, living room, and the like, and may facilitate determination of the user's current context and / or user device.

Referring now to Figure 11B, an example schematic diagram illustrates an example of user device 1126 that captures events and decides where to store events. As indicated above in connection with Figure 11A, device 1126 (eg, a portable device such as a smart watch) continually searches for existing prompts to capture events and contexts. Based on existing indications, device 1126 decides, as shown in 1120, where the captured data should be stored. For example, as shown at 1122, device 1126 decides what data should be stored as past events in history. For example, when you park a car in the office in the morning when you get to work, the location of the car in the parking area can be stored as a past event with its associated time stamp and context. Similarly, during an office meeting, the participants' initial presentations at the meeting can be stored as past events with time stamps and the associated context. As noted above, while these events are current events when they do occur, they go down in history after being stored. However, some other data, as shown in 1124, may be stored as future events. For example, if a decision is made just before the meeting ends about the date, time, and place of the next meeting, this event is stored as a future event. Similarly, if during the course of the day you receive a text message from a friend that you have to buy milk on the way home, this message or a summary of it should be stored as the future event.

Next, with respect to Figure 12A-12C, examples of schematic diagrams illustrate an example of a method of recovering from a past event. As indicated herein, a ring or dial can be rotated on a user's portable device, for example, counterclockwise, to retrieve a context-dependent past event. An example of a ring on a smart watch is shown in Figure 12A at 1202. The ring is shown held by the wearer's rings in Figure 12B at 1204. The ring is shown rotating counterclockwise in Figure 12C at 1206 to get one or more context dependent past events. However, other methods or means can be used to provide user input. For example, you can use a rotate gesture. In another example, rotating touch input can be provided by touching the smartwatch dial with your fingers and then having your fingers rotate counterclockwise. In another example, the smart watch must be tilted or shaken in a particular way. For example, a left-hand side tilt can provide an input to retrieve one or more context-dependent important past events, and a right-hand side tilt can provide an input to retrieve one or more important dependent future events. of the context. In another example, shaking the smart watch from left to right can provide user input to retrieve one or more future events. Similarly, shaking the smart watch from right to left can provide user input to retrieve one or more past events.

Referring now to Figure 13, an example schematic diagram illustrates an example of a past event retrieved based on a current context. At 1302, a participant's face is shown as recovered when, for example, another participant, who may have forgotten who a particular participant is, rotates ring 1202 counterclockwise to obtain the image and name of that participant. In this case, since the watch is aware of the current context, namely the current meeting, the watch retrieves the images of meeting participants along with their names. The participant who wants to know who a particular participant is continues to rotate ring 1202 until the participant in question is shown with the participant's name in audio and / or text over the image. Therefore, a context dependent event is easily retrieved.

Next, with respect to Figure 14, an example schematic diagram illustrates an example of a different retrieved past event based on a different current context. For example, at the end of office work hours, the same meeting participant for whom a past presentation event of a meeting was retrieved. image of a particular participant in a current meeting as a context dependent past event now you want to know where the participant parked the car in the parking area. In this case, when the person rotates ring 1202, device 1126 (eg, a smart watch) displays a car as parked at location C 23, 200 feet (sixty meters) away. In one example, the user may take additional action to cause the car to beep to indicate its location. For example, the user may additionally rotate ring 1202 to take action on this displayed event. Alternatively, a gesture can be performed to take an action, or the displayed entry can be touched to take the appropriate action, or one or more physical elements of the computing device 702 can be pressed (eg, a button). to take appropriate action. In some examples, the button may be a virtual button. Other ways of user input to trigger a displayed event are within the scope of the description.

Additional examples

In one example, while at least one of the selected event (s) can be provided to display, some other selected event (s) may not be provided but actions can be taken on at least one of those selected events but they were not provided for display. In some examples, computing device 702 includes security features such as a fingerprint reader to authenticate user 742 before taking any action on an event or triggering an event.

In an example scenario, during a meeting, if a participant wants to see a previous slide in a presentation, the participant can rotate ring 1202 to see all the slides presented so far. In some examples, the 1126 smart watch can be in communication with a mobile phone, and while fragments of the slide can be displayed on the 1126 smart watch, the detailed slides can be displayed on the mobile phone.

In another example scenario, if a user exits a mall after shopping, and the user arrived at the mall by the meter, clockwise rotation of ring 1202 may indicate the next available meter toward home. In another example, if the user has an appointment to meet someone in ten minutes, rotating ring 1202 clockwise can cause the appointment to be displayed. An additional entry to indicate the meeting location can show the meeting location. It may be noted that the user may have another appointment with someone the next day, but an important context-dependent current appointment is retrieved to be displayed, rather than a distant one. In this way, the user does not need to return to a calendar application to observe all tasks or appointments during a certain period; rather, a very important upcoming task or appointment is displayed on the 1126 smart watch.

In another example, if a student takes notes in a class on a device, the student can select a text and instruct the 1126 smartwatch to display previous notes related to that text. If the smart watch is in communication with the device, a small summary of related notes can be displayed on the 1126 smart watch, while details can be displayed on the student's device. Additionally, the student can select a word and the smart watch can display a dictionary definition and / or a thesaurus that provides synonyms and antonyms.

In another example, a student who went to school on a bicycle may be able to lock the bicycle as a future action, after parking the bicycle. At the end of classes, an order to retrieve a past event may show the location of the bicycle where it was parked, while a subsequent order may unlock the bicycle. Therefore, the examples in the disclosure provided herein, and those not specifically provided but within the scope of the disclosure, allow users to retrieve the most important events from countless events from Naturally and intuitively, the system retrieves an important event after determining the user's current context.

In another example scenario, when a writer's laptop is pinned to a smart watch 1126, if the writer has been updating a paragraph, counter-clockwise movement of ring 1202 may show the writer an earlier version of the paragraph.

The 1126 smart watch can also be used to continuously monitor a user's blood pressure and heart rate. In those cases, during a walk as part of an exercise, moving the ring 1202 backward can show how far the user has walked and how much the blood pressure and / or heart rate has changed. In such a situation, forward movement of ring 1202 may suggest how much further the user should walk before taking a break.

In some examples, an "Undo" option may be available on the smart watch. For example, while an order for a major past event in a meeting may feature a previous slide, an undo order may begin to display the current time and the remaining time of the meeting as scheduled. Similarly, in the example of the student unlocking a bicycle, an undo command can relock the bicycle.

As an alternative or in addition to the other examples described herein, the examples include any combination of the following options:

- displaying at least one context-dependent past event on the handheld device by determining that the direction of the rotation input is counterclockwise; or

- displaying at least one context-dependent future event on the handheld device by determining that the direction of the rotation input is clockwise.

- Provide information associated with at least one past event associated with a current event.

- Provide a recommendation to trigger the context dependent future event.

- Store multiple events with their corresponding time registers and associated contexts, and select the multiple event (s) based on the time registers and associated contexts.

- Determine a speed of a rotation input and determine a selection granularity of the multiple events depending on the determined speed of the rotation input.

- Store at least part of the data associated with the multiple events and contexts on the portable device and at least another part of the data in a cloud service, where the portable device is in communication with the cloud service directly or through another device.

- Select the event or events of the multiple events based on the direction of rotation and angle of rotation of the rotation input.

- Show a continuum of events depending on the direction and speed of the rotation input when the rotation angle is greater than a predefined angle and less than another predefined angle.

- Show information associated with a retrieved event and perform an action based on an additional user input, where the additional user input is based on the displayed information.

- Show a proposed action on the mobile computing device and take action automatically after a predetermined time when no additional user input is received.

- User input may comprise tilting the mobile computing device or moving the mobile computing device or gesturing.

- The current context depends on the data collected by one or more sensors and data received by the mobile computing device of a cloud service.

- Select one or more events from a set comprising past events on determining that the direction of the rotation user input is counterclockwise and select one or more events from a set comprising future events on determining that the Rotation user input direction is clockwise.

At least part of the functionality of the various elements shown in Figures 8, 9, and 10 can be executed by the components shown in Figure 7, or by an entity (eg, processor, web service, server, application program, computing device, etc.) not shown in Figure 7.

In some examples, the operations illustrated in Figures 8, 9, and 10 can be implemented as coded software instructions on a computer-readable medium and / or on hardware programmed or designed to perform the operations. For example, aspects of the description may be implemented as a system on a chip or other circuit, including multiple interconnected elements with electrical conductivity, or application specific ICs (ASICs) or programmable door arrays in field (FPGA).

While the aspects of the disclosure have been described in terms of various examples with their associated operations, one skilled in the art would realize that a combination of operations from any number of different examples is also within the scope of the aspects. of the description.

The term "pinned", as used herein, refers, in some examples, to situations where one device acts as an access point for another device to access the network. A tethered connection can be made through a wired connection or a wireless connection. The term "wifi", as used herein, refers, in some examples, to a wireless local area network using high-frequency radio signals for data transmission. The term "BLUETOOTH" as used herein refers, in some examples, to a wireless technology standard for exchanging data over short distances using short wavelength radio transmission. The term "cellular", as used herein, refers, in some Examples, to a wireless communication system using short-range radio stations that, when linked together, allow data transmission over a wide geographic area. The term "NFC", as used herein, refers, in some examples, to a short-range high-frequency wireless communication technology for data exchange over short distances.

While personal identifying information is not tracked in aspects of the description, the examples have been described with respect to supervised and / or collected data from users. In some examples, users may be notified of data collection (eg, through a dialog box or preference settings) and users are given the opportunity to consent or not to consent to the data collection. supervision and / or collection. Consent can take the form of a consent of inclusion or consent of exclusion.

Operating environment example

Examples of computer-readable media include flash memory drives, digital versatile discs (DVDs), compact discs (CDs), floppy disks, and tape cassettes. By way of non-limiting example, computer readable media comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer read instructions, data structures, programming modules, and other data. Computer storage media is tangible and mutually exclusive with the media. Computer storage media is implemented in hardware and excludes carrier waves and propagated signals. Computer storage media for purposes of the present disclosure are not signs per se. Examples of computer storage media include hard drives, flash drives, and other solid state memories. Instead, the communication means typically comprise computer read instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transport mechanisms, and include any means of information delivery.

While described in connection with an example of a computer system environment, the examples in the description can be implemented with numerous other specific general purpose or general use computer system environments, configurations, or devices.

Examples of well known computer systems, configurations and / or environments that may be suitable for use with aspects of the disclosure include, but are not limited to, mobile computing devices, personal computers, server equipment, portable devices or laptops, multiprocessor systems, video game consoles, microprocessor-based systems, television set-top boxes, programmable consumer electronic equipment, mobile phones, mobile communication and / or computing devices in accessory or portable form factors (eg, watches, glasses, headphones or earphones) ), Network PCs, minicomputers, central computers, distributed computing environments that include any of the above systems or devices, and the like. Those systems or devices can accept user input in any way, including from input devices such as keyboards or pointing devices, through gesture inputs, proximity inputs (such as proximity), and / or through voice inputs.

The examples in the description may be described in the general context of computer executable instructions, such as program modules, executed by one or more computers or other devices in software, firmware, hardware, or a combination thereof. Computer executable instructions can be organized into one or more computer executable modules or components. Typically, program modules include, but are not limited to, routines, programs, objects, components, and data structures that perform particular tasks or implement particular abstract data types. Aspects of the description can be implemented with any number and organization of those components or modules. For example, aspects of the description are not limited to the specific computer executable instructions or the specific components or modules that are illustrated in the figures and described herein. Other examples of the description may include different components or instructions executable by computer with more or less functionalities than those illustrated and described herein.

Aspects of the description transform a general-purpose computer into a special-purpose computing device when configured to execute the instructions described herein.

The examples that are illustrated and described herein, as well as examples that are not specifically described herein but are within the scope of aspects of the description, constitute examples of means for determining a current context of a user of a portable device, receiving a rotation input on the portable device to select one or more of multiple events based on the current context determined, where the multiple events comprise past, current and future events, where at least a part of a context and the minus one of the multiple events are captured by sensors available on the handheld, in response to receiving the rotation input, selecting the event or events of the multiple events based on the current context determined and a direction of rotation of the input of rotation and display on the portable device at least one of the selected event or events connected from multiple events.

For example, one or more of the elements illustrated in Figure 7, such as the input magnitude determining component, the input direction determining component, the input speed determining component, the context determination component, event selection component, user interface component, event trigger component, and communication interface component, when coded to perform the operations illustrated in Figures 8, 9 and 10, constitute examples of means to determine a current context of a user of a portable device, examples of means to receive a rotation input in the portable device to select one or more of multiple events based on the current determined context, where the multiple events comprise past, current and future events, examples of means to select the multiple event (s) in f anointing of the given current context and direction of rotation of the rotation input and examples of means to display on the handheld device at least one of the selected event or events from the multiple events.

Alternatively or additionally, the functionality described herein may be performed, at least in part, by one or more logical hardware components. As a non-limiting example, illustrative types of logical hardware components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standards products ( ASSP, system-on-chip (SOC) implementations, complex programmable logic devices ( ^cp L ^d ), etc.

The order of executing or performing the operations in examples of the description illustrated and described herein is not essential, unless otherwise specified. That is, the operations can be performed in any order, unless otherwise specified, and the examples in the description may include more or fewer additional operations than those described herein. For example, the execution or performance of a particular operation before, at the same time, or after another operation is contemplated to be within the scope of the disclosure aspects.

When elements of aspects of the description or examples are introduced, the articles “a”, “one”, “the”, “the” and the expression “said” are intended to refer to one or more of The elements. The terms "comprising", "including" and "having" are intended to be inclusive and to mean that there may be additional elements in addition to the elements listed. The expression "example of" is intended to mean "illustrative." The expression "one or more of the following: A, B and C" means "at least one of A and / or at least one of B and / or at least one of C". The expressions "at least one of", "one or more" and "and / or" are open expressions that are conjunctive and disjunctive. For example, "at least one of A, B and C", "at least one of A, B or C" and "A, B and / or C" mean only A, only B, only C, A and B together , A and C together, B and C together and A, B and C together.

Having described aspects of the disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of the invention as defined in the appended claims. As various changes could be made in the above constructions, products and methods, without departing from the scope of the invention as defined in the appended claims, it is intended that all the matter contained in the foregoing description and shown in the Attached drawings are to be interpreted as illustrative and not restrictive.

Although the matter has been described in specific language of the actions and / or structural characteristics, it should be understood that the matter defined in the appended claims is not necessarily limited to the specific characteristics or actions described above. Rather, the specific features and actions described above are described as examples of implementation of the claims and other equivalent features and actions are provided without departing from the scope of the invention, to be defined in the appended claims.

Claims (14)

1. A method of displaying one or more of context-dependent past, current and future events on a portable device, where the method comprises: determining (804) a current context of a user of the portable device based at least in part on sensors available on the portable device; capture (806), through sensors available on the available laptop, at least one event; storing (808) the captured event (s) as part of multiple stored past, current and future events; receiving (810) a rotation input into the portable device; select (818) one or more events based on the current determined context and rotation input; and providing (820) on the portable device a representation of at least one of the selected event or events from the multiple events; that is characterized by: respond to receiving the rotation input, determine (816) a speed of the rotation input, determine a quantity and granularity of events to select based on the determined speed of the rotation input, and determine (814) a magnitude of the rotation input, where said selection is based on the current context determined, the determined quantity and granularity of the events to be selected and the determined magnitude of the rotation input. 2. The method of claim 1, wherein providing the representation (820) comprises: displaying on the handheld device a representation of at least one context-dependent past event from determining that the direction of the rotation input is counterclockwise; or displaying on the handheld device a representation of at least one future context-dependent event from the determination that the direction of the rotation input is clockwise. The method of claim 2, wherein displaying the context dependent representation of the past event on the handheld device comprises providing information associated with at least one past event associated with a current event. The method of claim 2, wherein displaying the context dependent future event representation on the handheld device comprises providing a recommendation to trigger the context dependent future event. The method of any of claims 1-2, further comprising storing multiple events with their corresponding time registers and associated contexts, wherein selecting the multiple event (s) comprises selecting the event (s) based on the registers of time and associated contexts. 6. The method of any of claims 1-2 or 5, wherein the rotation input comprises rotating a ring associated with the portable device, performing a rotation gesture or providing a tactile input. 7. The method of any of claims 1-2, 5 or 6, wherein at least a part of the data associated with the multiple events and contexts is stored in the portable device and at least another part of the data is stored in a cloud service, where the portable device is in communication with the cloud service directly or through another device. The method of any of claims 1-2, 5, 6 or 7, wherein the selection of the event (s) is further based on the direction of rotation and where providing the representation comprises showing a continuum of events in depending on the direction and speed of the rotation input and depending on the magnitude of the rotation input being greater than a predefined angle and less than another predefined angle. 9. The method of any of claims 1-2, 5, 6, 7 or 8, wherein the current context comprises a location, an environment, a time of day, a date, an environment, the surroundings, a proximity with a set of predefined people, a mode of locomotion and / or a status of the portable device. 10. A system to perform an action associated with one or more of multiple past, current and future events based on a current context, where the system includes: a mobile computing device (702) having one or more sensors (706) to collect data associated with the current context of a user of the mobile computing device (702) and data associated with at least one of the multiple events; a memory area (748) of the mobile computing device (702) for storing data associated with the current context and data associated with the multiple events; and a processor (704) programmed to: determine (904, 1004) the current context; receiving (906, 1006) a rotation user input; retrieve (916, 924, 1016, 1026) the data associated with one or more of the multiple events in the memory area (748) based on the given context and the rotating user input; and performing (920, 1022) an action associated with the recovered data; characterized by: the processor is further programmed to, in response to receiving the rotation user input, determine (910, 1010) a speed of the rotation user input and determine an amount and granularity of the events to be recovered based on the determined speed of rotation user input; and the recovery of the data associated with the multiple events is based on the current context determined and the quantity and granularity determined. The system of claim 10, wherein performing the action comprises that the processor is programmed to display (1018) information associated with the retrieved data and perform the action based on the additional user input received (1020), where the additional user input is based on the displayed information. 12. The system of any of claims 10-11, wherein the rotating user input comprises tilting the mobile computing device (702), moving the mobile computing device, gesturing or providing a tactile input. 13. The system of any of claims 10-12, wherein performing the action comprises that the processor is programmed to display (918) a proposed action on the mobile computing device (702) and automatically perform the action after a default time if no additional user input is received. 14. The system of any of claims 10-13, wherein the processor is programmed to determine the current context based on the data collected by the sensor (s) (706) and data received by the mobile computing device (702) from a cloud service.