Intelligent Automated Assistant in Messaging Environment

System and environment 

Figure 1 illustrates a block diagram of system 100 according to various examples. In some examples, system 100 can implement a digital assistant. The terms“digital assistant,” “virtual assistant,” “intelligent automated assistant,” or “automatic digital assistant” can refer to any information processing system that interprets natural language input in spoken and/or textual form to infer user intent, and performs actions based on the inferred user intent. For example, to act on an inferred user intent, the system can perform one or more of the following: identifying a task flow with steps and parameters designed to accomplish the inferred user intent, inputting specific requirements from the inferred user intent into the task flow; executing the task flow by invoking programs, methods, services, APIs, or the like; and generating output responses to the user in an audible (e.g., speech) and/or visual form. 

Specifically, a digital assistant can be capable of accepting a user request at least partially in the form of a natural language command, request, statement, narrative, and/or inquiry. Typically, the user request can seek either an informational answer or performance of a task by the digital assistant. A satisfactory response to the user request can be a provision of the requested informational answer, a performance of the requested task, or a combination of the two. For example, a user can ask the digital assistant a question, such as “Where am I right now?” Based on the user’scurrent location, the digital assistant can answer, “You are in Central Park near the west gate.” The user can also request the performance of a task, for example, “Please invite my friends to my girlfriend’sbirthday partynext week.” In response, the digital assistant can acknowledge the request by saying “Yes, right away,” and then send a suitable calendar invite on behalf of the user to each of the user’sfriends listed in the user’selectronic address book. During performance of a requested task, the digital assistant can sometimes interact with the user in a continuous dialogue involving multiple exchanges of information over an extended period of time. There are numerous other ways of interacting with a digital assistant to request information or performance of various tasks. In addition to providing verbal responses and taking programmed actions, the digital assistant can also provide responses in other visual or audio forms, e.g., as text, alerts, music, videos, animations, etc. 

As shown in Figure 1, in some examples, a digital assistant can be implemented according to a client-server model. The digital assistant can include client-side portion 102 (hereafter “DA clientDA client 102“) executed on user device 104 and server-side portion 106 (hereafter “DA server 106“) executed on server system 108. DA client 102 can communicate with DA server 106 through one or more networks 110. DA client 102 can provide client-side functionalities such as user-facing input and output processing and communication with DA server 106. DA server 106 can provide server-side functionalities for any number of DA clients 102 each residing on a respective user device 104.

In some examples, DA server 106 can include client-facing I/O interface 112, one or more processing modules 114, data and models 116, and I/O interface to external services 118. The client-facing I/O interface 112 can facilitate the client-facing input and output processing for DA server 106. One or more processing modules 114 can utilize data and models 116 to processspeech input and determine the user’sintent based on natural language input. Further, one or more processing modules 114perform task execution based on inferred user intent. In some examples, DA server 106 can communicate with external services 120 through network(s) 110 for task completion or information acquisition. I/O interface to external services 118 can facilitate such communications. 

User device 104 can be any suitable electronic device. For example, user devices can be a portable multifunctional device (e.g., device 202, described below with reference to Figure 2), a multifunctional device (e.g., device 400, described below with reference to FIG. 4), or a personal electronic device (e.g., device 600, described below with reference to FIG. 6A-B.) A portable multifunctional device can be, for example, a mobile telephone that also contains other functions, such as PDA and/or music player functions. Specific examples of portable multifunction devices can include the iPhone.RTM., iPod Touch.RTM., and iPad.RTM. devices from Apple Inc. of cupertino, calif. Other examples of portable multifunction devices can include, without limitation, laptop or tablet computers. Further, in some examples, user device 104 can be a non-portable multifunctional device. In particular, user device 104 can be a desktop computer, a game console, a television, or a television set-top box. In some examples, user device 104 can include a touch-sensitive surface (e.g., touch screen displays and/or touchpads). Further, user device 104 can optionally include one or more other physical user-interface devices, such as a physical keyboard, a mouse, and/or a joystick. Various examples of electronic devices, such as multifunctional devices, are described below in greater detail. 

