SMARTWATCH OR OTHER WEARABLE DEVICE CONFIGURED TO INTELLIGENTLY INTERACT WITH A USER

Abstract

Several apparatus and a method for receiving and displaying unassociated information elements in useful ways on a wearable computing device are described. In one example, the apparatus receives, organizes, displays and navigates a logical ordering of unassociated information elements. In another example, the apparatus receives unassociated information elements and updates previously received unassociated information elements based on content, context and source. In another example, the apparatus receives, associates, updates, and adds interactive elements to unassociated information elements based on content and source.

Description

TECHNICAL FIELD

Examples described herein generally relate to wearable computing devices such as smart watches, and more specifically directed at wearable computing devices with interactive notification systems.

BACKGROUND ART

Historically wearable computing devices, including smart watches, have suffered from numerous design flaws including large size or poor functionality.

Due to the constraints of wearable computing device form factors, it is difficult to integrate high performance computing technology with an interface that is easy to use. Past wearable computing devices were often large and bulky. The size was usually a function of the power requirements for the included display as well as computational electronics.

At one time, engineering goals in the industry were to provide a full personal computer-type experience on the user's body. This may not be possible because of the aforementioned size, limited battery longevity, and clunky user interface. In order to extend battery life, certain portions of the device's functionality was placed in a limited mode, or switched off entirely.

Due to limitations in input methods available in the wearable computing device sized form factor, user input devices are limited. Attempts at providing a litany of multipurpose input buttons in conjunction with confusing displays can make user input to applications difficult, frustrating and disruptive.

Conversely, other previous efforts to avoid the size problems, produced products with underwhelming features and little added benefit. These wearable computing devices had limited programmability, and provided the user little benefit over their conventional counterparts.

Many attempts have failed to provide the user with an interface that is both elegant and functional.

BRIEF SUMMARY OF THE INVENTION

Several apparatus and a method for receiving and displaying unassociated information elements in useful ways on a wearable computing device are described. In one example, the apparatus receives, organizes, displays and navigates a logical ordering of unassociated information elements. In another example, the apparatus receives unassociated information elements and updates previously received unassociated information elements based on content, context and source. In another example, the apparatus receives, associates, updates, and adds interactive elements to unassociated information elements based on content and source.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating a system of devices providing unassociated information elements according to one example.

FIGS. 2A and 2B are flowcharts illustrating techniques for receiving, displaying, and navigating unassociated information elements according to one example.

FIGS. 3A, 3B, 3C, 3D, and 3E are illustrations demonstrating a technique for receiving informational elements and adding interactions to them.

FIGS. 4A, 4B and 4C are illustrations demonstrating a technique for navigating a logical ordering of future ordered information elements.

FIGS. 5A, 5B and 5C are illustrations demonstrating a technique for navigating a logical ordering of past ordered information elements.

FIGS. 6A, 6B and 6C are illustrations demonstrating a technique for receiving information elements and adding interactions to the elements.

FIGS. 7A, 7B and 7C are block diagrams of wearable computing devices illustrating the relationship between the components of a wearable computing device.

FIG. 8 is a diagram demonstrating navigational state changes utilizing chronological ordering and buttons as input devices.

FIGS. 9A and 9B are examples of alternative embodiments utilizing different input device configurations.

FIGS. 10A, 10B, and 10C are examples of alternative embodiments utilizing two logical orderings of unassociated information elements.

FIGS. 11A, 11B, 11C, 11D, and 11E are illustrations demonstrating a technique for automatically inserting elements based on future events.

DESCRIPTION OF EXAMPLES

In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without these specific details. In other instances, structure and devices are shown in block diagram form in order to avoid obscuring the invention. References to numbers without subscripts or suffixes are understood to reference all instance of subscripts and suffixes corresponding to the referenced number. Moreover, the language used in this disclosure has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter. Reference in the specification to “one example” or to “an example” means that a particular feature, structure, or characteristic described in connection with the examples is included in at least one example of the invention, and multiple references to “one example” or “an example” should not be understood as necessarily all referring to the same example.

As used herein, the terms “a computer system” or “system” can refer to a single computer or a plurality of computers working together to perform the function described as being performed on or by a computer system.

In order to accomplish a robust wearable computing platform, there must be systems in place for enabling information elements to be delivered in a useful manner, and processes implemented for useful interaction.

Elements of unassociated information are inputs into the apparatus. Unassociated information elements, in this context, are generally small capsules of information that one would expect to receive as a notification from an application, however any apparatus capable of generating a notification may be an input source. The applications that generate the unassociated information elements seldom have awareness into what other generating applications are presenting, which often make the unassociated information elements appear disjointed, or unassociated, if viewed cumulatively outside of the context of the applications that generated them. The sources of the unassociated information elements are numerous and include but are not limited to personal computing devices including smart phones and smart watches, other wearable devices, servers including web servers and application servers, personal digital assistants, home automation devices, and automobile computing platforms. These systems generate the unassociated information elements, which are meant to present the user with some information, often related to their operating context of the source. As unassociated information elements vary in type and content, they can be displayed in any part of a display and in various forms. As form factors of devices capable of displaying unassociated information events vary, the actual formatting varies as well.

The unassociated information elements may be distinguished into multiple subsets. These would include but are not limited to personal communication information, past and future event information, and fact-based information.

