Patent Grant
11743390
The disclosed embodiments relate generally to portable electronic devices, and more particularly, to portable devices that provide graphical user interfaces for managing a conference call among three or more parties.
As portable electronic devices become more compact, and the number of functions performed by a given device increase, it has become a significant challenge to design a user interface that allows users to easily interact with a multifunction device. This challenge is particular significant for handheld portable devices, which have much smaller screens than desktop or laptop computers. This situation is unfortunate because the user interface is the gateway through which users receive not only content but also responses to user actions or behaviors, including user attempts to access a device's features, tools, and functions. Some portable communication devices (e.g., mobile telephones, sometimes called mobile phones, cell phones, cellular telephones, and the like) have resorted to adding more pushbuttons, increasing the density of push buttons, overloading the functions of pushbuttons, or using complex menu systems to allow a user to access, store and manipulate data. These conventional user interfaces often result in complicated key sequences and menu hierarchies that must be memorized by the user.
Many conventional user interfaces, such as those that include physical pushbuttons, are also inflexible. This is unfortunate because it may prevent a user interface from being configured and/or adapted by either an application running on the portable device or by users. When coupled with the time consuming requirement to memorize multiple key sequences and menu hierarchies, and the difficulty in activating a desired pushbutton, such inflexibility is frustrating to most users.
Many cell phones support a “conference call” feature that allows three or more parties (corresponding to three or more phones) to participate in a single conversation simultaneously. At present, however, it is difficult for a cell phone user to manage a conference call, including such tasks as adding a new party to the conference call, removing an existing party from the conference call, temporarily converting the conference call into a private phone call with one of the existing parties, and returning to the conference call from the private phone call. With present devices, it is not readily apparent to a user how to perform these tasks.
Accordingly, there is a need for portable multifunction devices with more transparent and intuitive user interfaces for managing a conference call between multiple parties that are easy to use, configure, and/or adapt. Such interfaces increase the effectiveness, efficiency and user satisfaction with portable multifunction devices.
The above deficiencies and other problems associated with user interfaces for portable devices are reduced or eliminated by the disclosed portable multifunction device. In some embodiments, the device has a touch-sensitive display (also known as a “touch screen”) with a graphical user interface (GUI), one or more processors, memory and one or more modules, programs or sets of instructions stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through finger contacts and gestures on the touch-sensitive display. In some embodiments, the functions may include telephoning, video conferencing, e-mailing, instant messaging, blogging, digital photographing, digital videoing, web browsing, digital music playing, and/or digital video playing. Instructions for performing these functions may be included in a computer program product configured for execution by one or more processors.
One aspect of the invention involves a computer-implemented method performed by a portable multifunction device with a touch screen display. The method includes: displaying a phone call user interface on the touch screen display. The phone call user interface includes: a first informational item associated with an active phone call between a user of the device and a first party, a second informational item associated with a suspended phone call between the user and a second party, and a merge call icon. The method also includes: upon detecting a user selection of the merge call icon, merging the active phone call and the suspended phone call into a conference call between the user, the first party, and the second party, and replacing the phone call user interface with a conference call user interface. The conference call user interface includes: a third informational item associated with the conference call in replacement of the first and second informational items, and a conference call management icon.
Another aspect of the invention involves a portable multifunction device that includes a touch screen display, one or more processors, memory, and one or more programs. The one or more programs are stored in the memory and configured to be executed by the one or more processors. The programs includes: instructions for displaying a phone call user interface on the touch screen display, the phone call user interface including: a first informational item associated with an active phone call between a user of the device and a first party, a second informational item associated with a suspended phone call between the user and a second party, and a merge call icon; instructions for merging the active phone call and the suspended phone call into a conference call between the user, the first party, and the second party upon detecting a user selection of the merge call icon; and instructions for replacing the phone call user interface with a conference call user interface upon detecting the user selection of the merge call icon. The conference call user interface includes: a third informational item associated with the conference call in replacement of the first and second informational items, and a conference call management icon.
Another aspect of the invention involves a computer-program product that includes a computer readable storage medium and a computer program mechanism embedded therein. The computer program mechanism includes instructions, which when executed by a portable multifunction device with a touch screen display, cause the device to: display a phone call user interface on the touch screen display, the phone call user interface including: a first informational item associated with an active phone call between a user of the device and a first party, a second informational item associated with a suspended phone call between the user and a second party, and a merge call icon; merge the active phone call and the suspended phone call into a conference call between the user, the first party, and the second party upon detecting a user selection of the merge call icon; and replace the phone call user interface with a conference call user interface upon detecting the user selection of the merge call icon. In some embodiments, the conference call user interface includes: a third informational item associated with the conference call in replacement of the first and second informational items, and a conference call management icon.
Another aspect of the invention involves a phone call graphical user interface on a portable multifunction device with a touch screen display. The phone call graphical user interface includes: a first informational item associated with an active phone call between a user of the device and a first party, a second informational item associated with a suspended phone call between the user and a second party, and a merge call icon. Upon detecting a user selection of the merge call icon, the active phone call and the suspended phone call are merged into a conference call between the user, the first party, and the second party and the phone call graphical user interface is replaced with a conference call user interface. The conference call user interface includes: a third informational item associated with the conference call in replacement of the first and second informational items, and a conference call management icon.
Another aspect of the invention involves a portable multifunction device with a touch screen display. The device includes: means for displaying a phone call user interface on the touch screen display, the phone call user interface including: a first informational item associated with an active phone call between a user of the device and a first party, a second informational item associated with a suspended phone call between the user and a second party, and a merge call icon; means for merging, upon detecting a user selection of the merge call icon, the active phone call and the suspended phone call into a conference call between the user, the first party, and the second party; and means for replacing, upon detecting the user selection of the merge call icon, the phone call user interface with a conference call user interface. The conference call user interface includes: a third informational item associated with the conference call in replacement of the first and second informational items, and a conference call management icon.
Thus, the invention provides a transparent and intuitive user interface for managing conference calls on a portable multifunction device with a touch screen display.
For a better understanding of the aforementioned embodiments of the invention as well as additional embodiments thereof, reference should be made to the Description of Embodiments below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
Reference will now be made in detail to embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be apparent to one of ordinary skill in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first gesture could be termed a second gesture, and, similarly, a second gesture could be termed a first gesture, without departing from the scope of the present invention.
The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the description of the invention 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 “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.
Embodiments of a portable multifunction device, 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.
The user interface may include a physical click wheel in addition to a touch screen or a virtual click wheel displayed on the touch screen. A click wheel is a user-interface device that may provide navigation commands based on an angular displacement of the wheel or a point of contact with the wheel by a user of the device. A click wheel may also be used to provide a user command corresponding to selection of one or more items, for example, when the user of the device presses down on at least a portion of the wheel or the center of the wheel. Alternatively, breaking contact with a click wheel image on a touch screen surface may indicate a user command corresponding to selection. For simplicity, in the discussion that follows, a portable multifunction device that includes a touch screen is used as an exemplary embodiment. It should be understood, however, that some of the user interfaces and associated processes may be applied to other devices, such as personal computers and laptop computers, which may include one or more other physical user-interface devices, such as a physical click wheel, a physical keyboard, a mouse and/or a joystick.
The device supports a variety of applications, such as a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a blogging 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 may be executed on the device may use at least one common physical user-interface device, such as the touch screen. One or more functions of the touch screen as well as corresponding information displayed on the device may be 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 screen) of the device may support the variety of applications with user interfaces that are intuitive and transparent.
The user interfaces may include one or more soft keyboard embodiments. The soft keyboard embodiments may include standard (QWERTY) and/or non-standard configurations of symbols on the displayed icons of the keyboard, such as those described in U.S. patent application Ser. No. 11/459,606, “Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, and Ser. No. 11/459,615, “Touch Screen Keyboards For Portable Electronic Devices,” filed Jul. 24, 2006, the contents of which are hereby incorporated by reference herein in their entirety. The keyboard embodiments may include a reduced number of icons (or soft keys) relative to the number of keys in existing physical keyboards, such as that for a typewriter. This may make it easier for users to select one or more icons in the keyboard, and thus, one or more corresponding symbols. The keyboard embodiments may be adaptive. For example, displayed icons may be modified in accordance with user actions, such as selecting one or more icons and/or one or more corresponding symbols. One or more applications on the portable device may utilize common and/or different keyboard embodiments. Thus, the keyboard embodiment used may be tailored to at least some of the applications. In some embodiments, one or more keyboard embodiments may be tailored to a respective user. For example, one or more keyboard embodiments may be tailored to a respective user based on a word usage history (lexicography, slang, individual usage) of the respective user. Some of the keyboard embodiments may be adjusted to reduce a probability of a user error when selecting one or more icons, and thus one or more symbols, when using the soft keyboard embodiments.
Attention is now directed towards embodiments of the device.
It should be appreciated that the device 100 is only one example of a portable multifunction device 100, and that the device 100 may have more or fewer components than shown, may combine two or more components, or a may have a different configuration or arrangement of the components. The various components shown in
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. Access to memory 102 by other components of the device 100, such as the CPU 120 and the peripherals interface 118, may be controlled by the memory controller 122.
The peripherals interface 118 couples the input and output peripherals of the device to the 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 the device 100 and to process data.
In some embodiments, the peripherals interface 118, the CPU 120, and the memory controller 122 may be implemented on a single chip, such as a chip 104. In some other embodiments, they may be implemented on separate chips.
The RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. The RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. The RF circuitry 108 may include 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. The RF circuitry 108 may communicate with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication may use 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), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for email (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), and/or 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.
The audio circuitry 110, the speaker 111, and the microphone 113 provide an audio interface between a user and the device 100. The audio circuitry 110 receives audio data from the peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal to human-audible sound waves. The audio circuitry 110 also receives electrical signals converted by the microphone 113 from sound waves. The audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to the peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or the RF circuitry 108 by the peripherals interface 118. In some embodiments, the audio circuitry 110 also includes a headset jack (e.g. 212,
The I/O subsystem 106 couples input/output peripherals on the device 100, such as the touch screen 112 and other input/control devices 116, to the peripherals interface 118. The I/O subsystem 106 may include a display controller 156 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input/control devices 116 may 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 may be coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208,
The touch-sensitive touch screen 112 provides an input interface and an output interface between the device and a user. The display controller 156 receives and/or sends electrical signals from/to the touch screen 112. The 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, further details of which are described below.
A 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. The touch screen 112 and the 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 the touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages or images) that are displayed on the touch screen. In an exemplary embodiment, a point of contact between a touch screen 112 and the user corresponds to a finger of the user.
The touch screen 112 may use LCD (liquid crystal display) technology, or LPD (light emitting polymer display) technology, although other display technologies may be used in other embodiments. The touch screen 112 and the 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 a touch screen 112.
A touch-sensitive display in some embodiments of the touch screen 112 may be analogous to the multi-touch sensitive tablets 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 herein in their entirety. However, a touch screen 112 displays visual output from the portable device 100, whereas touch sensitive tablets do not provide visual output.
A touch-sensitive display in some embodiments of the 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.
The touch screen 112 may have a resolution in excess of 100 dpi. In an exemplary embodiment, the touch screen has a resolution of approximately 160 dpi. The user may make contact with the 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 are much 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, the 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 the touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
In some embodiments, the device 100 may include a physical or virtual click wheel as an input control device 116. A user may navigate among and interact with one or more graphical objects (henceforth referred to as icons) displayed in the touch screen 112 by rotating the click wheel or by moving a point of contact with the click wheel (e.g., where the amount of movement of the point of contact is measured by its angular displacement with respect to a center point of the click wheel). The click wheel may also be used to select one or more of the displayed icons. For example, the user may press down on at least a portion of the click wheel or an associated button. User commands and navigation commands provided by the user via the click wheel may be processed by an input controller 160 as well as one or more of the modules and/or sets of instructions in memory 102. For a virtual click wheel, the click wheel and click wheel controller may be part of the touch screen 112 and the display controller 156, respectively. For a virtual click wheel, the click wheel may be either an opaque or semitransparent object that appears and disappears on the touch screen display in response to user interaction with the device. In some embodiments, a virtual click wheel is displayed on the touch screen of a portable multifunction device and operated by user contact with the touch screen.
The device 100 also includes a power system 162 for powering the various components. The 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.
The device 100 may also include one or more optical sensors 164.
The device 100 may also include one or more proximity sensors 166.
The device 100 may also include one or more accelerometers 168.
In some embodiments, the software components stored in memory 102 may include an operating system 126, a communication module (or set of instructions) 128, a contact/motion module (or set of instructions) 130, a graphics module (or set of instructions) 132, a text input module (or set of instructions) 134, a Global Positioning System (GPS) module (or set of instructions) 135, and applications (or set of instructions) 136.
The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, 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.
The 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 the RF circuitry 108 and/or the external port 124. The 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 Computer, Inc.) devices.
The contact/motion module 130 may detect contact with the touch screen 112 (in conjunction with the display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). The contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred, determining if there is movement of the contact and tracking the movement across the touch screen 112, and determining if the contact has been broken (i.e., if the contact has ceased). Determining movement of the point of contact may include 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 may be applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, the contact/motion module 130 and the display controller 156 also detects contact on a touchpad. In some embodiments, the contact/motion module 130 and the controller 160 detects contact on a click wheel.
The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112, including components for changing the intensity 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.
The 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, email 140, IM 141, blogging 142, browser 147, and any other application that needs text input).
The 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 and/or blogger 142 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
The applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:
Examples of other applications 136 that may be stored in memory 102 include other word processing applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in the address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation with another party or with multiple parties (i.e., a conference call) 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. Embodiments of user interfaces and associated processes using telephone module 138 are described further below.
Each of the above identified modules and applications correspond to a set of instructions for performing one or more functions described above. These modules (i.e., 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 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152,
In some embodiments, the device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen 112 and/or a touchpad. By using a touch screen and/or a touchpad as the primary input/control device for operation of the device 100, the number of physical input/control devices (such as push buttons, dials, and the like) on the device 100 may be reduced.
The predefined set of functions that may be performed exclusively through a touch screen and/or a touchpad include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main, home, or root menu from any user interface that may be displayed on the device 100. In such embodiments, the touchpad may be referred to as a “menu button.” In some other embodiments, the menu button may be a physical push button or other physical input/control device instead of a touchpad.
The device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, the menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI in touch screen 112.
In one embodiment, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, a Subscriber Identity Module (SIM) card slot 210, a head set jack 212, and a docking/charging external port 124. The push button 206 may be 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, the device 100 also may accept verbal input for activation or deactivation of some functions through the microphone 113.
Attention is now directed towards embodiments of user interfaces (“UI”) and associated processes that may be implemented on a portable multifunction device 100.
In some embodiments, the device detects contact with the touch-sensitive display (e.g., a user's finger making contact on or near the unlock image 302) while the device is in a user-interface lock state. The device moves the unlock image 302 in accordance with the contact. The device transitions to a user-interface unlock state if the detected contact corresponds to a predefined gesture, such as moving the unlock image across channel 306. Conversely, the device maintains the user-interface lock state if the detected contact does not correspond to the predefined gesture. As noted above, processes that use gestures on the touch screen to unlock the device are 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, and Ser. No. 11/322,550, “Indication Of Progress Towards Satisfaction Of A User Input Condition,” filed Dec. 23, 2005, which are hereby incorporated by reference herein in their entirety.
In some embodiments, user interface 400B includes the following elements, or a subset or superset thereof:
In some embodiments, UI 400A or 400B displays all of the available applications 136 on one screen so that there is no need to scroll through a list of applications (e.g., via a scroll bar). In some embodiments, as the number of applications increase, the icons corresponding to the applications may decrease in size so that all applications may be displayed on a single screen without scrolling. In some embodiments, having all applications on one screen and a menu button enables a user to access any desired application with at most two inputs, such as activating the menu button 204 and then activating the desired application (e.g., by a tap or other finger gesture on the icon corresponding to the application).
In some embodiments, UI 400A or 400B provides integrated access to both widget-based applications and non-widget-based applications. In some embodiments, all of the widgets, whether user-created or not, are displayed in UI 400A or 400B. In other embodiments, activating the icon for user-created widget 149-6 may lead to another UI that contains the user-created widgets or icons corresponding to the user-created widgets.
In some embodiments, a user may rearrange the icons in UI 400A or 400B, e.g., using processes described in U.S. patent application Ser. No. 11/459,602, “Portable Electronic Device With Interface Reconfiguration Mode,” filed Jul. 24, 2006, which is hereby incorporated by reference herein in its entirety. For example, a user may move application icons in and out of tray 408 using finger gestures.
In some embodiments, UI 400A or 400B includes a gauge (not shown) that displays an updated account usage metric for an account associated with usage of the device (e.g., a cellular phone account), as described in U.S. patent application Ser. No. 11/322,552, “Account Information Display For Portable Communication Device,” filed Dec. 23, 2005, which is hereby incorporated by reference herein in its entirety.
In the discussion of
In some embodiments, a respective information item associated with a telephone call or conference call includes both a call descriptor (e.g., a name of the other party to the call, a telephone number, or a label such as “conference”) and a call status indicator, such as a call duration value (e.g., “00:05”) or call status (e.g., “Hold” or “On Hold”). However, in some embodiments or some interfaces, a respective information item may include the descriptor, or the status indicator, but not both.
In some embodiments, the device performs location-based dialing, which simplifies dialing when the user is located outside his/her home country and/or is trying to dial a destination number outside his/her home country.
Additional description of location-based dialing can be found in U.S. Patent Application No. 60/883,800, “Method, Device, And Graphical User Interface For Location-Based Dialing,” filed Jan. 7, 2007, the content of which is hereby incorporated by reference herein in its entirety.
In some embodiments, a user of the device 100 may want to create a conference call that involves the user and at least two other parties. For ease of discussion, assume that the user initiates a call with a second party. After the second party associated with the user-entered phone number answers the phone call, a connection is made between the user and the second party and the two sides can have a conversation. Then, assume the device 100 receives an incoming call from a first party.
While the phone call between the user and the second party is active, the device 100 receives a new incoming call from a first party (502). To alert the user of the incoming call, the device 100 replaces the phone call user interface with an incoming phone call user interface (503). Note that the user interface change does not suspend or terminate the ongoing phone call between the user and the second party. An exemplary incoming phone call user interface 3000C is shown in
To determine which, if any, icon is selected by the user and therefore what operations to perform, the device 100 monitors the next user contact with the touch screen display (504). For example, a finger tap or other predefined gesture on the “ignore” icon (506) indicates that the user chooses to continue the phone call with the second party and not to answer the incoming call.
In some embodiments, the device 100 detects the user's finger tap or other predefined gesture on the “end call+answer” icon (514), suggesting that the user chooses to terminate the phone call with the second party and answer the incoming call from the first party.
In some embodiments, the user may choose to answer the incoming call after temporarily suspending (but not completely terminating) the phone call with the second party by selecting the “hold call+answer” icon (510). After conversing with the first party, the user may merge the two separate phone calls—the active call with the first party and the suspended call with the second party—into a conference call so that the three parties can talk with each other simultaneously.
After talking with the first party while the second party is on hold, the user may decide to get the second party involved in a conference call by a tap or other gesture on the merge call icon. In response, the device 100 merges the two phone calls into a three-party conference call (808). A conference call user interface is displayed on the touch screen display (810) and the device 100 monitors the next user contact with the touch screen display (812). In some embodiments, the conference call user interface includes: a third informational item (e.g., 3042,
In some embodiments, in addition to merging separate calls (which may include a conference call) into a new conference call, the user may also be able to remove a party from the conference call or temporarily convert the conference call into a private call with a particular party by selecting a conference call management icon and using a conference call management user interface.
The device 100 monitors the next user contact with the touch screen display (904). For example, in response to a user selection of the end call icon associated with the first party, the device 100 drops the first party from the conference call (905) and the corresponding entry from the conference call management user interface (906). Note that the device 100 may perform the two operations 905 and 906 in a different order. In some embodiments, the device first displays a confirmation icon on the touch screen display in response to the user selection of the end call icon associated with the first party and then removes the first party and the corresponding management entry from the conference call management user interface after a user selection of the confirmation icon. If the user, the first party, and the second party were the only participants in the conference call, the conference call becomes a private phone call between the user and the second party. The device then monitors the next user contact with the touch screen display (912). In some embodiments, the device 100 also replaces the conference call user interface with the phone call user interface 3000B.
In some embodiments, upon detecting a user selection of the private call icon of the management entry associated with the second party, the device 100 suspends the conference call and replaces it with a private call between the user and the second party (908). The conference call management user interface is replaced with a phone call user interface that has a merge call icon (910). In some embodiments, the phone call user interface includes a fourth informational item associated with the suspended phone call between the user and the first party, a fifth informational item associated with the active phone call between the user and the second party, and a merge call icon. An exemplary user interface 3000J is shown in
As noted above, the user selection of a private call icon merely suspends the conference call. The user can resume the conference call by hitting the merge call icon.
As noted above, a conference call may be formed by merging an existing phone call with an incoming call or an outgoing call. The existing call itself may be a phone call between two individual parties or a conference call among three or more parties.
The user may choose to add a new party to an existing conference call by selecting the add call icon (e.g., 3018,
If the user-selected party answers the call, the device 100 replaces the initiate outgoing call user interface with a new phone call user interface (1108). The new phone call user interface includes: an informational item associated with the suspended conference call, another informational item representing the new outgoing call, and a merge call icon. The device 100 merges the two phone calls into a new conference call in response to a user selection of the merge call icon (1110) and monitors the next user contact with the touch screen display (1112).
In some embodiments, in response to a tap or other predefined user gesture, the device may: mute the call (e.g., if the gesture is applied to icon 3006); place the call on hold (e.g., if the gesture is applied to icon 3008); swap between two calls, placing one call on hold to continue the other call (e.g., if the gesture is applied to icon 3009); place the call on a speaker (e.g., if the gesture is applied to icon 3010); add a call (e.g., if the gesture is applied to icon 3018); display a numeric keypad for number entry (e.g., if the gesture is applied to icon 3016, UI 3000N in
In some embodiments, if the device receives an incoming call while the user is on another call (e.g., with someone at (650) 132-2234 in
In this example, in response to activation of the end+answer icon 3030 (e.g., by a finger tap on the icon), the call with (650) 132-2234 is ended, the call from Arlene Bascom is answered, and phone call UI 3000D (
In this example, in response to activation of the hold+answer icon 3028 (e.g., by a finger tap on the icon), the call with (650) 132-2234 is put on hold, the call from Arlene Bascom is answered, and phone call UI 3000E (
In some embodiments, if the merge icon 3038 (
In some embodiments, in response to activation of the conference call management icon 3044 (e.g., by a finger tap 3046 on the icon), a conference call management UI is displayed (e.g., UI 3000H,
In some embodiments, in response to activation of the private call icon 3056 (e.g., by a finger tap 3058 on the icon), the conference call is suspended and a phone call UI is displayed (e.g., UI 3000J,
If an incoming call is not from a caller known to the user (e.g. the phone number is not in the user's contact list), then an incoming call UI such as UI 3000K (
In some embodiments, in response to activation of the add call icon 3018 (e.g., by a finger tap on the icon in
In some embodiments, in response to activation of the keypad icon 3016 (e.g., by a finger tap on the icon), a keypad UI for entering digits during a call is displayed (e.g., UI 3000N,
Creating a Conference Call from Two Existing Calls
In some embodiments, the device 100 displays a phone call user interface (e.g., UI 3000E,
Upon detecting a user selection of the merge call icon, (1) the active phone call and the suspended phone call are merged into a conference call between the user, the first party, and the second party; and (2) the phone call user interface is replaced with a conference call user interface (e.g., UI 3000G,
Managing a Conference Call
In some embodiments, upon detecting a user selection (e.g., gesture 3046) of the conference call management icon 3044, the conference call user interface (e.g., UI 3000G) is replaced with a conference call management user interface (e.g., UI 3000H,
In some embodiments, upon detecting a user selection (e.g., gesture 3052) of the end call icon in the first management entry, a confirmation icon (e.g., 3062,
In some embodiments, upon detecting a user selection (e.g., gesture 3058) of the private call icon in the second management entry, the conference call is suspended and the conference call management user interface is replaced with the phone call user interface (e.g., UI 3000J,
In some embodiments, the conference call is resumed upon detecting a second user selection of the merge call icon; and the phone call user interface (e.g., UI 3000J,
Receive an Incoming Call During a Conference Call
In some embodiments, upon detecting an incoming phone call from a third party, the conference call user interface or the conference call management user interface (i.e., whichever interface is being displayed when the incoming call is detected) is replaced with an incoming phone call user interface (e.g., UI 3000C,
In some embodiments, upon detecting a user selection of the ignore incoming phone call icon (e.g., 3026), the incoming phone call from the third party is terminated or sent to voice mail; the conference call with the first and second parties is continued; and the incoming phone call user interface is replaced with the conference call user interface or the conference call management user interface (i.e., whichever interface was being displayed when the incoming call was detected).
In some embodiments, upon detecting a user selection of the end current phone call and answer incoming phone call icon (e.g., 3030), the conference call with the first and second parties is terminated; a phone call between the user and the third party is activated; and the incoming phone call user interface is replaced with a phone call user interface (e.g., UI 3000L,
In some embodiments, upon detecting a user selection of the suspend current phone call and answer incoming phone call icon (e.g., 3028), the conference call with the first and second parties is suspended; a phone call between the user and the third party is activated; and the incoming phone call user interface is replaced with a phone call user interface (e.g., UI 3000M,
In some embodiments, upon detecting a user selection of the suspend current phone call and answer incoming phone call icon, a phone call between the user and the third party is activated and the incoming phone call user interface is replaced with a phone call user interface (e.g., UI 3000M,
Adding a Caller During a Conference Call
In some embodiments, the conference call user interface includes an add caller icon (e.g., 3018,
An outgoing phone call is initiated to a third party using a phone number from an entry in the contact list or a phone number input by a user (e.g., using dial pad 2902,
Upon detecting an acceptance of the outgoing phone call, a phone call user interface is displayed (e.g., UI 3000M,
Upon detecting a user selection of the merge call icon, (1) the outgoing phone call between the user and the third party and the suspended conference call are merged into a conference call between the user, the first party, the second party, and the third party; and (2) the phone call user interface is replaced with a conference call user interface (e.g., UI 3000G,
Thus, as explained above, transparent and intuitive user interfaces for managing conference calls on a portable multifunction device with a touch screen display are provided. The disclosed user interfaces greatly simplify such tasks as adding a new party to a conference call, removing an existing party from a conference call, temporarily converting a conference call into a private phone call with one of the existing parties, and returning to a conference call from a private phone call.
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 utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated.
This application is a continuation of U.S. patent application Ser. No. 17/306,236, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed May 3, 2021, which is a continuation of U.S. patent application Ser. No. 16/434,794, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Jun. 7, 2019, which is a continuation of U.S. patent application Ser. No. 15/620,662, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Jun. 12, 2017, now U.S. Pat. No. 10,320,987, which is a continuation of U.S. patent application Ser. No. 15/137,127, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Apr. 25, 2016, now U.S. Pat. No. 9,706,054, which is a continuation of U.S. patent application Ser. No. 14/632,817, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Feb. 26, 2015, now U.S. Pat. No. 9,325,852, which is a continuation of U.S. patent application Ser. No. 13/176,703, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Jul. 5, 2011, now U.S. Pat. No. 8,972,904, which is a continuation of U.S. application Ser. No. 11/960,673, filed Jan. 7, 2007, now U.S. Pat. No. 7,975,242, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling” which claims priority to U.S. Provisional Patent Application Nos. 60/937,993, “Portable Multifunction Device,” filed Jun. 29, 2007; 60/947,133, “Portable Multifunction Device, Method, and Graphical User Interface for Conference Calling,” filed Jun. 29, 2007; 60/879,469, “Portable Multifunction Device,” filed Jan. 8, 2007; and 60/879,253, “Portable Multifunction Device,” filed Jan. 7, 2007. All of these applications are incorporated by reference herein in their entirety. This application is related to the following applications: (1) U.S. application Ser. No. 10/188,182, “Touch Pad For Handheld Device,” filed Jul. 1, 2002; (2) U.S. application Ser. No. 10/722,948, “Touch Pad For Handheld Device,” filed Nov. 25, 2003; (3) U.S. application Ser. No. 10/643,256, “Movable Touch Pad With Added Functionality,” filed Aug. 18, 2003; (4) U.S. application Ser. No. 10/654,108, “Ambidextrous Mouse,” filed Sep. 2, 2003; (5) U.S. application Ser. No. 10/840,862, “Multipoint Touchscreen,” filed May 6, 2004; (6) U.S. application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30, 2004; (7) U.S. application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices” filed Jan. 18, 2005; (8) U.S. patent application Ser. No. 11/057,050, “Display Actuator,” filed Feb. 11, 2005; (9) U.S. Provisional Application No. 60/658,777, “Multi-Functional Hand-Held Device,” filed Mar. 4, 2005; (10) U.S. application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006; and (11) U.S. Provisional Application No. 60/824,769, “Portable Multifunction Device,” filed Sep. 6, 2006. All of these applications are incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4686332 | Greanias et al. | Aug 1987 | A |
| 5619555 | Fenton et al. | Apr 1997 | A |
| 5627567 | Davidson | May 1997 | A |
| 5627978 | Altom et al. | May 1997 | A |
| 5633912 | Tsoi | May 1997 | A |
| 5644628 | Schwarzer et al. | Jul 1997 | A |
| 5701340 | Zwick | Dec 1997 | A |
| 5867150 | Bricklin et al. | Feb 1999 | A |
| 6026158 | Bayless et al. | Feb 2000 | A |
| 6047054 | Bayless et al. | Apr 2000 | A |
| 6070068 | Sudo | May 2000 | A |
| 6088696 | Moon et al. | Jul 2000 | A |
| 6094197 | Buxton et al. | Jul 2000 | A |
| 6236854 | Bradshaw, Jr. | May 2001 | B1 |
| 6259436 | Moon et al. | Jul 2001 | B1 |
| 6269159 | Cannon et al. | Jul 2001 | B1 |
| 6298045 | Pang et al. | Oct 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6392999 | Liu et al. | May 2002 | B1 |
| 6396531 | Gerszberg et al. | May 2002 | B1 |
| 6424711 | Bayless | Jul 2002 | B1 |
| 6430284 | Jones | Aug 2002 | B1 |
| 6430405 | Jambhekar et al. | Aug 2002 | B1 |
| 6448988 | Haitani et al. | Sep 2002 | B1 |
| 6505040 | Kim | Jan 2003 | B1 |
| 6516202 | Hawkins et al. | Feb 2003 | B1 |
| 6526274 | Fickes et al. | Feb 2003 | B1 |
| 6535730 | Chow et al. | Mar 2003 | B1 |
| 6542591 | Amro et al. | Apr 2003 | B1 |
| 6549612 | Gifford et al. | Apr 2003 | B2 |
| 6570557 | Westerman et al. | May 2003 | B1 |
| 6577721 | Vainio et al. | Jun 2003 | B1 |
| 6583806 | Ludwig et al. | Jun 2003 | B2 |
| 6593949 | Chew et al. | Jul 2003 | B1 |
| 6677932 | Westerman | Jan 2004 | B1 |
| 6738461 | Trandal et al. | May 2004 | B2 |
| 6763388 | Tsimelzon | Jul 2004 | B1 |
| 6768722 | Katseff et al. | Jul 2004 | B1 |
| 6772188 | Cloutier | Aug 2004 | B1 |
| 6792082 | Levine | Sep 2004 | B1 |
| 6839417 | Weisman et al. | Jan 2005 | B2 |
| 6879691 | Koretz | Apr 2005 | B1 |
| 6961420 | Desalvo | Nov 2005 | B2 |
| 7007239 | Hawkins et al. | Feb 2006 | B1 |
| 7031728 | Beyer, Jr. | Apr 2006 | B2 |
| 7046230 | Zadesky et al. | May 2006 | B2 |
| 7050557 | Creamer et al. | May 2006 | B2 |
| 7117445 | Berger | Oct 2006 | B2 |
| 7184428 | Gerszberg et al. | Feb 2007 | B1 |
| 7185058 | Blackwell et al. | Feb 2007 | B2 |
| 7212808 | Engstrom et al. | May 2007 | B2 |
| 7221748 | Moore et al. | May 2007 | B1 |
| 7225409 | Schnarel et al. | May 2007 | B1 |
| 7231208 | Robertson et al. | Jun 2007 | B2 |
| 7231229 | Hawkins et al. | Jun 2007 | B1 |
| 7251479 | Holder et al. | Jul 2007 | B2 |
| 7280652 | Booking et al. | Oct 2007 | B2 |
| 7280850 | Hama et al. | Oct 2007 | B2 |
| 7289614 | Twerdahl | Oct 2007 | B1 |
| 7295852 | Davis et al. | Nov 2007 | B1 |
| 7403767 | Kashanian et al. | Jul 2008 | B2 |
| 7409050 | Li et al. | Aug 2008 | B1 |
| 7479949 | Jobs et al. | Jan 2009 | B2 |
| 7493567 | Ollis et al. | Feb 2009 | B2 |
| 7495659 | Marriott et al. | Feb 2009 | B2 |
| 7499040 | Zadesky et al. | Mar 2009 | B2 |
| 7502633 | Engstrom et al. | Mar 2009 | B2 |
| 7509588 | Van Os et al. | Mar 2009 | B2 |
| 7526306 | Brems et al. | Apr 2009 | B2 |
| 7606598 | Kuhl et al. | Oct 2009 | B2 |
| 7614008 | Ording | Nov 2009 | B2 |
| 7623643 | Raghav et al. | Nov 2009 | B2 |
| 7650137 | Jobs et al. | Jan 2010 | B2 |
| 7653883 | Hotelling et al. | Jan 2010 | B2 |
| 7657849 | Chaudhri et al. | Feb 2010 | B2 |
| 7663607 | Hotelling et al. | Feb 2010 | B2 |
| 7664485 | Twerdahl et al. | Feb 2010 | B2 |
| 7680513 | Haitani et al. | Mar 2010 | B2 |
| 7685530 | Sherrard et al. | Mar 2010 | B2 |
| 7694231 | Kocienda et al. | Apr 2010 | B2 |
| 7715535 | Veen et al. | May 2010 | B2 |
| 7720218 | Abramson et al. | May 2010 | B2 |
| 7724887 | Jennings et al. | May 2010 | B2 |
| 7778399 | Ambrose | Aug 2010 | B2 |
| 7778671 | Roykkee et al. | Aug 2010 | B2 |
| 7779630 | Sakamoto | Aug 2010 | B2 |
| 7783283 | Kuusinen et al. | Aug 2010 | B2 |
| 7808479 | Hotelling et al. | Oct 2010 | B1 |
| 7812817 | Robertson et al. | Oct 2010 | B2 |
| 7839987 | Kirchhoff et al. | Nov 2010 | B1 |
| 7844914 | Andre et al. | Nov 2010 | B2 |
| 7894597 | Walker et al. | Feb 2011 | B2 |
| 7920886 | Lai et al. | Apr 2011 | B1 |
| 7975242 | Forstall et al. | Jul 2011 | B2 |
| 7991432 | Silverbrook et al. | Aug 2011 | B2 |
| 8001120 | Todd et al. | Aug 2011 | B2 |
| 8014760 | Forstall | Sep 2011 | B2 |
| 8019388 | Chiam et al. | Sep 2011 | B2 |
| 8064886 | Hawkins et al. | Nov 2011 | B2 |
| 8090087 | Jobs et al. | Jan 2012 | B2 |
| 8095879 | Goertz | Jan 2012 | B2 |
| 8126120 | Ward et al. | Feb 2012 | B2 |
| 8135389 | Forstall et al. | Mar 2012 | B2 |
| 8175656 | Beith | May 2012 | B2 |
| 8255003 | Forstall et al. | Aug 2012 | B2 |
| 8255033 | Petisce et al. | Aug 2012 | B2 |
| 8452342 | Forstall et al. | May 2013 | B2 |
| 8972904 | Forstall et al. | Mar 2015 | B2 |
| 9325852 | Forstall et al. | Apr 2016 | B2 |
| 9706054 | Forstall et al. | Jul 2017 | B2 |
| 10320987 | Forstall et al. | Jun 2019 | B2 |
| 20010049283 | Thomas | Dec 2001 | A1 |
| 20020015024 | Westerman et al. | Feb 2002 | A1 |
| 20020045438 | Tagawa et al. | Apr 2002 | A1 |
| 20020073207 | Widger et al. | Jun 2002 | A1 |
| 20020076015 | Norwitz et al. | Jun 2002 | A1 |
| 20020077158 | Scott | Jun 2002 | A1 |
| 20020084991 | Harrison et al. | Jul 2002 | A1 |
| 20020093531 | Barile | Jul 2002 | A1 |
| 20020111991 | Wood et al. | Aug 2002 | A1 |
| 20020116464 | Mak | Aug 2002 | A1 |
| 20020128036 | Yach et al. | Sep 2002 | A1 |
| 20030073430 | Robertson et al. | Apr 2003 | A1 |
| 20030138080 | Nelson et al. | Jul 2003 | A1 |
| 20030142138 | Brown et al. | Jul 2003 | A1 |
| 20030142200 | Canova, Jr. et al. | Jul 2003 | A1 |
| 20030198329 | Mcgee | Oct 2003 | A1 |
| 20040047461 | Weisman et al. | Mar 2004 | A1 |
| 20040137955 | Engstrom et al. | Jul 2004 | A1 |
| 20040203674 | Shi et al. | Oct 2004 | A1 |
| 20040235520 | Cadiz et al. | Nov 2004 | A1 |
| 20040267887 | Berger et al. | Dec 2004 | A1 |
| 20050015495 | Florkey et al. | Jan 2005 | A1 |
| 20050032527 | Sheha et al. | Feb 2005 | A1 |
| 20050047562 | Holz et al. | Mar 2005 | A1 |
| 20050048958 | Mousseau et al. | Mar 2005 | A1 |
| 20050052427 | Wu et al. | Mar 2005 | A1 |
| 20050074107 | Renner et al. | Apr 2005 | A1 |
| 20050074109 | Hanson et al. | Apr 2005 | A1 |
| 20050078613 | Covell et al. | Apr 2005 | A1 |
| 20050085274 | Lee et al. | Apr 2005 | A1 |
| 20050094792 | Berthoud et al. | May 2005 | A1 |
| 20050101308 | Lee | May 2005 | A1 |
| 20050123116 | Gau | Jun 2005 | A1 |
| 20050141686 | Matsunaga et al. | Jun 2005 | A1 |
| 20050157174 | Kitamura et al. | Jul 2005 | A1 |
| 20050182798 | Todd et al. | Aug 2005 | A1 |
| 20050250483 | Malik | Nov 2005 | A1 |
| 20050286693 | Brown et al. | Dec 2005 | A1 |
| 20060002536 | Ambrose | Jan 2006 | A1 |
| 20060010395 | Aaltonen | Jan 2006 | A1 |
| 20060015819 | Hawkins et al. | Jan 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060026535 | Hotelling et al. | Feb 2006 | A1 |
| 20060026536 | Hotelling et al. | Feb 2006 | A1 |
| 20060030369 | Yang | Feb 2006 | A1 |
| 20060033724 | Chaudhri et al. | Feb 2006 | A1 |
| 20060035632 | Sorvari et al. | Feb 2006 | A1 |
| 20060063539 | Beyer | Mar 2006 | A1 |
| 20060121925 | Jung | Jun 2006 | A1 |
| 20060121939 | Anwar et al. | Jun 2006 | A1 |
| 20060132595 | Kenoyer et al. | Jun 2006 | A1 |
| 20060135197 | Jin et al. | Jun 2006 | A1 |
| 20060140189 | Wu et al. | Jun 2006 | A1 |
| 20060154658 | Holder et al. | Jul 2006 | A1 |
| 20060161870 | Hotelling et al. | Jul 2006 | A1 |
| 20060168539 | Hawkins et al. | Jul 2006 | A1 |
| 20060178137 | Loveland | Aug 2006 | A1 |
| 20060181517 | Zadesky et al. | Aug 2006 | A1 |
| 20060190833 | Sangiovanni et al. | Aug 2006 | A1 |
| 20060197753 | Hotelling | Sep 2006 | A1 |
| 20060199612 | Beyer et al. | Sep 2006 | A1 |
| 20060205432 | Hawkins et al. | Sep 2006 | A1 |
| 20060222168 | Curley et al. | Oct 2006 | A1 |
| 20060229107 | Cho et al. | Oct 2006 | A1 |
| 20060264205 | Gibbs | Nov 2006 | A1 |
| 20060274051 | Longe et al. | Dec 2006 | A1 |
| 20060281449 | Kun et al. | Dec 2006 | A1 |
| 20070071186 | Sahasrabudhe et al. | Mar 2007 | A1 |
| 20070082697 | Bumiller et al. | Apr 2007 | A1 |
| 20070083600 | Bakos et al. | Apr 2007 | A1 |
| 20070091830 | Coulas et al. | Apr 2007 | A1 |
| 20070092072 | Jacobs | Apr 2007 | A1 |
| 20070111743 | Leigh et al. | May 2007 | A1 |
| 20070115919 | Chahal et al. | May 2007 | A1 |
| 20070116226 | Bennett et al. | May 2007 | A1 |
| 20070117508 | Jachner | May 2007 | A1 |
| 20070123239 | Leigh et al. | May 2007 | A1 |
| 20070123320 | Han et al. | May 2007 | A1 |
| 20070133771 | Stifelman et al. | Jun 2007 | A1 |
| 20070149188 | Miyashita | Jun 2007 | A1 |
| 20070150830 | Ording et al. | Jun 2007 | A1 |
| 20070152980 | Kocienda et al. | Jul 2007 | A1 |
| 20070152984 | Ording et al. | Jul 2007 | A1 |
| 20070155434 | Jobs et al. | Jul 2007 | A1 |
| 20070243858 | Marathe et al. | Oct 2007 | A1 |
| 20070257890 | Hotelling et al. | Nov 2007 | A1 |
| 20070280457 | Aberethy et al. | Dec 2007 | A1 |
| 20080055263 | Lemay et al. | Mar 2008 | A1 |
| 20080168361 | Forstall et al. | Jul 2008 | A1 |
| 20080168384 | Platzer et al. | Jul 2008 | A1 |
| 20080295017 | Tseng et al. | Nov 2008 | A1 |
| 20090280868 | Hawkins et al. | Nov 2009 | A1 |
| 20100273466 | Robertson et al. | Oct 2010 | A1 |
| 20100283743 | Coddington | Nov 2010 | A1 |
| 20140011485 | Forstall et al. | Jan 2014 | A1 |
| 20170085716 | Forstall et al. | Mar 2017 | A1 |
| 20170279967 | Forstall et al. | Sep 2017 | A1 |
| 20190394336 | Forstall et al. | Dec 2019 | A1 |
| 20210321003 | Forstall et al. | Oct 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 1444380 | Sep 2003 | CN |
| 19983569 | Oct 2001 | DE |
| 0804009 | Oct 1997 | EP |
| 0859498 | Aug 1998 | EP |
| 1069791 | Jan 2001 | EP |
| 1365564 | Nov 2003 | EP |
| 1621983 | Feb 2006 | EP |
| 1635543 | Mar 2006 | EP |
| 1763243 | Mar 2007 | EP |
| 2338141 | Dec 1999 | GB |
| 9708879 | Mar 1997 | WO |
| 9830002 | Jul 1998 | WO |
| 9848551 | Oct 1998 | WO |
| 9916181 | Apr 1999 | WO |
| 0016186 | Mar 2000 | WO |
| 0038042 | Jun 2000 | WO |
| 0232088 | Apr 2002 | WO |
| 03060622 | Jul 2003 | WO |
| 2004031902 | Apr 2004 | WO |
| 2005010738 | Feb 2005 | WO |
| 2005025081 | Mar 2005 | WO |
| 2005053279 | Jun 2005 | WO |
| 2006070228 | Jul 2006 | WO |
| 2006134473 | Dec 2006 | WO |
| Entry |
|---|
| Advisory Action received for U.S. Appl. No. 11/769,694, dated Feb. 23, 2011, 3 pages. |
| Agilent Technologies Inc., “Agilent Unveils Optical Proximity Sensor for Mobile Appliances”, available at: <http:/www.embeddedstar.com/press/content/2004/8/embedded16015.html>, Aug. 31, 2004, 2 pages. |
| Alejandre, Suzanne, “Graphing Linear Equations”, Available at: <http://mathforum.org/alejandre/palm/times.palm.html>, retrieved on Jun. 12, 2006, 2006, 3 pages. |
| Alltel, “My Account”, http://alltel.com/personal/cs/my_account.html, Dec. 1, 2005, 1 page. |
| Andrew's Widgets, “Developing Dashboard Widgets—A Brief Introduction to Building Widgets for Apple's Dashboard Environment”, Available online at: <http://andrew.hedges.name/widgets/dev/>, Retrieved on Mar. 13, 2015, 6 pages. |
| Aoki et al., “Tap Tips: Lightweight Discovery of Touchscreen Targets”, Xerox Palo Alto Research Center, Jan. 2001, 2 pages. |
| Apple Inc. vs. Samsung Electronics Co. Ltd et al., “Judgment in Interlocutory proceeding, Case No. 396957/KG ZA 11-730, civil law sector”, Aug. 24, 2011, pp. 1-65. |
| Apple Inc. vs. Samsung Electronics Co. Ltd et al., “Samsung's Motion to Supplement Invalidity Contentions, Case No. 11-cv-01846-LHK, filed Jan. 27, 2012, together with Exhibit 6”, Jan. 27, 2012, 47 pages. |
| Apple Inc. vs. Samsung Electronics Co. Ltd et al., “Samsung's Patent Local Rule 3-3 and 3-4 Disclosures, Case No. 11-cv-01846-LHK, dated Oct. 7, 2011, together with Exhibits G-1 through G-7 and Exhibit H”, Oct. 7, 2011, 287 pages. |
| Apple.com, “Tiger Developer Overview Series—Developing Dashboard Widgets”, Available online at: <http://developer.apple.com/macosx/dashboard.html>, Jun. 26, 2006, 9 pages. |
| Applicant-Initiated interview Summary received for U.S. Appl. No. 16/434,794, dated Sep. 11, 2020, 3 pages. |
| Atis, “Numbering and Dialing Plan within the United States”, Copyright © 2008 by Alliance for Telecommunications Industry Solutions, 2008, 17 pages. |
| Cadiz et al., “Exploring PC-Telephone Convergence with the Enhanced Telephony Prototype”, CHI, vol. 6, No. 1, Apr. 24-29, 2004, pp. 215-222. |
| Certification received for Australian Patent Application No. 2012100821, dated Jul. 6, 2012, 2 pages. |
| Chen et al., “A Novel Navigation and Transmission Technique for Mobile Handheld Devices”, Technical Report CSE-2003-1, Department of Computer Science, University of California at Davis, 2003, 8 pages. |
| Chen et al., “Detecting Web Pages Structure for Adaptive Viewing on Small Form Factor Devices”, Proceedings of the 12th international conference on World Wide Web, 2003, 9 pages. |
| Cibenix, “RIS Wireless Company Profile”, http://72.14.203.104/search/q=cache:N2vLplKG3SQJ:ris.com/directo, Nov. 29, 2005, 3 pages. |
| Cingular, “International Roaming Guide-Personal Experiences(s) from Customer and Community Member”, Cingular Customer Forums, printed Jun. 26, 2006, 6 pages. |
| Corrected Notice of Allowance received for U.S. Appl. No. 16/434,794, dated Feb. 8, 2021, 3 pages. |
| Cross-Browser.com, “CrossBrowser.com: Fixed Table Headers”, http://web.archive.org/web/20061205082655/http://cross-browser.com/x/examples/fixed_table_headers.html, Dec. 5, 2006, 3 pages. |
| Day B., “Will Cell Phones Render iPods Obsolete?”, available at <http://weblogs.iavanet/pub/wig/883>, Dec. 12, 2005, 3 pages. |
| Decision to Grant received for European Patent Application No. 07844104.5, dated Oct. 25, 2018, 2 pages. |
| Decision to Refuse Application, received for the European Patent Application No. 07841759.9, dated Dec. 8, 2011, 3 pages. |
| DIALDTMF,“A Pocket PC (Pocket Contact) plugin to Dial Telephone Numbers Using DTMF's (aka Dual Tone Multi-Frequency)”, http://dialdtmf.sourceforge.net, printed Jan. 10, 2009, 9 pages. |
| Dietz et al., “DiamondTouch: A Multi-User Touch Technology”, Proceedings of the 14th Annual ACM Symposium on User Interface Software and Technology, Nov. 11-14, 2001, pp. 219-226. |
| “Education & Training, Help Index”, Connecticut Education & Training, printed Dec. 31, 2007, 12 pages. |
| “Electric Potential”, http://en.wikipedia.org/wiki/Electrical_potential, printed Dec. 28, 2007, 5 pages. |
| Electrostatic Potential, “Scalar Potential versus Vector Field”, http://www.phy.duke.edu/˜rgb/Class/phy42/node10.html, printed Apr. 19, 2006, 2 pages. |
| Eloy J. C., “Status of the Mems Industry”, presentation of Yole Développement, © 2004, 19 pages. |
| Engst, Adam C., “SoundJam Keeps on Jammin'”, available at: <http://db.tidbits.com/getbits.acgi?tbart=05988>, Jun. 19, 2000, 3 pages. |
| Esato, “A Couple of My Mates. Meet JasJar and K-Jam (Many Pics)”, available at: <http://www.esato.com/archive/t.php/t-106524>, retrieved on Apr. 13, 2006, 90 pages. |
| Extended European Search Report received for European Patent Application No. 11176480.9, dated Oct. 14, 2011, 9 pages. |
| Extended European Search Report received for European Patent Application No. 18192595.9, dated Dec. 19, 2018, 7 pages. |
| Eyemodule, “Turn Your Handspring™ Handheld into a Digital Camera”, User's Manual, www.eyemodule.com, 2000, 9 pages. |
| “Fastap Keypads Redefine Mobile Phones”, DigitWireless, available at: <http://www.digitwireless.com>, retrieved on Nov. 18, 2005, 10 pages. |
| “Fastap”, DigitWireless, available at: <http://www.digitwireless.com/about/faq.html>, Dec. 6, 2005, 5 pages. |
| Final Office Action received for U.S. Appl. No. 11/769,694, dated Oct. 14, 2010, 12 pages. |
| Final Office Action received for U.S. Appl. No. 11/769,695, dated Jan. 21, 2011, 16 pages. |
| Final Office Action received for U.S. Appl. No. 13/903,962 dated Jul. 8, 2014, 8 pages. |
| Final Office Action received for U.S. Appl. No. 90/012,893, dated Apr. 24, 2014, 118 pages. |
| Final Office Action received for U.S. Appl. No. 13/903,962, dated Dec. 21, 2015, 10 pages. |
| Fingerworks Forums, “Is the Multitouch Lemur?”, Available at <http://64233.167.104/search?q=cache:sjVdtyFBvRMJ:forums.finger>, Dec. 24, 2004, 2 pages. |
| Fingerworks Inc., “Quick Reference Guide for iGesture Products”, available at: <http://www.fingerworks.com>, 1999-2002, 2 pages. |
| Fingerworks Inc., “Quick Reference Guide for Touchstream ST/LP”, available at: <http://www.fingerworks.com>, 2001-2003, 4 pages. |
| Fingerworks Inc., “Touchstream LP Silver”, available at: <http://www.fingerworks.com>, Apr. 27, 2005, 18 pages. |
| Fingerworks, “Installation and Operation Guide for the Touchstream”, www.fingerworks.com, Copyright © 2002, 2002, 14 pages. |
| Frey C., “First Look: Inspiration for the Pocket PC”, Innovation Tools, http://www.innovationtools.com/Tools/SoftwareDetails.asp191, Jul. 7, 2005, 3 pages. |
| Fromdistance, “Fromdistance MDM—Mobile Device Manager”, http://www.fromdistance.com/, 4 pages. |
| Fromdistance, “MDM—Mobile Video Blogger”, http://www.fromdistance.com/eng_mvb.html, Copyright 2006, 1 page. |
| Garmin, “Go, View Map, Save to Favorites, Cancel”, http://www8.garmin.com/buzz/nuvifone/m/g/sc-geotag-lg.jpg, retrieved on Mar. 13, 2015, 1 page. |
| Gears, Leigh, “Orange SPV C600 Review”, Available at: <http://www.coolsmartphone.com/article569.html>, retrieved on Apr. 14, 2006, 57 pages. |
| Grant for Invention received for Chinese Patent Application No. 200780046771.2, dated Jan. 16, 2013, 2 pages. |
| Griffin Technology,“IFM—Radio, Remote and Recorder for iPod”, available at: <http://www.griffintechnology.com/products/ifm/index.php>, retrieved on Mar. 17, 2015, 2 pages. |
| Han J. Y., “Multi-Touch Sensing Through Frustrated Total Internal Reflection”, Available at: <http://mrl.nyu.edu/˜jhan/ftirsense/>, 2005, 2 pages. |
| Han, “Multi-touch Interaction Wall”, In ACM SIGGRAPH, 2006, 1 page. |
| Heineman R., “Helio™ Unveils Custom Wireless Experience with Exclusive Handsets and 3G Services”, Feb. 16, 2006, 3 pages. |
| Hesseldahl, Arik, “An App the Mac can Brag About”, Forbes.com, Available at: <http://www.forbes.com/2003/12/15/cx_ah_1215tentech_print.html>, Dec. 15, 2003, 4 pages. |
| Holzinger, Andreas, “Finger Instead of Mouse: Touch Screens as a Means of Enhancing Universal Access”, LNCS, 2003, pp. 387-397. |
| “HTC Europe Co. Ltd and Apple Inc. invalidity Claim dated Jul. 29, 2011, together with amended Particulars of Claim and amended Grounds of Invalidity”, Jul. 29, 2011, 22 pages. |
| “HTC Europe Co. Ltd and Apple Inc. Invalidity Claim No. HC 12 C 01465, together with annexes”, dated Apr. 5, 2012, 12 pages. |
| IBM, “Visual for Multiple-Icon Drag Movement”, IBM Technical Disclosure Bulletin, vol. 37, No. 9, Sep. 1, 1994, pp. 417-418. |
| Ichat A. V., “Videoconferencing for the Rest of us”, Available at: <http://www.apple.com/macosx/features/ichat.html>, Apr. 13, 2006, 3 pages. |
| Intention to Grant received for European Patent Application No. 07844104.5, dated May 8, 2018, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077307, dated Mar. 10, 2009, 12 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/077436, dated Mar. 10, 2009, 10 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/080971, dated Apr. 28, 2009, 7 pages. |
| International Preliminary Report on Patentability received for PCT Patent Application No. PCT/US2007/088884, dated Jul. 7, 2009, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077307, dated Jul. 22, 2008, 16 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/077436, dated Jan. 28, 2008, 12 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/080971, dated Apr. 15, 2008, 9 pages. |
| International Search Report and Written Opinion received for PCT Patent Application No. PCT/US2007/088884, dated May 21, 2008, 11 pages. |
| “Introducing the Ultimate Smartphone Keypad”, Delta II™ Keypads, available at: <http://www.chicagologic.com>, retrieved on Nov. 18, 2005, 2 pages. |
| Invitation to Pay Additional Fees received PCT Patent Application No. PCT/US2007/077307, dated Mar. 6, 2008, 10 pages. |
| Kaljuvee et al., “Efficient Web Form Entry on PDAs”, May 1-5, 2001, 21 pages. |
| Khella et al., “Pocket PhotoMesa: A Zoomable Image Browser for PDAs”, Proceedings of the 3rd International Conference on Mobile and Ubiquitous Multimedia, available at: <http://delivery.acm.org/10.1145/1060000/1052384/p19-khella.pdf?key1=1052384&key2=2419987911&co11=GUIDE&d1=GUIDE&CFID=47073625&CFTOKEN=65767142>, Oct. 29, 2004, 2 pages. |
| Knudsen J., “Technical Articles and Tips, Introduction to Mobile Blogging”, <http://developers.sun.com.mobility/midp/articles/blogging> retrieved on Jan. 14, 2008, 2 pages. |
| Korpela, Jukka, “Using Inline Frames (iframe elements) to Embed Documents into HTML Documents”, (Online), available at: <http://web.archive.org/web/20060925113551/http://www.cs.tut.fi/˜jkorpela/html/iframe.html>, Sep. 25, 2006, 13 pages. |
| Macnn, “Garmin Hits iPhone Directly with Nuvifone”, <http://www.electronista.com/print/50764> retrieved on Mar. 17, 2008, 3 pages. |
| Mactech, “Keystrokes 3.5 for Mac OS X Boosts Word Prediction”, available at: <http://www.mactech.com/news/?p=1007129>, retrieved on Jan. 7, 2008, pp. 1-3. |
| Martin et al., “Use-Me.Gov”, Usability-driven Open Platform for Mobile Government, Copyright © Formatex 2005, 6 pages. |
| Mashup Camp Blog, “Mashps Explained. The Big Blue Way”, <http://blog.mashupcamp.com> retrieved on Aug. 19, 2006, 6 pages. |
| Mashup Camp, “About Mashup Camp”, <http://wiki.mashupcamp.com/index.php/AboutMashupCamp> retrieved on Jan. 14, 2008, 3 pages. |
| Mashup, “Web Application Hybrid”, <http://en.wikipedia.org/wiki/Mashup_%28web_application_hybrid%29> retrieved on Aug. 25, 2006, 9 pages. |
| Mashups, “The new breed of Web App”, <http://www-128.com/developerworks/library/x-mashups.html> retrieved on Aug. 25, 2006, 9 pages. |
| Microsoft Corporation, “To Answer or Reject a Call”, Audiovox PPC 5050, Pocket PC Phone User Manual, Available at: <http://www.cellphones.ca/cell-phones/audiovox-ppc-5050/>, Apr. 11, 2008, 3 pages. |
| “Microsoft Touts ‘Thumb-as-Stylus’ Interface Progress”, EE Times, New & Analysis, Available at: <https://www.informationweek.com/microsoft-touts-thumb-as-stylus-interface-progress/d/d-id/1031620 >, Apr. 4, 2005, pp. 1-9. |
| Microwaves RF, “MS Motion Sensors Boost Handset Reliability”, http://www.mwrf.cp,/Articles/Print.efm?ArticleID=12740, Copyright 2004, Penton Media Inc., Oct. 13, 2006, 4 pages. |
| Milic-Frayling et al., “Smartview: Enhanced Document Viewer for Mobile Devices”, Microsoft Technical Report, available at: <ftp://ftp.research.microsoft.com/pub/tr/tr-2002-114.pdf>, Nov. 15, 2002, 10 pages. |
| Miller, Dana, “PersonalJava Application Environment”, available at: <http://java.sun.com/products/personaljava/touchable/>, Jun. 8, 1999, 12 pages. |
| “Ming User Manual”, Motorola, 2006, 141 pages. |
| Mitchell, Robert, “GUI Gets a Makeover”, Available at: http://www.computerworld.com/action/article.do?command=printArticleBasic&articleId=263695, Sep. 25, 2006, 7 pages. |
| Mobhappy, “Location Based Taxis Meets LBS Advertising”, <http://mobhappy.typepad.com/russell_buckleys_mobhappy/2005/10/location_based_.html> retrieved on May 19, 2006, 3 pages. |
| Mobile Box Office™, “See How it Works”, <http://www.mbo.com/web/index.jsp> retrieved on Oct. 17, 2006, 1 page. |
| Mobile Tech News,“T9 Text Input Software Updated”, available at: <http://www.mobiletechnews.com/info/2004/11/23/122155.html>, Nov. 23, 2004, 4 pages. |
| Mobiqa, “Welcome to Mobiqa”, <http://www.mobiqa.com> retrieved on Oct. 17, 2006, 2 pages. |
| Moblog-Wikipedia, “Moblog”, <http://en.wikipedia.org/wiki/Moblog> retrieved on Apr. 5, 2006, 4 pages. |
| “Model 8690 Inter-Tel Protocol Mode User Guide”, Inter-Tel, Part No. 550.8116, Issue 11, Mar. 2006, 160 pages. |
| Morenet, “Dialing Plan-Research and Innovation-Technical Support”, <http://www.more.net/technical/research/dialplan/index.html.> retrieved on Jan. 11, 2008, 10 pages. |
| “Motorola A1000 User Guide”, Motorola, Sep. 15, 2004, pp. 1-122. |
| “Motorola Mobility Opposition Grounds to Apple Inc. European Patent EP 2126678 dated Apr. 11, 2012, together with Exhibits E3, E4, and E5 re: CHT 2005”, Apr. 2-7, 2005, Portland Oregon, USA, Apr. 2012, 53 pages. |
| Mountfocus Information Systems, “An Onscreen Virtual Keyboard: touchscreen, kiosk and Windows compatible”, Available at: http://www.virtual-keyboard.com, Dec. 19, 2007, 3 pages. |
| Move Mobile Systems, “Take the Real Web with You”, <http://www.movemobile.com> retrieved on Nov. 29, 2005, 1 page. |
| MS Mobiles.com—Simply Mobile, “New Program for Mobile Blogging for Pocket PC Release:My Blog”, Available online at: <http://msmobiles.com/news.php/4067.html>, 2005, 1 page. |
| Multimedia Soft, “3D Control Magic for NET”, <http://www.multimediasoft.com/3dcm> retrieved on Dec. 18, 2007, 2 pages. |
| Myers, Brad A., “Shortcutter for Palm”, available at: <http://www.cs.cmu.edu/˜pebbles/v5/shortcutter/palm/index.html>, retrieved on Jun. 18, 2014, 10 pages. |
| Namahn, “User-centered Design of Mobile Solutions—A New Paradigm”, 2006, 15 pages. |
| NCIP, “NCIP Library: Word Prediction Collection”, available at: <http://www2.edc.org/ncip/library/wp/toc.htm>, 1998, 4 pages. |
| NCIP, “What is Word Prediction?”, available at: <http://www2.edc.org/NCIP/library/wp/what_is.htm>, 1998, 2 pages. |
| “Nokia 5140 User Guide”, Issue 1, 2004, 66 pages. |
| “Nokia 9110 User's Manual”, Issue 3, Jun. 7, 1998, 190 pages. |
| Nokia, “7280 Bedienungsanleitung”, Available at: <htpp://web.archive.org/web/20051222023851/http://ndsl.nokia.com/phones/files/guides/nokia7280 UDG-de.pdf>, 2005, pp. 1-101. |
| Nokia, “7280 Interactive Demonstrations”, Screenshot, available at: <http://web.archive.org/web/2005112502636/europe.nokia.com/support/tutorials/7280/german/index.htm>, Nov. 25, 2005, 2 pages. |
| Nokia, “Nokia 7280 User Manual”, Available at: <http://nds1.nokia.com/phones/files/guides/Nokia_7280_UG-en.pdf>, Nov. 25, 2004, 74 pages. |
| Nokia, “Nokia 9000i User's Manual”, Issue 2, Jun. 7, 1998, 126 pages. |
| Nokia, “Press Backgrounder-Guide to Moblogging”, Feb. 2005, 3 pages. |
| Nokia-Enhancements, “Nokia Video Call Stand PT-8”, Apr. 13, 2006, 2 pages. |
| Nokia-Phone Features, “Nokia 6630 Imaging Smartphone”, Available at: <http://europe.nokia.com/nokia/0,8764,58711,00.html>, Apr. 13, 2006, 5 pages. |
| Non Final Office Action received for U.S. Appl. No. 11/553,429, dated Jul. 21, 2011, 21 pages. |
| Non Final Office Action received for U.S. Appl. No. 11/553,429, dated Oct. 6, 2010, 18 pages. |
| Non Final Office Action received for U.S. Appl. No. 11/769,695, dated Oct. 27, 2011, 17 pages. |
| Non Final Office Action received for U.S. Appl. No. 13/596,652, dated Sep. 19, 2012, 7 pages. |
| Non-Final Office Action received for U.S. Appl. No. 16/434,794, dated Apr. 16, 2020, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/553,429, dated Jun. 21, 2010, 14 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/769,694, dated May 6, 2010, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/769,695, dated Sep. 3, 2010, 21 pages. |
| Non-Final Office Action received for U.S. Appl. No. 11/960,673, dated Oct. 28, 2010, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/176,703, dated Apr. 30, 2014, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/903,962, dated Apr. 20, 2015, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 13/903,962, dated Nov. 1, 2013, 6 pages. |
| Non-Final Office Action received for U.S. Appl. No. 14/632,817, dated Jun. 4, 2015, 10 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/137,127, dated Jan. 30, 2017, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 15/620,662, dated Oct. 4, 2018, 8 pages. |
| Non-Final Office Action received for U.S. Appl. No. 17/306,236, dated Jan. 5, 2022, 11 pages. |
| Non-Final Office Action received for U.S. Appl. No. 90/012,893, dated Dec. 5, 2013, 119 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2008203349, dated Jul. 15, 2011, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2011244866, dated Jan. 14, 2015, 3 pages. |
| Notice of Acceptance received for Australian Patent Application No. 2015202221, dated Aug. 24, 2016, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/553,429, dated Apr. 4, 2011, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/553,429, dated Feb. 14, 2011, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/553,429, dated Nov. 7, 2011, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/769,694, dated Apr. 15, 2011, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/769,694, dated Jun. 1, 2011, 21 pages. |
| Notice of Allowance received for U.S. Appl. No. 11/960,673, dated Mar. 31, 2011, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/176,703, dated Dec. 23, 2014, 2 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/176,703, dated Oct. 21, 2014, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/205,586, dated Jan. 24, 2012, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/205,586, dated Nov. 21, 2011, 8 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/418,322, dated May 11, 2012, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/596,652, dated Feb. 7, 2013, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/596,652, dated Jan. 9, 2013, 7 pages. |
| Notice of Allowance received for U.S. Appl. No. 13/903,962, dated Dec. 16, 2014, 9 pages. |
| Notice of Allowance received for U.S. Appl. No. 14/632,817, dated Dec. 16, 2015, 6 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/137,127, dated Mar. 27, 2017, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 15/620,662, dated Jan. 30, 2019, 5 pages. |
| Notice of Allowance received for U.S. Appl. No. 16/434,794, dated Jan. 12, 2021, 13 pages. |
| Notice of Allowance received for U.S. Appl. No. 17/306,236, dated Mar. 28, 2022, 9 pages. |
| Notice of Grant received for Chinese Patent Application No. 201210261995.8, dated Jul. 4, 2014, 2 pages. |
| Notice of Intent received for U.S. Appl. No. 90/012,893, dated Aug. 8, 2014, 9 pages. |
| Office Action received for Australian Patent Application No. 2008203349, dated Feb. 19, 2010, 3 pages. |
| Office Action received for Australian Patent Application No. 2009100722, dated Oct. 5, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2009100723, dated Oct. 9, 2009, 2 pages. |
| Office Action received for Australian Patent Application No. 2011244866, dated Sep. 23, 2013, 3 pages. |
| Office Action received for Australian Patent Application No. 2015202221, dated Feb. 29, 2016, 4 pages. |
| Office Action received for Australian Patent Application No. 2016269522, dated Jan. 5, 2018, 4 pages. |
| Office Action received for Australian Patent Application No. 2016269522, dated Oct. 4, 2018, 3 pages. |
| Office Action received for Chinese Patent Application No. 200780040472.8, dated Jan. 18, 2012, 4 pages. |
| Office Action received for Chinese Patent Application No. 200780046771.2, dated Dec. 12, 2011, 9 pages. |
| Office Action received for Chinese Patent Application No. 200780046771.2, dated Sep. 13, 2012, 6 pages. |
| Office Action Received for Chinese Patent Application No. 201210261995.8, dated Dec. 4, 2013, 5 pages. |
| Office Action received for European Patent Application No. 07841759.9, dated Aug. 13, 2009, 7 pages. |
| Office Action received for European Patent Application No. 07841759.9, dated May 25, 2010, 5 pages. |
| Office Action received for European Patent Application No. 07844104.5, dated Jul. 12, 2011, 6 pages. |
| Office Action received for European Patent Application No. 07844104.5, dated Mar. 27, 2013, 4 pages. |
| Office Action Received for European Patent Application No. 078441045, dated Nov. 10, 2015, 6 pages. |
| Office Action received for European Patent Application No. 11176480.9, dated Nov. 14, 2014, 5 pages. |
| Office Action received for European Patent Application No. 11176480.9, dated Nov. 8, 2016, 12 pages. |
| Office Action received for European Patent Application No. 18192595.9, dated Apr. 16, 2020, 5 pages. |
| Office Action received for European Patent Application No. 18192595.9, dated Dec. 4, 2020, 3 pages. |
| Office Action received for European Patent Application No. 18192595.9, dated Sep. 17, 2021, 5 pages. |
| Office Action received for German Patent Application No. 112007001109.2, dated Sep. 14, 2010, 28 pages. |
| O'Neal, “Smart Phones with Hidden Keyboards”, available at: <http://msc.com/4250-6452_16-6229969-1.html>, Nov. 18, 2005, 3 pages. |
| “Onelook”, Dictionary Search, Retrieved from the Internet: http://onelook.com/?w=adjacent&ls=a, Retrieved on Jan. 7, 2008, 5 pages. |
| Openwave, “Inside the Wave-Alliances Fuel Location Services”, Retrieved from the Internet: http://www.openwave.com/us/openwave_iq/inside_wave/2003/july/location_services, Jul. 2003, 2 pages. |
| Opera Software, “Opera 8.5 Beta 2 for Windows Mobile, Pocket PC”, Available at: <http://www.opera.com/products/mobile/products/winmobileppc>, retrieved on Apr. 5, 2006, 2 pages. |
| Opera Software, “Opera 8.5 for S60 Phones—Get the Full Internet Experience on Your Mobile Phone”, Available at: <http://www.symbian-freak.com/news/1105/opera.htm>, Oct. 14, 2005, 3 pages. |
| Opera Software, “Opera for Mobile, The Full Web Anytime, Anywhere”, Available at: <www.opera.com/mobile>, Jan. 2006, 7 pages. |
| Opera Software, “Opera for S60 Tutorial”, Available at: <http://www.xmarks.com/site/www.opera.com/support/tutorials/s60/>, retrieved on Apr. 5, 2006, 5 pages. |
| Opera Software, “Opera for Windows Mobile Smartphone 2003 Tutorial”, Available at: <http://www.opera.com/support/tutorials/winmobile>, retrieved on Apr. 5, 2005, 4 pages. |
| Opera Software, “The New Opera Browser for Series 60 Features Zoom and Password Manager”, Press Releases Database, Available at: <http://pressreleases.techwhack.com/1334/1411-opera-browser-features-zoom-and-password>, Nov. 14, 2005, 3 pages. |
| “P900/P908 White Paper”, Sony Ericsson, Dec. 2003, pp. 1-128. |
| Padilla, Alfredo, “Palm Treo 750 Cell Phone Review—Messaging”, available at: <http://www.wirelessinfo.com/content/palm-Treo-750-Cell-Phone-Review/Messaging.htm>, Mar. 17, 2007, 6 pages. |
| “Palm Treo 700w User Manual”, Palm, 2005, 96 pages. |
| Palmone, “Your Mobile Manager”, Chapter 2, LifeDrive™ User's Guide, available at: <http://www.palm.com/us/support/handbooks/lifedrive/en/lifedrive_handbook.pdf>, 2005, 23 pages. |
| “PdQTM Applications Handbook”, Qualcomm, 1999, 192 pages. |
| Pfeiffer, “Who Will Make the iPod Phone? And When?”, eWeek, http://www.eweek.com/print_article2/0,1217,a=146078,00asp, Feb. 17, 2005, 3 pages. |
| Plaisant et al., “Touchscreen Toggle Design”, Proceedings of the Conference on Human Factors in Computing Systems, May 3-7, 1992, pp. 667-668. |
| “Pleading notes Mr B.J. Berghuis van Woortman, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731”, Aug. 10-11, 2010, pp. 1-16. |
| “Pleading notes Mr Kleemans, Mr Blomme and Mr Van Oorschot, in matter of Apple Inc. vs Samsung Electronics, Case No. KG ZA 11-730 and KG ZA 11-731”, Aug. 10, 2011, 35 pages. |
| Roos Gina, “Agilent's New Proximity Sensor Beats the Fumble-fingered Competition Hands Down . . . Literally”, Available at: <http://www.eeproductcenter.com/article/printalbeArticle.jhtml>, Sep. 1, 2004, 3 pages. |
| Samsung Electronics GmbH vs Apple Inc., “List scrolling and document translation, scaling and rotation on a touch-screen display”, Opposition, Jan. 30, 2012, 27 pages. |
| Samsung Electronics vs Apple Inc., “Statement of Defense Also Counterclaim, Case No. KG ZA 2011-730”, Jul. 20, 2011, 44 pages. |
| Samsung Electronics vs Apple Inc., “Statement of Defense Also Counterclaim, Case No. KG ZA 2011-731”, Jul. 20, 2011, 48 pages. |
| Savov, “iPhone and Magic Mouse linked up by BT stack”, (video) Jan. 4, 2010, http://www.engadget.com/2010/01/04/iphone-and-magic-mouse-linked-up-by-btstack-video/, 5 pages. |
| “SPH-i700 Series Digital Dual-Band Mobile Phone User Guide”, Samsung, 2004, 133 pages. |
| Summons to Attend Oral Proceedings received for European Patent Application No. 11176480.9, dated Apr. 26, 2016, 6 pages. |
| Summons to Attend Oral Proceedings received for the European Application No. 07841759.9, dated May 17, 2011, 4 pages. |
| “TAKEphONE User Manual”, Feb. 21, 2005, 32 pages. |
| “TAKEphONE User Manual”, Jun. 15, 2006, pp. 1-40. |
| “TealPhone User's Manual”, TealPoint Software, Jan. 24, 2006, 44 pages. |
| “The Kyocera 7135 Smartphone: Reference Guide”, Kyocera, 2002, 224 pages. |
| “The Kyocera 7135 Smartphone: Reference Guide”, Kyocera, 2003, 12 pages. |
| Third Party rejection received for U.S. Appl. No. 90/012,893, dated Jun. 14, 2013, 341 pages. |
| Tidwell, Jenifer, “Designing Interfaces, Animated Transition”, Archieved by Internet Wayback Machine, Available at: <https://web.archive.org/web/20060205040223/http://designinginterfaces.com:80/Animated_Transition>, Retrieved on Mar. 20, 2018, 2005, 2 pages. |
| “User's Guide Agendus for Symbian OS UIQ Edition”, Iambic, 2003, pp. 1-23. |
| “Using Your Palm Treo 700w Smartphone”, Palm, p. 30, 31, 48, 49, 52, 130, 253, 254, 2005-2006, 290 pages. |
| “Using YourTreoTM 650 Smartphone”, PALMONE, Dec. 7, 2004, 208 pages. |
| Williams, Martyn, “LG's Cell Phone Can Pause Live TV”, PC World, Oct. 11, 2005, 2 pages. |
| “XPlore M98 User Manual”, Group Sense PDA, Jul. 14, 2005, pp. 1-138. |
| Number | Date | Country | |
|---|---|---|---|
| 20220385763 A1 | Dec 2022 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60937993 | Jun 2007 | US | |
| 60947133 | Jun 2007 | US | |
| 60879469 | Jan 2007 | US | |
| 60879253 | Jan 2007 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17306236 | May 2021 | US |
| Child | 17878766 | US | |
| Parent | 16434794 | Jun 2019 | US |
| Child | 17306236 | US | |
| Parent | 15620662 | Jun 2017 | US |
| Child | 16434794 | US | |
| Parent | 15137127 | Apr 2016 | US |
| Child | 15620662 | US | |
| Parent | 14632817 | Feb 2015 | US |
| Child | 15137127 | US | |
| Parent | 13176703 | Jul 2011 | US |
| Child | 14632817 | US | |
| Parent | 11960673 | Dec 2007 | US |
| Child | 13176703 | US |