Examples of communication network(s) 110 can include local area networks (LAN) and wide area networks (WAN), e.g., the internet. Communication network(s) 110 can be implemented using any known network protocol, including various wired or wireless protocols, such as, for example, ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code divisionmultiple access (CDMA), time divisionmultiple access (TDMA), bluetooth, Wi-Fi, voice over Internet Protocol (VolP), Wi-MAX, or any other suitable communication protocol. 

Server system 108 can be implemented on one or more standalone data processing apparatus or a distributed network of computers. In some examples, server system 108 can also employ various virtual devices and/or services of third-party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of server system 108. 

In some examples, user device 104 can communicate with DA server 106 via second user device 122. Second user device 122 can be similar or identical to user device 104. For example, second user device 122 can be similar to devices 200, 400, or 600 described below with reference to FIGS. 2A, 4, and 6A-B. User device 104 can be configured to communicatively couple to second user device 122 via a direct communication connection, such as bluetooth, NFC, BTLE, or the like, or via a wired or wireless network, such as a local Wi-Fi network. In some examples, second user device 122 can be configured to act as a proxy between user device 104 and DA server 106. For example, DA client 102 of user device 104 can be configured to transmit information (e.g., a user request received at user device 104) to DA server 106 via second user device 122. DA server 106 can process the information and return relevant data (e.g., data content responsive to the user request) to user device 104 via second user device 122. 

In some examples, user device 104 can be configured to communicate abbreviated requests for data to second user device 122 to reduce the amount of information transmitted from user device 104. Second user device 122 can be configured to determine supplemental information to add to the abbreviated request to generate a complete request to transmit to DA server 106. This system architecture can advantageously allow user device 104 having limited communication capabilities and/or limited battery power (e.g., a watch or a similar compact electronic device) to access services provided by DA server 106 by using second user device 122, having greater communication capabilities and/or battery power (e.g., a mobile phone, laptop computer, tablet computer, or the like), as a proxy to DA server 106. While only two user devices 104 and 122 are shown in Figure 1, it should be appreciated that system 100 can include any number and type of user devices configured in this proxy configuration to communicate with DA server system 106. 

Although the digital assistant shown in Figure 1 can include both a client-side portion (e.g., DA client 102) and a server-side portion (e.g., DA server 106), in some examples, the functions of a digital assistant can be implemented as a standalone application installed on a user device. In addition, the divisions of functionalities between the client and server portions of the digital assistant can vary in different implementations. For instance, in some examples, the DA client can be a thin-client that provides only user-facing inputuser-facing input and output processingfunctions, and delegates all other functionalities of the digital assistant to a backend server. 

2. Electronic devices 

Attention is now directed toward embodiments of electronic devices for implementing the client-side portion of a digital assistant. Figure 2 is a block diagram illustratingportable multifunction device 202 with touch-sensitive display system 278 in accordance with some embodiments. Touch-sensitive display 278 is sometimes called a “touch screen” for convenience and is sometimes known as or called a “touch-sensitive display system.” Device 202 includes memory 202 (which optionally includes one or more computer-readable storage mediums), memory controller 318, one or more processing units (CPUs) 320, peripherals interface 322, RF circuitry 300, audio circuitry 306, speaker 310, microphone 308, input/output (I/O) subsystem 298, other input control devices 282, and external port 314. Device 202 optionally includes one or more optical sensors 296. Device 202 optionally includes one or more contactintensitysensors 294 for detecting intensity of contacts on device 202 (e.g., a touch-sensitive surface such as touch-sensitive display system 278 of device 202). device 202 optionally includes one or more tactile output generators 290 for generating tactile outputs on device 202 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 278 of device 202 or touchpad 455 of device 400). These components optionally communicate over one or more communication buses or signal lines 203. 

As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more forcesensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure, and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button). 

As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user’s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user’shand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user’smovements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click,” a “down click,” “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user. 

It should be appreciated that device 202 is only one example of a portable multifunction device, and that device 202 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in Figure 2 are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and/or application-specific integrated circuits. 

Memory 202 may include one or more computer-readable storage mediums. The computer-readable storage mediums may be tangible and non-transitory. Memory 202 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 318 may control access to memory 202 by other components of device 202. 

