US20160098598A1

US20160098598A1 - Dynamic vector map tiles

Info

Publication number: US20160098598A1
Application number: US14/842,782
Authority: US
Inventors: Aroon Pahwa; Brian A. Lenoski; Mathieu Courtemanche
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2014-09-02
Filing date: 2015-09-01
Publication date: 2016-04-07
Anticipated expiration: 2035-09-01
Also published as: WO2016036772A1; US9798926B2; WO2016036772A4

Abstract

The present disclosure relates to systems and processes for providing vector map data for generating a view of a map in a mapping application. In one example process, a request for a vector map sub-tile can be received by a map server. The map server can identify a pre-generated vector map tile corresponding to the requested vector map sub-tile and can generate the requested vector map sub-tile from the identified vector map tile by dividing the vector map tile into two or more vector map sub-tiles. In some examples, dividing the vector map tile into multiple vector map sub-tiles can include identifying features and attributes of the vector map tile that should be included in the requested vector map sub-tile and generating the requested vector map sub-tile to include these features and attributes. The map server can then transmit the requested vector map sub-tile to the requesting electronic device.

Description

BACKGROUND

1. Field
The present disclosure relates generally to mapping applications and, more specifically, to providing dynamic vector map data to display portions of a map in a mapping application.
2. Description of Related Art
Mapping applications have become increasingly popular due to the proliferation of location-aware mobile electronic devices. Typically, a map displayed by a mapping application can be defined by a set of map tiles. These map tiles can either include a raster image, in which the contents of the image are represented by a rectangular grid of colored pixels, or a vector image, in which contents of the image are represented by geometric primitives, such as points, lines, polygons, and the like. For an electronic device to display a desired view of a map, the electronic device can access map tiles corresponding to the viewable area of the map and can render an image based on these map tiles. As users interact with these mapping applications to pan, zoom, or rotate the view of the map, other map tiles can be accessed and used to render updated views.
Conventional mapping systems typically include a set of pre-generated map tiles that can be provided in response to a request from an electronic device. These pre-generated map tiles are typically sized based on the screen size of the electronic device expected to receive the map tiles. For example, the pre-generated map tiles can be sized to prevent the need to use a large number of map tiles to display a portion of a map while avoiding situations in which a large portion of a map tile is located outside the view of the device. While such a system can be used to effectively service requests from most electronic devices, problems can occur when requesting electronic devices have widely varying screen sizes or when a requesting electronic device has a relatively small amount of memory and/or limited bandwidth. For example, a compact mobile electronic device, such as a mobile phone or watch, may have insufficient memory to store large map tiles designed for desktop computers. Additionally, compact mobile electronic devices may lack communication means having a sufficient bandwidth to receive large map tiles at a rate that allows the device to display updates to a map in a timely manner.
Accordingly, there is a need for improved techniques for providing map tiles for mapping applications.

BRIEF SUMMARY

The present disclosure relates to systems and processes for providing vector map data for use in generating a view of a map by a mapping application. In one example process, a request for a vector map sub-tile can be received by a map server. The map server can identify a pre-generated vector map tile corresponding to the requested vector map sub-tile and can generate the requested vector map sub-tile from the identified vector map tile by dividing the vector map tile into two or more vector map sub-tiles. In some examples, dividing the vector map tile into multiple vector map sub-tiles can include identifying features and attributes of the vector map tile that should be included in the requested vector map sub-tile and generating the requested vector map sub-tile to include these features and attributes. The map server can then transmit the requested vector map sub-tile to the requesting electronic device.

DESCRIPTION OF THE FIGURES

FIG. 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some examples.

FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some examples.

FIG. 2 illustrates a portable multifunction device having a touch-sensitive display in accordance with some examples.

FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some examples.

FIGS. 4A and 4B illustrate an exemplary user interface for a menu of applications on a portable multifunction device in accordance with some examples.

FIG. 5A is a block diagram illustrating a portable multifunction device with a touch-sensitive display in accordance with some examples.

FIG. 5B illustrates a portable multifunction device having a touch-sensitive display in accordance with some examples.

FIG. 6 illustrates a block diagram of an exemplary system for providing vector map data for use in generating a view of a map by a mapping application according to various examples.

FIG. 7 illustrates an exemplary process for providing vector map data for use in generating a view of a map by a mapping application according to various examples.

FIG. 8 illustrates an exemplary vector map tile according to various examples.

FIG. 9 illustrates exemplary vector map sub-tiles that can be generated from the vector map tile shown in FIG. 8 according to various examples.

FIG. 10 illustrates an exemplary process that can be used to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIG. 11 illustrates another exemplary process that can be used to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIGS. 12-15 illustrate the processing of an exemplary map feature to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIG. 16 illustrates another exemplary process that can be used to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIGS. 17-18 illustrate the processing of an exemplary map feature to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIG. 19 illustrates another exemplary process that can be used to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIG. 20 illustrates the processing of an exemplary map feature to divide a vector map tile into multiple vector map sub-tiles according to various examples.

FIG. 21 illustrates an exemplary vector map sub-tile that can be generated from the vector map tile shown in FIG. 8 according to various examples.

FIG. 22 illustrates a functional block diagram of an electronic device according to various examples.

DETAILED DESCRIPTION

