Patent Grant
10914606
The present disclosure relates generally to mapping applications.
Mapping applications have become increasingly popular due to the proliferation of location-aware mobile electronic devices. Typically, users can interact with these mapping applications using touch-sensitive displays that are capable of both receiving user input and displaying portions of a map. While interacting with mapping applications in this way can be intuitive and simple on many electronic devices, it can be problematic when performed on compact mobile electronic devices having smaller displays. For example, it can be difficult to view route navigation directions overlaid on a map when displayed on a display of a compact mobile electronic device, such as a watch. Similarly, it can be difficult to type an address using a virtual keyboard displayed on the display of a compact mobile electronic device.
Some mapping application techniques using electronic devices, however, are generally cumbersome and inefficient. For example, some existing techniques use a complex and time-consuming user interface, which may include multiple key presses or keystrokes. Existing techniques require more time than necessary, wasting user time and device energy. This latter consideration is particularly important in battery-operated devices.
Accordingly, the present technique provides electronic devices with faster, more efficient methods and interfaces for interacting with mapping applications. Such methods and interfaces optionally complement or replace other methods for interacting with mapping applications. Such methods and interfaces reduce the cognitive burden on a user and produce a more efficient human-machine interface. For battery-operated computing devices, such methods and interfaces conserve power and increase the time between battery charges.
The present disclosure relates to systems and processes for interacting with mapping applications. In one example, a virtual assistant server can efficiently communicate with a map server to provide a user with map data in response to spoken user requests received at a user device. In another example, communicatively coupled electronic devices can be synchronized such that a location marker generated on one device can be displayed on the other device. In yet another example, an electronic device can display simplified views of individual route directions that can be updated based on movement of the user or in response to user requests. In yet another example, an electronic device can selectively display an interface including a current location of a user or an interface including a route to a predicted destination based on contextual information associated with the user. The interfaces can include affordances for causing the electronic device to launch an associated mapping application.
In some embodiments, a computer-implemented method at one or more servers is described. The method includes: receiving, from an electronic device: data corresponding to an audio input comprising user speech; and contextual data representing a context of the user speech; generating a textual representation of the user speech based on the data corresponding to the audio input; transmitting, to a map server, the textual representation of the user speech and the contextual data; receiving, from the map server, map data; and transmitting, to the electronic device, the map data.
In some embodiments, a system is described. The system includes: means for receiving data corresponding to an audio input comprising user speech; means for receiving contextual data representing a context of the user speech; means for generating a textual representation of the user speech based on the data corresponding to the audio input; means for transmitting, to a map server, the textual representation of the user speech and the contextual data; means for receiving, from the map server, map data; and means for transmitting, to the electronic device, the map data.
In some embodiments, a computer-implemented method at a first electronic device is described. The method includes: causing, on a display of the first electronic device, a display of a map; determining whether a first request to mark a first location on the map has been received; and in accordance with a determination that the first request to mark the first location on the map has been received: causing, on the display of the first electronic device, a display of a first location marker on the map at a position within the display corresponding to the first location; and transmitting, to a second electronic device, a first set of geographic coordinates corresponding to the first location.
In some embodiments, a system is described. The system includes: means for causing, on a display of a first electronic device, a display of a map; means for determining whether a first request to mark a first location on the map has been received; means for causing, on the display of the first electronic device, a display of a first location marker overlaid on the map at a position within the display corresponding to the first location in accordance with a determination that the first request to mark the first location on the map has been received; and means for transmitting, to a second electronic device, a first set of geographic coordinates corresponding to the first location in accordance with a determination that the first request to mark the first location on the map has been received.
In some embodiments, a computer-implemented method at an electronic device is described. The method includes: receiving an ordered set of route directions for navigating a route from a start location to an end location, wherein the route comprises a plurality of segments; and causing, on a display of the electronic device, a display of first route direction interface associated with a first route direction of the set of route directions, wherein the first route direction is associated with a first segment of the plurality of segments and comprises a first directional instruction and a first segment identifier associated with the first segment, and wherein the first route direction interface comprises: a first textual description of the first directional instruction and the first segment identifier; and a first visual representation of the first directional instruction.
In some embodiments, a system is described. The system includes: means for receiving an ordered set of route directions for navigating a route from a start location to an end location, wherein the route comprises a plurality of segments; and means for causing a display of first route direction interface associated with a first route direction of the set of route directions, wherein the first route direction is associated with a first segment of the plurality of segments and comprises a first directional instruction and a first segment identifier associated with the first segment, and wherein the first route direction interface comprises: a first textual description of the first directional instruction and the first segment identifier; and a first visual representation of the first directional instruction.
In some embodiments, a method at an electronic device with a display is described. The method includes: detecting a display triggering event; in accordance with a detection of the display triggering event, obtaining contextual data representing a context of the electronic device; determining, based on the contextual data, whether a user is likely to be traveling to a destination within a threshold length of time; in accordance with a determination that the user is likely to be traveling to the destination within the threshold length of time, causing, on the display, a display of a first interface representing a mapping application, wherein the first interface representing the mapping application comprises: a first affordance for launching the mapping application, and a set of information associated with traveling to the destination; and in accordance with a determination that the user is not likely to be traveling to the destination within the threshold length of time, causing, on the display, a display of a second interface representing the mapping application, wherein the second interface representing the mapping application comprises: a second affordance for launching the mapping application, and a visual representation of a location of the electronic device.
In some embodiments, a system is described. The system includes: means for detecting a display triggering event; means for obtaining contextual data representing a context of the electronic device in accordance with a detection of the display triggering event; means for determining, based on the contextual data, whether a user is likely to be traveling to a destination within a threshold length of time; means for causing a display of a first interface representing a mapping application in accordance with a determination that the user is likely to be traveling to the destination within the threshold length of time, wherein the first interface representing the mapping application comprises: a first affordance for launching the mapping application, and a set of information associated with traveling to the destination; and means for causing a display of a second interface representing the mapping application in accordance with a determination that the user is not likely to be traveling to the destination within the threshold length of time, wherein the second interface representing the mapping application comprises: a second affordance for launching the mapping application, and a visual representation of a location of the electronic device.
In some embodiments, one or more servers are described. The one or more servers include a processing unit configured to: receive, from an electronic device: data corresponding to an audio input comprising user speech; and contextual data representing a context of the user speech; generate a textual representation of the user speech based on the data corresponding to the audio input; transmit, to a map server, the textual representation of the user speech and the contextual data; receive, from the map server, map data; and transmit, to the electronic device, the map data.
In some embodiments, a first electronic device is described. The first electronic device comprises a display unit and a processing unit coupled to the display unit, the processing unit configured to: cause, on the display unit of the first electronic device, a display of a map; determine whether a first request to mark a first location on the map has been received; and in accordance with a determination that the first request to mark the first location on the map has been received: cause, on the display unit of the first electronic device, a display of a first location marker on the map at a position within the display corresponding to the first location; and transmit, to a second electronic device, a first set of geographic coordinates corresponding to the first location.
In some embodiments, an electronic device is described. The electronic device includes a display unit and a processing unit coupled to the display unit, the processing unit configured to: receive an ordered set of route directions for navigating a route from a start location to an end location, wherein the route comprises a plurality of segments; and cause, on a display unit of the electronic device, a display of first route direction interface associated with a first route direction of the set of route directions, wherein the first route direction is associated with a first segment of the plurality of segments and comprises a first directional instruction and a first segment identifier associated with the first segment, and wherein the first route direction interface comprises: a first textual description of the first directional instruction and the first segment identifier; and a first visual representation of the first directional instruction.
In some embodiments, an electronic device is described. The electronic device includes a display unit and a processing unit coupled to the display unit, the processing unit configure to: detect a display triggering event; in accordance with a detection of the display triggering event, obtain contextual data representing a context of the electronic device; determine, based on the contextual data, whether a user is likely to be traveling to a destination within a threshold length of time; in accordance with a determination that the user is likely to be traveling to the destination within the threshold length of time, cause, on the display unit, a display of a first interface representing a mapping application, wherein the first interface representing the mapping application comprises: a first affordance for launching the mapping application, and a set of information associated with traveling to the destination; and in accordance with a determination that the user is not likely to be traveling to the destination within the threshold length of time, cause, on the display unit, a display of a second interface representing the mapping application, wherein the second interface representing the mapping application comprises: a second affordance for launching the mapping application, and a visual representation of a location of the electronic device.
Executable instructions for performing these functions are, optionally, included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are, optionally, included in a transitory computer-readable storage medium or other computer program product configured for execution by one or more processors.
Thus, devices are provided with faster, more efficient methods and interfaces for interacting with mapping applications, thereby increasing the effectiveness, efficiency, and user satisfaction with such devices. Such methods and interfaces may complement or replace other methods for interacting with mapping applications.
The following description sets forth exemplary methods, parameters and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
The present disclosure relates to systems and processes for interacting with mapping applications. In one example, a virtual assistant server can efficiently communicate with a map server to provide a user with map data in response to spoken user requests received at a user device. In another example, communicatively coupled electronic devices can be synchronized such that a location marker generated on one device can be displayed on the other device. In yet another example, an electronic device can display simplified views of individual route directions that can be updated based on movement of the user or in response to user requests. In yet another example, an electronic device can selectively display an interface including a current location of a user or an interface including a route to a predicted destination based on contextual information associated with the user. The interfaces can include affordances for causing the electronic device to launch an associated mapping application.
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 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 touch pads), 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 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.
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 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 and/or IEEE 802.11n), 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 or 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, infrared port, 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 converts 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 stores device/global internal state 157, as shown in
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 thresholds 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 (lift off) 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 (lift off) 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 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 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 address book 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 module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing 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 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 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 a 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 module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, 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 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 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 system controller 156, contact 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 system controller 156, contact 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 system controller 156, contact 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 system controller 156, contact 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 system controller 156, contact 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 system controller 156, contact 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 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 system 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 system 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 content of which is hereby incorporated by reference in its entirety.
Each of the above identified modules and applications correspond 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 re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 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, peripheral 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, 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 module 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 includes 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 lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (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 lift-off 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 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 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 touch-pads; 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, head set 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 (“UI”) that may be implemented on 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.
Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed May 8, 2013 and International Patent Application Serial No. PCT/US2013/069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed Nov. 11, 2013.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.
Input mechanism 508 may be a microphone, in some examples. Computing device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of computing device 500 can be a non-transitory computer readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including processes 700, 800, 1200, and 1900 (
As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of device 100, 300, and/or 500 (
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 third 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 option 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 may be an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. These smoothing algorithms may 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 description 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.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the term “open application” or “executing application” refers to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application may be any one of the following types of applications:
As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
A virtual assistant can be capable of accepting a user request at least partially in the form of a natural language command, request, statement, narrative, and/or inquiry. Typically, the user request seeks either an informational answer or performance of a task by the virtual assistant. A satisfactory response to the user request can include either provision of the requested informational answer, performance of the requested task, or a combination of the two. For example, a user can ask the virtual assistant a question, such as “Where am I right now?” Based on the user's current location, the virtual assistant can answer, “You are in Central Park.” The user can also request the performance of a task, for example, “Please remind me to call Mom at 4 PM today.” In response, the virtual assistant can acknowledge the request and then create an appropriate reminder item in the user's electronic schedule. During performance of a requested task, the virtual assistant can sometimes interact with the user in a continuous dialogue involving multiple exchanges of information over an extended period of time. There are numerous other ways of interacting with a virtual assistant to request information or performance of various tasks. In addition to providing verbal responses and taking programmed actions, the virtual assistant can also provide responses in other visual or audio forms (e.g., as text, alerts, music, videos, animations, etc.) and possibly using multiple devices (e.g., output text to speech via a phone headset and display text on a TV).
An example of a virtual assistant is described in Applicants' U.S. Utility application Ser. No. 12/987,982 for “Intelligent Automated Assistant,” filed Jan. 10, 2011, the entire disclosure of which is incorporated herein by reference.
As shown in
Server system 610 can include one or more virtual assistant servers 614 that can include a client-facing I/O interface 622, one or more processing modules 618, data and model storage 620, and an I/O interface to external services 616. The client-facing I/O interface 622 can facilitate the client-facing input and output processing for virtual assistant server 614. The one or more processing modules 618 can utilize data and model storage 620 to determine the user's intent based on natural language input and can perform task execution based on inferred user intent. In some examples, virtual assistant server 614 can communicate with external services, such as telephony services, calendar services, information services, messaging services, navigation services, and the like, through network(s) 608 for task completion or information acquisition. The I/O interface to external services 616 can facilitate such communications.
In the example shown in
In some examples, the client-side portion executed on user devices 602 and 604 can include mapping applications, which can provide client-side functionalities, such as user-facing input and output processing and communications with server system 610 and/or 623. For example, the mapping applications can request map data from server system 623 via server system 610 and/or can request map data from server system 623 directly. Additionally, in some examples, one user device (e.g., user device 602) can be communicatively coupled with another user device (e.g., user device 604) via a direct communication connection, such as Bluetooth, NFC, BTLE, or the like, or via a wired or wireless network, such as a local Wi-Fi network. In these examples, one user device (e.g., user device 604) can act as a proxy between the other user device (e.g., user device 602) and server system 610 and/or server system 623 by receiving data or requests for data from the other user device and transmitting the data or the requests for data to server system 610 and/or server system 623. Additionally, in these examples, the proxy user device can receive data or requests for data from server system 610 and/or server system 623 and can transmit the data or request for data to the other user device. By allowing one user device to act as a proxy for another advantageously provides a user device having limited communication capabilities and/or limited battery power, such as a watch or other compact electronic device, with that ability to access virtual assistant services provided by server system 610 and mapping services provided by server system 623 by leveraging the communication capabilities and/or battery power of another user device, such as a mobile phone, laptop computer, tablet computer, or the like. While only two user devices 602 and 604 are shown in
Although the functionality of the virtual assistant and mapping services are shown in
At block 702, an audio input including user speech can be received at a user device. The user speech can include an instruction, request, or any other desired input for a mapping application. For example, the user speech can include a request for route navigation directions from the user's current location to a point of interest, an instruction to zoom-in or zoom-out from a displayed view of a map, an input containing an address or name of a point of interest, or the like. In some examples, a user device (e.g., user device 602 or 604) can receive the audio input that includes the user's speech via a microphone. The microphone can convert the audio input into an analog or digital representation, and provide the audio data to one or more processors of the device. The data representing the audio input can be transmitted to one or more servers for processing. For instance, in some examples, user device 602 or 604 can receive an audio input that represents the user's speech, convert the audio input into an analog or digital representation, and transmit the data representing the audio input to virtual assistant server 614 of server system 610 via network(s) 608. In other examples, one user device (e.g., user device 604) can be used as a proxy between another user device (e.g., user device 602) and the server systems 610 and 623. In these examples, user device 602 can receive the audio input that represents the user's speech, convert the audio input into an analog or digital representation, transmit the data representing the audio input to user device 604, and user device 604 can transmit the data representing the audio input to virtual assistant server 614 of server system 610 via network(s) 608.
Additionally, in some examples, contextual data associated with the user input can be transmitted along with the data representing the audio input at block 702. In general, the contextual data can include any type of information associated with the user input that can be used to infer the user's intent. In some examples, the contextual data can include sensor information from user device 602 or 604, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, current time, distance to another object, and the like. The contextual information can additionally or alternatively include information associated with the physical state of user device 602 or 604, such as the device orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signal strength, etc., or the software state of user device 602 or 604, such as running processes, installed programs, past and present network activities, background services, error logs, resources usage, contents displayed on the device, contents of a portion of a map displayed on the device, length of time that a current view has been displayed on the device, length of time since receiving a user input, length of time an application has been opened or running, etc. Any of these types of contextual information can be provided to the virtual assistant server 614 as contextual information associated with the user input.
At block 704, data corresponding to the audio input and the contextual data transmitted by the user device at block 702 can be received by one or more virtual assistant servers. For example, virtual assistant server 614 of server system 610 can receive the data corresponding to the audio input and the contextual data transmitted by user device 602 or 604 via network(s) 608.
At block 706, the one or more virtual assistant servers can perform speech-to-text conversion on the data corresponding to the audio input to convert the user speech into a textual representation of the user speech. The user speech can be converted using any known speech-to-text conversion process. For example, virtual assistant server 614 of server system 610 can perform a speech-to-text conversion on the audio input received at block 704.
At block 708, the one or more virtual assistant servers can transmit the textual representation of the user speech generated at block 706 and the contextual data received at block 704 to one or more map servers. For example, virtual assistant server 614 of server system 610 can transmit the textual representation of the user speech generated at block 706 and the contextual data received at block 704 to map server 624 of server system 623 via network(s) 608. In some examples, the textual representation may not also be transmitted to the user device.
At block 710, the textual representation of the user speech and the contextual data transmitted by the one or more virtual assistant servers at block 708 can be received by one or more map servers. For example, map server 624 of server system 623 can receive the textual representation of the user speech and the contextual data transmitted by virtual assistant server 614 via network(s) 608.
At block 712, the one or more map servers can process the textual representation of the user speech using the contextual data to infer the user's intent. Based on the inferred intent, the one or more servers can identify a task flow with steps and parameters designed to accomplish the inferred user intent, inputting input requirements from the inferred user intent into the task flow, execute the task flow by invoking programs, methods, services, APIs, or the like, and/or generate map data to be provided to the user of the user device in response to their audio input. In some examples, the map data can include map tiles to be displayed on a user device, route navigation information containing directions from a start location to an end location, geographic coordinates, textual descriptions and/or visual representations of a location, a point of interest, an object of interest, or the like. For example, map server 624 can process the textual representation of the user speech using the contextual data received at block 710 to determine the appropriate map data to provide to the user. If, for example, the user speech included the request “Give me directions to the park,” map server 624 can process the request by using the contextual data to determine which park the user is likely referring to. The user's current location, the presence or absence of a park within the portion of a map being displayed by the user device, and the like, can be used to make this determination. Once a specific park is identified, a navigation algorithm can be performed using the user's current location as a start point and the location of the park as an end point. The algorithm can produce map data containing the route from the user to the park. Similar processes can be performed to respond to other user requests and inputs with appropriate map data.
At block 714, the one or more map servers can transmit the map data output by the processing of the textual representation of user speech performed at block 712 to the one or more virtual assistant servers. For example, map server 624 of server system 623 can transmit the map data generated at block 712 to virtual assistant server 614 of server system 610 via network(s) 608.
At block 716, the map data transmitted by the one or more map and navigation servers at block 714 can be received by one or more virtual assistant servers. For example, virtual assistant server 614 can receive the map data transmitted by map server 624 of server system 623 via network(s) 608. In other examples, at block 714, the one or more map servers can instead transmit the map data directly to the user device, rather than to the one or more virtual assistant servers.
At block 718, the one or more virtual assistant servers can transmit the map data received at block 716 to the user device. For example, virtual assistant server 614 of server system 610 can transmit the map data received at block 716 to user device 602 or 604 via network(s) 608.
At block 720, the map data transmitted by the one or more virtual assistant servers at block 718 can be received by the user device. For example, user device 602 or 604 can receive the map data transmitted by virtual assistant server 614 via network(s) 608. In some examples, where a user device is used as a proxy for another user device, block 720 can further include transmitting the map data to the proxied user device.
Using process 700, a mapping service can quickly respond to a request or other user input in the form of user speech. In particular, process 700 advantageously routes the converted textual representation of user speech and contextual information from the virtual assistant server directly to the map and navigation server for processing. This provides a speed improvement over existing systems that return the textual representation of user speech from the virtual assistant server to the user device and that require the user device to then transmit the received textual representation of user speech and the contextual information to the map and navigation server. The speed improvement can be particularly noticeable when the virtual assistant server and the map server are located in close proximity or are connected to the same network, resulting in the communication speed between the virtual assistant server and the map server being greater than the communication speed between the user device and the map server.
At block 802 of process 800, a first electronic device can display a map on a display of the device. For example, user device 602 or 604 can display a map similar to that shown in interface 900 of
At block 804, the first electronic device can determine whether a request to mark a location on the displayed map has been received. For example, user device 602 or 604 can determine whether a request to mark a location on the map displayed at block 802 has been received. The request can be input into the first electronic device in any desired manner. For example, the request can be made by a selection of a button displayed on the displace of the first electronic device, a depression of a physical button, a rotation of a rotatable mechanism, a touch at a location on a touch-sensitive display corresponding to the desired location of the map to be marked, a touch and hold on a location on a touch-sensitive display corresponding to the desired location of the map to be marked, a press at a location on a pressure-sensitive display corresponding to the desired location of the map to be marked, or the like. To illustrate,
At block 806, the first electronic device can display a location marker overlaid on the map at the location requested by the user at block 804. The location marker can include any element that is visually distinct from the underlying map to allow a user to identify the marked location. For example, user device 602 or 604 can display a location marker similar or identical to location marker 1102, shown in
At block 808, the first electronic device can transmit the geographic coordinates associated with the location marker displayed at block 806 to a second electronic device. In some examples, other information associated with the location marker displayed at block 806, such as a street name, address, city, country, zip code, or the like, can also be transmitted to the second electronic device. The second electronic device can be a device that has been paired with the first electronic device, is associated with a same user account as the first electronic device, or is otherwise associated with the first electronic device. For example, user device 602 (alternatively user device 604) can transmit the geographic coordinates of the location requested to be marked at block 804 to user device 604 (alternatively user device 602) via a direct communication connection, such as Bluetooth, NFC, BTLE, or the like, or via a wired or wireless network, such as a local Wi-Fi network. In some examples, the second electronic device can store the geographic coordinates and other information associated with the location marker. In other examples, user device 602 (alternatively user device 604) can transmit the geographic coordinates of the location requested to be marked at block 804 to a server or remote database that can be accessed by user device 604 (alternatively user device 602).
After transmitting the geographic coordinates and, optionally, the other information associated with the location marker to the second electronic device, process 800 can return to block 804. Blocks 804, 806, and 808 can repeatedly be performed to allow a user to mark any number of locations. In some examples, an additional location marker can be displayed overlaid on the map each time block 806 is performed. In these examples, the geographic coordinates and other information associated with the additional location markers can also be stored on the first electronic device. In other examples, the location marker displayed at block 806 can replace one or more existing location markers previously displayed on the map. In these examples, the geographic coordinates and other information associated with the new location marker can replace previously stored geographic coordinates and other information associated with one or more older location markers.
In some examples, the second electronic device can use the geographic coordinates (and, optionally, other information associated with the location marker) provided by the first electronic device at block 808 to display a location marker overlaid on a map being displayed by the second electronic device. The location marker can be the same or different than the location marker displayed by the first electronic device. This advantageously allows a user to open a mapping application on the first electronic device, mark a location of interest within the mapping application, and view the marked location of interest in a mapping application on a different electronic device.
In some examples, process 800 can be performed by both the first electronic device and the second electronic device such that a request to mark a location on one device can cause the same location to be marked on the other electronic device. In these examples, the electronic device receiving the geographic coordinates and other information associated with a location marker can store that information in addition to previously stored information associated with other location markers or can replace the previously stored information associated with other marker(s) with the newly received information. In other examples, process 800 can be performed to synchronize marked locations between more than two electronic devices. In these examples, block 808 can include transmitting the geographic coordinates (and, optionally, other information associated with the location marker and with the location requested to be marked at block 804) to the other electronic devices. Moreover, process 800 can also be performed by the additional electronic devices.
At block 1202, an electronic device can receive a set of route directions for navigating a route from a start location to an end location. For example, an electronic device, such as user device 602 or 604, can receive a set of route navigation directions from a map server, such as map server 624 of server system 623. In other examples, the electronic device can instead generate the route navigation directions locally on the electronic device. In some examples, the route can include one or more segments corresponding to roads, highways, or other predefined or arbitrary portions of the route. In these examples, the set of route directions can include an ordered set of directions that can each include a directional instruction (e.g., an instruction to turn, and instruction to travel straight, or the like) and a name or other identifier of an associated segment of the route (e.g., a road/street/highway name, unique identifier, or the like). For example, one direction of the set of route directions can be “Turn Right on A Street.” In this example, the direction includes a directional instruction “Turn Right” and a name of the associated segment “A Street.” The other directions of the set of route directions can similarly include a directional instruction and the name or other identifier of an associated segment of the route.
At block 1204, the electronic device (e.g., user device 602 or 604) can display a route direction interface representing a direction of the set of route directions received or generated at block 1202. In some examples, the direction represented by the route direction interface can be the first direction in the ordered set of route directions.
Referring back to
At block 1208, the electronic device (e.g., user device 602 or 604) can determine whether a request to change the displayed direction has been received. The request can be input into the electronic device in any desired manner. For example, the request can be made by selecting a button displayed on the displace of the first electronic device, turning a rotatable mechanism, pressing on a pressure-sensitive display, pressing a physical button on the electronic device, taping on a touch-sensitive display, performing a swipe gesture (e.g., horizontally or vertically) across a touch-sensitive display, or the like. In some examples, a swipe gesture detected by a touch-sensitive display that travels from left to right on the touch-sensitive display can be interpreted as a request to change the displayed direction to the previous direction in the ordered set of directions, and a swipe gesture detected by a touch-sensitive display that travels from right to left on the touch-sensitive display can be interpreted as a request to change the displayed direction to the next direction in the ordered set of directions. If it is determined that no request to change the displayed direction has been received, the process can proceed to block 1210. However, if it is instead determined that a request to change the displayed direction has been received, the process can proceed to block 1214 where a route direction interface representing the direction requested to be displayed at block 1208 can be displayed.
In some examples, a downward swipe gesture (e.g., traveling from top to bottom) detected by a touch-sensitive display can be interpreted as a request to change the displayed direction to the previous direction in the ordered set of directions, and an upward swipe gesture (e.g., traveling from bottom to top) detected by a touch-sensitive display can be interpreted as a request to change the displayed direction to the next direction in the ordered set of directions. In some examples, rather than displaying a single direction in the ordered set of directions on the touch-sensitive display, multiple directions of the ordered set of directions are simultaneously displayed on the touch-sensitive display (e.g., as a list). As a result, the downward swipe gesture and the upward swipe gesture may be used to scroll through multiple directions in the ordered set of directions.
In some examples, an upward swipe gesture (e.g., traveling from bottom to top) detected by a touch-sensitive display can be interpreted as a request to change the displayed direction to the previous direction in the ordered set of directions, and an downward swipe gesture (e.g., traveling from top to bottom) detected by a touch-sensitive display can be interpreted as a request to change the displayed direction to the next direction in the ordered set of directions. In some examples, rather than displaying a single direction in the ordered set of directions on the touch-sensitive display, multiple directions of the ordered set of directions are simultaneously displayed on the touch-sensitive display (e.g., as a list). As a result, the downward swipe gesture and the upward swipe gesture may be used to scroll through multiple directions in the ordered set of directions.
At block 1210, the electronic device (e.g., user device 602 or 604) can determine whether a request to view a map view of a displayed direction has been received. The request can be input into the electronic device in any desired manner. For example, the request can be made by selecting a button displayed on the displace of the first electronic device, pressing on a pressure-sensitive display, turning a rotatable mechanism, pressing a physical button on the electronic device, taping on a touch-sensitive display, performing a swipe gesture (e.g., horizontally or vertically) across a touch-sensitive display, or the like. In some examples, a swipe gesture detected by a touch-sensitive display that travels from top to bottom of the touch-sensitive display can be interpreted as a request to view a map representation of the direction currently being displayed. In other examples, a swipe gesture detected by a touch-sensitive display that travels from bottom to top of the touch-sensitive display can be interpreted as a request to view a map representation of the direction currently being displayed. In other examples, a swipe gesture detected by a touch-sensitive display that travels from left to right on the touch-sensitive display can be interpreted as a request to view a map representation of the direction currently being displayed. In other examples, a swipe gesture detected by a touch-sensitive display that travels from right to left on the touch-sensitive display can be interpreted as a request to view a map representation of the direction currently being displayed. If it is determined that no request to view the map representation has been received, the process can return to block 1206. However, if it is instead determined that a request to view the map representation has been received, the process can proceed to block 1216 where a map view interface corresponding to the previously displayed direction (e.g., the direction being displayed when the request to display the map view was received at block 1210) can be displayed.
To illustrate the operation of process 1200,
At block 1206, if it is determined that the user's location has changed or if the user's location changed from a location corresponding to the route direction currently displayed to a location corresponding to another route direction in the ordered set of route directions, process 1200 can proceed to block 1212. At block 1212, the electronic device (e.g., user device 602 or 604) can display a route direction interface representing the route direction corresponding to the new location of the user. To illustrate, continuing with the example described above and shown in
If it is then determined that no location change has occurred at block 1206, that no request to change the displayed direction is received at block 1208, and that a request (e.g., a swipe on the touch-sensitive display) to display a map view of the displayed direction is received at block 1210 while interface 1500 is being displayed (e.g., receiving a swipe gesture from the top of the touch-sensitive display of the electronic device to the bottom of the touch-sensitive display; receiving a swipe gesture from left to right on the touch-sensitive display of the electronic device; or receiving a swipe gesture from right to left on the touch-sensitive display of the electronic device), an interface similar to interface 1600, shown in
In some embodiments, while displaying a map view interface (e.g., 1400, 1600), the device receives user input corresponding to rotation of the rotatable input mechanism. In response to receiving the user input corresponding to the rotation of the rotatable input mechanism, the device pans (e.g., translates) the map view. In some examples, the direction of the pan of the map view is based on the ordered set of route directions. This allows the user view different portions of the map. In some examples, the direction of the pan is along a predetermined axis.
If it is determined that no change in location has occurred at block 1206 and that a request to change the displayed direction is received at block 1208 while interface 1500 is being displayed, the process can proceed to block 1214. At block 1214, the electronic device (e.g., user device 602 or 604) can display a route direction interface representing the direction requested to be displayed at block 1208. For example, if a request to view the next direction in the ordered set of directions was received while interface 1500 was being displayed (e.g., in response to receiving a swipe gesture from the right of the touch-sensitive display of the electronic device to the left of the touch-sensitive display), an interface similar to interface 1700, shown in
If it is then determined that no location change has occurred at block 1206, that no request to change the displayed direction is received at block 1208, and that a request to display a map view of the displayed direction is received at block 1210 while interface 1700 is being displayed (e.g., receiving a swipe gesture from the top of the touch-sensitive display of the electronic device to the bottom of the touch-sensitive display), an interface similar to interface 1800, shown in
While the blocks of process 1200 are shown in a particular order, it should be appreciated that the blocks can be performed in any order and some blocks may not be performed at all. For example, blocks 1206, 1208, and 1210 can be evaluated in any order and with any desired frequency or at any desired interval of time to determine whether the displayed interface should be changed based on the user's location, a request to change the displayed direction, and a request to display a map view, respectively.
Using process 1200, individual route directions can be presented to a user in manner that allows the user to easily identify the next direction in the route with a quick glance at the user device. Additionally, process 1200 advantageously allows a user to scroll through previous or subsequent directions and to view map representations of the directions to obtain a better understanding of the route being displayed.
At block 1902 of process 1900, an electronic device (e.g., device 602 or 604) can detect a triggering event for activating a display of the electronic device. The triggering event can include any predefined or user-selected event. In some examples, detecting the triggering event can include detecting that the electronic device is moved into a position that can be viewed by a user. For example, if the electronic device is a wearable electronic device, such as a watch, detecting the triggering event can include detecting that the watch is raised and oriented in a direction that would be viewable by the user. In other examples, the triggering event can include the depression of a physical button, a touch on a touch-sensitive display, a press on a pressure-sensitive display, or the like. In response to detecting the triggering event, process 1900 can proceed to block 1904.
At block 1904, the electronic device (e.g., device 602 or 604) can obtain contextual data representing a context of the electronic device. In general, the contextual data can include any type of information associated with the user input that can be used to infer the user's intent. In some examples, the contextual data can include sensor information from user device 602 or 604, such as lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, distance to another object, and the like. The contextual information can additionally or alternatively include information associated with the physical state of user device 602 or 604, such as the device orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signal strength, etc., or the software state of user device 602 or 604, such as running processes, installed programs, past and present network activities, background services, error logs, resources usage, contents displayed on the device, contents of a portion of a map displayed on the device, length of time that a current view has been displayed on the device, length of time since receiving a user input, length of time an application has been opened or running, etc. The contextual data can additionally or alternatively include information associated with the user, such as the user's contact list, calendar, task or to-do list, historical activity data, preferences, or the like.
At block 1906, the electronic device (e.g., device 602 or 604) can determine, based on the contextual data obtained at block 1904, whether it is likely that the user will be traveling to a destination within a threshold length of time. This determination can be made, for example, based on the contextual data obtained at block 1904, which can include appointments (having locations and times) in the user's calendar, items (having locations and times) in the user's task or to-do list, a pattern of the user traveling to the same destination at the same time based on the historical activity of the user, or the like. The threshold length of time can be a predetermined value or can vary depending on the current location of the user and the location of the destination of the predicted travel. For example, the threshold length of time can be greater than or equal to an estimated travel time required for the user to travel from his/her current location to the destination of the predicted travel. This can depend on, for example, the distance to the destination, type of roads being traveled, traffic conditions, the user's mode of the transportation, length of time previously required to travel the same route, or the like. If it is determined that it is likely the user will be traveling, process 1900 can proceed to block 1908. Alternatively, if it is instead determined that it is not likely that the user will be traveling, process 1900 can proceed to block 1910.
At block 1908, the electronic device (e.g., device 602 or 604) can display an interface representing a mapping application based on the traveling predicted to be performed by the user determined at block 1906. The interface can generally include an affordance for opening or launching the mapping application and a set of data associated with the predicted traveling obtained from the mapping application that can be updated based on data from the application. The set of data associated with the predicted travel can include an estimated time of arrival at the destination, an estimated length of time to travel to the destination, one or more directions for traveling to destination, a map comprising at least a portion of a route to the destination, traffic information associated with the route to the destination, or the like. For example, an interface similar to interface 2000, shown in
In some examples, interface 2000 can include an affordance, such as a text label or icon, for opening or launching the represented mapping application. The affordance can include any portion or the entirety of the interface. For example, the affordance can include a virtual button or can include all of interface 2000. The electronic device can open the represented mapping application in response to selection of the affordance. For example, the electronic device can open the mapping application in response to a tap on a touch-sensitive display, a press on a pressure-sensitive display, a swipe gesture performed across a touch-sensitive display, a depression of a physical button, a turn of a rotatable mechanism, a selection of a displayed option, or the like, while interface 2000 is displayed. In some examples, the mapping application can be opened using the predicted travel determined at block 1906 as an input. For example, the mapping application can be opened and the predicted travel can be entered as a desired destination for a navigation route.
In some examples, interface 2000 can be generated using a process or application separate from the mapping application that it represents. In these examples, the mapping application may not be displayed and may instead be executed in the background.
In some examples, interface 2000 can include an affordance, such as a text label or icon, for opening or launching the represented mapping application. The affordance can include any portion or the entirety of the interface. For example, the affordance can include a virtual button or can include all of interface 2000. The electronic device can open the represented mapping application in response to selection of the affordance. For example, the electronic device can open the mapping application in response to a tap on a touch-sensitive display, a press on a pressure-sensitive display, a swipe gesture performed across a touch-sensitive display, a depression of a physical button, a turn of a rotatable mechanism, a selection of a displayed option, or the like, while interface 2000 is displayed. In some examples, the mapping application can be opened using the expected travel determined at block 1906 as an input. For example, the mapping application can be opened and the expected travel can be entered as a desired destination for a navigation route.
In some examples, interface 2100 can be generated using a process or application separate from the mapping application that it represents. In these examples, the mapping application may not be displayed and may instead be executed in the background.
At block 1910, the electronic device (e.g., device 602 or 604) can display an interface representing a mapping application based on the current location of the user since no predicted travel was determined at block 1906. The interface can generally include an affordance for opening or launching the mapping application and information associated with the user's current location. For example, an interface similar to interface 2200, shown in
Using process 1900, an electronic device can advantageously present the user with an interface containing an affordance for easily opening a mapping application. Additionally, the interface can advantageously modify the type of information presented in the interface to include information that is likely relevant to the user as determined by the electronic device based on contextual information. Moreover, the electronic device can launch the mapping application using the information displayed within the interface to reduce the amount of input required from the user to cause the mapping application to perform a desired function.
As shown in
Processing unit 2308 can be configured to receive (e.g., using audio receiving unit 2310) data corresponding to an audio input comprising user speech. Contextual data receiving unit 2312 can be configured to receive contextual data representing a context of the user speech. Generating unit 2314 can generate a textual representation of the user speech based on the data corresponding to the audio input. Text transmitting unit 2316 can transmit, to a map server, the textual representation of the user speech and the contextual data. Map data receiving unit 2318 can receive, from the map server, map data and map data transmitting unit 2320 can transmit the map data to the electronic device.
In some examples, the contextual data can include a location of the electronic device. In other examples, the contextual data can include a software state of the electronic device. In other examples, the contextual data can include a content being displayed by the electronic device. In other examples, the contextual data can include a state of a mapping application running on the electronic device. In some examples, the current state of the mapping application can include a current view of the mapping application being displayed on the electronic device. In some examples, the current state of the mapping application can include a length of time that the current view of the mapping application has been displayed. In some examples, the contextual data can include length of time since the electronic device received a user input.
In some examples, the map data can include: one or more map tiles, a set of geographic coordinates, routing information from a start location to an end location, or traffic data. In some examples, the textual representation of the user speech is not transmitted to the electronic device.
As shown in
Processing unit 2408 can be configured to cause (e.g., using map displaying unit 2410), on a display of a first electronic device, a display of a map. Determining unit 2412 can determine whether a first request to mark a first location on the map has been received. First location marker displaying unit 2414 can cause, on the display of the first electronic device, a display of a first location marker on the map at a position within the display corresponding to the first location in accordance with a determination that the first request to mark the first location on the map has been received. First geographic coordinate transmitting unit 2416 can transmit, to a second electronic device, a first set of geographic coordinates corresponding to the first location in accordance with a determination that the first request to mark the first location on the map has been received.
In some examples, storing unit 2418 can be configured to store, at the first electronic device, the first set of geographic coordinates.
In some examples, first location marker displaying unit 2414 can be further configured to cause, on the display of the first electronic device, a display of information associated with the first location. In some examples, the information associated with the first location can include an address, a street name, a name of a city, a name of a country, a zip code, or an estimated travel time to the first location.
In some examples, determining unit 2412 can be configured to determine whether the first request to mark the first location on the map has been received by determining whether a touch has been detected at the position within the display corresponding to the first location for more than a threshold length of time.
In some examples, determining unit 2412 can be further configured to determine whether a second request to mark a second location on the map has been received. Second location marker displaying unit 2420 can be configured to cause, on the display of the first electronic device, a display of a second location marker overlaid on the map at a position within the display corresponding to the second location in accordance with a determination that the second request to mark the second location on the map has been received. Second coordinate transmitting unit 2422 can be configured to transmit, to the second electronic device, a second set of geographic coordinates corresponding to the second location in accordance with a determination that the second request to mark the second location on the map has been received.
In some examples, second location marker displaying unit 2420 can configured to cause, on the display of the first electronic device, the display of the second location marker overlaid on the map by removing the first location marker from the display of the first electronic device. In some examples, storing unit 2418 can be configured to replace the stored first set of geographic coordinates with the second set of geographic coordinates.
In some examples, receiving unit 2424 can be configured to receive, at the first electronic device, a third set of geographic coordinates from the second electronic device. In some examples, storing unit 2418 can be further configured to replace the stored first set of geographic coordinates with the third set of geographic coordinates. In some examples, third location marker displaying unit 2426 can be configured to cause, on the display of the first electronic device, a display of a third location marker overlaid on the map at a position within the display corresponding to the third set of geographic coordinates.
In some examples, third location marker displaying unit 2426 can be further configured to cause, on the display of the first electronic device, the display of the third location marker overlaid on the map further by removing the first location marker from the display of the first electronic device.
As shown in
Processing unit 2508 can be configured to receive (e.g., using receiving unit 2510) an ordered set of route directions for navigating a route from a start location to an end location, wherein the route comprises a plurality of segments. Displaying unit 2512 can cause a display of first route direction interface associated with a first route direction of the set of route directions, wherein the first route direction is associated with a first segment of the plurality of segments and comprises a first directional instruction and a first segment identifier associated with the first segment, and wherein the first route direction interface comprises: a first textual description of the first directional instruction and the first segment identifier and a first visual representation of the first directional instruction.
In some examples, the first route direction interface excludes a map. In some examples, the first route direction interface excludes a view of any of the plurality of segments. In some examples, the first visual representation consists of an image of an arrow. In some examples, the first directional instruction includes an instruction to turn or an instruction to travel straight. In some examples, the first route direction interface further includes an estimated time of arrival at the end location.
In some examples, determining unit 2515 can be configured to determine whether a location of the electronic device corresponds to a second segment of the plurality of segments. In some examples, displaying unit 2512 can be configured to replace, in accordance with a determination that the location of the electronic device corresponds to the second segment of the plurality of segments, the first route direction interface with a second route direction interface associated with a second route direction of the set of route directions, wherein the second route direction is associated with the second segment of the plurality of segments and comprises a second directional instruction and a second segment identifier associated with the second segment, and wherein the second route direction interface comprises a second textual description of the second directional instruction and the second segment identifier and a second visual representation of the second directional instruction.
In some examples, determining unit 2512 can be configured to determine whether a request to view a third direction of the set of route directions has been received. In some examples, displaying unit 2512 can be configured to replace, in accordance with a determination that the request to view the third direction of the set of route directions has been received, the first route direction interface with a third route direction interface associated with a third route direction of the set of route directions, wherein the third route direction is associated with the third segment of the plurality of segments and comprises a third directional instruction and a third segment identifier associated with the third segment, and wherein the third route direction interface comprises: a third textual description of the third directional instruction and the third segment identifier and a third visual representation of the third directional instruction.
In some examples, determining unit 2512 can be configured to determine whether the request to view the third direction of the set of route directions has been received by determining whether a swipe gesture has been detected across the display of the electronic device. In some examples, the swipe gesture includes a horizontal swipe gesture.
In some examples, determining unit 2514 can be configured to determine whether a request to view a map view of the first direction has been received. In some examples, displaying unit 2512 can be configured to replace, in accordance with a determination that the request to view the map view of the first direction has been received, the first route direction interface with a first map view interface associated with the first route direction, wherein the first map view interface comprises a map comprising the first segment and a combined textual and visual representation of the first direction.
In some examples, determining unit 2514 can be configured to determine whether the request to view the map view of the first direction has been received by determining whether a swipe gesture has been detected across the display of the electronic device. In some examples, the swipe gesture includes a vertical swipe gesture.
As shown in
Processing unit 2608 can be configured to detect (e.g., using detecting unit 2610) a display triggering event. Obtaining unit 2612 can be configured to obtain contextual data representing a context of the electronic device in accordance with a detection of the display triggering event. Determining unit 2614 can be configured to determine, based on the contextual data, whether a user is likely to be traveling to a destination within a threshold length of time. First displaying unit 2616 can be configured to cause a display of a first interface representing a mapping application in accordance with a determination that the user is likely to be traveling to the destination within the threshold length of time, wherein the first interface representing the mapping application comprises: a first affordance for launching the mapping application and a set of information associated with traveling to the destination. Second displaying unit 2616 can be configured to cause a display of a second interface representing the mapping application in accordance with a determination that the user is not likely to be traveling to the destination within the threshold length of time, wherein the second interface representing the mapping application comprises: a second affordance for launching the mapping application and a visual representation of a location of the electronic device.
In some examples, the threshold length of time is greater than or equal to an estimated travel time to the destination.
In some examples, the contextual data comprises the user's calendar data and determining unit 2614 can be configured to determine whether the user is likely to be traveling to a destination by determining whether the user has a scheduled appointment within the threshold length of time based on the calendar data, the scheduled appointment associated with the destination.
In some examples, the contextual data includes the user's task list data and determining unit 2614 can be configured to determine whether the user is likely to be traveling to a destination by determining whether the user has a scheduled task to perform within the threshold length of time based on the task list data, the scheduled task associated with the destination.
In some examples, the contextual data includes the user's historical activity data and determining unit 2614 can be configured to determine whether the user is likely to be traveling to a destination by determining whether the user has a pattern of traveling to the destination at a time during a day, wherein the time during the day is within the threshold length of time from a current time.
In some examples, the set of information associated with traveling to the destination includes: an estimated time of arrival at the destination, an estimated length of time to travel to the destination, one or more directions for traveling to destination, a map comprising at least a portion of a route to the destination, or traffic information associated with the route to the destination.
In some examples, the mapping application is executing on the electronic device and is not displayed on the display.
In some examples, detecting unit 2610 can be further configured to detect a selection of the first affordance and first displaying unit 2616 can be configured to replace, in response to detecting the selection of the first affordance, the display of the first interface with a display of the mapping application.
In some examples, detecting unit 2610 can be further configured to detect a selection of the second affordance and second displaying unit 2618 can be configured to replace, in response to detecting the selection of the second affordance, the display of the second interface with a display of the mapping application.
In some examples, the display triggering event includes the electronic device being oriented in a predetermined orientation. In other examples the display triggering event includes a touch detected at the display of the electronic device.
Although the disclosure and examples have been fully described with reference to the accompanying figures, 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 disclosure and examples as defined by the appended claims.
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 may 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 embodiments 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 embodiments, the present disclosure also contemplates that the various embodiments can also be implemented without the need for accessing such personal information data. That is, the various embodiments 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 publically available information.
This application is a continuation of U.S. patent application Ser. No. 14/836,754 entitled “USER INTERACTIONS FOR A MAPPING APPLICATION”, filed on Aug. 26, 2015, which claims priority to U.S. Provisional Patent Application 62/129,849 entitled “USER INTERACTIONS FOR A MAPPING APPLICATION”, filed on Mar. 8, 2015; U.S. Provisional Patent Application 62/044,944 entitled “USER INTERACTIONS FOR A MAPPING APPLICATION”, filed on Sep. 2, 2014; and U.S. Provisional Patent Application 62/044,993 entitled “REDUCED-SIZE USER INTERFACES FOR DYNAMICALLY UPDATED APPLICATION OVERVIEWS”, filed on Sep. 2, 2014. The contents of these applications are hereby incorporated by reference in their entirety for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4803487 | Willard et al. | Feb 1989 | A |
| 5237159 | Stephens et al. | Aug 1993 | A |
| 5265007 | Barnhard et al. | Nov 1993 | A |
| 5484988 | Hills et al. | Jan 1996 | A |
| 5617031 | Tuttle | Apr 1997 | A |
| 5691524 | Josephson | Nov 1997 | A |
| 5717868 | James | Feb 1998 | A |
| 5729219 | Armstrong et al. | Mar 1998 | A |
| 5783808 | Josephson | Jul 1998 | A |
| 5815657 | Williams et al. | Sep 1998 | A |
| 5853327 | Gilboa | Dec 1998 | A |
| 5864337 | Marvin | Jan 1999 | A |
| 5910989 | Naccache | Jun 1999 | A |
| 5917913 | Wang | Jun 1999 | A |
| 5983197 | Enta | Nov 1999 | A |
| 6016484 | Williams et al. | Jan 2000 | A |
| 6097371 | Siddiqui et al. | Aug 2000 | A |
| 6164528 | Hills et al. | Dec 2000 | A |
| 6167353 | Piernot et al. | Dec 2000 | A |
| 6189785 | Lowery | Feb 2001 | B1 |
| 6190174 | Lam | Feb 2001 | B1 |
| 6193152 | Fernando et al. | Feb 2001 | B1 |
| 6230148 | Pare et al. | May 2001 | B1 |
| 6260027 | Takahashi et al. | Jul 2001 | B1 |
| 6282656 | Wang | Aug 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6328207 | Gregoire et al. | Dec 2001 | B1 |
| 6398646 | Wei et al. | Jun 2002 | B1 |
| 6416471 | Kumar et al. | Jul 2002 | B1 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6581042 | Pare et al. | Jun 2003 | B2 |
| 6597378 | Shiraishi et al. | Jul 2003 | B1 |
| 6644546 | George et al. | Nov 2003 | B2 |
| 6662166 | Pare et al. | Dec 2003 | B2 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6842182 | Ungar et al. | Jan 2005 | B2 |
| 6889138 | Krull et al. | May 2005 | B1 |
| 6944818 | Newman et al. | Sep 2005 | B2 |
| 6950810 | Lapsley et al. | Sep 2005 | B2 |
| 6963349 | Nagasaki | Nov 2005 | B1 |
| 6970855 | Das et al. | Nov 2005 | B2 |
| 7081905 | Raghunath | Jul 2006 | B1 |
| 7088342 | Rekimoto et al. | Aug 2006 | B2 |
| 7098896 | Kushler et al. | Aug 2006 | B2 |
| 7099845 | Higgins et al. | Aug 2006 | B2 |
| 7099850 | Mann, II et al. | Aug 2006 | B1 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7155411 | Blinn et al. | Dec 2006 | B1 |
| 7190349 | Kim et al. | Mar 2007 | B2 |
| 7305350 | Bruecken | Dec 2007 | B1 |
| 7347361 | Lovett | Mar 2008 | B2 |
| 7356516 | Richey et al. | Apr 2008 | B2 |
| 7359880 | Abel et al. | Apr 2008 | B2 |
| 7406666 | Davis et al. | Jul 2008 | B2 |
| 7430537 | Templeton et al. | Sep 2008 | B2 |
| 7496527 | Silverstein et al. | Feb 2009 | B2 |
| 7535344 | Obradovich | May 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7633076 | Huppi et al. | Dec 2009 | B2 |
| 7644019 | Woda et al. | Jan 2010 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657441 | Richey et al. | Feb 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7689508 | Davis et al. | Mar 2010 | B2 |
| 7810720 | Lovett | Oct 2010 | B2 |
| 7843471 | Doan et al. | Nov 2010 | B2 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7890422 | Hirka et al. | Feb 2011 | B1 |
| 7957762 | Herz et al. | Jun 2011 | B2 |
| RE42574 | Cockayne | Jul 2011 | E |
| 8006002 | Kalayjian et al. | Aug 2011 | B2 |
| 8050997 | Nosek et al. | Nov 2011 | B1 |
| 8105208 | Oleson et al. | Jan 2012 | B2 |
| 8121945 | Rackley et al. | Feb 2012 | B2 |
| 8157164 | Billman | Apr 2012 | B1 |
| 8195507 | Postrel | Jun 2012 | B2 |
| 8195576 | Grigg et al. | Jun 2012 | B1 |
| 8239784 | Hotelling et al. | Aug 2012 | B2 |
| 8279180 | Hotelling et al. | Oct 2012 | B2 |
| 8368658 | Brisebois et al. | Feb 2013 | B2 |
| 8381135 | Hotelling et al. | Feb 2013 | B2 |
| 8392259 | MacGillivray et al. | Mar 2013 | B2 |
| 8452654 | Wooters et al. | May 2013 | B1 |
| 8453940 | Diamond | Jun 2013 | B2 |
| 8479122 | Hotelling et al. | Jul 2013 | B2 |
| 8514186 | Tan et al. | Aug 2013 | B2 |
| 8554694 | Ward et al. | Oct 2013 | B1 |
| 8571937 | Rose et al. | Oct 2013 | B2 |
| 8583549 | Mohsenzadeh | Nov 2013 | B1 |
| 8606512 | Bogovich et al. | Dec 2013 | B1 |
| 8606640 | Brody et al. | Dec 2013 | B2 |
| 8619034 | Grad | Dec 2013 | B2 |
| 8706628 | Phillips | Apr 2014 | B2 |
| 8762272 | Cozens et al. | Jun 2014 | B1 |
| 8763896 | Kushevsky et al. | Jul 2014 | B2 |
| 8825445 | Hoffman et al. | Sep 2014 | B2 |
| 8831677 | Villa-Real | Sep 2014 | B2 |
| 8836768 | Rafii et al. | Sep 2014 | B1 |
| 8842082 | Migos et al. | Sep 2014 | B2 |
| 8880055 | Clement et al. | Nov 2014 | B1 |
| 8892474 | Inskeep et al. | Nov 2014 | B1 |
| 8894462 | Leyland et al. | Nov 2014 | B2 |
| 8924259 | Neighman et al. | Dec 2014 | B2 |
| 8924292 | Ellis et al. | Dec 2014 | B1 |
| 8931703 | Mullen et al. | Jan 2015 | B1 |
| 8942420 | Kim et al. | Jan 2015 | B2 |
| 9013423 | Ferren | Apr 2015 | B2 |
| 9244604 | Lewbel et al. | Jan 2016 | B1 |
| 9305310 | Radhakrishnan et al. | Apr 2016 | B2 |
| 9324067 | Van Os et al. | Apr 2016 | B2 |
| 9355393 | Purves et al. | May 2016 | B2 |
| 9389090 | Levine | Jul 2016 | B1 |
| 9436381 | Migos et al. | Sep 2016 | B2 |
| 9483763 | Van Os et al. | Nov 2016 | B2 |
| 9519901 | Dorogusker | Dec 2016 | B1 |
| 9547419 | Yang et al. | Jan 2017 | B2 |
| 9558636 | Burdick | Jan 2017 | B1 |
| 9574896 | McGavran et al. | Feb 2017 | B2 |
| 9818171 | Zaitsev et al. | Nov 2017 | B2 |
| 9851214 | Chintakindi | Dec 2017 | B1 |
| 9940637 | Van Os et al. | Apr 2018 | B2 |
| 10019904 | Chan et al. | Jul 2018 | B1 |
| 10250735 | Butcher et al. | Apr 2019 | B2 |
| 10251034 | Langlois et al. | Apr 2019 | B2 |
| 10282451 | Ho et al. | May 2019 | B1 |
| 10482461 | Van Os et al. | Nov 2019 | B2 |
| 20020004760 | Yoshida et al. | Jan 2002 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020023215 | Wang et al. | Feb 2002 | A1 |
| 20020029169 | Oki et al. | Mar 2002 | A1 |
| 20020046064 | Maury et al. | Apr 2002 | A1 |
| 20020065774 | Young et al. | May 2002 | A1 |
| 20020087262 | Bullock et al. | Jul 2002 | A1 |
| 20030006280 | Seita et al. | Jan 2003 | A1 |
| 20030061157 | Hirka et al. | Mar 2003 | A1 |
| 20030128237 | Sakai | Jul 2003 | A1 |
| 20030142227 | Van Zee | Jul 2003 | A1 |
| 20030171984 | Wodka et al. | Sep 2003 | A1 |
| 20030181201 | Bomze et al. | Sep 2003 | A1 |
| 20030182628 | Lira | Sep 2003 | A1 |
| 20030184528 | Kawasaki et al. | Oct 2003 | A1 |
| 20030200184 | Dominguez et al. | Oct 2003 | A1 |
| 20030236746 | Turner et al. | Dec 2003 | A1 |
| 20040044953 | Watkins et al. | Mar 2004 | A1 |
| 20040077462 | Brown et al. | Apr 2004 | A1 |
| 20040100389 | Naito et al. | May 2004 | A1 |
| 20040122685 | Bunce | Jun 2004 | A1 |
| 20040143553 | Torget et al. | Jul 2004 | A1 |
| 20040150630 | Hinckley et al. | Aug 2004 | A1 |
| 20040169722 | Pena | Sep 2004 | A1 |
| 20040215572 | Uehara et al. | Oct 2004 | A1 |
| 20040254891 | Blinn et al. | Dec 2004 | A1 |
| 20050012723 | Pallakoff | Jan 2005 | A1 |
| 20050052471 | Nagasaki | Mar 2005 | A1 |
| 20050117601 | Anderson et al. | Jun 2005 | A1 |
| 20050187873 | Labrou et al. | Aug 2005 | A1 |
| 20050190059 | Wehrenberg | Sep 2005 | A1 |
| 20050191159 | Benko | Sep 2005 | A1 |
| 20050197063 | White | Sep 2005 | A1 |
| 20050210417 | Marvit et al. | Sep 2005 | A1 |
| 20050237194 | Voba | Oct 2005 | A1 |
| 20050250538 | Narasimhan et al. | Nov 2005 | A1 |
| 20050253814 | Ghassabian | Nov 2005 | A1 |
| 20060000900 | Fernandes et al. | Jan 2006 | A1 |
| 20060017692 | Wehrenherg et al. | Jan 2006 | A1 |
| 20060025923 | Dotan et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060053392 | Salmimaa et al. | Mar 2006 | A1 |
| 20060064313 | Steinbarth et al. | Mar 2006 | A1 |
| 20060064372 | Gupta | Mar 2006 | A1 |
| 20060079973 | Bacharach | Apr 2006 | A1 |
| 20060132455 | Rimas-Ribikauskas et al. | Jun 2006 | A1 |
| 20060135064 | Cho et al. | Jun 2006 | A1 |
| 20060150087 | Cronenberger et al. | Jul 2006 | A1 |
| 20060165060 | Dua | Jul 2006 | A1 |
| 20060173749 | Ward et al. | Aug 2006 | A1 |
| 20060179404 | Yolleck et al. | Aug 2006 | A1 |
| 20060181518 | Shen et al. | Aug 2006 | A1 |
| 20060197750 | Kerr et al. | Sep 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060208065 | Mendelovich et al. | Sep 2006 | A1 |
| 20060218502 | Matthews et al. | Sep 2006 | A1 |
| 20060294007 | Barthelemy | Dec 2006 | A1 |
| 20060294025 | Mengerink | Dec 2006 | A1 |
| 20070061410 | Alperin | Mar 2007 | A1 |
| 20070096283 | Ljung et al. | May 2007 | A1 |
| 20070096765 | Kagan | May 2007 | A1 |
| 20070123205 | Lee et al. | May 2007 | A1 |
| 20070131759 | Cox et al. | Jun 2007 | A1 |
| 20070188409 | Repetto et al. | Aug 2007 | A1 |
| 20070194110 | Esplin et al. | Aug 2007 | A1 |
| 20070194113 | Esplin et al. | Aug 2007 | A1 |
| 20070219901 | Garbow et al. | Sep 2007 | A1 |
| 20070240079 | Flynt et al. | Oct 2007 | A1 |
| 20070254712 | Chitti | Nov 2007 | A1 |
| 20070255564 | Yee et al. | Nov 2007 | A1 |
| 20070260558 | Look | Nov 2007 | A1 |
| 20080006762 | Fadell et al. | Jan 2008 | A1 |
| 20080016443 | Hiroshima et al. | Jan 2008 | A1 |
| 20080027947 | Pritchett et al. | Jan 2008 | A1 |
| 20080040265 | Rackley III et al. | Feb 2008 | A1 |
| 20080040786 | Chang | Feb 2008 | A1 |
| 20080041936 | Vawter | Feb 2008 | A1 |
| 20080052181 | Devitt-carolan et al. | Feb 2008 | A1 |
| 20080054081 | Mullen | Mar 2008 | A1 |
| 20080059351 | Richey et al. | Mar 2008 | A1 |
| 20080067626 | Hirler et al. | Mar 2008 | A1 |
| 20080076637 | Gilley et al. | Mar 2008 | A1 |
| 20080077673 | Thomas | Mar 2008 | A1 |
| 20080078831 | Johnson et al. | Apr 2008 | A1 |
| 20080120029 | Zelek et al. | May 2008 | A1 |
| 20080120707 | Ramia | May 2008 | A1 |
| 20080126971 | Kojima | May 2008 | A1 |
| 20080141126 | Johnson et al. | Jun 2008 | A1 |
| 20080165136 | Christie et al. | Jul 2008 | A1 |
| 20080214191 | Yach et al. | Sep 2008 | A1 |
| 20080221903 | Kanevsky et al. | Sep 2008 | A1 |
| 20080247519 | Abella et al. | Oct 2008 | A1 |
| 20080275779 | Lakshminarayanan | Nov 2008 | A1 |
| 20080284741 | Hsu et al. | Nov 2008 | A1 |
| 20080292074 | Boni et al. | Nov 2008 | A1 |
| 20080319875 | Levchin et al. | Dec 2008 | A1 |
| 20080320391 | Lemay et al. | Dec 2008 | A1 |
| 20090005080 | Forstall et al. | Jan 2009 | A1 |
| 20090023433 | Walley et al. | Jan 2009 | A1 |
| 20090027495 | Oskin et al. | Jan 2009 | A1 |
| 20090030793 | Fordyce, III | Jan 2009 | A1 |
| 20090036165 | Brede | Feb 2009 | A1 |
| 20090037326 | Chitti et al. | Feb 2009 | A1 |
| 20090057396 | Barbour et al. | Mar 2009 | A1 |
| 20090083850 | Fadell et al. | Mar 2009 | A1 |
| 20090088207 | Sweeney et al. | Apr 2009 | A1 |
| 20090091541 | Chen | Apr 2009 | A1 |
| 20090138194 | Geelen | May 2009 | A1 |
| 20090159696 | Mullen | Jun 2009 | A1 |
| 20090167706 | Tan et al. | Jul 2009 | A1 |
| 20090173784 | Yang | Jul 2009 | A1 |
| 20090182674 | Patel et al. | Jul 2009 | A1 |
| 20090195402 | Izadi et al. | Aug 2009 | A1 |
| 20090195469 | Lim et al. | Aug 2009 | A1 |
| 20090199130 | Tsern et al. | Aug 2009 | A1 |
| 20090203315 | Kawabata et al. | Aug 2009 | A1 |
| 20090207743 | Huq et al. | Aug 2009 | A1 |
| 20090210308 | Toomer et al. | Aug 2009 | A1 |
| 20090213081 | Case, Jr. | Aug 2009 | A1 |
| 20090216556 | Martin et al. | Aug 2009 | A1 |
| 20090222748 | Lejeune et al. | Sep 2009 | A1 |
| 20090228825 | Van Os et al. | Sep 2009 | A1 |
| 20090256817 | Perlin et al. | Oct 2009 | A1 |
| 20090258677 | Ellis et al. | Oct 2009 | A1 |
| 20090307139 | Mardikar et al. | Dec 2009 | A1 |
| 20090325630 | Tlitola et al. | Dec 2009 | A1 |
| 20090327975 | Stedman | Dec 2009 | A1 |
| 20100019990 | Lee | Jan 2010 | A1 |
| 20100020034 | Kim | Jan 2010 | A1 |
| 20100023449 | Skowronek et al. | Jan 2010 | A1 |
| 20100026453 | Yamamoto et al. | Feb 2010 | A1 |
| 20100042517 | Paintin et al. | Feb 2010 | A1 |
| 20100078471 | Lin et al. | Apr 2010 | A1 |
| 20100078472 | Lin et al. | Apr 2010 | A1 |
| 20100082445 | Hodge et al. | Apr 2010 | A1 |
| 20100082462 | Yuan et al. | Apr 2010 | A1 |
| 20100082481 | Lin et al. | Apr 2010 | A1 |
| 20100082485 | Lin et al. | Apr 2010 | A1 |
| 20100100839 | Tseng et al. | Apr 2010 | A1 |
| 20100114731 | Kingston et al. | May 2010 | A1 |
| 20100125456 | Weng et al. | May 2010 | A1 |
| 20100125816 | Bezos | May 2010 | A1 |
| 20100131190 | Terauchl et al. | May 2010 | A1 |
| 20100131303 | Collopy et al. | May 2010 | A1 |
| 20100149090 | Morris et al. | Jun 2010 | A1 |
| 20100153265 | Hershfield et al. | Jun 2010 | A1 |
| 20100159909 | Stifelman | Jun 2010 | A1 |
| 20100161434 | Herwig et al. | Jun 2010 | A1 |
| 20100162170 | Johns et al. | Jun 2010 | A1 |
| 20100164864 | Chou | Jul 2010 | A1 |
| 20100185446 | Homma et al. | Jul 2010 | A1 |
| 20100191570 | Michaud et al. | Jul 2010 | A1 |
| 20100194682 | Orr et al. | Aug 2010 | A1 |
| 20100194692 | Orr et al. | Aug 2010 | A1 |
| 20100198453 | Dorogusker et al. | Aug 2010 | A1 |
| 20100205091 | Graziano et al. | Aug 2010 | A1 |
| 20100216425 | Smith | Aug 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100243741 | Eng | Sep 2010 | A1 |
| 20100267362 | Smith et al. | Oct 2010 | A1 |
| 20100272250 | Yap et al. | Oct 2010 | A1 |
| 20100281374 | Schulz et al. | Nov 2010 | A1 |
| 20100287513 | Singh et al. | Nov 2010 | A1 |
| 20100302168 | Giancarlo et al. | Dec 2010 | A1 |
| 20100306107 | Nahari | Dec 2010 | A1 |
| 20100311397 | Li | Dec 2010 | A1 |
| 20110040657 | Roswell | Feb 2011 | A1 |
| 20110059769 | Brunolli | Mar 2011 | A1 |
| 20110074699 | Marr et al. | Mar 2011 | A1 |
| 20110078025 | Shrivastav | Mar 2011 | A1 |
| 20110078614 | Lee et al. | Mar 2011 | A1 |
| 20110081860 | Brown et al. | Apr 2011 | A1 |
| 20110098928 | Hoffman et al. | Apr 2011 | A1 |
| 20110099079 | White | Apr 2011 | A1 |
| 20110145049 | Hertel et al. | Jun 2011 | A1 |
| 20110153628 | Basu et al. | Jun 2011 | A1 |
| 20110159959 | Mallinson et al. | Jun 2011 | A1 |
| 20110161116 | Peak et al. | Jun 2011 | A1 |
| 20110167369 | Van Os | Jul 2011 | A1 |
| 20110177845 | Fasold | Jul 2011 | A1 |
| 20110184820 | Mon et al. | Jul 2011 | A1 |
| 20110187647 | Woloszynski et al. | Aug 2011 | A1 |
| 20110201306 | Ali | Aug 2011 | A1 |
| 20110202417 | DeWakar et al. | Aug 2011 | A1 |
| 20110218849 | Rutigliano et al. | Sep 2011 | A1 |
| 20110225057 | Webb et al. | Sep 2011 | A1 |
| 20110227872 | Huska et al. | Sep 2011 | A1 |
| 20110244796 | Khan et al. | Oct 2011 | A1 |
| 20110251892 | Laracey | Oct 2011 | A1 |
| 20110258537 | Rives et al. | Oct 2011 | A1 |
| 20110283334 | Choi et al. | Nov 2011 | A1 |
| 20120015779 | Powch et al. | Jan 2012 | A1 |
| 20120022872 | Gruber et al. | Jan 2012 | A1 |
| 20120028609 | Hruska | Feb 2012 | A1 |
| 20120035924 | Jitkoff et al. | Feb 2012 | A1 |
| 20120036029 | Esplin et al. | Feb 2012 | A1 |
| 20120036556 | Lebeau et al. | Feb 2012 | A1 |
| 20120078751 | Macphail et al. | Mar 2012 | A1 |
| 20120084210 | Farahmand | Apr 2012 | A1 |
| 20120089300 | Wolterman | Apr 2012 | A1 |
| 20120089507 | Zhang et al. | Apr 2012 | A1 |
| 20120092383 | Hysek et al. | Apr 2012 | A1 |
| 20120101881 | Taylor et al. | Apr 2012 | A1 |
| 20120101887 | Harvey et al. | Apr 2012 | A1 |
| 20120105367 | Son et al. | May 2012 | A1 |
| 20120109764 | Martin et al. | May 2012 | A1 |
| 20120110431 | Rosenfeld et al. | May 2012 | A1 |
| 20120116669 | Lee et al. | May 2012 | A1 |
| 20120123806 | Schumann et al. | May 2012 | A1 |
| 20120123937 | Spodak | May 2012 | A1 |
| 20120127206 | Thompson et al. | May 2012 | A1 |
| 20120136780 | El-awady et al. | May 2012 | A1 |
| 20120185397 | Levovitz | Jul 2012 | A1 |
| 20120191603 | Nuzzi | Jul 2012 | A1 |
| 20120192065 | Migos et al. | Jul 2012 | A1 |
| 20120192093 | Migos et al. | Jul 2012 | A1 |
| 20120192094 | Goertz | Jul 2012 | A1 |
| 20120197740 | Grigg et al. | Aug 2012 | A1 |
| 20120198531 | Ort et al. | Aug 2012 | A1 |
| 20120209748 | Small | Aug 2012 | A1 |
| 20120215553 | Leston | Aug 2012 | A1 |
| 20120215647 | Powell et al. | Aug 2012 | A1 |
| 20120216113 | Li | Aug 2012 | A1 |
| 20120221464 | Pasquero et al. | Aug 2012 | A1 |
| 20120232968 | Calman et al. | Sep 2012 | A1 |
| 20120235921 | Laubach | Sep 2012 | A1 |
| 20120236037 | Lessing et al. | Sep 2012 | A1 |
| 20120238363 | Watanabe et al. | Sep 2012 | A1 |
| 20120245985 | Cho et al. | Sep 2012 | A1 |
| 20120245986 | Regan et al. | Sep 2012 | A1 |
| 20120271712 | Katzin et al. | Oct 2012 | A1 |
| 20120284185 | Mettler et al. | Nov 2012 | A1 |
| 20120287290 | Jain | Nov 2012 | A1 |
| 20120290449 | Mullen et al. | Nov 2012 | A1 |
| 20120290472 | Mullen et al. | Nov 2012 | A1 |
| 20120303268 | Su et al. | Nov 2012 | A1 |
| 20120310760 | Phillips et al. | Dec 2012 | A1 |
| 20120316777 | Kitta | Dec 2012 | A1 |
| 20120316933 | Pentland et al. | Dec 2012 | A1 |
| 20120317023 | Moon et al. | Dec 2012 | A1 |
| 20120322370 | Lee | Dec 2012 | A1 |
| 20120322371 | Lee | Dec 2012 | A1 |
| 20130006637 | Kanevsky et al. | Jan 2013 | A1 |
| 20130006746 | Moore | Jan 2013 | A1 |
| 20130013499 | Kalgi | Jan 2013 | A1 |
| 20130030934 | Bakshi et al. | Jan 2013 | A1 |
| 20130041654 | Walker et al. | Feb 2013 | A1 |
| 20130047034 | Salomon et al. | Feb 2013 | A1 |
| 20130050263 | Khoe et al. | Feb 2013 | A1 |
| 20130054336 | Graylin | Feb 2013 | A1 |
| 20130060678 | Oskolkov et al. | Mar 2013 | A1 |
| 20130065482 | Trickett | Mar 2013 | A1 |
| 20130073321 | Hofmann et al. | Mar 2013 | A1 |
| 20130076591 | Sirpal et al. | Mar 2013 | A1 |
| 20130080162 | Chang et al. | Mar 2013 | A1 |
| 20130080272 | Ronca et al. | Mar 2013 | A1 |
| 20130080275 | Ronca et al. | Mar 2013 | A1 |
| 20130085931 | Runyan | Apr 2013 | A1 |
| 20130085936 | Law et al. | Apr 2013 | A1 |
| 20130093715 | Marsden et al. | Apr 2013 | A1 |
| 20130103519 | Kountotsis et al. | Apr 2013 | A1 |
| 20130106603 | Weast et al. | May 2013 | A1 |
| 20130110719 | Carter et al. | May 2013 | A1 |
| 20130115932 | Williams et al. | May 2013 | A1 |
| 20130117022 | Chen et al. | May 2013 | A1 |
| 20130124319 | Hodge et al. | May 2013 | A1 |
| 20130124423 | Fisher | May 2013 | A1 |
| 20130125016 | Pallakoff et al. | May 2013 | A1 |
| 20130134212 | Chang | May 2013 | A1 |
| 20130137073 | Nacey et al. | May 2013 | A1 |
| 20130141325 | Bailey | Jun 2013 | A1 |
| 20130144706 | Qawami et al. | Jun 2013 | A1 |
| 20130151414 | Zhu et al. | Jun 2013 | A1 |
| 20130166325 | Ganapathy et al. | Jun 2013 | A1 |
| 20130166679 | Kuwahara | Jun 2013 | A1 |
| 20130179304 | Swist | Jul 2013 | A1 |
| 20130185059 | Riccardi | Jul 2013 | A1 |
| 20130189953 | Mathews | Jul 2013 | A1 |
| 20130189963 | Epp et al. | Jul 2013 | A1 |
| 20130194066 | Rahman et al. | Aug 2013 | A1 |
| 20130198112 | Bhat | Aug 2013 | A1 |
| 20130200146 | Moghadam | Aug 2013 | A1 |
| 20130212655 | Hoyos et al. | Aug 2013 | A1 |
| 20130218721 | Borhan et al. | Aug 2013 | A1 |
| 20130219285 | Iwasaki | Aug 2013 | A1 |
| 20130219303 | Eriksson et al. | Aug 2013 | A1 |
| 20130226792 | Kushevsky et al. | Aug 2013 | A1 |
| 20130227413 | Thorsander et al. | Aug 2013 | A1 |
| 20130232073 | Sheets et al. | Sep 2013 | A1 |
| 20130234924 | Janefalkar et al. | Sep 2013 | A1 |
| 20130234929 | Libin | Sep 2013 | A1 |
| 20130238455 | Laracey | Sep 2013 | A1 |
| 20130244615 | Miller | Sep 2013 | A1 |
| 20130246202 | Tobin | Sep 2013 | A1 |
| 20130253980 | Blom et al. | Sep 2013 | A1 |
| 20130282533 | Foran-owens et al. | Oct 2013 | A1 |
| 20130282577 | Milne | Oct 2013 | A1 |
| 20130295961 | Lehtiniemi et al. | Nov 2013 | A1 |
| 20130297414 | Goldfarb et al. | Nov 2013 | A1 |
| 20130304514 | Hyde et al. | Nov 2013 | A1 |
| 20130304651 | Smith | Nov 2013 | A1 |
| 20130307792 | Andres et al. | Nov 2013 | A1 |
| 20130320080 | Olson et al. | Dec 2013 | A1 |
| 20130322665 | Bennett et al. | Dec 2013 | A1 |
| 20130326563 | Mulcahy et al. | Dec 2013 | A1 |
| 20130332113 | Piemonte et al. | Dec 2013 | A1 |
| 20130332358 | Zhao | Dec 2013 | A1 |
| 20130332364 | Templeton et al. | Dec 2013 | A1 |
| 20130339436 | Gray | Dec 2013 | A1 |
| 20130344905 | Kim et al. | Dec 2013 | A1 |
| 20130345971 | Stamm et al. | Dec 2013 | A1 |
| 20130345975 | Vulcano et al. | Dec 2013 | A1 |
| 20130346273 | Stockton et al. | Dec 2013 | A1 |
| 20130346302 | Purves et al. | Dec 2013 | A1 |
| 20130346408 | Duarte et al. | Dec 2013 | A1 |
| 20130346882 | Shiplacoff et al. | Dec 2013 | A1 |
| 20140003597 | Lazaridis et al. | Jan 2014 | A1 |
| 20140006285 | Chi et al. | Jan 2014 | A1 |
| 20140006949 | Briand et al. | Jan 2014 | A1 |
| 20140009399 | Zhang | Jan 2014 | A1 |
| 20140011481 | Kho | Jan 2014 | A1 |
| 20140015546 | Frederick | Jan 2014 | A1 |
| 20140015786 | Honda | Jan 2014 | A1 |
| 20140019352 | Shrivastava | Jan 2014 | A1 |
| 20140019522 | Weng et al. | Jan 2014 | A1 |
| 20140025513 | Cooke et al. | Jan 2014 | A1 |
| 20140025520 | Mardikar et al. | Jan 2014 | A1 |
| 20140036099 | Balassanian | Feb 2014 | A1 |
| 20140052553 | Uzo | Feb 2014 | A1 |
| 20140058860 | Roh et al. | Feb 2014 | A1 |
| 20140058935 | Mijares | Feb 2014 | A1 |
| 20140058939 | Savla | Feb 2014 | A1 |
| 20140058941 | Moon et al. | Feb 2014 | A1 |
| 20140064155 | Evans | Mar 2014 | A1 |
| 20140068751 | Last | Mar 2014 | A1 |
| 20140073252 | Lee et al. | Mar 2014 | A1 |
| 20140074407 | Hernandez-Silveira et al. | Mar 2014 | A1 |
| 20140074569 | Francis et al. | Mar 2014 | A1 |
| 20140074635 | Reese et al. | Mar 2014 | A1 |
| 20140074716 | Ni | Mar 2014 | A1 |
| 20140074717 | Evans | Mar 2014 | A1 |
| 20140081854 | Sanchez et al. | Mar 2014 | A1 |
| 20140084857 | Liu et al. | Mar 2014 | A1 |
| 20140092025 | Pala et al. | Apr 2014 | A1 |
| 20140094124 | Dave et al. | Apr 2014 | A1 |
| 20140094143 | Ayotte | Apr 2014 | A1 |
| 20140095225 | Williams et al. | Apr 2014 | A1 |
| 20140099886 | Monroe | Apr 2014 | A1 |
| 20140101056 | Wendling | Apr 2014 | A1 |
| 20140109024 | Miyazaki | Apr 2014 | A1 |
| 20140122331 | Vaish et al. | May 2014 | A1 |
| 20140128035 | Sweeney | May 2014 | A1 |
| 20140129435 | Pardo et al. | May 2014 | A1 |
| 20140129441 | Blanco et al. | May 2014 | A1 |
| 20140134947 | Stouder-Studenmund | May 2014 | A1 |
| 20140138435 | Khalid | May 2014 | A1 |
| 20140139454 | Mistry et al. | May 2014 | A1 |
| 20140140587 | Ballard et al. | May 2014 | A1 |
| 20140142851 | Larmo et al. | May 2014 | A1 |
| 20140143145 | Kortina et al. | May 2014 | A1 |
| 20140143737 | Mistry et al. | May 2014 | A1 |
| 20140143784 | Mistry et al. | May 2014 | A1 |
| 20140149198 | Kim et al. | May 2014 | A1 |
| 20140155031 | Lee et al. | Jun 2014 | A1 |
| 20140156531 | Poon et al. | Jun 2014 | A1 |
| 20140160033 | Brikman et al. | Jun 2014 | A1 |
| 20140164082 | Sun et al. | Jun 2014 | A1 |
| 20140164241 | Neuwirth | Jun 2014 | A1 |
| 20140167986 | Parada et al. | Jun 2014 | A1 |
| 20140172533 | Andrews et al. | Jun 2014 | A1 |
| 20140173455 | Shimizu et al. | Jun 2014 | A1 |
| 20140176475 | Myers et al. | Jun 2014 | A1 |
| 20140180582 | Pontarelli et al. | Jun 2014 | A1 |
| 20140181747 | Son | Jun 2014 | A1 |
| 20140187163 | Fujita | Jul 2014 | A1 |
| 20140187856 | Holoien et al. | Jul 2014 | A1 |
| 20140188673 | Graham et al. | Jul 2014 | A1 |
| 20140189584 | Weng et al. | Jul 2014 | A1 |
| 20140191715 | Wechlin et al. | Jul 2014 | A1 |
| 20140197234 | Hammad | Jul 2014 | A1 |
| 20140207659 | Erez et al. | Jul 2014 | A1 |
| 20140207680 | Rephlo | Jul 2014 | A1 |
| 20140222664 | Milne | Aug 2014 | A1 |
| 20140236840 | Islam | Aug 2014 | A1 |
| 20140237389 | Ryall et al. | Aug 2014 | A1 |
| 20140244365 | Price et al. | Aug 2014 | A1 |
| 20140244493 | Kenyon et al. | Aug 2014 | A1 |
| 20140244495 | Davis et al. | Aug 2014 | A1 |
| 20140257871 | Christensen et al. | Sep 2014 | A1 |
| 20140277843 | Langlois et al. | Sep 2014 | A1 |
| 20140278028 | Nye et al. | Sep 2014 | A1 |
| 20140279442 | Luoma et al. | Sep 2014 | A1 |
| 20140279474 | Evans et al. | Sep 2014 | A1 |
| 20140279497 | Qaim-magarni et al. | Sep 2014 | A1 |
| 20140279556 | Priebatsch et al. | Sep 2014 | A1 |
| 20140280580 | Langlois et al. | Sep 2014 | A1 |
| 20140281957 | Weng et al. | Sep 2014 | A1 |
| 20140282987 | Narendra et al. | Sep 2014 | A1 |
| 20140292396 | Bruwer et al. | Oct 2014 | A1 |
| 20140297385 | Ryan | Oct 2014 | A1 |
| 20140298266 | Lapp | Oct 2014 | A1 |
| 20140304635 | Kristinsson et al. | Oct 2014 | A1 |
| 20140320387 | Eriksson et al. | Oct 2014 | A1 |
| 20140336931 | Wilkins | Nov 2014 | A1 |
| 20140337207 | Zhang et al. | Nov 2014 | A1 |
| 20140337450 | Choudhary et al. | Nov 2014 | A1 |
| 20140343843 | Yanku | Nov 2014 | A1 |
| 20140344082 | Soundararajan | Nov 2014 | A1 |
| 20140359481 | Dawson et al. | Dec 2014 | A1 |
| 20140365113 | Mcgavran et al. | Dec 2014 | A1 |
| 20140365126 | Vulcano et al. | Dec 2014 | A1 |
| 20140370807 | Lei et al. | Dec 2014 | A1 |
| 20150006207 | Jarvis et al. | Jan 2015 | A1 |
| 20150006376 | Nuthulapati et al. | Jan 2015 | A1 |
| 20150012417 | Joao et al. | Jan 2015 | A1 |
| 20150012425 | Mathew | Jan 2015 | A1 |
| 20150014141 | Rao et al. | Jan 2015 | A1 |
| 20150017956 | Jeong | Jan 2015 | A1 |
| 20150039494 | Sinton et al. | Feb 2015 | A1 |
| 20150044965 | Kamon et al. | Feb 2015 | A1 |
| 20150051846 | Masuya | Feb 2015 | A1 |
| 20150056957 | Mardikar et al. | Feb 2015 | A1 |
| 20150058146 | Gaddam et al. | Feb 2015 | A1 |
| 20150061972 | Seo et al. | Mar 2015 | A1 |
| 20150065035 | Kim et al. | Mar 2015 | A1 |
| 20150066758 | Denardis et al. | Mar 2015 | A1 |
| 20150067513 | Zambetti et al. | Mar 2015 | A1 |
| 20150067580 | Um et al. | Mar 2015 | A1 |
| 20150077362 | Seo | Mar 2015 | A1 |
| 20150089407 | Suzuki | Mar 2015 | A1 |
| 20150094031 | Liu | Apr 2015 | A1 |
| 20150095174 | Dua | Apr 2015 | A1 |
| 20150098309 | Adams et al. | Apr 2015 | A1 |
| 20150100982 | Sirpal et al. | Apr 2015 | A1 |
| 20150112752 | Wagner et al. | Apr 2015 | A1 |
| 20150121405 | Ekselius et al. | Apr 2015 | A1 |
| 20150127539 | Ye et al. | May 2015 | A1 |
| 20150130830 | Nagasaki et al. | May 2015 | A1 |
| 20150153850 | Fujii et al. | Jun 2015 | A1 |
| 20150178878 | Huang | Jun 2015 | A1 |
| 20150185896 | Gwin et al. | Jul 2015 | A1 |
| 20150186871 | Laracey | Jul 2015 | A1 |
| 20150187019 | Fernandes et al. | Jul 2015 | A1 |
| 20150217163 | Amis et al. | Aug 2015 | A1 |
| 20150220924 | Bakker | Aug 2015 | A1 |
| 20150257004 | Shanmugam et al. | Sep 2015 | A1 |
| 20150269848 | Yuen et al. | Sep 2015 | A1 |
| 20150302493 | Batstone et al. | Oct 2015 | A1 |
| 20150302510 | Godsey et al. | Oct 2015 | A1 |
| 20150326985 | Priyantha et al. | Nov 2015 | A1 |
| 20150339652 | Park et al. | Nov 2015 | A1 |
| 20150348001 | Van Os et al. | Dec 2015 | A1 |
| 20150348002 | Van Os et al. | Dec 2015 | A1 |
| 20150348009 | Brown et al. | Dec 2015 | A1 |
| 20150348014 | Van Os et al. | Dec 2015 | A1 |
| 20150348018 | Campos et al. | Dec 2015 | A1 |
| 20150348029 | Van Os et al. | Dec 2015 | A1 |
| 20150350448 | Coffman et al. | Dec 2015 | A1 |
| 20150370529 | Zambetti et al. | Dec 2015 | A1 |
| 20160005028 | Mayblum et al. | Jan 2016 | A1 |
| 20160012465 | Sharp | Jan 2016 | A1 |
| 20160019536 | Ortiz et al. | Jan 2016 | A1 |
| 20160021003 | Pan | Jan 2016 | A1 |
| 20160047666 | Fuchs | Feb 2016 | A1 |
| 20160048705 | Yang | Feb 2016 | A1 |
| 20160058336 | Blahnik et al. | Mar 2016 | A1 |
| 20160061613 | Jung et al. | Mar 2016 | A1 |
| 20160061623 | Pahwa et al. | Mar 2016 | A1 |
| 20160062487 | Foss et al. | Mar 2016 | A1 |
| 20160062572 | Yang et al. | Mar 2016 | A1 |
| 20160065505 | Iskander | Mar 2016 | A1 |
| 20160104228 | Sundaresan | Apr 2016 | A1 |
| 20160110329 | Yu et al. | Apr 2016 | A1 |
| 20160180305 | Dresser et al. | Jun 2016 | A1 |
| 20160224966 | Van Os et al. | Aug 2016 | A1 |
| 20160224973 | Van Os et al. | Aug 2016 | A1 |
| 20160232513 | Purves et al. | Aug 2016 | A1 |
| 20160238402 | Mcgavran et al. | Aug 2016 | A1 |
| 20160253665 | Van Os et al. | Sep 2016 | A1 |
| 20160259489 | Yang | Sep 2016 | A1 |
| 20160260414 | Yang | Sep 2016 | A1 |
| 20160269540 | Butcher et al. | Sep 2016 | A1 |
| 20160358133 | Van Os et al. | Dec 2016 | A1 |
| 20160358134 | Van Os et al. | Dec 2016 | A1 |
| 20160358167 | Van Os et al. | Dec 2016 | A1 |
| 20160358168 | Van Os et al. | Dec 2016 | A1 |
| 20160358180 | Van Os et al. | Dec 2016 | A1 |
| 20160358199 | Van Os et al. | Dec 2016 | A1 |
| 20160370879 | Sharma | Dec 2016 | A1 |
| 20170004507 | Henderson et al. | Jan 2017 | A1 |
| 20170011210 | Cheong et al. | Jan 2017 | A1 |
| 20170013408 | Grzywaczewski et al. | Jan 2017 | A1 |
| 20170032375 | Van Os et al. | Feb 2017 | A1 |
| 20170038856 | Missig et al. | Feb 2017 | A1 |
| 20170083188 | Yang et al. | Mar 2017 | A1 |
| 20170139517 | Morton et al. | May 2017 | A9 |
| 20170160098 | Mcgavran et al. | Jun 2017 | A1 |
| 20170161018 | Lemay et al. | Jun 2017 | A1 |
| 20170169185 | Weng | Jun 2017 | A1 |
| 20170300897 | Ferenczi et al. | Oct 2017 | A1 |
| 20170353815 | Jagannathan et al. | Dec 2017 | A1 |
| 20170354845 | Williams et al. | Dec 2017 | A1 |
| 20170357439 | Lemay et al. | Dec 2017 | A1 |
| 20170357972 | Van Os et al. | Dec 2017 | A1 |
| 20180088761 | Schobel et al. | Mar 2018 | A1 |
| 20180108243 | Scherer | Apr 2018 | A1 |
| 20180117944 | Lee | May 2018 | A1 |
| 20180158066 | Van Os et al. | Jun 2018 | A1 |
| 20180225297 | Andrew et al. | Aug 2018 | A1 |
| 20180276673 | Van Os et al. | Sep 2018 | A1 |
| 20180350144 | Rathod | Dec 2018 | A1 |
| 20180356243 | Mehta et al. | Dec 2018 | A1 |
| 20190050867 | Van Os et al. | Feb 2019 | A1 |
| 20190173996 | Butcher et al. | Jun 2019 | A1 |
| 20190213021 | Missig et al. | Jul 2019 | A1 |
| 20190232110 | Williams et al. | Aug 2019 | A1 |
| 20190232111 | Williams et al. | Aug 2019 | A1 |
| 20190297478 | Langlois et al. | Sep 2019 | A1 |
| 20190334907 | Rodden et al. | Oct 2019 | A1 |
| 20200065821 | Van Os et al. | Feb 2020 | A1 |
| 20200120170 | Amitay et al. | Apr 2020 | A1 |
| 20200159894 | Keen et al. | May 2020 | A1 |
| 20200211047 | Van Os et al. | Jul 2020 | A1 |
| 20200358897 | Dellinger et al. | Nov 2020 | A1 |
| Number | Date | Country |
|---|---|---|
| 2015100708 | Mar 2015 | AU |
| 2015100709 | Jul 2015 | AU |
| 2016100796 | Dec 2016 | AU |
| 101171604 | Apr 2008 | CN |
| 101730907 | Jun 2010 | CN |
| 102244676 | Nov 2011 | CN |
| 102282578 | Dec 2011 | CN |
| 102989159 | Mar 2013 | CN |
| 103188280 | Jul 2013 | CN |
| 103210366 | Jul 2013 | CN |
| 103413218 | Nov 2013 | CN |
| 103701605 | Apr 2014 | CN |
| 103778533 | May 2014 | CN |
| 104038256 | Sep 2014 | CN |
| 104205785 | Dec 2014 | CN |
| 104252675 | Dec 2014 | CN |
| 104272854 | Jan 2015 | CN |
| 104281430 | Jan 2015 | CN |
| 104288983 | Jan 2015 | CN |
| 104346297 | Feb 2015 | CN |
| 0836074 | Apr 1998 | EP |
| 1614992 | Jan 2006 | EP |
| 1858238 | Nov 2007 | EP |
| 2096413 | Sep 2009 | EP |
| 2150031 | Feb 2010 | EP |
| 2247087 | Nov 2010 | EP |
| 2306692 | Apr 2011 | EP |
| 2341315 | Jul 2011 | EP |
| 2428947 | Mar 2012 | EP |
| 2466260 | Jun 2012 | EP |
| 2523439 | Nov 2012 | EP |
| 2632131 | Aug 2013 | EP |
| 2654275 | Oct 2013 | EP |
| 2672377 | Dec 2013 | EP |
| 2674889 | Dec 2013 | EP |
| 2701107 | Feb 2014 | EP |
| 2720442 | Apr 2014 | EP |
| 2725537 | Apr 2014 | EP |
| 2505476 | Mar 2012 | GB |
| 0-6-284182 | Oct 1994 | JP |
| 9-292262 | Nov 1997 | JP |
| 11-39385 | Feb 1999 | JP |
| 11-73530 | Mar 1999 | JP |
| 11-183183 | Jul 1999 | JP |
| 2001-92586 | Apr 2001 | JP |
| 2001-318751 | Nov 2001 | JP |
| 2002-99854 | Apr 2002 | JP |
| 2003-16398 | Jan 2003 | JP |
| 2003-178244 | Jun 2003 | JP |
| 2003-295994 | Oct 2003 | JP |
| 2003-346059 | Dec 2003 | JP |
| 2004-252736 | Sep 2004 | JP |
| 2004-258738 | Sep 2004 | JP |
| 2005-521961 | Jul 2005 | JP |
| 2005-523505 | Aug 2005 | JP |
| 2006-31182 | Feb 2006 | JP |
| 2006-93912 | Apr 2006 | JP |
| 2006-114018 | Apr 2006 | JP |
| 2006-163960 | Jun 2006 | JP |
| 2006-197071 | Jul 2006 | JP |
| 2006-221468 | Aug 2006 | JP |
| 2006-277670 | Oct 2006 | JP |
| 2007-34637 | Feb 2007 | JP |
| 2007-507011 | Mar 2007 | JP |
| 2007-124667 | May 2007 | JP |
| 2007-226794 | Sep 2007 | JP |
| 2007-334637 | Dec 2007 | JP |
| 2008-102860 | May 2008 | JP |
| 2008-306667 | Dec 2008 | JP |
| 2009-9350 | Jan 2009 | JP |
| 2009-49878 | Mar 2009 | JP |
| 2009-99076 | May 2009 | JP |
| 2009-134521 | Jun 2009 | JP |
| 2009-136456 | Jun 2009 | JP |
| 2010-61402 | Mar 2010 | JP |
| 2010-517390 | May 2010 | JP |
| 2010-524051 | Jul 2010 | JP |
| 2011-519439 | Jul 2011 | JP |
| 2012-504273 | Feb 2012 | JP |
| 2012-508930 | Apr 2012 | JP |
| 2012-99025 | May 2012 | JP |
| 2012-114676 | Jun 2012 | JP |
| 2012-198625 | Oct 2012 | JP |
| 2012-208645 | Oct 2012 | JP |
| 2012-215981 | Nov 2012 | JP |
| 2012-529699 | Nov 2012 | JP |
| 2013-20496 | Jan 2013 | JP |
| 2013-25357 | Feb 2013 | JP |
| 2013-25409 | Feb 2013 | JP |
| 2013-34322 | Feb 2013 | JP |
| 2013-120468 | Jun 2013 | JP |
| 2013-530445 | Jul 2013 | JP |
| 2013-533532 | Aug 2013 | JP |
| 5267966 | Aug 2013 | JP |
| 2013-191234 | Sep 2013 | JP |
| 2013-206274 | Oct 2013 | JP |
| 2013-218663 | Oct 2013 | JP |
| 2013-222410 | Oct 2013 | JP |
| 2014-503891 | Feb 2014 | JP |
| 2014-41616 | Mar 2014 | JP |
| 2014-44719 | Mar 2014 | JP |
| 2014-44724 | Mar 2014 | JP |
| 2014-53692 | Mar 2014 | JP |
| 2014-75155 | Apr 2014 | JP |
| 2014-123169 | Jul 2014 | JP |
| 2014-191653 | Oct 2014 | JP |
| 10-2004-0049502 | Jun 2004 | KR |
| 10-2004-0067514 | Jul 2004 | KR |
| 10-2006-0098024 | Sep 2006 | KR |
| 10-2008-0064395 | Jul 2008 | KR |
| 10-2009-0100320 | Sep 2009 | KR |
| 10-2010-0045059 | May 2010 | KR |
| 10-2011-0056561 | May 2011 | KR |
| 10-2011-0078008 | Jul 2011 | KR |
| 10-2011-0093729 | Aug 2011 | KR |
| 10-2012-0040693 | Apr 2012 | KR |
| 10-2012-0057800 | Jun 2012 | KR |
| 10-1184865 | Sep 2012 | KR |
| 10-2013-0027326 | Mar 2013 | KR |
| 10-2013-0112339 | Oct 2013 | KR |
| 10-2013-0116905 | Oct 2013 | KR |
| 10-1330962 | Nov 2013 | KR |
| 10-2014-0018019 | Feb 2014 | KR |
| 10-2014-0026263 | Mar 2014 | KR |
| 10-2014-0027029 | Mar 2014 | KR |
| 10-2014-0055429 | May 2014 | KR |
| 10-2014-0105309 | Sep 2014 | KR |
| 201012152 | Mar 2010 | TW |
| 201137722 | Nov 2011 | TW |
| 201215086 | Apr 2012 | TW |
| 201316247 | Apr 2013 | TW |
| 201324310 | Jun 2013 | TW |
| 201409345 | Mar 2014 | TW |
| 201509168 | Apr 2015 | TW |
| M474482 | Nov 2016 | TW |
| 2003038698 | May 2003 | WO |
| 2003083793 | Oct 2003 | WO |
| 2003093765 | Nov 2003 | WO |
| 2007000012 | Jan 2007 | WO |
| 2007008321 | Jan 2007 | WO |
| 2007105937 | Sep 2007 | WO |
| 2007116521 | Oct 2007 | WO |
| 2008147457 | Dec 2008 | WO |
| 2010039337 | Apr 2010 | WO |
| 2010056484 | May 2010 | WO |
| 2010077960 | Jul 2010 | WO |
| 2011063516 | Jun 2011 | WO |
| 2012078079 | Jun 2012 | WO |
| 2012083113 | Jun 2012 | WO |
| 2012172970 | Dec 2012 | WO |
| 2013017736 | Feb 2013 | WO |
| 2013023224 | Feb 2013 | WO |
| 2013066659 | May 2013 | WO |
| 2013157330 | Oct 2013 | WO |
| 2013169875 | Nov 2013 | WO |
| 2013177548 | Nov 2013 | WO |
| 2014074407 | May 2014 | WO |
| 2014078965 | May 2014 | WO |
| 2014171734 | Oct 2014 | WO |
| 2015009581 | Jan 2015 | WO |
| 2015030912 | Mar 2015 | WO |
| 2015051361 | Apr 2015 | WO |
| Entry |
|---|
| Google, “How to create a “My Map” in Google Maps,” Dec. 8, 2008, https://www.youtube.com/watch?v=TftFnot5uXw (Year: 2008). |
| Office Action received for European Patent Application No. 16201159.7, dated Jun. 12, 2019, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-224506, dated May 14, 2019, 22 pages (11 pages of English Translation and 11 pages of Official Copy). |
| Office Action received for Japanese Patent Application No. 2018-121118, dated May 14, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2016-0152210, dated May 30, 2019, 8 pages (4 pages of English Translation and 4 pages of Official copy). |
| 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). |
| Kawai, Yasuhiro, “Resolving anxieties regarding card payment abuse by authentication—overcoming cumbersomeness by cooperation with mobile phones”, Nikkei Internet Solutions No. 78, Japan, Nikkei BP, Dec. 22, 2003, pp. 28-31(Official Copy only) {See Communication under 37 CFR § 1.98(a) (3)}. |
| Certificate of Examination received for Australian Patent Application No. 2018101855, dated Aug. 6, 2019, 02 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/866,341, dated Aug. 21, 2019, 3 pages. |
| Final Office Action received for U.S. Appl. No. 15/713,551, dated Jul. 29, 2019, 21 pages. |
| Intention to Grant received for European Patent Application No. 13795330.3, dated Aug. 9, 2019, 13 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201380080659.6, dated Jul. 29, 2019, 2 pages (1 page of English Translation and 1 page of Official Copy). |
| Office Action received for Korean Patent Application No. 10-2017-0022582, dated Jul. 31, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Supplementary European Search Report received for European Patent Application. No. 17810749.6, dated Aug. 6, 2019, 6 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). |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/294,439, dated Mar. 13, 2019, 4 pages. |
| Decision to Refuse received for European Patent Application No. 16201195.1, dated on Mar. 4, 2019, 23 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-569665, dated Feb. 22, 2019, 4 pages (1 Page of English Translation and 3 Pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2018200485, dated Feb. 20, 2019, 6 pages. |
| Office Action received for Japanese Patent Application No. 2017-562050, dated Feb. 1, 2019, 15 pages (8 pages of Englisn Translation and 7 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 Taiwanese Patent Application No. 104117508, dated Jan. 25, 2019, 24 pages (5 pages of English Translation and 19 pages of Official Copy). |
| Supplemental Notice of Allowance received for U.S. Appl. No. 14/870,726, dated Mar. 6, 2019, 6 pages. |
| Office Action received for Australian Patent Application No. 2018101855, dated Feb. 22, 2019, 4 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2017/035554, dated Dec. 20, 2018, 39 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/164,561, dated Jan. 4, 2019, 14 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/294,439, dated Jan. 8, 2019, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Jan. 3, 2019, 8 pages. |
| Office Action received for Chinese Patent Application No. 201510284715.9, dated Dec. 21, 2018, 22 pages (5 pages of English Translation and 17 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201710094150.7 dated Dec. 19, 2018, 12 Pages.( 5 pages of English translation and 7 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510284715.9, dated Jun. 19, 2019, 26 pages (8 pages of English Translation and 18 pages of Official Copy). |
| Office Action received for Taiwanese Patent Application No. 104117508, dated May 22, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/871,635, dated Jan. 15, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201610371856.9, dated Dec. 18, 2019, 6 pages (3 pages of English Translation and 3 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 Allowance received for Chinese Patent Application No. 201610371856.9, dated May 11, 2020, 2 pages (1 page of English Translation and 1 page of Official copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-0048600, dated Apr. 30, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/667,271, dated May 12, 2020, 11 pages. |
| Office Action received for Chinese Patent Application No. 201510284715.9, dated Apr. 14, 2020, 19 pages (7 pages of English Translation and 12 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15728352.4, mailed on May 12, 2020, 25 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 13795330.3, mailed on Aug. 2, 2019, 7 pages. |
| Office Action received for Australian Patent Application No. 2018202559, dated Jul. 19, 2019, 5 pages. |
| 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 Chinese Patent Application No. 201610371856.9, dated Jul. 10, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 15/866,341, dated Jul. 26, 2019, 8 pages. |
| Decision to Grant received for European Patent Application No. 13795330.3, dated Jan. 16, 2020, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-224506, dated Jan. 24, 2020, 4 pages (1 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/871,635, dated Feb. 3, 2020, 3 pages. |
| Office Action received for Chinese Patent Application No. 201510284715.9, dated Dec. 18, 2019, 24 pages (7 pages of English Translation and 17 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15727291.5, mailed on Jan. 28, 2020, 13 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16201205.8, mailed on Jan. 28, 2020, 18 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16804040.0, mailed on Jan. 24, 2020, 11 pages. |
| Brief Communication regarding Oral Proceedings received for European Patent Application No. 16201205.8, dated May 29, 2020, 29 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 16804040.0, dated May 28, 2020, 15 pages. |
| Decision to Refuse received for European Patent Application No. 15728352.4, dated May 28, 2020, 25 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 Japanese Patent Application No. 2017-562050, dated Jun. 1, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Non-Final Office Action Received for U.S. Appl. No. 14/871,635, dated Nov. 16, 2018, 36 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/866,341, dated Nov. 13, 2018, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/033,551, dated Nov. 14, 2018, 10 pages. |
| Office Action received for Korean Patent Application No. 10-2017-7034677, dated Nov. 1, 2018, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 14/503,296, dated Oct. 2, 2015, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/869,715, dated Feb. 8, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/869,715, dated May 18, 2017, 6 pages. |
| Advisory Action received for U.S. Appl. No. 14/869,877, dated on Jan. 5, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 14/870,793, dated on Apr. 13, 2017, 3 pages. |
| Advisory Action received for U.S. Appl. No. 15/137,944, dated May 11, 2017, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 14/836,754, dated May 23, 2018, 2 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/137,944, dated Jan. 11, 2018, 2 pages. |
| Corrected Notice of Allowance received for U S. Appl. No. 15/137,944, dated Jan. 19, 2018, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201570664, dated Feb. 20, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201570665, dated Apr. 26, 2017, 2 pages. |
| Decision to Grant received for Danish Patent Application No. PA201670042, dated Mar. 19, 2018, 2 pages. |
| “Does Apple Pay Change Payment?” Mac Fan, Japan, Mynavi Publishing Corporation, vol. 22, No. 11 common No. 381, Nov. 1, 2014, 11 pages (4 pages of English Translation and 7 pages of Official copy only). |
| Extended European Search Report received for European Patent Application No. 16201159.7, dated Mar. 27, 2017, 12 pages. |
| Extended European Search Report received for European Patent Application No. 16201195.1, dated Feb. 7, 2017, 13 pages. |
| Extended European Search Report received for European Patent Application No. 16201205.8, dated Jan. 5, 2017, 12 pages. |
| Extended European Search Report received for European Patent Application No. 16803996.4, dated Feb. 7, 2018, 8 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. 18154163.2, dated Mar. 2, 2018, 4 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,327, dated May 18, 2017, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/871,654, dated Nov. 16, 2017, 32 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,072, dated Mar. 2, 2017, 9 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,072, dated Sep. 1, 2015, 16 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,296, dated Jul. 2, 2015, 7 pages. |
| Final Office Action received for U.S. Appl. No. 14/719,217, dated Feb. 23, 2017, 37 pages. |
| Final Office Action received for U.S. Appl. No. 14/836,754, dated Jun. 14, 2017, 23 pages. |
| Final Office Action received for U.S. Appl. No. 14/839,897, dated Jan. 10, 2018, 16 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,715, dated Jun. 17, 2016, 35 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,715, dated Mar. 7, 2017, 41 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,715, dated Oct. 6, 2016, 37 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,831, dated Aug. 2, 2016, 14 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,831, dated May 19, 2017, 20 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. 14/871,635, dated Jan. 18, 2018, 33 pages. |
| Final Office Action received for U.S. Appl. No. 15/137,944, dated Feb. 27, 2017, 10 pages. |
| Final Office Action received for U.S. Appl. No. 14/836,754, dated Mar. 31, 2017, 24 pages. |
| Final Office Action received for U.S. Appl. No. 14/870,694, dated Apr. 7, 2017, 16 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570665, dated Feb. 28, 2017 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201570773, dated Mar. 9, 2018, 2 pages. |
| Intention to Grant received for Danish Patent Application No. PA201670042, dated Jan. 29, 2018, 2 pages. |
| Intention to Grant received for European Patent Application No. 15724160.5, dated Mar. 7, 2018, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/025188, dated Mar. 2, 2017, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/030199, dated Dec. 15, 2016, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/033326, dated Dec. 8, 2016, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/033380, dated Dec. 8, 2016, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/046892, dated Mar. 16, 2017, 14 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/047507, dated Mar. 16, 2017, 16 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2015/055165, dated Sep. 21, 2017, 15 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/015316, dated Aug. 10, 2017, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/016621, dated Aug. 24, 2017, 8 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/033751, dated Dec. 14, 2017, 11 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/034175, dated Dec. 14, 2017, 14 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/033326, dated Aug. 10, 2015, 13 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/033380, dated Aug. 10, 2015, 13 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2016/016621, dated May 9, 2016, 12 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2016/033751, dated Oct. 5, 2016, 14 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2016/034175, dated Oct. 7, 2016, 17 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2017/031748, dated Aug. 29, 2017, 14 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2016/015316, dated Mar. 8, 2016, 13 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2017/031748, dated Jun. 21, 2017, 2 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2016/033751, dated Jul. 22, 2016, 2 pages. |
| Invitation to Pay Additional Fee received for PCT Patent Application No. PCT/US2016/034175, dated Aug. 11, 2016, 3 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. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,327, dated Sep. 12, 2016, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/869,715, dated Jan. 29, 2016, 62 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,072, dated Jan. 26, 2015, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,296, dated Jan. 30, 2015, 16 pages. |
| 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/870,793, dated Apr. 19, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,364, dated Feb. 3, 2016, 16 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/869,831, dated Jan. 29, 2016, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/869,831, dated Nov. 22, 2017, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,072, dated Jun. 17, 2016, 19 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,296, dated Aug. 28, 2017, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,296, dated Oct. 5, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,381, dated May 13, 2015, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/719,217, dated Jul. 28, 2016, 28 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/836,754, dated Aug. 16, 2017, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/836,754, dated Oct. 21, 2016, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,897, dated May 18, 2017, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,903, dated Feb. 26, 2018, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,913, dated Jul. 28, 2016, 12 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/864,011, dated Jun. 10, 2016, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/869,715, dated Oct. 11, 2016, 37 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. 14/871,635, dated May 5, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/871,654, dated May 4, 2017, 23 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/137,944, dated Jul. 27, 2017, 13 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/137,944, dated Oct. 18, 2016, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/294,439, dated Jan. 26, 2018, 18 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/433,238, dated Nov. 3, 2017, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/870,694, dated Sep. 23, 2016, 13 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015266650, dated Jan. 18, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015266693, dated Jan. 19, 2018, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2016211504, dated Oct. 17, 2017, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2017201064, dated Feb. 20, 2018, 3 pages. |
| Notice of Allowance received for Chinese Patent Application No. 201520357381.9, dated Jul. 29, 2015, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Notice of Allowance received for Chinese Patent Application No. 201520358683.8, dated Mar. 10, 2016, 5 pages (3 pages of English Translation and 2 pages of Official copy). |
| Notice of Allowance received for Chinese Patent Application No. 201620480708.6, dated Apr. 20, 2017, 3 pages (2 pages of English Translation and 1 page of Official copy). |
| Notice of Allowance received for Chinese Patent Application No. 201620480846.4, dated Apr. 20, 2017, 3 pages (2 pages of English Translation and 1 page of Official copy). |
| Notice of Allowance received for Danish Patent Application No. PA201570771, dated Sep. 2, 2016, 2 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-224508, dated Jun. 20, 2017, 3 pages (Official copy only). |
| Notice of Allowance received for Korean Patent Application No. 10-2017-0022365, dated Mar. 27, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2017-0022546, dated Feb. 27, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104114953, dated Oct. 17, 2017, 3 pages (Official copy only). |
| Notice of Allowance received for Taiwanese Patent Application No. 104128700, dated Mar. 27, 2017, 3 pages (Official copy only). |
| Notice of Allowance received for Taiwanese Patent Application No. 104133756, dated Nov. 30, 2017, 5 pages (2 pages of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Taiwanese Patent Application No. 104133757, dated Jan. 18, 2017, 3 pages (Official copy only). |
| Notice of Allowance received for the U.S. Appl. No. 14/503.381, dated Dec. 16, 2015, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,072, dated Mar. 26, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,327, dated Mar. 22, 2018, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,327, dated Nov. 30, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,364, dated Jun. 16, 2016, 11 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/836,754, dated May 10, 2018, 27 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/839,913, dated Aug. 11, 2016, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/864,011, dated Apr. 28, 2016, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/864,011, dated Oct. 5, 2016, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/869,715, dated Dec. 19, 2017, 32 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/137,944, dated Dec. 21, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2017100558, dated Feb. 27, 2018, 3 pages. |
| Office Action received for European Patent Application No. 15728352.4, dated Jan. 25, 2018, 10 pages. |
| Office Action received for Japanese Patent Application No. 2016-224507, dated Dec. 1, 2017, 14 pages (7 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Australan Patent Application No. 2015100708, dated Sep. 8, 2015, 4 pages. |
| Office Action received for Australian Patent Application No. 2015100709, dated Sep. 9, 2015 (examination Report 1), 4 pages. |
| Office Action received for Australian Patent Application No. 2015100709, dated Sep. 9, 2015 (examination Report 2), 4 pages. |
| Office Action received for Australian Patent Application No. 2015286650, dated Apr. 10, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2015266693, dated Apr. 10, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2015302298, dated Apr. 4, 2018, 3 pages. |
| Office Action received for Australian Patent Application No. 2015302298, dated Sep. 14, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2015385757, dated Sep. 11, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100090, dated Apr. 13, 2016, 7 pages. |
| Office Action received for Australian Patent Application No. 2016100090, dated Oct. 7, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100367, dated May 25, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100367, dated Oct. 26, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100383, dated Jun. 9, 2016, 2 pages. |
| Office Action received for Australian Patent Application No. 2016100383, dated Nov. 11, 2016, 3 pages. |
| Office Action received for Australian Patent Application No. 2016100795, dated Aug. 12, 2016, 6 pages. |
| Office Action received for Austraiian Patent Application No. 2016100795, dated Feb. 6, 2017, 3 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. 2016102031, dated Feb. 28, 2017, 4 pages. |
| Office Action received for Australian Patent Application No. 2017100070, dated Mar. 16, 2017, 6 pages. |
| Office Action received for Australian Patent Application No. 2017100231, dated Apr. 13, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017100326, dated May 16, 2017, 3 pages. |
| Office Action received for Australian Patent Application No. 2017100328, dated Oct. 16, 2017, 6 pages. |
| Office Action received for Australian Patent Application No. 2017100558, dated Sep. 1, 2017, 5 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 Austraiian Patent Application No. 2017201064, dated Mar. 9, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2017201068, dated Jan. 17, 2018, 5 pages. |
| Office Action received for Australian Patent Application No. 2017201068, dated Mar. 10, 2017, 2 pages. |
| Office Action received for Australian Patent Application No. 2018200485, dated Mar. 15, 2018, 3 pages. |
| Office Action received for Chinese Patent Application No. 201520358683.8, dated Sep. 2, 2015, 4 pages (2 pages of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620101636.x, dated May 25, 2016, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620101636.x, dated Oct. 13, 2016, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620119869.2, dated Jun. 3, 2016, 2 pages (1 page of English Translation and 1 page of Official copy). |
| Office Action received for Chinese Patent Application No. 201620119869.2, dated Nov. 22, 2016, 2 pages (Official copy only). |
| Office Action received for Chinese Patent Application No. 201620480708.6, dated Jan. 9, 2017, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620480708.6, dated Sep. 14, 2016, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620480846.4, dated Jan. 9, 2017, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620480846.4, dated Sep. 14, 2016, 3 pages (1 page of English Translation and 2 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201620509362.8, dated Feb. 10, 2017, 2 pages (Official copy only). |
| Office Action received for Chinese Patent Application No. 201620509362.8, dated Oct. 21, 2016, 3 pages (1 page of English Translation and 2 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. PA201570709, dated Jul. 21, 2017, 4 pages. |
| Office Action received for Danish Patent Application No. PA201670709, dated Nov. 30, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201570664, dated Dec. 14, 2016, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570664, dated Jun. 3, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570665, dated Sep. 5, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570771, dated Jun. 13, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570773, dated Feb. 15, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201570773, dated Sep. 12, 2016, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670042, dated Feb. 15, 2017, 3 pages. |
| Office Action received for Danish Patent Application No. PA201670042, dated Jun. 23, 2016, 5 pages. |
| Office Action received for Danish Patent Application No. PA201670042, dated Mar. 31, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670042, dated Sep. 25, 2017, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670074, dated Jun. 28, 2016, 5 pages. |
| Office Action received for Danish Patent Application No. PA201670074, dated Mar. 16, 2017, 2 pages. |
| 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. PA201670363, dated Feb. 12, 2018, 2 pages. |
| Office Action received for Danish Patent Application No. PA201670363, dated Jun. 1, 2017, 5 pages. |
| Office Action received for Danish Patent Application No. PA201670363, dated Nov. 4, 2016, 11 pages. |
| Office Action received for Danish Patent Application No. PA201670710, dated Dec. 8, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201670710, dated Sep. 25, 2017, 6 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. PA201770292, dated Jun. 6, 2017, 7 pages. |
| Office Action received for Danish Patent Application No. PA201770292, dated Sep. 6, 2017, 4 pages. |
| Office Action received for European Patent Application No. 15727291.5, dated Jan. 15, 2018, 8 pages. |
| Office Action received for European Patent Application No. 16201195.1, dated Feb. 14, 2018, 12 pages. |
| Office Action received for European Patent Application No. 16201205.8, dated Feb. 16, 2018, 12 pages. |
| Office Action received for German Patent Application No. 202015004267.8, dated Nov. 4, 2015, 4 pages (3 pages of English Translation and 1 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-224507, dated Jun. 16, 2017, 16 pages (8 pages of English Translation and 8 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-558332, dated Dec. 8, 2017, 12 pages (6 pages of English Translation and 6 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-569665, dated Jan. 19, 2018, 10 pages (5 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2017-540616, dated Jan. 12, 2018, 24 pages (13 pages of English Translation and 11 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2017-545733, dated Feb. 13, 2018, 7 pages (3 pages of English Translation and 4 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-0022365, dated Jun. 26, 2017, 10 pages (4 pages of English Translation and 6 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-0022546, dated Jun. 21, 2017, 12 pages (5 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2018-7001854, dated Apr. 2, 2018, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104114953, dated Feb. 18, 2017, 9 pages(4 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104114953, dated Jun. 8, 2016, 11 pages (5 pages of English Translation and 6 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104117508, dated Jul. 14, 2017, 9 pages (4 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104117508, dated Jul. 20, 2016, 19 pages (8 pages of English Translation and 11 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104117508, dated Mar. 20, 2017, 22 pages (9 pages of English Translation and 13 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104128689, dated Aug. 21, 2017, 8 pages (3 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104128689, dated Nov. 14, 2016, 12 pages (5 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104128700, dated Aug. 31, 2016, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104133756, dated May 17, 2017, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Taiwanese Patent Application No. 104133757, dated Jul. 6, 2016, 22 pages (9 pages of English Translation and 13 pages of Official copy). |
| “Real Solution of Two-step-authentication Password Management for Authentication Enhancement”,Fukuda Takao, Nikkei PC, JPN, Nikkei Business Publications, Inc, No. 694. Mar. 24, 2014, 11 pages (3 pages of English Translation and 8 pages of Official copy). |
| Final Office Action received for U.S. Appl. No. 14/836,754, dated Mar. 22, 2016, 17 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/836,754, dated Nov. 17, 2015, 15 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/839,913, dated Mar. 2, 2016, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/864,011, dated Jan. 21, 2016, 10 pages. |
| Office Action received for Australian Patent Application No. 2016100155, dated May 4, 2016, 7 pages. |
| Cazlar, “[ios] Mapsgps (formerly Pebbgps) is Now Available—Now with Colour Turn-by-turn Directions!”, Online Available at <https://forums.pebble.com/t/ios-mapsgps-formerly-pebbgps-is-now-available-now-with-colour-turn-by-turn-directions/5584>, 2013, 31 pages. |
| EasyVideoGuides, “Mapquest”, available on: https://www.youtube.com/watch?v=7sDIDNM2bCI, Dec. 26, 2007, 4 pages. |
| Ehowtech, “How to Get Written Directions on a Garmin: Using a Garmin”, available online at: https://www.youtube.com/watch?v=s_EKT6qH4L, Dec. 2, 2012, 1 page. |
| Haris, “Google Maps Navigation on Android 2.0”, Sizzled Core, Online available at <http://www.sizzledcore.com/2009/10/29/google-maps-navigation-on-android-20/>, Oct. 29, 2009, 6 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. |
| Naver Blog, “How to Use Smart Wallet and Registered Card”, Online Available at <http://feena74.blog.me/140185758401>, Mar. 29, 2013, 20 pages. |
| Npasqua, “Maps: Ability to Swipe Step by Step in Turn-by-turn Mode”, 2012, Apple Support Communities, https://discussions.apple.com/thread/4424256?start=O&tstart=0, Oct. 12, 2012, 4 pages. |
| Oates, Nathan, “Pebbgps”, Available online at:—https://pebble.devpost.com/submissions/21694-pebbgps, Mar. 16, 2014, 2 pages. |
| Office Action received for Danish Patent Application No. PA201570664, dated Mar. 15, 2016, 10 pages. |
| Office Action received for Danish Patent Application No. PA201570665, dated Mar. 31, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201570771, dated Mar. 17, 2016, 8 pages. |
| Office Action received for Danish Patent Application No. PA201570773, dated Mar. 18, 2016, 9 pages. |
| Office Action received for Danish Patent Application No. PA201670074, dated Apr. 7, 2016, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/025188, dated Jun. 23, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/030199, dated Aug. 14, 2015, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/046892, dated Jan. 27, 2016, 20 pages. |
| Invitation to Pay Additional Fees and Partial Search Report received for PCT Patent Application No. PCT/US2015/046892, mailed on Nov. 4, 2015, 5 pages. |
| International Search Report and Written Opinion received for PCT Application No. PCT/US2015/047507, dated Feb. 22, 2016, 22 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047507, dated Jan. 4, 2016, 8 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/055165, dated Apr. 20, 2016, 22 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/055165, dated Jan. 18, 2016, 6 pages. |
| The Gadget Pill, “Sygic for Android Navigation with Hud”, Available online at:—https://www.youtube.com/watch?v=fGqrycRevGU, Mar. 23, 2014, 1 page. |
| Walker, Alissa, “Apple Watch's Walking Directions Buzz Your Wrist When It's Time to Turn”, available online at: http://gizmodo.com/apple-watch-will-give-you-a-buzz-when-its-time-to-turn-1632557384, Sep. 9, 2014, 2 pages. |
| Brief Communication Regarding Oral Proceedings received for European Patent Application No. 15727291.5, dated Jun. 9, 2020, 12 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 15728352.4, dated May 27, 2020, 3 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. |
| Non-Final Office Action received for U.S. Appl. No. 16/358,453, dated Mar. 19, 2020, 15 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2017-0022582, dated Feb. 27, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Decision on Appeal received for Korean Patent Application No. 10-2016-0152210, dated Jun. 23, 2020, 20 pages (2 pages of English Translation and 18 pages of Official Copy). |
| Decision to Refuse received for European Patent Application No. 15727291.5, dated Jun. 30, 2020, 21 pages. |
| Decision to Refuse received for European Patent Application No. 16201205.8, dated Jun. 30, 2020, 29 pages. |
| European Search Report received for European Patent Application No. 20180033.1, dated Jul. 6, 2020, 4 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/869,877, dated Jun. 26, 2020, 14 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 15727291.5, mailed on Jun. 29, 2020, 8 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 16201205.8, mailed on Jun. 29, 2020, 6 pages. |
| 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). |
| Certification of Examination received for Australian Patent Application No. 2018100158 dated Oct. 23, 2018, 2 pages. |
| Final Office Action received for U.S. Appl. No. 13/076,411 dated Nov. 8, 2018, 10 pages. |
| Notice of Allowance received for Taiwanese Patent Application No. 104128689 dated Aug. 28, 2018, 5 pages (2 pages of English Translation and 3 pages of Official copy). |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/667,271, dated Apr. 8, 2020, 3 pages. |
| Decision to Refuse Application received for the European Patent Application No. 16803996.4, dated Apr. 3, 2020, 25 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/267,817, dated Apr. 15, 2020, 25 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7005262, dated Mar. 25, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for Korean Patent Application No. 10-2020-7004737, dated Mar. 31, 2020, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 16/164,561, dated Apr. 8, 2020, 5 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 15/866,341, dated Aug. 26, 2019, 3 pages. |
| Final Office Action received for U.S. Appl. No. 16/164,561, dated Sep. 5, 2019, 12 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,296, dated Aug. 28, 2019, 12 pages. |
| Office Action received for Chinese Patent Application No. 201710094150.7, dated Jul. 31, 2019, 6 pages. (2 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810094316.X, dated Aug. 5, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Office Action received for European Patent Application No. 17810749.6, dated Aug. 20, 2019, 9 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2016-7014051, dated Nov. 27, 2018, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2016270323, dated Nov. 26, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016270775, dated Nov. 26, 2018, 5 pages. |
| Office Action received for Chinese Patent Application No. 201380080659.6, dated Oct. 26, 2018, 11 pages (3 pages of English Translation and 8 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201810094316.X, dated Oct. 29, 2018, 12 pages (5 pages of English Translation and 7 pages of Official Copy). |
| Office Action received for European Patent Application No. 16803996.4, dated Nov. 29, 2018, 12 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 18154163.2, mailed on Nov. 29, 2018, 9 pages. |
| Advisory Action received for U.S. Appl. No. 13/076,411, dated Mar. 10, 2014, 6 pages. |
| Examiner's Answer to Appeal Brief received for U.S. Appl. No. 14/870,793, mailed on Apr. 16, 2018, 15 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,296, dated Jun. 4, 2018, 8 pages. |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Apr. 26, 2018, 18 pages. |
| International Preliminary Report on Patentability Received for PCT Patent Application No. PCT/US2016/044990, dated Feb. 15, 2018, 8 pages. |
| International Search Report and Written Opinion for PCT Patent Application No. PCT/US2016/044990, dated Nov. 23, 2016, 11 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2017/035554, dated Sep. 22, 2017, 42 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2016/044990, dated Sep. 29, 2016, 3 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2017/035554, dated Jul. 20, 2017, 2 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. 13/076,411, dated Mar. 21, 2018, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/033,551, dated May 24, 2018, 26 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/057,835, dated Jan. 3, 2018, 8 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2013404001, dated Nov. 21, 2017, 3 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-527367, dated Jul. 30, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for Japanese Patent Application No. 2018-008937, dated Jul. 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-2018-7001854, dated Aug. 21, 2018, 4 pages (1 page of English Translation and 3 pages of Official copy). |
| Notice of Allowance received for U.S. Appl. No. 13/076,414, dated May 4, 2016, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/503,072, dated Jun. 4, 2018, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/871,654, dated May 22, 2018, 22 pages. |
| Office Action received for European Patent Application No. 13795330.3, dated Oct. 9, 2017, 8 pages. |
| Office Action received for Australian Patent Application No. 2013404001, dated Aug. 3, 2017, 5 pages. |
| Office Action received for Australian Patent Application No. 2013404001, dated Nov. 26, 2016, 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. 2018100158, dated Apr. 23, 2018, 5 pages. |
| Office Action received for Chinese Patent Application No. 201380080659.6, dated Apr. 4, 2018, 15 pages (5 pages of English Translation and 10 pages of Official copy). |
| Office Action received for Chinese Patent Application No. 201510284896.5, dated Jun. 28, 2018, 15 pages (4 pages of English Translation and 11 pages of Official copy). |
| Office Action received for Danish Patent Application No. PA201770423, dated Jun. 12, 2018, 7 pages. |
| Office Action received for European Patent Application No. 18154163.2, dated Apr. 11, 2018, 6 pages. |
| Office Action received for Japanese Patent Application No. 2016-527367, dated Feb. 26, 2018, 15 pages (8 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-527367, dated Jul. 7, 2017, 16 pages (8 pages of English Translation and 8 pages of Official copy). |
| Office Action received for Japanese Patent Application No. 2016-558332, dated Jul. 27, 2018, 9 pages (4 pages of English Translation and 5 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2016-0152210, dated May 14, 2018, 13 pages (6 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2016-7014051, dated Apr. 30, 2018, 14 pages (7 pages of English Translation and 7 pages of Official copy). |
| Office Action received for Korean Patent Application No. 1020167014051, dated Jun. 20, 2017, 16 pages (8 pages of English Translation and 8 pages of Official copy). |
| Search Report and Opinion received for Danish Patent Application No. PA201770423, dated Oct. 4, 2017, 10 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16201195.1, mailed on Sep. 4, 2018, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,407, dated Dec. 5, 2013, 16 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,407, dated May 20, 2014, 9 pages. |
| Final Office Action received in U.S. Appl. No. 13/076,411, dated Nov. 15, 2013, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,411, dated Jun. 13, 2013, 9 pages. |
| Final Office Action received for U.S. Appl. No. 13/076,414, dated Feb. 19, 2014, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/076,414, dated Aug. 21, 2013, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/076,414, dated Aug. 26, 2015, 7 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/294,439, dated Sep. 10, 2018, 9 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. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2013/067634, dated May 12, 2016, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2013/067634, dated Apr. 16, 2014, 11 pages. |
| Razykdreviews, “In Depth Review of Apple Watch Activity and Workout App”, Online Available at: URL: https://www.youtube.com/watch?v=GkKI3qIK0ow, May 11, 2015, 1 page. |
| Rizknows, “Garmin Connect Mobile App—Review #2”, Online Available at: https://www.youtube.com/watch?v=7my3wMpeRbE, Oct. 22, 2015, 1 page. |
| Non-Final Office Action received for U.S. Appl. No. 16/667,271, dated Dec. 13, 2019, 8 pages. |
| Office Action received for Australian Patent Application No. 2016270775, dated Nov. 26, 2019, 3 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). |
| Office Action received for Japanese Patent Application No. 2018-121118, dated Nov. 18, 2019, 10 pages (5 pages of English Translation and 5 pages of Official Copy). |
| Decision to Refuse received for European Patent Application No. 18154163.2, dated May 17, 2019, 22 pages. |
| Final Office Action Received for U.S. Appl. No. 14/871,635, dated May 3, 2019, 32 pages. |
| Final Office Action received for U.S. Appl. No. 15/866,341, dated May 14, 2019, 10 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 18154163.2, mailed on May 17, 2019, 7 pages. |
| Office Action received for European Patent Application No. 16804040.0, dated May 13, 2019, 12 pages. |
| Office Action received for Korean Patent Application No. 10-2019-7005262, dated May 3, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Preliminary Opinion before oral proceedings received for European Patent Application No. 18154163.2, mailed on Apr. 16, 2019, 12 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-558332, dated Jan. 11, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2018202559, dated Jan. 16, 2019, 6 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. 201610371856.9, dated Dec. 19, 2018, 12 pages (5 pages of English Translation and 7 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). |
| Decision to Refuse Application received for the European Patent Application No. 16803996.4, dated Apr. 14, 2020, 28 pages. |
| Office Action received for Australian Patent Application No. 2020200685, dated Apr. 20, 2020, 3 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). |
| Final Office Action received for U.S. Appl. No. 15/057,835, dated Sep. 21, 2018, 9 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/503,296, dated Sep. 18, 2018, 20 pages. |
| Office Action received for Japanese Patent Application No. 2016-569665, dated Aug. 20, 2018, 9 pages (4 pages of English Translation and 5 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 14/869,877, dated Jun. 11, 2019, 35 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2017-7034677, dated May 27, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2016270323, dated May 29, 2019, 4 pages. |
| Office Action received for Australian Patent Application No. 2016270775, dated May 29, 2019, 3 pages. |
| Office Action received for Chinese Patent Application No. 201810094316.X, dated Apr. 28, 2019, 9 pages (3 pages of English Translation and 6 pages of Official Copy). |
| Notice of Allowance received for Chinese Patent Application No. 201710093861.2, dated Sep. 24, 2019, 4 pages (1 page of English Translation and 3 pages of Official Copy). |
| 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). |
| Notice of Allowance received for Taiwanese Patent Application No. 104117508, dates Sep. 18, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510284896.5, dated Sep. 3, 2019, 9 pages (2 pages of English Translation and 7 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). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 16803996.4, dated Oct. 2, 2019, 16 pages. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 15/713,551, dated Nov. 5, 2019, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2018202559, dated Oct. 21, 2019, 3 pages. |
| Office Action received for Indian Patent Application No. 201617039493, dated Oct. 21, 2019, 6 pages. |
| Office Action received for Japanese Patent Application No. 2017-562050, dated Sep. 30, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Australian Patent Application No. 2020200685, dated Feb. 10, 2020, 4 pages. |
| Result of Consultation received for European Patent Application No. 16803996.4, dated Feb. 17, 2020, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/713,551 dated Mar. 21, 2019, 18 pages. |
| Notice of Allowance received for Japanese Patent Application No. 2016-224507, dated Mar. 26, 2019, 3 pages (1 page of English Translation and 2 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 13/076,411, dated Apr. 8, 2019, 13 pages. |
| Office Action received for Australian Patent Application No. 2018200485, dated Mar. 15, 2019, 4 pages. |
| Office Action received for Chinese Patent Application No. 201380080659.6, dated Mar. 4, 2019, 9 pages (5 pages of English Translation and 4 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201510284896.5, dated Mar. 6, 2019, 13 pages (4 pages of English Translation and 9 pages of Official Copy). |
| Office Action received for Chinese Patent Application No. 201710093861.2, dated Mar. 5, 2019, 6 pages (3 pages of English Translation and 3 pages of Official Copy). |
| Office Action received for Danish Patent Application No. PA201770423, dated Mar. 29, 2019, 6 pages. |
| Supplemental Notice of Allowance received for U.S. Appl. No. 15/616,480, dated Mar. 28, 2019, 2 pages. |
| Final Office Action received for U.S. Appl. No. 14/503,296, dated Apr. 24, 2019, 5 pages. |
| Office Action received for Australian Patent Application No. 2018202559, dated Apr. 8, 2019, 4 pages. |
| Partial Supplementary European Search Report received for European Patent Application No. 17810749.6, dated Apr. 25, 2019, 8 pages. |
| Office Action received for Korean Patent Application No. 10-2016-0152210, dated Jan. 29, 2019, 7 pages (3 pages of English Translation and 4 pages of Official Copy). |
| Advisory Action received for U.S. Appl. No. 16/164,561, dated Nov. 14, 2019, 2 pages. |
| Notice of Allowance received for Korean Patent Application No. 10-2019-7025322, dated Nov. 20, 2019, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Notice of Allowance received for U.S. Appl. No. 14/871,635, dated Nov. 14, 2019, 14 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 15728352.4, mailed on Nov. 18, 2019, 15 pages. |
| Smart Card Alliance, “Security of Proximity Mobile Payments”, Online Available at: https://www.securetechalliance.org/resources/pdf/Security_of_Proximity_Mobile_Payments.pdf, May 2009, pp. 1-39. |
| Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Oct. 5, 2018, 19 pages. |
| Office Action received for Chinese Patent Application No. 201710093861.2, dated Sep. 14, 2018, 15 pages (6 pages of English Translation and 9 pages of Official copy). |
| Office Action received for Korean Patent Application No. 10-2017-0022582, dated Sep. 19, 2018, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Summons to Attend Oral Proceedings received for European Patent Application No. 13795330.3, dated Oct. 19, 2018, 13 pages. |
| Office Action received for Korean Patent Application No. 10-2020-0097418, dated Aug. 28, 2020, 6 pages (2 pages of English Translation and 4 pages of Official Copy). |
| Non-Final Office Action received for U.S. Appl. No. 15/992,722, dated Aug. 6, 2020, 7 pages. |
| Office Action received for Australian Patent Application No. 2020200685, 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. |
| Applicant Initiated Interview Summary received for U.S. Appl. No. 16/358,453, dated Jul. 28, 2020, 5 pages. |
| Applicant-Initiated Interview Summary received for U.S. Appl. No. 16/267,817, dated Jul. 14, 2020, 5 pages. |
| Examiner's Pre-Review Report received for Japanese Patent Application No. 2018-121118, dated Jun. 2, 2020, 4 pages (2 pages of English Translation and 2 pages of Official Copy). |
| Office Action received for European Patent Application No. 20180033.1, dated Jul. 17, 2020, 7 pages. |
| Office Action received for Japanese Patent Application No. 2020-028315, dated Jul. 6, 2020, 18 pages (10 pages of English Translation and 8 pages of Official Copy). |
| Final Office Action received for U.S. Appl. No. 16/267,817, dated Aug. 24, 2020, 23 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/713,551, dated Aug. 27, 2020, 12 pages. |
| Office Action received for Australian Patent Application No. 2017277971, dated Aug. 12, 2020, 3 pages. |
| Decision on Appeal received for U.S. Appl. No. 14/870,793, dated Nov. 3, 2020, 11 pages. |
| Decision to Refuse received for European Patent Application No. 16804040.0, dated Nov. 4, 2020, 18 pages. |
| Final Office Action received for U.S. Appl. No. 16/358,453, dated Nov. 16, 2020, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2020/031528, dated Sep. 23, 2020, 18 pages. |
| Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2020/031528, dated Jul. 30, 2020, 11 pages. |
| Minutes of the Oral Proceedings received for European Patent Application No. 16804040.0, dated Nov. 2, 2020, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/533,540, dated Oct. 23, 2020, 34 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2020200685, dated Oct. 29, 2020, 3 pages. |
| Record of Oral Hearing received for U.S. Appl. No. 14/870,793, dated Nov. 3, 2020, 24 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. |
| Bao et al., “Location-based and Preference-Aware Recommendation Using Sparse Geo-Social Networking Data”, ACM SIGSPATIAL GIS Redondo Beach, CA, Online available at : https://www.microsoft.com/en-us/research/wp-content/uploads/2016/02/LocationRecommendation.pdf, Nov. 6-9, 2012, 10 pages. |
| Lu Haiyun, “Recommendations Based on Purchase Patterns”, International Journal of. Machine Learning and Computing, vol. 4, No. 6, Online available at: http://www.ijmlc.org/papers/462-0015.pdf, Dec. 2014, pp. 501-504. |
| Non-Final Office Action received for U.S. Appl. No. 16/990,974, dated Oct. 15, 2020, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/992,722, dated Oct. 19, 2020, 5 pages. |
| Office Action received for Australian Patent Application No. 2019271921, dated Oct. 6, 2020, 5 pages. |
| Office Action received for Korean Patent Application No. 10-2020-7018655, dated Oct. 13, 2020, 5 pages (2 pages of English Translation and 3 pages of Official Copy). |
| Number | Date | Country | |
|---|---|---|---|
| 20190003849 A1 | Jan 2019 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62129849 | Mar 2015 | US | |
| 62044944 | Sep 2014 | US | |
| 62044993 | Sep 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14836754 | Aug 2015 | US |
| Child | 16102146 | US |
