Patent Grant
11430571
The following disclosure relates generally to data management and, more specifically, to aggregating and sharing wellness data.
Approximately 133 million Americans currently suffer from at least one chronic condition. This number is expected to rise to approximately 165 million by the year 2020. As a result, the cost of healthcare in the United States is expected to increase dramatically. Attempts have been made to improve the health of individuals by providing them with tools to monitor and track their wellness data. Wellness data can generally include any type of data associated with a person's health, such as their weight, heart rate, blood pressure, blood glucose level, medication compliance, activity level, or the like. Users can monitor their wellness using devices, such as blood pressure cuffs, blood glucose monitors, electrocardiograms, step counters, and the like. Software applications (e.g., Apps) associated with each of these devices have also been developed to allow users to track their wellness data over time. While each application can be used to view useful information about a user's health, current applications are limited in their ability to allow users to store, view, and share wellness data collected by different devices.
The present disclosure relates to processes for aggregating and sharing wellness data. One example process can include causing a display of an aggregated view of a plurality of types of wellness data, wherein the aggregated view comprises a plurality of partitions, each partition of the plurality of partitions associated with a type of the plurality of types of wellness data; receiving a selection of a partition of the plurality of partitions; and causing a display of an expanded view of the selected partition of the plurality of partitions.
Another example process can include causing, on a device, a display of a plurality of partitions, wherein each partition of the plurality of partitions is associated with a type of wellness data of a plurality of types of wellness data; in response to detecting a change in an orientation of the device, selecting a subset of the plurality of partitions; and causing a display of the selected subset of the plurality of partitions.
Another example process can include causing a display of a first plurality of partitions associated with a first user, wherein each partition of the first plurality of partitions is associated with a type of wellness data of the first user; and in response to receiving a request to view a second plurality of partitions associated with a second user, causing a display of a second plurality of partitions associated with a second user, wherein each partition of the second plurality of partitions is associated with a type of wellness data of the second user.
Another example process can include receiving an identification of a user authorized to access a set of wellness data; in response to detecting an update to the set of wellness data, transmitting a notification to the user authorized to access the set of wellness data notifying the user authorized to access the set of wellness data that the update to the set of wellness data has been detected; and transmitting at least a portion of the set of wellness data to the user authorized to access the set of wellness data.
Another example process can include receiving, from a first user, a request to access wellness data associated with a second user; transmitting, to the second user, a request to authorize the first user to access the wellness data associated with the second user; and in response to receiving an authorization from the second user, transmitting the wellness data associated with the second user to the first user.
Another example process can include, at an electronic device comprising a display: displaying, on the display, a graph comprising a first data-set representation of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation of a second data set in which a second dependent variable varies as the independent variable changes, wherein the first data-set representation is associated with a first range of vertical positions within the graph and the second data-set representation is associated with a second range of vertical positions within the graph. The process can further include detecting, at a respective location on the display, a user input; in response to detecting the user input: in accordance with a determination that the respective location is within the first range of vertical positions associated with the first data-set representation, displaying, on the display, an indication that the first data-set representation has been selected; and in accordance with a determination that the respective location is within the second range of vertical positions associated with the second data-set representation, displaying, on the display, an indication that the second data-set representation has been selected.
Another example process can include, at an electronic device comprising a display: while the electronic device is in a locked state: detecting a request to display emergency information about a user of the device; and in response to detecting the request, displaying, on the display, an emergency information interface comprising emergency information about the user of the device without unlocking the device.
Another example process can include, at an electronic device: receiving, from a user, information identifying a plurality of approved sources of wellness data, wherein the information identifying the plurality of approved sources identifies one or more types of wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database; and receiving, from the user, information identifying a plurality of approved destinations of wellness data, wherein the information identifying the plurality of approved destinations identifies one or more types of wellness data that are approved to be accessed from the wellness database by the plurality of approved destinations of wellness data.
The present disclosure also relates to methods for approving sources and destinations of wellness data with granularity. One example process can include receiving, from a user, information identifying a plurality of approved sources of wellness data, wherein the information identifying the plurality of approved sources identifies one or more types of wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database; and receiving, from the user, information identifying a plurality of approved destinations of wellness data, wherein the information identifying the plurality of approved destinations identifies one or more types of wellness data that are approved to be accessed from the wellness database by the plurality of approved destinations of wellness data.
In some examples, the plurality of approved sources comprise an electronic device or software application.
In some examples, the plurality of approved destinations comprise an electronic device or software application.
In some examples, the plurality of approved sources are ranked amongst each other.
In some examples, the method further includes identifying a first wellness data entry in the wellness database that was received from a first approved source of the plurality of approved sources, the first wellness data entry comprising a first wellness data type and a first timestamp; and identifying a second wellness data entry in the wellness database that was received from a second approved source of the plurality of approved sources, the second wellness data entry comprising a second wellness data type and a second timestamp, wherein the first wellness data type and the second wellness data type are the same, and wherein the first timestamp is within a threshold length of time from the second timestamp.
In some examples, the first approved source has been identified by the user as being preferred over the second approved source, and wherein the method further comprises using the first wellness data entry instead of using the second wellness data entry.
In some examples, the first approved source has been identified by the user as being preferred over the second approved source, and wherein the method further comprises prioritizing the first wellness data entry over the second wellness data entry.
In some examples, the method further includes in accordance with a determination that the first wellness data entry is prioritized over the second wellness data entry, using the first wellness data entry instead of using the second wellness data entry.
In some examples, the second approved source has been identified by the user as being preferred over the first approved source, and wherein the method further comprises prioritizing the second wellness data entry over the first wellness data entry.
In some examples, the method further includes in accordance with a determination that the second wellness data entry is prioritized over the first wellness data entry, using the second wellness data entry instead of using the first wellness data entry.
In some examples, the method further includes displaying, on the display, a plurality of categories of wellness data stored in the wellness database.
In some examples, the method further includes detecting a selection of a category of wellness data from the displayed plurality of categories of wellness data; and in response to detecting the selection of the category of wellness data, displaying, on the display, one or more sub-categories of the category of wellness data.
In some examples, the method further includes detecting a selection of a sub-category from the displayed one or more sub-categories; and in response to detecting the selection of the sub-category, displaying, on the display, a detailed view of the sub-category.
In some examples, the detailed view of the sub-category comprises a graph representation of the sub-category of wellness data over time and a numerical daily value of the sub-category of wellness data.
In some examples, the detailed view of the sub-category further comprises an input field for entering a wellness data entry, and wherein the method further comprises receiving a wellness data entry to be stored in the wellness database that was input into the input field.
In some examples, the detailed view of the sub-category further comprises a textual description of the sub-category.
In some examples, the detailed view of the sub-category further comprises an option to view wellness data entries corresponding to the sub-category, and wherein the method further comprises displaying, on the display, a plurality of wellness data entries corresponding to the sub-category stored in the wellness database.
In some examples, each of the plurality of wellness data entries comprises a numerical value of the data entry, a timestamp, and an identification of a source of the data entry.
In some examples, the detailed view of the sub-category further comprises an option to share wellness data, and wherein the method further includes displaying, on the display, a data sharing interface comprising the plurality of approved sources and the plurality of approved destinations.
In some examples, the method further includes detecting a request to reorder the displayed plurality of approved sources; and in response to detecting the request to reorder the displayed plurality of approved sources, reordering the displayed plurality of approved sources in accordance with the detected request to reorder the displayed plurality of approved sources.
In some examples, the data sharing interface further comprises options to add an approved destination to the plurality of approved destinations and to remove an approved destination from the plurality of approved destinations.
In some examples, the method further includes receiving a search query; and displaying, on the display, one or more sub-categories of the plurality of categories that match the search query, wherein the displayed one or more sub-categories that match the search query are color-coded based on their respective categories.
In some examples, the method further includes displaying, on the display, a source interface comprising a list of known sources.
In some examples, the source interface further comprises a numerical indicator associated a known source of the known sources that represents a number of new types of wellness data that can be provided by the known source.
In some examples, the method further includes detecting a selection of a known source from the displayed list of known sources; and in response to detecting the selection of the known source, displaying, on the display, a list of types of wellness data that the known source can provide.
In some examples, the list of types of wellness data that the known source can provide comprises a selectable option for each of the types of wellness data that the known source can provide to approve or reject the associated type of wellness data.
In some examples, the method further includes detecting a selection of the selectable option for a type of wellness data that the known source can provide; and in response to detecting the selection of the selectable option, approving or rejecting the type of wellness data that the known source can provide in accordance with the detected selection of the selectable option.
Devices and non-transitory computer-readable storage media for performing these processes are also provided.
In the following description of the disclosure and examples, reference is made to the accompanying drawings in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be practiced and structural changes can be made without departing from the scope of the disclosure.
The present disclosure relates to aggregating and sharing wellness data. The wellness data can be received by a user device from any number of sensors external or internal to the user device, from a user manually entering the wellness data, or from other users or entities. The user device can securely store the wellness data on the user device and transmit the wellness data to be stored on a remote database. A user of the device can share some or all of the wellness data with friends, relatives, caregivers, healthcare providers, or the like. The user device can further display a user's wellness data in an aggregated view of different types of wellness data. For example, the aggregated view can include a set of partitions, where each partition corresponds to a different type of wellness data. Wellness data of other users can also be viewed if authorizations from those users have been received. In some examples, the partitions can be displayed as having the appearance and associated animations of a stack of cards, where each card corresponds to a different partition (and thus, a different type of wellness data). In this view of stacked cards, each card can display a partial view of a portion of its corresponding wellness data. When the user selects one of the cards, a first expanded view of the selected card including at least one of first reconfigured data, additional data, or an expanded view of the original data can be displayed. A second expanded view of the selected card can be displayed in response to a change in the orientation of the user device. The second expanded view can include at least one of second reconfigured data, additional data, or an expanded view of the original data can be displayed. In one example, the second expanded view can include a graph of the wellness data over time.
Exemplary Devices
Examples of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some examples, the device includes portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Examples of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), are, optionally, used. It should also be understood that, in some examples, the device is not a portable communications device, but is a desktop computer or a television with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad). In some examples, the device does not have a touch screen display and/or a touch pad, but rather is capable of outputting display information (such as the user interfaces of the disclosure) for display on a separate display device, and capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad). In some examples, the device has a display, but is capable of receiving input information from a separate input device having one or more input mechanisms (such as one or more buttons, a touch screen display and/or a touch pad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick. Further, as described above, it should be understood that the described electronic device, display and touch-sensitive surface are optionally distributed amongst two or more devices. Therefore, as used in this disclosure, information displayed on the electronic device or by the electronic device is optionally used to describe information outputted by the electronic device for display on a separate display device (touch-sensitive or not). Similarly, as used in this disclosure, input received on the electronic device (e.g., touch input received on a touch-sensitive surface of the electronic device) is optionally used to describe input received on a separate input device, from which the electronic device receives input information.
The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, a television channel browsing application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Below,
Although the following description uses terms “first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes,” “including,” “comprises,” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 may also include one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device 100.
It should be noted that the icon labels illustrated in
Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch-sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse-based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of devices 100 and/or 300 (
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector” so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the second threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective operation or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm optionally includes one or more of: an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. In some circumstances, these smoothing algorithms eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments the contact-detection intensity threshold is zero. In some embodiments, the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter,” where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90%, or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the descriptions of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
System Overview
System 500 can include one or more user devices 510 including any electronic device, such as a mobile phone, tablet computer, desktop computer, laptop computer, PDA, or the like. In some examples, user device 510 can include a device similar or identical to those shown in
User device 510 can be configured to receive wellness or non-wellness data from various sources and can store the received data in the wellness database 511. For example, user device 510 can be configured to receive wellness or non-wellness data from sensors 502, 504, 506, and 508. These sensors can include any type of sensor capable of obtaining wellness data, such as a biometric sensor, activity tracker, or the like. For example, sensors 502, 504, 506, and 508 can include, but are not limited to, a scale, blood pressure cuff, blood glucose monitor, electrocardiogram, step counter, gyroscope, accelerometer, SpO2 sensor, respiration sensor, posture sensor, stress sensor, photoplethysmogram, galvanic skin response sensor, temperature sensor, asthma inhaler, or the like. Sensors 502, 504, 506, and 508 can also include other types of sensors, such as audio sensors, ambient light sensors, electromagnetic sensors, touch sensors, capacitive sensors, and the like, for obtaining non-wellness data, such as situational data, temporal data, personal data, contact data, and the like data. In some examples, each sensor can be a separate device, while, in other examples, any combination of two or more of the sensors can be included within a single device. For example, the gyroscope, accelerometer, photoplethysmogram, galvanic skin response sensor, and temperature sensor can be included within a wearable electronic device, such as a smart watch, while the scale, blood pressure cuff, blood glucose monitor, SpO2 sensor, respiration sensor, posture sensor, stress sensor, and asthma inhaler can each be separate devices. While specific examples are provided, it should be appreciated that other sensors can be used and other combinations of sensors can be combined into a single device.
Sensors 502, 504, 506, and 508 can be used to measure wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, sensors 502, 504, 506, and 508 can be used to obtain a single measurement or multiple measurements over a length of time. Sensors 502, 504, 506, and 508 can be configured to measure wellness or non-wellness data at the same intervals of time, or can be configured to measure wellness or non-wellness data at different intervals of time. These intervals may be set by a user or may be a default setting for each sensor. Additionally, sensors 502, 504, 506, 508 can be used to measure wellness or non-wellness data at any time or location desired by the user. Moreover, sensors 502, 504, 506, and 508 can be used with or without the supervision of a healthcare provider. For example, a user can use sensors 502, 504, 506, and 508 to obtain sensor measurements at home without the supervision of a medical professional.
In some examples, user device 510 can include software sensor applications 513 (e.g., third party applications) associated with each of sensors 502, 504, 506, and 508 for interfacing with the sensors to allow user device 510 to receive the wellness or non-wellness data. In these examples, the applications 513 can use the device's APIs to store the wellness or non-wellness data in the wellness database 511 of user device 510. In some examples, the software sensor applications 513 can be Apps and device 510 can be a smart phone, tablet computer, or the like. It should be understood that “third party” can correspond to an entity different than the manufacturer of device 510 and/or the entity that created and/or maintains the operating system of device 510. In these instances, third party applications and their corresponding sensors can communicate and function within the operating system of device 510 according to a predefined device protocol associated with device 510.
The applications 513 can similarly use the device's APIs to access data stored in the wellness database 511. In other examples, user device 510 can be configured to share one or more communication formats with sensors 502, 504, 506, and 508 to allow user device 510 to receive and interpret the wellness or non-wellness data from the sensors. The received data can then be stored in the wellness database 511 of user device 510.
User device 510 can further receive wellness or non-wellness data from its own wellness or non-wellness data sensors 515, such as a GPS sensor, clock, gyroscope, accelerometer, or the like, from a user interacting with user device 510, from another entity, such as a physician, or from other non-sensor sources. For example, using the device's APIs, wellness or non-wellness data can be received from applications 517 on user device 510, such as a clock application, a calendaring application, a gaming application, an application from a healthcare provider, a messaging application, or the like. The wellness or non-wellness data from the applications 517 can originate from a user interacting with the applications, a remote database (e.g., database for a medical website), a healthcare provider institution (e.g., via the institution's App), or the like. In these examples, the usage of the application 517 (e.g., how long you play a video game application, when you play the video game, number of times interacting with a stock application, number of times interacting with a social networking application, length of time interacting with a social networking application, etc.), usage of user device 510 (e.g., length of time on the phone or number of text messages sent as determined from a phone payment application, time spent browsing the Internet as determined from the device's browser, etc.), time spent listening to music as determined from a music or streaming radio application, time spent using a remote application for controlling a television, amount of time or money spent on shopping websites, time spent on pornographic websites (e.g., to identify addictions), weather data from a weather application (e.g., to determine how weather affects a user's health), type of events occurring in the user's life as determined from a calendar (e.g., meetings, birthdays, holidays, etc.), interactions with certain people as determined from a contact list and/or calendar application and/or a messaging application and/or phone of user device 510, or the like, can be received by user device 510 and stored in the wellness database 511.
In some examples, default or user-selected settings can be provided to restrict the access that at least one application (e.g., at least one of applications 513 and 517) on user device 510 has to the wellness database 511 of user device 510 (for both storage and retrieval purposes) and to the sensor data generated by sensors 515 within user device 510 and/or sensor data generated by sensors 502, 504, 506, and 508. For example, an application for tracking a user's running sessions can be granted access to the data generated by the GPS sensor of user device 510, but can be prevented from accessing the user's blood pressure data stored in the wellness database 511. In some examples, an entity other than the owner of user device 510 can set the authorization settings for various applications on user device 510. For example, the manufacturer of user device 510 and/or the entity that created and/or maintains the operating system of user device 510 can evaluate the applications to determine if they should be given access to the user's wellness data and/or sensor data generated or received by user device 510. In some examples, these settings can be overridden by the user.
User device 510 can further include a display for displaying the stored wellness data or non-wellness data. A more detailed description of the interface of the display of user device 510 is described below with respect to
In some examples, user server 514 and user database 516 can be configured to securely store a user's wellness or non-wellness data using a public/private key system that only allows the owner of the wellness or non-wellness data to decrypt the data. Additionally, the wellness or non-wellness data stored in user database 516 can be stored anonymously (e.g., without identifying and/or personal information about the user, such as a legal name, username, time and location data, or the like). In this way, other users, hackers, and the owner/operator of user database 516 cannot determine the identity of the user associated with the data stored in database 516. In some examples, a user can access their wellness or non-wellness data stored in user database 516 from a user device that is different than the one used to upload the wellness or non-wellness data to user server 514. In these instances, the user can be required to provide login credentials to access their wellness or non-wellness data. User server 514 can be configured to perform the authorization process to restrict access to the data within user database 516.
System 600 can further include any number of other user devices 522 and 524 coupled to network 512. In some examples, user devices 522 and 524 can be operated by the same user as user device 510. In these instances, the user can access their wellness or non-wellness data stored in user database 516 by providing user server 514 with the appropriate credentials. In some examples, wellness and non-wellness data can be synced between user database 516 and one or more of user device 510, 522, and 524. In other examples, the user of user devices 522 and 524 can be a person that is different than the user of user device 510. In these examples, the users of devices 522 and 524 cannot access the wellness or non-wellness data of the user of user device 510 without the authorization of the user of user device 510. If authorization is given, wellness or non-wellness data can be shared with the users of user devices 522 and 524. The sharing of this data will be discussed in greater detail below with respect to
In some examples, any of the above described sources of wellness or non-wellness data can be configured to measure, generate, or receive wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. As such, the wellness or non-wellness data can similarly be stored or updated in wellness database 511 or user database 516 continuously, intermittently, periodically, or at any other desired frequency or interval of time. The frequencies and intervals of time used for measuring, generating, receiving, or storing wellness or non-wellness can be the same or they can be different. Additionally, these frequencies and intervals can be default values or they can be set by a user to provide the user with wellness or non-wellness data that has been updated within a desired length of time.
While not shown, it should be appreciated that many other user devices can be coupled to user server 514 through network 512 to collect and store wellness or non-wellness data for other users in a manner similar to that described above.
User Database
As discussed above, a user's wellness or non-wellness data can be stored in user database 516 and can be shared with other users with the owning user's authorization. The other users can be any type of user, such as a friend, family member, caregiver, physician, social media provider, or the like. Different types and levels of authorization can be granted for the wellness or non-wellness data contained in wellness database 516.
In some examples, the shared wellness or non-wellness data can be pushed to the user device (e.g., user device 522 or 524) of the authorized other user.
At block 704, the user's wellness or non-wellness data can be monitored by the user's device to determine if any updates to the data have been made. If no update has been made, the process can repeat block 704. If, however, an addition or change to the user's wellness or non-wellness data has been identified, the process can proceed to block 706. In some examples, any change to the user's wellness or non-wellness data can cause process 700 to proceed to block 706, while, in other examples, only changes to certain types of the user's wellness or non-wellness data can cause process 700 to proceed to block 706.
At block 706, a notification can be transmitted to one or more authorized other users. For example, a notification can be transmitted from the user's device (e.g., user device 510) to the device of the authorized other user (e.g., user device 522 or 524). The notification can include a message indicating that an update has been made to the user's wellness or non-wellness data. The process can then proceed to block 708.
At block 708, the updated wellness or non-wellness data can be transmitted to the authorized other user. For example, the updated wellness or non-wellness data can be transmitted from the user's device (e.g., user device 510) to the device of the authorized other user (e.g., user device 522 or 524). In some examples, this data can only be transmitted if the authorized other user indicated a desire to view the updated wellness or non-wellness data, while, in other examples, the updated wellness or non-wellness data can be transmitted to the user device of the authorized other user without receiving a request from the authorized other user to view the data.
The pushing of wellness or non-wellness data performed using process 700 can be useful in situations in which a user wants to keep a caregiver or family member (or other user) updated with his/her wellness or non-wellness data. For instance, an elderly parent can grant authorization to push his/her wellness or non-wellness data to a child to allow the child to easily monitor the elderly user's health or medication compliance without having to constantly request this information from the parent.
In other examples, a user's wellness or non-wellness data can be shared with other users by allowing other users to pull the wellness or non-wellness data.
At block 804, a request for authorization can be transmitted to the user associated with the requested wellness or non-wellness data. In some examples, the request can be transmitted from the user device (e.g., user device 522 or 524) of the requesting user to the user device (e.g., user device 510) of the user associated with the requested data. The request can then be displayed to the user associated with the requested data by the user's device (e.g., user device 510).
At block 806, it can be determined if an authorization has been received from the user associated with the requested wellness or non-wellness data. The authorization can be received in any manner. For example, a prompt can be displayed to the user associated with the requested data on their user device 510. If authorization is denied, the process can return to block 802. If, however, authorization is granted, the process can proceed to block 808.
At block 808, the requested wellness or non-wellness data can be transmitted to the entity that requested access to the wellness or non-wellness data at block 802. The requested wellness or non-wellness data can be transmitted from the user's device (e.g., user device 510) to the requesting entity's device (e.g., user device 522 or 524).
In some examples, if authorization to access a user's wellness or non-wellness data is granted before a request is made at block 802, process 800 can proceed from block 802 to block 808 without performing blocks 804 or 806. For example, if a parent grants access to their wellness or non-wellness data to their child, a request by the child for the parent's wellness or non-wellness data can be received at block 802 and the requested wellness or non-wellness data can be transmitted to the child at block 808 without any intervening action by the parent.
The pulling of wellness or non-wellness data using process 800 can be useful in situations where an authorized other user does not want to be constantly updated with updates to a user's wellness or non-wellness data, but would like occasional access to the data. For example, a physician may want access to a patient's medical records and wellness or non-wellness data just prior to meeting with the patient. In this situation, the physician can request the patient's wellness or non-wellness data and can either receive the requested data or cause a request to be sent to the user device 510 of the patient. In response to receiving an authorization from the patient, the requested data can be sent from user device 510 to the physician's computing device (e.g., user device 522 or 524). In some examples, the received wellness or non-wellness data can be added to an electronic medical record (EMR) associated with the user.
In some examples, whether using a push or pull sharing model, the wellness or non-wellness data of a user may not be permanently stored on the user device of authorized other users. In this way, authorization to these other users can be revoked, causing the user's wellness data to be inaccessible by the formerly authorized other users. Additionally, in some examples, reports detailing or summarizing a user's wellness or non-wellness data can be generated. These reports can then be transmitted via email, secure transfer, or the like, to any desired recipient. In yet other examples, user device 510 can be configured to communicate some or all of the user's wellness or non-wellness data, such as medical insurance information, blood type, medical history, etc., to medical personnel using near field communication or another communication protocol. This can be useful when checking in to a hospital or during medical emergencies when relevant medical data is needed.
Aggregated Data View
As discussed above, user device 510 can be configured to aggregate wellness or non-wellness data associated with a user that was received from the user, from one or more sensors 502, 504, 506, and 508, or from anon-sensor source. User device 510 can also be configured to display the user's aggregated wellness or non-wellness data in various ways using various interfaces.
Interface 900 can include a first partition 902 displayed at the top of the interface that can include an identifier (e.g., name) of the user. As shown, the name “John Smith” of the user of user device 510 is displayed on partition 902. Interface 900 can further include button 901 for viewing wellness data associated with other users. This feature is described in greater detail below with respect to
Interface 900 can further include another partition 904 displayed adjacent to partition 902 such that it appears to be overlapping partition 902 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 904 includes the word “Weight” to indicate that the partition contains weight data associated with the user “John Smith.” Partition 904 can further include the most recent weight “185 lbs” of “John Smith.”
Interface 900 can further include another partition 906 displayed adjacent to partition 904 such that it appears to be overlapping partition 904 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 906 includes the words “Blood Sugar” to indicate that the partition contains blood sugar data associated with the user “John Smith.” Partition 906 can further include the most recent blood sugar level “164 mg/dL” of “John Smith.”
Interface 900 can further include another partition 908 displayed adjacent to partition 906 such that it appears to be overlapping partition 906 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion the partition's wellness data. Specifically, partition 908 includes the words “Blood Pressure” to indicate that the partition contains blood pressure data associated with the user “John Smith.” Partition 908 can further include the most recent blood pressure measurement “117/67 mmHg” of “John Smith.”
Interface 900 can further include another partition 910 displayed adjacent to partition 908 such that it appears to be overlapping partition 908 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion of the partition's wellness data. Specifically, partition 910 includes the word “Activity” to indicate that the partition contains activity data (e.g., calories burned) associated with the user “John Smith.” Partition 910 can further include the current daily number of calories burned “467 kcal” by “John Smith.”
Interface 900 can further include another partition 912 displayed adjacent to partition 910 such that it appears to be overlapping partition 910 like a stacked card. This partition can include an indication of the type of wellness data contained on the partition as well as a partial view (e.g., summary, example, or the like) of a portion of the partition's wellness data. Specifically, partition 912 includes the words “Heart Rate” to indicate that the partition contains heart rate data associated with the user “John Smith.” Partition 912 can further include the most recent heart rate measurement “122 bpm” of “John Smith.” Additionally, since partition 912 is at the top of the stack of partitions, additional information 914 and/or options 916 can be displayed on the face of the partition. In the illustrated example, the additional information includes the minimum, maximum, and resting heart rate of “John Smith” over the span of a week, which was selected using options 916.
The ordering of some or all of the partitions can be static or dynamic. For example, partition 902 containing the user's name can remain at the top of the display, while the remaining partitions can be ordered based on the time of day, how recently the wellness data associated with the partition is updated, the frequency that the wellness data associated with the partition is updated, whether a notable event is approaching (e.g., medication that should be taken, a sensor measurement that should be performed, etc.), or the like. The ordering can also be manually changed by the user. If interface 900 includes more partitions than can be displayed on a single screen, a vertical scrolling can be performed to display the remaining partitions. Alternatively, a 3D scrolling of the partitions may be performed to give the appearance of flipping through a stack of cards.
While specific example partition types have been provided above, it should be appreciated that partitions containing different types of wellness data can be included within interface 900. Additionally, users can generate customized partitions that can be used to display any desired type of user-entered data. For example, a partition can be created to track the medication compliance of a user. The user can enter the time, amount, and type of medicine taken and this data can be displayed on the created partition. Other custom partitions for different wellness data types, such as nutrition, sleep, smoking, or the like can also be generated.
Additionally, while specific examples of partial views (e.g., summary, example, or the like) of a portion of the partitions' wellness data have been provided above, it should be appreciated that the partial views can summarize or provide examples of the wellness data in different ways. For example, rather than display the most recent value of a particular wellness data type, a mean, mode, median, another single data point, or the like of the wellness data over all or a portion of time (e.g., a week, month, year, etc.) can be displayed on the partitions in the aggregated view. Alternatively, in other examples, a current and average value can be displayed on the partitions in the aggregated view. In yet other examples, the partitions in the aggregated view can include a display of a current value and a goal value for the type of wellness data.
The partitions 902, 904, 906, 908, 910, and 912 can be selected to display an expanded view of the partition containing reconfigured data, additional data, or an enlarged view of the original data contained on the partition. For example, a user can select a partition by tapping on the desired partition displayed on a touch sensitive display, can highlight and click on the partition using a mouse or other input device, or select the desired partition using any other input means. In response to a selection of a partition, user device 510 can hide the contents of the other partitions and display the selected partition on all or most of the display of user device 510.
For example,
In some examples, a user's wellness data used to generate the interfaces shown in
At block 1504, a selection of one of the displayed partitions can be received. The selection can be received by the user device, and can be in the form of a mouse click, tap on a touch sensitive display, or the like. In response to a selection of the partition, an expanded view of the selected partition can be displayed at block 1506. The expanded view can include a view showing a larger portion of the selected partition and at least one of reconfigured wellness data (e.g., a rearranged view of the wellness data displayed on the selected partition in the aggregated view displayed at block 1502), additional wellness data (e.g., wellness data that was not previously displayed on the selected partition in the aggregated view displayed at block 1502), or an enlarged view of the wellness data displayed in the aggregated view displayed at block 1502 (e.g., a larger view of the same wellness data displayed on the selected partition in the aggregated view displayed at block 1502). Additionally, partitions that were not selected can be reduced in size or removed from the display. For example, any of interfaces 1000, 1100, 1200, 1300, or 1400 can be displayed in response to a selection of partition 904, 906, 908, 910, or 912 of interface 900, respectively.
In some examples, the display presented at block 1506 can include a selectable option (e.g., button 1004) to share wellness data. In other examples, the display presented at block 1506 can further include a selectable option (e.g., partitions 1002) to cause the aggregated view containing partitions displayed at block 1502 to again be displayed. The process can then return to block 1504, where a selection of another partition can be received.
At block 1704, a change in orientation of the user device can be detected. For example, a gyroscope and/or an accelerometer within the user device can indicate that the orientation of the device has been changed from portrait to landscape. In response to a detected change in orientation by a threshold amount, the process can proceed to block 1706.
At block 1706, a subset of the plurality of partitions displayed at block 1702 can be selected for display. In some examples, the subset can be a predetermined subset of the plurality of partitions. In other examples, the subset can be selected based on user-defined preferences for display. In yet other examples, the subset of the plurality of partitions can be selected based on an analysis of the wellness data sets associated with each partition to determine if any of the types of wellness data are potentially correlated. If a potential correlation is identified, the partitions associated with the potentially correlated data can be selected at block 1706.
At block 1708, expanded views of the subset of partitions selected at block 1706 can be displayed. In some examples, the identifier for the type of wellness data displayed on the expanded view of the partition and/or the summary, example, or other view of the type of wellness data associated with the partition can be different than that shown on the partitions at block 1702. For example, the summary or example data on each expanded view can be replaced with a graph representation of the wellness data over time, as shown in
As discussed above, in some examples, the user of user device 510 can be granted access to the wellness data of other users. In these examples, user device 510 can allow the user to view the wellness data of other users in a similar format as discussed above with respect to
At block 2004, a request to view a second plurality of partitions of a second user can be received. The second user can be a user that has authorized the first user to view their wellness data as described above. In some examples, the request can include a user input to scroll the display of the first plurality of partitions displayed at block 2002 and can be received by the user device in the form of rotation of a mouse wheel, an arrow key on a keyboard, a touch and/or swipe on a touch sensitive display, or the like. Similar to the example shown in
At block 2006, a display of the second plurality of partitions associated with the second user can be displayed. In some examples, when the request to view the second plurality of partitions received at block 2004 included a request to scroll the display of the first plurality of partitions, the first plurality of partitions can be translated off the display in the direction of the scroll, while the second plurality of partitions can be translated onto the display in the same direction but from the opposite side of the display, as shown in
It should be appreciated that the processes described above can be combined. For example, process 1700 can be combined with process 1500 such that after the plurality of partitions are displayed at block 1502, a change in orientation of the user device can cause blocks 1704, 1706, and 1708 to be performed. Similarly, process 2000 can be combined with process 1500 such that after the plurality of partitions are displayed at block 1502, the receipt of a request to view partitions associated with other users can cause blocks 2004 and 2006 to be performed to display a plurality of partitions associated with another user.
As mentioned above, systems 500 and 600 can be configured to measure, generate, receive, or store wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. Processes 1500, 1700, and 2000 can similarly be performed to update the display of wellness or non-wellness data continuously, intermittently, periodically, or at any other desired frequency or interval of time. For example, the device performing process 1500, 1700, or 2000 can receive updated wellness or non-wellness data from wellness database 511 or user database 516 continuously, intermittently, periodically, or at any other desired frequency or interval of time. In some examples, the device performing process 1500, 1700, or 2000 can receive updates to all wellness or non-wellness data at the same frequency or interval of time. In other examples, the device performing process 1500, 1700, or 2000 can be configured to receive updates to different types of data at different frequencies or intervals of time. For example, heart rate data can be updated every second, while weight data can be updated daily. These intervals and frequencies can be default values or can be selected by the user.
Dashboard View
In some examples, a partition can include an identification of the type of wellness or non-wellness data that the partition represents (e.g., calories, steps, weight, or the like), a numerical daily value of the represented type of wellness or non-wellness data, and a graph representation of the represented type of wellness or non-wellness data. For example, partition 2102 can include the text “Calories” to indicate that it represents Calorie data, a current daily value 2110 of 1250 Calories burned, and a graph representation 2108 of the Calorie data over time throughout the day. Similarly, partition 2104 can include the text “Steps” to indicate that it represents step data, a current daily value 2111 of 3000 steps, and a graph representation 2109 of the step data over time throughout the day. Interface 2100 can further include a partial view of partition 2106 showing the text “Weight” to indicate that it represents weight data, as well as a daily value 2112 of 160 lbs. In the illustrated example, the graphs of each partition are non-overlapping with each other.
In some examples, the detailed view of the user's wellness or non-wellness data can include partitions not shown in interface 2100. In these examples, a user can initiate a scroll request by swiping up or down on a touch sensitive display, by clicking and dragging on a display using a mouse or other input device, by manipulating a scroll-wheel, by performing a swiping gesture on a touch pad, or the like. In response to detecting the scroll request, user device 510 can scroll the view of interface 2100 to display other partitions that were not previously displayed (or were partially displayed, such as partition 2106).
For example,
In some examples, the order of partitions within interface 2100 or 2200 can be changed in response to detecting a user request to reorder the partitions. In some examples, the request to reorder can include a selecting and holding of one of the partitions for greater than a threshold length of time. After detecting that the threshold length of time has elapsed, user device 510 can animate the partitions in a way that indicates that the partitions can be reordered. In some examples, the partitions can be reordered by dragging a selected partition to a desired location. However, in other examples, the partitions can be reordered in any other desired manner.
While only four partitions 2102, 2104, 2106, and 2116 are shown in the detailed view illustrated by interfaces 2100 and 2200, it should be appreciated that the detailed view can include additional partitions representing any number and any type of wellness or non-wellness data. Similar to partitions 2102, 2104, 2106, and 2116, these additional partitions can include identifications of the type of wellness or non-wellness data that the partitions represent, numerical daily values of the represented types of wellness or non-wellness data, and graph representations of the represented types of wellness or non-wellness data.
In some examples, a graph view of some or all of the wellness or non-wellness data displayed in the detailed view can be displayed in response to a graph-view input. In some examples, the graph-view input can include a detected change in orientation of user device 510. For example,
In some examples, the data-set representations can be displayed in a color based on the type of wellness or non-wellness data that it represents. For example, a data-set representation representing nutrition data can be displayed in one color, and a data-set representation of fitness data can be displayed in another. In some examples, the colors used for the different types of wellness or non-wellness data can correspond to the colors used to display the partitions in the detailed views of interfaces 2100 and 2200. For example, a partition representing a set of nutrition data can be displayed in the same color as a data-set representation representing the same set of nutrition data.
In some examples, the independent variable of the x-axis can be the same for all data-set representations shown in the graph view. For example, the time represented by the x-axis can be the same for each data-set representation.
In some examples, the dependent variable of the y-axis can be measured in a different unit for some or all of the data-set representations. For example, the dependent variable for data-set representation 2302 can be expressed in Calories, the dependent variable for data-set representation 2304 can be expressed in a number of steps, the dependent variable for data-set representation 2306 can be expressed in pounds (representing weight data), and the dependent variable for data-set representation 2308 can be expressed in mmHg (representing blood pressure data). Since these data-set representations having different units of measurement can be shown overlaid on the same display, a different vertical y-axis scaling can be used to display the various data-set representations. In some examples, to determine a vertical scale for one of the data-set representations, the minimum and maximum value of the represented data set that are to be displayed within the graph can be determined. For example, to determine the scaling factor for data-set representation 2302 representing Calorie data, the maximum and minimum values of the Calorie data can be determined over the span of time represented by the x-axis of the display. In the example shown in
In some examples, one or more of the displayed data-set representations can be selected to display additional data associated with the selected data-set representation. In some examples, for the purpose of selecting a particular data-set representation by a user, the data-set representations of the graph view shown in interface 2300 can be associated with a range (e.g., a unique range) of vertical positions within the graph. For example, the graph shown in interface 2300 can be divided into four ranges of vertical positions 2310, 2312, 2314, and 2316 separated by the dashed lines. In this example, data-set representation 2302 can be associated with first range of vertical positions 2310, data-set representation 2304 can be associated with second range of vertical positions 2312, data-set representation 2306 can be associated with third range of vertical positions 2314, and data-set representation 2308 can be associated with fourth range of vertical positions 2316. A selection of one of the data-set representations can be made by entering a user input within a range of vertical positions corresponding to the desired data-set representation, regardless of the horizontal position of the user input. For example, to select data-set representation 2302, a user input in the form of a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be made at location 2318 having a vertical position located within the first range of vertical positions 2310. In response to detecting the user input at location 2318 having a vertical position within first range 2310, user device 510 can display an indication that data-set representation 2302 was selected. For example,
In some examples, one of the data-set representations 2302, 2304, 2306, or 2308 can represent blood pressure data. In these examples, for purposes of generating the line of the data-set representation, the dependent variable for the blood pressure data can include an average of the diastolic and the systolic blood pressure. However, the numerical value displayed in response to a selection of the data-set representation for blood pressure data can include a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure associated with the time corresponding to the horizontal position of the user input.
In some examples, one of the data-set representations 2302, 2304, 2306, or 2308 can represent heart rate data. In these examples, the numerical value displayed in response to a selection of the data-set representation for heart rate data can include a high value for heart rate and a low value for heart rate associated with the time corresponding to the horizontal position of the user input.
In some examples, the indication of a selection displayed in response to detecting a user input can further include highlighting an area below the line of the selected data-set representation. For example, the area below the line of the selected data-set representation can be darkened, brightened, displayed with a different color, or otherwise highlighted relative to other portions of the graph to change the line graph into an area graph of the selected data set. In some examples, the data-set representations that are not currently selected can be removed from the display, greyed out, or otherwise made less visible within the graph.
In some examples, a user input can be continuously applied to the displayed graph and moved in a horizontal direction within one of the range of vertical positions to scrub through values of the selected data-set representation. For example, in response to detecting that the user input received at location 2318 is moved in the left direction, the circle marker displayed over data-set representation 2302 can be animated such that it appears to move along the line of data-set representation 2302 at horizontal positions corresponding to the current horizontal position of the user input. Similarly, the displayed value can change to reflect the value of the data set represented by data-set representation 2302 at the horizontal position of the user input.
In some examples, the vertical ranges of values within the graph associated with the data-set representations can be static. In other examples, the vertical ranges of values within the graph associated with the data-set representations can change. For example, in response to detecting a user input at a location within first range 2310, the size of first range 2310 can expand based on a length of time that the detected user input remains within first range 2310. As a result, the other vertical ranges can contract, or decrease in size. In some examples, the size of first range 2310 can expand to cover the entire graph. In other examples, the size of first range 2310 can expand to a predefined limit. Expanding the size of a selected range of vertical positions advantageously provides the user with a greater tolerance for vertical deviation as the user moves their user input in a horizontal direction to select different portions of a data-set representation.
In some examples, interface 2300 or 2400 can include a compare option 2320 to select the sets of wellness or non-wellness data that are to be displayed within the graph view. For example,
In some examples, the detailed view of the wellness or non-wellness data can be displayed in response to a detailed-view input received while any of interfaces 2300, 2400, or 2500 are being displayed. In some examples, the detailed-view input can include a detected change in orientation of user device 510. For example, interface 2100 or 2200 can be displayed in response to detecting a rotation of user device 510 to a portrait view.
While the graph view shown in interfaces 2300 and 2400 include four data-set representations, it should be appreciated that the graph can include any number of data-set representations. Additionally, the number of ranges of vertical positions can change based on the number of displayed data-set representations (e.g., to be equal to the number of displayed data-set representations). For example, if six data-set representations are displayed within the graph, then six discrete ranges of vertical positions can be associated with the data-set representations to allow a user to select the desired data-set representation.
As described below, process 2600 provides an intuitive way to select overlapping data-set representations in a graph view. The process allows a user to select a particular data-set representation without having to target a specific location on the data-set representation, which can be difficult at locations where multiple data-set representations overlap.
At block 2602, a graph view of wellness or non-wellness data can be displayed on a display of a user device (e.g., user device 510). For example, an interface similar or identical to interface 2300 or 2400 can be displayed. The graph view can include a first data-set representation (e.g., data set representation 2302) of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation (e.g., data set representation 2304) of a second data set in which a second dependent variable varies as the independent variable changes. The first data-set representation can be associated with a first range of vertical positions within the graph (e.g., first range 2310) and the second data-set representation can be associated with a second range of vertical positions within the graph (e.g., first range 2312).
In some examples, the first data-set representation can be displayed in the graph overlapping the second data-set representation. For example, data-set representations 2302, 2304, 2306, and 2308 are shown as overlapping in interfaces 2300 and 2400. In some examples, the first data-set representation and the second data-set representation can be colored-coded based on a type of data that they represent.
In some examples, the first data set can include a first set of wellness data, and the second data set can include a second set of wellness data. In some examples, the dependent variable for the first data set can be measured in different units from the dependent variable for the second data set.
In some examples, the first range of vertical positions can be uniquely associated with the first data-set representation, and the second range of vertical positions can be uniquely associated with the second data-set representation. For example, first range 2310 is uniquely associated with data-set representation 2302 and second range 2312 is uniquely associated with data-set representation 2304 in interfaces 2300 and 2400.
In some examples, a vertical scale for displaying the first data-set representation can be different from a vertical scale for displaying the second data-set representation. In these examples, displaying the graph can include determining a vertical scale for the first data-set representation based on the maximum and minimum values of the first dependent variable of the first data-set representation that are to be displayed in the graph. Displaying the graph can further include determining a vertical scale for the second data-set representation based on the maximum and minimum values of the second dependent variable of the second data-set representation that are to be displayed in the graph. In some examples, the vertical scale for the first data-set representation can be defined by a maximum vertical position within the graph corresponding to a first multiplying factor multiplied by the maximum value of the first dependent variable of the first data-set representation that are to be displayed in the graph, and a minimum vertical position within the graph corresponding to a second multiplying factor multiplied by the minimum value of the first dependent variable of the first data-set representation that are to be displayed in the graph. In some examples, the vertical scale for the second data-set representation can be defined by a maximum vertical position within the graph corresponding to a third multiplying factor multiplied by the maximum value of the second dependent variable of the second data-set representation that are to be displayed in the graph, and a minimum vertical position within the graph corresponding to a fourth multiplying factor multiplied by the minimum value of the second dependent variable of the second data-set representation that are to be displayed in the graph.
At block 2604, a user input can be detected at a location on the display. Detecting the user input can include detecting a touch or hover event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch or hover event on a touch pad, or the like.
At block 2606, a location of the user input can be determined. For example, the vertical and horizontal positions (e.g., y and x-axis coordinates) of the user input can be determined. In response to determining that the location of the user input on the display detected at block 2604 has a vertical position associated with the first range of vertical positions, an indication of a selection of the first data-set representation can be displayed. Alternatively, in response to determining that the location of the user input on the display detected at block 2604 has a vertical position associated with the second range of vertical positions, an indication of a selection of the second data-set representation can be displayed.
In some examples, displaying the indication of a selection can include displaying a marker overlaid on the selected data-set representation at a horizontal position corresponding to the horizontal position of the location of the user input. For example, a circle marker can be displayed over data-set representation 2302 in interface 2400 of
In some examples, the first data set or the second data set can include blood pressure data. In these examples, the displayed numerical value of the data entry can include a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure. In some examples, the dependent variable of the first data-set representation or the second data-set representation can include average of blood pressure values.
In other examples, the first data set or the second data set can include heart rate data. In these examples, the displayed numerical value of the data entry can include a high value for heart rate and a low value for heart rate.
In some examples, the first data-set representation can include a first line in the graph. In these examples, displaying the indication that the first data-set representation has been selected can include highlighting an area below the first line. For example, the area below the line of the selected data-set representation can be darkened, brightened, displayed with a different color, or otherwise highlighted relative to other portions of the graph to change the line graph into an area graph of the selected data set. In some examples, the data-set representations that are not currently selected can be removed from the display, greyed out, or otherwise made less visible within the graph.
In some examples, the first range of vertical positions within the graph can expand based on a length of time that the user input is detected while a vertical position of the location of the user input is within the first range of vertical positions. In other examples, the second range of vertical positions within the graph can expand based on a length of time that the user input is detected while the vertical position of the location of the user input is within the second range of vertical positions.
At block 2608, a detailed-view input can be detected at the electronic device. In some examples, detecting the detailed-view input can include detecting a change in orientation of the electronic device while displaying the graph. For example, detecting the detailed-view input can include detecting a change in orientation of the electronic device from a landscape view (e.g., shown in
At block 2610, in response to detecting the detailed-view input, a detailed view of the first data set and the second data set can be displayed. For example, a detailed view similar or identical to those shown in interfaces 2100 and 2200 can be displayed. The detailed view can include a first partition associated with the first data set (e.g., partition 2102) and a second partition associated with the second data set (e.g., partition 2104).
In some examples, the first partition can include a first graph representation of the first data set (e.g., graph 2108), and the second partition can include a second graph representation of the second data set (e.g., graph 2110). In some examples, unlike the first and second data-set representation of the graph view, the first graph representation can be non-overlapping with the second graph representation in the detailed view.
In some examples, the first partition can be displayed in a color matching a color of the first data-set representation, and the second partition can be displayed in a color matching a color of the second data-set representation. For example, partition 2102 can be displayed in a color matching a color of data-set representation 2302, and partition 2104 can be displayed in a color matching a color of data-set representation 2304.
In some examples, process 2600 can further include detecting a request to scroll the detailed view and, in response to detecting the request to scroll the detailed view, scrolling the detailed view. For example, the detailed view shown in interface 2100 can be scrolled in the upward direction to display interface 2200 containing other partitions that were not previously displayed.
In some examples, process 2600 can further include detecting a request to reorder the first partition and the second partition and, in response to detecting the request to reorder the first partition and the second partition, reordering the first partition and the second partition within the detailed view. In some examples, detecting the request to reorder can include detecting a selection of one of the partitions for greater than a threshold length of time. After detecting the selection for the threshold length of time, user device 510 can animate the partitions in a way that indicates that the partitions can be reordered. The partitions can be displayed reordered in response to detecting that a selected partition is dragged to a new location within the detailed view.
In some examples, process 2600 can further include detecting a graph-view input at the electronic device and, in response to detecting the graph-view input, displaying the graph comprising the first data-set representation of the first data set and the second data-set representation of the second data set. In some examples, detecting the graph-view input can include detecting a change in orientation of the electronic device. For example, interface 2300 can be displayed in response to detecting a change in orientation of the electronic device from a portrait view to a landscape view.
It should be understood that the particular order in which the operations in
Input and Output of Heath Data with Granularity
In some examples, each item in list 2702 can include an indicator 2704 that can be color-coded based on the type of wellness or non-wellness data of the associated item in list 2702. For example, the indicator 2704 associated with “Fitness” can have a different color than the indicator 2704 associated with “Vital Signs.” In some examples, the items in list 2702 can further include a selectable option 2706 that can be used to expand the associated category.
For example,
Referring back to
In some examples, any of the sub-categories shown in interfaces 2800 and 2900 can be selected to display a detailed view of the sub-category. For example,
In some examples, interface 3000 can further include a current daily value 3004 of 1250 kcal and a graph representation 3002 showing the number of Calories burned over time throughout the day. Interface 3000 can further include “Show All Data” option 3006 that can be used to display all data that falls within the sub-category of “Calories Burned.” For example,
While shown for Calories burned, it should be appreciated that a list of data entries associated with any type of sub-category of wellness or non-wellness data can be displayed in a similar manner.
Referring back to
Referring back to
As shown in
In some examples, the detailed view of the sub-category can further include additional information not shown in interface 3000. In these examples, a user can initiate a scroll request by swiping up or down on a touch sensitive display, by clicking and dragging on a display using a mouse or other input device, by manipulating a scroll-wheel, by performing a swiping gesture on a touch pad, or the like. In response to detecting the scroll request, user device 510 can scroll the view of interface 3000 to display information that was not previously displayed (or was partially displayed).
For example,
Referring back to
Interface 3400 can further include a list 3404 of known possible destinations of wellness or non-wellness data. This list can include known devices or software applications that can potentially receive a user's wellness or non-wellness data (e.g., stored in wellness database 511). When option 3412 of share option 3402 is moved to the off position, data sharing for all listed devices and applications can be turned off. As such, selectable options 3414, 3416, and 3418 can be removed from interface 3400 or otherwise made inactive. When option 3412 of share option 3402 is moved to the on position, selectable options 3414, 3416, and 3418 associated with the destinations in list 3404 can be displayed or made selectable. Similar to option 3412, the position of the switches of options 3414, 3416, and 3418 can be changed to turn data sharing on or off for the associated destination. For example, option 3414 for Device 1 is in the off position, indicating that data sharing is not turned on for Device 1. Options 3416 and 3418, however, are in the on position, indicating that data sharing is turned on for App 1 and App 2. When data sharing is turned on, the associated device or application can access the user's wellness or non-wellness data (e.g., stored in wellness database 511). For example, App 1, which can represent a weight tracking application, can access a user's fitness and nutrition data to track the user's caloric intake and outtake. When data sharing is turned off, the associated device or application may be prevented from accessing the user's wellness or non-wellness data (e.g., stored in wellness database 511). For example, Device 1 may be unable to access data stored in wellness database 511.
Interface 3400 can further include source list 3406 containing a list of known devices and applications that can potentially provide wellness or non-wellness data (e.g., to be stored in wellness database 511). The devices and applications in source list 3406 can be arranged in an order based on their priority. For example, as shown, Device 1 has priority over Device 2, which has priority over App 3. These relative priorities can be used to de-duplicate wellness or non-wellness data generated by two or more of the sources. For example, if Device 1 represents a fitness-tracking watch, and Device 2 represents a mobile phone, it is possible that both devices can provide step data associated with the user. Thus, by prioritizing the different sources, data from a higher ranked source can be used in place of data from a lower ranked source, or otherwise prioritized over data from the lower ranked source. This can be advantageous when one device is more likely to produce more accurate results than another. In some examples, duplicate data entries can be detected by identifying two or more data entries having metadata indicating that they are of the same type (e.g., step data, Calories burned, etc.) and having an associated timestamp that is within a threshold length of time from each other.
In some examples, interface 3400 can further include edit option 3408 for changing the order of the sources of source list 3406. For example, in response to a selection of option 3408, each item in source list 3406 can be moved (e.g., by clicking and dragging, etc.) relative to each other. The new order of sources within source list 3406 can define a new prioritization between sources.
In some examples, the “Sources” option of source list 3406 can be selected to display a more detailed view of the sources. For example,
For example,
Interface 3600 can further include a list 3606 of data types that can be provided by Device 1. When option 3412 of share option 3604 is moved in the off position, data uploading for all listed types of data can be turned off. As such, selectable options 3608, 3610, 3612, and 3614 can be removed from interface 3600 or otherwise made inactive. When option 3604 of upload data option 3602 is moved to the on position, selectable options 3608, 3610, 3612, and 3614 associated with the list 3606 of data types can be displayed or made selectable. Similar to option 3604, the position of the switches of options 3608, 3610, 3612, and 3614 can be changed to turn data uploading on or off for the associated types of data. For example, option 3608 for Blood Pressure is in the off position, indicating that data uploading is not turned on for Blood Pressure data from Device 1. Options 3610, 3612, and 3614, however, are in the on position, indicating that data uploading is turned on for Calorie, Step, and Stairs Climbed data. When data uploading is turned on, the associated type of data can be provided by the device or application to be stored by user device 510 (e.g., in wellness database 511). For example, Calorie data generated by Device 1 can be received by user device 510 from Device 1 and stored in wellness database 511. When data uploading is turned off, the associated type of data may not be provided by the device or application to be stored by user device 510 (e.g., in wellness database 511). For example, blood pressure data generated by Device 1 may not be received by user device 510 from Device 1 and stored in wellness database 511. The options of interface 3600 advantageously allow a user to specifically define what types of data can be provided by a particular device or application.
While the examples shown in
As described below, process 3700 provides an intuitive way to manage sources and destinations of data stored in wellness database 511. The process allows a user to specify which devices and applications can access data in wellness database 511, as well as to specify the devices and applications that can serve as sources for data to be stored in wellness database 511. Additionally, for the sources, the user can specify what types of data those sources can provide and which sources take priority over others. This can be advantageous when one device is more likely to produce more accurate results than another.
At block 3702, information identifying a plurality of approved sources of wellness data can be received by a user device (e.g., user device 510) from a user. In some examples, the information identifying the plurality of approved sources can identify one or more types of wellness or non-wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database (e.g., wellness database 511). For example, the information identifying the plurality of approved sources can be received via an interface similar or identical to interfaces 3400, 3500, and 3600. In these examples, a user can specify which types of data can be provided by each of the plurality of approved sources to be stored in the wellness database.
At block 3704, information identifying a plurality of approved destinations of wellness or non-wellness data can be received by a user device (e.g., user device 510) from the user. For example, the information identifying the plurality of approved destinations can be received via an interface similar or identical to interface 3400. In these examples, a user can specify which destinations are approved to access data from the wellness database.
In some examples, the plurality of approved sources can include an electronic device or a software application. For example, an approved electronic device, such as a watch, a mobile phone, or the like, can provide wellness or non-wellness data to user device 510 to be stored in wellness database 511. Similarly, an approved software application on or otherwise associated with user device 510 can provide wellness or non-wellness data to user device 510 to be stored in wellness database 511. In some examples, the approved software application can be a software application associated with an electronic device and is capable of communicating with the electronic device.
Similarly, in some examples, the plurality of approved destinations can include an electronic device or a software application. For example, an approved electronic device, such as a watch, a mobile phone, or the like, can access wellness or non-wellness data stored in wellness database 511. Similarly, an approved software application on or otherwise associated with user device 510 can access wellness or non-wellness data stored in wellness database 511. In some examples, the approved software application can be a software application associated with an electronic device and is capable of communicating with the electronic device.
In some examples, the plurality of approved sources can be ranked amongst each other. In some examples, an interface similar or identical to interface 3400 can be used to display and adjust the relative ranking of the approved sources. For example, as shown in interface 3400, Device 1 can be ranked higher than Device 2 to prioritize data from Device 1 over data from Device 2, and Device 2 can be ranked higher than App 3 to prioritize data from Device 1 and Device 2 over data from App 3.
In some examples, process 3700 can further include, at block 3706, identifying a first wellness data entry and a second wellness data entry that are duplicates of one another. In some examples, this can include identifying a first wellness data entry in the wellness database that was received from a first approved source of the plurality of approved sources, the first wellness data entry comprising a first wellness data type and a first timestamp, and identifying a second wellness data entry in the wellness database that was received from a second approved source of the plurality of approved sources, the second wellness data entry comprising a second wellness data type and a second timestamp, wherein the first wellness data type and the second wellness data type are the same, and wherein the first timestamp is within a threshold length of time from the second timestamp. For example, a first data entry can have a type of “step data” and an associated timestamp of 2:30 p.m. on Mar. 1, 2014. The second data entry can have a type of “step data” and an associated timestamp of 2:31 p.m. on Mar. 1, 2014. If the threshold length of time used at block 3706 is 5 minutes, it can be determined that the first data entry and the second data entry are of the same data type and include timestamps that are within a threshold length of time from each other. This can indicate that the first data entry and the second data entry are likely duplicate entries representing the same actions performed by the user.
At block 3708, one of the first data entry and the second data entry can be prioritized or otherwise identified as being preferred over the other based on a ranking of the plurality of sources. For example, as discussed above, the plurality of approved sources can be ranked amongst each other (e.g., as shown in interface 3400). In some examples, if the first approved source providing the first data entry is identified by the user as being preferred over the second approved source, block 3708 can include using the first wellness data entry instead of using the second wellness data entry. For example, this can include deleting the second data entry from wellness database 511 or otherwise ignoring the second data entry for purposes of being displayed or presented to the user. In other examples, if the first approved source has been identified by the user as being preferred over the second approved source, then block 3706 can include prioritizing the first wellness data entry over the second wellness data entry. A data entry that is prioritized over another can be used in place of the other (e.g., displayed, used in calculations, or the like in favor of the other data entry).
In other examples, if the second approved source has been identified by the user as being preferred over the first approved source, then block 3706 can include prioritizing the second wellness data entry over the first wellness data entry. A data entry that is prioritized over another can be used in place of the other (e.g., displayed, used in calculations, or the like in favor of the other data entry).
In some examples, as shown in
At block 3712, a selection of a category of wellness data from the displayed plurality of categories of wellness data can be detected at the electronic device. For example, a selection of one of the categories displayed in an interface similar or identical to interface 2700 made via a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be detected. In some examples, each of the displayed plurality of categories can include an indicator (e.g., indicator 2704) that can be color-coded based on the type of wellness or non-wellness data of the category. For example, the indicator associated with “Fitness” can have a different color than the indicator associated with “Vital Signs.”
At block 3714, one or more sub-categories of the category of wellness data can be displayed in response to detecting the selection of the category of wellness data. For example, an interface similar or identical to interface 2800 containing a list of sub-categories falling within the category selected at block 3712 can be displayed. In some examples, the displayed interface can include indicators that can be color-cored based on the type of wellness or non-wellness data that it represents.
At block 3716 a selection of a sub-category from the displayed one or more sub-categories can be detected. For example, a selection of one of the sub-categories displayed in an interface similar or identical to interface 2800 made via a touch event by a finger or other device on a touch sensitive display, a click of a mouse or other device, a touch event on a touch pad, or the like, can be detected.
At block 3718, a detailed view of the selected sub-category can be displayed in response to detecting the selection of the sub-category at block 3716. For example, an interface similar or identical to interface 3100 can be displayed. The detailed view of the sub-category can include a graphical representation of the sub-category of data (e.g., graph 3002) and a numerical daily value (e.g., daily value 3004). The detailed view can further include options to show all data (e.g., option 3006), add a data point (e.g., option 3008), share data (e.g., option 3010), and show on dashboard (e.g., option 3012). The detailed view can further include a graphic representation of the sub-category (e.g., graphic 3014) and a text description of the sub-category (e.g., description 3022),
In some examples, process 3700 can include displaying an interface similar or identical to interface 3300 in response to a selection of the add a data point option (e.g., option 3008). The interface can include one or more input fields (e.g., fields 3302, 3304, and 3306) for entering information associated with the wellness data entry. In some examples, process 3700 can further include receiving a wellness data entry to be stored in the wellness database that was input into the input field (e.g., input into fields 3302, 3304, and 3306).
In some examples, process 3700 can further include displaying an interface similar or identical to interface 3200 in response to a selection of the show all data option (e.g., option 3006). The interface can include a plurality of wellness data entries corresponding to the sub-category stored in the wellness database (e.g., entries in list 3202) In some examples, each of the plurality of wellness data entries can include a numerical value of the data entry, a timestamp, and an identification of a source of the data entry (e.g., indicator 3204).
In some examples, process 3700 can further include displaying a data sharing interface similar or identical to interface 3400 in response to a selection of the share data option (e.g., option 3010). The interface can include the plurality of approved sources (e.g., source list 3406) and the plurality of approved destinations (e.g., list 3404). In some examples, a request to reorder the displayed plurality of approved sources can be detected by the electronic device. For example, a selection of edit button 3408 can be received and movement of one or more of the sources in source list 3406 can be detected. In response to detecting the request to reorder the displayed plurality of approved sources, the displayed plurality of approved sources can be reordered in accordance with the detected request to reorder the displayed plurality of approved sources
In some examples, the data sharing interface (e.g., interface 3400) can further include options to add an approved destination to the plurality of approved destinations and to remove an approved destination from the plurality of approved destinations (e.g., options 3412, 3414, 3416, and 3418).
In some examples, process 3700 can further include receiving, at the electronic device, a search query. In response, one or more sub-categories of the plurality of categories that match the search query can be displayed. The displayed one or more sub-categories that match the search query can be color-coded based on their respective categories. For example, a search query can be received from a search box (e.g., search box 2708) displayed within an interface similar or identical to interface 2700 or 2800. A search results interface similar or identical to interface 2900 can be displayed in response to the search query. The search results interface can include the one or more sub-categories that match the search query.
In some examples, process 3700 can further include displaying, on the display, a source interface comprising a list of known sources. For example, an interface similar or identical to interface 3500 can be displayed having a list of known sources (e.g., list 3506). The source interface can further include a numerical indicator associated a known source of the known sources that represents a number of new types of wellness data that can be provided by the known source. For example, the number “2” is shown for Device 1, indicating the two new types of data (e.g., Calories burned and flights of stairs climbed) are available.
In some examples, process 3700 can further include detecting a selection of a known source from the list of displayed sources. In response to detecting the selection of the known source, a list of types of wellness data that the known source can provide can be displayed. For example, a source from source list 3506 of interface 3500 can be received by a user selecting an option 3510 associated with the source. In response, an interface similar or identical to interface 3600 can be displayed. The displayed interface can include a list (e.g., list 3606) of known types of data that the source can provide. In some examples, the list of types of wellness data that the known source can provide can include a selectable option (e.g., options 3604, 3608, 3610, 3612, and 3614) for each of the types of wellness data that the known source can provide to approve or reject the associated type of wellness data.
In some examples, process 3700 can further include detecting a selection of the selectable option for a type of wellness data that the known source can provide at the electronic device. In response to detecting the selection of the selectable option, process 3700 can further include approving or rejecting the type of wellness data that the known source can provide in accordance with the detected selection of the selectable option. For example, user device 510 can accept or reject the types of wellness data shown in interface 3600 based on the positions of the switches of options 3604, 3608, 3610, 3612, and 3614.
It should be understood that the particular order in which the operations in
Medical Identification Information
As shown in
Interface 3900 can further include Medical ID or emergency information option 3902 for viewing medical information associated with a user by the temporary user. In this example, the user can be a primary user or owner of user device 510 that has customized the device by installing applications and/or entering personal information to user device 510. Thus, Medical ID or emergency information option 3902 can be selected by the temporary user to view emergency information associated with the primary user without requiring the temporary user to unlock user device 510.
For example,
Interface 4000 can further include emergency contacts 4012. Emergency contacts 4012 can include a list of one or more people that the user has designated as being his/her emergency contact. Emergency contacts 4012 can include a name of each emergency contact and a relationship between the user and the emergency contact. For example, one entry for an emergency contact can include the name “Jane Smith” having a relationship with the user of “mother.” In some examples, emergency contacts 4012 can further include contact information for the emergency contact, such as a phone number, email address, or the like. In other examples, emergency contact 4012 can exclude contact information for the emergency contact, such as a phone number, email address, or the like. This can be done to protect the privacy of the emergency contact. In either example, user device 510 can allow a temporary user to select one of the displayed emergency contacts to initiate communication with that contact (even if the phone number of the emergency contact is not displayed) while user device 510 remains in the locked state. For example, in response to a selection of one of the emergency contacts, user device 510 can initiate a phone call to the contact, send an SMS message to the contact, send an email to the emergency contact, or the like, while the device remains in the locked state. In some examples, when user device 510 initiates a call to an emergency contact in response to a selection of that emergency contact, user device 510 can flag the call as being an emergency call. In some examples, emergency calls can be accepted by a receiving device in any state of operation. For example, a call flagged as being an emergency call can cause the receiving device to ring while in a do-not-disturb mode, a silent mode, or the like. Additionally, an indicator can be displayed on the receiving device notifying the recipient that the call is an emergency call.
In some examples, a primary user can create their medical identification from the contact list of user device 510. For example,
As described below, process 4400 provides a way for a temporary user to view medical information associated with a primary user or owner of an electronic device while the device remains in a locked state. Process 4400 also allows a temporary user to initiate communication with the primary user's emergency contacts while the device remains in the locked state. This advantageously allows a temporary user that finds the primary user (e.g., in a state in which the primary user is unable to operate the electronic device or communicate) to assist the primary user in getting the appropriate medical care.
At block 4402, at an electronic device (e.g., user device 510) while the electronic device is in a locked state, a request to display emergency information about a user of the device can be detected. For example, the request to display the emergency information can be received while an emergency dialing interface similar or identical to interface 3900 is being displayed, and the request can include a selection of an emergency information option similar or identical to option 3902. The emergency information about the user of the device can include the user's name, birthday, medical conditions, allergies and reactions, medications, and one or more emergency contacts of the user. As discussed above, the user can be a primary user or owner of user device 510 that has customized the device by installing applications and/or entering personal information to user device 510. The request to display the medical information can be made by a temporary user, such as a first responder or other person that encounters the primary user of the device when the primary user of the device is unable to operate user device 510 (e.g., because the primary user is unconscious or injured).
At block 4404, in response to detecting the request, an emergency information interface comprising emergency information about the user of the device can be displayed without unlocking the device. For example, an interface similar or identical to interface 4000 can be displayed.
In some examples, the emergency information about the user can include information associated with an emergency contact. The information associated with the emergency contact can include a name of the emergency contact and a relationship between the user and the emergency contact. For example, information about an emergency contact can be displayed in a manner similar or identical to emergency contact 4012 in interface 4000. One example emergency contact can include the contact's name “Jane Smith,” and the relationship “mother” between the user and the contact.
At block 4406, user device 510 can detect a request to communicate with an emergency contact while the electronic device is in the locked state. For example, a selection of a contact 4012 from interface 4000 can be detected.
At block 4408, user device 510 can initiate communication with the emergency contact in response to detecting the request to communicate. In some examples, initiating communication with the emergency contact includes sending an SMS message or email to the emergency contact. In other examples, initiating communication with the emergency contact can include calling a phone number associated with the emergency contact. In some examples, calling the phone number associated with the emergency contact can include flagging the call to the phone number as an emergency call. In some examples, the phone number associated with the emergency contact can be included in the information associated with the emergency contact displayed within the emergency information interface (e.g., interface 4000). In other examples, the phone number associated with the emergency contact may not be included in the information associated with the emergency contact displayed within the emergency information interface (e.g., interface 4000). However, a call or other communication can still be made to this emergency contact. This can be done to protect the privacy of the emergency contact.
In some examples, process 4400 can include displaying an emergency dialing interface prior to displaying the emergency information interface. The emergency dialing interface can include a numerical input pad and an emergency information option. For example, an emergency dialing interface similar or identical to interface 3900 can be displayed prior to displaying emergency information interface 4000. The emergency dialing interface 3900 can include a numerical input pad similar or identical to input pad 3904 and an emergency information option similar or identical to option 3902. In some examples, the emergency information interface (e.g., interface 4000) can be displayed in response to a selection of the emergency information option (e.g., option 3902).
In some examples, process 4400 can further include detecting a predefined phone number entered using the numerical input pad while the electronic device is in the locked state. In response to detecting the predefined phone number, process 4400 can further include calling the predefined phone number. For example, user device 510 can detect a predefined number (e.g., 9-1-1) entered in the numerical input pad (e.g., input pad 3904). In response to detecting the predefined phone number, user device 510 can call the predefined number while still in the locked state. In some examples, calling the predefined phone number can include flagging the call to the predefined phone number as an emergency call.
In some examples, calls flagged as being emergency calls can be accepted by a receiving electronic device in any state of operation. For example, a call flagged as being an emergency call can cause the receiving device to ring while in a do-not-disturb mode, a silent mode, or the like. Additionally, an indicator can be displayed on the receiving device notifying the recipient that the call is an emergency call.
In some examples, process 4400 can further include displaying a lock screen interface comprising an emergency option prior to displaying the emergency dialing interface. For example, an interface similar or identical to interface 3800 can be displayed having an emergency option similar or identical to option 3802. The lock screen interface can further include one or more controls for unlocking the device. For example, a numerical input pad can be displayed to allow a user to enter a passcode, or user device 510 can be configured to detect predefined gestures to unlock the device. In these examples process 4400 can further include detecting a selection of the emergency option and displaying the emergency dialing interface in response to detecting the selection of the emergency option. For example, user device 510 can detect a selection of option 3802 and display interface 3900 in response to detecting the selection of option 3802.
It should be understood that the particular order in which the operations in
In some examples, the interfaces shown in
One or more of the functions relating to aggregating and sharing wellness data can be performed by a system similar or identical to system 4500 shown in
The instructions can also be propagated within any transport medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “transport medium” can be any medium that can communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The transport medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic or infrared wired or wireless propagation medium.
In some examples, system 4500 can be included within user device 510 or user server 514. Processor 4506 can be configured to perform processes 700, 800, 1500, 1700, 2000, 2600, 3700, or 4400. It is to be understood that the system is not limited to the components and configuration of
Electronic De Vice
In accordance with some examples,
As shown in
Processing unit 4608 can be configured to display (e.g., using graph displaying unit 4610) a graph comprising a first data-set representation of a first data set in which a first dependent variable varies as an independent variable changes and a second data-set representation of a second data set in which a second dependent variable varies as the independent variable changes, wherein the first data-set representation is associated with a first range of vertical positions within the graph and the second data-set representation is associated with a second range of vertical positions within the graph. Processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) a user input at a respective location on the display. Processing unit 4608 can be further configured to, in response to detecting the user input and in accordance with a determination that the respective location is within the first range of vertical positions associated with the first data-set representation, display (e.g., using first indication displaying unit 4614) an indication that the first data-set representation has been selected. Processing unit 4608 can be further configured to, in response to detecting the user input and in accordance with a determination that the respective location is within the second range of vertical positions associated with the second data-set representation display (e.g., using second indication displaying unit 4616) an indication that the second data-set representation has been selected.
In some examples, processing unit 4608 can be further configured to display (e.g., using graph displaying unit 4610) the first data-set representation in the graph overlapping the second data-set representation.
In some examples, the first data set comprises a first set of wellness data and the second data set comprises a second set of wellness data.
In some examples, the first range of vertical positions is uniquely associated with the first data-set representation, and the second range of vertical positions is uniquely associated with the second data-set representation.
In some examples, the first data-set representation and the second data-set representation are colored-coded based on a type of data that they represent.
In some examples, processing unit 4608 can be further configured to display (e.g., using first indication displaying unit 4614) the indication that the first data-set representation has been selected by displaying, on the display, a marker overlaid on the first data-set representation at a horizontal position corresponding to a horizontal position of the respective location on the display.
In some examples, processing unit 4608 can be further configured to display (e.g., using second indication displaying unit 4616) the indication that the second data-set representation has been selected by displaying, on the display, a marker overlaid on the second data-set representation at a horizontal position corresponding to a horizontal position of the respective location on the display.
In some examples, processing unit 4608 can be further configured to display (e.g., using first indication displaying unit 4614) the indication that the first data-set representation has been selected by displaying, on the display, a numerical value of a first data entry of the first data set associated with a value of the independent variable corresponding to a horizontal position of the respective location on the display.
In some examples, processing unit 4608 can be further configured to display (e.g., using second indication displaying unit 4616) the indication that the second data-set representation has been selected by displaying, on the display, a numerical value of a second data entry of the second data set associated with a value of the independent variable corresponding to a horizontal position of the respective location on the display.
In some examples, the first data set or the second data set comprises blood pressure data, and wherein the numerical value of the first data entry or the second data entry comprises a high value for diastolic blood pressure, a low value for diastolic blood pressure, a high value for systolic blood pressure, and a low value for systolic blood pressure.
In some examples, processing unit 4608 can be further configured to generate (e.g., using graph displaying unit 4610) the first data-set representation or the second data-set representation based on an average of blood pressure values.
In some examples, the first data set or the second data set comprises heart rate data, and the numerical value of the first data entry or the second data entry comprises a high value for heart rate and a low value for heart rate.
In some examples, the first data-set representation comprises a first line in the graph, and processing unit 4608 can be further configured to display (e.g., using first indication displaying unit 4614) the indication that the first data-set representation has been selected by highlighting an area below the first line.
In some examples, the second data-set representation comprises a second line in the graph, and processing unit 4608 can be further configured to display (e.g., using first indication displaying unit 4614) the indication that the second data-set representation has been selected by highlighting an area below the second line.
In some examples, processing unit 4608 can be further configured to expand (e.g., using detecting unit 4614) the first range of vertical positions within the graph based on a length of time that the user input is detected while a vertical position of the respective location on the display is within the first range of vertical positions, and to expand (e.g., using detecting unit 4614) the second range of vertical positions within the graph based on a length of time that the user input is detected while the vertical position of the respective location on the display is within the second range of vertical positions.
In some examples, the dependent variable for the first data set is measured in different units from the dependent variable for the second data set.
In some examples, a vertical scale for displaying the first data-set representation is different from a vertical scale for displaying the second data-set representation.
In some examples, processing unit 4608 can be further configured to determine (e.g., using graph displaying unit 4610) the vertical scale for the first data-set representation based on the maximum and minimum values of the first dependent variable of the first data-set representation that are to be displayed in the graph, and to determine (e.g., using graph displaying unit 4610) the vertical scale for the second data-set representation based on the maximum and minimum values of the second dependent variable of the second data-set representation that are to be displayed in the graph.
In some examples, the vertical scale for the first data-set representation of the plurality of sets of wellness data is defined by: a maximum vertical position within the graph corresponding to a first multiplying factor multiplied by the maximum value of the first dependent variable of the first data-set representation that are to be displayed in the graph; and a minimum vertical position within the graph corresponding to a second multiplying factor multiplied by the minimum value of the first dependent variable of the first data-set representation that are to be displayed in the graph.
In some examples, the vertical scale for the second data-set representation of the plurality of sets of wellness data is defined by: a maximum vertical position within the graph corresponding to a third multiplying factor multiplied by the maximum value of the second dependent variable of the second data-set representation that are to be displayed in the graph; and a minimum vertical position within the graph corresponding to a fourth multiplying factor multiplied by the minimum value of the second dependent variable of the second data-set representation that are to be displayed in the graph.
In some examples, processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) a detailed-view input and display (e.g., using detailed view displaying unit 4618) a detailed view of the first data set and the second data set in response to detecting the detailed-view input, wherein the detailed view comprises a first partition associated with the first data set and a second partition associated with the second data set.
In some examples, processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) the detailed-view input by detecting a change in orientation of the electronic device while displaying the graph.
In some examples, processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) a request to scroll the detailed view and scroll (e.g., using detailed view displaying unit 4618) the detailed view in response to detecting the request to scroll the detailed view.
In some examples, the first partition comprises a first graph representation of the first data set, and the second partition comprises a second graph representation of the second data set.
In some examples, the first graph representation is non-overlapping with the second graph representation.
In some examples, the first partition is displayed in a color matching a color of the first data-set representation, and the second partition is displayed in a color matching a color of the second data-set representation.
In some examples, the first partition is displayed in a color matching a color of the first data-set representation, and the second partition is displayed in a color matching a color of the second data-set representation.
In some examples, processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) a request to reorder the first partition and the second partition and to reorder (e.g., using detailed view displaying unit 4618) the first partition and the second partition within the detailed view in response to detecting the request to reorder the first partition and the second partition.
In some examples, processing unit 4608 can be further configured to detect (e.g., using detecting unit 4612) graph-view input and display (e.g., using graph displaying unit 4610) the graph comprising the first data-set representation of the first data set and the second data-set representation of the second data set in response to detecting the graph-view input.
In accordance with some examples,
As shown in
Processing unit 4708 can be configured to detect (e.g., using detecting unit 4710) a request to display emergency information about a user of the device while the electronic device is in a locked state. Processing unit 4708 can be further configured to display (e.g., using displaying unit 4712), while the electronic device is in the locked state, an emergency information interface comprising emergency information about the user of the device without unlocking the device in response to detecting the request.
In some examples, processing unit 4708 can be configured to restrict one or more functions of the electronic device from being used while electronic device 4700 is in the locked state.
In some examples, processing unit 4708 can be configured to prevent access to at least a subset of data stored on the electronic device while electronic device 4700 is in the locked state.
In some examples, processing unit 4708 can be configured to restrict communications from the electronic device while electronic device 4700 is in the locked state.
In some examples, the emergency information about the user comprises information associated with an emergency contact, and the information associated with the emergency contacts comprises a name of the emergency contact and a relationship between the user and the emergency contact.
In some examples, processing unit 4708 can be further configured to detect (e.g., using detecting unit 4710) a request to communicate while the electronic device is in the locked state and to initiate (e.g., using communication unit 4714) communication with the emergency contact in response to detecting the request to communicate.
In some examples, initiating communication with the emergency contact comprises sending an SMS message or email to the emergency contact.
In some examples, initiating communication with the emergency contact comprises calling a phone number associated with the emergency contact. In some examples, calling the phone number associated with the emergency contact comprises flagging the call to the phone number as an emergency call.
In some examples, the information associated with the emergency contacts further comprises the phone number associated with the emergency contact.
In some examples, the information associated with the emergency contacts excludes the phone number associated with the emergency contact.
In some examples, processing unit 4708 can be further configured to display (e.g., using displaying unit 4716), prior to displaying the emergency information interface an emergency dialing interface comprising a numerical input pad and an emergency information option. Processing unit 4708 can be further configured to detect (e.g., using detecting unit 4712), while displaying the emergency dialing interface, a selection of the emergency information option and to display (e.g., using displaying unit 4712) the emergency information interface in response to detecting selection of the emergency information option.
In some examples, processing unit 4708 can be further configured to detect (e.g., using detecting unit 4710) a predefined phone number entered using the numerical input pad while the electronic device is in the locked state and to call (e.g., using communication unit 4714) the predefined phone number in response to detecting the predefined phone number. In some examples, calling the predefined phone number comprises flagging the call to the predefined phone number as an emergency call. In some examples, calls flagged as an emergency call are to be accepted by a receiving electronic device in any state of operation.
In some examples, processing unit 4708 can be further configured to display (e.g., using displaying unit 4718), prior to displaying the emergency dialing interface, a lock screen interface comprising an emergency option and to detect (e.g., using detecting unit 4710) a selection of the emergency option. Processing unit 4708 can be further configured to display (e.g., using displaying unit 4716) and the emergency dialing interface in response to detecting the selection of the emergency option.
In some examples, the emergency information about the user comprises one or more of: the user's name, birthday, medical conditions, allergies and reactions, medications, and one or more emergency contacts of the user.
In accordance with some examples,
As shown in
Processing unit 4808 can be configured to receive (e.g., using source receiving unit 4810), from a user, information identifying a plurality of approved sources of wellness data, wherein the information identifying the plurality of approved sources identifies one or more types of wellness data that are approved to be received from the plurality of approved sources and stored in a wellness database. Processing unit 4808 can be further configured to receive (e.g., using destination receiving unit 4812), from the user, information identifying a plurality of approved destinations of wellness data, wherein the information identifying the plurality of approved destinations identifies one or more types of wellness data that are approved to be accessed from the wellness database by the plurality of approved destinations of wellness data.
In some examples, the plurality of approved sources comprise an electronic device or software application.
In some examples, the plurality of approved destinations comprise an electronic device or software application.
In some examples, the plurality of approved sources are ranked amongst each other.
In some examples, processing unit 4808 can be further configured to identify (e.g., using first identifying unit 4814) a first wellness data entry in the wellness database that was received from a first approved source of the plurality of approved sources, the first wellness data entry comprising a first wellness data type and a first timestamp and to identify (e.g., using second identifying unit 4816) a second wellness data entry in the wellness database that was received from a second approved source of the plurality of approved sources, the second wellness data entry comprising a second wellness data type and a second timestamp, wherein the first wellness data type and the second wellness data type are the same, and wherein the first timestamp is within a threshold length of time from the second timestamp.
In some examples, the first approved source has been identified by the user as being preferred over the second approved source, and wherein processing unit 4808 can be further configured to use (e.g., using prioritizing unit 4818) the first wellness data entry instead of using the second wellness data entry.
In some examples, the first approved source has been identified by the user as being preferred over the second approved source, and processing unit 4808 can be further configured to prioritize (e.g., using prioritizing unit 4818) the first wellness data entry over the second wellness data entry.
In some examples, in accordance with a determination that the first wellness data entry is prioritized over the second wellness data entry, processing unit 4808 can be further configured to use (e.g., using prioritizing unit 4818) the first wellness data entry instead of using the second wellness data entry.
In some examples, the second approved source has been identified by the user as being preferred over the first approved source, and processing unit 4808 can be further configured to prioritize (e.g., using prioritizing unit 4818) the second wellness data entry over the first wellness data entry.
In some examples, in accordance with a determination that the second wellness data entry is prioritized over the first wellness data entry, processing unit 4808 can be further configured to use (e.g., using prioritizing unit 4818) the second wellness data entry instead of using the first wellness data entry.
In some examples, processing unit 4808 can be further configured to display (e.g., using displaying unit 4820) a plurality of categories of wellness data stored in the wellness database.
In some examples, processing unit 4808 can be further configured to detect (e.g., using detecting unit 4822) a selection of a category of wellness data from the displayed plurality of categories of wellness data and to display (e.g., using displaying unit 4820) one or more sub-categories of the category of wellness data in response to detecting the selection of the category of wellness data.
In some examples, processing unit 4808 can be further configured to detect (e.g., using detecting unit 4822) a selection of a sub-category from the displayed one or more sub-categories and to display (e.g., using displaying unit 4820) a detailed view of the sub-category in response to detecting the selection of the sub-category.
In some examples, the detailed view of the sub-category comprises a graph representation of the sub-category of wellness data over time and a numerical daily value of the sub-category of wellness data.
In some examples, the detailed view of the sub-category further comprises an input field for entering a wellness data entry, and wherein processing unit 4808 can be further configured to receive (e.g., using receiving unit 4824) a wellness data entry to be stored in the wellness database that was input into the input field.
In some examples, the detailed view of the sub-category further comprises a textual description of the sub-category.
In some examples, the detailed view of the sub-category further comprises an option to view wellness data entries corresponding to the sub-category, and processing unit 4808 can be further configured to display (e.g., using displaying unit 4820) a plurality of wellness data entries corresponding to the sub-category stored in the wellness database.
In some examples, each of the plurality of wellness data entries comprises a numerical value of the data entry, a timestamp, and an identification of a source of the data entry.
In some examples, the detailed view of the sub-category further comprises an option to share wellness data, and processing unit 4808 can be further configured to reorder (e.g., using displaying unit 4820) the displayed plurality of approved sources in accordance with the detected request to reorder the displayed plurality of approved sources in response to detecting the request to reorder the displayed plurality of approved sources.
In some examples, the data sharing interface further comprises options to add an approved destination to the plurality of approved destinations and to remove an approved destination from the plurality of approved destinations.
In some examples, processing unit 4808 can be further configured to receive (e.g., using receiving unit 4824) a search query and to display (e.g., using displaying unit 4820) one or more sub-categories of the plurality of categories that match the search query, wherein the displayed one or more sub-categories that match the search query are color-coded based on their respective categories.
In some examples, processing unit 4808 can be further configured to display (e.g., using displaying unit 4820) a source interface comprising a list of known sources.
In some examples, the source interface further comprises a numerical indicator associated a known source of the known sources that represents a number of new types of wellness data that can be provided by the known source.
In some examples, processing unit 4808 can be further configured to detect (e.g., using detecting unit 4822) a selection of a known source from the displayed list of known sources and to display (e.g., using displaying unit 4820) a list of types of wellness data that the known source can provide in response to detecting the selection of the known source.
In some examples, the list of types of wellness data that the known source can provide comprises a selectable option for each of the types of wellness data that the known source can provide to approve or reject the associated type of wellness data.
In some examples, processing unit 4808 can be further configured to detect (e.g., using detecting unit 4822) a selection of the selectable option for a type of wellness data that the known source can provide and to approve or reject the type of wellness data that the known source can provide in accordance with the detected selection of the selectable option in response to detecting the selection of the selectable option
As described above, one aspect of the present technology is the gathering and use of data available from various sources to improve the delivery to users of invitational content or any other content that may be of interest to them. The present disclosure contemplates that in some instances, this gathered data can include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data can include demographic data, location-based data, telephone numbers, email addresses, home addresses, or any other identifying information.
The present disclosure recognizes that the use of such personal information data, in the present technology, can be used to the benefit of users. For example, the personal information data can be used to deliver targeted content that is of greater interest to the user. Accordingly, use of such personal information data enables calculated control of the delivered content. Further, other uses for personal information data that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates examples in which users selectively block the use of, or access to, personal information data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of advertisement delivery services, the present technology can be configured to allow users to select to “opt in” or “opt out” of participation in the collection of personal information data during registration for services. In another example, users can select not to provide location information for targeted content delivery services. In yet another example, users can select to not provide precise location information, but permit the transfer of location zone information.
Therefore, although the present disclosure broadly covers use of personal information data to implement one or more various disclosed examples, the present disclosure also contemplates that the various examples can also be implemented without the need for accessing such personal information data. That is, the various examples of the present technology are not rendered inoperable due to the lack of all or a portion of such personal information data. For example, content can be selected and delivered to users by inferring preferences based on non-personal information data or a bare minimum amount of personal information, such as the content being requested by the device associated with a user, other non-personal information available to the content delivery services, or publicly available information.
Although examples have been fully described with reference to the accompanying drawings, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the various examples as defined by the appended claims.
This application is a continuation of U.S. patent application Ser. No. 14/599,424, filed on Jan. 16, 2015, entitled “WELLNESS AGGREGATOR”, which claims priority to U.S. Provisional Ser. No. 62/006,032, filed on May 30, 2014, entitled “WELLNESS AGGREGATOR,” which are hereby incorporated by reference in their entireties for all purposes. This application relates to the following provisional application: U.S. Patent Application Ser. No. 62/006,031, entitled “MANAGING USER INFORMATION,” filed May 30, 2014, which is hereby incorporated by reference in its entirety. This application also relates to the following non-provisional application: U.S. patent application Ser. No. 14/599,425, entitled “WELLNESS AGGREGATOR,” filed Jan. 16, 2015, which is hereby incorporated by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5788655 | Yoshimura et al. | Aug 1998 | A |
| 5815657 | Williams et al. | Sep 1998 | A |
| 6097371 | Siddiqui et al. | Aug 2000 | A |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6594654 | Salam et al. | Jul 2003 | B1 |
| 6603477 | Tittle | Aug 2003 | B1 |
| 6662023 | Helle | Dec 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6912694 | Harrison et al. | Jun 2005 | B1 |
| 7081905 | Raghunath | Jul 2006 | B1 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7302650 | Allyn et al. | Nov 2007 | B1 |
| 7305350 | Bruecken | Dec 2007 | B1 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7773460 | Holt | Aug 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| 7970827 | Cumberbatch et al. | Jun 2011 | B1 |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8105208 | Oleson et al. | Jan 2012 | B2 |
| 8121945 | Rackle et al. | Feb 2012 | B2 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8453940 | Diamond | Jun 2013 | B2 |
| 8462997 | Pettit et al. | Jun 2013 | B2 |
| 8467770 | Ben Ayed | Jun 2013 | B1 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8543081 | Scott et al. | Sep 2013 | B2 |
| 8554694 | Ward et al. | Oct 2013 | B1 |
| 8566403 | Pascal et al. | Oct 2013 | B2 |
| 8595798 | Anand et al. | Nov 2013 | B2 |
| 8624836 | Miller et al. | Jan 2014 | B1 |
| 8666361 | Chu et al. | Mar 2014 | B2 |
| 8700158 | Mass et al. | Apr 2014 | B2 |
| 8706628 | Phillips | Apr 2014 | B2 |
| 8825445 | Hoffman et al. | Sep 2014 | B2 |
| 8910299 | Michalske | Dec 2014 | B2 |
| 8931703 | Mullen et al. | Jan 2015 | B1 |
| 8948819 | Yun et al. | Feb 2015 | B2 |
| 9020538 | White et al. | Apr 2015 | B1 |
| 9125566 | Libbus | Sep 2015 | B2 |
| 9338242 | Suchland et al. | May 2016 | B1 |
| 9557881 | Jain et al. | Jan 2017 | B1 |
| 9600178 | Yun et al. | Mar 2017 | B2 |
| 9600630 | Keegan | Mar 2017 | B2 |
| 9904906 | Kim et al. | Feb 2018 | B2 |
| 10019136 | Ozog | Jul 2018 | B1 |
| 10051103 | Gordon et al. | Aug 2018 | B1 |
| 10275116 | Decker et al. | Apr 2019 | B2 |
| 10425284 | Dellinger et al. | Sep 2019 | B2 |
| 10873786 | Folse et al. | Dec 2020 | B2 |
| 20010031622 | Kivela et al. | Oct 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020029169 | Oki et al. | Mar 2002 | A1 |
| 20020068600 | Chihara et al. | Jun 2002 | A1 |
| 20020118121 | Lehrman et al. | Aug 2002 | A1 |
| 20020142734 | Wickstead | Oct 2002 | A1 |
| 20030002391 | Biggs | Jan 2003 | A1 |
| 20030182628 | Lira | Sep 2003 | A1 |
| 20040077462 | Brown et al. | Apr 2004 | A1 |
| 20040083474 | Mckinlay et al. | Apr 2004 | A1 |
| 20040168107 | Sharp et al. | Aug 2004 | A1 |
| 20040181771 | Anonsen et al. | Sep 2004 | A1 |
| 20040218472 | Narayanaswami et al. | Nov 2004 | A1 |
| 20040225966 | Besharat et al. | Nov 2004 | A1 |
| 20040246607 | Watson et al. | Dec 2004 | A1 |
| 20050156873 | Walter et al. | Jul 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050197063 | White | Sep 2005 | A1 |
| 20050202846 | Glass et al. | Sep 2005 | A1 |
| 20060000900 | Fernandes et al. | Jan 2006 | A1 |
| 20060010098 | Goodnow et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenberg et al. | Jan 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060052727 | Palestrant | Mar 2006 | A1 |
| 20060122748 | Nou | Jun 2006 | A1 |
| 20060155578 | Eisenberger et al. | Jul 2006 | A1 |
| 20060173749 | Ward et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060217104 | Cho | Sep 2006 | A1 |
| 20060218500 | Sauve et al. | Sep 2006 | A1 |
| 20060271605 | Petruzzo | Nov 2006 | A1 |
| 20060277469 | Chaudhri et al. | Dec 2006 | A1 |
| 20070067733 | Moore et al. | Mar 2007 | A1 |
| 20070096765 | Kagan | May 2007 | A1 |
| 20070101279 | Chaudhri et al. | May 2007 | A1 |
| 20070135043 | Hayes et al. | Jun 2007 | A1 |
| 20070143495 | Porat | Jun 2007 | A1 |
| 20070194110 | Esplin et al. | Aug 2007 | A1 |
| 20070194113 | Esplin et al. | Aug 2007 | A1 |
| 20070254712 | Chitti | Nov 2007 | A1 |
| 20070261537 | Eronen et al. | Nov 2007 | A1 |
| 20070271340 | Goodman et al. | Nov 2007 | A1 |
| 20080027586 | Hern et al. | Jan 2008 | A1 |
| 20080040265 | Rackley, III et al. | Feb 2008 | A1 |
| 20080076637 | Gilley et al. | Mar 2008 | A1 |
| 20080077936 | Goel et al. | Mar 2008 | A1 |
| 20080150731 | Laukkanen et al. | Jun 2008 | A1 |
| 20080183909 | Lim et al. | Jul 2008 | A1 |
| 20080247519 | Abella et al. | Oct 2008 | A1 |
| 20080259829 | Rosenblatt | Oct 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20090037326 | Chitti et al. | Feb 2009 | A1 |
| 20090054743 | Stewart | Feb 2009 | A1 |
| 20090057396 | Barbour et al. | Mar 2009 | A1 |
| 20090060170 | Coughlan et al. | Mar 2009 | A1 |
| 20090070675 | Li | Mar 2009 | A1 |
| 20090113315 | Fisher et al. | Apr 2009 | A1 |
| 20090195497 | Fitzgerald et al. | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090205041 | Michalske | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090231960 | Hutcheson | Sep 2009 | A1 |
| 20090262088 | Moll-carrillo et al. | Oct 2009 | A1 |
| 20090276463 | Miller | Nov 2009 | A1 |
| 20090300598 | Choi | Dec 2009 | A1 |
| 20090311993 | Horodezky | Dec 2009 | A1 |
| 20090313579 | Poulson | Dec 2009 | A1 |
| 20090319467 | Berg et al. | Dec 2009 | A1 |
| 20100048358 | Tchao et al. | Feb 2010 | A1 |
| 20100054519 | Mulvey et al. | Mar 2010 | A1 |
| 20100064255 | Rottler et al. | Mar 2010 | A1 |
| 20100079291 | Kroll et al. | Apr 2010 | A1 |
| 20100082481 | Lin et al. | Apr 2010 | A1 |
| 20100125785 | Moore et al. | May 2010 | A1 |
| 20100151908 | Skarby et al. | Jun 2010 | A1 |
| 20100151918 | Annambhotla et al. | Jun 2010 | A1 |
| 20100157742 | Relyea et al. | Jun 2010 | A1 |
| 20100190468 | Scott et al. | Jul 2010 | A1 |
| 20100194692 | Orr et al. | Aug 2010 | A1 |
| 20100198453 | Dorogusker et al. | Aug 2010 | A1 |
| 20100202368 | Hans | Aug 2010 | A1 |
| 20100211685 | Mcdowall et al. | Aug 2010 | A1 |
| 20100222645 | Nadler et al. | Sep 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100223563 | Green | Sep 2010 | A1 |
| 20100225962 | Okigami et al. | Sep 2010 | A1 |
| 20100226213 | Drugge et al. | Sep 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20100292600 | Dibenedetto et al. | Nov 2010 | A1 |
| 20100295795 | Wilairat | Nov 2010 | A1 |
| 20100299601 | Kaplan et al. | Nov 2010 | A1 |
| 20100305965 | Benjamin et al. | Dec 2010 | A1 |
| 20100331145 | Lakovic et al. | Dec 2010 | A1 |
| 20110003665 | Burton et al. | Jan 2011 | A1 |
| 20110004835 | Yanchar et al. | Jan 2011 | A1 |
| 20110010195 | Cohn | Jan 2011 | A1 |
| 20110029750 | Jang et al. | Feb 2011 | A1 |
| 20110059769 | Brunolli | Mar 2011 | A1 |
| 20110061010 | Wasko | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110078025 | Shrivastav | Mar 2011 | A1 |
| 20110083111 | Forutanpour et al. | Apr 2011 | A1 |
| 20110088086 | Swink et al. | Apr 2011 | A1 |
| 20110093728 | Das | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110106954 | Chatterjee et al. | May 2011 | A1 |
| 20110130168 | Vendrow et al. | Jun 2011 | A1 |
| 20110137678 | Williams | Jun 2011 | A1 |
| 20110137836 | Kuriyama et al. | Jun 2011 | A1 |
| 20110159959 | Mallinson et al. | Jun 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110193878 | Seo et al. | Aug 2011 | A1 |
| 20110197165 | Filippov et al. | Aug 2011 | A1 |
| 20110202883 | Oh et al. | Aug 2011 | A1 |
| 20110205851 | Harris et al. | Aug 2011 | A1 |
| 20110218765 | Rogers | Sep 2011 | A1 |
| 20110227872 | Huska et al. | Sep 2011 | A1 |
| 20110230986 | Lafortune et al. | Sep 2011 | A1 |
| 20110234152 | Frossen et al. | Sep 2011 | A1 |
| 20110246509 | Migita et al. | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110261079 | Ingrassia et al. | Oct 2011 | A1 |
| 20110271223 | Cruz moreno et al. | Nov 2011 | A1 |
| 20110296324 | Goossens et al. | Dec 2011 | A1 |
| 20110304685 | Khedouri et al. | Dec 2011 | A1 |
| 20120001922 | Escher et al. | Jan 2012 | A1 |
| 20120015779 | Powch et al. | Jan 2012 | A1 |
| 20120036029 | Esplin et al. | Feb 2012 | A1 |
| 20120036220 | Dare et al. | Feb 2012 | A1 |
| 20120036460 | Cieplinski et al. | Feb 2012 | A1 |
| 20120044062 | Jersa et al. | Feb 2012 | A1 |
| 20120047447 | Haq | Feb 2012 | A1 |
| 20120059664 | Georgiev et al. | Mar 2012 | A1 |
| 20120059787 | Brown et al. | Mar 2012 | A1 |
| 20120060092 | Hill et al. | Mar 2012 | A1 |
| 20120066628 | Ens et al. | Mar 2012 | A1 |
| 20120071770 | Grey et al. | Mar 2012 | A1 |
| 20120079122 | Brown et al. | Mar 2012 | A1 |
| 20120083258 | Rabii | Apr 2012 | A1 |
| 20120084210 | Farahmand | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120101887 | Harvey et al. | Apr 2012 | A1 |
| 20120116550 | Hoffman et al. | May 2012 | A1 |
| 20120117507 | Tseng et al. | May 2012 | A1 |
| 20120131441 | Jitkoff et al. | May 2012 | A1 |
| 20120136780 | El-awady et al. | May 2012 | A1 |
| 20120143013 | Davis et al. | Jun 2012 | A1 |
| 20120169608 | Forutanpour et al. | Jul 2012 | A1 |
| 20120191603 | Nuzzi | Jul 2012 | A1 |
| 20120197523 | Kirsch et al. | Aug 2012 | A1 |
| 20120209829 | Thomas et al. | Aug 2012 | A1 |
| 20120253485 | Weast et al. | Oct 2012 | A1 |
| 20120258684 | Franz et al. | Oct 2012 | A1 |
| 20120290109 | Engelberg et al. | Nov 2012 | A1 |
| 20120310674 | Faulkner et al. | Dec 2012 | A1 |
| 20120310760 | Phillips et al. | Dec 2012 | A1 |
| 20120324390 | Tao | Dec 2012 | A1 |
| 20120326873 | Utter, II | Dec 2012 | A1 |
| 20130013327 | Horseman | Jan 2013 | A1 |
| 20130017846 | Schoppe | Jan 2013 | A1 |
| 20130027341 | Mastandrea | Jan 2013 | A1 |
| 20130031490 | Joo et al. | Jan 2013 | A1 |
| 20130044072 | Kobayashi et al. | Feb 2013 | A1 |
| 20130047034 | Salomon et al. | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130054150 | Sacks et al. | Feb 2013 | A1 |
| 20130054634 | Chakraborty et al. | Feb 2013 | A1 |
| 20130055147 | Vasudev et al. | Feb 2013 | A1 |
| 20130063383 | Anderssonreimer et al. | Mar 2013 | A1 |
| 20130069893 | Brinda et al. | Mar 2013 | A1 |
| 20130093715 | Marsden et al. | Apr 2013 | A1 |
| 20130103814 | Carrasco et al. | Apr 2013 | A1 |
| 20130106603 | Weast et al. | May 2013 | A1 |
| 20130106684 | Weast et al. | May 2013 | A1 |
| 20130111579 | Newman et al. | May 2013 | A1 |
| 20130117696 | Robertson et al. | May 2013 | A1 |
| 20130132028 | Crankson et al. | May 2013 | A1 |
| 20130137073 | Nacey et al. | May 2013 | A1 |
| 20130143512 | Hernandez et al. | Jun 2013 | A1 |
| 20130184613 | Homsi et al. | Jul 2013 | A1 |
| 20130188322 | Lowe | Jul 2013 | A1 |
| 20130190083 | Toy et al. | Jul 2013 | A1 |
| 20130197679 | Balakrishnan et al. | Aug 2013 | A1 |
| 20130203475 | Kil et al. | Aug 2013 | A1 |
| 20130205210 | Jeon et al. | Aug 2013 | A1 |
| 20130217979 | Blackadar et al. | Aug 2013 | A1 |
| 20130222270 | Winkler et al. | Aug 2013 | A1 |
| 20130225118 | Jang et al. | Aug 2013 | A1 |
| 20130239063 | Ubillos et al. | Sep 2013 | A1 |
| 20130246202 | Tobin | Sep 2013 | A1 |
| 20130254685 | Batraski et al. | Sep 2013 | A1 |
| 20130254705 | Mooring et al. | Sep 2013 | A1 |
| 20130260896 | Miura et al. | Oct 2013 | A1 |
| 20130262155 | Hinkamp | Oct 2013 | A1 |
| 20130290013 | Forrester | Oct 2013 | A1 |
| 20130295872 | Guday et al. | Nov 2013 | A1 |
| 20130304276 | Flies | Nov 2013 | A1 |
| 20130320080 | Olson et al. | Dec 2013 | A1 |
| 20130325394 | Yuen et al. | Dec 2013 | A1 |
| 20130325396 | Yuen et al. | Dec 2013 | A1 |
| 20130332856 | Sanders et al. | Dec 2013 | A1 |
| 20130345978 | Lush et al. | Dec 2013 | A1 |
| 20140006769 | Chory et al. | Jan 2014 | A1 |
| 20140022183 | Ayoub et al. | Jan 2014 | A1 |
| 20140025737 | Kruglick | Jan 2014 | A1 |
| 20140058860 | Roh et al. | Feb 2014 | A1 |
| 20140058935 | Mijares | Feb 2014 | A1 |
| 20140059493 | Kim et al. | Feb 2014 | A1 |
| 20140068520 | Missig et al. | Mar 2014 | A1 |
| 20140073298 | Rossmann | Mar 2014 | A1 |
| 20140074407 | Hernandez-silveira et al. | Mar 2014 | A1 |
| 20140074570 | Hope et al. | Mar 2014 | A1 |
| 20140074717 | Evans | Mar 2014 | A1 |
| 20140075234 | Stekkelpak et al. | Mar 2014 | A1 |
| 20140081666 | Teller et al. | Mar 2014 | A1 |
| 20140081854 | Sanchez et al. | Mar 2014 | A1 |
| 20140082383 | De Cesare et al. | Mar 2014 | A1 |
| 20140082384 | De Cesare et al. | Mar 2014 | A1 |
| 20140094124 | Dave et al. | Apr 2014 | A1 |
| 20140128021 | Walker et al. | May 2014 | A1 |
| 20140134947 | Stouder-studenmund | May 2014 | A1 |
| 20140139637 | Mistry et al. | May 2014 | A1 |
| 20140143145 | Kortina et al. | May 2014 | A1 |
| 20140143678 | Mistry et al. | May 2014 | A1 |
| 20140149198 | Kim et al. | May 2014 | A1 |
| 20140164241 | Neuwirth | Jun 2014 | A1 |
| 20140172864 | Shum | Jun 2014 | A1 |
| 20140176475 | Myers et al. | Jun 2014 | A1 |
| 20140179272 | Zhang et al. | Jun 2014 | A1 |
| 20140181205 | Sherrets et al. | Jun 2014 | A1 |
| 20140181558 | Taha et al. | Jun 2014 | A1 |
| 20140187314 | Perry et al. | Jul 2014 | A1 |
| 20140187323 | Perry | Jul 2014 | A1 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140195826 | Wojcik et al. | Jul 2014 | A1 |
| 20140199966 | Schushan | Jul 2014 | A1 |
| 20140208250 | Ording et al. | Jul 2014 | A1 |
| 20140218369 | Yuen et al. | Aug 2014 | A1 |
| 20140236459 | Boesch et al. | Aug 2014 | A1 |
| 20140239065 | Zhou et al. | Aug 2014 | A1 |
| 20140240122 | Roberts et al. | Aug 2014 | A1 |
| 20140244009 | Mestas | Aug 2014 | A1 |
| 20140244495 | Davis et al. | Aug 2014 | A1 |
| 20140245161 | Yuen et al. | Aug 2014 | A1 |
| 20140245177 | Maklouf | Aug 2014 | A1 |
| 20140250391 | Jong et al. | Sep 2014 | A1 |
| 20140257537 | Stroupe et al. | Sep 2014 | A1 |
| 20140282103 | Crandall | Sep 2014 | A1 |
| 20140282153 | Christiansen et al. | Sep 2014 | A1 |
| 20140287821 | Barclay et al. | Sep 2014 | A1 |
| 20140289660 | Min et al. | Sep 2014 | A1 |
| 20140293755 | Geiser et al. | Oct 2014 | A1 |
| 20140304738 | Nakaoka et al. | Oct 2014 | A1 |
| 20140310618 | Venkatesh | Oct 2014 | A1 |
| 20140317543 | Kim | Oct 2014 | A1 |
| 20140325384 | Kobayashi | Oct 2014 | A1 |
| 20140325408 | Leppanen et al. | Oct 2014 | A1 |
| 20140337207 | Zhang et al. | Nov 2014 | A1 |
| 20140337450 | Choudhary et al. | Nov 2014 | A1 |
| 20140337451 | Choudhary et al. | Nov 2014 | A1 |
| 20140344723 | Malik et al. | Nov 2014 | A1 |
| 20140362056 | Zambetti et al. | Dec 2014 | A1 |
| 20150006376 | Nuthulapati et al. | Jan 2015 | A1 |
| 20150012425 | Mathew | Jan 2015 | A1 |
| 20150026615 | Choi et al. | Jan 2015 | A1 |
| 20150039494 | Sinton et al. | Feb 2015 | A1 |
| 20150052618 | Michalske | Feb 2015 | A1 |
| 20150057943 | Self et al. | Feb 2015 | A1 |
| 20150066758 | Denardis et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150100982 | Sirpal et al. | Apr 2015 | A1 |
| 20150106025 | Keller et al. | Apr 2015 | A1 |
| 20150121405 | Ekselius et al. | Apr 2015 | A1 |
| 20150130830 | Nagasaki et al. | May 2015 | A1 |
| 20150160856 | Jang et al. | Jun 2015 | A1 |
| 20150180980 | Welinder et al. | Jun 2015 | A1 |
| 20150185995 | Shoemaker et al. | Jul 2015 | A1 |
| 20150205509 | Scriven et al. | Jul 2015 | A1 |
| 20150205930 | Shaanan et al. | Jul 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150227782 | Salvador et al. | Aug 2015 | A1 |
| 20150256491 | Eatough et al. | Sep 2015 | A1 |
| 20150269848 | Yuen et al. | Sep 2015 | A1 |
| 20150286391 | Jacobs et al. | Oct 2015 | A1 |
| 20150295901 | Woodward et al. | Oct 2015 | A1 |
| 20150301506 | Koumaiha | Oct 2015 | A1 |
| 20150324751 | Orenstein et al. | Nov 2015 | A1 |
| 20150334546 | Diamond | Nov 2015 | A1 |
| 20150341695 | Pattan | Nov 2015 | A1 |
| 20150347711 | Soli et al. | Dec 2015 | A1 |
| 20150348009 | Brown et al. | Dec 2015 | A1 |
| 20150350141 | Yang et al. | Dec 2015 | A1 |
| 20150350861 | Soli et al. | Dec 2015 | A1 |
| 20150355804 | Nguyen et al. | Dec 2015 | A1 |
| 20150374310 | Lee | Dec 2015 | A1 |
| 20160004393 | Faaborg et al. | Jan 2016 | A1 |
| 20160014266 | Bhatt | Jan 2016 | A1 |
| 20160019360 | Pahwa et al. | Jan 2016 | A1 |
| 20160022202 | Peterson et al. | Jan 2016 | A1 |
| 20160027420 | Eronen | Jan 2016 | A1 |
| 20160028869 | Bhatt | Jan 2016 | A1 |
| 20160044269 | Kang | Feb 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160058337 | Blahnik et al. | Mar 2016 | A1 |
| 20160065505 | Iskander | Mar 2016 | A1 |
| 20160066005 | Davis et al. | Mar 2016 | A1 |
| 20160073034 | Mukherjee et al. | Mar 2016 | A1 |
| 20160089569 | Blahnik | Mar 2016 | A1 |
| 20160098137 | Kim et al. | Apr 2016 | A1 |
| 20160150063 | Choi et al. | May 2016 | A1 |
| 20160180568 | Bullivant et al. | Jun 2016 | A1 |
| 20160188181 | Smith et al. | Jun 2016 | A1 |
| 20160202889 | Shin et al. | Jul 2016 | A1 |
| 20160217601 | Tsuda et al. | Jul 2016 | A1 |
| 20160226713 | Dellinger et al. | Aug 2016 | A1 |
| 20160239724 | Arfvidsson et al. | Aug 2016 | A1 |
| 20160253864 | Weber et al. | Sep 2016 | A1 |
| 20160256741 | Holma et al. | Sep 2016 | A1 |
| 20160261675 | Block et al. | Sep 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160357363 | Decker et al. | Dec 2016 | A1 |
| 20160358133 | Van os et al. | Dec 2016 | A1 |
| 20160358134 | Van os et al. | Dec 2016 | A1 |
| 20160358180 | Van os et al. | Dec 2016 | A1 |
| 20170004507 | Henderson et al. | Jan 2017 | A1 |
| 20170026430 | Beckhardt et al. | Jan 2017 | A1 |
| 20170041549 | Kim et al. | Feb 2017 | A1 |
| 20170053542 | Wilson et al. | Feb 2017 | A1 |
| 20170063753 | Probasco et al. | Mar 2017 | A1 |
| 20170093769 | Lind et al. | Mar 2017 | A1 |
| 20170093780 | Lieb et al. | Mar 2017 | A1 |
| 20170123571 | Huang et al. | May 2017 | A1 |
| 20170134321 | Ushio et al. | May 2017 | A1 |
| 20170239524 | Lee et al. | Aug 2017 | A1 |
| 20170243508 | Cheng et al. | Aug 2017 | A1 |
| 20170269792 | Xu et al. | Sep 2017 | A1 |
| 20170281057 | Blahnik et al. | Oct 2017 | A1 |
| 20170344257 | Gnedin et al. | Nov 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170359623 | Folse et al. | Dec 2017 | A1 |
| 20180034765 | Keszler et al. | Feb 2018 | A1 |
| 20180039406 | Kong et al. | Feb 2018 | A1 |
| 20180081515 | Block et al. | Mar 2018 | A1 |
| 20180143761 | Choi et al. | May 2018 | A1 |
| 20190220243 | Decker et al. | Jul 2019 | A1 |
| 20190232110 | Williams et al. | Aug 2019 | A1 |
| 20190232111 | Williams et al. | Aug 2019 | A1 |
| 20190250813 | Block et al. | Aug 2019 | A1 |
| 20190334782 | Dellinger et al. | Oct 2019 | A1 |
| 20190339822 | Devine et al. | Nov 2019 | A1 |
| 20200149921 | Hoffman et al. | May 2020 | A1 |
| 20200213437 | Bhatt | Jul 2020 | A1 |
| 20210042028 | Block et al. | Feb 2021 | A1 |
| 20210092488 | Folse et al. | Mar 2021 | A1 |
| 20210263700 | Decker et al. | Aug 2021 | A1 |
| 20210289067 | Dellinger et al. | Sep 2021 | A1 |
| 20220047918 | Williams et al. | Feb 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2016100796 | Jun 2016 | AU |
| 2897539 | Oct 2014 | CA |
| 1443427 | Sep 2003 | CN |
| 1536511 | Oct 2004 | CN |
| 1782685 | Jun 2006 | CN |
| 1997050 | Jul 2007 | CN |
| 101061484 | Oct 2007 | CN |
| 101505320 | Aug 2009 | CN |
| 101822020 | Sep 2010 | CN |
| 101827363 | Sep 2010 | CN |
| 101828411 | Sep 2010 | CN |
| 101939740 | Jan 2011 | CN |
| 101978374 | Feb 2011 | CN |
| 102646081 | Aug 2012 | CN |
| 102989159 | Mar 2013 | CN |
| 103154954 | Jun 2013 | CN |
| 103297610 | Sep 2013 | CN |
| 103577108 | Feb 2014 | CN |
| 103581456 | Feb 2014 | CN |
| 103902808 | Jul 2014 | CN |
| 103914238 | Jul 2014 | CN |
| 103973899 | Aug 2014 | CN |
| 104288983 | Jan 2015 | CN |
| 104508426 | Apr 2015 | CN |
| 105874447 | Aug 2016 | CN |
| 107710197 | Feb 2018 | CN |
| 1705883 | Sep 2006 | EP |
| 1935339 | Jun 2008 | EP |
| 2025368 | Feb 2009 | EP |
| 2426902 | Mar 2012 | EP |
| 2632139 | Aug 2013 | EP |
| 2550639 | Nov 2017 | GB |
| 6187118 | Jul 1994 | JP |
| 2001-076078 | Mar 2001 | JP |
| 2002-73486 | Mar 2002 | JP |
| 2003-296246 | Oct 2003 | JP |
| 2003-337863 | Nov 2003 | JP |
| 2004-102609 | Apr 2004 | JP |
| 2004-258738 | Sep 2004 | JP |
| 2005-339017 | Dec 2005 | JP |
| 2006-230679 | Sep 2006 | JP |
| 2008-183339 | Aug 2008 | JP |
| 2008-272301 | Nov 2008 | JP |
| 2009-147889 | Jul 2009 | JP |
| 2010-12335 | Jan 2010 | JP |
| 2010-122901 | Jun 2010 | JP |
| 2011-125633 | Jun 2011 | JP |
| 2011-192126 | Sep 2011 | JP |
| 2011-198184 | Oct 2011 | JP |
| 2012-53642 | Mar 2012 | JP |
| 2012-203537 | Oct 2012 | JP |
| 2012-230503 | Nov 2012 | JP |
| 2012-533117 | Dec 2012 | JP |
| 2013-29925 | Feb 2013 | JP |
| 2013-54468 | Mar 2013 | JP |
| 2014-44724 | Mar 2014 | JP |
| 2014-216868 | Nov 2014 | JP |
| 2015-531916 | Nov 2015 | JP |
| 10-2004-0067514 | Jul 2004 | KR |
| 10-2009-0112132 | Oct 2009 | KR |
| 10-2013-0109466 | Oct 2013 | KR |
| 10-2013-0135282 | Dec 2013 | KR |
| 10-2014-0105309 | Sep 2014 | KR |
| 498240 | Aug 2002 | TW |
| 200512616 | Apr 2005 | TW |
| 201210368 | Mar 2012 | TW |
| 201240499 | Oct 2012 | TW |
| 9941682 | Aug 1999 | WO |
| 2005070289 | Aug 2005 | WO |
| 2007000012 | Jan 2007 | WO |
| 2007142703 | Dec 2007 | WO |
| 2007149731 | Dec 2007 | WO |
| 2008114491 | Sep 2008 | WO |
| 2012078079 | Jun 2012 | WO |
| 2013109762 | Jul 2013 | WO |
| 2013109777 | Jul 2013 | WO |
| 2014002711 | Jan 2014 | WO |
| 2014022711 | Feb 2014 | WO |
| 2014074407 | May 2014 | WO |
| 2014207294 | Dec 2014 | WO |
| 2016126733 | Aug 2016 | WO |
| Entry |
|---|
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Jul. 7, 2020, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Jul. 13, 2020, 10 pages. |
| Advisory Action received for U.S. Appl. No. 14/839,922, dated Mar. 24, 2017, 4 pages. |
| Extended European Search Report received for European Patent Application No. 18154145.9, dated Mar. 2, 2018, 8 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,424, dated Jun. 28, 2018, 12 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated May 19, 2017, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated Oct. 8, 2015, 20 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,922, dated Dec. 14, 2016, 22 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570668, dated Mar. 27, 2017, 2 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/037686, dated Mar. 1, 2018, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 16, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/032474, dated Dec. 15, 2016, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047282, dated Mar. 16, 2017, 26 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/032474, dated Aug. 19, 2015, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/047282, dated May 9, 2016, 33 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/037686, dated Sep. 9, 2016, 19 pages. |
| International Search Report received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 23, 2014, 3 pages. |
| International Written Opinion received for PCT Patent Application No. PCT/US2013/073195, dated Jun. 23, 2014, 8 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047282, dated Dec. 22, 2015, 7 pages. |
| “IPhone User Guide For iOS 7.1 Software”, available online at <https://manuals.info.apple.com/MANUALS/1000/MA1681/en_US/iphone_ios7_user_guide.pdf>, Mar. 10, 2014, pp. 1-162. |
| Jenbsjourney, “Wondering About a Fitbit?”, Available at: https://jenbsjourney.blogspot.kr/2013/08/wondering-about-fitbit.html, Aug. 6, 2013, 12 pages. |
| Kamijo, Noboru, “Next Generation Mobile System—WatchPad1.5”, Available at <http://researcher.ibm.com/researcher/view_group_subpage.php?id=5617>, retrieved on Jul. 4, 2015, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,916, dated Feb. 4, 2016, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,922, dated Feb. 25, 2016, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,372, dated Dec. 5, 2014, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,424, dated Jan. 17, 2018, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Jan. 11, 2018, 42 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Mar. 17, 2015, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/599,425, dated Oct. 26, 2016., 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/732,773, dated Jan. 19, 2018., 45 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,916, dated May 1, 2017, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,922, dated Aug. 17, 2016, 25 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015267240, dated Apr. 10, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015312215, dated Oct. 9, 2017, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201520358505.5, dated Jan. 13, 2016, 3 pages (2 pages of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Danish Patent Application No. PA201570666, dated Sep. 15, 2016, 1 page. |
| Notice of Allowance received for Danish Patent Application No. PA201570668, dated Oct. 30, 2017, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-535045, dated Mar. 2, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7033638, dated May 31, 2017, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104117509, dated Mar. 31, 2017, 3 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104128685, dated May 3, 2017, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/599,424, dated Dec. 13, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,916, dated Aug. 31, 2016, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,916, dated Jan. 10, 2018, 19 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Jan. 26, 2018, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Jul. 6, 2017, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,922, dated Nov. 2, 2017, 8 pages. |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Nov. 10, 2017, 8 pages (4 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2015100734, dated Jul. 29, 2015, 5 pages. |
| Office Action received for Australian Patent Application No. 2015267240, dated Apr. 10, 2017, 5 pages. |
| Office Action received for Australian Patent Application No. 2015267240, dated Mar. 21, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2015312215, dated Oct. 13, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2018200428, dated Mar. 7, 2018, 4 pages. |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Jul. 9, 2018, 11 pages (2 pages of English Translation and 9 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Nov. 28, 2017, 15 pages (5 pages of English Translation and 10 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201580028677.9, dated May 25, 2018, 14 pages (4 pages of English Translation and 10 pages of Official copy). |
| Office Action Received for Danish Patent Application No. PA201670656, dated Nov. 3, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570666, dated Feb. 2, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201570666, dated Jun. 27, 2016, 4 pages. |
| Office Action received for Danish Patent Application No. PA201570668, dated Apr. 8, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570668, dated Sep. 9, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670656, dated Jun. 14, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670656, dated May 30, 2018, 5 pages. |
| Office Action received for Danish Patent Application No. PA201770191, dated Jan. 25, 2018, 3 pages. |
| Office Action received for European Patent Application No. 13811085.3, dated Apr. 20, 2018, 15 pages. |
| Office Action received for European Patent Application No. 15730890.9, dated Aug. 3, 2017, 4 pages. |
| Office Action received for European Patent Application No. 18154145.9, dated Apr. 3, 2018, 6 pages. |
| Office Action received for European Patent Application No. 15771747.1, dated Oct. 31, 2017, 7 pages. |
| Office Action received for Japanese Patent Application No. 2016-535045, dated May 12, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Apr. 13, 2018, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-557650, dated Aug. 10, 2017, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Sep. 10, 2018, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014577, dated Dec. 26, 2017, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-7033638, dated Jan. 31, 2017, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104117509, dated Aug. 22, 2016, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104128685, dated Jan. 4, 2017, 40 pages (15 pages of English Translation and 25 pages of Official Copy). |
| Search Report and Opinion received for Danish Patent Application No. PA201770191, dated Jun. 30, 2017, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13811085.3, mailed on Jan. 26, 2018, 14 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15730890.9, mailed on Sep. 10, 2018, 11 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15771747.1, mailed on May 25, 2018, 17 pages. |
| “Utilization of Galaxy S4-S Health, ChatOn and Samsung Hub”, Available at: http://seeit.kr/1263, Jun. 12, 2013, 25 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Jun. 22, 2021, 2 pages. |
| European Search Report received for European Patent Application No. 21165295.3, dated Jun. 18, 2021, 4 pages. |
| Final Office Action received for U.S. Appl. No. 16/145,033, dated Jul. 6, 2021, 113 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204259, dated Jun. 11, 2021, 3 pages. |
| Office Action received for Australian Patent Application No. 2019266054, dated Jun. 29, 2021, 3 pages. |
| Office Action received for European Patent Application No. 21165295.3, dated Jul. 1, 2021, 10 pages. |
| Office Action received for European Patent Application No. 19724963.4, dated Jul. 28, 2020, 6 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Jan. 31, 2020, 3 pages. |
| Intention to Grant received for Danish Patent Application No. PA201870385, dated Jan. 24, 2020, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-569945, dated Jan. 7, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2018279037, dated Jan. 17, 2020, 4 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16804040.0, mailed on Jan. 24, 2020, 11 pages. |
| Wikipedia, “Emoji”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoji&oldid=648831795, Feb. 25, 2015, 12 pages. |
| Wikipedia, “Emoticon”, Available online at: https://en.wikipedia.org/w/index.php?title=Emoticon&oldid=648776142, Feb. 25, 2015, 9 pages. |
| Final Office Action received for U.S. Appl. No. 16/389,722, dated Dec. 8, 2020, 18 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Dec. 16, 2020, 6 pages. |
| Office Action received for Australian Patent Application No. 2020204259, dated Nov. 30, 2020, 8 pages. |
| Office Action received for Australian Patent Application No. 2020204506, dated Dec. 7, 2020, 6 pages. |
| Office Action received for European Patent Application No. 16762356.0, dated Dec. 11, 2020, 7 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, dated Dec. 15, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 16/377,892, dated Apr. 9, 2021, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Mar. 26, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Mar. 26, 2021, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Apr. 9, 2021, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/407,590, dated Mar. 22, 2021, 6 pages. |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Feb. 1, 2021, 8 pages (3 pages of English Translation and 5 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Dec. 23, 2020, 8 pages. |
| Certificate of Examination received for Australian Patent Application No. 2018101855, dated Aug. 6, 2019, 02 pages. |
| Office Action received for Australian Patent Application No. 2019100490, dated Jul. 26, 2019, 4 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Aug. 15, 2019, 3 pages. |
| Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Aug. 6, 2019, 6 pages. |
| Certificate of Examination received for Australian Patent Application No. 2019100490, dated Oct. 16, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 15/554,204, dated Oct. 31, 2019, 22 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/614,121, dated Nov. 4, 2019, 44 pages. |
| Advisory Action received for U.S. Appl. No. 16/389,722, dated Mar. 9, 2021, 5 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017277971, dated Feb. 17, 2021, 3 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, dated Sep. 21, 2021, 2 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 19724963.4, mailed on Sep. 3, 2021, 6 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2020-010239, dated Sep. 3, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Sep. 9, 2021, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Sep. 22, 2021, 7 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Nov. 6, 2019, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Nov. 5, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Internet Blog Post, “[PC] Pre-Customization of Black Desert's Characters”, Online Available at: https://blog.naver.com/hsh6051/220209813968,Dec. 14, 2014, 41 pages (21 pages of English translation and 20 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/407,590, dated Nov. 17, 2020, 6 pages. |
| Office Action received for Japanese Patent Application No. 2019-151358, dated Oct. 2, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Jun. 29, 2020, 5 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/869,877, dated Jun. 26, 2020, 14 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680008151.9, dated Jun. 16, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811330077.X, dated May 18, 2020, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Intention to Grant received for European Patent Application No. 18213157.3, dated May 19, 2021, 8 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201680013193.1, dated May 7, 2021, 5 pages (1 page of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/377,892, dated May 24, 2021, 9 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16762356.0, mailed on May 10, 2021, 10 pages. |
| Advisory Action received for U.S. Appl. No. 14/841,606, dated Feb. 28, 2019, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/869,877, dated Jan. 5, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/870,793, dated Apr. 13, 2017, 3 pages. |
| Certification of Examination received for Australian Patent Application No. 2018100158, dated Oct. 23, 2018, 2 pages. |
| Codrington, Simon, “Intuitive Scrolling Interfaces with CSS Scroll Snap Points”, Online Available at: https://www.sitepoint.com/intuitive-scrolling-interfaces-with-css-scroll-snap-points/,, Dec. 8, 2015, 14 pages. |
| Decision to Grant received for European Patent Application No. 16706081.3, dated Nov. 29, 2018, 2 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/870,793, dated Apr. 16, 2018, 15 pages. |
| Extended European Search Report received for European Patent Application No. 16762356.0, dated Nov. 9, 2018, 10 Pages. |
| Extended European Search Report received for European Patent Application No. 16804040.0, dated Feb. 26, 2018, 9 pages. |
| Extended European Search Report received for European Patent Application No. 18213157.3, dated Apr. 12, 2019, 8 pages. |
| Final Office Action received for U.S. Appl. No. 14/599,425, dated Jun. 12, 2018, 45 pages. |
| Final Office Action received for U.S. Appl. No. 14/841,606, dated Sep. 7, 2018, 34 pages. |
| Final Office Action received for U.S. Appl. No. 14/863,069, dated Jul. 5, 2018, 19 pages. |
| Final Office Action received for U.S. Appl. No. 14/864,759, dated Sep. 4, 2018, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Apr. 26, 2018, 18 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Aug. 3, 2016, 13 pages. |
| Final Office Action received for U.S. Appl. No. 14/870,726, dated Apr. 19, 2017, 17 pages. |
| Final Office Action received for U.S. Appl. No. 14/870,793, dated Jan. 19, 2017, 16 pages. |
| Final Office Action received for U.S. Appl. No. 15/614,121, dated Apr. 8, 2019, 32 pages. |
| Intention to Grant received for European Patent Application No. 16706081.3, dated Jul. 18, 2018, 8 pages. |
| Intention to Grant received for European Patent Application No. 16706081.3, dated Jun. 11, 2018, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/053353, dated Sep. 21, 2017, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/014997, dated Dec. 21, 2017, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/016216, dated May 4, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/021403, dated Sep. 21, 2017, 21 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/034175, dated Dec. 14, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035554, dated Dec. 20, 2018, 39 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/036608, dated Dec. 27, 2018, 12 pages. |
| International Search Report & Written Opinion received for PCT Patent Application No. PCT/US2016/014997, dated Aug. 31, 2016, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/053353, dated May 9, 2016, 21 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/016216, dated Jun. 27, 2016, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/021403, dated May 12, 2016, 23 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/034175, dated Oct. 7, 2016, 17 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035554, dated Sep. 22, 2017, 42 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/036608, dated Oct. 20, 2017, 15 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2016/014997, dated May 2, 2016, 5 pages. |
| Invitation to Pay Addition Fees and Partial International Search Report received for PCT Patent Application No. PCT/US2016/016216, dated Apr. 20, 2016, 6 pages. |
| Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2017/036608, dated Aug. 14, 2017, 2 pages. |
| Invitation to Pay Additional fees received for PCT Patent Application No. PCT/US2015/053353, dated Jan. 21, 2016, 7 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/034175, dated Aug. 11, 2016, 3 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/035554, dated Jul. 20, 2017, 2 pages. |
| Invitation to Restrict or Pay Additional Fees received for PCT Patent Application No. PCT/US2016/016216, dated Dec. 19, 2016, 9 pages. |
| IOS Security, “White Paper”, Available online at <https://web.archive.org/web/20150526223200/http://www.apple.com/business/docs/iOS_Security_Guide.pdf>, Apr. 2015, 55 pages. |
| “Mugs”, Online Available at: https://web.archive.org/web/20151029034349/http://le-mugs.com/,, Oct. 29, 2015. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Jan. 29, 2016, 18 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Jun. 16, 2017, 17 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Oct. 5, 2018, 19 pages. |
| Non Final Office Action received for U.S. Appl. No. 14/870,793, dated Apr. 19, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/554,204, dated Apr. 17, 2019, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated Dec. 7, 2017, 30 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/841,606, dated May 8, 2019, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/863,069, dated Oct. 5, 2017, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/864,759, dated Mar. 20, 2018, 20 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/870,726, dated Sep. 16, 2016, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/614,121, dated Nov. 30, 2018, 28 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016215440, dated Feb. 28, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016229847, dated Sep. 12, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201580028677.9, dated Apr. 2, 2019, 2 pages (1 pages of English Translation and 1 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/599,425, dated Dec. 19, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Feb. 6, 2019, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/864,759, dated Dec. 14, 2018, 10 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/870,726, dated Sep. 11, 2018, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Jan. 3, 2019, 8 pages. |
| Office Action received for Australian Patent Application No. 2016100796, dated Aug. 26, 2016, 6 pages. |
| Office Action received for Australian Patent Application No. 2016100796, dated Feb. 13, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2016215440, dated Jan. 22, 2019, 2 pages. |
| Office Action received for Australian Patent Application No. 2016215440, dated Mar. 13, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2016229847, dated Jul. 3, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016270323, dated Nov. 26, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017100231, dated Apr. 13, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017100667, dated Aug. 3, 2017, 9 pages. |
| Office Action received for Australian Patent Application No. 2017101375, dated Dec. 1, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017101375, dated Feb. 19, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2017286296, dated May 8, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018100158, dated Apr. 23, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2018101855, dated Feb. 22, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Apr. 1, 2019, 4 pages. |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Dec. 19, 2018, 13 pages (5 pages of English Translation and 8 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620509515.9, dated Nov. 9, 2016, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Danish Patent Application No. PA201670362, dated Jan. 29, 2018, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670362, dated Jun. 1, 2017, 6 pages. |
| Office Action received for Danish Patent Application No. PA201670362, dated Nov. 21, 2016, 11 pages. |
| Office Action received for Danish Patent Application No. PA201670749, dated Jan. 30, 2017, 11 pages. |
| Office Action received for Danish Patent Application No. PA201670749, dated Oct. 3, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670751, dated Jan. 13, 2017, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670751, dated Nov. 13, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Jun. 12, 2018, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770423, dated Mar. 29, 2019, 6 pages. |
| Office Action received for European Patent Application No. 16804040.0, dated May 13, 2019, 12 pages. |
| Office Action received for Japanese Patent Application No. 2017-545918, dated Sep. 14, 2018, 12 pages (7 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2017-562330, dated Jan. 18, 2019, 11 pages (6 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Sep. 28, 2018, 14 pages (6 pages of English Translation and 8 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Dec. 15, 2018, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Dec. 13, 2018, 26 pages (9 pages of English Translation and 17 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Mar. 23, 2017, 25 pages (10 pages of English Translation and 15 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104132636, dated Oct. 31, 2017, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Partial Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Apr. 25, 2019, 8 pages. |
| Preliminary Opinion received for European Patent Application No. 15730890.9, dated Mar. 7, 2019, 4 pages. |
| Razykdreviews, “In Depth Review of Apple Watch Activity and Workout App”, available at <URL: https://www.youtube.com/watch?v=GkKl3qlK0ow>, May 11, 2015, 1 page. |
| Rizknows, “Garmin Connect Mobile App—Review#2”, https://www.youtube.com/watch?v=7my3wMpeRbE, Oct. 22, 2015, 1 page. |
| Search Report and Opinion received for Danish Patent Application No. PA201770423, dated Oct. 4, 2017, 10 pages. |
| Search Report and Opinion received for Danish Patent Application No. PA201870385, dated Nov. 16, 2018, 10 Pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069 , dated Mar. 29, 2019, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Mar. 1, 2019, 3 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/870,726, dated Mar. 6, 2019, 6 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Mar. 28, 2019, 2 pages. |
| Tweedie, Steven, “Create and Customize Your Own Emojis with ‘Makemoji’ for iPhone”, Available online at: http://www.businessinsider.com/create-custom-emojis-with-makemoji-app-2014-8, Aug. 19, 2014, 6 pages. |
| Whitwam, Ryan, “Facer is Fast Becoming the De Facto Custom Watch Face Maker for Android Wear”, Available online at: http://www.androidpolice.com/2014/09/19/facer-is-fast-becoming-the-de-facto-custom-watch-face-maker-for-android-wear, Sep. 19, 2014, 11 pages. |
| Written Opinion Issued from International Preliminary Examining Authority for PCT Application No. PCT/US2016/016216, dated Feb. 20, 2017, 12 pages. |
| Decision to Refuse received for European Patent Application No. 17810749.6, dated Jan. 29, 2021, 24 pages. |
| Final Office Action received for U.S. Appl. No. 16/377,892, dated Jan. 28, 2021, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/378,136, dated Jan. 28, 2021, 9 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 17810749.6, mailed on Jan. 26, 2021, 8 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201710439448.7, dated Jan. 26, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Japanese Patent Application No. 2019-151358, dated Jan. 22, 2021, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2020-010239, dated Jan. 4, 2021, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 17810749.6, mailed on Jan. 18, 2021, 3 pages. |
| Result of Consultation received for European Patent Application No. 17810749.6, mailed on Jan. 21, 2021, 18 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Sep. 7, 2021, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/679,967, dated Sep. 2, 2021, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/116,775, dated Aug. 24, 2021, 20 pages. |
| Office Action received for Australian Patent Application No. 2019266054, dated Aug. 23, 2021, 4 pages. |
| Office Action received for Australian Patent Application No. 2018279037, dated Jun. 18, 2019, 5 pages. |
| Board Opinion received for Chinese Patent Application No. 201510284850.3, mailed on Jul. 2, 2021, 13 pages (3 pages of English Translation and 10 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, dated Jul. 15, 2021, 16 pages. |
| Office Action received for Chinese Patent Application No. 201780034193.4, dated Jun. 8, 2021, 16 pages (7 pages of English Translation and 9 pages of Official Copy). |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on Jul. 8, 2021, 3 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/863,099, mailed on Aug. 22, 2019, 9 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2019/024790, dated Jul. 18, 2019, 10 pages. |
| Office Action received for European Patent Application No. 17810749.6, dated Aug. 20, 2019, 9 pages. |
| Office Action received for Japanese Patent Application No. 2016-569945, dated Jul. 29, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Decision on Appeal received for U.S. Appl. No. 14/774,664, mailed on Sep. 12, 2019, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2019/024790, dated Sep. 11, 2019, 18 pages. |
| Office Action received for Danish Patent Application No. PA201870385, dated Aug. 23, 2019, 3 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/363,945, dated Apr. 24, 2020, 13 pages. |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Mar. 27, 2020, 13 pages (7 pages of English Translation and 6 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Nov. 24, 2020, 4 pages. |
| Decision to Refuse received for European Patent Application No. 16804040.0, dated Nov. 4, 2020, 18 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2019/024790, dated Nov. 19, 2020, 11 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 16804040.0, mailed on Nov. 2, 2020, 6 pages. |
| Office Action received for Chinese Patent Application No. 201710439448.7, dated Oct. 10, 2020, 19 pages (8 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811136445.7, dated Oct. 28, 2020, 17 pages (10 pages of English Translation and 7 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 16/377,892, dated May 21, 2020, 9 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017286296, dated May 1, 2020, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018279037, dated May 13, 2020, 3 pages. |
| Office Action received for European Patent Application No. 18213157.3, dated May 15, 2020, 7 pages. |
| Advisory Action received for U.S. Appl. No. 16/145,033, dated Nov. 2, 2021, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Oct. 25, 2021, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/116,775, dated Nov. 3, 2021, 4 pages. |
| Final Office Action received for U.S. Appl. No. 16/679,967, dated Nov. 10, 2021, 14 pages. |
| Intention to Grant received for European Patent Application No. 18213157.3, dated Oct. 27, 2021, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/068,386, dated Oct. 28, 2021, 20 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780034193.4, dated Oct. 20, 2021, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Sep. 24, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/863,099, dated Sep. 8, 2016, 3 pages. |
| Dharmasena, Anusha, “iMessage-Send as Text Message Option”, YouTube, Available online at: https://www.youtube.com/watch?v=hXG-MdlW6FA, Feb. 18, 2013, 1 page. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/774,664, dated May 31, 2018, 28 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/863,099, dated Jul. 28, 2017, 31 pages. |
| Final Office Action received for U.S. Appl. No. 14/774,664, dated Aug. 25, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/863,099, dated Apr. 21, 2016, 20 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2014/027882, dated Sep. 24, 2015, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/032498, dated Feb. 10, 2014, 18 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2014/027882, dated Oct. 10, 2014, 11 pages. |
| Invitation to Pay Addition Fees received for PCT Patent Application No. PCT/US2014/027882, dated Aug. 5, 2014, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/774,664, dated Mar. 7, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/863,099, dated Dec. 2, 2015, 12 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-545918, dated Jul. 22, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510284850.3, dated Jun. 21, 2019, 10 pages (4 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Jul. 8, 2019, 6 pages (3 pages of English Translation and 3 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-7024570, dated Jul. 10, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/377,892, dated Aug. 11, 2021, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Aug. 11, 2021, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201811136445.7, dated Aug. 11, 2021, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7029673, dated Aug. 3, 2021, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2020210234, dated Jul. 30, 2021, 7 pages. |
| Office Action received for Chinese Patent Application No. 201780034203.4, dated Jul. 14, 2021, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Phandroid, “How to record & stream using YouTube Gaming”, Available online at: https://www.youtube.com/watch?v=8H5Q1L9M_ql, Jun. 1, 2016, 3 pages. |
| Sansford Steve, “Streaming Android Games with OBS On Linux”, Available online at: https://www.youtube.com/watch?v=twyh32Ud8vQ, May 20, 2016, 3 pages. |
| Xzulas, “PS4 to Twitch—How to Broadcast Gameplay—Camera and Audio Settings”, Available online at: https://www.youtube.com/watch?v=TyTR64RF0wl, Nov. 3, 2014, 4 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/363,945, dated Aug. 13, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/554,204, dated Aug. 19, 2020, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/407,590, dated Aug. 25, 2020, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/614,121, dated Aug. 27, 2020, 8 pages. |
| Office Action received for Australian Patent Application No. 2017277971, dated Aug. 12, 2020, 3 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 17810749.6, mailed on Aug. 12, 2020, 11 pages. |
| Final Office Action received for U.S. Appl. No. 16/145,033, dated Sep. 22, 2020, 49 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/363,945, dated Sep. 23, 2020, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Sep. 3, 2020, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Apr. 30, 2021, 4 pages. |
| Office Action received for Chinese Patent Application No. 201811136445.7, dated Apr. 14, 2021, 7 pages (4 pages of English Translation and 3 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/145,033, dated Oct. 7, 2021, 4 pages. |
| Intention to Grant received for European Patent Application No. 19724963.4, dated Sep. 20, 2021, 7 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/377,892, dated Oct. 13, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/378,136, dated Oct. 13, 2020, 4 pages. |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Sep. 7, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for European Patent Application No. 19163212.4, dated Oct. 12, 2020, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7038235, dated Mar. 9, 2020, 15 pages (7 pages of English Translation and 8 pages of Official Copy). |
| Extended European Search Report received for European Patent Application No. 19163212.4, dated Jun. 25, 2019, 11 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Jun. 11, 2019, 35 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/863,069, dated Jun. 18, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2016270323, dated May 29, 2019, 4 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Jun. 4, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Wikipedia, “Enhanced Multi-Level Precedence And Pre-emption Service”, “Available online at: https://de.wikipedia.org/w/index.php?%20title=Enhanced%20Multi%E3%83%BCLevel_Precedence_And_Pre-emption_Service&oldid=123047429”,Oct. 2013, 2 pages {(Official Copy Only) See Communication under 37 CFR § 1.98(a) (3)}. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/614,121, dated Feb. 13, 2020, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/145,033, dated Mar. 4, 2020, 50 pages. |
| Office Action received for Australian Patent Application No. 2018206772, dated Feb. 6, 2020, 4 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Feb. 11, 2021, 4 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/145,033, dated Feb. 9, 2021, 55 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/407,590, dated Jun. 5, 2020, 3 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16804040.0, mailed on May 28, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/378,136, dated Jun. 2, 2020, 8 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201610371774.4, dated Jun. 4, 2020, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Australian Patent Application No. 2017277971, dated Jun. 3, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201680008151.9, dated Apr. 20, 2020, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680013193.1, dated Mar. 25, 2020, 21 pages (8 pages of English Translation and 13 pages of Official Copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 15/554,204, dated Oct. 11, 2019, 5 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2017-562330, dated Sep. 20, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201680008151.9, dated Aug. 27, 2019, 24 pages (11 pages of English Translation and 13 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-7034558, dated Sep. 25, 2019, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 11, 2021, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Jun. 3, 2021, 17 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/378,136, dated Jun. 3, 2021, 7 pages. |
| Result of Consultation received for European Patent Application No. 19724963.4, mailed on May 31, 2021, 3 pages. |
| Decision to Grant received for Danish Patent Application No. PA201870385, dated Mar. 26, 2020, 2 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/389,722, dated Apr. 3, 2020, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/407,590, dated Apr. 10, 2020, 12 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018206772, dated Mar. 17, 2020, 3 pages. |
| Advisory Action received for U.S. Appl. No. 15/554,204, dated Mar. 12, 2020, 3 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/614,121, dated Mar. 6, 2020, 8 pages. |
| Extended European Search Report received for European Patent Application No. 17813824.4, dated Dec. 5, 2019, 7 pages. |
| “How to Send and Receive files over Bluetooth on an Android Phone”, Online Available at: https://web.archive.org/web/20160529062240/http://www.androidtipsandhacks.com/android/send-receive-files-bluetooth-android-phone/, May 29, 2016, 7 pages. |
| “Kamcord—Wikipedia”, Online Available at: https://en.wikipedia.org/w/index.php?title=Kamcord&oldid=712263010>, Mar. 28, 2016, 2 pages. |
| “Kamcord Developers”, Online Available at: https://web.archive.org/web/20140827043641/http://www.kamcord.com/developers/>, Aug. 27, 2014, 7 pages. |
| “Kamcord Developers—Quick Start Guide”, Online Available at: https://web.archive.org/web/20140801055705/https://www.kamcord.com/developers/docs/ios/features-and-settings/, Aug. 1, 2014, 10 pages. |
| Office Action received for Chinese Patent Application No. 201610371774.4, dated Dec. 2, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201811330077.X, dated Nov. 13, 2019, 14 pages (6 pages of English Translation and 8 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/378,136, dated Apr. 12, 2021, 4 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020204506, dated Apr. 8, 2021, 3 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7029673, dated Apr. 8, 2021, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 17/327,204, dated Nov. 26, 2021, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2021-7036016, dated Nov. 10, 2021, 13 pages (6 pages of English Translation and 7 pages of Official Copy). |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 17/327,204, dated Jan. 25, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/068,386, dated Jan. 13, 2022, 2 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 17/126,571, dated Jan. 27, 2022, 4 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/116,775, dated Jan. 18, 2022, 10 pages. |
| Final Office Action received for U.S. Appl. No. 16/389,722, dated Dec. 6, 2021, 19 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2019266054, dated Nov. 25, 2021, 3 pages. |
| Office Action received for European Patent Application No. 17813824.4, dated Nov. 30, 2021, 8 pages. |
| Result of Consultation received for European Patent Application No. 16762356.0, mailed on Nov. 29, 2021, 3 pages. |
| Board Decision received for Chinese Patent Application No. 201510284850.3, dated Mar. 3, 2022, 27 pages (1 page of English Translation and 26 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2021203636, dated Mar. 23, 2022, 3 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 17/116,775, dated Jan. 28, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 19724963.4, dated Feb. 3, 2022, 2 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201780034203.4, dated Jan. 17, 2022, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Final Office Action received for U.S. Appl. No. 17/068,386, dated Mar. 3, 2022, 29 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/126,571, dated Mar. 11, 2022, 9 pages. |
| Office Action received for Australian Patent Application No. 2021203216, dated Mar. 7, 2022, 8 pages. |
| Office Action received for Japanese Patent Application No. 2021-023661, dated Feb. 25, 2022, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Jurick D. et al., “Iphone Hacks”, Tips & Tools for Unlocking the Power of Your iPhone & iPod touch, URL: https://api.pageplace.de/preview/DT0400.9780596550974_A23629666/preview-9780596550974_A23629666.pdf, Apr. 2009, 49 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/389,722, dated Feb. 18, 2022, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Feb. 10, 2022, 2 pages. |
| Decision to Grant received for European Patent Application No. 18213157.3, dated Feb. 24, 2022, 2 pages. |
| Intention to Grant received for European Patent Application No. 16762356.0, dated Dec. 23, 2021, 8 pages. |
| Minutes of Oral Proceedings received for European Patent Application No. 16762356.0, mailed on Dec. 17, 2021, 5 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/126,571, dated Dec. 21, 2021, 19 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 19163212.4, mailed on Dec. 15, 2021, 9 pages. |
| Decision to Grant received for European Patent Application No. 16762356.0, dated Apr. 26, 2022, 2 pages. |
| Extended European Search Report received for European Patent Application No. 22152524.9, dated May 2, 2022, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/516,537, dated May 5, 2022, 8 pages. |
| Extended European Search Report received for European Patent Application No. 22150207.3, dated Apr. 11, 2022, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/679,967, dated Apr. 19, 2022, 13 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020210234, dated Feb. 3, 2022, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2021203636, dated Apr. 14, 2022, 3 pages. |
| Office Action received for Australian Patent Application No. 2021218036, dated Jun. 21, 2022, 5 pages. |
| Puryear Blake, “A modular framework for home healthcare monitoring”, Online available at: https://scholarworks.uark.edu/cgi/viewcontent.cgi?article=1009&context=csceuht, May 2012, 92 pages. |
| Willem Jonker, “Secure Data Management”, Online available at: http://ndl.ethernet.edu.et/bitstream/123456789/21649/1/291.pdf, Sep. 17, 2010, 177 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/679,967, dated Jun. 1, 2022, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/327,204, dated May 18, 2022, 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20190349463 A1 | Nov 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62006032 | May 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14599424 | Jan 2015 | US |
| Child | 16388493 | US |