The following description sets forth exemplary methods, parameters and the like. It should be recognized, however, that such description is not intended as a limitation on the scope of the present disclosure but is instead provided as a description of exemplary embodiments.
The present disclosure relates to systems and processes for providing vector map data for use in generating a view of a map by a mapping application. In one example process, a request for a vector map sub-tile can be received by a map server. The map server can identify a pre-generated vector map tile corresponding to the requested vector map sub-tile and can generate the requested vector map sub-tile from the identified vector map tile by dividing the vector map tile into two or more vector map sub-tiles. In some examples, dividing the vector map tile into multiple vector map sub-tiles can include identifying features and attributes of the vector map tile that should be included in the requested vector map sub-tile and generating the requested vector map sub-tile to include these features and attributes. The map server can then transmit the requested vector map sub-tile to the requesting electronic device.
Below, FIGS. 1A-1B, 2, 3, and 5A-5B provide a description of exemplary devices for providing and receiving vector map tiles used to display portions of a map in a mapping application. FIGS. 4A-4B illustrate exemplary user interfaces that can be displayed on these exemplary devices.
Although the following description uses terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, a first touch could be termed a second touch, and, similarly, a second touch could be termed a first touch, without departing from the scope of the various described embodiments. The first touch and the second touch are both touches, but they are not the same touch.
The terminology used in the description of the various described embodiments herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “includes”, “including”, “comprises”, and/or “comprising”, when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting”, depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event]”, depending on the context.
Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described. In some embodiments, the device is a portable communications device, such as a mobile telephone, that also contains other functions, such as PDA and/or music player functions. Exemplary embodiments of portable multifunction devices include, without limitation, the iPhone®, iPod Touch®, and iPad® devices from Apple Inc. of Cupertino, Calif. Other portable electronic devices, such as laptops or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and/or touch pads), are, optionally, used. It should also be understood that, in some embodiments, the device is not a portable communications device, but is a desktop computer with a touch-sensitive surface (e.g., a touch screen display and/or a touch pad).
In the discussion that follows, an electronic device that includes a display and a touch-sensitive surface is described. It should be understood, however, that the electronic device optionally includes one or more other physical user-interface devices, such as a physical keyboard, a mouse and/or a joystick.
The device may support a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk authoring application, a spreadsheet application, a gaming application, a telephone application, a video conferencing application, an e-mail application, an instant messaging application, a workout support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and/or a digital video player application.
The various applications that are executed on the device optionally use at least one common physical user-interface device, such as the touch-sensitive surface. One or more functions of the touch-sensitive surface as well as corresponding information displayed on the device are, optionally, adjusted and/or varied from one application to the next and/or within a respective application. In this way, a common physical architecture (such as the touch-sensitive surface) of the device optionally supports the variety of applications with user interfaces that are intuitive and transparent to the user.
Attention is now directed toward embodiments of portable devices with touch-sensitive displays. FIG. 1A is a block diagram illustrating portable multifunction device 100 with touch-sensitive displays 112 in accordance with some embodiments. Touch-sensitive display 112 is sometimes called a “touch screen” for convenience, and is sometimes known as or called a touch-sensitive display system. Device 100 includes memory 102 (which optionally includes one or more computer readable storage mediums), memory controller 122, one or more processing units (CPU″s) 120, peripherals interface 118, RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, input/output (I/O) subsystem 106, other input or control devices 116, and external port 124. Device 100 optionally includes one or more optical sensors 164. Device 100 optionally includes one or more intensity sensors 165 for detecting intensity of contacts on device 100 (e.g., a touch-sensitive surface such as touch-sensitive display system 112 of device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile outputs on device 100 (e.g., generating tactile outputs on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touchpad 355 of device 300). These components optionally communicate over one or more communication buses or signal lines 103.
As used in the specification and claims, the term “intensity” of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch sensitive surface, or to a substitute (proxy) for the force or pressure of a contact on the touch sensitive surface. The intensity of a contact has a range of values that includes at least four distinct values and more typically includes hundreds of distinct values (e.g., at least 256). Intensity of a contact is, optionally, determined (or measured) using various approaches and various sensors or combinations of sensors. For example, one or more force sensors underneath or adjacent to the touch-sensitive surface are, optionally, used to measure force at various points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., a weighted average) to determine an estimated force of a contact. Similarly, a pressure-sensitive tip of a stylus is, optionally, used to determine a pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and/or changes thereto, the capacitance of the touch-sensitive surface proximate to the contact and/or changes thereto, and/or the resistance of the touch-sensitive surface proximate to the contact and/or changes thereto are, optionally, used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some implementations, the substitute measurements for contact force or pressure are used directly to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurements). In some implementations, the substitute measurements for contact force or pressure are converted to an estimated force or pressure and the estimated force or pressure is used to determine whether an intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of a contact as an attribute of a user input allows for user access to additional device functionality that may otherwise not be accessible by the user on a reduced-size device with limited real estate for displaying affordances (e.g., on a touch-sensitive display) and/or receiving user input (e.g., via a touch-sensitive display, a touch-sensitive surface, or a physical/mechanical control such as a knob or a button).
As used in the specification and claims, the term “tactile output” refers to physical displacement of a device relative to a previous position of the device, physical displacement of a component (e.g., a touch-sensitive surface) of a device relative to another component (e.g., housing) of the device, or displacement of the component relative to a center of mass of the device that will be detected by a user with the user-s sense of touch. For example, in situations where the device or the component of the device is in contact with a surface of a user that is sensitive to touch (e.g., a finger, palm, or other part of a user-s hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in physical characteristics of the device or the component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is, optionally, interpreted by the user as a “down click” or “up click” of a physical actuator button. In some cases, a user will feel a tactile sensation such as an “down click” or “up click” even when there is no movement of a physical actuator button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user-s movements. As another example, movement of the touch-sensitive surface is, optionally, interpreted or sensed by the user as “roughness” of the touch-sensitive surface, even when there is no change in smoothness of the touch-sensitive surface. While such interpretations of touch by a user will be subject to the individualized sensory perceptions of the user, there are many sensory perceptions of touch that are common to a large majority of users. Thus, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., an “up click”, a “down click”, “roughness”), unless otherwise stated, the generated tactile output corresponds to physical displacement of the device or a component thereof that will generate the described sensory perception for a typical (or average) user.
It should be appreciated that device 100 is only one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. The various components shown in FIG. 1A 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 102 may include one or more computer readable storage mediums. The computer readable storage mediums may be tangible and non-transitory. Memory 102 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Memory controller 122 may control access to memory 102 by other components of device 100.
Peripherals interface 118 can be used to couple input and output peripherals of the device to CPU 120 and memory 102. The one or more processors 120 run or execute various software programs and/or sets of instructions stored in memory 102 to perform various functions for device 100 and to process data. In some embodiments, peripherals interface 118, CPU 120, and memory controller 122 may be implemented on a single chip, such as chip 104. In some other embodiments, they may be implemented on separate chips.
RF (radio frequency) circuitry 108 receives and sends RF signals, also called electromagnetic signals. RF circuitry 108 converts electrical signals to/from electromagnetic signals and communicates with communications networks and other communications devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a CODEC chipset, a subscriber identity module (SIM) card, memory, and so forth. RF circuitry 108 optionally communicates with networks, such as the Internet, also referred to as the World Wide Web (WWW), an intranet and/or a wireless network, such as a cellular telephone network, a wireless local area network (LAN) and/or a metropolitan area network (MAN), and other devices by wireless communication. The wireless communication optionally uses any of a plurality of communications standards, protocols and technologies, including but not limited to Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), high-speed downlink packet access (HSDPA), high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), near field communication (NFC), wideband code division multiple access (W-CDMA), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet message access protocol (IMAP) and/or post office protocol (POP)), instant messaging (e.g., extensible messaging and presence protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Leveraging Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)), and/or Short Message Service (SMS), or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document.
Audio circuitry 110, speaker 111, and microphone 113 provide an audio interface between a user and device 100. Audio circuitry 110 receives audio data from peripherals interface 118, converts the audio data to an electrical signal, and transmits the electrical signal to speaker 111. Speaker 111 converts the electrical signal to human-audible sound waves. Audio circuitry 110 also receives electrical signals converted by microphone 113 from sound waves. Audio circuitry 110 converts the electrical signal to audio data and transmits the audio data to peripherals interface 118 for processing. Audio data may be retrieved from and/or transmitted to memory 102 and/or RF circuitry 108 by peripherals interface 118. In some embodiments, audio circuitry 110 also includes a headset jack (e.g., 212, FIG. 2). The headset jack provides an interface between audio circuitry 110 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 106 couples input/output peripherals on device 100, such as touch screen 112 and other input control devices 116, to peripherals interface 118. I/O subsystem 106 optionally includes display controller 156, optical sensor controller 158, intensity sensor controller 159, haptic feedback controller 161 and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive/send electrical signals from/to other input or control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slider switches, joysticks, click wheels, and so forth. In some alternate embodiments, input controller(s) 160 are, optionally, coupled to any (or none) of the following: a keyboard, infrared port, USB port, and a pointer device such as a mouse. The one or more buttons (e.g., 208, FIG. 2) optionally include an up/down button for volume control of speaker 111 and/or microphone 113. The one or more buttons optionally include a push button (e.g., 206, FIG. 2).
A quick press of the push button may disengage a lock of touch screen 112 or begin a process that uses gestures on the touch screen to unlock the device, as described in U.S. patent application Ser. No. 11/322,549, “Unlocking a Device by Performing Gestures on an Unlock Image”, filed Dec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated by reference in its entirety. A longer press of the push button (e.g., 206) may turn power to device 100 on or off. The user may be able to customize a functionality of one or more of the buttons. Touch screen 112 is used to implement virtual or soft buttons and one or more soft keyboards.
Touch-sensitive display 112 provides an input interface and an output interface between the device and a user. Display controller 156 receives and/or sends electrical signals from/to touch screen 112. Touch screen 112 displays visual output to the user. The visual output may include graphics, text, icons, video, and any combination thereof (collectively termed “graphics”). In some embodiments, some or all of the visual output may correspond to user-interface objects.
Touch screen 112 has a touch-sensitive surface, sensor or set of sensors that accepts input from the user based on haptic and/or tactile contact. Touch screen 112 and display controller 156 (along with any associated modules and/or sets of instructions in memory 102) detect contact (and any movement or breaking of the contact) on touch screen 112 and converts the detected contact into interaction with user-interface objects (e.g., one or more soft keys, icons, web-pages or images) that are displayed on touch screen 112. In an exemplary embodiment, a point of contact between touch screen 112 and the user corresponds to a finger of the user.
Touch screen 112 may use LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies may be used in other embodiments. Touch screen 112 and display controller 156 may detect contact and any movement or breaking thereof using any of a plurality of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch screen 112. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as that found in the iPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.
A touch-sensitive display in some embodiments of touch screen 112 may be analogous to the multi-touch sensitive touchpads described in the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, whereas touch sensitive touchpads do not provide visual output.
A touch-sensitive display in some embodiments of touch screen 112 may be as described in the following applications: (1) U.S. patent application Ser. No. 11/381,313, “Multipoint Touch Surface Controller”, filed May 2, 2006; (2) U.S. patent application Ser. No. 10/840,862, “Multipoint Touchscreen”, filed May 6, 2004; (3) U.S. patent application Ser. No. 10/903,964, “Gestures For Touch Sensitive Input Devices”, filed Jul. 30, 2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures For Touch Sensitive Input Devices”, filed Jan. 31, 2005; (5) U.S. patent application Ser. No. 11/038,590, “Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”, filed Jan. 18, 2005; (6) U.S. patent application Ser. No. 11/228,758, “Virtual Input Device Placement On A Touch Screen User Interface”, filed Sep. 16, 2005; (7) U.S. patent application Ser. No. 11/228,700, “Operation Of A Computer With A Touch Screen Interface”, filed Sep. 16, 2005; (8) U.S. patent application Ser. No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”, filed Sep. 16, 2005; and (9) U.S. patent application Ser. No. 11/367,749, “Multi-Functional Hand-Held Device”, filed Mar. 3, 2006. All of these applications are incorporated by reference herein in their entirety.
Touch screen 112 may have a video resolution in excess of 100 dpi. In some embodiments, the touch screen has a video resolution of approximately 160 dpi. The user may make contact with touch screen 112 using any suitable object or appendage, such as a stylus, a finger, and so forth. In some embodiments, the user interface is designed to work primarily with finger-based contacts and gestures, which can be less precise than stylus-based input due to the larger area of contact of a finger on the touch screen. In some embodiments, the device translates the rough finger-based input into a precise pointer/cursor position or command for performing the actions desired by the user.
In some embodiments, in addition to the touch screen, device 100 may include a touchpad (not shown) for activating or deactivating particular functions. In some embodiments, the touchpad is a touch-sensitive area of the device that, unlike the touch screen, does not display visual output. The touchpad may be a touch-sensitive surface that is separate from touch screen 112 or an extension of the touch-sensitive surface formed by the touch screen.
Device 100 also includes power system 162 for powering the various components. Power system 162 may include a power management system, one or more power sources (e.g., battery, alternating current (AC)), a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator (e.g., a light-emitting diode (LED)) and any other components associated with the generation, management and distribution of power in portable devices.
Device 100 may also include one or more optical sensors 164. FIGS. 1A and 1B show an optical sensor coupled to optical sensor controller 158 in I/O subsystem 106. Optical sensor 164 may include charge-coupled device (CCD) or complementary metal-oxide semiconductor (CMOS) phototransistors. Optical sensor 164 receives light from the environment, projected through one or more lens, and converts the light to data representing an image. In conjunction with imaging module 143 (also called a camera module), optical sensor 164 may capture still images or video. In some embodiments, an optical sensor is located on the back of device 100, opposite touch screen display 112 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-s image may be obtained for videoconferencing while the user views the other video conference participants on the touch screen display. In some embodiments, the position of optical sensor 164 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 164 may be used along with the touch screen display for both video conferencing and still and/or video image acquisition.
Device 100 optionally also includes one or more contact intensity sensors 165. FIG. 1A shows a contact intensity sensor coupled to intensity sensor controller 159 in I/O subsystem 106. Contact intensity sensor 165 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 165 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 112). In some embodiments, at least one contact intensity sensor is located on the back of device 100, opposite touch screen display 112 which is located on the front of device 100.
Device 100 may also include one or more proximity sensors 166. FIGS. 1A and 1B show proximity sensor 166 coupled to peripherals interface 118. Alternately, proximity sensor 166 may be coupled to input controller 160 in I/O subsystem 106. Proximity sensor 166 may perform as described in U.S. patent application Ser. No. 11/241,839, “Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “Proximity Detector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient Light Sensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862, “Automated Response To And Sensing Of User Activity In Portable Devices”; and Ser. No. 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 112 when the multifunction device is placed near the user-s ear (e.g., when the user is making a phone call).
Device 100 optionally also includes one or more tactile output generators 167. FIG. 1A shows a tactile output generator coupled to haptic feedback controller 161 in I/O subsystem 106. Tactile output generator 167 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 165 receives tactile feedback generation instructions from haptic feedback module 133 and generates tactile outputs on device 100 that are capable of being sensed by a user of device 100. 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 112) and, optionally, generates a tactile output by moving the touch-sensitive surface vertically (e.g., in/out of a surface of device 100) or laterally (e.g., back and forth in the same plane as a surface of device 100). In some embodiments, at least one tactile output generator sensor is located on the back of device 100, opposite touch screen display 112 which is located on the front of device 100.
Device 100 may also include one or more accelerometers 168. FIGS. 1A and 1B show accelerometer 168 coupled to peripherals interface 118. Alternately, accelerometer 168 may be coupled to an input controller 160 in I/O subsystem 106. Accelerometer 168 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 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 100 optionally includes, in addition to accelerometer(s) 168, 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 100.
In some embodiments, the software components stored in memory 102 include operating system 126, communication module (or set of instructions) 128, contact/motion module (or set of instructions) 130, graphics module (or set of instructions) 132, text input module (or set of instructions) 134, Global Positioning System (GPS) module (or set of instructions) 135, and applications (or sets of instructions) 136. Furthermore, in some embodiments memory 102 stores device/global internal state 157, as shown in FIGS. 1A, lB and 3. Device/global internal state 157 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 112; sensor state, including information obtained from the device″s various sensors and input control devices 116; and location information concerning the device″s location and/or attitude.
Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and/or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.) and facilitates communication between various hardware and software components.
Communication module 128 facilitates communication with other devices over one or more external ports 124 and also includes various software components for handling data received by RF circuitry 108 and/or external port 124. External port 124 (e.g., Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly to other devices or indirectly over a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is a multi-pin (e.g., 30-pin) connector that is the same as, or similar to and/or compatible with the 30-pin connector used on iPod® (trademark of Apple Inc.) devices.
Contact/motion module 130 optionally detects contact with touch screen 112 (in conjunction with display controller 156) and other touch sensitive devices (e.g., a touchpad or physical click wheel). Contact/motion module 130 includes various software components for performing various operations related to detection of contact, such as determining if contact has occurred (e.g., detecting a finger-down event), determining an intensity of the contact (e.g., the force or pressure of the contact or a substitute for the force or pressure of the contact) determining if there is movement of the contact and tracking the movement across the touch-sensitive surface (e.g., detecting one or more finger-dragging events), and determining if the contact has ceased (e.g., detecting a finger-up event or a break in contact). Contact/motion module 130 receives contact data from the touch-sensitive surface. Determining movement of the point of contact, which is represented by a series of contact data, optionally includes determining speed (magnitude), velocity (magnitude and direction), and/or an acceleration (a change in magnitude and/or direction) of the point of contact. These operations are, optionally, applied to single contacts (e.g., one finger contacts) or to multiple simultaneous contacts (e.g., “multitouch”/multiple finger contacts). In some embodiments, contact/motion module 130 and display controller 156 detect contact on a touchpad.
In some embodiments, contact/motion module 130 uses a set of one or more intensity thresholds to determine whether an operation has been performed by a user (e.g., to determine whether a user has “clicked” on an icon). In some embodiments at least a subset of the intensity thresholds are determined in accordance with software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of particular physical actuators and can be adjusted without changing the physical hardware of device 100). For example, a mouse “click” threshold of a trackpad or touch screen display can be set to any of a large range of predefined thresholds values without changing the trackpad or touch screen display hardware. Additionally, in some implementations a user of the device is provided with software settings for adjusting one or more of the set of intensity thresholds (e.g., by adjusting individual intensity thresholds and/or by adjusting a plurality of intensity thresholds at once with a system-level click “intensity” parameter).
Contact/motion module 130 optionally detects a gesture input by a user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and/or intensities of detected contacts). Thus, a gesture is, optionally, detected by detecting a particular contact pattern. For example, detecting a finger tap gesture includes detecting a finger-down event followed by detecting a finger-up (lift off) event at the same position (or substantially the same position) as the finger-down event (e.g., at the position of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger-down event followed by detecting one or more finger-dragging events, and subsequently followed by detecting a finger-up (lift off) event.
Graphics module 132 includes various known software components for rendering and displaying graphics on touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast or other visual property) of graphics that are displayed. As used herein, the term “graphics” includes any object that can be displayed to a user, including without limitation text, web pages, icons (such as user-interface objects including soft keys), digital images, videos, animations and the like.
In some embodiments, graphics module 132 stores data representing graphics to be used. Each graphic is, optionally, assigned a corresponding code. Graphics module 132 receives, from applications etc., one or more codes specifying graphics to be displayed along with, if necessary, coordinate data and other graphic property data, and then generates screen image data to output to display controller 156.
Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator(s) 167 to produce tactile outputs at one or more locations on device 100 in response to user interactions with device 100.
Text input module 134, which may be a component of graphics module 132, provides soft keyboards for entering text in various applications (e.g., contacts 137, e-mail 140, IM 141, browser 147, and any other application that needs text input).
GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to telephone 138 for use in location-based dialing, to camera 143 as picture/video metadata, and to applications that provide location-based services such as weather widgets, local yellow page widgets, and map/navigation widgets).
Applications 136 may include the following modules (or sets of instructions), or a subset or superset thereof:

- contacts module 137 (sometimes called an address book or contact list);
- telephone module 138;
- video conferencing module 139;
- e-mail client module 140;
- instant messaging (IM) module 141;
- workout support module 142;
- camera module 143 for still and/or video images;
- image management module 144;
- video player module 145;
- music player module 146;
- browser module 147;
- calendar module 148;
- widget modules 149, which may include one or more of: weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, as well as user-created widgets 149-6;
- widget creator module 150 for making user-created widgets 149-6;
- search module 151;
- video and music player module 152, which merges video player module 145 and music player module 146;
- notes module 153;
- map module 154; and/or
- online video module 155.

Examples of other applications 136 that may be stored in memory 102 include other word processing applications, other image editing applications, drawing applications, presentation applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, contacts module 137 may be used to manage an address book or contact list (e.g., stored in application internal state 192 of contacts module 137 in memory 102 or memory 370), including: adding name(s) to the address book; deleting name(s) from the address book; associating telephone number(s), e-mail address(es), physical address(es) or other information with a name; associating an image with a name; categorizing and sorting names; providing telephone numbers or e-mail addresses to initiate and/or facilitate communications by telephone 138, video conference 139, e-mail 140, or IM 141; and so forth.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, telephone module 138 may be used to enter a sequence of characters corresponding to a telephone number, access one or more telephone numbers in address book 137, modify a telephone number that has been entered, dial a respective telephone number, conduct a conversation and disconnect or hang up when the conversation is completed. As noted above, the wireless communication may use any of a plurality of communications standards, protocols and technologies.
In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and telephone module 138, videoconferencing module 139 includes executable instructions to initiate, conduct, and terminate a video conference between a user and one or more other participants in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, e-mail client module 140 includes executable instructions to create, send, receive, and manage e-mail in response to user instructions. In conjunction with image management module 144, e-mail client module 140 makes it very easy to create and send e-mails with still or video images taken with camera module 143.
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the instant messaging module 141 includes executable instructions to enter a sequence of characters corresponding to an instant message, to modify previously entered characters, to transmit a respective instant message (for example, using a Short Message Service (SMS) or Multimedia Message Service (MMS) protocol for telephony-based instant messages or using XMPP, SIMPLE, or IMPS for Internet-based instant messages), to receive instant messages and to view received instant messages. In some embodiments, transmitted and/or received instant messages may include graphics, photos, audio files, video files and/or other attachments as are supported in a MMS and/or an Enhanced Messaging Service (EMS). As used herein, “instant messaging” refers to both telephony-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).
In conjunction with RF circuitry 108, touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, workout support module 142 includes executable instructions to create workouts (e.g., with time, distance, and/or calorie burning goals); communicate with workout sensors (sports devices); receive workout sensor data; calibrate sensors used to monitor a workout; select and play music for a workout; and display, store and transmit workout data.
In conjunction with touch screen 112, display controller 156, optical sensor(s) 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions to capture still images or video (including a video stream) and store them into memory 102, modify characteristics of a still image or video, or delete a still image or video from memory 102.
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions to arrange, modify (e.g., edit), or otherwise manipulate, label, delete, present (e.g., in a digital slide show or album), and store still and/or video images.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, browser module 147 includes executable instructions to browse the Internet in accordance with user instructions, including searching, linking to, receiving, and displaying web-pages or portions thereof, as well as attachments and other files linked to web-pages.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, e-mail client module 140, and browser module 147, calendar module 148 includes executable instructions to create, display, modify, and store calendars and data associated with calendars (e.g., calendar entries, to do lists, etc.) in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, widget modules 149 are mini-applications that may be downloaded and used by a user (e.g., weather widget 149-1, stocks widget 149-2, calculator widget 149-3, alarm clock widget 149-4, and dictionary widget 149-5) or created by the user (e.g., user-created widget 149-6). In some embodiments, a widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, a widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! Widgets).
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, and browser module 147, the widget creator module 150 may be used by a user to create widgets (e.g., turning a user-specified portion of a web-page into a widget).
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, and text input module 134, search module 151 includes executable instructions to search for text, music, sound, image, video, and/or other files in memory 102 that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow the user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions to display, present or otherwise play back videos (e.g., on touch screen 112 or on an external, connected display via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).
In conjunction with touch screen 112, display controller 156, contact module 130, graphics module 132, and text input module 134, notes module 153 includes executable instructions to create and manage notes, to do lists, and the like in accordance with user instructions.
In conjunction with RF circuitry 108, touch screen 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 may be used to receive, display, modify, and store maps and data associated with maps (e.g., driving directions; data on stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
In conjunction with touch screen 112, display system controller 156, contact module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, text input module 134, e-mail client module 140, and browser module 147, online video module 155 includes instructions that allow the user to access, browse, receive (e.g., by streaming and/or download), play back (e.g., on the touch screen or on an external, connected display via external port 124), send an e-mail with a link to a particular online video, and otherwise manage online videos in one or more file formats, such as H.264. In some embodiments, instant messaging module 141, rather than e-mail client module 140, is used to send a link to a particular online video. Additional description of the online video application can be found in U.S. Provisional Patent Application No. 60/936,562, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos”, filed Jun. 20, 2007, and U.S. patent application Ser. No. 11/968,067, “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos”, filed Dec. 31, 2007, the content of which is hereby incorporated by reference in its entirety.
Each of the above identified modules and applications correspond to a set of executable instructions for performing one or more functions described above and the methods described in this application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. For example, video player module 145 may be combined with music player module 146 into a single module (e.g., video and music player module 152, FIG. 1A). In some embodiments, memory 102 may store a subset of the modules and data structures identified above. Furthermore, memory 102 may store additional modules and data structures not described above.
In some embodiments, device 100 is a device where operation of a predefined set of functions on the device is performed exclusively through a touch screen and/or a touchpad. By using a touch screen and/or a touchpad as the primary input control device for operation of device 100, the number of physical input control devices (such as push buttons, dials, and the like) on device 100 may be reduced.
The predefined set of functions that are performed exclusively through a touch screen and/or a touchpad optionally include navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates device 100 to a main, home, or root menu from any user interface that is displayed on device 100. In such embodiments, a “menu button” is implemented using a touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device instead of a touchpad.
FIG. 1B is a block diagram illustrating exemplary components for event handling in accordance with some embodiments. In some embodiments, memory 102 (in FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., in operating system 126) and a respective application 136-1 (e.g., any of the aforementioned applications 137-151, 155, 380-390).
Event sorter 170 receives event information and determines the application 136-1 and application view 191 of application 136-1 to which to deliver the event information. Event sorter 170 includes event monitor 171 and event dispatcher module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates the current application view(s) displayed on touch sensitive display 112 when the application is active or executing. In some embodiments, device/global internal state 157 is used by event sorter 170 to determine which application(s) is (are) currently active, and application internal state 192 is used by event sorter 170 to determine application views 191 to which to deliver event information.
In some embodiments, application internal state 192 includes additional information, such as one or more of: resume information to be used when application 136-1 resumes execution, user interface state information that indicates information being displayed or that is ready for display by application 136-1, a state queue for enabling the user to go back to a prior state or view of application 136-1, and a redo/undo queue of previous actions taken by the user.
Event monitor 171 receives event information from peripherals interface 118. Event information includes information about a sub-event (e.g., a user touch on touch-sensitive display 112, as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I/O subsystem 106 or a sensor, such as proximity sensor 166, accelerometer(s) 168, and/or microphone 113 (through audio circuitry 110). Information that peripherals interface 118 receives from I/O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.
In some embodiments, event monitor 171 sends requests to the peripherals interface 118 at predetermined intervals. In response, peripherals interface 118 transmits event information. In other embodiments, peripheral interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and/or for more than a predetermined duration).
In some embodiments, event sorter 170 also includes a hit view determination module 172 and/or an active event recognizer determination module 173.
Hit view determination module 172 provides software procedures for determining where a sub-event has taken place within one or more views, when touch sensitive display 112 displays more than one view. Views are made up of controls and other elements that a user can see on the display.
Another aspect of the user interface associated with an application is a set of views, sometimes herein called application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of a respective application) in which a touch is detected may correspond to programmatic levels within a programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected may be called the hit view, and the set of events that are recognized as proper inputs may be determined based, at least in part, on the hit view of the initial touch that begins a touch-based gesture.
Hit view determination module 172 receives information related to sub-events of a touch-based gesture. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies a hit view as the lowest view in the hierarchy which should handle the sub-event. In most circumstances, the hit view is the lowest level view in which an initiating sub-event occurs (e.g., the first sub-event in the sequence of sub-events that form an event or potential event). Once the hit view is identified by the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
Active event recognizer determination module 173 determines which view or views within a view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of a sub-event are actively involved views, and therefore determines that all actively involved views should receive a particular sequence of sub-events. In other embodiments, even if touch sub-events were entirely confined to the area associated with one particular view, views higher in the hierarchy would still remain as actively involved views.
Event dispatcher module 174 dispatches the event information to an event recognizer (e.g., event recognizer 180). In embodiments including active event recognizer determination module 173, event dispatcher module 174 delivers the event information to an event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores in an event queue the event information, which is retrieved by a respective event receiver module 182.
In some embodiments, operating system 126 includes event sorter 170. Alternatively, application 136-1 includes event sorter 170. In yet other embodiments, event sorter 170 is a stand-alone module, or a part of another module stored in memory 102, such as contact/motion module 130.
In some embodiments, application 136-1 includes a plurality of event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events that occur within a respective view of the application″s user interface. Each application view 191 of the application 136-1 includes one or more event recognizers 180. Typically, a respective application view 191 includes a plurality of event recognizers 180. In other embodiments, one or more of event recognizers 180 are part of a separate module, such as a user interface kit (not shown) or a higher level object from which application 136-1 inherits methods and other properties. In some embodiments, a respective event handler 190 includes one or more of: data updater 176, object updater 177, GUI updater 178, and/or event data 179 received from event sorter 170. Event handler 190 may utilize or call data updater 176, object updater 177 or GUI updater 178 to update the application internal state 192. Alternatively, one or more of the application views 191 includes one or more respective event handlers 190. Also, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in a respective application view 191.
A respective event recognizer 180 receives event information (e.g., event data 179) from event sorter 170, and identifies an event from the event information. Event recognizer 180 includes event receiver 182 and event comparator 184. In some embodiments, event recognizer 180 also includes at least a subset of: metadata 183, and event delivery instructions 188 (which may include sub-event delivery instructions).
Event receiver 182 receives event information from event sorter 170. The event information includes information about a sub-event, for example, a touch or a touch movement. Depending on the sub-event, the event information also includes additional information, such as location of the sub-event. When the sub-event concerns motion of a touch the event information may also include speed and direction of the sub-event. In some embodiments, events include rotation of the device from one orientation to another (e.g., from a portrait orientation to a landscape orientation, or vice versa), and the event information includes corresponding information about the current orientation (also called device attitude) of the device.
Event comparator 184 compares the event information to predefined event or sub-event definitions and, based on the comparison, determines an event or sub-event, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definitions 186. Event definitions 186 contain definitions of events (e.g., predefined sequences of sub-events), for example, event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in an event (187) include, for example, touch begin, touch end, touch movement, touch cancellation, and multiple touching. In one example, the definition for event 1 (187-1) is a double tap on a displayed object. The double tap, for example, comprises a first touch (touch begin) on the displayed object for a predetermined phase, a first lift-off (touch end) for a predetermined phase, a second touch (touch begin) on the displayed object for a predetermined phase, and a second lift-off (touch end) for a predetermined phase. In another example, the definition for event 2 (187-2) is a dragging on a displayed object. The dragging, for example, comprises a touch (or contact) on the displayed object for a predetermined phase, a movement of the touch across touch-sensitive display 112, and lift-off of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
In some embodiments, event definition 187 includes a definition of an event for a respective user-interface object. In some embodiments, event comparator 184 performs a hit test to determine which user-interface object is associated with a sub-event. For example, in an application view in which three user-interface objects are displayed on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user-interface objects is associated with the touch (sub-event). If each displayed object is associated with a respective event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with the sub-event and the object triggering the hit test.
In some embodiments, the definition for a respective event (187) also includes delayed actions that delay delivery of the event information until after it has been determined whether the sequence of sub-events does or does not correspond to the event recognizer″s event type.
When a respective event recognizer 180 determines that the series of sub-events do not match any of the events in event definitions 186, the respective event recognizer 180 enters an event impossible, event failed, or event ended state, after which it disregards subsequent sub-events of the touch-based gesture. In this situation, other event recognizers, if any, that remain active for the hit view continue to track and process sub-events of an ongoing touch-based gesture.
In some embodiments, a respective event recognizer 180 includes metadata 183 with configurable properties, flags, and/or lists that indicate how the event delivery system should perform sub-event delivery to actively involved event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate how event recognizers may interact, or are enabled to interact, with one another. In some embodiments, metadata 183 includes configurable properties, flags, and/or lists that indicate whether sub-events are delivered to varying levels in the view or programmatic hierarchy.
In some embodiments, a respective event recognizer 180 activates event handler 190 associated with an event when one or more particular sub-events of an event are recognized. In some embodiments, a respective event recognizer 180 delivers event information associated with the event to event handler 190. Activating an event handler 190 is distinct from sending (and deferred sending) sub-events to a respective hit view. In some embodiments, event recognizer 180 throws a flag associated with the recognized event, and event handler 190 associated with the flag catches the flag and performs a predefined process.
In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver event information to event handlers associated with the series of sub-events or to actively involved views. Event handlers associated with the series of sub-events or with actively involved views receive the event information and perform a predetermined process.
In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates the telephone number used in contacts module 137, or stores a video file used in video player module 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates a new user-interface object or updates the position of a user-interface object. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends it to graphics module 132 for display on a touch-sensitive display.
In some embodiments, event handler(s) 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of a respective application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.
It shall be understood that the foregoing discussion regarding event handling of user touches on touch-sensitive displays also applies to other forms of user inputs to operate multifunction devices 100 with input-devices, not all of which are initiated on touch screens. For example, mouse movement and mouse button presses, optionally coordinated with single or multiple keyboard presses or holds; contact movements such as taps, drags, scrolls, etc., on touch-pads; pen stylus inputs; movement of the device; oral instructions; detected eye movements; biometric inputs; and/or any combination thereof are optionally utilized as inputs corresponding to sub-events which define an event to be recognized.
FIG. 2 illustrates a portable multifunction device 100 having a touch screen 112 in accordance with some embodiments. The touch screen optionally displays one or more graphics within user interface (UI) 200. In this embodiment, as well as others described below, a user is enabled to select one or more of the graphics by making a gesture on the graphics, for example, with one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, selection of one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, right to left, upward and/or downward) and/or a rolling of a finger (from right to left, left to right, upward and/or downward) that has made contact with device 100. In some implementations or circumstances, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
Device 100 may also include one or more physical buttons, such as “home” or menu button 204. As described previously, menu button 204 may be used to navigate to any application 136 in a set of applications that may be executed on device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on touch screen 112.
In one embodiment, device 100 includes touch screen 112, menu button 204, push button 206 for powering the device on/off and locking the device, volume adjustment button(s) 208, Subscriber Identity Module (SIM) card slot 210, head set jack 212, and docking/charging external port 124. Push button 206 is, optionally, used to turn the power on/off on the device by depressing the button and holding the button in the depressed state for a predefined time interval; to lock the device by depressing the button and releasing the button before the predefined time interval has elapsed; and/or to unlock the device or initiate an unlock process. In an alternative embodiment, device 100 also accepts verbal input for activation or deactivation of some functions through microphone 113. Device 100 also, optionally, includes one or more contact intensity sensors 165 for detecting intensity of contacts on touch screen 112 and/or one or more tactile output generators 167 for generating tactile outputs for a user of device 100.
FIG. 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface in accordance with some embodiments. Device 300 need not be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a child″s learning toy), a gaming system, or a control device (e.g., a home or industrial controller). Device 300 typically includes one or more processing units (CPU″s) 310, one or more network or other communications interfaces 360, memory 370, and one or more communication buses 320 for interconnecting these components. Communication buses 320 optionally include circuitry (sometimes called a chipset) that interconnects and controls communications between system components. Device 300 includes input/output (I/O) interface 330 comprising display 340, which is typically a touch screen display. I/O interface 330 also optionally includes a keyboard and/or mouse (or other pointing device) 350 and touchpad 355, tactile output generator 357 for generating tactile outputs on device 300 (e.g., similar to tactile output generator(s) 167 described above with reference to FIG. 1A), sensors 359 (e.g., optical, acceleration, proximity, touch-sensitive, and/or contact intensity sensors similar to contact intensity sensor(s) 165 described above with reference to FIG. 1A). Memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. Memory 370 optionally includes one or more storage devices remotely located from CPU(s) 310. In some embodiments, memory 370 stores programs, modules, and data structures analogous to the programs, modules, and data structures stored in memory 102 of portable multifunction device 100 (FIG. 1A), or a subset thereof. Furthermore, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores drawing module 380, presentation module 382, word processing module 384, website creation module 386, disk authoring module 388, and/or spreadsheet module 390, while memory 102 of portable multifunction device 100 (FIG. 1A) optionally does not store these modules.
Each of the above identified elements in FIG. 3 may be stored in one or more of the previously mentioned memory devices. Each of the above identified modules corresponds to a set of instructions for performing a function described above. The above identified modules or programs (e.g., sets of instructions) need not be implemented as separate software programs, procedures or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various embodiments. In some embodiments, memory 370 may store a subset of the modules and data structures identified above. Furthermore, memory 370 may store additional modules and data structures not described above.
Attention is now directed towards embodiments of user interfaces (“UI”) that may be implemented on portable multifunction device 100.
FIG. 4A illustrates an exemplary user interface for a menu of applications on portable multifunction device 100 in accordance with some embodiments. Similar user interfaces may be implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