In some examples, a non-transitory computer-readable storage medium of memory 202 can be used to storeinstructions (e.g., for performing aspects of processes described below) for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In other examples, the instructions (e.g., for performing aspects of the processes described below) can be stored on a non-transitory computer-readable storage medium (not shown) of the server system 108 or can be divided between the non-transitory computer-readable storage medium of memory 202 and the non-transitory computer-readable storage medium of server system 108. In the context of this document, a “non-transitory computer-readable storage medium” can be any medium that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. 

Peripherals interface 322 can be used to couple input and output peripherals of the device to CPU 320 and memory 202. The one or more processors 320 run or execute various software programs and/or sets of instructions stored in memory 202 to perform various functions for device 202 and to processdata. In some embodiments, peripherals interface 322, CPU 320, and memory controller 318 may be implemented on a single chip, such as chip 316. In some other embodiments, they may be implemented on separate chips. 

RF (radio frequency) circuitry 300 receives and sends RF signals, also called electromagnetic signals. RF circuitry 300 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 300 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 300 optionally communicates with networks, such as the internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The RF circuitry 300 optionally includes well-known circuitry for detecting near field communication (NFC) fields, such as by a short-range communication radio. The wireless communication optionally uses any of a plurality of communications standards, protocols, and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code divisionmultiple access (W-CDMA), code divisionmultiple access (CDMA), time divisionmultiple access (TDMA), bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n, and/or IEEE 802.11ac), voice over Internet Protocol (VolP), Wi-MAX, a protocol for e mail (e.g., internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for instant messaging and Presence Leveraging Extensions (SIMPLE), instant messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. 

Audio circuitry 306, speaker 310, and microphone 308 provide an audio interface between a user and device 202. Audio circuitry 306 receives audio data from peripherals interface 322, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 310. Speaker 310 converts the electrical signal to human-audible sound waves. Audio circuitry 306 also receives electrical signals converted by microphone 308 from sound waves. Audio circuitry 306 converts the electrical signal to audio data and transmits the audio data to peripherals interface 322 for processing. Audio data may be retrieved from and/or transmitted to memory 202 and/or RF circuitry 300 by peripherals interface 322. In some embodiments, audio circuitry 306 also includes a headset jack (e.g., 312, FIG. 3). The headset jack provides an interface between audio circuitry 306 and removable audio input/output peripherals, such as output-only headphones or a headset with both output (e.g., a headphone for one or both ears) and input (e.g., a microphone). 

I/O subsystem 298 couplesinput/output peripherals on device 202, such as touch screen 278 and other input control devices 282, to peripherals interface 322. I/O subsystem 298 optionally includes display controller 280, optical sensor controller 292, intensity sensor controller 286, haptic feedback controller 284, and one or more input controllers 288 for other input or control devices. The one or more input controllers 288 receive/send electrical signals from/to other input control devices 282. The other input control devices 282 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 288 are, optionally, coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 308, FIG. 3) optionally include an up/down button for volume control of speaker 310 and/or microphone 308. The one or more buttons optionally include a push button (e.g., 306, FIG. 3). 

A quick press of the push button may disengage a lock of touch screen 278 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a device by Performing Gestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 306) may turn power to device 202 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 278 is used to implement virtual or soft buttons and one or more soft keyboards. 

Touch-sensitive display 278 provides an input interface and an output interface between the device and a user. Display controller 280 receives and/or sends electrical signals from/to touch screen 278. Touch screen 278 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects. 

Touch screen 278 has a touch-sensitive surface, sensor, or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 278 and display controller 280 (along with any associated modules and/or sets of instructions in memory 202) detect contact (and any movement or breaking of the contact) on touch screen 278 and convert the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web pages, or images) that are displayed on touch screen 278. In an exemplary embodiment, a point of contact between touch screen 278 and the user corresponds to a finger of the user. 

Touch screen 278 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 278 and display controller 280 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 278. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone.RTM. and iPod Touch.RTM. from Apple Inc. of cupertino, calif. 