Personal communication information is a subset of the unassociated information elements that deal with a user's personal interactions with others. These unassociated information elements are distinguished from other information elements in that they have a characteristic that makes them unique to the user. Personal communication information is intended and specifically directed to a particular user, unlike other information elements that are broadly available for all users to access. Personal communication information may be incorporated from an external provider, or from the wearable itself. Examples include but are not limited to short message service (SMS), emails, texts, tweets, fitness metrics, missed telephone calls, Instagram and Facebook notifications.

Event information is a subset of the unassociated information elements that deal with a user's scheduling. Event information is usually a time-based occurrence or series of occurrences for which the user is affected. Examples include but are not limited to calendar entries and reminders.

Fact-based information is a subset of the unassociated information elements that deal with published facts for which the user exhibits an interest. Fact-based information are readily available information points, that can be in the public domain, and that allow the user to better understand the world around him or her. Examples include but are not limited to sports scores, stock ticker information, weather updates, horoscope information, fitness information and news updates.

Upon reception by the wearable computing device, the unassociated information elements are categorized and classified. The categorization and classification can be the result of evaluation of associated meta-data for the unassociated information element, usually the content of the unassociated information element and the source. Some unassociated information elements may require some sort of user interaction based on the type of the unassociated information element received, which may be added to the unassociated information element upon reception.

An example data structure capable of representing an unassociated information element internal to a computing device may take the form of a JavaScript Object Notation (JSON) object. As JSON is very flexible, the member data fields of a representative JSON object may include but are not limited to an “id”, “time”, “duration”, “layout”, “reminders”, and “actions.” As JSON supports nesting, each of these components may also have sub-components that further define their behavior. Below as code example 1 is a basic example of JSON implemented unassociated information element.

{
“id”: “example-element”,
“time”: “2015-03-19T18:00:00Z”,
“duration”: 12,
“layout”: { ... }
}

In this example only the “id,” “time” field and the “layout” field are required member data fields, as they are required to properly display an unassociated information element on the wearable computing device. Other member data fields in this example are optional. In other examples, other fields may also be required.

FIG. 1 is a block diagram illustrating a system of devices providing unassociated information elements from multiple sources according to one example. The system includes a well-defined software interface 140 for the collection of the unassociated information elements.

An unassociated information element is received by the well-defined software interface 140 from any number of connected devices. Connected devices, as demonstrated in this example, include but are not limited to PDAs 130, personal computers 110, automobiles 170, smart devices 160 including smart phone or smart watches, data servers 120 and home automation components 150, illustrated by a smart thermostat. The connections can be wired, wireless or a combination.

Connected devices, in this example, only need to be able to access the well-defined software interface 140 by a networking or communication protocol, and properly provide the unassociated information element to the well-defined software interface 140 by utilizing the proper application programming interface (API). An API suitable for one example would be a one that conforms to Representational State Transfer (REST) architectural constraints, or is a RESTful API.

Connected devices need an implementation for communication of the unassociated information elements to the well-defined software interface 140. A standards based defined protocol for the transmission and reception of unassociated information elements can be used. In one embodiment, this may be a proprietary protocol. In another embodiment, it can be a standards based defined protocol for the transmission and reception of the JSON encoded unassociated information elements. An example of an application layer protocol operable to carry the JSON payload, is hypertext transfer protocol secure (HTTPS). Utilizing the HTTPS request methods would enable a data source to push unassociated information elements to wearable devices. For example, creating an unassociated information element uses the HTTPS PUT command. Similarly updating an unassociated information element, the same HTTPS PUT command may be used, but the JSON payload would be adapted to reference the original unassociated information element by a unique identifier, thereby overwriting the original unassociated information element and updating every field present in the JSON payload. Below as code example 2 is an example of a HTTPS PUT request of a JSON implemented element by the application curl.

curl -X PUT https://timeline-
api.getpebble.com/v1/user/pins/reservation-1234567 \
--header “Content-Type: application/json” \
--header “X-User-Token: a70b23d3820e9ee640aeb590fdf03a56” \
-d @element.json

In the above example the X-User-Token field corresponds to a unique token that is unique per user per application that provides unassociated information elements. The element.json is the JSON encoded unassociated information element itself.

Analogously to the creation of an unassociated information element, a HTTPS DELETE command may be used for the removal of an unassociated information element. Utilizing a unique identifier in the JSON payload, the specific unassociated information element may be targeted as in code example 3.

curl -X DELETE https://timeline-
api.getpebble.com/v1/user/pins/reservation-1234567 \
--header “Content-Type: application/json” \
--header “X-User-Token: a70b23d3820e9ee640aeb590fdf03a56” \
-d @element.json

Accessible to the well-defined software interface 140 is a smart device 160. In this example, the smart device 160 illustrated by a smart phone operates as a bi-directional relay device to a wearable computing device 180, illustrated by a smart watch. The smart device 160 and the wearable computing device 180 are paired and communicate via a wireless communication technology such as Bluetooth® or Zigbee. Alternatively a wired or combination communication technology could be used for communication between the devices as well. In other embodiments, the smart device 160 may be a wearable device that communicates directly with the well-defined software interface 140. Alternatively, the wearable computing device 180 may be connected directly to the well-defined software interface 140 via a wireless communication technology such as WiFi® or 4G LTE.

In this example, the smart device 160 relays RESTful commands to the well-defined software interface 140. In another example, the wearable computing device 180 can send RESTful commands directly to the well-defined software interface 140. The RESTful command includes an unassociated information element or an unassociated information element update provided back to the well-defined software interface 140.