- Signal strength indicator(s) 402 for wireless communication(s), such as cellular and Wi-Fi signals;
- Time 404;
- Bluetooth indicator 405;
- Battery status indicator 406;
- Tray 408 with icons for frequently used applications, such as:
  - Icon 416 for telephone module 138, labeled “Phone”, which optionally includes an indicator 414 of the number of missed calls or voicemail messages;
  - Icon 418 for e-mail client module 140, labeled “Mail”, which optionally includes an indicator 410 of the number of unread e-mails;
  - Icon 420 for browser module 147, labeled “Browser;” and
  - Icon 422 for video and music player module 152, also referred to as iPod (trademark of Apple Inc.) module 152, labeled “iPod;” and
- Icons for other applications, such as:
  - Icon 424 for IM module 141, labeled “Messages;”
  - Icon 426 for calendar module 148, labeled “Calendar;”
  - Icon 428 for image management module 144, labeled “Photos;”
  - Icon 430 for camera module 143, labeled “Camera;”
  - Icon 432 for online video module 155, labeled “Online Video”
  - Icon 434 for stocks widget 149-2, labeled “Stocks;”
  - Icon 436 for map module 154, labeled “Map;”
  - Icon 438 for weather widget 149-1, labeled “Weather;”
  - Icon 440 for alarm clock widget 149-4, labeled “Clock;”
  - Icon 442 for workout support module 142, labeled “Workout Support;”
  - Icon 444 for notes module 153, labeled “Notes;” and
  - Icon 446 for a settings application or module, which provides access to settings for device 100 and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A are merely exemplary. For example, icons 422 for video and music player module 152 are labeled “Music” or “Music Player.” Other labels are, optionally, used for various application icons. In some embodiments, a label for a respective application icon includes a name of an application corresponding to the respective application icon. In some embodiments, a label for a particular application icon is distinct from a name of an application corresponding to the particular application icon.