A touch-sensitive display in some embodiments of touch screen 278 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No.: 6,323,846 (westerman et al.), U.S. Pat. No. 6,570,557 (westerman et al.), and/or U.S. Pat. No. 6,677,932 (westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 278 displays visual output from device 202, whereas touch-sensitive touchpads do not provide visual output. 

A touch-sensitive display in some embodiments of touch screen 278 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 No. 11/048,264, “Gestures For Touch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A computer With A Touch Screen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety. 

Touch screen 278 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 278 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user. 

In some embodiments, in addition to the touch screen, device 202 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 displayvisual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 278 or an extension of the touch-sensitive surface formed by the touch screen. 

Device 202 also includes power system 312 for powering the various components. Power system 312 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices. 

Device 202 may also include one or more optical sensors 296. Figure 2 shows an optical sensor coupled to optical sensor controller 292 in I/O subsystem 298. Optical sensor 296 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 296 receives light from the environment, projected through one or more lenses, and converts the light to data representing an image. In conjunction with imaging module 236 (also called a camera module), optical sensor 296 may capture still images or video. In some embodiments, an optical sensor is located on the back of device 202, opposite touch screen display 278 on the front of the device so that the touch screen display may be used as a viewfinder for still and/or video image acquisition. In some embodiments, an optical sensor is located on the front of the device so that the user’simage may be obtained for video conferencing while the userviews the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 296 can be changed by the user (e.g., by rotating the lens and the sensor in the device housing) so that a single optical sensor 296 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition. 

Device 202 optionally also includes one or more contactintensitysensors 294. Figure 2 shows a contact intensity sensor coupled to intensity sensor controller 286 in I/O subsystem 298. Contact intensity sensor 294 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electric force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other intensity sensors (e.g., sensors used to measure the force (or pressure) of a contact on a touch-sensitive surface). contact intensity sensor 294 receives contact intensity information (e.g., pressure information or a proxy for pressure information) from the environment. In some embodiments, at least one contact intensity sensor is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 278). In some embodiments, at least one contact intensity sensor is located on the back of device 202, opposite touch screen display 278, which is located on the front of device 202. 

Device 202 may also include one or more proximity sensors 304. Figure 2 shows proximity sensor 304 coupled to peripherals interface 322. Alternately, proximity sensor 304 may be coupled to input controller 288 in I/O subsystem 298. Proximity sensor 304 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; 11/240,788, “Proximity Detector In Handheld Device”; 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and 11/638,251, “Methods And Systems For Automatic Configuration Of peripherals,” which are hereby incorporated by reference in their entirety. In some embodiments, the proximity sensor turns off and disables touch screen 278 when the multifunction device is placed near the user’s ear (e.g., when the user is making a phone call). 

device 202 optionally also includes one or more tactile output generators 290. Figure 2 shows a tactile output generator coupled to haptic feedback controller 284 in I/O subsystem 298. Tactile output generator 290 optionally includes one or more electroacoustic devices such as speakers or other audio components and/or electromechanical devices that convert energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component that converts electrical signals into tactile outputs on the device). contact intensity sensor 294 receives tactile feedback generation instructions from haptic feedback module 260 and generates tactile outputs on device 202 that are capable of being sensed by a user of device 202. In some embodiments, at least one tactile output generator is collocated with, or proximate to, a touch-sensitive surface (e.g., touch-sensitive display system 278) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 202) or laterally (e.g., back and forth in the same plane as a surface of device 202). In some embodiments, at least one tactile output generator sensor is located on the back of device 202, opposite touch screen display 278, which is located on the front of device 202. 

Device 202 may also include one or more accelerometers 302. Figure 2 shows accelerometer 302 coupled to peripherals interface 322. Alternately, accelerometer 302 may be coupled to an input controller 288 in I/O subsystem 298. Accelerometer 302 may perform as described in U.S. Patent Publication No. 20050190059, “Acceleration-based Theft Detection System for Portable Electronic Devices,” and U.S. Patent Publication No. 20060017692, “Methods And Apparatuses For Operating A Portable Device Based On An accelerometer,” both of which are incorporated by reference herein in their entirety. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on an analysis of data received from the one or more accelerometers. Device 202 optionally includes, in addition to accelerometer(s) 302, a magnetometer (not shown) and a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information concerning the location and orientation (e.g., portrait or landscape) of device 202. 