In another example, the wearable computing device 180 provides the smart device 160 with proprietary commands, which upon receipt are converted in a RESTful command to be transmitted to the well-defined software interface 140.

FIG. 2A is a flowchart illustrating a technique for receiving, displaying, and navigating unassociated information elements according to one example.

The flowchart begins with a start block 210.

At block 220, one or more unassociated information elements are received. These unassociated information elements are received from multiple sources, which in many cases is the reason why they are unassociated. Unassociated information elements once received may already include meta-data. In one embodiment, the unassociated information elements, once received, are assigned specific meta-data. The meta-data is derived from the source and the content of the unassociated information element itself. The unassociated information elements include but are not limited to emails, short message service (SMS) text messages, emails, Instagram notifications, Facebook notifications, calendar events, and current weather status.

Alternatively, one or more unassociated information elements may be received pre-ordered. This most likely occurs when the one or more elements are from a single source, or from a preprocessor, such as a paired mobile device.

Additionally, at any given point during the flow, one or more unassociated information element updates may be received 220 and the iterative nature of the processing allows the flow to restart upon the reception at block 220.

At block 230, the unassociated information element updates are assigned meta-data to associate them with their original unassociated information element. The meta-data comprises source and content information that enables the unassociated information element update to be related back to the original unassociated information element. The updates can change the content of the original unassociated information element or add to that content.

At block 240, the one or more of the unassociated information elements, any unassociated information element updates and the assigned meta-data are logically organized. The unassociated information elements and the respective updates are merged in this process using the meta-data to provide a set of unassociated information elements to be logically organized. In one example of logical organization, the unassociated information elements would be ordered by the time in which they were received. Alternatively, logical organization could be taken by the source of the unassociated information elements, as well as the content of the unassociated information elements, or any combination or permutation of these. Examples would include organizing and displaying received SMS text messages in alphanumeric order from the contact or the telephone number from which the messages were received. The result of the logical organization is that logically adjacent to a given organized unassociated information element, either above or below, is a preceding and a following organized unassociated information element.

If the received one or more unassociated elements are pre-ordered, they may be processed as described since the received pre-ordered elements may overlap with elements already present in the logical organization. However, if it is determined that the pre-ordered elements do not overlap with elements already present in the logical organization, they may be inserted as a batch directly into the logical organization with minimal comparison against other elements. This is accomplished by observing the first pre-ordered element and the last pre-ordered element, and determining a range established by the first pre-ordered element and the last pre-ordered element. The range is then compared against the logical organization to determine if any existing elements in the logical ordering are within that range.

At block 260, the relevant elements from the logical organization of the one or more organized unassociated information elements are provided to a display device. The display device is implemented via liquid crystal display, e-paper, OLED display or even a cathode ray tube. The relevant elements are formatted and provided to the display device for display. In many cases the relevant elements are displayed in the order in the logical organization. In other cases related organized unassociated information elements can be displayed simultaneously. For example, calendar event elements are combined with weather forecast elements to provide the user context for their calendar appointment.

At block 270, the logical ordering of one or more organized unassociated information elements displayed upon the display device is navigated by the usage of an input device. The input device implementation includes but is not limited to buttons, motion, scroll bars, touch screen, or voice commands. Utilizing the input device, the user advances a focus through the logical ordering of one or more organized information unassociated elements, across the display device. The input devices also allows the user to retreat the focus through the logical ordering of one or more organized unassociated information elements.

The flowchart ends at block 280.

FIG. 2B is an alternative of FIG. 2A. In the example of FIG. 2B, the flow omits step 230 in which meta data is assigned to the unassociated information elements. Updates to existing unassociated information elements are correlated not by meta data, but instead by the presented fields that are unique to the initial unassociated information element and its subsequent updates or by a time component.

FIGS. 3A, 3B, 3C, 3D, and 3E are illustrations demonstrating a technique for updating an unassociated information element based on the context of another unassociated information element according to one example.

In this example, FIG. 3A is a baselined state where the wearable computing device 301 displays two unassociated information elements. An unassociated information element depicting sunrise 306 and an unassociated information element depicting sunset 308 are displayed. Upon drilldown into either a sunrise 306 element or a sunset 308 element, a weather forecast is displayed for that portion of the day. Under normal operation, the weather forecast is for the local area, in which the wearable computing device 301 is physically located. Drill down into any element may be accomplished by pressing the select input button 310, while the element is aligned correspondingly with the select input button 310.

FIG. 3B is an updated state of the wearable computing device 302 illustrating the typical usage behavior of the selection of the sunrise 306 or the sunset 308 element. The pressing of the select input button 310 drills down into a weather forecast for the local area 312. In this example, the wearable 302 is located in San Jose, the temperature is 74 degrees Fahrenheit, and the sky is cloudy.

FIG. 3C is an updated state of the wearable computing device 303 where a new unassociated information element has been inserted into the display occurring between the sunrise 306 and the sunset 308. A reminder information element for a flight to Denver 314 has been inserted into the display. The sunset 308 element is updated to reflect the correct time for the event in the area where the user is traveling. In this instance, the sunset 308 element was updated to reflect the sunset time of Denver at 7:04 P.M.

FIG. 3D is a further updated state of the wearable computing device 304 where the navigation has advanced in time, past the reminder information element for a flight to Denver 314 and to the sunset 308 unassociated information element. By pressing the select input button 310, the user may drill down into the forecast details for the day corresponding to the unassociated information element for sunset 308.