FIG. 4B illustrates an exemplary user interface on a device (e.g., device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tablet or touchpad 355, FIG. 3) that is separate from the display 450 (e.g., touch screen display 112). Device 300 also, optionally, includes one or more contact intensity sensors (e.g., one or more of sensors 357) for detecting intensity of contacts on touch-sensitive surface 451 and/or one or more tactile output generators 359 for generating tactile outputs for a user of device 300.
Although some of the examples which follow will be given with reference to inputs on touch screen display 112 (where the touch sensitive surface and the display are combined), in some embodiments, the device detects inputs on a touch-sensitive surface that is separate from the display, as shown in FIG. 4B. In some embodiments the touch sensitive surface (e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) that corresponds to a primary axis (e.g., 453 in FIG. 4B) on the display (e.g., 450). In accordance with these embodiments, the device detects contacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface 451 at locations that correspond to respective locations on the display (e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470). In this way, user inputs (e.g., contacts 460 and 462, and movements thereof) detected by the device on the touch-sensitive surface (e.g., 451 in FIG. 4B) are used by the device to manipulate the user interface on the display (e.g., 450 in FIG. 4B) of the multifunction device when the touch-sensitive surface is separate from the display. It should be understood that similar methods are, optionally, used for other user interfaces described herein.
Additionally, while the following examples are given primarily with reference to finger inputs (e.g., finger contacts, finger tap gestures, finger swipe gestures), it should be understood that, in some embodiments, one or more of the finger inputs are replaced with input from another input device (e.g., a mouse based input or stylus input). For example, a swipe gesture is, optionally, replaced with a mouse click (e.g., instead of a contact) followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is, optionally, replaced with a mouse click while the cursor is located over the location of the tap gesture (e.g., instead of detection of the contact followed by ceasing to detect the contact). Similarly, when multiple user inputs are simultaneously detected, it should be understood that multiple computer mice are, optionally, used simultaneously, or a mouse and finger contacts are, optionally, used simultaneously.
FIG. 5A illustrates exemplary personal electronic device 500. Device 500 includes body 502. In some embodiments, device 500 can include some or all of the features described with respect to devices 100 and 300 (e.g., FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitive display screen 504, hereafter touchscreen 504. Alternatively, or in addition to touchscreen 504, device 500 has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touchscreen 504 (or the touch-sensitive surface) may have one or more intensity sensors for detecting intensity of contacts (e.g., touches) being applied. The one or more intensity sensors of touchscreen 504 (or the touch-sensitive surface) can provide output data that represents the intensity of touches. The user interface of device 500 can respond to touches based on their intensity, meaning that touches of different intensities can invoke different user interface operations on device 500. As used here, the term “intensity” of a contact (or touch) on touchscreen 504 (or the touch-sensitive surface) refers to the force or pressure (force per unit area) of a touch (e.g., a finger) on the touchscreen.
Techniques for detecting and processing touch intensity may be found, for example, in related applications: International Patent Application Serial No. PCT/US2013/040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application”, filed May 8, 2013 and International Patent Application Serial No. PCT/US2013/069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships”, filed Nov. 11, 2013.
In some embodiments, device 500 has one or more input mechanisms 506 and 508. Input mechanisms 506 and 508, if included, can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, device 500 has one or more attachment mechanisms. Such attachment mechanisms, if included, can permit attachment of device 500 with, for example, hats, eyewear, earrings, necklaces, shirts, jackets, bracelets, watch straps, chains, trousers, belts, shoes, purses, backpacks, and so forth. These attachment mechanisms may permit device 500 to be worn by a user.
FIG. 5B depicts exemplary personal electronic device 500. In some embodiments, device 500 can include some or all of the components described with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512 that operatively couples I/O section 514 with one or more computer processors 516 and memory 518. I/O section 514 can be connected to display 504, which can have touch-sensitive component 522 and, optionally, touch-intensity sensitive component 524. In addition, I/O section 514 can be connected with communication unit 530 for receiving application and operating system data, using Wi-Fi, Bluetooth”, near field communication (“NFC”), cellular and/or other wireless communication techniques. Device 500 can include input mechanisms 506 and/or 508. Input mechanism 506 may be a rotatable input device or a depressible and rotatable input device, for example. Input mechanism 508 may be a button, in some examples.
Input mechanism 508 may be a microphone, in some examples. Computing device 500 can include various sensors, such as GPS sensor 532, accelerometer 534, directional sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and/or a combination thereof, all of which can be operatively connected to I/O section 514.
Memory 518 of computing device 500 can be a non-transitory computer readable storage medium, for storing computer-executable instructions, which, when executed by one or more computer processors 516, for example, can cause the computer processors to perform the techniques described above, including processes 700, 1000, 1100, 1600, and 1900 (FIGS. 7, 10, 11, 16, and 19). The computer-executable instructions can also be stored and/or transported within any non-transitory computer readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For purposes of this document, a “non-transitory computer readable storage medium” can be any medium that can tangibly contain or store computer-executable instructions for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer readable storage medium can include, but is not limited to, magnetic, optical, and/or semiconductor storages. Examples of such storage include magnetic disks, optical discs based on CD, DVD, or Blu-ray technologies, as well as persistent solid-state memory such as flash, solid-state drives, and the like. Computing device 500 is not limited to the components and configuration of FIG. 5B, but can include other or additional components in multiple configurations.
As used here, the term “affordance” refers to a user-interactive graphical user interface object that may be displayed on the display screen of device 100, 300, and/or 500 (FIGS. 1, 3, and 5). For example, an image (e.g., icon), a button, and text (e.g., hyperlink) may each constitute an affordance.
As used herein, the term “focus selector” refers to an input element that indicates a current part of a user interface with which a user is interacting. In some implementations that include a cursor or other location marker, the cursor acts as a “focus selector”, so that when an input (e.g., a press input) is detected on a touch-sensitive surface (e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B) while the cursor is over a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations that include a touch-screen display (e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112 in FIG. 4A) that enables direct interaction with user interface elements on the touch-screen display, a detected contact on the touch-screen acts as a “focus selector”, so that when an input (e.g., a press input by the contact) is detected on the touch-screen display at a location of a particular user interface element (e.g., a button, window, slider or other user interface element), the particular user interface element is adjusted in accordance with the detected input. In some implementations focus is moved from one region of a user interface to another region of the user interface without corresponding movement of a cursor or movement of a contact on a touch-screen display (e.g., by using a tab key or arrow keys to move focus from one button to another button); in these implementations, the focus selector moves in accordance with movement of focus between different regions of the user interface. Without regard to the specific form taken by the focus selector, the focus selector is generally the user interface element (or contact on a touch-screen display) that is controlled by the user so as to communicate the user-s intended interaction with the user interface (e.g., by indicating, to the device, the element of the user interface with which the user is intending to interact). For example, the location of a focus selector (e.g., a cursor, a contact or a selection box) over a respective button while a press input is detected on the touch-sensitive surface (e.g., a touchpad or touch screen) will indicate that the user is intending to activate the respective button (as opposed to other user interface elements shown on a display of the device).
As used in the specification and claims, the term “characteristic intensity” of a contact refers to a characteristic of the contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is, optionally, based on a predefined number of intensity samples, or a set of intensity samples collected during a predetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10 seconds) relative to a predefined event (e.g., after detecting the contact, prior to detecting liftoff of the contact, before or after detecting a start of movement of the contact, prior to detecting an end of the contact, before or after detecting an increase in intensity of the contact, and/or before or after detecting a decrease in intensity of the contact). A characteristic intensity of a contact is, optionally based on one or more of: a maximum value of the intensities of the contact, a mean value of the intensities of the contact, an average value of the intensities of the contact, a top 10 percentile value of the intensities of the contact, a value at the half maximum of the intensities of the contact, a value at the 90 percent maximum of the intensities of the contact, or the like. In some embodiments, the duration of the contact is used in determining the characteristic intensity (e.g., when the characteristic intensity is an average of the intensity of the contact over time). In some embodiments, the characteristic intensity is compared to a set of one or more intensity thresholds to determine whether an operation has been performed by a user. For example, the set of one or more intensity thresholds may include a first intensity threshold and a second intensity threshold. In this example, a contact with a characteristic intensity that does not exceed the first threshold results in a first operation, a contact with a characteristic intensity that exceeds the first intensity threshold and does not exceed the second intensity threshold results in a second operation, and a contact with a characteristic intensity that exceeds the third threshold results in a third operation. In some embodiments, a comparison between the characteristic intensity and one or more thresholds is used to determine whether or not to perform one or more operations (e.g., whether to perform a respective option or forgo performing the respective operation) rather than being used to determine whether to perform a first operation or a second operation.
In some embodiments, a portion of a gesture is identified for purposes of determining a characteristic intensity. For example, a touch-sensitive surface may receive a continuous swipe contact transitioning from a start location and reaching an end location, at which point the intensity of the contact increases. In this example, the characteristic intensity of the contact at the end location may be based on only a portion of the continuous swipe contact, and not the entire swipe contact (e.g., only the portion of the swipe contact at the end location). In some embodiments, a smoothing algorithm may be applied to the intensities of the swipe contact prior to determining the characteristic intensity of the contact. For example, the smoothing algorithm may be an unweighted sliding-average smoothing algorithm, a triangular smoothing algorithm, a median filter smoothing algorithm, and/or an exponential smoothing algorithm. These smoothing algorithms may eliminate narrow spikes or dips in the intensities of the swipe contact for purposes of determining a characteristic intensity.
The intensity of a contact on the touch-sensitive surface may be characterized relative to one or more intensity thresholds, such as a contact-detection intensity threshold, a light press intensity threshold, a deep press intensity threshold, and/or one or more other intensity thresholds. In some embodiments, the light press intensity threshold corresponds to an intensity at which the device will perform operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, the deep press intensity threshold corresponds to an intensity at which the device will perform operations that are different from operations typically associated with clicking a button of a physical mouse or a trackpad. In some embodiments, when a contact is detected with a characteristic intensity below the light press intensity threshold (e.g., and above a nominal contact-detection intensity threshold below which the contact is no longer detected), the device will move a focus selector in accordance with movement of the contact on the touch-sensitive surface without performing an operation associated with the light press intensity threshold or the deep press intensity threshold. Generally, unless otherwise stated, these intensity thresholds are consistent between different sets of user interface figures.
An increase of characteristic intensity of the contact from an intensity below the light press intensity threshold to an intensity between the light press intensity threshold and the deep press intensity threshold is sometimes referred to as a “light press” input. An increase of characteristic intensity of the contact from an intensity below the deep press intensity threshold to an intensity above the deep press intensity threshold is sometimes referred to as a “deep press” input. An increase of characteristic intensity of the contact from an intensity below the contact-detection intensity threshold to an intensity between the contact-detection intensity threshold and the light press intensity threshold is sometimes referred to as detecting the contact on the touch-surface. A decrease of characteristic intensity of the contact from an intensity above the contact-detection intensity threshold to an intensity below the contact-detection intensity threshold is sometimes referred to as detecting liftoff of the contact from the touch-surface. In some embodiments the contact-detection intensity threshold is zero. In some embodiments the contact-detection intensity threshold is greater than zero.
In some embodiments described herein, one or more operations are performed in response to detecting a gesture that includes a respective press input or in response to detecting the respective press input performed with a respective contact (or a plurality of contacts), where the respective press input is detected based at least in part on detecting an increase in intensity of the contact (or plurality of contacts) above a press-input intensity threshold. In some embodiments, the respective operation is performed in response to detecting the increase in intensity of the respective contact above the press-input intensity threshold (e.g., a “down stroke” of the respective press input). In some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the press-input threshold (e.g., an “up stroke” of the respective press input).
In some embodiments, the device employs intensity hysteresis to avoid accidental inputs sometimes termed “jitter”, where the device defines or selects a hysteresis intensity threshold with a predefined relationship to the press-input intensity threshold (e.g., the hysteresis intensity threshold is X intensity units lower than the press-input intensity threshold or the hysteresis intensity threshold is 75%, 90% or some reasonable proportion of the press-input intensity threshold). Thus, in some embodiments, the press input includes an increase in intensity of the respective contact above the press-input intensity threshold and a subsequent decrease in intensity of the contact below the hysteresis intensity threshold that corresponds to the press-input intensity threshold, and the respective operation is performed in response to detecting the subsequent decrease in intensity of the respective contact below the hysteresis intensity threshold (e.g., an “up stroke” of the respective press input). Similarly, in some embodiments, the press input is detected only when the device detects an increase in intensity of the contact from an intensity at or below the hysteresis intensity threshold to an intensity at or above the press-input intensity threshold and, optionally, a subsequent decrease in intensity of the contact to an intensity at or below the hysteresis intensity, and the respective operation is performed in response to detecting the press input (e.g., the increase in intensity of the contact or the decrease in intensity of the contact, depending on the circumstances).
For ease of explanation, the description of operations performed in response to a press input associated with a press-input intensity threshold or in response to a gesture including the press input are, optionally, triggered in response to detecting either: an increase in intensity of a contact above the press-input intensity threshold, an increase in intensity of a contact from an intensity below the hysteresis intensity threshold to an intensity above the press-input intensity threshold, a decrease in intensity of the contact below the press-input intensity threshold, and/or a decrease in intensity of the contact below the hysteresis intensity threshold corresponding to the press-input intensity threshold. Additionally, in examples where an operation is described as being performed in response to detecting a decrease in intensity of a contact below the press-input intensity threshold, the operation is, optionally, performed in response to detecting a decrease in intensity of the contact below a hysteresis intensity threshold corresponding to, and lower than, the press-input intensity threshold.
As used herein, an “installed application” refers to a software application that has been downloaded onto an electronic device (e.g., devices 100, 300, and/or 500) and is ready to be launched (e.g., become opened) on the device. In some embodiments, a downloaded application becomes an installed application by way of an installation program that extracts program portions from a downloaded package and integrates the extracted portions with the operating system of the computer system.
As used herein, the term “open application” or “executing application” refers to a software application with retained state information (e.g., as part of device/global internal state 157 and/or application internal state 192). An open or executing application may be any one of the following types of applications:

- an active application, which is currently displayed on a display screen of the device that the application is being used on;
- a background application (or background processes) which is not currently displayed, but one or more processes for the application are being processed by one or more processors; and
- a suspended or hibernated application, which is not running, but has state information that is stored in memory (volatile and non-volatile, respectively) and that can be used to resume execution of the application.