In some embodiments, the software components stored in memory 202 include operating system 208, communication module (or set of instructions) 276, contact/motion module (or set of instructions) 270, graphics module (or set of instructions) 266, text input module (or set of instructions) 258, Global Positioning System (GPS) module (or set of instructions) 252, Digital Assistant Client Module 248, and applications (or sets of instructions) 226. Further, memory 202 can storedata and models, such as user data and models 244. Furthermore, in some embodiments, memory 202 (Figure 2) or 470 (FIG. 4) storesdevice/global internal state 232, as shown in FIGS. 2A and 4. Device/global internal state 232 includes one or more of: active application state, indicating which applications, if any, are currently active; display state, indicating what applications, views or other information occupy various regions of touch screen display 278; sensor state, including information obtained from the device’svarious sensors and inputcontrol devices 282; and location information concerning the device’slocation and/or attitude. 

Operating system 208 (e.g., darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardwarehardware and softwarecomponents. 

Communication module 276 facilitates communication with other devices over one or more external ports 314 and also includes various software components for handling data received by RF circuitry 300 and/or external port 314. External port 314 (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.RTM. (trademark of Apple Inc.) Devices. 

Contact/motion module 270 optionally detects contact with touch screen 278 (in conjunction with display controller 280) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). contact/motion module 270 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact), determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). contact/motion module 270 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one fingercontacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 270 and display controller 280 detect contact on a touchpad. 

In some embodiments, contact/motion module 270 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments, at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 202). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined threshold values without changing the trackpad or touch screen display hardware. Additionally, in some implementations, a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter). 

contact/motion module 270 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (liftoff) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (liftoff) event. 

Graphics module 266 includes various known software components for rendering and displaying graphics on touch screen 278 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including ,without limitation, text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations, and the like. 

In some embodiments, graphics module 266storesdata representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 266 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 280. 

Haptic feedback module 260 includes various software components for generating instructions used by tactile output generator(s) 290 to produce tactile outputs at one or more locations on device 202 in response to user interactions with device 202. 

Text input module 258, which may be a component of graphics module 266, provides soft keyboards for entering text in various applications (e.g., contacts 240, e mail 212, IM 241, browser 274, and any other application that needs text input). 

GPS module 252determines the location of the device and provides this information for use in various applications (e.g., to telephone 243 for use in location-based dialing; to camera 236 as picture/video metadata; and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets). 

Digital Assistant Client Module 248 can include various client-side digital assistant instructions to provide the client-side functionalities of the digital assistant. For example, Digital Assistant Client Module 248 can be capable of accepting voice input (e.g., speech input), text input, touch input, and/or gestural input through various user interfaces (e.g., microphone 308, accelerometer(s) 302, touch-sensitive display system 278, optical sensor(s) 296, other input control devices 282, etc.) of portable multifunction device 202. Digital Assistant Client Module 248 can also be capable of providing output in audio (e.g., speech output), visual, and/or tactile forms through various output interfaces (e.g., speaker 310, touch-sensitive display system 278, tactile output generator(s) 290, etc.) of portable multifunction device 202. For example, output can be provided as voice, sound, alerts, text messages, menus, graphics, videos, animations, vibrations, and/or combinations of two or more of the above. During operation, Digital Assistant Client Module 248 can communicate with DA server 106 using RF circuitry 300. 

User data and models 244 can include various data associated with the user (e.g., user-specific vocabulary data, user preference data, user-specified name pronunciations, data from the user’selectronic address book, to-do lists, shopping lists, etc.) to provide the client-side functionalities of the digital assistant. Further, user data and models 244 can includes various models (e.g., speech recognition models, statistical language models, natural language processing models, ontology, task flow models, service models, etc.) for processing user input and determining user intent. 

In some examples, Digital Assistant Client Module 248 can utilize the various sensors, subsystems, and peripheral devices of portable multifunction device 202 to gather additional information from the surrounding environment of the portable multifunction device 202 to establish a context associated with a user, the current user interaction, and/or the current user input. In some examples, Digital Assistant Client Module 248 can provide the contextual information or a subset thereof with the user input to DA server 106 to help infer the user’sintent. In some examples, the digital assistant can also use the contextual information to determine how to prepare and deliver outputs to the user. Contextual information can be referred to as context data. 