FIG. 3E is the state of the wearable computing device 305 after the select input button 310 was pressed. The display shows the weather forecast 318 corresponding to the sunrise or sunset selected. In this example, the weather for Denver is going to be 60 degrees Fahrenheit and rainy. The context and content of the reminder information element for the flight to Denver 310, determines whether and how the weather forecast 318 gets updated.

Alternatively, the weather forecast 318 without the context and content of the reminder information element for the flight to Denver 314, would instead not be updated prior to departing and would display the weather forecast information for the current location until the user reacquires locational information upon arriving at the destination. The wearable computing device 304 would not update the weather forecast 318 as the context would indicate no change in location, until arrival. The utilization of the reminder information element for the flight to Denver 314 is advantageous in that it allows the user to more effectively use the wearable computing device for planning purposes prior to departure.

FIGS. 4A, 4B, and 4C are illustrations demonstrating a technique for navigating a logical ordering of future ordered information elements.

For this example, the ordered information elements are ordered chronologically. The content and source of the ordered information element can help determine the ordering relationship. Calendar events that are specifically time-based are ordered based on when the event is scheduled to occur. SMS text messages and missed telephone calls, which do not correspond to any scheduled event, are ordered based on the time at which they were received. Interval events, such as fitness metrics, are ordered individually at the time at which they were sampled. Alternatively, the ordering can be based on other relationships between the ordered information elements, including source or content.

In this example, the start state 401 for the device for viewing the ordered information elements begins with a watch face 404. The watch face 404 displays the current time for the user's frame of reference. Additionally, the wearable computing device 400 provides an input device to navigate the ordered information elements. In this example, buttons 407, 408, 410 are provided for navigation, however, other implementations including a touch screen, voice commands, or gestures could be used. Specific to this example, one button 410 is provided for advancing navigation. The advancing navigation button 410, when pushed, changes the watch face 404 to display present and future ordered information elements in FIG. 4B.

The present and future state 402 displays the present ordered information element 406 chronologically following and a future ordered information element 409.

In this example, a present ordered information element 406 is shown. As mentioned previously, the content and source can help determine the ordering relationship for the ordered information elements. The present ordered information element 406, a calendar appointment for the weekly staff meeting, is ordered based on when that event occurs, not when the ordered information element for that appointment was received.

Also shown is a future ordered information element 409 at the bottom of the display. The future ordered information element 409 is displayed adding context to the user's view. In this example, the future ordered information element 409 is an entry from the public transit schedule. Likewise to the present ordered information element 406, the future ordered information element 409 is ordered based on when the event is to occur, not when the future ordered information element 409 containing the future ordered information element 409 was received, all determined based on the content and source of the future ordered information element 409.

The present and future state 402 provide the input devices, buttons 407, 408, 410, for navigational purposes. The bottom button 410 is now functionally an advancing button and is used to advance to a future state 403.

The future state 403 displays future ordered information elements 412, 413, 414 which chronologically occur in the future. Each ordered information element is displayed with the time 411 in which they are ordered and occur.

As displayed here, different future ordered information element 412, 413, 414 types can be displayed simultaneously. First future ordered information element 412, displayed indicating 5:30 PM, is a public transit schedule of interest. Second future ordered information element 413, displayed indicating 6:00 PM is a sporting event of interest on ESPN. Third future ordered information element 414, displayed indicating 7:15 PM, is a weather event of notice, the sun setting and the beginning of night. Each one of these future ordered information elements would have come from different sources and are unrelated to one another, yet are arranged and placed in a useful view for the user.

FIGS. 5A, 5B and 5C are illustrations demonstrating a technique for navigating a logical ordering of past ordered information elements.

For this example, similar to FIGS. 4A, 4B, and 4C, the ordered information elements are ordered chronologically.

In this example, the start state 501 for the device 500 for viewing the elements begins with a watch face 504. The watch face 504 displays the current time for the user's frame of reference. Additionally, the device 500 provides an input device to navigate the past ordered information elements. In this example, buttons 507, 508, 509 are provided for navigation, however, other implementations including a touch screen, voice commands, or gestures could be used. Specific to this example a button 507 is provided for retreating navigation. The retreating navigation button 507, when pushed, changes the watch face 504 to display past ordered information elements.

The past state 502 displays the past ordered information elements 506, 510 that are chronologically occurring in the past.

In this example, a past ordered information element 510 is shown. As mentioned previously, the content and source determine the ordering relationship for the ordered information element. The focused past ordered information element 510 happens to be a news update, based on stock market information and can be ordered and displayed based on when the update was received.

FIG. 5B shows another past ordered information element 506 which occurred prior to the focused past ordered information element 510. In this example, the past ordered information element 506 is a calendar appointment for lunch. Unlike the past ordered information element 510 displayed as a news update, the past ordered information element 506 illustrated by the lunch appointment, is ordered based on the content of the past ordered information element 506, not when the past ordered information element 506 was received.

The past state 502 provides input devices for navigational purposes. A retreating button 511 is provided to retreat further into past ordered information elements 503.

The further past state 503 displays past ordered information elements 513, 514, 515 which chronologically occur in the past. Each past ordered information element 513, 514, 515 is displayed with the time 512 in which they occurred.