As used herein, the term “closed application” refers to software applications without retained state information (e.g., state information for closed applications is not stored in a memory of the device). Accordingly, closing an application includes stopping and/or removing application processes for the application and removing state information for the application from the memory of the device. Generally, opening a second application while in a first application does not close the first application. When the second application is displayed and the first application ceases to be displayed, the first application becomes a background application.
FIG. 6 illustrates an exemplary mapping system 600 for providing vector map data for use in generating a view of a map by a mapping application according to various examples. As shown, in some examples, system 600 can be implemented according to a client-server model. Mapping system 600 can include a client-side portion executed on a user device 602 and/or 604, and a server-side portion executed on a server system 623. User device 602 and/or 604 can include any electronic device, such as device 100, 300, or 500, and can communicate with server system 623 through one or more networks 608, which can include the Internet, an intranet, or any other wired or wireless public or private network.
Server system 623 can provide server-side functionalities for any number of clients residing on respective user devices 602 and 604 and can include one or more map servers 624 that can include a client-facing I/O interface 626, one or more processing modules 628, and map and navigation data storage 630. The client-facing I/O interface 626 can facilitate the client-facing input and output processing for map server 624. The one or more processing modules 628 can utilize map and navigation data storage 630 to provide appropriate map tiles for display on user device 602 and/or 604, provide geocoding and reverse geocoding functions, provide navigation and routing functions to determine directions from a start location to and end location, provide traffic information, and the like. In some examples, as described in greater detail below with respect to FIG. 7, processing modules 628 can be configured to dynamically generate vector map sub-tiles of any size from a set of pre-generated vector map tiles stored in map and navigation storage 630. These vector map sub-tiles can be provided to user devices 602 and 604 to allow mapping applications executed on these devices to display portions of a map represented by the set of vector map tiles. Server system 623 can be implemented on one or more standalone data processing devices or a distributed network of computers. In some examples, server system 623 can 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 623.
In some examples, the client-side portion executed on user devices 602 and 604 can include mapping applications, which can provide client-side functionalities, such as user-facing input and output processing and communications with server system 623. For example, the mapping applications can request map data from server system 623. Additionally, in some examples, one user device (e.g., user device 602) can be communicatively coupled with another user device (e.g., user device 604) via a direct communication connection, such as Bluetooth, NFC, BTLE, or the like, or via a wired or wireless network, such as a local Wi-Fi network. In these examples, one user device (e.g., user device 604) can act as a proxy between the other user device (e.g., user device 602) and server system 623 by receiving data or requests for data from the other user device and transmitting the data or the requests for data to server system 623. Additionally, in these examples, the proxy user device can receive data or requests for data from server system 623 and can transmit the data or request for data to the other user device. Allowing one user device to act as a proxy for another advantageously provides a user device having limited communication capabilities and/or limited battery power, such as a watch or other compact electronic device, with that ability to access mapping services provided by server system 623 by leveraging the communication capabilities and/or battery power of another user device, such as a mobile phone, laptop computer, tablet computer, or the like. While only two user devices 602 and 604 are shown in FIG. 6, it should be appreciated that system 600 can include any number and type of user devices that operate independently or that are configured in a proxy configuration to communicate with server system 623.
Although the functionality of the mapping services are shown in FIG. 6 as including both a client-side portion and a server-side portion, in some examples, the functions of the mapping services can be implemented as a standalone application installed on a user device. In addition, the division of functionalities between the client and server portions of the mapping services can vary in different examples. For instance, in some examples, the client executed on user device 602 or 604 can be a thin-client that provides only user-facing input and output processing functions, and delegates all other functionalities of the mapping services to a backend server.
FIG. 7 illustrates an exemplary process 700 for providing vector map data for use in generating a view of a map by a mapping application. In some examples, process 700 can be performed using a system similar or identical to system 600, shown in FIG. 6. In these examples, the blocks of process 700 can be performed by processing modules 628 of one or more map servers 624. As mentioned above, a map displayed by a mapping application can be represented by a set of map tiles. One type of map tile that can be used is a vector map tile, which can include an image of a portion of a map that is represented using vector data. The vector data can represent various features of the map, such as roads, buildings, bodies of water, parks, areas of land, or the like, using geometric primitives, such as points, lines, polygons, and the like. For example, FIG. 8 illustrates an example vector map tile 800. As shown, vector map tile 800 includes point-type geometric primitives point 802 and point 804 that represent points of interest (e.g., “Store” and “School”). Vector map tile 800 further includes line-type geometric primitives (which can include both lines and curves) line 806, line 808, and line 810 representing roads (e.g., “1^stStreet” and “2^ndStreet”), rivers (e.g., “River”), or the like. Vector map tile 800 further includes two-dimensional (2D) polygon-type geometric primitives (which can include shapes having curved or straight edges) polygon 812, polygon 814, and polygon 816 representing areas of land, bodies of water, or the like. Vector map tile 800 further includes three-dimensional (3D) polygon-type geometric primitives (which can include shapes having curved or straight edges) 3D polygon 818, 3D polygon 820, and 3D polygon 822 representing buildings or other 3D objects. In some examples, a vector map tile can further include textual labels (e.g., names of streets, cities, businesses, bodies of water, parks, etc.), attributes (e.g., direction of local north), or other visible or non-visible data.
Referring back to FIG. 7, at block 702 of process 700, a request for a vector map sub-tile can be received from an electronic device. The vector map sub-tile can represent a portion of a pre-generated vector map tile, such as vector map tile 800. However, the vector map sub-tile may not be a pre-generated and may not exist as a separate file prior to the performance of process 700. FIG. 9 illustrates example vector map sub-tiles 902, 904, 906, and 908 of pre-generated vector map tile 800. While four vector map sub-tiles are shown, it should be appreciated that a vector map tile can be divided into any number of vector map sub-tiles. In some examples, the request for a vector map sub-tile can include an identification of a specific vector map sub-tile to be provided by the map server. For example, the request can include a unique identifier of a predefined (but not pre-generated) vector map sub-tile, geographic coordinates of the vector map sub-tile, a desired size of the vector map sub-tile, combinations thereof, or the like. In these examples, the requesting electronic device can determine an appropriate size of the vector map sub-tile(s) to request based on the screen size of the device and can determine, based on the locations to be viewed within a mapping application executing on the device, the appropriate vector map sub-tile(s) to request from the map server. An example process for selecting map tiles to request from a map server is described in U.S. patent application Ser. No. 13/706,243, “Map Tile Selection in 3D”, filed Dec. 5, 2012, which is incorporated by reference herein in its entirety for all purposes. Alternatively, in other examples, the request for a vector map sub-tile can include one or more locations to be viewed within the mapping application executed on the electronic device. In these examples, the map server can determine the appropriate vector map sub-tile to provide to the electronic device based on the received location(s), type (e.g., make/model) of the electronic device, and known properties of the device.
While square vector map tiles and vector map sub-tiles are shown, it should be appreciated that the vector map tiles and sub-tiles can have any desired shape. Moreover, the vector map tiles need not be the same shape as the vector map sub-tiles. For example, the vector map tile can be a square, while the vector map sub-tiles can be non-square rectangles.
At block 704, the map server can identify a vector map tile that corresponds to the vector map sub-tile requested at block 702. Since the requested vector map sub-tile may not exist as a separate file when the request is received at block 702, the map server can identify the pre-generated vector map tile stored in data and navigation storage 630 that contains or encompasses the requested vector map sub-tile. For example, if vector map sub-tile 902 is requested at block 702, the map server can determine that vector map sub-tile 902 represents a subset of the area represented by vector map tile 800 and that vector map tile 800 corresponds to the requested vector map sub-tile.
At block 706, the map server can access the vector map tile identified at block 704. Accessing the vector map tile can include retrieving the vector map tile from a storage located at or remotely from the map server. For example, map server 624 can retrieve the identified vector map tile from map and navigation storage 630.
At block 708, the map server can generate the requested vector map sub-tile by dividing the vector map tile identified at block 704 into multiple sub-tiles. For example, in response to a request for vector map sub-tile 902, the map server can divide vector map tile 800 into four vector map sub-tiles 902, 904, 906, and 908. If a smaller vector map sub-tile was requested, vector map tile 800 can be divided into a larger number of vector map sub-tiles. Unlike a raster image, which simply includes a grid of pixels having colors and intensities that can easily be separated from one another, a vector image includes vectorized mathematical models of shapes that are more complicated to divide. Thus, in some examples, dividing the vector map tile into smaller sub-tiles can generally include analyzing each feature of the vector map tile to determine if it should be included in the vector map sub-tile, identifying attributes of the vector map tile that should be inherited by the vector map sub-tile, and adding data to the vector map sub-tile to account for the map tile boundaries created by dividing the vector map tile. For example, block 708 can include determining, for each feature in the vector map tile identified at block 704, whether some or all of the feature should be included in the requested vector map sub-tile. FIGS. 10, 11, 16, and 17 illustrate exemplary processes that can be performed to determine whether a feature should be included in the requested vector map sub-tile for common map feature types.
For example, FIG. 10 illustrates an exemplary process 1000 that can be performed at block 708 of process 700 to determine whether a point-type feature (e.g., a point of interest or other featured defined by a single point location) should be included within the requested vector map sub-tile. At block 1002, it can be determined whether a location associated with the point-type feature (e.g., point 802 or 804) is located within an area represented by the requested vector map sub-tile. For example, the point-type feature can be associated with a set of geographic coordinates that represent the feature″s real world location. In this example, block 1002 can include determining whether that geographic coordinate is located within the area represented by the requested vector map sub-tile. If it is determined that the location associated with the point-type feature is located within the area represented by the requested vector map sub-tile, process 1000 can proceed to block 1004, where the point can be included in the requested vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1002 that point 802 has an associated location within the area represented by the requested vector map sub-tile since point 802 is located within the bounds of vector map sub-tile 902. As a result, point 802 can be included in the requested vector map sub-tile 902 at block 1004. Alternatively, if it is instead determined at block 1002 that the location associated with the point-type feature is not located within the area represented by the requested vector map sub-tile, process 1000 can proceed to block 1006, where the point can be excluded from the vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1002 that point 804 has an associated location that is not within the area represented by the requested vector map sub-tile since point 804 is located outside the bounds of vector map sub-tile 902. As a result, point 804 can be excluded from the requested vector map sub-tile 902 at block 1006. In some examples, process 1000 can be performed on some or all of the point-type features of the vector map tile identified at block 704 of process 700. For example process 1000 can be performed on point 802 to determine that point 802 should be included in the requested vector map sub-tile 902 and on point 804 to determine that point 804 should be excluded from requested vector map sub-tile 902.
FIG. 11 illustrates an exemplary process 1100 that can be performed at block 708 of process 700 to determine whether a line-type (e.g., a road, a river, or the like) feature should be included within the requested vector map sub-tile. As mentioned above, a line-type feature can refer to straight line segments as well as curves. At block 1102, it can be determined whether a location associated with the line-type feature (e.g., line 806, 808, or 810) is located within an area represented by the requested vector map sub-tile. For example, the line-type feature can be associated with one or more sets of geographic coordinates that represent the feature″s real world location. Block 1102 can include determining whether the set(s) of geographic coordinates are located within the area represented by the requested vector map sub-tile. If it is determined that the location associated with the line-type feature is located entirely within the area represented by the requested vector map sub-tile, process 1100 can proceed to block 1104, where the entire line can be included in the requested vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1102 that line 806 has an associated location entirely within the area represented by the requested vector map sub-tile since line 806 is located entirely within the bounds of vector map sub-tile 902. As a result, the entirety of line 806 can be included in the requested vector map sub-tile 902 at block 1104. If it is instead determined at block 1102 that the location associated with the line-type feature is located entirely outside the area represented by the requested vector map sub-tile, process 1100 can proceed to block 1106, where the line can be excluded from the vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1102 that line 810 has an associated location that is entirely outside the area represented by the requested vector map sub-tile since line 810 is located entirely outside the bounds of vector map sub-tile 902. As a result, the entirety of line 810 can be excluded from the requested vector map sub-tile 902 at block 1106. If it is instead determined at block 1102 that the location associated with the line-type feature is located partially within the area represented by the requested vector map sub-tile, process 1100 can proceed to block 1108. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1102 that line 808 has an associated location partially within the area represented by the requested vector map sub-tile since line 808 is partially located within the bounds of vector map sub-tile 902. As a result, the process can proceed to block 1108.
At block 1108, a flattening algorithm can be applied to the line to flatten the line into a set of straight lines. Any known line flattening algorithm can be used. For example, the algorithm can include defining straight lines between adjacent vertices that define the line. This can be performed to simplify the process of dividing the line into multiple segments when dividing the vector map tile. To illustrate, FIG. 12 shows line 808 (with the other features of vector map tile 800 removed) and the vertices 1202 that define the line. As shown, line 808 has a curved shape that passes through vertices 1202. After applying the flattening algorithm at block 1108, line 808 can include a set of straight lines connecting its vertices 1202, as shown by flattened line 1302 in FIG. 13.
At block 1110, the map server can divide the flattened line generated at block 1108 into two or more line segments. This can include dividing the line at points that it intersects a division between vector map sub-tiles. For example, as shown in FIG. 13, flattened line 1302 can be divided along division line 1304 to create two line segments, one to the left of division line 1304 and one to the right of division line 1304. In some examples, block 1110 can further include tagging the endpoints 1204 of the two line segments that were generated by dividing the flattened line. These endpoints 1204 can be tagged to indicate that the endpoint connects to a line segment from another vector map sub-tile. This can be used, for example, by the mapping application executed on the requesting electronic device when rendering an image based on the received vector map sub-tile. For example, some mapping applications can display a marker (e.g., a circle or an end-cap) that identifies the endpoint of a line. The tag added to endpoints 1204 can instruct the mapping application to refrain from displaying such a marker since endpoint 1204 represents an artificial end to the line, rather than an actual end to the line. Additionally, in some examples, the tag added to endpoints 1204 can instruct the mapping application to request the adjacent vector map sub-tile containing the other line segment to allow the mapping application to render some or all of the map feature represented by the line.
At block 1112, the map server can apply a curve fitting algorithm to one or more of the line segments produced at block 1110 that are associated with locations within an area represented by the requested vector map sub-tile. Any known curve fitting algorithm can be used at block 1112, such as a Gauss-Newton algorithm, or the like. This can be done to reintroduce the curvature of the line that was removed by the performance of block 1108. For example, continuing with the example above, FIG. 14 illustrates the line segment 1402 resulting from the performance of block 1110 that is located within the requested vector map sub-tile 902. A curve fitting algorithm can be applied to line segment 1402 (e.g., using the vertices of line segment 1402) at block 1112 to generate a curved line, such as curved line 1502, shown in FIG. 15.
At block 1114, the one or more curved lines generated at block 1114 can be included in the requested vector map sub-tile. For example, curved line 1502 can be included within the requested vector map sub-tile 902. In some examples, process 1100 can be performed on some or all of the line-type features of the vector map tile identified at block 704 of process 700. For example process 1100 can be performed on line 806 to determine that the entirety of line 806 should be included within the requested vector map sub-tile 902, on line 808 to determine that a portion of line 808 should be included within the requested vector map sub-tile 902, and on line 810 to determine that line 810 should be excluded from the requested vector map sub-tile 902.
FIG. 16 illustrates an exemplary process 1600 that can be performed at block 708 of process 700 to determine whether a 2D polygon-type feature (e.g., a body of water, area of land, or the like) should be included within the requested vector map sub-tile. At block 1602, it can be determined whether a location associated with the 2D polygon-type feature (e.g., polygon 812, 814, or 816) is located within an area represented by the requested vector map sub-tile. For example, the polygon-type feature can be associated with one or more sets of geographic coordinates that represent the feature″s real world location. Block 1602 can include determining whether the set(s) of geographic coordinates are located within the area represented by the requested vector map sub-tile. If it is determined that the location associated with the 2D polygon-type feature is located entirely within the area represented by the requested vector map sub-tile, process 1600 can proceed to block 1604, where the entire polygon can be included in the requested vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1602 that polygon 812 has an associated location entirely within the area represented by the requested vector map sub-tile since polygon 812 is located entirely within the bounds of vector map sub-tile 902. As a result, the entirety of polygon 812 can be included in the requested vector map sub-tile 902 at block 1604. If it is instead determined at block 1602 that the location associated with the 2D polygon-type feature is located entirely outside the area represented by the requested vector map sub-tile, process 1600 can proceed to block 1606, where the polygon can be excluded from the vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1602 that polygon 816 has an associated location that is entirely outside the area represented by the requested vector map sub-tile since polygon 816 is located outside the bounds of vector map sub-tile 902. As a result, the entirety of polygon 816 can be excluded from the requested vector map sub-tile 902 at block 1606. If it is instead determined at block 1602 that the location associated with the 2D polygon-type feature is located partially within the area represented by the requested vector map sub-tile, process 1600 can proceed to block 1608. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1602 that polygon 814 has an associated location partially within the area represented by the requested vector map sub-tile since polygon 814 is located partially within the bounds of vector map sub-tile 902. As a result, the process can proceed to block 1608.
At block 1608, the map server can divide the polygon into two or more polygon segments. This can include dividing the polygon along division lines between vector map sub-tiles. For example, as shown in FIG. 17, polygon 814 can be divided along division line 1702 to create two polygon segments, one above division line 1702 and one below division line 1702. In some examples, block 1608 can further include tagging the edges 1704 between the two polygon segments that were generated by dividing the polygon. These edges 1704 can be tagged to indicate that the edge represents an interior edge created by dividing the vector map tile into vector map sub-tiles. This can be used, for example, by the mapping application executed on the requesting electronic device when rendering an image based on the received vector map sub-tile. For example, some mapping applications can connect corners or vertices of a polygon to ensure that the resulting object forms a closed shape. The tag added to edges 1704 can instruct the mapping application to refrain from creating an additional line along these edges since edges 1704 represent an interior edge to the polygon, rather than an actual edge. Additionally, in some examples, the tag added to edges 1704 can instruct the mapping application to request the adjacent vector map sub-tile containing the other polygon segment to allow the mapping application to render some or all of the map feature represented by the polygon.
At block 1610, one or more of the polygon segments generated at block 1608 that are associated with locations within an area represented by the requested vector map sub-tile can be included in the requested vector map sub-tile. For example, FIG. 18 illustrates the polygon segment 1802 resulting from the performance of block 1608 that is located within the requested vector map sub-tile 902. This polygon segment 1802 can be included within the requested vector map sub-tile at block 1610. In some examples, process 1600 can be performed on some or all of the 2D polygon-type features of the vector map tile identified at block 704 of process 700. For example process 1600 can be performed on polygon 812 to determine that the entirety of polygon 812 should be included within the requested vector map sub-tile 902, on polygon 814 to determine that a portion of polygon 814 should be included within the requested vector map sub-tile 902, and on polygon 816 to determine that polygon 816 should be excluded from the requested vector map sub-tile 902.
FIG. 19 illustrates an exemplary process 1900 that can be performed at block 708 of process 700 to determine whether a 3D polygon-type feature (e.g., a building or other 3D object) should be included within the requested vector map sub-tile. At block 1902, it can be determined whether the requested vector map sub-tile is the vector map sub-tile of the vector map tile having the largest portion of a base of the 3D polygon-type feature (e.g., 3D polygon 818, 820, or 822) located therein. The base of the 3D polygon can include a 2D polygon that represents the footprint of the 3D polygon (e.g., the base of the 3D polygon that contacts the ground). For example, FIG. 20 illustrates example footprints 2018, 2020, and 2022 of 3D polygons 818, 820, and 822, respectively. If it is determined that the requested vector map sub-tile is the vector map sub-tile of the vector map tile having the largest portion of a base of the 3D polygon-type feature located therein, process 1900 can proceed to block 1904, where the 3D polygon can be included in the requested vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1902 that the requested vector map sub-tile 902 is the vector map sub-tile of vector map tile 800 having the largest portion of footprint 2018 of 3D polygon 818 located therein (e.g., since the other vector map sub-tiles 904, 906, and 908 do not include any portion of footprint 2018). As a result, 3D polygon 818 can be included in the requested vector map sub-tile 902 at block 1904. Alternatively, if it is instead determined at block 1902 that the requested vector map sub-tile is not the vector map sub-tile of the vector map tile having the largest portion of a base of the 3D polygon-type feature located therein, process 1900 can proceed to block 1906, where the 3D polygon can be excluded from the vector map sub-tile. For example, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1902 that the requested vector map sub-tile 902 is not the vector map sub-tile of vector map tile 800 having the largest portion of footprint 2020 of 3D polygon 820 located therein (e.g., since vector map sub-tile 904 includes a larger portion of footprint 2020). As a result, 3D polygon 820 can be excluded from the requested vector map sub-tile 902 at block 1906. Similarly, if vector map sub-tile 902 was requested at block 702 of process 700, it can be determined at block 1902 that the requested vector map sub-tile 902 is not the vector map sub-tile of vector map tile 800 having the largest portion of footprint 2022 of 3D polygon 822 located therein (e.g., since vector map sub-tile 906 includes all of footprint 2022). As a result, 3D polygon 822 can be excluded from the requested vector map sub-tile 902 at block 1906. In some examples, process 1900 can be performed on some or all of the 3D polygon-type features of the vector map tile identified at block 704 of process 700. For example process 1900 can be performed on 3D polygon 818 to determine that 3D polygon 818 should be included in the requested vector map sub-tile 902, on 3D polygon 820 to determine that 3D polygon 820 should be excluded from the requested vector map sub-tile 902, and on 3D polygon 822 to determine that 3D polygon 822 should be excluded from requested vector map sub-tile 902.
In some examples, some or all of processes 1000, 1100, 1600, and 1900 can be performed at block 708 of process 700 depending on the type of map features present in the vector map tile accessed at block 706. These processes can be performed on each map feature included within the vector map tile to determine the appropriate features to include in the requested vector map sub-tile. FIG. 21 illustrates an example vector map sub-tile 902 that can be generated from vector map tile 800 using processes 1000, 1100, 1600, and 1900.
Referring back to FIG. 7, after generating the requested vector map sub-tile at block 708, the map server can transmit the requested vector map sub-tile to the electronic device that requested it at block 702. The electronic device receiving the requested vector map sub-tile can then use the received vector map sub-tile alone or in combination with other vector map sub-tiles to render an image of a portion of a map for display to a user. In response to a request to change a view of the map at the electronic device, the electronic device can transmit another request for a vector map sub-tile that can be received by the map server, causing process 700 to be repeated.
In some examples, the vector map tile accessed at block 706 can be produced using a production pipeline that results in the vector map tile being encoded in a particular encoding format. In these examples, block 706 can include decoding the vector map tile from this format to allow the map server to generate the requested vector map sub-tile from the vector map tile at block 708. Additionally, in these examples, process 700 can further include encoding the vector map sub-tile generated at block 708 in the same encoding format used by the vector map tile. This can be done to advantageously allow process 700 to be used with an existing vector map tile pipeline without having to modify the pipeline to produce a non-encoded vector map tile and without having to modify the operation of the electronic devices to handle received vector map tiles in a different manner.
In some examples, process 700 can further include identifying attributes of the vector map tile identified at block 704 that should be inherited by the vector map sub-tile generated at block 708. This can be done because the vector map sub-tile may not inherently include these properties since it is a newly generated object. For example, some vector map tiles can include an attribute that identifies the local North direction. In these examples, process 700 can include generating the requested vector map sub-tile to include this attribute. A similar process can be performed for any other attributes of the vector map tile.
While process 700 is described above as being used to receive a request for a single vector map sub-tile, it should be appreciated that process 700 can be used to service requests for any number of vector map sub-tiles. For example, process 700 can be repeated multiple times for each requested vector map sub-tile. Alternatively, block 702 can include receiving a request for more than one vector map sub-tile. In these examples, block 704 can include identifying one or more vector map tiles that correspond to the multiple requested vector map sub-tiles, block 706 can include accessing the one or more vector map tiles, block 708 can include generated the requested vector map sub-tiles by determining the appropriate features and attributes to include for each requested vector map sub-tile, and block 710 can include transmitting the multiple requested vector map sub-tiles.
Using process 700, a mapping system can provide dynamically sized vector map tiles to an electronic device without having to store multiple sets of pre-generated vector map tiles. Additionally, since it can be significantly faster to divide a pre-generated vector map tile into segments using process 700, described above, than to generate a vector map tile, process 700 can be used to quickly provide an electronic device with an appropriately sized vector map tile. This advantageously reduces the amount of time required to download a vector map tile by the electronic device and reduces the amount of memory of the electronic device required to store the vector map tiles needed to render an image of a map. This can be particularly beneficial to compact electronic devices that have a relatively small amount of memory and/or limited bandwidth.
FIG. 22 shows a functional block diagram of an electronic device 2200 configured in accordance with the principles of the various described examples. The functional blocks of the device can be implemented by hardware, software, or a combination of hardware and software to carry out the principles of the various described examples. It is understood by persons of skill in the art that the functional blocks described in FIG. 22 can be combined or separated into sub-blocks to implement the principles of the various described examples. Therefore, the description herein optionally supports any possible combination or separation or further definition of the functional blocks described herein.
As shown in FIG. 22, electronic device 2200 can include a display unit 2204 configured to display graphical objects, a touch-sensitive surface unit 2202 configured to receive user gestures, and a processing unit 2208. In some examples, processing unit 2208 can include a receiving unit 2210, an identifying unit 2212, an accessing unit 2214, a generating unit 2216, a transmitting unit 2218, an encoding unit 2220, and a tagging unit 2222.
Processing unit 2208 can be configured to receive (e.g., using receiving unit 2210), from an electronic device, a request for a vector map sub-tile. Identifying unit 2212 can be configured to identify a vector map tile corresponding to the requested vector map sub-tile. Accessing unit 2214 can be configured to access the vector map tile. Generating unit 2218 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles, the plurality of vector map sub-tiles comprising the requested vector map sub-tile. Transmitting unit 2218 can be configured to transmit the requested vector map sub-tile to the electronic device.
In some examples, the vector map tile comprises vector data representing a portion of a map.
In some examples, accessing unit 2214 can be configured to access the vector map tile by retrieving the vector map tile from a storage of the one or more servers and decoding the vector map tile from an encoding format. In some examples, generating unit 2216 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises dividing the decoded vector map tile. In some examples, processing unit 2208 can be configured to encode (e.g., using encoding unit 2220) the requested vector map sub-tile into the encoding format prior to transmitting the requested vector map sub-tile to the electronic device.
In some examples, the vector map tile comprises a point map feature. In some examples, generating unit 2218 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles by determining whether the point map feature is located within the requested vector map sub-tile, in accordance with a determination that the point map feature is located within the requested vector map sub-tile, generating the requested vector map sub-tile to include the point map feature, and in accordance with a determination that the point map feature is not located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the point map feature. In some examples, the point map feature represents a point of interest.
In some examples, the vector map tile comprises a line map feature. In some examples, generating unit 2216 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles by determining whether the line map feature is located within the requested vector map sub-tile, in accordance with a determination that the line map feature is not at least partially located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the line map feature, in accordance with a determination that the line map feature is located entirely within the requested vector map sub-tile, generating the requested vector map sub-tile to include the line map feature, and in accordance with a determination that the line map feature is located partially within the requested vector map sub-tile: applying a flattening algorithm to the line map feature, generating a plurality of line segments by dividing the flattened line map feature at intersections between vector map sub-tiles of the plurality of vector map sub-tiles, applying a curve fitting algorithm to one or more line segments of the plurality of line segments located within the requested vector map sub-tile, and generating the requested vector map sub-tile to include the one or more line segments.
In some examples, processing unit 2208 can be further configured to tag (e.g., using tagging unit 2222) ends of the one or more line segments located at an edge of the requested vector map sub-tile to indicate that the one or more line segments connect to other line segments of other vector map sub-tiles in accordance with a determination that the line map feature is located partially within the requested vector map sub-tile. In some examples, the line map feature represents a road, a path, a highway, or a river.
In some examples, the vector map tile comprises a polygon map feature. In some examples, generating unit 2216 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles by determining whether the polygon map feature is located within the requested vector map sub-tile, in accordance with a determination that the polygon map feature is not at least partially located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the polygon map feature, in accordance with a determination that the polygon map feature is located entirely within the requested vector map sub-tile, generating the requested vector map sub-tile to include the line polygon feature, and in accordance with a determination that the polygon map feature is located partially within the requested vector map sub-tile: generating a plurality of polygon segments by dividing the polygon map feature at intersections between vector map sub-tiles of the plurality of vector map sub-tiles, and generating the requested vector map sub-tile to include one or more polygon segments of the plurality of polygon segments located within the requested vector map sub-tile.
In some examples, processing unit 2208 can be configured to tag (e.g., using tagging unit 2222) edges of the one or more polygon segments located at an edge of the requested vector map sub-tile to indicate that the tagged edges represent interior edges in accordance with a determination that the polygon map feature is located partially within the requested vector map sub-tile. In some examples, the line polygon map feature represents a body of water or an area of land.
In some examples, the vector map tile comprises a three-dimensional (3D) polygon map feature, the 3D polygon map feature having a two-dimensional (2D) base. In some examples, generating unit 2216 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles by determining whether the requested vector map sub-tile is a vector map sub-tile of the plurality of vector map sub-tiles having a largest portion of the 2D base located therein, in accordance with a determination that the requested vector map sub-tile is the vector map sub-tile of the plurality of vector map sub-tiles having the largest portion of the 2D base located therein, generating the requested vector map sub-tile to include the 3D polygon map feature, and in accordance with a determination that the requested vector map sub-tile is not the vector map sub-tile of the plurality of vector map sub-tiles having the largest portion of the 2D base located therein, generating the requested vector map sub-tile to exclude the 3D polygon map feature. In some examples, the line 3D polygon map feature represents a building.
In some examples, generating unit 2216 can be configured to generate the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles by generating the requested vector map sub-tile to include one or more attributes of the vector map tile. In some examples, the one or more attributes comprises a local North direction.
Although the disclosure and examples have been fully described with reference to the accompanying figures, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the appended claims.