In some examples, the contextual information that accompanies the user input can include sensor information, e.g., lighting, ambient noise, ambient temperature, images or videos of the surrounding environment, etc. In some examples, the contextual information can also include the physical state of the device, e.g., devicedevice orientation, device location, device temperature, power level, speed, acceleration, motion patterns, cellular signals strength, etc. In some examples, information related to the software state of DA server 106, e.g., running processes, installed programs, past and present network activities, background services, error logs, resources usage, etc., and of portable multifunction device 202 can be provided to DA server 106 as contextual information associated with a user input. 

In some examples, the Digital Assistant Client Module 248 can selectively provide information (e.g., user data 244) stored on the portable multifunction device 202 in response to requests from DA server 106. In some examples, Digital Assistant Client Module 248 can also elicit additional input from the user via a natural language dialogue or other user interfaces upon request by DA server 106. Digital Assistant Client Module 248 can pass the additional input to DA server 106 to help DA server 106 in intent deduction and/or fulfillment of the user’sintent expressed in the user request. 

A more detailed description of a digital assistant is described below with reference to FIGS. 7A-C. It should be recognized that Digital Assistant Client Module 248 can include any number of the sub-modules of digital assistant module 726 described below. 

Applications 226 may include the following modules (or sets of instructions), or a subset or superset thereof: [0087] contacts module 240 (sometimes called an address book or contact list); [0088] telephone module 243; [0089] video conference module 228; [0090] e-mail client module 212; [0091] instant messaging (IM) module 224; [0092] workout support module 242; [0093] camera module 236 for still and/or video images; [0094] image management module 230; [0095] video player module; [0096] music player module; [0097] browser module 274; [0098] calendar module 268; [0099] widget modules 262, which may include one or more of: weather widget 256, stocks widget 254, calculator widget 250, alarm clock widget 246, dictionary widget 238, and other widgets obtained by the user, as well as user-created widgets 220; [0100] widget creator module 210 for making user-created widgets 220; [0101] search module 272; [0102] video and music player module 218, which merges video player module and music player module; [0103] notes module 222; [0104] map module 214; and/or [0105] online video module 264. 

Examples of other applications 226 that may be stored in memory 206 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication. 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, contacts module 240 may be used to manage an address book or contact list (e.g., stored in application internal state 332 of contacts module 240 in memory 206or memory 470), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 243, video conference module 228, e-mail 212, or IM 224; and so forth. 

In conjunction with RF circuitry 300, audio circuitry 306, speaker 310, microphone 308, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, telephone module 243 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in contacts module 240, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation, and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols, and technologies. 

In conjunction with RF circuitry 300, audio circuitry 306, speaker 310, microphone 308, touch screen 278, display controller 280, optical sensor 296, optical sensor controller 292, contact/motion module 270, graphics module 266, text input module 258, contacts module 240, and telephone module 243, video conference module 228 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, e-mail client module 212 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 230, e-mail client module 212 makes it very easy to create and send e-mails with still or video images taken with camera module 236. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, the instant messaging module 224 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for internet-based instant messages), to receive instant messages, and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in an MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS). 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, GPS module 252, map module 214, and music player module, workout support module 242 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store, and transmit workout data. 