As displayed here, different past ordered information element 513, 514, 515 types can be displayed simultaneously. First, displayed at 6:30 AM, is a past ordered information element 513 illustrated as a weather event of notice, sunrise. Second, displayed at 7:00 AM is a past ordered information element 514 representing a personal communication information in the form of a missed telephone call. Third, displayed at 11:15 AM, is a past ordered information element 515 for a calendar event for a lunch meeting. Each one of these past ordered information elements 513, 514, 515 come from different sources and are unrelated to one another, yet are arranged and placed in a useful view for the user.

Each ordered information element has a specific layout that may be configured for effective viewing by the user. As mentioned above, the ordered information element may be represented as a JSON object. A layout member may be used to present the information in a given fashion. A layout may comprise other data members including type, title, subtitle, body, and icon as in code example 4.

{
“id”: “example-element”,
“time”: “2015-03-19T18:00:00Z”,
“duration”: 12,
“layout”: {
“type”: “genericElement”,
“title”: “News at 6 o'clock”,
“tinyIcon”: “system://images/NOTIFICATION_FLAG”
}
}

Various member data fields will determine how the unassociated information element is displayed to the user. The “type” member data fields also may determine available members data fields and their layout. To contrast, a “calendar” type will have different member data fields than a “sports update” type to accommodate information relating to that specific event. The following code example 5 is an example in the different member data fields as determined by type.

//a calendar type layout
layout: {
“type”: “calendar”,
“title”: “Client Meeting”,
“locationName”: “Conf Room 1”,
“body”: “Discuss Client matters.”
}
//a sports type layout
layout: {
“type”: “sports”,
“title”: “Bulls at Bears”,
“subtitle”: “Halftime”,
“sportsGameState”: “in-game”,
“scoreAway”: “54”,
“scoreHome”: “52”,
“nameAway”: “Bulls”,
“nameAway”: “Bears”,
}

FIGS. 6A, 6B, and 6C are illustrations demonstrating a technique for receiving unassociated information elements and adding interactions to the unassociated information elements.

Depicted here is the receiving state 601 when wearable computing device 600 receives an unassociated information element. The unassociated information element 604 in this example is a SMS text message with a request for dinner from a known contact.

In this example, the wearable computing device 600 evaluates the unassociated information element 604 and determines what kind of unassociated information element 604 it is based on meta-data surrounding the unassociated information element 604. Usually the meta-data includes the message's source and the content. Since the unassociated information element 604 received was a SMS text message, the wearable computing device 600 determines the response is a SMS text message directed back to the sender. Based on the content, the wearable computing device 600, can additionally determine and present the user with a few options for responses.

Upon receiving the unassociated information element 604, the user may select to view some wearable computing device 600 responses by pressing the “select” button 605. The select button 605 moves the display into a selection display state 602 presenting the user with options of response to the reception of the unassociated information element 604. Alternatively, other methods of input may be implemented to move the view into the selection display state 602. Touch screen input devices utilize swiping gesture based input to navigate. Voice commands respond to verbal cues to navigate as well.

The selection display state 602 presents the user with a few options to quickly respond in an applicable way based on the content and source of the received unassociated information element 604. In this instance, the received unassociated information element 604 was a SMS text message, so the response would be a SMS text message. For other unassociated information element 604 types, such as emails, the response correspondingly would match.

As mentioned above, the unassociated information element in this example is represented in JSON. Each action may be identified in the unassociated information element as a nested JSON object identified with the “action” keyword. The “action” JSON object may comprise two data members: title and type. The title would be the character string that is displayed in the navigational context. The type may be a character string indicative of the action the wearable computing device performs when that specific action is selected. Below as code example 6 is the example JSON implemented element with actions added.

{
“id”: “example-element”,
“time”: “2015-03-19T18:00:00Z”,
“duration”: 12,
“layout”: {
“type”: “genericElement”,
“title”: “News at 6 o'clock”,
“tinyIcon”: “system://images/NOTIFICATION_FLAG”
}
“actions”: [
{
“title”: “Yes”,
“type”: “openWatchApp”,
“launchCode”: 15
},
{
“title”: “No”,
“type”: “openWatchApp”,
“launchCode”: 22
},
{
“title”: “Another time?”,
“type”: “openWatchApp”,
“launchCode”: 31
}
]
}

In the above example, the type keyword specifies opening the watchApp. The launchCode is presented as an argument to the specified watchApp for discrete processing of the user selected action.

Options presented in this example are in the affirmative with a “yes” 606, the negative with a “no” 607, and a proposal for a new time 608. Alternatively, options may include brief descriptions explaining the action or the unassociated information element 604 itself as well. Each response would be input by the corresponding input device, buttons 609, 610, 611, accompanying it, which in this example would be buttons 609, 610, 611 alongside the display. Alternatively, with touchscreen based input, the user could simply touch the option, or with voice command input, the user could simply speak the option.

The user in this instance selects the affirmative option 606. The device then sends the response to the original sender, and updates the unassociated information element 604.

In another example, the user may select an option that will send a response back to the sender directly in the time based view without changing the view. Some watchApps do not instantiate a new view to the user, and execute transparently in the background. This behavior is dependent on the watchApp implementation.

Based on the interaction selected, the unassociated information element may promote notifications itself. Just as the SMS response was sent, other notifications can be integrated into the user actions.

The unassociated information element 604 is updated and moved into the user's time-based view state 603. In this example, the response accepted the sender's request for dinner. The wearable computing device 600 then updated that received, now ordered information element 612, to include a future component and placed it in order of when it should occur 612. Effectively, the wearable computing device 600 changed a received SMS text message into a calendar appointment based on the user's response.