Claims

What is claimed is:

1. A computer-implemented method comprising:

at one or more servers:

receiving, from an electronic device, a request for a vector map sub-tile;

identifying a vector map tile corresponding to the requested vector map sub-tile;

accessing the vector map tile;

generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles, the plurality of vector map sub-tiles comprising the requested vector map sub-tile; and

transmitting the requested vector map sub-tile to the electronic device.

2. The computer-implemented method of claim 1, wherein the vector map tile comprises vector data representing a portion of a map.

3. The computer-implemented method of claim 1, wherein accessing the vector map tile comprises:

retrieving the vector map tile from a storage of the one or more servers; and

decoding the vector map tile from an encoding format.

4. The computer-implemented method of claim 3, wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises dividing the decoded vector map tile.

5. The computer-implemented method of claim 3 further comprising:

at the one or more servers, encoding the requested vector map sub-tile into the encoding format prior to transmitting the requested vector map sub-tile to the electronic device.

6. The computer-implemented method of claim 1, wherein the vector map tile comprises a point map feature, and wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises:

at the one or more servers:

determining whether the point map feature is located within the requested vector map sub-tile;

in accordance with a determination that the point map feature is located within the requested vector map sub-tile, generating the requested vector map sub-tile to include the point map feature; and

in accordance with a determination that the point map feature is not located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the point map feature.

