User interface for phone call routing among devices
The invention is directed to a first electronic device. The first electronic device receives a phone call that was routed to the first electronic device by a call-routing service. While receiving the call, the first electronic device receives a request to route the phone call to a second electronic device. In response to receiving the request to route the phone call to the second electronic device, in accordance with a determination that a first routing criteria have been met, the first electronic device sends a request to the call-routing service to route the phone call to the second electronic device instead of routing the phone call to the first electronic device. In accordance with a determination that a second routing criteria have been met, the first electronic device causes call data associated with the call to be routed through the first electronic device to the second electronic device.
Latest Apple Patents:
This application claims priority to U.S. Provisional Application Ser. No. 62/005,990, filed May 30, 2014, entitled “User Interface for Phone Call Routing Among Devices,” which is incorporated herein by reference in its entirety.
FIELD OF THE DISCLOSUREThe present disclosure relates generally to user interfaces for routing phone calls among electronic devices.
BACKGROUND OF THE DISCLOSUREElectronic devices that provide communications capabilities (e.g., voice, text, and/or video communications) come in various form factors (e.g., phone, tablet, laptop, desktop, etc.). However, transferring a call from a phone to a tablet, for example, may be impossible in many cases.
SUMMARY OF THE DISCLOSUREMany electronic devices provide communications capabilities (e.g., voice, text, and/or video communications). There is a need to provide a fast, efficient, and intuitive way for users to route phone calls (and other communications) among electronic devices. In particular, a call-routing service may or may not be able to route a phone call directly to a second electronic device in response to a request from the first electronic device (e.g., routing-service routing). Instead, the first electronic device optionally routes the phone call through the first electronic device to the second electronic device (e.g., through-device routing). The embodiments described herein provide an intuitive way for a first electronic device to cause a phone call to be routed from the first electronic device to a second electronic device using routing-service routing if it is available, and falling back on through-device routing if routing-service routing is unavailable. Further, embodiments described herein provide an intuitive way for a first electronic device to pull a phone call from the second electronic device to the first electronic device and/or to push a phone call from the first electronic device to the second electronic device.
In accordance with some embodiments, a non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a first electronic device, cause the first electronic device to perform a method. The method includes: generating for presentation on a display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device; while the user interface is presented on the display, receiving a request to route the phone call to the first electronic device; in response to the request, requesting call data associated with the phone call; and after requesting the call data, presenting the phone call at the first electronic device.
In accordance with some embodiments, a method is performed at a first electronic device with one or more processors and memory. The method includes: generating for presentation on a display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device; while the user interface is presented on the display, receiving a request to route the phone call to the first electronic device; in response to the request, requesting call data associated with the phone call; and after requesting the call data, presenting the phone call at the first electronic device.
In accordance with some embodiments, a first electronic device comprises a memory; a display; and a processor coupled to the display and the memory. The processor is configured to perform a method comprising: generating for presentation on the display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device; while the user interface is presented on the display, receiving a request to route the phone call to the first electronic device; in response to the request, requesting call data associated with the phone call; and after requesting the call data, presenting the phone call at the first electronic device.
For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
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.
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.
Exemplary DevicesEmbodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touchpads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touchpad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick.
The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user's sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in
Memory 102 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 108 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212,
I/O subsystem 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch-sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164.
Device 100 optionally also includes one or more contact intensity sensors 165.
Device 100 may also include one or more proximity sensors 166.
Device 100 optionally also includes one or more tactile output generators 167.
Device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments, memory 102 (
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with, the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including, without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing; to camera 143 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
-
- Contacts module 137 (sometimes called an address book or contact list);
- Telephone module 138;
- Video conferencing module 139;
- E-mail client module 140;
- Instant messaging (IM) module 141;
- Workout support module 142;
- Camera module 143 for still and/or video images;
- Image management module 144;
- Video player module;
- Music player module;
- Browser module 147;
- Calendar module 148;
- Widget modules 149, which may include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
- Widget creator module 150 for making user-created widgets 149-6;
- Search module 151;
- Video and music player module 152, which merges video player module and music player module;
- Notes module 153;
- Map module 154; and/or
- Online video module 155.
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact/motion module 130, graphics module 132, text input module 134, contacts module 137, and telephone module 138, video conference module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact/motion module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact/motion module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact/motion module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety.
Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 152,
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripherals interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application's user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177, or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 include one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170 and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer's event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, subscriber identity module (SIM) card slot 210, headset jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
Each of the above-identified elements in
Attention is now directed towards embodiments of user interfaces that may be implemented on, for example, portable multifunction device 100.
-
- Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
- Time 404;
- Bluetooth indicator 405;
- Battery status indicator 406;
- Tray 408 with icons for frequently used applications, such as:
- Icon 416 for telephone module 138, labeled “Phone,” which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
- Icon 418 for e-mail client module 140, labeled “Mail,” which optionally includes an indicator 410 of the number of unread e-mails;
- Icon 420 for browser module 147, labeled “Browser;” and
- Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
- Icons for other applications, such as:
- Icon 424 for IM module 141, labeled “Messages;”
- Icon 426 for calendar module 148, labeled “Calendar;”
- Icon 428 for image management module 144, labeled “Photos;”
- Icon 430 for camera module 143, labeled “Camera;”
- Icon 432 for online video module 155, labeled “Online Video;”
- Icon 434 for stocks widget 149-2, labeled “Stocks;”
- Icon 436 for map module 154, labeled “Maps;”
- Icon 438 for weather widget 149-1, labeled “Weather;”
- Icon 440 for alarm clock widget 149-4, labeled “Clock;”
- Icon 442 for workout support module 142, labeled “Workout Support;”
- Icon 444 for notes module 153, labeled “Notes;” and
- Icon 446 for a settings application or module, labeled “Settings,” which provides access to settings for device 100 and its various applications 136.
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.
The first and second electronic devices 500 and 502 are optionally in communication with a call-routing service 504. A call-routing service 504 is a local exchange carrier, a mobile network operator (MNO), a voice over Internet Protocol (VoIP) provider, other phone carrier, etc. The call-routing service 504 sends call data associated with a phone call to one or both of the first electronic device 500 (as illustrated in
In some embodiments, the first electronic device 500 optionally causes the phone call to be routed to the second electronic device 502, either by routing-service routing or by through-device routing (illustrated in
In some embodiments, the first electronic device 500 and the second electronic device 502 are optionally in communication with a device coordination server 506, as illustrated in
User Interfaces and Associated Processes
Through-Device Routing and Routing-Service Routing
Many electronic devices provide communications capabilities (e.g., voice, text, and/or video communications). There is a need to provide a fast, efficient, and intuitive way for users to route phone calls (and other communications) among electronic devices. In particular, a call-routing service may or may not provide routing-service routing. The embodiments described below provide an intuitive way for a first electronic device to cause a phone call to be routed from the first electronic device to a second electronic device using routing-service routing if it is available, and falling back on through-device routing if routing-service routing is unavailable. In some embodiments, the first electronic device causes the phone call to be routed from the first electronic device to the second electronic device using through-device routing if available, and falling back on routing-service routing if routing-service routing is unavailable. In some embodiments, other criteria are used to determine the particular routing scheme to use.
In some embodiments, the first electronic device 500 optionally receives a request to route the phone call to the second electronic device 502, and the first electronic device causes the phone call to be routed to the second electronic device, as illustrated in
In some embodiments, after the phone call has been routed to the second electronic device 502, a user interface object 634 is optionally displayed in the user interface of the first electronic device 500, as illustrated in
In some embodiments, the first electronic device 500 optionally receives input corresponding to selection of the user interface object 634, and in response to the input, the phone call is pulled back to the first electronic device 500, as illustrated in
As described below, the method 700 provides ways of causing a phone call to be routed from a first electronic device to a second electronic device, using routing-service routing if available, or through-device routing as a fallback. The method reduces the cognitive burden on a user when interacting with a user interface on the device by providing an intuitive user interface for routing a phone call among electronic devices, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interfaces conserves power and increases the time between battery charges.
In some embodiments, a first electronic device 500 with one or more processors and memory receives (702), at the first electronic device, a phone call that was routed to the first electronic device by a call-routing service (e.g., a local exchange carrier associated with the phone call, a mobile network operator (MNO) associated with the phone call, a voice over Internet Protocol (VoIP) provider associated with the phone call, other phone carrier, etc.). In some embodiments, the phone call is optionally an audio-only call. In some embodiments, the phone call is optionally a video call. The phone call is optionally presented at the first electronic device, as illustrated in
While receiving the phone call, the first electronic device receives (706) a request to route the phone call to a second electronic device 502. For example, the first electronic device optionally receives user input on the first electronic device requesting to route the phone call to the second electronic device (push request received at the first electronic device), the first electronic device receives the request from a different electronic device such as the second electronic device (pull request received from the second electronic device), etc. In some embodiments, both devices are associated with a same user account and/or are on a same local network. In some embodiments, the request to route the phone call to the second electronic device is optionally received (708) from the second electronic device (and the request is sent in response to input on the second electronic device answering the phone call). In some embodiments, the request to route the phone call to the second electronic device optionally corresponds (710) to user input received at the first electronic device.
In response to receiving the request to route the phone call to the second electronic device (712), in accordance with a determination that a first routing criteria have been met (714), the first electronic device sends (720) a request to the call-routing service to route the phone call to the second electronic device instead of routing the phone call to the first electronic device (e.g., routing-service routing). In some embodiments, the first routing criteria optionally include (718) a criterion that is met when the call-routing service has enabled a carrier routing protocol (e.g., routing-service routing: if the carrier has can directly route the phone call to the second electronic device without going through the first electronic device). In some embodiments, the carrier routing protocol is optionally determined based on information stored on the first electronic device. In some embodiments, the carrier routing protocol is optionally determined based on communication with a remote device, such as a carrier server that sends information associated with the carrier routing protocol to the first electronic device.
Further in response to receiving the request to route the phone call to the second electronic device (712), in accordance with a determination that a second routing criteria have been met (716), the first electronic device causes (730) call data associated with the phone call to be routed through the first electronic device to the second electronic device. For example, the first electronic device optionally receives audio data associated with the phone call at the first electronic device and sends the received audio data to the second electronic device, etc. In some embodiments, the second routing criteria optionally include (728) a criterion that is met when the call-routing service has not enabled the carrier routing protocol.
In some embodiments, after the phone call has been routed to the second electronic device, the phone call is optionally presented at the second electronic device as illustrated in
In some embodiments, before receiving the request to route the phone call, the first electronic device optionally opens (704) a connection associated with the phone call. Further in accordance with the determination that the first routing criteria (e.g., routing-service routing) have been met (714), the first electronic device closes (722) the connection associated with the phone call. In some embodiments, the connection associated with the phone call is closed in response to receiving confirmation that the second electronic device has opened a connection associated with the phone call (724).
In some embodiments, in accordance with the determination that the second routing criteria (e.g., through-device routing) have been met (716), the first electronic device maintains (736) the connection associated with the phone call for the duration of the phone call. In some embodiments, the first electronic device optionally receives (742) a hang-up command from the second electronic device. For example, in
In some embodiments, causing call data associated with the phone call to be routed through the first electronic device to the second electronic device optionally includes receiving (732) the call data and sending different data to the second electronic device (e.g., audio data extracted from the call data, audio data and metadata, etc.).
In some embodiments, causing call data associated with the phone call to be routed through the first electronic device to the second electronic device optionally includes receiving (734) the call data and sending the call data to the second electronic device without extracting audio content from the call data (e.g., the call data is relayed, unchanged to the second electronic device).
In some embodiments, in accordance with the determination that the second routing criteria (e.g., through-device routing) have been met, the first electronic device displays (738) a user interface object indicating the phone call is routed through the first electronic device (e.g., on a display such as displays 112, 340, and/or 450 in
In some embodiments, in accordance with the determination that the first routing criteria (e.g., routing-service routing) have been met, the first electronic device optionally displays (726) a user interface object indicating the phone call has been routed to the second electronic device (e.g., on a display such as displays 112, 340, and/or 450 in
In some embodiments, there are optionally differences in functionality depending on the routing scheme. For example, if through-device routing is used, the phone call optionally ends on the second electronic device if the first electronic device is turned off or loses signal during the phone call. If routing-service routing is used, the phone call optionally continues on the second electronic device if the first electronic device is turned off or loses signal during the phone call. For another example, the first electronic device is optionally able to make a second phone call after routing the first phone call using routing-service routing. If through-device routing is used, the first electronic device is optionally unable to make a second phone call until the first phone call ends.
The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described above with respect to
The operations described above with reference to
It should be understood that the particular order in which the operations in
Pull to First Device from Second Device
Many electronic devices provide communications capabilities (e.g., voice, text, and/or video communications). There is a need to provide a fast, efficient, and intuitive way for users to route phone calls (and other communications) among electronic devices. In particular, the embodiments below provide an intuitive way for a first electronic device to pull a phone call from a second electronic device to a first electronic device.
In some embodiments, input is optionally received on any of the user interface objects 802, 804, 806, and 808 to cause the phone call to be routed to the first electronic device 500 (e.g., the phone call may be pulled to the first electronic device). In response to the input, the phone call is optionally presented on the first electronic device 500, as illustrated in
As illustrated in
As described below, the method 900 provides ways of pulling a phone call from a second electronic device to a first electronic device. The method reduces the cognitive burden on a user when interacting with a user interface on the device by providing an intuitive user interface for routing a phone call among electronic devices, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interfaces conserves power and increases the time between battery charges.
In some embodiments, a first electronic device 500 with one or more processors and memory generates (906) for presentation on a display (e.g., a remote display device or a display that is integrated into the electronic device, such as displays 112, 340, and/or 450 in
While the user interface is presented on the display, the first electronic device receives (922) a request to route the phone call to the first electronic device (e.g., receiving user input on the first electronic device requesting to route the phone call to the first electronic device, receiving the request from a different electronic device, etc.). For example, the first electronic device optionally receives input selecting any of user interface objects 802 (status bar), 804 (on a lock screen), 806 (notification), or 808 (in a phone call user interface) illustrated in
In response to the request, the first electronic device requests (924) call data (e.g., from a carrier associated with the phone call, from the second electronic device, etc.) associated with the phone call.
After requesting the call data, the first electronic device presents (932) the phone call at the first electronic device (e.g., in response to requesting the call data, the call is routed to the first electronic device and the first electronic device connects the phone call). For example,
In some embodiments, after requesting the call data, the first electronic device optionally instructs (930) the second electronic device to stop playing audio associated with the phone call (e.g., through a speaker or headset in communication with the second electronic device, such as speaker 111 illustrated in
In some embodiments, while the phone call is presented at the first electronic device (934), the phone call is optionally not presented (936) at the second electronic device (e.g., the first device and the second device are not devices that share a common phone line).
In some embodiments, requesting the call data optionally includes causing (926) the call data to be routed through the second electronic device to the first electronic device (e.g., using through-device routing, as described above). In some embodiments, requesting the call data optionally includes sending (928) a request to a routing service to reroute the phone call from the second electronic device to the first electronic device (e.g., using routing-service routing, as described above).
In some embodiments, the first electronic device optionally receives (902), from the second electronic device, information that the phone call has been routed to the second electronic device, and the user interface is generated based on the information (908). In some embodiments, the information that the phone call has been routed to the second electronic device is received prior to displaying user interface object indicating that a phone call has been routed to a second electronic device on the display. For example, user interface objects 802, 804, 806, and 808 in
In some embodiments, the first electronic device optionally receives (904), from a device coordination server 506 (e.g., a server at a carrier, phone service provider, internet service provider, other service provider, etc. that optionally stores information regarding first and second electronic devices and optionally sends the information to other electronic devices) that is in communication with the first electronic device and the second electronic device, information that the phone call has been routed to the second electronic device, and the user interface is generated based on the information (904). For example, user interface objects 802, 804, 806, and 808 in
In some embodiments, while the phone call is presented at the first electronic device (934), the first electronic device optionally generates (938) for presentation on the display an affordance for transferring the phone call back to the second electronic device. For example,
In some embodiments, while the phone call is presented at the first electronic device (934), the first electronic device optionally generates (940) for presentation on the display an identifier of the second electronic device (e.g., text indicating that the call is routed “from your iPhone”, etc.). For example,
In some embodiments, the user interface object is optionally generated (910) in accordance with a determination that the first and second electronic devices are both associated with the same user identity. In some embodiments, the user interface object is optionally generated (912) in accordance with a determination that the first and second electronic devices are connected to the same network (e.g., the same WiFi, the same subnet, etc.). In some embodiments, the user interface object is optionally generated (914) in accordance with a determination that the second electronic device is Bluetooth discoverable from the first electronic device. For example, the first electronic device is optionally only able to pull phone calls from devices that are associated with the same user identity, on the same network, and/or Bluetooth discoverable from the first electronic device, among other possibilities (e.g., this allows routing only to devices that are compatible with the routing scheme and provides an element of security to the pushing/pulling/etc.).
The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described above with respect to
The operations described above with reference to
It should be understood that the particular order in which the operations in
Push from First Device to Second Device
Many electronic devices provide communications capabilities (e.g., voice, text, and/or video communications). There is a need to provide a fast, efficient, and intuitive way for users to route phone calls (and other communications) among electronic devices. In particular, the embodiments below provide an intuitive way for a first electronic device to push a phone call from a first electronic device to a second electronic device.
In some embodiments, input is optionally received on the affordance 1002 to cause a phone call application to be invoked on the second electronic device to receive the phone call and call data is routed to the second electronic device, as illustrated in
In some embodiments, a phone call interface is displayed on the first electronic device 500 even though the phone call is no longer presented on the first electronic device (e.g., audio of the phone call is not played on the first electronic device and/or call data associated with the phone call is not received, among other possibilities), as illustrated in
In some embodiments, hanging up the phone call at the second electronic device optionally causes a hang-up notification to be received at the first electronic device as illustrated in
In some embodiments, after pushing the phone call to the second electronic device, the first electronic device optionally displays a phone call user interface including an affordance 1032 for causing the call data to be routed back to the first electronic device, as illustrated in
As described below, the method 1100 provides ways of pushing a phone call from a first electronic device to a second electronic device. The method reduces the cognitive burden on a user when interacting with a user interface on the device by providing an intuitive user interface for routing a phone call among electronic devices, thereby creating a more efficient human-machine interface. For battery-operated electronic devices, increasing the efficiency of the user's interaction with the user interfaces conserves power and increases the time between battery charges.
In some embodiments, while receiving a phone call on a first electronic device 500 with one or more processors and memory (1102), the first electronic device generates (1104) for presentation on a display (e.g., a remote display device or a display that is integrated into the electronic device, such as displays 112, 340, and/or 450 in
The first electronic device detects (1116) selection of the first affordance (e.g., touch input on the first affordance, a click, a key press, etc.).
In response to detecting the selection of the first affordance (1118), the first electronic device instructs (1122) the second electronic device to invoke a phone call application to receive the phone call. For example,
Further in response to detecting the selection of the first affordance (1118), the first electronic device causes (1124) call data associated with the phone call to be routed to the second electronic device (e.g., by routing the call data through the first electronic device, by instructing a carrier associated with the phone call to route the phone call to the second electronic device, etc.).
In some embodiments, after causing the call data to be routed to the second electronic device, the first electronic device receives (1132) input controlling the phone call (e.g., mute the call, put the call on hold, hang-up the call, etc.). For example, the first electronic device optionally receives input on phone call controls 1016-1026 illustrated in
In some embodiments, the first electronic device receives (1136) a hang-up command from the second electronic device. For example, a hang-up command is optionally sent by the second electronic device in response to input selecting the end call control 1028 illustrated in
In some embodiments, the first electronic device optionally receives (1144) an indication that the second electronic device ended the phone call. In response to receiving the indication that the second electronic device ended the phone call, the first electronic device optionally generates (1146) for presentation on the display a notification in the user interface of the first device (e.g., cease to display the call in progress status bar at the top of the display). For example,
In some embodiments, the call data is optionally caused (1126) to be routed through the first electronic device to the second electronic device (e.g., using through-device routing, as described above). In some embodiments, causing the call data to be routed to the second electronic device includes sending (1128) a request to a call-routing service to route the phone call to the second electronic device instead of routing the phone call to the first electronic device (e.g., using routing-service routing, as described above).
In some embodiments, while receiving the phone call on the first electronic device (1102), the first electronic device plays (1114) audio associated with the phone call at the first electronic device (e.g., through speaker 111 illustrated in
In some embodiments, the first affordance is optionally included (1106) in a plurality of affordances in the user interface associated with electronic devices capable of receiving the phone call. In some embodiments, generating the plurality of affordances optionally includes (1108) selecting the electronic devices that are associated with a user identity of the first electronic device. In some embodiments, generating the plurality of affordances optionally includes (1110) selecting the electronic devices that are connected to the same network as the first electronic device (e.g., the same WiFi, the same subnet, etc.). In some embodiments, generating the plurality of affordances optionally includes selecting (1112) the electronic devices that are Bluetooth discoverable from the first electronic device. For example,
In some embodiments, after causing the call data associated with the phone call to be routed to the second electronic device, the first electronic device optionally displays (1148) an affordance for causing the call data to be routed back to the first electronic device. For example,
The operations in the information processing methods described above are, optionally, implemented by running one or more functional modules in an information processing apparatus such as general purpose processors (e.g., as described above with respect to
The operations described above with reference to
It should be understood that the particular order in which the operations in
In accordance with some embodiments,
As shown in
In some embodiments, the processing unit 1210 is configured to receive, at the first electronic device, a phone call (e.g., with the receiving unit 1214) that was routed to the first electronic device by a call-routing service. The processing unit 1210 is further configured to, while receiving the phone call, receive a request (e.g., with the receiving unit 1214) to route the phone call to a second electronic device. The processing unit 1210 is further configured to, in response to receiving the request to route the phone call to the second electronic device, and in accordance with a determination that a first routing criteria have been met, send a request (e.g., with the sending unit 1216) to the call-routing service to route the phone call to the second electronic device instead of routing the phone call to the first electronic device. The processing unit 1210 is further configured to, in accordance with a determination that a second routing criteria have been met, cause call data associated with the phone call to be routed through the first electronic device to the second electronic device (e.g., with the routing unit 1218).
In some embodiments, the processing unit 1210 is configured to generate for presentation on a display a user interface (e.g., with the display enabling unit 1212) including a user interface object indicating that a phone call has been routed to a second electronic device. The processing unit 1210 is further configured to, while the user interface is presented on the display, receive a request (e.g., with the receiving unit 1214) to route the phone call to the first electronic device. The processing unit 1210 is further configured to, in response to the request, request (e.g., with the sending unit 1216) call data associated with the phone call. The processing unit 1210 is further configured to, after requesting the call data, present the phone call at the first electronic device (e.g., with the audio enabling unit 1220).
In some embodiments, the processing unit 1210 is configured to, while receiving a phone call on the first electronic device: generate for presentation on a display a user interface (e.g., with the display enabling unit 1212) including a first affordance associated with a second electronic device capable of receiving the phone call, and detect selection of the first affordance (e.g., with the receiving unit 1214). The processing unit 1210 is further configured to, in response to detecting the selection of the first affordance, instruct the second electronic device (e.g., with the sending unit 1216) to invoke a phone call application to receive the phone call, and cause call data associated with the phone call to be routed to the second electronic device (e.g., with the routing unit 1218).
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the invention and its practical applications, to thereby enable others skilled in the art to best use the invention and various described embodiments with various modifications as are suited to the particular use contemplated.
Claims
1. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a first electronic device, cause the first electronic device to:
- generate for presentation on a display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device;
- while the user interface is presented on the display, receive a request to route the phone call to the first electronic device;
- in response to the request, request call data associated with the phone call, wherein the instructions to cause the first electronic device to request the call data includes instructions to cause the call data to be routed through the second electronic device to the first electronic device, wherein the call data includes audio content of the call; and
- after requesting the call data, present the phone call at the first electronic device.
2. The non-transitory computer-readable storage medium of claim 1, further comprising instructions to cause the first electronic device to:
- after requesting the call data, instruct the second electronic device to stop playing audio associated with the phone call.
3. The non-transitory computer-readable storage medium of claim 1, wherein, while the phone call is presented at the first electronic device, the phone call is not presented at the second electronic device.
4. The non-transitory computer-readable storage medium of claim 1, wherein the instructions to cause the first electronic device to request the call data includes instructions to cause the device to:
- send a request to a routing service to reroute the phone call from the second electronic device to the first electronic device.
5. The non-transitory computer-readable storage medium of claim 1, further comprising instructions to cause the first electronic device to:
- receive, from the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
6. The non-transitory computer-readable storage medium of claim 1, further comprising instructions to cause the first electronic device to:
- receive, from a device coordination server that is in communication with the first electronic device and the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
7. The non-transitory computer-readable storage medium of claim 1, further comprising instructions to cause the first electronic device to:
- while presenting the phone call at the first electronic device, generate for presentation on the display an affordance for transferring the phone call back to the second electronic device.
8. The non-transitory computer-readable storage medium of claim 7, further comprising instructions to cause the first electronic device to:
- detect selection of the affordance; and
- in response to detecting selection of the affordance, cause the phone call to be routed back to the second electronic device.
9. The non-transitory computer-readable storage medium of claim 1, further comprising instructions to cause the first electronic device to:
- while presenting the phone call at the first electronic device, generate for presentation on the display an identifier of the second electronic device.
10. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are both associated with the same user identity.
11. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are connected to the same network.
12. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object is generated in accordance with a determination that the second electronic device is discoverable from the first electronic device using short-range communication radio.
13. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed on a lock screen of the first electronic device.
14. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed as a notification at the first electronic device.
15. The non-transitory computer-readable storage medium of claim 1, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed in a phone call user interface on the first electronic device.
16. A method comprising:
- at a first electronic device with one or more processors and memory: generating for presentation on a display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device; while the user interface is presented on the display, receiving a request to route the phone call to the first electronic device; in response to the request, requesting call data associated with the phone call, wherein requesting the call data includes causing the call data to be routed through the second electronic device to the first electronic device, wherein the call data includes audio content of the call; and after requesting the call data, presenting the phone call at the first electronic device.
17. The method of claim 16, further comprising:
- after requesting the call data, instructing the second electronic device to stop playing audio associated with the phone call.
18. The method of claim 16, wherein, while the phone call is presented at the first electronic device, the phone call is not presented at the second electronic device.
19. The method of claim 16, wherein requesting the call data includes:
- sending a request to a routing service to reroute the phone call from the second electronic device to the first electronic device.
20. The method of claim 16, further comprising:
- receiving, from the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
21. The method of claim 16, further comprising:
- receiving, from a device coordination server that is in communication with the first electronic device and the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
22. The method of claim 16, further comprising:
- while presenting the phone call at the first electronic device, generating for presentation on the display an affordance for transferring the phone call back to the second electronic device.
23. The method of claim 22, further comprising:
- detecting selection of the affordance; and
- in response to detecting selection of the affordance, causing the phone call to be routed back to the second electronic device.
24. The method of claim 16, further comprising:
- while presenting the phone call at the first electronic device, generating for presentation on the display an identifier of the second electronic device.
25. The method of claim 16, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are both associated with the same user identity.
26. The method of claim 16, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are connected to the same network.
27. The method of claim 16, wherein the user interface object is generated in accordance with a determination that the second electronic device is discoverable from the first electronic device using short-range communication radio.
28. The method of claim 16, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed on a lock screen of the first electronic device.
29. The method of claim 16, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed as a notification at the first electronic device.
30. The method of claim 16, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed in a phone call user interface on the first electronic device.
31. A first electronic device, comprising:
- a display;
- a memory; and
- a processor coupled to the display and the memory, the processor configured to:
- generate for presentation on the display a user interface including a user interface object indicating that a phone call has been routed to a second electronic device;
- while the user interface is presented on the display, receive a request to route the phone call to the first electronic device;
- in response to the request, request call data associated with the phone call, wherein requesting the call data includes causing the call data to be routed through the second electronic device to the first electronic device, wherein the call data includes audio content of the call; and
- after requesting the call data, present the phone call at the first electronic device.
32. The electronic device of claim 31, the processor configured to:
- after requesting the call data, instruct the second electronic device to stop playing audio associated with the phone call.
33. The electronic device of claim 31, wherein, while the phone call is presented at the first electronic device, the phone call is not presented at the second electronic device.
34. The electronic device of claim 31, wherein requesting the call data includes:
- sending a request to a routing service to reroute the phone call from the second electronic device to the first electronic device.
35. The electronic device of claim 31, the processor configured to:
- receive, from the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
36. The electronic device of claim 31, the processor configured to:
- receive, from a device coordination server that is in communication with the first electronic device and the second electronic device, information that the phone call has been routed to the second electronic device, wherein the user interface is generated based on the information.
37. The electronic device of claim 31, the processor configured to:
- while presenting the phone call at the first electronic device, generate for presentation on the display an affordance for transferring the phone call back to the second electronic device.
38. The electronic device of claim 37, the processor configured to:
- detect selection of the affordance; and
- in response to detecting selection of the affordance, cause the phone call to be routed back to the second electronic device.
39. The electronic device of claim 31, the processor configured to:
- while presenting the phone call at the first electronic device, generate for presentation on the display an identifier of the second electronic device.
40. The electronic device of claim 31, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are both associated with the same user identity.
41. The electronic device of claim 31, wherein the user interface object is generated in accordance with a determination that the first and second electronic devices are connected to the same network.
42. The electronic device of claim 31, wherein the user interface object is generated in accordance with a determination that the second electronic device is discoverable from the first electronic device using short-range communication radio.
43. The electronic device of claim 31, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed on a lock screen of the first electronic device.
44. The electronic device of claim 31, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed as a notification at the first electronic device.
45. The electronic device of claim 31, wherein the user interface object indicating that the phone call has been routed to the second electronic device is displayed in a phone call user interface on the first electronic device.
4803487 | February 7, 1989 | Willard et al. |
5617031 | April 1, 1997 | Tuttle |
5853327 | December 29, 1998 | Gilboa |
6167353 | December 26, 2000 | Piernot et al. |
6190174 | February 20, 2001 | Lam et al. |
6323846 | November 27, 2001 | Westerman et al. |
6398646 | June 4, 2002 | Wei et al. |
6570557 | May 27, 2003 | Westerman et al. |
6677932 | January 13, 2004 | Westerman |
6889138 | May 3, 2005 | Krull et al. |
7081905 | July 25, 2006 | Raghunath |
7130664 | October 31, 2006 | Williams |
7305350 | December 4, 2007 | Bruecken |
7614008 | November 3, 2009 | Ording |
7633076 | December 15, 2009 | Huppi et al. |
7644019 | January 5, 2010 | Woda et al. |
7653883 | January 26, 2010 | Hotelling et al. |
7657849 | February 2, 2010 | Chaudhri et al. |
7663607 | February 16, 2010 | Hotelling et al. |
7843471 | November 30, 2010 | Doan et al. |
7844914 | November 30, 2010 | Andre et al. |
7890422 | February 15, 2011 | Hirka et al. |
7957762 | June 7, 2011 | Herz et al. |
8006002 | August 23, 2011 | Kalayjian et al. |
8050997 | November 1, 2011 | Nosek et al. |
8195507 | June 5, 2012 | Postrel |
8239784 | August 7, 2012 | Hotelling et al. |
8279180 | October 2, 2012 | Hotelling et al. |
8381135 | February 19, 2013 | Hotelling et al. |
8392259 | March 5, 2013 | MacGillivray et al. |
8453940 | June 4, 2013 | Diamond |
8479122 | July 2, 2013 | Hotelling et al. |
8763896 | July 1, 2014 | Kushevsky et al. |
8831677 | September 9, 2014 | Villa-Real |
8892474 | November 18, 2014 | Inskeep et al. |
8894462 | November 25, 2014 | Huang et al. |
8931703 | January 13, 2015 | Mullen et al. |
9324067 | April 26, 2016 | Van Os et al. |
9483763 | November 1, 2016 | Van Os et al. |
9547419 | January 17, 2017 | Yang et al. |
9574896 | February 21, 2017 | McGavran et al. |
20020015024 | February 7, 2002 | Westerman et al. |
20020029169 | March 7, 2002 | Oki et al. |
20020087262 | July 4, 2002 | Bullock et al. |
20030128237 | July 10, 2003 | Sakai |
20030171984 | September 11, 2003 | Wodka et al. |
20030200184 | October 23, 2003 | Dominguez et al. |
20040044953 | March 4, 2004 | Watkins et al. |
20040100389 | May 27, 2004 | Naito et al. |
20040254891 | December 16, 2004 | Blinn et al. |
20050117601 | June 2, 2005 | Anderson et al. |
20050187873 | August 25, 2005 | Labrou et al. |
20050190059 | September 1, 2005 | Wehrenberg |
20050191159 | September 1, 2005 | Benko |
20050237194 | October 27, 2005 | VoBa |
20060000900 | January 5, 2006 | Fernandes et al. |
20060017692 | January 26, 2006 | Wehrenberg et al. |
20060025923 | February 2, 2006 | Dotan et al. |
20060026536 | February 2, 2006 | Hotelling et al. |
20060033724 | February 16, 2006 | Chaudhri et al. |
20060079973 | April 13, 2006 | Bacharach |
20060135064 | June 22, 2006 | Cho et al. |
20060165060 | July 27, 2006 | Dua |
20060197753 | September 7, 2006 | Hotelling |
20060294025 | December 28, 2006 | Mengerink |
20070096283 | May 3, 2007 | Ljung et al. |
20070096765 | May 3, 2007 | Kagan |
20070188409 | August 16, 2007 | Repetto et al. |
20070194113 | August 23, 2007 | Esplin et al. |
20070254712 | November 1, 2007 | Chitti |
20080016443 | January 17, 2008 | Hiroshima et al. |
20080027947 | January 31, 2008 | Pritchett et al. |
20080040265 | February 14, 2008 | Rackley, III et al. |
20080040786 | February 14, 2008 | Chang |
20080041936 | February 21, 2008 | Vawter |
20080077673 | March 27, 2008 | Thomas |
20080120029 | May 22, 2008 | Zelek et al. |
20080165136 | July 10, 2008 | Christie et al. |
20080214191 | September 4, 2008 | Yach et al. |
20080292074 | November 27, 2008 | Boni |
20080320391 | December 25, 2008 | Lemay et al. |
20090036165 | February 5, 2009 | Brede |
20090037326 | February 5, 2009 | Chitti et al. |
20090057396 | March 5, 2009 | Barbour et al. |
20090088207 | April 2, 2009 | Sweeney et al. |
20090195402 | August 6, 2009 | Izadi et al. |
20090199130 | August 6, 2009 | Tsern et al. |
20090203315 | August 13, 2009 | Kawabata et al. |
20090207743 | August 20, 2009 | Huq et al. |
20090210308 | August 20, 2009 | Toomer et al. |
20090222748 | September 3, 2009 | Lejeune et al. |
20090325630 | December 31, 2009 | Tiitola et al. |
20100082481 | April 1, 2010 | Lin et al. |
20100114731 | May 6, 2010 | Kingston et al. |
20100131190 | May 27, 2010 | Terauchi et al. |
20100149090 | June 17, 2010 | Morris et al. |
20100153265 | June 17, 2010 | Hershfield et al. |
20100185446 | July 22, 2010 | Homma et al. |
20100223145 | September 2, 2010 | Dragt |
20100267362 | October 21, 2010 | Smith et al. |
20100272250 | October 28, 2010 | Yap |
20100287513 | November 11, 2010 | Singh et al. |
20110059769 | March 10, 2011 | Brunolli |
20110078025 | March 31, 2011 | Shrivastav |
20110081860 | April 7, 2011 | Brown et al. |
20110099079 | April 28, 2011 | White |
20110153628 | June 23, 2011 | Basu et al. |
20110159959 | June 30, 2011 | Mallinson et al. |
20110251892 | October 13, 2011 | Laracey |
20120036029 | February 9, 2012 | Esplin et al. |
20120036556 | February 9, 2012 | LeBeau et al. |
20120078751 | March 29, 2012 | MacPhail et al. |
20120084210 | April 5, 2012 | Farahmand |
20120089300 | April 12, 2012 | Wolterman |
20120089507 | April 12, 2012 | Zhang et al. |
20120116669 | May 10, 2012 | Lee et al. |
20120123937 | May 17, 2012 | Spodak |
20120191603 | July 26, 2012 | Nuzzi |
20120192094 | July 26, 2012 | Goertz |
20120198531 | August 2, 2012 | Ort et al. |
20120221464 | August 30, 2012 | Pasquero et al. |
20120236037 | September 20, 2012 | Lessing et al. |
20120245985 | September 27, 2012 | Cho et al. |
20120287290 | November 15, 2012 | Jain |
20120290449 | November 15, 2012 | Mullen et al. |
20120303268 | November 29, 2012 | Su et al. |
20120310760 | December 6, 2012 | Phillips et al. |
20120316777 | December 13, 2012 | Kitta |
20120322370 | December 20, 2012 | Lee |
20120322371 | December 20, 2012 | Lee |
20130047034 | February 21, 2013 | Salomon et al. |
20130065482 | March 14, 2013 | Trickett |
20130076591 | March 28, 2013 | Sirpal et al. |
20130080272 | March 28, 2013 | Ronca et al. |
20130080275 | March 28, 2013 | Ronca et al. |
20130085931 | April 4, 2013 | Runyan |
20130103519 | April 25, 2013 | Kountotsis et al. |
20130106603 | May 2, 2013 | Weast et al. |
20130110719 | May 2, 2013 | Carter et al. |
20130115932 | May 9, 2013 | Williams |
20130124423 | May 16, 2013 | Fisher |
20130125016 | May 16, 2013 | Pallakoff et al. |
20130134212 | May 30, 2013 | Chang |
20130141325 | June 6, 2013 | Bailey |
20130166679 | June 27, 2013 | Kuwahara |
20130189963 | July 25, 2013 | Epp |
20130200146 | August 8, 2013 | Moghadam |
20130218721 | August 22, 2013 | Borhan et al. |
20130219285 | August 22, 2013 | Iwasaki |
20130219303 | August 22, 2013 | Eriksson et al. |
20130244615 | September 19, 2013 | Miller |
20130246202 | September 19, 2013 | Tobin |
20130304651 | November 14, 2013 | Smith |
20130322665 | December 5, 2013 | Bennett et al. |
20130332358 | December 12, 2013 | Zhao |
20130332364 | December 12, 2013 | Templeton et al. |
20130339436 | December 19, 2013 | Gray |
20130345975 | December 26, 2013 | Vulcano et al. |
20130346273 | December 26, 2013 | Stockton et al. |
20130346882 | December 26, 2013 | Shiplacoff et al. |
20140003597 | January 2, 2014 | Lazaridis |
20140006285 | January 2, 2014 | Chi et al. |
20140006949 | January 2, 2014 | Briand et al. |
20140015546 | January 16, 2014 | Frederick |
20140025513 | January 23, 2014 | Cooke et al. |
20140058860 | February 27, 2014 | Roh et al. |
20140058935 | February 27, 2014 | Mijares |
20140064155 | March 6, 2014 | Evans |
20140068751 | March 6, 2014 | Last |
20140073252 | March 13, 2014 | Lee et al. |
20140074716 | March 13, 2014 | Ni |
20140074717 | March 13, 2014 | Evans |
20140081854 | March 20, 2014 | Sanchez et al. |
20140084857 | March 27, 2014 | Liu et al. |
20140094124 | April 3, 2014 | Dave et al. |
20140094143 | April 3, 2014 | Ayotte |
20140101056 | April 10, 2014 | Wendling |
20140122331 | May 1, 2014 | Vaish et al. |
20140128035 | May 8, 2014 | Sweeney |
20140129435 | May 8, 2014 | Pardo et al. |
20140129441 | May 8, 2014 | Blanco et al. |
20140134947 | May 15, 2014 | Stouder-Studenmund |
20140142851 | May 22, 2014 | Larmo et al. |
20140143145 | May 22, 2014 | Kortina et al. |
20140143737 | May 22, 2014 | Mistry et al. |
20140149198 | May 29, 2014 | Kim et al. |
20140155031 | June 5, 2014 | Lee et al. |
20140160033 | June 12, 2014 | Brikman et al. |
20140164241 | June 12, 2014 | Neuwirth |
20140167986 | June 19, 2014 | Parada et al. |
20140173455 | June 19, 2014 | Shimizu et al. |
20140180582 | June 26, 2014 | Pontarelli et al. |
20140187163 | July 3, 2014 | Fujita |
20140188673 | July 3, 2014 | Graham et al. |
20140191715 | July 10, 2014 | Wechlin et al. |
20140237389 | August 21, 2014 | Ryall et al. |
20140244495 | August 28, 2014 | Davis et al. |
20140279442 | September 18, 2014 | Luoma et al. |
20140279497 | September 18, 2014 | Qaim-Maqami et al. |
20140279556 | September 18, 2014 | Priebatsch et al. |
20140320387 | October 30, 2014 | Eriksson et al. |
20140337207 | November 13, 2014 | Zhang et al. |
20140337450 | November 13, 2014 | Choudhary et al. |
20140343843 | November 20, 2014 | Yanku |
20140359481 | December 4, 2014 | Graham et al. |
20140365113 | December 11, 2014 | McGavran et al. |
20140370807 | December 18, 2014 | Lei et al. |
20150006376 | January 1, 2015 | Nuthulapati et al. |
20150012425 | January 8, 2015 | Mathew |
20150017956 | January 15, 2015 | Jeong |
20150039494 | February 5, 2015 | Sinton et al. |
20150044965 | February 12, 2015 | Kamon et al. |
20150051846 | February 19, 2015 | Masuya |
20150058146 | February 26, 2015 | Gaddam et al. |
20150061972 | March 5, 2015 | Seo et al. |
20150065035 | March 5, 2015 | Kim et al. |
20150066758 | March 5, 2015 | DeNardis et al. |
20150067580 | March 5, 2015 | Um et al. |
20150094031 | April 2, 2015 | Liu |
20150121405 | April 30, 2015 | Ekselius et al. |
20150127539 | May 7, 2015 | Ye et al. |
20150257004 | September 10, 2015 | Shanmugam et al. |
20150339652 | November 26, 2015 | Park et al. |
20150348001 | December 3, 2015 | Van Os et al. |
20150348002 | December 3, 2015 | Van Os et al. |
20150348009 | December 3, 2015 | Brown et al. |
20150348014 | December 3, 2015 | Van Os et al. |
20150348029 | December 3, 2015 | Van Os et al. |
20160048705 | February 18, 2016 | Yang et al. |
20160061613 | March 3, 2016 | Jung et al. |
20160061623 | March 3, 2016 | Pahwa et al. |
20160062572 | March 3, 2016 | Yang et al. |
20160238402 | August 18, 2016 | Mcgavran et al. |
20160253665 | September 1, 2016 | Van Os et al. |
20160259489 | September 8, 2016 | Yang |
20160260414 | September 8, 2016 | Yang |
20160358133 | December 8, 2016 | Van Os et al. |
20160358134 | December 8, 2016 | Van Os et al. |
20160358180 | December 8, 2016 | Van Os et al. |
20170011210 | January 12, 2017 | Cheong et al. |
20170032375 | February 2, 2017 | Van Os et al. |
20170083188 | March 23, 2017 | Yang et al. |
20170160098 | June 8, 2017 | Mcgavran et al. |
2016100796 | January 2014 | AU |
104205785 | December 2014 | CN |
104272854 | January 2015 | CN |
104281430 | January 2015 | CN |
104346297 | February 2015 | CN |
0836074 | April 1998 | EP |
1614992 | January 2006 | EP |
1858238 | November 2007 | EP |
2096413 | September 2009 | EP |
2247087 | November 2010 | EP |
2306692 | April 2011 | EP |
2341315 | July 2011 | EP |
2428947 | March 2012 | EP |
2466260 | June 2012 | EP |
2523439 | November 2012 | EP |
2632131 | August 2013 | EP |
2672377 | December 2013 | EP |
2720442 | April 2014 | EP |
2725537 | April 2014 | EP |
2505476 | March 2014 | GB |
6-284182 | October 1994 | JP |
11-73530 | March 1999 | JP |
11-183183 | July 1999 | JP |
2003-16398 | January 2003 | JP |
2003-346059 | December 2003 | JP |
2004-252736 | September 2004 | JP |
2005-521961 | July 2005 | JP |
2005-523505 | August 2005 | JP |
2006-114018 | April 2006 | JP |
2006-163960 | June 2006 | JP |
2006-197071 | July 2006 | JP |
2007-334637 | December 2007 | JP |
2009-49878 | March 2009 | JP |
2012-508930 | April 2012 | JP |
2013-20496 | January 2013 | JP |
2013-34322 | February 2013 | JP |
2014-44719 | March 2014 | JP |
2014-44724 | March 2014 | JP |
10-2004-0049502 | June 2004 | KR |
10-2008-0064395 | July 2008 | KR |
10-2011-0056561 | May 2011 | KR |
201012152 | March 2010 | TW |
201137722 | November 2011 | TW |
201215086 | April 2012 | TW |
201316247 | April 2013 | TW |
201324310 | June 2013 | TW |
201409345 | March 2014 | TW |
M474482 | March 2014 | TW |
201509168 | March 2015 | TW |
2003/083793 | October 2003 | WO |
03093765 | November 2003 | WO |
2007/000012 | January 2007 | WO |
2007/008321 | January 2007 | WO |
2007/105937 | September 2007 | WO |
2010/039337 | April 2010 | WO |
2010/056484 | May 2010 | WO |
2011063516 | June 2011 | WO |
2012/083113 | June 2012 | WO |
2013/023224 | February 2013 | WO |
2013/169875 | November 2013 | WO |
2013/177548 | November 2013 | WO |
2014/074407 | May 2014 | WO |
2014078965 | May 2014 | WO |
2014/171734 | October 2014 | WO |
- Lemay et al., U.S. Appl. No. 60/936,562, filed Jun. 20, 2007, titled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos”, 61 pages.
- Non Final Office Action received for U.S. Appl. No. 14/839,913, dated Mar. 2, 2016, 11 pages.
- Final Office Action received for U.S. Appl. No. 14/836,754, dated Mar. 22, 2016, 17 pages.
- 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).
- Office Action received for German Patent Application No. 2020150042678, dated Nov. 4, 2015, 5 pages (3 pages of English Translation and 2 pages of Official Copy).
- EASYVIDEOGUIDES, “Mapquest”, available on : https://www.youtube.com/watch?v=7sDIDNM2bCI, Dec. 26, 2007, 4 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.
- International Search Report and Written Opinion received for PCT Application No. PCT/US2015/047507, dated Feb. 22, 2016, 22 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/055165, dated Apr. 20, 2016, 22 pages.
- Office Action received for Australian Patent Application No. 2016100155, dated May 4, 2016, 7 pages.
- Office Action received for Denmark Patent Application No. PA201670074, dated Apr. 7, 2016, 8 pages.
- Notice of Allowance received for U.S. Appl. No. 14/864,011, dated Apr. 28, 2016, 5 pages.
- Advisory Action received for U.S. Appl. No. 14/503,296, dated Oct. 2, 2015, 3 pages.
- Non-Final Office Action received for U.S. Appl. No. 14/503,072, dated Jun. 17, 2016, 19 pages.
- Notice of Allowance received for U.S. Appl. No. 14/503,364, dated Jun. 16, 2016, 11 pages.
- Office Action received for Australian Patent Application No. 2016100367, dated May 25, 2016, 3 pages.
- Office Action received for Australian Patent Application No. 2016100383, dated Jun. 9, 2016, 2 pages.
- Office Action received for Danish Patent Application No. PA201570664, dated Jun. 3, 2016, 3 pages.
- 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 ).
- 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.
- Office Action received for Danish Patent Application No. PA201670074, dated Jun. 28, 2016, 5 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2016/016621, dated May 9, 2016, 12 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/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.
- Notice of Allowance received for U.S. Appl. No. 14/839,913, dated Aug. 11, 2016, 5 pages.
- 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 Taiwanese Patent Application No. 104117508, dated Jul. 20, 2016, 19 pages (8 pages of English Translation and 11 pages of Official Copy).
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/030199, dated Aug. 14, 2015, 11 pages.
- Final Office Action received for U.S. Appl. No. 14/503,072, dated Sep. 1, 2015, 16 pages.
- Non Final Office Action received for U.S. Appl. No. 14/503,072, dated Jan. 26, 2015, 12 pages.
- Final Office Action received for U.S. Appl. No. 14/503,296, dated Jul. 2, 2015, 7 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/503,381, dated May 13, 2015, 13 pages.
- Notice of Allowance received for the U.S. Appl. No. 14/503,381, dated Dec. 16, 2015, 8 pages.
- Non Final Office Action received for U.S. Appl. No. 14/836,754, dated Nov. 17, 2015, 15 pages.
- Office Action received for Australian 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.
- 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).
- 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).
- Kamijo, Noboru, “Next Generation Mobile System—WatchPad1.5”, Available at <http://researcher.ibm.com/researcher/view_group_subpage.php?id=5617>, accessed on Jul. 4, 2015, 2 pages.
- Npasqua, “Maps: ability to swipe step by step in turn-by-turn mode”, 2012, Apple Support Communities, Available at: <https://discussions.apple.com/thread/4424256?start=O&tstart=0>.
- 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 Patent Application No. PCT/US2015/033380, dated Aug. 10, 2015, 13 pages.
- Invitation to Pay Additional Fees and Partial Search Report received for PCT Patent Application No. PCT/US2015/046892, dated Nov. 4, 2015, 5 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2015/025188, dated Jun. 23, 2015, 11 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/864,011, dated Jan. 21, 2016, 10 pages.
- Non Final Office Action received for U.S. Appl. No. 14/869,877, dated Jan. 29, 2016, 18 pages.
- International Search Report and Written Opinion received for PCT Application No. PCT/US2015/046892, dated Jan. 27, 2016, 20 pages.
- Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/047507, dated Jan. 4, 2016, 8 pages.
- Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US2015/055165, dated Jan. 18, 2016, 6 pages.
- Final Office Action received for U.S. Appl. No. 15/137,944, dated Feb. 27, 2017, 11 pages.
- Final Office Action received for U.S. Appl. No. 14/836,754, dated Mar. 31, 2017, 24 pages.
- 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.
- 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/719,217, dated Feb. 23, 2017, 37 pages.
- Intention to Grant received for Danish Patent Application No. PA201570665, dated Feb. 28, 2017, 2 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/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.
- Notice of Allowance received for Danish Patent Application No. PA201570664, dated Feb. 20, 2017, 2 pages.
- Office Action received for Danish Patent Application No. PA201570773, dated Feb. 15, 2017, 3 pages.
- Advisory Action received for U.S. Appl. No. 14/870,793, dated Apr. 13, 2017, 3 pages.
- Extended European Search Report received for European Patent Application No. 16201159.7, dated Mar. 27, 2017, 12 pages.
- Final Office Action received for U.S. Appl. No. 14/870,726, dated Apr. 19, 2017, 17 pages.
- Office Action received for Australian Patent Application No. 201710231, dated Apr. 13, 2017, 3 pages.
- Office Action received for Australian Patent Application No. 2015266650, 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 Taiwanese Patent Application No. 104117508,dated Mar. 20, 2017, 22 pages (9 pages of English Translation and 13 pages of Official Copy).
- 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.
- Office Action received for Australian Patent Application No. 2016100383, dated Nov. 11, 2016, 3 pages.
- Office Action received for Chinese Patent Application No. 201620509515.9, dated Nov. 9, 2016, 2 pages (1 page of English Translation and 1 page of Official Copy).
- Office Action received for Danish Patent Application No. PA201670362, dated Nov. 21, 2016, 11 pages.
- 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 Danish Patent Application No. PA201570664, dated Dec. 14, 2016, 2 pages.
- Office Action received for Australian Patent Application No. 2017100070, dated Mar. 16, 2017, 6 pages.
- Office Action received for Australian Patent Application No. 2017201064, dated Mar. 9, 2017, 2 pages.
- Office Action received for Australian Patent Application No. 2017201068 dated Mar. 10, 2017, 2 pages.
- Office Action received for Danish Patent Application No. PA201670074, dated Mar. 16, 2017, 2 pages.
- Office Action received for Taiwanese Patent Application No. 104114953, dated Feb. 18, 2017, 9 pages (4 pages of English Translation and 2 pages of Official Copy).
- Ehowtech, “How to Get Written Directions on a Garmin : Using a Garmin”, available online at: https://www.youtube.com/watch?v=s_EKT6qH4LI, Dec. 2, 2012, 1 page.
- Non-Final Office Action received for U.S. Appl. No. 14/836,754, dated Oct. 21, 2016, 18 pages.
- Office Action received for Australian Patent Application No. 2016100367, dated Oct. 26, 2016, 3 pages.
- 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).
- Final Office Action received for U.S. Appl. No. 14/869,877, dated Aug. 3, 2016, 13 pages.
- International Search Report and Written Opinion received for PCT Patent Application No. PCT/US16/34175, dated Oct. 7, 2016, 17 pages.
- Invitation to Pay Additional Fees received for PCT Patent Application No. PCT/US16/34175, mailed on Aug. 11, 2016, 3 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,296, dated Oct. 5, 2016, 11 pages.
- Non-Final Office Action received for U.S. Appl. No. 14/870,726, dated Sep. 16, 2016, 12 pages.
- Non-Final Office Action received for U.S. Appl. No. 15/137,944, dated Oct. 18, 2016, 10 pages.
- Notice of Allowance received for Danish Patent Application No. PA201570771, dated Sep. 2, 2016, 2 pages.
- Notice of Allowance received for U.S. Appl. No. 14/864,011, dated Oct. 5, 2016, 5 pages.
- Office Action received for Australian Patent Application No. 2016100796, dated Aug. 26, 2016, 6 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. 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. PA201570773, dated Sep. 12, 2016, 3 pages.
- 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. 104133757, dated Jul. 6, 2016, 22 pages (9 pages of English Translation and 13 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).
- Advisory Action received for U.S. Appl. No. 14/869,877, dated Jan. 5, 2017, 3 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.
- Final Office Action received for U.S. Appl. No. 14/870,793, dated Jan. 19, 2017, 16 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.
- Office Action received for Australian Patent Application No. 2016100796, dated Feb. 13, 2017, 4 pages.
- Office Action received for Chinese Patent Application No. 201620119869.2, dated Nov. 22, 2016, 2 pages (Official Copy only). {See Communication Under 37 CFR § 1.98(a)(3)}.
- 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. 201620480708.6, dated Jan. 9, 2017, 3 pages (1 page of English Translation and 1 page of Official Copy).
- Office Action received for Danish Patent Application No. PA201670749, dated Jan. 30, 2017, 11 pages.
- Office Action received for Danish Patent Application No. PA201670751, dated Jan. 13, 2017, 9 pages.
- Advisory Action received for U.S. Appl. No. 15/137,944, dated May 11, 2017, 6 pages.
- Decision to Grant received for Danish Patent Application No. PA201570665, dated Apr. 26, 2017, 2 pages.
- 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 2 pages of Official Copy).
- Notice of Allowance received for Taiwanese Patent Application No. 104128700, dated Mar. 27, 2017, 3 pages (Official Copy only). {See Communication under 37 CFR § 198(a)(3)}.
- Extended European Search Report received for European Patent Application No. 16804040.0, dated Feb. 26, 2018, 9 pages.
- Intention to Grant received for European Patent Application No. 15724160.5, dated Mar. 7, 2018, 8 pages.
- Non-Final Office Action received for U.S. Appl. No. 14/839,903, dated Feb. 26, 2018, 10 pages.
- Notice of Acceptance received for Australian Patent Application No. 2017201064, dated Feb. 20, 2018, 3 pages.
- Office Action received for Australian Patent Application No. 2017101375, dated Feb. 19, 2018, 4 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.
- 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.
- 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.
- 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.
- 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/016621, dated Aug. 24, 2017, 8 pages.
- International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2016/034175, dated Dec. 14, 2017, 14 pages.
- Naver Blog, “How to Use Smart Wallet and Registered Card”, Online Available at <http://feena74.blog.me/140185758401>, Mar. 29, 2013, 20 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/503,296, dated Aug. 28, 2017, 14 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/839,897, dated May 18, 2017, 11 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/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.
- 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 Allowance received for Japanese Patent Application No. 2016-224508, dated Jun. 20, 2017, 3 pages. (Official Copy only) (see attached 37 CFR § 1.98(a) (3)).
- Notice of Allowance received for Taiwanese Patent Application No. 104114953, dated Oct. 17, 2017, 3 pages. (Official Copy only) (see attached 37 CFR § 1.98(a) (3)).
- 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) (see attached 37 CFR § 1.98(a) (3)).
- Notice of Allowance received for U.S. Appl. No. 15/137,944, dated Dec. 21, 2017, 8 pages.
- Oates, Nathan, “PebbGPS”, Available online at:- https://pebble.devpost.com/submissions/21694-pebbgps, Mar. 16, 2014, 2 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 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. 2017101375, dated Dec. 1, 2017, 3 pages.
- Office Action received for Australian Patent Application No. 2017201068, dated Jan. 17, 2018, 5 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. PA201670749, dated Oct. 3, 2017, 3 pages.
- Office Action received for Danish Patent Application No. PA201670751, dated Nov. 13, 2017, 2 pages.
- Office Action received for European Patent Application No. 15727291.5, dated Jan. 15, 2018, 8 pages.
- 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 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 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. 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. 104133756, dated May 17, 2017, 13 pages (6 pages of English Translation and 7 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, 8 pages (Official Copy only) (see attached 37 CFR § 1.98(a) (3)).
- The Gadget Pill, “Sygic for Android Navigation with HUD”, Available online at:- https://www.youtube.com/watch?v=fGqrycRevGU, Mar. 23, 2014, 1 page.
Type: Grant
Filed: Sep 30, 2014
Date of Patent: May 8, 2018
Patent Publication Number: 20150350448
Assignee: Apple Inc. (Cupertino, CA)
Inventors: Patrick L. Coffman (San Francisco, CA), Keith Walter Rauenbuehler (San Francisco, CA)
Primary Examiner: Nafiz E Hoque
Application Number: 14/503,327
International Classification: H04M 3/53 (20060101); H04M 3/54 (20060101); G06F 3/0481 (20130101); G06F 3/0484 (20130101); H04M 3/42 (20060101); H04M 3/58 (20060101); H04M 3/46 (20060101);