FIG. 7A is a block diagram of an exemplary wearable computing device.

A processor 708 provides the computational component for the wearable computing device 700. The processor 708 executes the software that manipulates the data structure representation of the unassociated information elements. Additionally, the processor 708 adds any user actions to the unassociated information elements.

The processor 708 is coupled to a bi-directional receiver 706. The bi-directional receiver 706 receives and transmits radio frequency messages to any communicatively coupled devices. The bi-directional receiver 706 is the main entry point for any unassociated information element.

Additionally, a memory 718 is coupled to the processor 708. The memory 718 hosts the data structure representation of the unassociated information elements. The memory 718 additionally contains the software that manipulates the data structure representation and also the software that generally provides the wearable computing device 700 functions, the software being stored in a non-volatile portion of the memory 718.

A display 704 is coupled to the processor 708. The display 704 renders the unassociated information elements once they have been manipulated by the processor 708 in accordance with the software.

A plurality of input devices 710, 712, 714, 716 are coupled to the processor 708. The input devices 710, 712, 714, 716 are represented as buttons. The input devices 710, 712, 714, 716 provide the user an interface to interact with the software executing on the processor 708.

A wearable computing device 700 hosts all of the internal devices providing interactive information elements to a user. The chassis 702 physically contains all of the components.

FIG. 7B is similar to FIG. 7A except that the display 704 is changed to a touchscreen and display 720 and input devices 710, 712, 714 have been removed. The touchscreen provides users input capabilities to replace input devices 710, 712, 714 and additional input options.

FIG. 7C is similar to FIG. 7B except input device 716 has been removed and all user input is accepted by the touchscreen and display 720.

FIG. 8 is a diagram demonstrating navigational state changes utilizing chronological ordering and buttons as input devices.

To further explain the nature of the navigational implementation of this example, FIG. 8 is illustrative of the changes in state based on button depresses.

Horizontally along the top of FIG. 8 are the states of the watch face state 802 which corresponds to 404 and 504 (in FIGS. 4A and 5A), a past state 804 which corresponds to 502 and 503 (in FIGS. 5B, and 5C), present state 806 represented as 406 in FIG. 4B, and future state 808 represented as 403 in FIG. 4C. Additionally, a drill down state 810 represents the user's selection of an item.

Vertically along the left of FIG. 8 are the buttons identified corresponding to those physically on the wearable computing device 700. Button one 812 corresponds with a return state button, depicted as 716. Button two 814 corresponds with a backward navigational motion through time, depicted by 710. Button three 816 corresponds with a selection action and is depicted by 712. Button four 818 corresponds with a forward navigational motion through time depicted by 714.

Button one 812 acts as a state reset button. No matter the state at which the wearable computing device is currently operating in, button one 812 returns it to the watch face state 802, as depicted by button one events 820.

Button two 814 acts as a past state 804 initiator. The only way to navigate into the past state 804, is by depressing button two 814 from the watch face state 802, which is depicted by the button two events 822. It is also possible to navigate into the present state from a future state by depressing button two 814.

Button three 816 acts as a drill down state 810 initiator. The drill down state 810 may be entered in from the past state 804, the present state 806, and the future state 808, as depicted by the button three events 824.

Button four 818 provides access to both the present state 806 as well as the future state 808. As depicted by the button four events 826, the initial push of button four 818 moves the wearable computing device 700 into the present state 806. Once in the present state 806, a subsequent push of button four 818 moves the wearable computing device 700 into the future state 806.

FIG. 9A is an example of an alternative embodiment utilizing different input device configurations.

The smart watch of 900 is a configuration utilizing a touchscreen for accepting user input. A touchscreen 902 such as in the touchscreen with touchscreen and display 720 may be utilized as the display device for the smart watch 900. Organized information elements 904, 906, 908 are displayed on the touchscreen 902 in a manner similar to other embodiments. Navigation of the organized information elements 904, 906, 908 may include swiping from the bottom of the touchscreen 902 to the top of the touchscreen 902 or from the right of the touchscreen 902 to the left of the touch screen 902. When the logical ordering of the organized information elements 904, 906, 908 is time based, this navigational input is consistent with advancing the display of the organized information elements 904, 906, 908 forward in time. Similarly, another navigational input may include swiping from the top of the touchscreen 902 to the bottom of the touchscreen 902 or from the left of the touchscreen 902 to the right of the touchscreen 902. Again, if the logical ordering of the organized information elements 904, 906, 908 is time based, this navigational input is consistent with retreating the display of the organized information elements 904, 906, 908 backward in time. Alternatively, as can be appreciated by one skilled in the art, with touch screen 902, different types of swiping in one or many directions may be used to achieve the ability to retreat and advance the display of organized information elements.

Utilizing the touchscreen 902, the user may use long presses to select an organized information element 904, 906, 908 leading the touchscreen 902 to display more information about the selected organized information element 904, 906, 908 in a drilldown screen.

Alternatively, via the touchscreen 902, the user may similarly use a double tap gesture, to select an organized information element 904, 906, 908 leading the touchscreen 902 to display more information about the selected organized information element 904, 906, 908 in a drilldown screen.

By swiping the touchscreen 902 from left to right, the user may return to the previously displayed screen.