7. The computer-implemented method of claim 6, wherein the point map feature represents a point of interest.

8. The computer-implemented method of claim 1, wherein the vector map tile comprises a line map feature, and wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises:

at the one or more servers:

determining whether the line map feature is located within the requested vector map sub-tile;

in accordance with a determination that the line map feature is not at least partially located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the line map feature;

in accordance with a determination that the line map feature is located entirely within the requested vector map sub-tile, generating the requested vector map sub-tile to include the line map feature; and

in accordance with a determination that the line map feature is located partially within the requested vector map sub-tile:

applying a flattening algorithm to the line map feature;

generating a plurality of line segments by dividing the flattened line map feature at intersections between vector map sub-tiles of the plurality of vector map sub-tiles;

applying a curve fitting algorithm to one or more line segments of the plurality of line segments located within the requested vector map sub-tile; and

generating the requested vector map sub-tile to include the one or more line segments.

9. The computer-implemented method of claim 8 further comprising:

at the one or more servers:

in accordance with a determination that the line map feature is located partially within the requested vector map sub-tile, tagging ends of the one or more line segments located at an edge of the requested vector map sub-tile to indicate that the one or more line segments connect to other line segments of other vector map sub-tiles.

10. The computer-implemented method of claim 8, wherein the line map feature represents a road, a path, a highway, or a river.

11. The computer-implemented method of claim 1, wherein the vector map tile comprises a polygon map feature, and wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises:

at the one or more servers:

determining whether the polygon map feature is located within the requested vector map sub-tile;

in accordance with a determination that the polygon map feature is not at least partially located within the requested vector map sub-tile, generating the requested vector map sub-tile to exclude the polygon map feature;

in accordance with a determination that the polygon map feature is located entirely within the requested vector map sub-tile, generating the requested vector map sub-tile to include the line polygon feature; and

in accordance with a determination that the polygon map feature is located partially within the requested vector map sub-tile:

generating a plurality of polygon segments by dividing the polygon map feature at intersections between vector map sub-tiles of the plurality of vector map sub-tiles; and

generating the requested vector map sub-tile to include one or more polygon segments of the plurality of polygon segments located within the requested vector map sub-tile.

12. The computer-implemented method of claim 11 further comprising:

at the one or more servers:

in accordance with a determination that the polygon map feature is located partially within the requested vector map sub-tile, tagging edges of the one or more polygon segments located at an edge of the requested vector map sub-tile to indicate that the tagged edges represent interior edges.

13. The computer-implemented method of claim 11, wherein the line polygon map feature represents a body of water or an area of land.

14. The computer-implemented method of claim 1, wherein the vector map tile comprises a three-dimensional (3D) polygon map feature, the 3D polygon map feature having a two-dimensional (2D) base, and wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises:

at the one or more servers:

determining whether the requested vector map sub-tile is a vector map sub-tile of the plurality of vector map sub-tiles having a largest portion of the 2D base located therein;

in accordance with a determination that the requested vector map sub-tile is the vector map sub-tile of the plurality of vector map sub-tiles having the largest portion of the 2D base located therein, generating the requested vector map sub-tile to include the 3D polygon map feature; and

in accordance with a determination that the requested vector map sub-tile is not the vector map sub-tile of the plurality of vector map sub-tiles having the largest portion of the 2D base located therein, generating the requested vector map sub-tile to exclude the 3D polygon map feature.

15. The computer-implemented method of claim 14, wherein the line 3D polygon map feature represents a building.

16. The computer-implemented method of claim 1, wherein generating the requested vector map sub-tile by dividing the vector map tile into a plurality of vector map sub-tiles comprises:

at the one or more servers:

generating the requested vector map sub-tile to include one or more attributes of the vector map tile.

17. The computer-implemented method of claim 16, wherein the one or more attributes comprises a local North direction.

18. The computer-implemented method of claim 1, wherein the electronic device is a watch.

19. The computer-implemented method of claim 1, wherein the electronic device is a mobile phone.