In conjunction with touch screen 278, display controller 280, optical sensor(s) 296, optical sensor controller 292, contact/motion module 270, graphics module 266, and image management module 230, camera module 236 includes executable instructions to capture still images or video (including a video stream) and store them into memory 206, modify characteristics of a still image or video, or delete a still image or video from memory 206. 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, and camera module 236, image management module 230 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, browser module 274 includes executable instructions to browse the internet in accordance with user instructions, including searching, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, e-mail client module 212, and browser module 274, calendar module 268 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to-do lists, etc.) in accordance with user instructions. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, and browser module 274, widget modules 262 are mini-applications that may be downloaded and used by a user (e.g., weather widget 262-1, stocks widget 254, calculator widget 250, alarm clock widget 246, and dictionary widget 238) or created by the user (e.g., user-created widget 220). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widgets). 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, and browser module 274, the widget creator module 210 may be used by a user to create widgets (e.g., turning a user-specified portion of a web page into a widget). 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, search module 272 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 206 that match one or more search criteria (e.g., one or more user-specified searchterms) in accordance with user instructions. 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, audio circuitry 306, speaker 310, RF circuitry 300, and browser module 274, video and music player module 218 includes executable instructions that allow the user to download and playback recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present, or otherwise play backvideos (e.g., on touch screen 278 or on an external, connected display via external port 314). In some embodiments, device 202 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.). 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, and text input module 258, notes module 222 includes executable instructions to create and manage notes, to-do lists, and the like in accordance with user instructions. 

In conjunction with RF circuitry 300, touch screen 278, display controller 280, contact/motion module 270, graphics module 266, text input module 258, GPS module 252, and browser module 274, map module 214 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions, data on stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions. 

In conjunction with touch screen 278, display controller 280, contact/motion module 270, graphics module 266, audio circuitry 306, speaker 310, RF circuitry 300, text input module 258, e-mail client module 212, and browser module 274, online video module 264 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 314), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 224, rather than e-mail client module 212, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “portable multifunction device, method, and Graphical User Interface for Playing online videos,” filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “portable multifunction device, method, and Graphical User Interface for Playing online videos,” filed Dec. 31, 2007, the contents of which are hereby incorporated by reference in their entirety. 

Each of the above-identified modules and applications corresponds to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise rearranged in various embodiments. For example, video player module may be combined with music player module into a single module (e.g., video and music player module 218, Figure 2). In some embodiments, memory 206 may store a subset of the modules and data structures identified above. Furthermore, memory 206 may storeadditional modulesmodules and data structures not described above. 

In some embodiments, device 202 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 202, the number of physical input control devices (such as push buttons, dials, and the like) on device 202 may be reduced. 

The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 202 to a main, home, or root menu from any user interface that is displayed on device 202. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad. 

Figure 3 is a block diagram illustratingexemplary components for event handling in accordance with some embodiments. In some embodiments, memory 206 (Figure 2) or 470 (FIG. 4) includes event sorter 338 (e.g., in operating system 208) and a respective application 226

event sorter 338 receives event information and determines the application 226 and application view 302 of application 226 to which to deliver the event information. Event sorter 338 includes event monitor 308 and event dispatcher module 322. In some embodiments, application 226 includes application internal state 332, which indicates the current application view(s) displayed on touch-sensitive display 278 when the application is active or executing. In some embodiments, devicedevice/global internal state 232 is used by event sorter 338 to determine which application(s) is (are) currently active, and application internal state 332 is used by event sorter 338 to determine application views 302 to which to deliver event information. 

In some embodiments, application internal state 332 includes additional information, such as one or more of: resume information to be used when application 226 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 226, a state queue for enabling the user to go back to a prior state or view of application 226, and a redo/undo queue of previous actions taken by the user. 

Event monitor 308 receives event information from peripherals interface 322. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 278, as part of a multi-touch gesture). peripherals interface 322 transmits information it receives from I/O subsystem 298 or a sensor, such as proximity sensor 304, accelerometer(s) 302, and/or microphone 308 (through audio circuitry 306). information that peripherals interface 322 receives from I/O subsystem 298 includes information from touch-sensitive display 278 or a touch-sensitive surface. 

In some embodiments, event monitor 308 sends requests to the peripherals interface 322 at predetermined intervals. In response, peripherals interface 322 transmits event information. In other embodiments, peripherals interface 322 transmits event information only when there is a significant event (e.g., receiving an inputabove a predetermined noise threshold and/or for more than a predetermined duration). 

In some embodiments, event sorter 338 also includes a hit view determination module 310 and/or an active event recognizer determination module 316. 

Hit view determination module 310 provides software procedures for determining where a sub-event has taken place within one or more views when touch-sensitive display 278 displays more than one view. Views are made up of controls and other elements that a user can see on the display. 

Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture. 