FIG. 9B is similar to FIG. 9A except that by rotating a scroll bar 910, the user may return to the previously displayed screen or retreat and advance the display of organized information elements as described above. The scroll bar 910 may also be used to wake the device from a power-conserving state.

In alternative embodiments, scroll bar 910 may also be a button. Many combinations of input mechanisms are possible to achieve the described navigation. For example, a scroll bar by itself, a scroll bar with a touch screen, one button, one or more buttons, touch screen with a button, touch screen with a scroll bar, touch screen with multiple buttons and many other configurations of user input devices.

FIGS. 10A, 10B, and 10C are examples of alternative embodiments utilizing multiple logical orderings of unassociated information elements.

A wearable computing device 1000 with two displays of ordered unassociated information elements. In this example, there is a time based ordering of elements 1004 displayed, and a source based ordering of elements 1010 displayed. A touchscreen 1014 is used as the input device.

In state 1000 both the time based ordering of elements 1004 and source based ordering of elements 1010 are displayed simultaneously on the wearable computing device 1000. In this example, the current time 1008 is displayed as well.

As the user utilizes the touchscreen 1014 with a swiping gesture (upward in one embodiment), the state of the wearable computing device changes to a second display state 1002. In the second display state 1002, the time based ordering of elements 1006 has incremented into a future event. The opposite swiping motion advances the time based ordering of elements 1006 in time. The source based ordering of elements 1012 also advances with the swiping motion to another informational element organized by source.

Alternatively, the user may utilize the touchscreen 1014 with a downward swiping gesture (in one embodiment) to change the state of the wearable computing device to a third display state 1016. The third display state 1016 includes the time based ordering of elements 1018 retreating into the past. The source based ordering of elements 1020 retreat to the previous element in the internal logical ordering of the unassociated information elements.

In this example, the user may tap the touchscreen 1014 either in the area of the source based ordering of elements 1010, 1012, 1020 or the area of the time based ordering of elements 1004, 1006, 1018 to display more information about that particular element.

In other examples, a single swiping gesture can control the navigation of both the source based ordering of elements 1010, 1012, 1020 and the time based ordering of elements 1004, 1006, 1018. Alternatively, the touchscreen 1014 may be operable to detect a localized swiping gesture limited to an area corresponding to the source based ordering of elements 1010, 1012, 1020 or the time based ordering of elements and navigate each independently. A combination of the approaches is applicable as well, where a single swiping gesture not localized to the area of the source based ordering of elements 1010, 1012, 1020 or the time based ordering of elements 1004, 1006, 1018 controls the navigation of both, yet localized swiping gestures controls them independently.

This example may include more than two logical orderings of unassociated information elements, as there are many ways to logically order and display the unassociated information elements.

FIGS. 11A, 11B, 11C, 11D, and 11E are illustrations demonstrating a technique for automatically inserting elements based on future events.

In this example, FIG. 11A is a baselined state where the wearable computing device 1101 displays two unassociated information elements. An unassociated information element depicting sunrise 1106 and an unassociated information element depicting sunset 1108 are displayed.

FIG. 11B is the state of the wearable computing device 1102 where time has passed and an unassociated informational element has been inserted into the display. A fitness interval informational element 1112 was inserted to notify the user that thirty minutes of walking was completed at 3:30 P.M. As time is progressing into the future, the display has updated to remove the past sunrise 1106 from view, and now includes an element for tomorrow's sunrise 1110. Navigation to tomorrow's sunrise 1110 can be accomplished by the pressing of an advancing navigation input button 1114.

FIG. 11C is the state of the wearable computing device 1103 prior to the drill down into tomorrow's sunrise 1116. By pressing the select input button 1116, the user may drill down into the forecast details for the day corresponding to the element for tomorrow's sunrise.

FIG. 11D is the state of the wearable computing device 1104 after the select input button 1116 was pressed. The display shows the weather forecast 1120 corresponding to the sunrise or sunset previously selected. In this example, the local weather for the day corresponding to the sunrise or sunset previously selected is going to be 60 degrees Fahrenheit and rainy. The user may elect to return to the list view of unassociated informational elements by pressing the back input button 1118.

FIG. 11E is the state of the wearable computing device 1105 after the back input button 1118 was pressed from the drill down display. Based on the amount of activity depicted in the fitness interval information element 1112, user preferences indicating a fitness goal that the user is working to attain, and the context of the weather forecast 1120, the wearable computing device 1105 generates a suggestive reminder information element 1122 that brings attention to user that they may not be able to meet their fitness goal in the future because of the weather forecast 1120.

Alternatively to FIGS. 11C and 11D, the wearable computing device 1105 may add the suggestive reminder information element 1122 without any navigational effort. As long as the fitness interval information element 1112 and the weather forecast 1120 is contained within the drill down of tomorrow's sunrise 1110, the wearable computing device 1105 may insert the suggestive reminder information element 1122 without any additional user interaction.

While a smart watch has been used as the illustrated wearable device, other wearable device examples are brooch, pin, necklace, earring, and bike helmet.

As mentioned above, past attempts at providing an elegant and functional wearable computing experience have been insufficient. Utilizing unassociated information elements as an input, the apparatus contained within manipulates the unassociated elements in an intelligent fashion and displays them in a manner that allows the user the opportunity to interact, easily and unobtrusively.

It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described examples may be used in combination with each other. Many other examples will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention therefore should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.

Claims

