Patent Publication Number: US-2016246453-A1

Title: Smartwatch or other wearable device configured to intuitively interact with a user

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application claims priority to U.S. Provisional Application Ser. No. 62/120,238 entitled “A SMARTWATCH OR OTHER NOTIFICATION DEVICE CONFIGURED TO INTUITIVELY INTERACT WITH A USER BASED ON TIME AND THE WAY THE USER USES THE DEVICE” filed Feb. 24, 2015, which is incorporated by reference in its entirety herein. 
     This application is related to U.S. application Ser. No. ______, entitled “A SMARTWATCH OR OTHER WEARABLE DEVICE CONFIGURED TO INTELLIGENTLY INTERACT WITH A USER,” filed concurrently herewith, which is incorporated by reference in its entirety herein. 
    
    
     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&#39;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&#39;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 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, associates, and navigates unassociated information elements. 
    
    
     
       BRIEF DESCRIPTION OF DRAWINGS 
         FIGS. 1A, 1B, 1C, 1D, and 1E  are illustrations demonstrating a technique for receiving informational elements and adding interactions to them. 
         FIGS. 2A, 2B and 2C  are illustrations demonstrating a technique for navigating a logical ordering of future ordered information elements. 
         FIGS. 3A, 3B and 3C  are illustrations demonstrating a technique for navigating a logical ordering of past ordered information elements. 
         FIGS. 4A, 4B and 4C  are an illustrations demonstrating a technique for receiving information elements and adding interactions to the elements. 
         FIGS. 5A, 5B and 5C  are block diagrams of wearable computing devices illustrating the relationship between the components of a wearable computing device. 
         FIG. 6  is a diagram demonstrating navigational state changes utilizing chronological ordering and buttons as input devices. 
         FIGS. 7A and 7B  are flowcharts illustrating techniques for receiving, displaying, and navigating unassociated information elements according to one example. 
     
    
    
     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&#39;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&#39;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. 
       FIGS. 1A, 1B, 1C, 1D, and 1E  are illustrations demonstrating a technique for receiving informational elements and adding interactions to them. 
     In this example,  FIG. 1A  is a baselined state where the wearable computing device  101  displays two unassociated information elements. An unassociated information element depicting sunrise  106  and an unassociated information element depicting sunset  108  are displayed. Upon drilldown into either a sunrise  106  element or a sunset  108  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  101  is physically located. Drill down into any element may be accomplished by pressing the select input button  110 , while the element is aligned correspondingly with the select input button  110 . 
       FIG. 1B  is an updated state of the wearable computing device  102  illustrating the typical usage behavior of the selection of the sunrise  106  or the sunset  108  element. The pressing of the select input button  110  drills down into a weather forecast for the local area  112 . In this example, the wearable  102  is located in San Jose, the temperature is 74 degrees Fahrenheit, and the sky is cloudy. 
       FIG. 1C  is an updated state of the wearable computing device  103  where a new unassociated information element has been inserted into the display occurring between the sunrise  106  and the sunset  108 . A reminder information element for a ride on Caltrain NB 126  114  has been inserted into the display. 
       FIG. 1D  is a further updated state of the wearable computing device  104  where the navigation has advanced in time by the use of a forward navigational button  116 , to the reminder information element for the ride on Caltrain NB 126  114 . The user may drill down into the information element for the ride on Caltrain NB 126  114  by using the select input button  110 . 
       FIG. 1E  is the drill down into the element for the ride on Caltrain NB 126  118 . In this example, the wearable computing device  105  anticipates the users interaction and presents an option to purchase a ticket  120  with the select input button  110 . 
       FIGS. 2A, 2B, and 2C  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  201  for the device for viewing the ordered information elements begins with a watch face  204 . The watch face  204  displays the current time for the user&#39;s frame of reference. Additionally, the wearable computing device  200  provides an input device to navigate the ordered information elements. In this example, buttons  207 ,  208 ,  210  are provided for navigation, however, other implementations including a touch screen, voice commands, or gestures could be used. Specific to this example, one button  210  is provided for advancing navigation. The advancing navigation button  210 , when pushed, changes the watch face  204  to display present and future ordered information elements in  FIG. 2B . 
     The present and future state  202  displays the present ordered information element  206  chronologically following and a future ordered information element  209 . 
     In this example, a present ordered information element  206  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  206 , 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  209  at the bottom of the display. The future ordered information element  209  is displayed adding context to the user&#39;s view. In this example, the future ordered information element  209  is an entry from the public transit schedule. Likewise to the present ordered information element  206 , the future ordered information element  209  is ordered based on when the event is to occur, not when the future ordered information element  209  was received, all determined based on the content and source of the future ordered information element  209 . 
     The present and future state  202  provide the input devices, buttons  207 ,  208 ,  210 , for navigational purposes. The bottom button  210  is now functionally an advancing button and is used to advance to a future state  203 . 
     The future state  203  displays future ordered information elements  212 ,  213 ,  214  which chronologically occur in the future. Each ordered information element is displayed with the time  211  in which they are ordered and occur. 
     As displayed here, different future ordered information element  212 ,  213 ,  214  types can be displayed simultaneously. First future ordered information element  212 , displayed indicating 5:30 PM, is a public transit schedule of interest. Second future ordered information element  213 , displayed indicating 6:00 PM is a sporting event of interest on ESPN. Third future ordered information element  214 , 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. 3A, 3B and 3C  are illustrations demonstrating a technique for navigating a logical ordering of past ordered information elements. 
     For this example, similar to  FIGS. 2A, 2B, and 2C , the ordered information elements are ordered chronologically. 
     In this example, the start state  301  for the device  300  for viewing the elements begins with a watch face  304 . The watch face  304  displays the current time for the user&#39;s frame of reference. Additionally, the device  300  provides an input device to navigate the past ordered information elements. In this example, buttons  307 ,  308 ,  309  are provided for navigation, however, other implementations including a touch screen, voice commands, or gestures could be used. Specific to this example a button  307  is provided for retreating navigation. The retreating navigation button  307 , when pushed, changes the watch face  304  to display past ordered information elements. 
     The past state  302  displays the past ordered information elements  306 ,  310  that are chronologically occurring in the past. 
     In this example, a past ordered information element  310  is shown. As mentioned previously, the content and source determine the ordering relationship for the ordered information element. The focused past ordered information element  310  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. 3B  shows another past ordered information element  306  which occurred prior to the focused past ordered information element  310 . In this example, the past ordered information element  306  is a calendar appointment for lunch. Unlike the past ordered information element  310  displayed as a news update, the past ordered information element  306  illustrated by the lunch appointment, is ordered based on the content of the past ordered information element  306 , not when the past ordered information element  306  was received. 
     The past state  302  provides input devices for navigational purposes. A retreating button  311  is provided to retreat further into past ordered information elements  303 . 
     The further past state  303  displays past ordered information elements  313 ,  314 ,  315  which chronologically occur in the past. Each past ordered information element  313 ,  314 ,  315  is displayed with the time  312  in which they occurred. 
     As displayed here, different past ordered information element  313 ,  314 ,  315  types can be displayed simultaneously. First, displayed at 6:30 AM, is a past ordered information element  313  illustrated as a weather event of notice, sunrise. Second, displayed at 7:00 AM is a past ordered information element  314  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  315  for a calendar event for a lunch meeting. Each one of these past ordered information elements  313 ,  314 ,  315  come from different sources and are unrelated to one another, yet are arranged and placed in a useful view for the user. 
       FIGS. 4A, 4B, and 4C  are illustrations demonstrating a technique for receiving unassociated information elements and adding interactions to the unassociated information elements. 
     Depicted here is the receiving state  401  when wearable computing device  400  receives an unassociated information element. The unassociated information element  404  in this example is a SMS text message with a request for dinner from a known contact. 
     In this example, the wearable computing device  400  evaluates the unassociated information element  404  and determines what kind of unassociated information element  404  it is based on meta-data surrounding the unassociated information element  404 . Usually the meta-data includes the message&#39;s source and the content. Since the unassociated information element  404  received was a SMS text message, the wearable computing device  400  determines the response is a SMS text message directed back to the sender. Based on the content, the wearable computing device  400 , can additionally determine and present the user with a few options for responses. 
     Upon receiving the unassociated information element  404 , the user may select to view some wearable computing device  400  responses by pressing the “select” button  405 . The select button  405  moves the display into a selection display state  402  presenting the user with options of response to the reception of the unassociated information element  404 . Alternatively, other methods of input may be implemented to move the view into the selection display state  402 . 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  402  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  404 . In this instance, the received unassociated information element  404  was a SMS text message, so the response would be a SMS text message. For other unassociated information element  404  types, such as emails, the response correspondingly would match. 
     Options presented in this example are in the affirmative with a “yes”  406 , the negative with a “no”  407 , and a proposal for a new time  408 . Alternatively, options may include brief descriptions explaining the action or the unassociated information element  404  itself as well. Each response would be input by the corresponding input device, buttons  409 ,  410 ,  411 , accompanying it, which in this example would be buttons  409 ,  410 ,  411  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  406 . The device then sends the response to the original sender, and updates the unassociated information element  404 . 
     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  404  is updated and moved into the user&#39;s time-based view state  403 . In this example, the response accepted the sender&#39;s request for dinner. The wearable computing device  400  then updated that received, now ordered information element  412 , to include a future component and placed it in order of when it should occur 412. Effectively, the wearable computing device  400  changed a received SMS text message into a calendar appointment based on the user&#39;s response. 
       FIG. 5A  is a block diagram of an exemplary wearable computing device. 
     A processor  508  provides the computational component for the wearable computing device  500 . The processor  508  executes the software that manipulates the data structure representation of the unassociated information elements. Additionally, the processor  508  adds any user actions to the unassociated information elements. 
     The processor  508  is coupled to a bi-directional receiver  506 . The bi-directional receiver  506  receives and transmits radio frequency messages to any communicatively coupled devices. The bi-directional receiver  506  is the main entry point for any unassociated information element. 
     Additionally, a memory  518  is coupled to the processor  508 . The memory  518  hosts the data structure representation of the unassociated information elements. The memory  518  additionally contains the software that manipulates the data structure representation and also the software that generally provides the wearable computing device  500  functions, the software being stored in a non-volatile portion of the memory  518 . 
     A display  504  is coupled to the processor  508 . The display  504  renders the unassociated information elements once they have been manipulated by the processor  508  in accordance with the software. 
     A plurality of input devices  510 ,  512 ,  514 ,  516  are coupled to the processor  508 . The input devices  510 ,  512 ,  514 ,  516  are represented as buttons. The input devices  510 ,  512 ,  514 ,  516  provide the user an interface to interact with the software executing on the processor  508 . 
     A wearable computing device  500  hosts all of the internal devices providing interactive information elements to a user. The chassis  502  physically contains all of the components. 
       FIG. 5B  is similar to  FIG. 5A  except that the display  504  is changed to a touchscreen and display  520  and input devices  510 ,  512 ,  514  have been removed. The touchscreen provides users input capabilities to replace input devices  510 ,  512 ,  514  and additional input options. 
       FIG. 5C  is similar to  FIG. 5B  except input device  516  has been removed and all user input is accepted by the touchscreen and display  520 . 
       FIG. 6  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. 6  is illustrative of the changes in state based on button depresses. 
     Horizontally along the top of  FIG. 6  are the states of the watch face state  602  which corresponds to  204  and  304  (in  FIGS. 2A and 3A ), a past state  604  which corresponds to  302  and  303  (in  FIGS. 3B and 3C ), present state  606  represented as  206  in  FIG. 2B , and future state  608  represented as  203  in  FIG. 2C . Additionally, a drill down state  610  represents the user&#39;s selection of an item. 
     Vertically along the left of  FIG. 6  are the buttons identified corresponding to those physically on the wearable computing device  500 . Button one  612  corresponds with a return state button, depicted as  516 . Button two  614  corresponds with a backward navigational motion through time, depicted by  510 . Button three  616  corresponds with a selection action and is depicted by  512 . Button four  618  corresponds with a forward navigational motion through time depicted by  514 . 
     Button one  612  acts as a state reset button. No matter the state at which the wearable computing device is currently operating in, button one  612  returns it to the watch face state  602 , as depicted by button one events  620 . 
     Button two  614  acts as a past state  604  initiator. The only way to navigate into the past state  604 , is by depressing button two  614  from the watch face state  602 , which is depicted by the button two events  622 . It is also possible to navigate into the present state from a future state by depressing button two  614 . 
     Button three  616  acts as a drill down state  610  initiator. The drill down state  610  may be entered in from the past state  604 , the present state  606 , and the future state  608 , as depicted by the button three events  624 . 
     Button four  618  provides access to both the present state  606  as well as the future state  608 . As depicted by the button four events  626 , the initial push of button four  618  moves the wearable computing device  500  into the present state  606 . Once in the present state  606 , a subsequent push of button four  618  moves the wearable computing device  500  into the future state  606 . 
       FIG. 7A  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  710 . 
     At block  720 , 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 elements may be received  720  and the iterative nature of the processing allows the flow to restart upon the reception at block  720 . 
     At block  730 , the unassociated information elements are assigned meta-data. The meta-data comprises source and content information. The meta-data is utilized to find like unassociated information elements and apply an ordering. For example meta-data based ordering for emails could be from “Source A” and further ordered based on their content. 
     At block  740 , the one or more of the unassociated information elements, and the assigned meta-data are 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  760 , 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  770 , 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  780 . 
       FIG. 7B  is an alternative of  FIG. 7A . In the example of  FIG. 7B , the flow omits step  730  in which meta-data is assigned to the unassociated information elements. 
     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.