Hit view determination module 310 receives information related to sub events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 310 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module 310, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view. 

Active event recognizer determination module 316determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 316determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 316determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views. 

Event dispatcher module 322 dispatches the event information to an event recognizer (e.g., event recognizer 336). In embodiments including active event recognizer determination module 316, event dispatcher module 322 delivers the event information to an event recognizer determined by active event recognizer determination module 316. In some embodiments, event dispatcher module 322stores in an event queue the event information, which is retrieved by a respective event receiver 304. 

In some embodiments, operating system 208 includes event sorter 338. Alternatively, application 226 includes event sorter 338. In yet other embodiments, event sorter 338 is a stand-alone module, or a part of another module stored in memory 206, such as contact/motion module 338. 

In some embodiments, application 226 includes a plurality of event handlers 334 and one or more application views 302, each of which includes instructions for handling touchevents that occur within a respective view of the application’suser interface. Each application view 302 of the application 226 includes one or more event recognizers 336. Typically, a respective application view 302 includes a plurality of event recognizers 336. In other embodiments, one or more of event recognizers 336 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 226 inherits methods and other properties. In some embodiments, a respective event handler 334 includes one or more of: data updater 306, object updater 314, GUI updater 330, and/or event data 328 received from event sorter 338. Event handler 334 may utilize or call data updater 306, object updater 314, or GUI updater 330 to update the application internal state 332. Alternatively, one or more of the application views 302 include one or more respective event handlers 334. Also, in some embodiments, one or more of data updater 306, object updater 314, and GUI updater 330 are included in a respective application view 302. 

A respective event recognizer 336 receives event information (e.g., event data 328) from event sorter 338 and identifies an event from the event information. Event recognizer 336 includes event receiver 304 and event comparator 312. In some embodiments, event recognizer 336 also includes at least a subset of: metadata 318, and event delivery instructions 226 (which may include sub-event delivery instructions). 

event receiver 304 receives event information from event sorter 338. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch, the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device. 

Event comparator 312 compares the event information to predefined eventevent or sub-eventsub-event definitions and, based on the comparison, determines an event or sub event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 312 includes event definitions 286. Event definitions 286 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (324), event 2 (320), and others. In some embodiments, sub-events in an event (287) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (324) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first liftoff (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second liftoff (touch end) for a predetermined phase. In another example, the definition for event 2 (320) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 278, and liftoff of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 334. 

In some embodiments, event definition 287 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 312 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 278, when a touch is detected on touch-sensitive display 278, event comparator 312 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 334, the event comparator uses the result of the hit test to determine which event handler 334 should be activated. For example, event comparator 312 selects an event handler associated with the sub-event and the object triggering the hit test. 

In some embodiments, the definition for a respective event (287) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer’sevent type. 

When a respective event recognizer 336 determines that the series of sub-events do not match any of the events in event definitions 286, the respective event recognizer 336 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and processsub-events of an ongoing touch-based gesture. 

In some embodiments, a respective event recognizer 336 includes metadata 318 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 318 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 318 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy. 

In some embodiments, a respective event recognizer 336 activates event handler 334 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 336 delivers event information associated with the event to event handler 334. Activating an event handler 334 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 336 throws a flag associated with the recognized event, and event handler 334 associated with the flag catches the flag and performs a predefined process. 

In some embodiments, event delivery instructions 226 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructionsdeliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process. 

In some embodiments, data updater 306 creates and updates data used in application 226. For example, data updater 306 updates the telephone number used in contacts module 240, or stores a video file used in video player module. In some embodiments, object updater 314 creates and updates objects used in application 226. For example, object updater 314 creates a new user-interface object or updates the position of a user-interface object. GUI updater 330 updates the GUI. For example, GUI updater 330 prepares display information and sends it to graphics module 266 for display on a touch-sensitive display. 

In some embodiments, event handler(s) 334 includes or has access to data updater 306, object updater 314, and GUI updater 330. In some embodiments, data updater 306, object updater 314, and GUI updater 330 are included in a single module of a respective application 226 or application view 302. In other embodiments, they are included in two or more software modules. 

It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 200 with input devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc. on touchpads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.