1. An apparatus comprising: a processor, configured to: receive from multiple sources two or more elements of unassociated information, wherein at least two of the elements of unassociated information are different, the at least two different elements of unassociated information selected from personal communication information, event information, and fact-based information,wherein the two or more elements of unassociated information include meta-data, the meta-data for each of the elements of unassociated information including a time component, andwherein the time component for the personal communication information is a receipt time, the time component for the event information in an event start time, and the time component for the fact-based information is a sampling time or an event start time;order in a logical ordering the elements of unassociated information based on the time components of the meta-data; andprovide at least a portion of the logical ordering for display, wherein the portion of the logical ordering corresponds to the at least two different elements of unassociated information; anda display device coupled to the processor configured to display the portion of the logical ordering, wherein the processor is configured to accept user input from an input device to cause the display to either advance or retreat chronologically in the logical ordering from a displayed element of unassociated information, wherein the time component is different among at least two elements of unassociated information.

2. The apparatus of claim 1, wherein the processor is configured to assign meta-data to each of the elements of unassociated information.

3. The apparatus of claim 2, wherein the processor is configured to associate a user interaction component with one or more of the elements of unassociated information, the user interaction involving the input device.

4. The apparatus of claim 1, wherein the processor is configured to receive additional elements of unassociated information including meta-data, the meta-data for each of the additional elements of unassociated information including a time component;correlate the additional elements of unassociated information to previously received elements of unassociated information occurring in the future; andupdate the elements of unassociated information occurring in the future to reflect anticipated changes in user activities based on the additional elements of unassociated information.

5. The apparatus of claim 1, wherein the apparatus is an electronic wearable device selected from a smart watch, brooch, pin, necklace, earring, and bike helmet.

6. The apparatus of claim 1, wherein sources of the elements of unassociated information comprise personal computers, PDAs, smart phones, smart watches, home automation components, automotive sensors, email servers, or other servers.

7. An electronic wearable device comprising: a processor, anda memory coupled to the processor on which are stored instructions that when executed cause the processor to: receive elements of unassociated information, wherein the elements of unassociated information include meta-data, the meta-data for each of the elements of unassociated information including a time component,wherein the time component is selected from a receipt time, an event start time, and a sampling time, andwherein the time component is different among at least two elements of unassociated information;order in a logical ordering the elements of unassociated information based on the time components of the meta-data; anddisplay at least a portion of the logical ordering, wherein the portion of the logical ordering corresponds to the at least two elements of unassociated information with different time components.

8. The electronic wearable device of claim 7, wherein the stored instructions that when executed further cause the processor to assign meta-data to each of the elements of unassociated information.

9. The electronic wearable device of claim 7, wherein the elements of unassociated information include at least two different types of information selected from personal communication information, event information, and fact-based information, andwherein the time component for the personal communication information is the receipt time, the time component for the event information in the event start time, and the time component for the fact-based information is the sampling time or an event start time.

10. The electronic wearable device of claim 9, wherein the personal communication information is selected from emails, texts, tweets, and Facebook notifications.

11. The electronic wearable device of claim 9, wherein the event information is selected from calendar appointments and reminders.

12. The electronic wearable device of claim 9, wherein the fact-based information is selected from a sports score, stock ticker data, a weather update, and a news update.

13. The electronic wearable device of claim 7, wherein the stored instructions that when executed further cause the processor to associate a user interaction component with one or more of the elements of unassociated information.

14. The electronic wearable device of claim 7, wherein the multiple sources comprise personal computers, PDAs, smart phones, home automation components, automotive sensors, email servers, or other servers.

15. The electronic wearable device of claim 7, wherein the instructions that when executed further cause the processor to: receive additional elements of unassociated information including meta-data, the meta-data for each of the additional elements of unassociated information including a time component;correlate by the meta-data the additional elements of unassociated information to previously received elements of unassociated information occurring in the future; andupdate the elements of unassociated information occurring in the future to reflect anticipated changes in user activities based on the additional elements of unassociated information.

16. A method comprising: receiving by a processor of a wearable computing device elements of unassociated information, wherein the elements of unassociated information include meta-data, the meta-data for each of the elements of unassociated information including a time component,wherein the time component is selected from a receipt time, an event start time, and a sampling time, andwherein the time component is different among at least two elements of unassociated information;ordering by the processor in a logical ordering the elements of unassociated information based on the time components of the meta-data; anddisplaying on a display of the wearable computing device at least a portion of the logical ordering, wherein the portion of the logical ordering corresponds to the at least two elements of unassociated information with different time components.

17. The method of claim 16 further comprising: receiving by the processor additional elements of unassociated information including meta-data, the meta-data for each of the additional elements of unassociated information including a time component;correlating by the processor the meta-data of the additional elements of unassociated information to previously received elements of unassociated information occurring in the future; andupdating by the processor the elements of unassociated information occurring in the future to reflect anticipated changes in user activities based on the additional elements of unassociated information.

18. The method of claim 16 further comprising, assigning by the processor meta-data to each of the elements of unassociated information.

19. The method of claim 16, wherein the elements of unassociated information include at least two different types of information selected from personal communication information, event information, and fact-based information, andwherein the time component for the personal communication information is the receipt time, the time component for the event information in the event start time, and the time component for the fact-based information is the sampling time or an event start time.

20. The method of claim 17, wherein the additional elements of unassociated information include any information selected from personal communication information, event information, and fact-based information, andwherein the time component is different among the at least two elements of unassociated information and at least one of the additional elements of unassociated information.