Patent Grant
10508926
Many map-based applications available today are designed for a variety of different devices (e.g., desktops, laptops, tablet devices, smartphones, handheld global positioning system (GPS) receivers, etc.) and for various different purposes (e.g., navigation, browsing, sports, etc.). Most of these applications generate displays of a map based on map data that describes relative locations of streets, highways, points of interest, etc., in the map.
The maps used in such applications are usually two-dimensional (2D) maps or three-dimensional (3D) maps. However, a large number of the applications use 2D maps due in part to the processing-intensive demands of viewing 3D maps. For the same reason, the applications that use 3D maps are often slow, inefficient, plain, and/or simple, to the point that renders the application useless.
Some embodiments of the invention provide a device that includes a navigation application with several novel features. In some embodiments, the device has a touch-sensitive screen that displays the output of the application, and a multi-touch interface that allows a user to provide touch and gestural inputs through the screen to interact with the application.
In some embodiments, the novel features of the navigation application include (1) multiple different views (e.g., a two-dimensional turn-by-turn view, a three-dimensional turn-by-turn view, an overall route view, etc.) and smooth transitions between these views during the navigation, (2) novel user interface (UI) controls for navigation, (3) realistic looking road signs for identifying maneuvers along a navigated route, (4) dynamic generation of instructions and directional indicators for road signs and other presentations of the identified maneuvers, (5) informative navigation displays when the navigation application is operating in the background on the device, (6) novel voice recognition navigation guidance, and (7) integration with other routing applications available on or for the device.
While all these features are part of the navigation application in some embodiments, other embodiments do not employ all of these features in the navigation application. Also, in some embodiments, the navigation application is part of an integrated mapping application that provides several other useful operations, including location browsing, map searching, and route identifying operations. However, one of ordinary skill will realize that in other embodiments, the navigation application is a stand-alone application that does not include some or all of these other operations.
Each of the above-described features are described here. As mentioned above, the navigation application of some embodiments provides multiple different views during navigation and smooth transitions between these views. In some embodiments, examples of such views include a two-dimensional (2D) turn-by-turn view, a three-dimensional (3D) turn-by-turn view, and an overall route view. The application in some embodiments generates the turn-by-turn views from a perspective rendering position within a 3D navigation scene that the device renders. This perspective rendering position in some embodiments is adjustable and can be viewed as a virtual camera that can capture the 3D navigation scene from a variety of different perspectives (e.g., from a variety of different positions and orientations). Accordingly, in some embodiments, the turn-by-turn navigation is an animated rendering of navigated route that is rendered from the vantage point of a virtual camera that traverses along the direction of the route based on the traversal direction and speed of the user carrying the device, which in some embodiments is captured by directional data (e.g., GPS data, triangulated cell-tower data, etc.) associated with the device.
During navigation, the navigation application of some embodiments allows a user to change the position of the virtual camera (i.e., the position from which the navigated route is rendered) through gestural input on the device's screen. Movement of the virtual camera (i.e., movement of the position from which the route is rendered) allows the navigation application to present alternative 3D view. Some embodiments even use the virtual camera to render a top-down 2D view for the turn-by-turn navigation, while other embodiments render the top-down 2D view by zooming in and out of a 2D map.
In some embodiments, the navigation application presents a 3D control (e.g., button) that serves both as a 3D indicator and a 3D initiator/toggle. The 3D control is implemented in some embodiments as a floating control that can “float” above the 2D or 3D navigation presentation when it is needed and “float” out of the presentation when it is not needed. This control also serves as an indicator that the current view is a 3D view. The 3D control may have different appearances (e.g., colored as grey, black, blue, etc.) to provide different indications. In some embodiments, the 3D control is grey when 3D data is not available for the user's current location, black when the 3D data is available but the user is currently viewing the map in 2D, and purple when the user is viewing the map in 3D mode. In some embodiments, the 3D control displays an image of a building when the user is at a certain zoom level and provides a “flyover” of the buildings in the area when selected by the user. It also provides a quick mechanism of getting into and out of 3D navigation. As further described below, the navigation application allows transitions between the 2D and 3D navigation views through other gestural inputs of the multi-touch interface of the device.
The navigation application in some embodiments uses floating controls in order to keep the on-screen controls to a minimum and thereby display as much of the interactive navigation as possible. In some embodiments, the floating controls are part of a cluster of controls that adapt to the task at hand by adjusting its contents in an animated fashion when a user moves between different navigation views, or between different application modalities for embodiments in which the navigation is just one of several modalities of another application. This adaptive nature allows the navigation application to optimize for different tasks while maintaining a consistent look and interaction model while moving between those tasks.
When the navigation application starts a navigation presentation, the application in some embodiments (1) automatically hides the floating controls and a bar (containing other UI controls) on the top of a map along which the navigation is displayed, and (2) starts a full-screen turn-by-turn navigation presentation. In this mode, the application restricts touch interaction with the map. In some embodiments, a tap is required to access the controls that were automatically hidden. In some embodiments, these controls are adapted towards a full-screen navigation look, including a prominent display of the estimated time of arrival (ETA) in the bar along the top.
In some embodiments, one of the controls in the top bar is an overview button. By selecting this button at any time during the navigation, a user can seamlessly switch between the full-screen; turn-by-turn presentation that displays a view optimized for turn-by-turn directions; and an overview presentation that displays a view of the remaining route that better accommodate browsing.
In some embodiments, the constant set of controls and the in-place transition in the map provide continuity between the overview mode and the full-screen mode. These controls also include a control that allows the user to end the navigation in either the overview mode or full-screen model. Some embodiments also allow for a search to be performed while navigating. For instance, some embodiments provide a pull down handle that allows the search field to be pulled into the overview display while navigating in the overview mode. Alternatively, or conjunctively, some embodiments allow for searches to be performed during navigation through a voice-recognition input of the device of some embodiments. Also, in some embodiments, the application allows a user to perform searches (e.g., voice-initiated and/or text-based searches) during turn-by-turn navigation. The navigation application of some embodiments also allows navigation to be initiated through voice-recognition input of the device.
During navigation, the navigation application of some embodiments also allows a user to provide some gestural input without reference to the floating controls or the top-bar controls. For instance, different embodiments provide different gestural inputs to adjust the 2D/3D view during turn-by-turn navigation. In some embodiments, the gestural input is a two-finger pinching/spreading operation to adjust the zoom level. This adjustment of the zoom level inherently adjusts the position and rotation of the camera with respect to the route direction, and thereby changes the 2D/3D perspective view of the route direction. Alternatively, other embodiments provide other gestural inputs (e.g., a finger drag operation) that change the position of the camera instead of or in addition to the zoom operation. In yet other embodiments, a gestural input (e.g., a finger drag operation) momentarily changes the viewing direction of the camera to allow a user to momentarily glance to a side of the navigated route. In these embodiments, the application returns the camera to its previous view along the route after a short time period.
Another novel feature of the navigation application are the realistic-looking road signs that are used during navigation. In some embodiments, the signs are textured images that bear a strong resemblance to actual highway signs. These signs in some embodiments include instructional arrows, text, shields, and distance. The navigation application of some embodiments presents a wide number of sign variants in a large number of different contexts. Also, in some embodiments, the application presents signs in different colors according to the regional norms.
For maneuvers that are close together, the application in some embodiments presents a secondary sign beneath the primary sign. Also, as one maneuver is passed, the navigation application animates the sign passing away with a motion that mimics a sign passing overhead on the highway. When an upcoming maneuver is approaching, the navigation application draws attention to the sign with a subtle animation (e.g., a shimmer across the entire sign).
In some embodiments, the navigation application dynamically generates instructions for a road sign and other presentation (e.g., a list view) associated with a navigation maneuver based on the context under which the application is displaying the sign or presentation. For a given context, the instruction text is chosen by considering factors such as the available space, the availability of information conveyed by means other than text (e.g., the availability of voice guidance), the localized length of each of the instruction variants, the size of the display screen of the device, etc. By locally synthesizing and evaluating several alternatives, the application can pick an optimal instruction string in every scenario.
Similarly, the navigation application of some embodiments adaptively generates directional graphical indicators for a road sign and other presentation (e.g., a list view) associated with a navigation maneuver based on the context under which the application is displaying the sign or presentation. For instance, when there is sufficient space on a sign or presentation for the use of a bigger sign, the navigation application of some embodiments identifies a maneuver to perform at a juncture along a route by using a larger graphical directional indicator that includes (1) a prominent stylized arrow roughly representing the path of the vehicle, and (2) a de-emphasized set of lines and curves corresponding to other elements of the junction. In some embodiments that use this approach, a right turn at a T-junction is represented by a large arrow with a right-angle joined with a smaller, dimmer segment that runs parallel to one of the large arrow's segments. The smaller segment in some embodiments is also pushed off to the side so that the path taken by the vehicle dominates.
Such a representation of a maneuver (that includes a prominent stylized arrow and a de-emphasized set of lines) provides fairly complete information about the maneuver while remaining abstract and easily understandable. However, there may not be sufficient space on the sign or other presentation for such a representation in other contexts. Accordingly, for such cases, the navigation application of some embodiments uses an alternate representation of the maneuver that omits displaying the junction and instead only displays an arrow in the direction of movement.
To generate either the prominent stylized arrow or the simplified arrow for a juncture maneuver along a route, the navigation application in some embodiments receives from a server a description of the juncture and maneuver. In some embodiments, the server performs an automated process to generate this description based on map data, and provides this information in terms of compressed, geometric point data. Also, at the beginning of a route navigation, the server in some embodiments supplies to the navigation application the description of all junctures and maneuvers along the route, and occasionally updates this description when the user strays from the route and the server computes a new route.
When the navigation application receives the juncture and maneuver description, the application of some embodiments initially performs a process to simplify the characterization of the juncture and the maneuver, and then uses this simplified characterization to generate the prominent stylized graphical directional indicator for the juncture. To display a maneuver at a juncture, some navigation applications often provide a plain arrow that is not expressed in terms of the juncture and does not convey much information, while other navigation applications provide a very detailed representation of the juncture and a complex directional representation through this detailed representation. Thus, one existing approach provides very little information, while another approach provides so much information that the information is rendered practically useless. By generating the prominent stylized directional indicator based on the simplified description of the juncture, the navigation application of some embodiments displays a detailed representation of the maneuver at the juncture while eliminating some of the unnecessary complexities of the juncture.
In some embodiments, the navigation application provides navigation instructions while the application is operating in the background and even while the device is locked. In some embodiments, the device is locked when only a reduced set of controls can be used to provide input into the device. For instance, in some embodiments, the locking of the device greatly limits the number of inputs that a user can provide through the touch-sensitive screen of the device.
In some embodiments, voice guidance instructions are one example of instructions that can be provided while the navigation application is operating in the background or while the device is locked. Alternatively to, or conjunctively with, the voice guidance, the navigation application can provide text and/or graphical instructions in at least two modes while operating in the background.
First, the application of some embodiments incorporates in the lock screen background, a live navigation view (e.g., a turn-by-turn view) that includes text and graphical navigation description in the lock-screen display. With this presentation, the user can see the navigation instructions while the application is running in the background without unlocking the device. In some embodiments, the application further refines the lock screen experience by sending notifications that would normally occupy the space being taken by the navigation display to a drawer in the lock-screen display, which in some embodiments is done immediately while in other embodiments is done after a short time period in which the notification is shown on the lock screen view. Also, whenever a user unlocks the device, some embodiments return without animation to the navigation display in order to make the experience seamless.
In some embodiments, the application turns off the lock screen navigation display after a time period if no maneuvers are impending. However, the application in some of these embodiments lights up the screen when approaching an imminent maneuver and/or new navigation instructions need to be provided. This is a small amount of time relative to the duration of each step, so the display of the navigation instructions does not come at the expense of noticeably degraded battery life. To enhance the experience, the navigation application in some embodiments activates an ambient light sensor well before the navigation prompt so that the ambient light settings can be used to light the screen to the correct brightness when it comes time to show the navigation map.
Second, in some embodiments, the navigation application operates in the background even when the device is unlocked. This is the case when the navigation application operates on a device (e.g., a smartphone) that executes several other applications. In such a device, the navigation application would operate in the background when the device is presenting a view (e.g., a page) that is provided by the operating system of the device or a view that is provided by another application on the device.
When the navigation application operates in the background on an unlocked device, the device in some embodiments (1) uses a double-height status bar to indicate the background operation of the navigation application when far from an upcoming maneuver, and (2) uses a sign-like navigation banner that includes dynamically updated distance to a maneuver when approaching a maneuver or when guidance instructions are audible. Further, the application maintains the sign-like banner until the maneuver is complete and suppresses other notifications in that space. Selection of either the double-height status bar or the navigation banner in some embodiments directs the device to switch to a navigation view generated by the navigation application.
The above-described features as well as some other features of the navigation application of some embodiments are further described below. In the description above and below, many of the features are described as part of an integrated mapping application that provides novel location browsing, location searching, route identifying and route navigating operations. However, one of ordinary skill will realize that these novel operations are performed in other embodiments by applications that do not perform all of these operations, or perform other operations in addition to these operations.
The preceding Summary is intended to serve as a brief introduction to some embodiments of the invention. It is not meant to be an introduction or overview of all inventive subject matter disclosed in this document. The Detailed Description that follows and the Drawings that are referred to in the Detailed Description will further describe the embodiments described in the Summary as well as other embodiments. Accordingly, to understand all the embodiments described by this document, a full review of the Summary, Detailed Description and the Drawings is needed. Moreover, the claimed subject matters are not to be limited by the illustrative details in the Summary, Detailed Description and the Drawings, but rather are to be defined by the appended claims, because the claimed subject matters can be embodied in other specific forms without departing from the spirit of the subject matters.
The novel features of the invention are set forth in the appended claims. However, for purposes of explanation, several embodiments of the invention are set forth in the following figures.
In the following detailed description of the invention, numerous details, examples, and embodiments of the invention are set forth and described. However, it will be clear and apparent to one skilled in the art that the invention is not limited to the embodiments set forth and that the invention may be practiced without some of the specific details and examples discussed.
I. Navigation User Interface
A. Start
The navigation application of some embodiments is part of an integrated mapping application that includes several useful modalities, including location browsing, map searching, route identifying and route navigating operations. This integrated application (referred to below as the mapping application, the navigation application, or the integrated application) in some embodiments is defined to be executed by a device that has a touch-sensitive screen that displays the output of the application. In some embodiments, this device has a multi-touch interface for allowing a user to provide touch and gestural inputs through the screen to interact with the application. Examples of such devices are smartphones (e.g., iPhone® sold by Apple Inc., phones operating the Android® operating system, phones operating the Windows 8® operating system, etc.).
The second stage 110 shows the device after the mapping application has opened. As shown in this stage, the mapping application's UI has a starting page that in some embodiments displays (1) a map of the current location of the device and (2) several UI controls arranged in a top bar 140, and as floating controls. As shown in
In some embodiments, a user can initiate a search by tapping in the search field 165. This directs the application to present an animation that (1) presents an on-screen keyboard and (2) opens a search table full of invaluable completions. This table has some important subtleties. When the search field is tapped and before the terms are edited, or when the search field is empty, the table contains a list of “recents,” which in some embodiments are recent searches and route directions that the user has requested. This makes it very easy to quickly bring up recently accessed results.
After any input on the search field, the table is filled with search completions both from local sources (e.g., bookmarks, contacts, recent searches, recent route directions, etc.) and remote servers. The incorporation of the user's contact card into the search interface adds additional flexibility to the design. When showing recents, a route from the current location to the user's home is always offered in some embodiments, while it is offered in the contexts that are deemed to be “appropriate” in other embodiments. Also, when the search term matches at least part of an address label (e.g., ‘ork’ for ‘Work’), the application presents the user's labeled address as a completion in the search table in some embodiments. Together these behaviors make the search UI a very powerful way to get results onto a map from a variety of sources. In addition to allowing a user to initiate a search, the presence of the text field in the primary map view in some embodiments also allows users to see the query corresponding to search results on the map and to remove those search results by clearing the query.
The bookmark control 170 (e.g., button) allows location and routes to be bookmarked by the application. The position indicator 145 allows the current position of the device to be specifically noted on the map. Once this indicator is selected, the application maintains the current position of the device in the center of the map. In some embodiments, it can also identify the direction to which the device currently points.
The 3D control 150 is a control for viewing a map or inspecting a route in three dimensions (3D). The mapping application provides the 3D control as a quick mechanism of getting into and out of 3D. This control also serves as (1) an indicator that the current view is a 3D view, (2) an indicator that a 3D perspective is available for a given map view (e.g., a map view that is zoomed out might not have a 3D view available), (3) an indicator that a 3D perspective is not available (e.g., the 3D data is not available for the map region), and (4) an indicator that a flyover animation is available at the given zoom level. The 3D control may provide a different appearance corresponding to each indication. For instance, the 3D control may be colored grey when the 3D view is unavailable, black when the 3D view is available but the map is in the 2D view, and blue when the map is in the 3D view. In some embodiments, the 3D control changes to an image of a building when the flyover animation is available for the user's given zoom level and location on the map.
The page curl control 155 is a control that allows the application to minimize the number of on-screen controls, by placing certain less frequently used actions in a secondary UI screen that is accessible through the page curl control that is displayed on the map. In some embodiments, the page curl is permanently displayed on at least some of the map views that the application provides. For instance, in some embodiments, the application displays the page curl permanently on the starting page (illustrated in the second stage 110) that it provides for allowing a user to browse or search for a location or to identify a route.
The direction control 160 opens a direction entry page 180 through which a user can request a route to be identified between a starting location and an ending location. The third stage 115 of
The fourth stage 117 shows that the direction entry page 180 includes starting and ending fields for providing starting and ending locations for a route, and a table that lists recent routes that the application has provided to the user. Other controls on this page are controls for starting a route, for reversing the order of the start and end locations, for canceling the direction request, for picking walking, auto, or public transit routes. These controls and other aspects of the mapping application are described in U.S. patent application Ser. No. 13/632,102 now issued as U.S. Pat. No. 9,052,197, entitled “Problem Reporting in Maps.” U.S. patent application Ser. No. 13/632,102 is incorporated herein by reference.
The fourth stage illustrates the user selecting one of the recent directions that was auto-populated in the table 182. The fifth stage 119 then shows three routes on a 2D map view between the specified start and end locations specified through the page 180. It also shows the selection of the second route and some information about this route in a bar at the top of the layout. This bar is shown to include start and end buttons. The start button is shown to be selected in the fifth stage.
As shown in the sixth stage, the selection of the start button directs the application to enter a turn-by-turn navigation mode. In this example, the application has entered a 2D turn-by-turn navigation mode. In other embodiments, the application will enter by default into a 3D turn-by-turn navigation mode. In this mode, the application displays a realistic sign 184 that identifies the distance from the current location of the device to the next juncture maneuver in the navigated route and some other pertinent information. The application also displays a top bar that includes some information about the navigation as well as End and Overview buttons, for respectively ending the navigation and obtaining an overview of the remaining portion of the navigated route or the entire portion of the navigated route in other embodiments.
The mapping application of some embodiments identifies the location of the device using the coordinates (e.g., longitudinal, altitudinal, and latitudinal coordinates) in the GPS signal that the device receives at the location of the device. Alternatively or conjunctively, the mapping application uses other methods (e.g., cell tower triangulation) to compute the current location. When the user carrying the device deviates from the route, the mapping application of some embodiments tracks the location of the device and re-calculates a new route from the deviated location in order to re-direct the user to the destination location from the deviated location. In other words, the mapping application of some embodiments operating in the navigation mode requires the device to be on a route at all times.
The application further displays the floating 3D control and the floating list control, which were described above. It should be noted that the list control was adaptively added to the floating control cluster upon entering the route inspection and route navigation modalities, while the position indicator was removed from the floating control upon entering the route navigation modality. Also, upon transition from the route inspection mode to the route navigation mode, the application performs an animation in some embodiments that involves the page curl uncurling completely before the application transitions into the navigation presentation.
In some embodiments, the animation transition includes removing the top bar, its associated controls and the floating controls from the navigation presentation, and moving the sign 184 to the top edge of the presentation a short time period after starting the navigation presentation. As further described below, the application requires the user tap on the navigated map to bring back the top bar, its controls and the floating controls, and requires another tap to remove these controls again from the map, in some embodiments. Other embodiments provide other mechanisms for viewing and removing these controls.
As another way of allowing the user to get navigation experience, the mapping application of some embodiments provides a UI item in an informational banner that appears by a pin that represents a point of interest (POI).
The first stage 205 illustrates a map in a 3D map view. As shown, a 3D control 250 appears highlighted to indicate that the map is in a 3D map view. The first stage 205 also illustrates two informational banners for the two pins for the search resulting from running a search with a search query “Pizza” as shown. The user selects the car icon 230. As mentioned above, the car icon 230 is for showing one or more routes to the location that is represented by a pin with which the banner that includes the car icon 230 is associated. The banner 240 which includes the car icon 230 also shows a brief description of the place, a star rating, and an arrow for launching a “stage” for the POI.
The second stage 210 illustrates the two routes, route 1 and route 2, that the mapping application of some embodiments shows in response to the selection of the car icon 230 in the previous stage 205. The user has selected route 1 as indicated by the highlight on the route 1. The user also selects the start button. As mentioned above, the start button in some embodiments is for starting the navigation according to the selected route.
The third stage 215 illustrates that the mapping application displays an instruction sign 260, which is the sign for the first instruction. The mapping application has replaced the clear control 255 and the start button with an end button 270 and an overview control 275 in the top bar 140. The end button is for ending the navigation of the route and the overview control 275 is for showing the entire route in the map view by adjusting the zoom level of the displayed map if adjusting the zoom level is necessary to show the entire route. In some embodiments, the mapping application displays in the top bar 140 the ETA, the amount of time to get to the destination, and the remaining distance to the destination as shown.
When the mapping application receives a selection of the end button while the mapping application is operating in the route inspection mode, the mapping application of some embodiments stops inspection of the selected route by going back to map browsing mode. The mapping application of some embodiments goes back to the map browsing mode by removing the selected route from the map, putting back the page curl, and replacing the information and controls in the top bar with a set of other controls including a direction control, a search field, and a bookmark control. That is, the mapping application takes the appearance of the UI page back to a UI page similar to the UI page shown in the first stage 205. The mapping application of some embodiments does not shift the map to another region when switching to the map browsing mode from the inspection mode.
B. 2D and 3D Navigation
The navigation application of some embodiments can display navigation in either a 2D mode or a 3D mode. As mentioned above, one of the floating controls is the 3D control 250 that allows a user to view a navigation presentation in three dimensions (3D).
The second stage 310 illustrates the navigation presentation in the midst of its transition into a 3D presentation. As shown in this figure, the 3D control appears highlighted at this stage to indicate that the navigation presentation has entered a 3D mode. As mentioned above, the navigation application generates the 3D view of the navigated map in some embodiments by rendering the map view from a particular position in the three dimensional scene that can be conceptually thought of as the position of a virtual camera that is capturing the map view. This rendering is further described below by reference to
The third stage 315 then illustrates the navigation presentation at the end of its transition into its 3D appearance. As shown by the difference between the heights of the buildings in the second and third stages, the transition from 2D to 3D navigation in some embodiments includes an animation that shows three-dimensional objects in the navigated map becoming larger. Generating such animation that shows objects rising/falling and becoming larger/smaller is further described in the U.S. patent application Ser. No. 13/632,027, now published as U.S. Patent Publication number 2014/0071119, entitled “Displaying 3D Objects in a 3D Map Presentation.” U.S. patent application Ser. No. 13/632,027 is incorporated herein by reference.
Some embodiments use a cinematic transition from the 2D map view to the 3D map view or vice versa. For instance, when the mapping application receives a selection of the 3D control 250 while showing a starting location of a route, the mapping application begins from the 2D map view and transitions smoothly from a first virtual camera view for the 2D to a new virtual camera 3D view that is more zoomed in and pointing in the direction of the start of the route. In doing so, the virtual camera performs a combination of translation, zoom, and rotation operations in order to reach the start of the route for navigation. That is, the virtual camera moves in an arc and rotates upward as the camera moves downward along the arc. Also, the mapping application may rotate the arc itself to align the virtual camera viewpoint to the initial road segment of the route. In other words, the mapping application rotates the map during the cinematic transition.
The first stage 405 illustrates a user selecting a quick-route button for a location “Pizza Place” in order to generate a route from the user's current location (near the center of the screen of device 400) to the selected location. The second stage 410 illustrates the mapping application displaying a route 435 to reach the location “Pizza Place.” At the second stage 410, the user selects the “Start” UI control 440. Accordingly, the application begins entering navigation.
As shown at the third through sixth stages 415-430, some embodiments use a cinematic transition from the 2D (or 3D) non-immersive map view into the 3D immersive map view. The application display begins from its current state (that shown at 410) and transitions smoothly from the first virtual camera view to the new virtual camera view that is more zoomed in and pointing in the direction of the start of the route. In doing so, the virtual camera may perform a combination of translation, zoom, and rotation operations in order to reach the start of the route for navigation. As shown in these stages, the virtual camera moves and rotates into its eventual location behind the navigation location indicator (i.e., the puck) shown in the sixth stage 430.
Also, in some embodiments, the mapping application provides two different types of 3D presentations—an immersive 3D presentation and a non-immersive 3D presentation. The immersive presentation in some embodiments not only displays more geometries but also displays more details for the geometries that are displayed in the non-immersive presentation. The mapping application also provides smooth transitions between the non-immersive and immersive presentations.
To achieve such smooth transitions and generate other novel effects, the mapping application of some embodiments uses a novel image processing pipeline. This pipeline performs a variety of pre-load operations to download, retrieve and/or decompress map tiles that may be needed for a navigation presentation, to prepare its rendering pipeline for its rendering operations, and to prepare a duplicate pipeline to smoothly transition between the immersive and non-immersive 3D presentations. In order to display immersive and non-immersive 3D map presentations, some embodiments have to generate a variety of tiles for client devices to render in order to generate roads, building, and surrounding scenery. In some embodiments, examples of such tiles include road and building tiles used for non-immersive 3D presentations, and navigation and building tiles used for immersive 3D presentations. This pipeline is described in above-incorporated U.S. patent application Ser. No. 13/632,102, now published as U.S. Patent Publication number 2013/0326407, entitled “Problem Reporting in Maps.”. This pipeline is also described in detail in the U.S. patent application Ser. No. 13/632,040, now issued as U.S. Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.”. U.S. patent application Ser. No. 13/632,040 is incorporated herein by reference.
In some embodiments, the non-immersive and immersive viewing modes are viewing modes for viewing different 3D maps that have different constructs and/or geometries. For instance, the non-immersive viewing mode of some embodiments is for viewing a 3D map that includes roads, buildings, land cover, etc. The immersive viewing mode is for viewing a more detailed 3D map that includes the same or similar elements (e.g., roads, buildings, land cover, etc.) as the 3D map for the non-immersive viewing mode. However, this more detailed 3D map also includes higher detail constructs (e.g., trees, foliage, sidewalks, medians, lanes of roads, road asphalt, medians, cross walks, etc.) that provide a more realistic and rich 3D map.
In addition, the non-immersive and immersive viewing modes may be defined for viewing 3D maps at different ranges of zoom levels. For example, the non-immersive viewing mode of some embodiments is defined for viewing a 3D map at low zoom levels (e.g., zoom levels 0-14) while the immersive viewing mode of some embodiments is defined for viewing the 3D map at high zoom levels (e.g., zoom levels 16-21). The viewing modes may be defined to view any number of different zoom levels in different embodiments. In some instances, the range of zoom levels of the immersive viewing mode are defined as higher zoom levels than, lower zoom levels than, the same zoom levels as, or zoom levels that overlap with the zoom levels defined for the non-immersive viewing mode. These viewing modes and other aspects of the mapping application are described in the U.S. patent application Ser. No. 13/632,040, now issued as U.S. Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.” U.S. patent application Ser. No. 13/632,040 is incorporated herein by reference.
1. Virtual Camera
The navigation application of some embodiments is capable of displaying navigation maps from multiple perspectives. The application can show maps in three dimensions (3D) or in two dimensions (2D). The 3D maps are generated simulations of a virtual scene as seen by a virtual camera.
The first stage 501 shows the virtual camera 512 at a first position pointing downwards at an angle (e.g., a 30 degree angle) towards the 3D scene 510. By rendering the 3D scene from the position and angle shown in stage 501 the application generates the 3D map view 518. From this position, the camera is pointing at a location that is a moving position in front of the device. The virtual camera 512 is kept behind the current location of the device. “Behind the current location” in this case means backward along the navigation application's defined path in the opposite direction from the current direction that the device is moving in.
The navigation map view 518 looks as though it was shot by a camera from above and behind the device's location indicator 516. The location and angle of the virtual camera places the location indicator 516 near the bottom of the navigation map view 518. This also results in the majority of the screen being filled with the streets and buildings ahead of the present location of the device. In contrast, in some embodiments, the location indicator 516 is in the center of the screen, with half of the screen representing things ahead of the device and the other half representing things behind the device. To simplify the figure, no road signs are depicted for the views 518, 528, and 538.
The second stage 502 shows the virtual camera 512 at a different position, pointing downwards towards the scene 510 at a larger second angle (e.g., −45°). The application renders the scene 510 from this angle, resulting in the 3D navigation map view 528. The buildings and the roads are smaller than their illustration in the first navigation map view 518. Once again the virtual camera 512 is above and behind the location indicator 516 in the scene 510. This again results in the location indicator appearing in the lower part of the 3D map view 528. The location and orientation of the camera also results again in the majority of the screen displaying things ahead of the location indicator 516 (i.e., the location of the car carrying the device), which is what someone navigating needs to know.
The third stage 503 shows the virtual camera 512 at a top-down view that looks downwards on a location in the 3D map scene 510 that was used to render the 3D views 518 and 528. The scene that is rendered from this perspective is the 2D map view 538. Unlike the 3D rendering operations of the first and second stages that in some embodiments are perspective 3D rendering operations, the rendering operation in the third stage is relatively simple as it only needs to crop a portion of the 2D map that is identified by a zoom level specified by the application or the user. Accordingly, the virtual camera characterization in this situation somewhat unnecessarily complicates the description of the operation of the application as cropping a portion of a 2D map is not a perspective rendering operation.
At the third stage 503, the mapping application in some embodiments switches from rendering a 3D scene from a particular perspective direction to cropping a 2D scene when the camera switches from the 3D perspective view to a 2D top-down view. This is because in these embodiments, the application is designed to use a simplified rendering operation that is easier and that does not generate unnecessary perspective artifacts. In other embodiments, however, the mapping application uses a perspective rendering operation to render a 3D scene from a top-down virtual camera position. In these embodiments, the 2D map view that is generated is somewhat different than the map view 538 illustrated in the third stage 503, because any object that is away from the center of the view is distorted, with the distortions being greater the further the object's distance from the center of the view.
The virtual camera 512 moves along different trajectories in different embodiments. Two such trajectories 550 and 555 are illustrated in
While moving along one of the arcs, the camera rotates to maintain a point ahead of the location indicator at the focal point of the camera. In some embodiments, the user can turn off the three dimensional view and go with a purely two dimensional view. For example, the application of some embodiments allows a three dimensional mode to be turned on and off by use of a 3D button 560. The 3D button 560 is essential to the turn-by-turn navigation feature, where it has a role as an indicator and a toggle. When 3D is turned off, the camera will maintain a 2D navigation experience, but when 3D is turned on, there may still be some top-down perspectives when 3D viewing angles are not appropriate (e.g., when going around a corner that would be obstructed in 3D mode).
2. 3D Control
The second stage 610 shows that the mapping application is displaying the map at a higher zoom level than it did at the previous stage 605. However, the 3D control 150 is maintaining the first appearance because the 3D map data is still not available even at this particular higher zoom level. The second stage 610 also shows that the mapping application is receiving another gestural input to zoom in on the map further.
The third stage 615 shows that the mapping application is displaying the map at a higher zoom level than it did at the previous stage 610. The mapping application has changed the appearance of the 3D control 150 into a second appearance (e.g., “3D” in black letters) to indicate that the 3D map data is available at this zoom level. When the mapping application receives a selection of the 3D control 150, the mapping application of some embodiments would change the appearance of the 3D control 150 to a third appearance (e.g., “3D” in blue letters) and display the map in 3D (e.g., by changing into a perspective view from a straight-down view for 2D). The third appearance therefore would indicate that the map is displayed in 3D. The third stage 615 shows that the mapping application is receiving yet another gestural input to zoom in the map even further to a higher zoom level. The third stage 615 shows that the mapping application is displaying buildings in the map as grey boxes at this zoom level.
The fourth stage 620 shows that the mapping application is displaying the map at a higher zoom level than it did at the previous stage 615. The mapping application has changed the appearance of the 3D control 150 into a fourth appearance (e.g., a building icon in a first color as shown) in order to indicate that 3D immersive map data for rendering an immersive 3D map view is available at this zoom level. The fourth stage 620 also shows that the mapping application of some embodiments is receiving a selection of the 3D control 150.
The fifth and sixth stages 625 and 630 show subsequent views (though not necessarily successive views) that the mapping application provides after it starts to provide a 3D immersive map view. The zoom level does not change between the fifth and sixth stages in some embodiments but the height of the buildings in the map views increases to provide an animation that conveys that the view is moving into the 3D immersive map view from the 2D view. Also, from the fourth stage 620 to the fifth stage 625, the mapping application has changed the appearance of the 3D control into the fifth appearance (e.g., a building icon in a second color as shown) in order to indicate that the map is displayed in the 3D immersive view.
3. Automatic Changing of Views
The application of some embodiments allows any particular virtual camera angle to be used, not just the 30 degree and 60 degree angles specified here. The application of some embodiments allows the user to set the downward angle for the camera. The application of some embodiments automatically adjusts the angle of the camera for various reasons, (e.g., to keep a particular point of focus near the top of the screen). In still other embodiments, the navigation application automatically sets the angle of the camera, but allows the user to override the automatically set angle.
In some embodiments, when a device running the navigation application in a 3D mode is about to reach a junction with a turn, the navigation application switches to a 2D mode in order to enable the user to more clearly identify the turn.
As the device approaches the junction in stage 702 (as indicated by navigation box 720) the 3D map 712 switches to a 2D map 722 with the location indicator 724 in 2D as well. The mapping application also changes the appearance of the 3D control 150 to indicate that the map is now in 2D. The map 722 remains in 2D as the device rounds the corner in stage 703. As the device rounds the corner, the navigation box 730 with the instructions “turn right into A St.” in stage 703 is replaced by the navigation box 740 with the instructions “0.5 miles continue straight on A St.” in stage 704. The map remains in 2D in stage 704 until the corner has been fully navigated at which point, in stage 705, the map returns to a 3D view with new instructions “0.3 miles Destination will be on your left” in navigation box 750. The mapping application also has changed the appearance of the 3D control 150 to indicate the map is now back in 3D.
In some embodiments, the navigation application determines some or all of the following five pieces of information for every location update (e.g., 1 time per second). First, the navigation application determines the location of the point of reference (i.e. the user's location).
Second, the navigation application determines the location of the point of focus of the virtual camera, which is used to determine which direction the virtual camera should face. If the user is off-route, the point of focus will be a fixed distance ahead of the user along the user's direction of travel (if that can be determined) or a fixed distance north of the user (if the user's direction of travel cannot be determined). If the user is on-route, the point of focus will be a fixed distance ahead of the user along the route, with the angle between the vector from the user and this point of focus and the user's travel direction capped at a maximum value. This allows the virtual camera to subtly peek around turns before the user actually turns. For example, if the route turns a corner shortly ahead, the point of focus will be a point around the corner from the current location of the device. As turning the virtual camera to face that actual point could cause the virtual camera to directly face a building, the virtual camera is capped as to how far off the present direction it can look. Third, the navigation application determines the location of the point of interest (e.g., the location of an upcoming intersection).
Fourth, the navigation application determines the virtual camera view style (top-down centered, top-down forward, or rooftop). “Top-down centered” means that the virtual camera should look straight down on the user's location such that the user's location is in the center of the screen. “Top-down forward” means the virtual camera should look straight down on the user's location such that the user's location is toward the bottom of the screen. “Rooftop” means the virtual camera should be behind the user's location and pitched so that it is looking forward along the vector from the user's location to the point of focus. If the user is off-route or the user's direction of travel cannot be determined (e.g., when the user is parked), the virtual camera will be in top-down centered view style. Otherwise, the view style will be determined by whether the user has requested “2D” navigation or not. If the user has requested 2D navigation, the view style will be top-down forward. Otherwise, the view style will be rooftop.
Fifth, the navigation application determines the virtual camera focus style (e.g., cruise or hard focus). “Cruise focus style” means the virtual camera should adopt a preset height and pitch angle based on the view style. “Hard focus” means that the virtual camera should adjust its height (in the case of top-down centered or top-down forward view styles) or pitch (in the case of rooftop view style) so that the given point-of-interest is just on screen (i.e. the virtual camera should focus in on the point-of-interest as the user approaches it). When far from an intersection, the navigation application puts the virtual camera in cruise focus mode. When approaching an ‘interesting’ intersection, the navigation application puts the virtual camera in hard focus mode as described above and the location of the intersection (point of interest) will be passed to the virtual camera. When in hard focus mode, the application adjusts the virtual camera's height (in the case of top-down centered or top-down forward view styles) or pitch (in the case of rooftop view style) so that the intersection is at a reasonable position on screen. A given intersection is determined to be ‘interesting’ enough to focus on using the angle at which the user will leave the intersection. If the angle is large enough (e.g., a 90 degree right turn), the intersection is considered to be ‘interesting’ and the virtual camera will focus on it. If the angle is too small (e.g., merging onto a freeway), the virtual camera will stay in cruise focus style
From these five pieces of information, the navigation application computes the virtual camera's desired position and orientation. From the desired position and orientation, the positions of the following three key points can be extracted: (1) the virtual camera's position, (2) the intersection between the virtual camera's forward vector and the ground, and (3) a point along the virtual camera's right vector. The three points are animated independently from each other as follows: (1) when a new point is available, the application fits a cubic polynomial between the last evaluated position/tangent for that point and the new point and (2) every step of the animation, the navigation application evaluates the cubic polynomials for each curve and extracts the virtual camera position and orientation from them.
4. User Adjustment of Camera Height
Besides (or instead of) having the navigation application control the camera (e.g., turning from 3D to 2D when going around corners) some embodiments also allow the user to adjust the level of the camera. Some embodiments allow the user to make a command gesture with two fingers to adjust the distance (height) and angle of the camera. Some embodiments even allow multiple types of gestures to control the camera.
In stage 802, the user makes a gesture by placing two fingertips near each other on the screen of the device, on the screen view 824 and moving the fingertips apart while they are on the screen. Moving the fingertips apart has the effect of making the map (both the part between the fingers and the rest of the map) larger. In order to make the things in the map appear larger, the application causes the virtual camera 812 to zoom in. In some embodiments, the line 850 that the mapping application uses to move the virtual camera 812 along is a line formed by the front of the virtual camera 812 and the virtual camera 812's point of focus. The mapping application of some embodiments moves the virtual camera 812 along a line formed by the front of the virtual camera 812 and a location in the 3D map 810 based on the user's input to zoom into the view of the 3D map 810.
After zooming in for stage 802, the user decides to zoom out for stage 803. In this stage the user has placed two fingers on the screen and brought them closer together. Bringing the fingers closer together has the effect of shrinking the map (both the part between the fingers and the rest of the map). The zoom-out adjustment is accomplished by moving the virtual camera 812 moving farther away from the 3D map 810 along the line 855. In some embodiments, the line 855 that the mapping application uses to move the virtual camera 812 along is a line formed by the front of the virtual camera 812 and the virtual camera 812's point of focus. The mapping application of some embodiments moves the virtual camera 812 along a line formed by the front of the virtual camera 812 and a location in the 3D map 810 based on the user's input to zoom into the view of the 3D map 810.
Rendering a 3D map view using the virtual camera 812 at this position results in a 3D map view 834 in which the buildings and the roads appear farther than the position illustrated in the 3D map view 824. As shown by the dashed-line version of the virtual camera 812, the virtual camera 812 moved farther from the 3D map 810 along the line 855.
In addition to being controllable by zooming in and out, some applications allow a user to change the angle of the virtual camera.
In stage 902, the user has placed two fingers 920 on the screen approximately horizontal to each other and dragged up. This has the apparent effect of dragging the scene up with the fingers. The scene rising is accomplished by the virtual camera 912 lowering and changing its viewing angle from 45 degrees to 30 degrees. In the screen view 924, the buildings and the location indicator look taller than in stage 901.
After the user drags the scene up in stage 902, the user then drags the scene down in stage 903. To do this, the user again placed two fingers 930 on the screen and drags them down. This drags the scene down along with the fingers 930. The scene dropping is accomplished by the virtual camera 912 rising and changing its angle with the scene 910 to 60 degrees downward. In stage 903, the camera 912 has moved farther up and is angled down more than in stage 901. Accordingly, the buildings and location identifier 916 again look shorter and smaller in stage 903 than in stage 901.
In some embodiments, the mapping application provides an inertia effect for different operations (e.g., panning, rotating, entering from 2D to 3D). When a user provides a particular type of input (e.g., input that terminates at a velocity greater than a threshold velocity) to pan the 3D map, the mapping application generates an inertia effect that causes the 3D map to continue panning and decelerate to a stop. The inertia effect in some embodiments provides the user with a more realistic interaction with the 3D map that mimics behaviors in the real world. Details of inertia effects and implementations of inertia effects are described in U.S. patent application Ser. No. 13/632,040, now issued as U.S. Pat. No. 9,269,178, entitled “Virtual Camera for 3D Maps.” U.S. patent application Ser. No. 13/632,040 is incorporated herein by reference.
The application of some embodiments allows the distance and angle of the camera to be independently controlled. For example, it allows the distance to be controlled by the contracting and expanding finger gestures and the angle to be controlled by the dragging of horizontally placed fingers. Other embodiments use whichever gesture is being performed to set either a distance or an angle of the camera, with the other variable being set automatically. While
The first stage 1005 shows the virtual camera 1000 at a particular position along the arc 1050. As shown, the arc 1050 represents a defined range (e.g., angular range) within which the virtual camera 1000 is movable. The first stage 1005 also shows three positions 1055-1065 along the arc 1050 (e.g., perspective view angles). In this example, the mapping application moves the virtual camera 1000 along the arc 1050 between the high perspective end of the arc 1050 (e.g., the position along the arc 1050 when the virtual camera 1000 is most tilted downwards) and the position 1055 in a manner similar to that described above by reference to
When the virtual camera 1000 passes the position 1055 while moving towards the low perspective end of the arc 1050, the mapping application reduces the speed (e.g., decelerates) that the virtual camera 1000 moves towards the low perspective end of the arc 1050 regardless of the input provided by a user. In some embodiments, the mapping application reduces the speed of the virtual camera 1000 at a constant rate while, in other embodiments, the mapping application reduces the speed of the virtual camera 1000 at an exponential rate. Additional and/or different methods for decreasing the speed of the virtual camera 1000 are used in some embodiments.
The second stage 1010 shows that the virtual camera 1000 has moved to a position along the arc 1050 at or near the low perspective end of the arc 1050. As shown, a user is providing input to adjust the perspective of the view of the 3D map 1035 by touching two fingers on the screen and dragging the two fingers in an upward direction (e.g., a swipe gesture). In response to the input, the mapping application moved the virtual camera 1000 toward the low perspective end of the arc 1050 while tilting the virtual camera 1050 upwards. When the virtual camera reaches the position 1065 along the arc 1050, the mapping application prevents the virtual camera 1000 from moving lower and beyond the position 1065 even while the user continues to provide input to decrease the perspective of the view of the 3D map 1035 (e.g., the user continues to drag the two fingers upwards on the touchscreen).
In some embodiments, when the user stops providing input to decrease the perspective of the view of the 3D map 1035 (e.g., the user lifts the two fingers off the touchscreen), the mapping application “bounces” or “snaps” the position of the virtual camera 1000 from the position 1065 up to the position 1060 along the arc 1050. As the mapping application is generating or rendering 3D map views of the 3D map 1035 based on the view of the virtual camera 1000 during the bounce or snap motion, the generated 3D map views provide a bounce animation that displays the 3D map view briefly bouncing or snapping down in order to indicate to the user that the perspective of the map view cannot be decreased any farther. Rendering a 3D map view using the virtual camera 1000 positioned at this angle results in a 3D map view 1030 in which the buildings and the roads are taller compared to the map view 1025.
The third stage 1015 shows the virtual camera 1000 after the mapping application has bounced or snapped the position of the virtual camera 1000 to the position 1060 in response to the user ceasing to provide input. Different embodiments use different techniques for implementing the bounce or snap of the virtual camera 1000. For instance, the mapping application of some embodiments starts quickly accelerating the virtual camera 1000 along the arc 1050 for a defined distance or until the virtual camera 1000 reaches a defined speed. Then the mapping application decelerates the virtual camera 1000 for the remaining distance to the position 1060 along the arc 1050. Other ways to implement the bounce or snap effect are used in some embodiments. Rendering a 3D map view using the virtual camera 1000 positioned at the position 1060 along the arc 1050 in the third stage 1015 results in a 3D map view 1040 in which the buildings appear a little smaller and flatter and the roads appear a little smaller compared to the map view 1030.
As described above,
C. Other User Interactions
1. Appearing and Disappearing Controls
The applications of some embodiments, while navigating, have a full screen mode. That is, during the actual providing of directions, the controls that ordinarily take up some of the screen surface are hidden.
Also in stage 1102, the first instruction 1120 is shown along with an end control 1122, trip status area 1124 (including an ETA, a trip duration estimate, and a distance of planned route indicator), an overview button 1126, status bar 1127, and a 3D control 1128. The end button 1122 ends the running of the navigation instructions. The status area 1124 displays information about the planned route. The overview button 1126 displays an overview of the route. The 3D control is an indicator of whether the navigation application is showing a scene in 3D or 2D and a toggle for entering and leaving 3D mode. The selection of the list control 1132 at this stage will cause the mapping application to display the set of navigation instructions in a list format. This stage also shows that the road names are displayed in banners rather than on the roads because the mapping application is operating in the navigation mode.
After a brief amount of time, the end control 1122, the list control 1132, status area 1124, overview button 1126, and 3D control 1128 disappear. In some embodiments, the controls disappear abruptly, while in other embodiments the controls fade away. In some embodiments, the status bar 1127 at the top of the screen also vanishes and navigation box 1120 moves to the top of the screen.
The absence of the controls and movement of navigation box 1120 is shown in stage 1103, in which the navigation map 1121 is seen without the controls except for the raised navigation box 1120. The user can restore the hidden controls by tapping the screen in some embodiments. This is demonstrated in stages 1104 and 1105. In stage 1104, the user taps the screen with finger 1140. In stage 1105, as a result of the tap in the previous stage, the controls are back and the navigation box 1120 has dropped back down to its original position. The restored controls include end control 1122, status area 1124, overview button 1126, status bar 1127, and 3D control 1128. Once the controls are back, the user can make the controls vanish again by tapping, as shown in stage 1105 where a user taps the screen with finger 1150 to restore the navigation application to full screen mode in stage 1106. In addition to the hidden controls, in full-screen in some embodiments the touch interaction with the map is greatly restricted. In some embodiments, more controls exist that are shown in some modes, but hidden in full screen mode (e.g., a list control).
In some embodiments, when the controls are shown and there is an addition to the status bar (e.g., a phone call status bar showing the length of an ongoing call) the navigation box is shortened in order to make more room for the expanded status bar. This is shown in
2. Ending Navigation
In the ordinary course of the running of a set of navigation instructions by a navigation application, as the device reaches each new junction that needs navigation instructions, the instructions for the next such junction appear. This continues until the device reaches its destination. When the destination is reached, the navigation application stops providing instructions and the running of the programmed route ends.
In some embodiments, destinations can be in places not reachable by car, for example, the end pin could be in the middle of a park. In some such embodiments, the driving directions will end, but there will be continued directions for foot travel. In other such embodiments, the application will not give textual directions for travel on foot, but will still maintain a pin on the location (e.g., the middle of a park) when displaying maps in map mode or in locked mode. In some such embodiments, the last instruction after the automotive portion of the journey ends will be a direction “please reach on foot”.
3. Gestures to Look to the Side of the Route During Navigation
As described above, the default behavior for the virtual camera is to follow the location of the device through a virtual world and point down and in the direction the device is moving, or at least to a part of its route a short way ahead of the device's present position. However, it is not always desirable to have the camera pointing straight ahead. Sometimes the user wants the camera to point at an angle instead. Accordingly, the navigation application of some embodiments rotates the virtual camera around when the user drags the map sideways.
In the illustrated embodiment, the application only rotates the buildings while the user is dragging the map to the left (or right), or for a short time after (e.g., with simulated inertia). Once the user stops dragging the map 1514 or holding his finger in place to hold the map 1514 in place, the map 1514 reverts to its default view in the direction of the route the camera is taking. This is shown in stage 1503 in which the user has stopped dragging the map 1514 and the virtual camera is rotating and/or moving back to its original position directly behind the device as it moves on its route. By stage 1504, the map 1514 has resumed its previous orientation. In some embodiments, the virtual camera merely rotates when the map is dragged sideways, rather than moving as well as rotating. While in other embodiments, the camera revolves around the location identifier so that the location identifier appears to be a fixed point while the map revolves around it.
4. Route Overview Mode
In some cases, rather than looking at only a small scale map that shows the next junction, some users may sometimes want to get a look at the big picture. That is, the users may want to look at the entirety of their navigation application's planned route while the user is traveling over the route. Therefore some embodiments provide an overview option that shows the user the entire route.
In stage 1602, the navigation application has displayed an overview map 1620, resume button 1622, location indicator pin 1626, end pin 1628 and position indicator control 1630. The overview map 1620 shows the user his entire planned route starting from the present position. In the illustrated embodiment, the overview map focuses on the remaining route, not the entire route from the beginning, as it does not show a light colored line indicating the previously traveled route. However, in some embodiments, the overview map shows the entire route rather than just the route from the current location of the device. In some embodiments, list control 1617 is also present in the overview map to allow the user to go directly from the overview map to a list of maneuvers (e.g., upcoming turns). The second stage 1602 also shows that the road names are displayed on the road because the mapping application is displaying the overview map (i.e., not in the navigation mode). It is to be noted that the mapping application of some embodiments alternatively or conjunctively uses banners to display the road names regardless of the mode in which the mapping application is operating.
The resume button 1622 switches the navigation application back to the navigation view of stage 1601. The location indicator pin 1626 and the end pin 1628 show the current location of the device and the final destination of the navigation route, respectively. In some embodiments, the application allows a user to move the map around, zoom in and out, and otherwise focus on different parts of the overview map 1620. The position indicator control 1630 in some embodiments centers the map on the location indicator pin 1626.
In some embodiments, the overview mode has a search box that allows a user to enter search queries for items that may be found in the overview map. For example, the user could search for gas stations on the map so that the user can determine where to refuel his car. Another example would be a search for coffee shops so the user could stop for coffee. Some embodiments allow a user to switch from an original end destination to a destination found in a search before resuming navigation.
In some embodiments all overview maps are 2D. In other embodiments, some or all overview maps are in 3D. For example, some embodiments use 2D overview maps for routes that cover large distances, but use 3D overview maps for navigation routes that cover short distances.
In stage 1702, the navigation application has displayed an overview map 1720, resume button 1722, location indicator pin 1726, end pin 1728 and position indicator control 1730. The overview map 1720 shows the user their entire planned route. The resume button 1722 switches the navigation application back to the navigation view of stage 1701. The location indicator pin 1726 and end pin 1728 show the current location of the device and the final destination of the navigation route, respectively. The position indicator control 1730 centers the map on the location indicator pin 1726.
In some embodiments, the 3D overview maps include a search function as described with respect to
D. Multi-Mode Application
1. Rendering Module
The tile retrievers 1805 perform various processes to retrieve map tiles in some embodiments, according to requests for the map tiles from the mesh builders 1815. The mesh builders 1815, as will be described below, identify existing map tiles (that are stored on a mapping service server or in a cache on the device performing the processing pipeline 1800) needed to build their respective meshes. The tile retrievers 1805 receive the requests for the map tiles, determine the best location from which to retrieve the map tiles (e.g., from the mapping service, from a cache on the device) and decompress the map tiles if required.
The mesh builders 1815 (also referred to as tile sources) of some embodiments are instantiated by the tile provider 1820 in order to build different layers of view tiles. Depending on the type of map being displayed by the mapping application, the tile provider 1820 may instantiate a different number and different types of mesh builders 1815. For instance, for a flyover (or satellite) view map, the tile provider 1820 might only instantiate one mesh builder 1815, as the flyover map tiles of some embodiments do not contain multiple layers of data. In fact, in some embodiments, the flyover map tiles contain an already-built mesh generated at the mapping service for which the flyover images (taken by a satellite, airplane, helicopter, etc.) are used as textures. However, in some embodiments, additional mesh builders may be instantiated for generating the labels to overlay on the flyover images when the application is in a hybrid mode. For a 2D or 3D rendered vector map (i.e., a non-satellite image map), some embodiments instantiate separate mesh builders 1815 to build meshes for landcover polygon data (e.g., parks, bodies of water, etc.), roads, place of interest markers, point labels (e.g., labels for parks, etc.), road labels, traffic (if displaying traffic), buildings, raster data (for certain objects at certain zoom levels), as well as other layers of data to incorporate into the map.
The mesh builders 1815 of some embodiments, receive “empty” view tiles from the tile provider 1820 and return “built” view tiles to the tile provider 1820. That is, the tile provider 1820 sends to each of the mesh builders 1815 one or more view tiles (not shown). Each of the view tiles indicates an area of the world for which to draw a mesh. Upon receiving such a view tile, a mesh builder 1815 identifies the map tiles needed from the mapping service, and sends its list to the tile retrievers 1805.
Upon receiving the tiles back from the tile retrievers 1805, the mesh builder uses vector data stored in the tiles to build a polygon mesh for the area described by the view tile. In some embodiments, the mesh builder 1815 uses several different mesh building processors 1810 to build the mesh. These functions may include a mesh generator, a triangulator, a shadow generator, and/or a texture decoder. In some embodiments, these functions (and additional mesh building functions) are available to each mesh builder, with different mesh builders 1815 using different functions. After building its mesh, each mesh builder 1815 returns its view tiles to the tile provider 1820 with its layer of the mesh filled in.
The tile provider 1820 receives from the controller 1875 a particular view (i.e., a volume, or viewing frustrum) that represents the map view to be displayed (i.e., the volume visible from the virtual camera 1830). The tile provider performs any culling (e.g., identifying the surface area to be displayed in the view tile), then sends these view tiles to the mesh builders 1815.
The tile provider 1820 then receives the built view tiles from the mesh builders and, in some embodiments, performs culling on the built mesh using the particular view from the virtual camera 1830 (e.g., removing surface area too far away, removing objects that will be entirely behind other objects, etc.). In some embodiments, the tile provider 1820 receives the built view tiles from the different mesh builders at different times (e.g., due to different processing times to complete more and less complicated meshes, different time elapsed before receiving the necessary map tiles from the tile retrievers 1805, etc.). Once all of the layers of view tiles have been returned, the tile provider 1820 of some embodiments puts the layers together and releases the data to the controller 1875 for rendering.
The virtual camera 1830 generates a volume or surface for the pipeline 1800 to render, and sends this information to the controller 1875. Based on a particular location and orientation from which the map will be rendered (i.e., the point in 3D space from which the user “views” the map), the virtual camera identifies a field of view to actually send to the tile provider 1820. In some embodiments, when the mapping application is rendering the 3D perspective view for navigation, the field of view of the virtual camera is determined according to an algorithm that generates a new virtual camera location and orientation at regular intervals based on the movement of the user device.
The controller 1875 is responsible for managing the tile provider 1820, virtual camera 1830, and map rendering engine 1825 in some embodiments. In some embodiments, multiple tile providers may actually be instantiated, and the controller puts together several view tiles (e.g., map tiles and building tiles) to create a scene that is handed off to the map rendering engine 1825.
The map rendering engine 1825 is responsible for generating a drawing to output to a display device based on the mesh tiles (not shown) sent from the virtual camera. The map rendering engine 1825 of some embodiments has several sub-processes. In some embodiments, each different type of map element is rendered by a different sub-process, with the rendering engine 1825 handling the occlusion of different layers of objects (e.g., placing labels above or behind different buildings, generating roads on top of land cover, etc.). Examples of such rendering processes include a road rendering process, a building rendering process, a label rendering process, a vegetation rendering process, a raster traffic rendering process, a raster road rendering process, a satellite rendering process, a polygon rendering process, a background raster rendering process, etc.
The operation of the rendering pipeline 1800 in some embodiments will now be described. Based on user input to view a particular map region at a particular zoom level, the virtual camera 1830 specifies a location and orientation from which to view the map region, and sends this viewing frustrum, or volume, to the controller 1875. The controller 1875 instantiates one or more tile providers. While one tile provider 1820 is shown in this figure, some embodiments allow the instantiation of multiple tile providers at once. For instance, some embodiments instantiate separate tile providers for building tiles and for map tiles.
The tile provider 1820 performs any culling necessary to generate an empty view tile identifying regions of the map for which a mesh needs to be built, and sends the empty view tile to the mesh builders 1815, which are instantiated for the different layers of the drawn map (e.g., roads, land cover, POI labels, etc.). The mesh builders 1815 use a manifest received from the mapping service that identifies the different tiles available on the mapping service server (i.e., as nodes of a quadtree). The mesh builders 1815 request specific map tiles from the tile retrievers 1805, which return the requested map tiles to the mesh builders 1815.
Once a particular mesh builder 1815 has received its map tiles, it begins using the vector data stored in the map tiles to build the mesh for the view tiles sent from the tile provider 1820. After building the mesh for its map layer, the mesh builder 1815 sends the built view tile back to the tile provider 1820. The tile provider 1820 waits until it has received all of the view tiles from the various mesh builders 1815, then layers these together and sends the completed view tile to the controller 1875. The controller stitches together the returned tiles from all of its tile providers (e.g., a map view tile and a building view tile) and sends this scene to the rendering engine 1825. The map rendering engine 1825 uses the information in the map tiles to draw the scene for display.
2. State Diagram for Different Modes
When a user initially opens the mapping application, the application is in state 1905, the map browsing state. In this state 1905, the application will have generated and displayed a map view. To generate and display this map view, the application of some embodiments identifies a required set of map tiles for a region, requests the map tiles (e.g., from a mapping service server), generates a view of the map tiles from a particular location, orientation, and perspective of a virtual camera, and renders the map view to a device display. When in state 1905, the map view is static. With the application in state 1905, the user can perform numerous operations to modify the map view, search for entities (e.g., places of interest, addresses, etc.), retrieve a route for navigation, etc.
In some embodiments, the integrated application is displayed on a device with an integrated touch-sensitive display. Various gestural interactions over the map may cause the application to perform different modifications to the map view (e.g., panning, rotating, zooming, modifying the map perspective, etc.). When the integrated application receives gestural interactions over the map display (as opposed to touch inputs over various floating or non-floating controls overlaid on the map display), the application transitions to state 1910 to perform gestural input recognition.
The gestural input recognition state 1910 differentiates between different types of gestural input and translates these types of input into different map view modification operations. In some embodiments, the mapping application receives the gestural input as translated by the operating system of the device with the integrated touch-sensitive display. The operating system translates the touch input into gesture types and locations (e.g., a “tap” at coordinates (x,y), a “pinch” operation with separate touch inputs at two different locations, etc.). At state 1910, the integrated mapping application of some embodiments translates these into the different map view modification operations.
When the application receives a first type of gestural input (e.g., two separate touch inputs moving together in a rotational motion over the map view), the application transitions to state 1915 to rotate the map. To rotate the map view, some embodiments modify the location and/or orientation of the virtual camera that determines which portion of the map is rendered to create the map view. When in 3D mode, for example, the mapping application rotates the virtual camera about a particular position (e.g., the center of the touch inputs, the center of the display, a location indicator identifying the user's location, etc.). As the first type of gestural input continues, the mapping application remains in state 1915 to continue rotating the map.
When the user releases the first type of gestural input, the application of some embodiments transitions to state 1930 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform the associated map view modification for a particular amount of time and/or distance. In this case, after the user releases the rotation input, the application transitions to the inertia calculation state 1930 to calculate the additional rotation amount and the time over which this rotation should be performed. In some embodiments, the application slows down the rotation from the (angular) velocity at which the map was being rotated, as if a “frictional” force was applied to the map. As such, the inertia calculation of some embodiments is based on the speed of the first type of gestural input. From state 1930, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 1915 (the rotation state) to the inertia calculation state 1930, it then transitions back to state 1915 after performing the inertia calculation. After the rotation of the map is complete, the application transitions back to state 1905.
When the application receives a second type of gestural input (e.g., a single touch input moving over the map view), the application transitions to state 1920 to pan the map. To pan the map view, some embodiments modify the location of the virtual camera that determines which portion of the map is rendered to create the map view. This causes the map to appear to slide in a direction derived from the direction of the second type of gestural input. In some embodiments, when the map view is in a 3D perspective mode, the panning process involves performing a correlation of the location of the touch input to a location on the flat map, in order to avoid sudden unwanted jumps in the map view. As the second type of gestural input continues, the mapping application remains in state 1920 to continue panning the map.
When the user releases the second type of gestural input, the application of some embodiments transitions to state 1930 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform the associated map view modification for a particular amount of time and/or distance. In this case, after the user releases the panning input, the application transitions to the inertia calculation state 1930 to calculate the additional amount to move the map view (i.e., move the virtual camera) and the time over which this movement should be performed. In some embodiments, the application slows down the panning movement from the velocity at which the map was being panned, as if a “frictional” force was applied to the map. As such, the inertia calculation of some embodiments is based on the speed of the second type of gestural input. From state 1930, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 1920 (the panning state) to the inertia calculation state 1930, it then transitions back to state 1920 after performing the inertia calculation. After the panning of the map is complete, the application transitions back to state 1905.
When the application receives a third type of gestural input (e.g., two separate touch inputs moving closer together or farther apart), the application transitions to state 1925 to zoom in on or out of the map. To change the zoom level of the map view, some embodiments modify the location (i.e., height) of the virtual camera that determines which portion of the map is rendered to create the map view. This causes the map view to include more (if zooming out) or less (if zooming in) of the map. In some embodiments, as the user zooms in or out, the application retrieves different map tiles (for different zoom levels) to generate and render the new map view. As the third type of gestural input continues, the mapping application remains in state 1925 to continue zooming in on or out of the map.
When the user releases the second type of gestural input, the application of some embodiments transitions to state 1930 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform the associated map view modification for a particular amount of time and/or distance (i.e., moving the virtual camera higher or lower). In this case, after the user releases the zoom input, the application transitions to the inertia calculation state 1930 to calculate the additional amount to zoom the map view (i.e., move the virtual camera) and the time over which this movement should be performed. In some embodiments, the application slows down the zooming movement from the velocity at which the map was being zoomed in on or out of (i.e., the speed at which the virtual camera changes height), as if a “frictional” force was applied to the camera. As such, the inertia calculation of some embodiments is based on the speed of the third type of gestural input. From state 1930, the application transitions back to the map modification state that the application was previously in. That is, when the application transitions from state 1925 (the zooming state) to the inertia calculation state 1930, it then transitions back to state 1925 after performing the inertia calculation. After the zooming of the map is complete, the application transitions back to state 1905.
For simplicity, the state diagram 1900 illustrates the map panning, zooming, and rotation processes using the same inertia calculation process (state 1930). However, in some embodiments, each of these different map modification processes actually uses a different inertia calculation to identify the slow-down and stop for its particular type of movement. In addition, some embodiments calculate and modify the inertia variables as the input is received rather than when the user removes the gestural input.
When the application receives a fourth type of gestural input (e.g., two separate touch inputs moving up or down the touch-sensitive display in unison), the application transitions to state 1935 to modify the perspective view of the map. To change the perspective view of the map, some embodiments move the virtual camera along an arc over the map, modifying both the location and orientation of the virtual camera (as the camera keeps the center of its field of view at a particular location on the map). In some embodiments, different zoom levels use different arcs along which the virtual camera moves. Each of these arcs has a top point at which the virtual camera is pointing straight down, giving a 2D perspective view of the map. In addition, each arc has a bottom point, that is the lowest point on the arc to which the virtual camera can be moved. Thus, the fourth type of gestural input can cause the application to change between a 2D map view and a 3D perspective map view in some embodiments. As the fourth type of gestural input continues, the mapping application remains in state 1935 to continue modifying the perspective view of the map.
When the user releases the fourth type of gestural input, the application of some embodiments transitions to state 1940 to perform an inertia calculation. In some embodiments, after the user releases certain types of touch inputs, the application continues to perform the associated map view modification for a particular amount of time and/or distance (i.e., moving the virtual camera higher or lower). In this case, after the user releases the perspective view change input, the application transitions to the inertia calculation state 1940 to calculate the additional amount to modify the perspective of the map view (i.e., move the virtual camera along its arc) and the time over which this movement should be performed. In some embodiments, the application slows down the movement from the velocity at which the map was changing perspective (i.e., the speed at which the virtual camera moves along its arc), as if a “frictional” force was applied to the camera. As such, the inertia calculation of some embodiments is based on the speed with which the fourth type of gestural input was performed.
In addition, for the perspective change operation, some embodiments transition to a rebound calculation state 1945. As stated, the perspective change operation has a maximum and minimum perspective shift allowed in some embodiments, which may depend on the zoom level of the current map view. Thus, in addition to an inertia calculation, the application performs a rebound calculation at state 1945. The rebound calculation uses the inertia calculation to determine whether the maximum point along the virtual camera arc will be reached and, if so, the velocity of the virtual camera at this point. Some embodiments allow the virtual camera to move slightly past the maximum point to hit a “rebound” point, at which point the application turns the virtual camera around on its arc, moving it back towards the maximum point. Some embodiments include such a bounce-back functionality only on one end of the virtual camera arc (e.g., the bottom of the arc), while other embodiments include the functionality on both ends of the arc. From the rebound calculation state 1945, the application transitions back to the inertia calculation state 1940, then back to the perspective changing state 1935 to display the map view movement. In addition, when the user performs the fourth type of touch input for long enough and the perspective reaches its maximum point, the application transitions directly from the state 1935 to state 1945 to calculate the rebound information and then transitions back to state 1935. After the modification to the perspective view of the map is complete, the application transitions back to state 1905.
The above states relate to the various multi-touch gestures over the map presentation that the integrated mapping, search, and navigation application translates into different modifications to the map presentation. Various other touch inputs can also cause the application to change states and perform various functions. For instance, some embodiments overlay a 3D selectable item on the map view (e.g., as a floating control), and selecting (e.g., with a tap input) the 3D item causes the application to transition to 1935 to modify the perspective of the map view. When the map view starts in a 3D perspective view, the application modifies the perspective into a 2D view; when the map view starts in the 2D view, the application modifies the perspective into a 3D view. After the modification, the application returns to state 1905.
When a user is viewing a map in state 1905, the application presents various labels as part of the map view. Some of these labels indicate places of interest, or other locations. When a user selects certain labels (e.g., for certain businesses, parks, etc.), the application transitions to state 1950 to display a banner for the selected location (e.g., an information display banner), then returns to the map browsing state (with the banner displayed over the map). In some embodiments, this banner includes (1) a quick-route navigation UI control (e.g., a button) that causes the application to retrieve a route (e.g., a driving route) from a current location of the device to the selected location without leaving the map view and (2) an information UI control (e.g., button) that causes the application to provide additional information about the location.
When a user selects the UI control button, the application transitions from state 1905 to state 1955 to display a staging area for the selected location. In some embodiments, this staging area displays a media presentation of the selected location (e.g., a 3D video presentation, a flyover view of the selected location, a series of images captured for the location, etc.), as well as various information for the selected location (contact information, reviews, etc.). The application stays in the state 1955 as the user performs various operations to navigate the staging area and view information within the staging area. When a user selects a UI control to transfer back to the map view, the application transitions to state 1905.
From the map browsing view, the user can also easily access the search function of the application. When a particular UI control (e.g., a search bar) is selected, the application transitions to a search entry suggestion state 1960. At the search entry state, some embodiments display a touchscreen keyboard with which the user can enter a search term. The search term may be a business name, an address, a type of location (e.g., coffee shops), etc. While the user enters characters, the application remains in state 1960 and provides suggestions based on recent searches, the letters already entered, etc. Some embodiments may use prefix-based suggestions (e.g., suggestions starting with the characters already entered) as well as other suggestions (e.g., making spelling corrections to add characters at the beginning of the already-entered string, transpose characters, etc.). In some embodiments, the selections may also include recently entered routes in addition to locations. If the user selects a cancellation UI control at this stage, the application transfers back to state 1905 without performing a search.
When the user selects a search term (either a suggested term or a term entered completely by the user), the application transitions to state 1965 to display the search results over the map view, then transitions to state 1905 with the search results displayed. Some embodiments display the search results as selectable items (e.g., pins) on the map; selection of one of the items causes a transition to state 1950 to display the banner for the selected item. In addition, the application of some embodiments automatically selects one of the search results (e.g., a “best” result) and displays this banner as part of the state 1965.
As the application is a tightly integrated mapping, search, routing, and navigation application, the user can easily access the routing function from the map browsing state. When a particular UI control (e.g., a route entry button) is selected, the application transitions to the route entry state 1970. At the route entry state, some embodiments display a touchscreen keyboard with which the user can enter locations (e.g., addresses, place names, place types, etc.) into both “to” and “from” fields in order to request a route. While the user enters characters, the application remains in state 1970 and provides suggestions based on recent routes, recent searches, an autocomplete similar to that described for the search entry, etc. If the user selects a cancellation UI control at this stage, the application transfers back to state 1905 without retrieving a route.
When the user selects a route (e.g., by entering a “to” location and a “from” location), the application transitions to the route displaying state 1975. At this state, the application displays one or more routes from a first selected location to a second selected location over the map view (e.g., by overlaying route lines on the map view). Some embodiments automatically select a first one of the routes. The user can select any of the other routes (e.g., by tapping over an unselected route), with the application remaining in state 1975 (but modifying the display of the route lines to indicate the selection of the other route). In addition, when in state 1975, the application of some embodiments displays different UI controls related to routing and navigation, including a direction list control, a navigation start control, and others.
Also, various gestural interactions over the map on which the routes are displayed may cause the application to perform different modifications to the map view (e.g., panning, rotating, zooming, modifying the map perspective, etc.). When the integrated application receives gestural interaction over the map display while in the route display state 1975, the application transitions to state 1910 to perform gestural input recognition, with all of the gestural map modification operations (e.g., corollaries to states 1915-1945) available. That is, the application translates the gestural input into panning, rotation, zoom, and/or perspective change operations similar to those described above for states 1915-1945, with similar inertia and rebound features for the virtual camera movement. Whereas the operations 1915-1945 return to the map browsing state 1905, the corollary operations accessed from the route display state 1975 return to the route display state 1975.
In some embodiments, the route display state 1975 is accessible from other states as well. For instance, if a user selects the quick-route UI control on a banner while in state 1905, the application retrieves one or more routes from the current location of the device to the location with which the banner is associated. In addition, some embodiments display previously requested routes among the search suggestions at state 1960. When the user selects one of these suggested routes, the application transitions directly from state 1960 to state 1975 to display one or more routes over the map.
From the route display state 1975, the application can transition into various different modes depending on different controls selected by the user. When the user selects a UI control to clear the routes, the application transitions back to state 1905 to display the map without any routes. In addition, the integrated application may enter one or more navigation modalities from the route displaying state 1975.
When the selected route displayed at state 1975 starts at the current location of the device and the user selects a navigation starting control, the application transitions to the navigation state 1980. In some embodiments, the application displays a cinematic transition from the map view into a more immersive 3D view for navigation. Within the navigation state 1980 of some embodiments, a virtual camera follows the location of the user along the selected route in order to present the upcoming portions of the route. When either the route is completed (the device reaches the destination location) or the user selects a control to end navigation, the application transitions to state 1905 to present the map browsing view 1905.
In some embodiments, various gestural interactions over the map on which the routes are displayed may cause the application to perform different modifications to the map view (e.g., panning, rotating, zooming, modifying the map perspective, etc.) while in the navigation mode 1980. In some embodiments, only some of the described map modification operations are available in the navigation mode. For instance, some embodiments allow the user to zoom in or out, but do not allow any other modifications to the map. Thus, when the user provides gestural input, the gestural input recognition state 1910 filters out types of gestural input not associated with the zoom operation (and subsequently the application returns to state 1980). When the type of gestural input associated with the zoom operation is received, the gestural input recognition state recognizes this input and the application transitions to a state similar to state 1925, for changing the zoom level of the map (with the inertia calculation, in some embodiments).
Other embodiments may enable different map modification operations. For instance, in some embodiments all of the gestural map modification operations (e.g., corollaries to states 1915-1945) are available while in the navigation mode. Some embodiments allow a subset of the gestural map modification operations, such as zooming and a limited panning operation. The panning operation of some embodiments, upon receiving the type of gestural input associated with panning, moves the virtual camera (while in the navigation mode) to the side, then returns the virtual camera back to pointing along the route. Whereas the operations 1915-1945 return to the map browsing state 1905, the corollary operations accessed from the navigation state 1980 return to the navigation state 1980.
When the selected route displayed at state 1975 starts at a location other than the current location of the device (or the route is a walking route) and the user selects a navigation starting control, the application transitions to the stepping mode, or route inspection mode, at state 1985. In some embodiments, the application displays the maneuvers performed along the route one at a time (e.g., as navigation signs). By providing gestural input (e.g., swipe gestures) to the maneuvers, the user can view the different maneuvers while in the route inspection mode. The maneuvers are overlaid on a map and at least a portion of the route is displayed in the map.
As in the route display mode, various gestural interactions over the map may cause the application to perform different modifications to the map view (e.g., panning, rotating, zooming, modifying the map perspective, etc.). When the integrated application receives gestural interaction over the map display while in the stepping mode 1985, the application transitions to state 1910 to perform gestural input recognition, with all of the gestural map modification operations (e.g., corollaries to states 1915-1945) available. That is, the application translates the gestural input into panning, rotation, zoom, and/or perspective change operations similar to those described above for states 1915-1945, with similar inertia and rebound features for the virtual camera movement. Whereas the operations 1915-1945 return to the map browsing state 1905, the corollary operations accessed from the stepping mode 1985 return to the stepping mode 1985.
Furthermore, in some embodiments the gestural input recognition recognizes at least one type of gestural input over the displayed maneuvers in order to switch between the maneuvers. When a particular type of gestural input (e.g., a swipe gesture) is received over the displayed maneuver (as opposed to over the map view), the application transitions to a state (not shown) for changing the displayed maneuver, then returns to state 1985.
When the integrated application receives gestural interaction over the map displayed while in the stepping state 1985, the application transitions to state 1910 to perform gestural input recognition, with all of the gestural map modification operations (e.g., corollaries to states 1915-1945) available. When the modification operations are done, the application returns to state 1985. When the user selects a control to end stepping through the maneuvers, the application transitions to state 1905 to present the map browsing view.
In addition, in some embodiments the application can transition from the stepping mode 1985 to an auto-stepping state 1990. When the user selects a location tracking control while the application is in state 1985, the application transitions to an automatic stepping mode 1990, which is a different navigation modality. When in the automatic stepping mode of some embodiments, the integrated mapping, search, and navigation application displays the maneuver to which the device's location is closest (e.g., as measured by a juncture at which the maneuver is performed). When the device moves (e.g., along the route) to a location closer to a different maneuver, the auto-stepping mode automatically displays the different maneuver. When the user deselects the location tracking control, the application transitions back to the stepping mode 1985. When the user selects a control to end navigation while in the auto-stepping state 1990, the application transitions to state 1905 to present the map browsing view.
As in the stepping mode 1985, various gestural interactions over the map may cause the application to perform different modifications to the map view (e.g., panning, rotating, zooming, modifying the map perspective, etc.). When the integrated application receives gestural interaction over the map display while in the auto-stepping mode 1990, the application transitions to state 1910 to perform gestural input recognition, with all of the gestural map modification operations (e.g., corollaries to states 1915-1945) available. That is, the application translates the gestural input into panning, rotation, zoom, and/or perspective change operations similar to those described above for states 1915-1945, with similar inertia and rebound features for the virtual camera movement. Whereas the operations 1915-1945 return to the map browsing state 1905, the corollary operations accessed from the auto-stepping mode 1990 return to the auto-stepping mode 1990. In addition, some embodiments automatically turn the location tracking control off when the user pans the map a particular distance, in which case the application returns to the stepping mode state 1985 rather than auto-stepping state 1990.
II. Display of Navigation Signs
The above sections introduce the turn-by-turn navigation features of some embodiments. One such feature is the navigation signs provided by the mapping application describing the different maneuvers for the user to perform. These signs may indicate turns, a distance over which to continue traveling straight, when to take a freeway off-ramp, or other maneuvers for the user to perform. Some embodiments provide various animations for the signs, including showing the signs as passing over the user location indicator in 3D mode, modifying the appearance of a sign to indicate an upcoming maneuver, and using secondary signs when two maneuvers will be performed in rapid succession.
A. Realistic Look and Different Formats in Different Contexts
The navigation signs, in some embodiments, may have different appearances in different contexts. Some of these differences are described in greater detail further below. Specifically, graphical indicators of maneuvers to perform (e.g., direction indicators that are described further below) and instruction text describing those maneuvers may be adapted to fit the context of the navigation signs being displayed. For example, different-sized signs may have either simple or complex maneuver descriptions, and instruction text may be adapted to the size of the sign and may be based on other information displayed within the sign.
Some embodiments display the navigation signs in such a way as to give the signs the appearance of a realistic road sign. Some embodiments display the navigation signs as rich, textured images (e.g., using shadows, shading, etc.) as opposed to simply displaying a flat image on the map display. In addition, some embodiments use shading for the navigation sign that matches the color(s) of road signs in the area through which the application is navigating. The application also uses realistic highway shields to mark roads in some embodiments. For instance, for numbered state and federal highways, the application will either use the highway shield associated with the road within the navigation sign (e.g., off to the side of the sign), replace the name of the road in navigation instructions with the highway shield, or otherwise include the highway shield in the graphical display. Generation and use of these road signs are further described in U.S. patent application Ser. No. 13/632,121, now published as U.S. Patent Publication number 2013/0322634, entitled “Context Aware Voice Guidance.” U.S. patent application Ser. No. 13/632,121 is incorporated herein by reference.
The second example 2010 illustrates the highway shield displayed on the right side of the navigation sign rather than inline in the text instruction. This scenario illustrates an alternative display used by some embodiments for the same instruction as in example 2005. The highway shield in this case is displayed as the same size as the graphical indicator arrow on the left side of the navigation sign. In addition, because the information is presented in the road sign, the application removes the “on 101 North” portion of the text that would otherwise be present.
The third example 2015 illustrates the case in which the navigation sign is shaded to match the type of road shown in the highway shield. In this scenario, the instruction tells the user to go straight on CA-1 North. The “CA-1” is replaced with the highway shield sign for CA-1. While some embodiments shade this sign using green (the color of signs used for California state highways), other embodiments shade the navigation sign using the color of the road shield signs found along the actual highway. Other embodiments use green to match the color of road instruction signs found above freeways in the region in which the device is located (e.g., green for California).
The fourth scenario 2020 illustrates a merge maneuver onto Interstate-5 within the navigation sign. Much like the first example 2005, this illustrates the road shield sign as inline text. Furthermore, shading is used within the road shield in order to match the look of the actual interstate signs, with the top portion shaded red and the bottom portion shaded blue. As mentioned, some embodiments instead shade the entire navigation sign using a combination of these colors.
Although
1. Different Direction Indicators in Different Contexts
For a currently displayed navigation instruction sign, in the context of full-screen turn-by-turn navigation, the mapping application of some embodiments abstracts a maneuver down to two elements: a prominent stylized arrow roughly representing the path of the vehicle through the juncture, and a de-emphasized set of lines and curves corresponding to other elements of the juncture. For instance, a right turn at a T-junction is represented by a large arrow with a right-angle joined with a smaller, dimmer segment that runs parallel to one of the large arrow's segments. The smaller segment will also be pushed off to the side so that the path taken by the vehicle through the juncture dominates the display. Such a representation of a maneuver which includes an arrow with junction context provides fairly complete information about the maneuver while remaining abstract and easily understandable.
An alternate representation of a maneuver may omit the juncture context entirely and simplify the primary arrow indicating the maneuver. When a user looks at maneuvers beyond the current maneuver (the next maneuver to make), the more detailed graphical representation may provide more information than is required and be harder to read with a quick glance. For example, even if there is space to display the junction context for a secondary instruction that follows the current maneuver, some embodiments display only the simplified arrow for clarity. This adaptive approach also benefits space-constrained UI elements. While multitasking or looking at lists of instructions, for example, the mapping application of some embodiments draws the simpler maneuver abstraction in order to produce something more easily discernible in a smaller area.
The second scenario 2110 illustrates turn-by-turn navigation when the user device on which the mapping application operates is locked. As described in detail below, the application is able to display turn-by-turn navigation instructions even when the device is locked, in order to continue providing instructions to the user. In this scenario, as shown, a simplified arrow is also displayed in some embodiments. This provides a simple graphical indication of the turn within the lock screen (in this case, a right turn), without providing the context data that might be difficult for a user to pick out in the lock screen.
The third scenario 2115 also illustrates turn-by-turn navigation when the mapping application is not open (or not presently displayed) on the device on which the application operates. As described in detail above, the application displays turn-by-turn navigation instructions within the notification banner space when the mapping application is not displayed. Much like in the lock-screen mode, the mapping application uses a simple graphical indicator for the indicated maneuver (in this case a left turn). Due to space constraints and the reasons described above for the lock-screen mode, the simple graphical indicator is used.
The previous three scenarios illustrate situations in which the simple graphical indicators are used. One of ordinary skill in the art will recognize that in some embodiments, the more complex stylized juncture plus maneuver graphical indicators might be used in the above situations. The following three scenarios illustrate indications in which these more complex indicators are used.
The fourth scenario 2120 illustrates route overview directions, in which the user can view an entire route from a starting location to ending location. The user can swipe through the different instructions (e.g., using swipe gestures) to view the route segments between maneuvers. Here, the complex juncture indication is used, showing the intersection context (a T intersection) and the maneuver made through the intersection, with the maneuver arrow emphasized over the intersection context.
The fifth scenario 2125 illustrates navigation instructions in the context of the standard turn-by-turn navigation (i.e., not in the lock-screen mode, or with a different application open, etc.). In this case, the more complex arrow graphical indicator is used. In the illustrated example, the road juncture is slightly more complicated than the previous example, with a fourth branch angling up and to the right from the direction of approach. The sixth scenario 2130 also illustrates navigation instructions during turn-by-turn navigation. In this case, the maneuver being performed is a U-turn. Representing a U-turn with the juncture branches as in scenario 2125 would result in the arrow pointing up and down the same branch (the bottom branch). As a result, the application instead displays a stored U-turn indicator arrow.
2. Different Navigation Instructions in Different Contexts
The mapping application of some embodiments displays textual route instructions in a large variety of cases, some of which are more space constrained than others, and some in which other guidance elements provide information about a maneuver that can take the place of the text instructions. Rather than selecting a single instruction string and then shrinking the font or truncating as dictated by the constraints, the application uses a sophisticated method to synthesize strings that are best adapted to each context from a number of details about the maneuver itself.
For a given context, the application chooses instruction text by considering factors such as the available space, the amount of information conveyed by means other than text (e.g., the graphical indicators, road signs, etc.), the localized length of each of the instruction variants, among other factors. By synthesizing and evaluating several alternatives locally on the client device (as opposed to simply receiving instruction text from the mapping service), the mapping application can pick an optimal instruction string in every scenario. In addition, this approach allows for the application to use different instruction text on a differently-sized device (e.g., using more text on a tablet computer as compared to a smaller smart phone). A similar approach can also be used for spoken instructions that need to fit within a particular amount of time, and when voice instructions are used, the application of some embodiments will reduce the length of the displayed instructions.
In some embodiments, the “At” field is based on map information that includes traffic light and stop sign information, etc. For the examples shown in
The “Onto” field indicates the pathway (i.e., street, freeway, etc.) onto which the maneuver exits the juncture. In the case of the first juncture in
Next, after generating each of the component strings for a set of instructions, the mapping application of some embodiments generates different levels of instructions. The table 2300 illustrates a set of synthesized instructions for the first juncture. Specifically, the table 2300 illustrates five sets of instructions, of varying lengths, for a particular juncture. However, one of ordinary skill in the art will recognize that different embodiments might include fewer, additional, or different synthesized strings based on the set of string fields.
The first instruction set uses all five of the fields. This is the longest instruction set, reading “At the end of the road, turn right onto 1st St., towards B. St. for 0.1 miles”. As it is the longest instruction set, the application assigns the instruction set a rank of 1. The second instruction set removes the “For” field, using only the “At”, “Turn”, “Onto”, and “Towards” fields. The third instruction set removes the “At” field. These fields add context, and are therefore nice to have when additional room is available. However, they are less integral to the maneuver itself, and therefore are the first fields to remove when shortening the instruction text. Next, for the fourth instruction set, the application removes the “Towards” field, as the “Turn” and “Onto” fields are considered more important. Lastly, the fifth instruction set contains only the “Turn” field, simply stating “Turn right”.
Again, some embodiments will include additional instruction sets, when different length instructions (that still make sense) are available. For instance, some embodiments will include an instruction set that removes the “At” field but keeps the “For” field, in the case that the “For” field is shorter than the “At” field. This enables the application to have another option in case the second instruction set (with the “For” field removed) is just slightly too long for the allocated space. Furthermore, some embodiments may include additional, fewer, or different fields. For instance, some embodiments might include a “In” field, that gives the distance to the upcoming juncture (i.e., “In 0.5 miles, . . . ”).
The first scenario 2405 illustrates instructions for the particular maneuver displayed during turn-by-turn navigation. In this case, the application allots three text lines for the instruction. The distance (0.5 miles) is already displayed in large font at the top of the navigation sign, but this is not counted as one of the text lines. With three lines available, the highest ranked instruction set can be used in the navigation sign.
The second scenario 2410 illustrates turn-by-turn navigation instructions for the particular maneuver while in lock screen mode. In this mode, only two lines of large text are allotted in some embodiments, so the highest ranked instructions that fit use only the “Turn” and “Onto” fields. This simplifies into the direction of the turn and the street onto which the user turns. The third scenario 2415 illustrates navigation instructions for the maneuver while the mapping application is not open on the device, in which case the instructions show up as an alert banner. In this case, the application only allots one line to the instructions, so the lowest ranked instructions (“Turn right”) are used.
The fourth scenario 2420 illustrates the display of information in the list view for route directions. This view, as described above, lists subsequent instructions for each of the maneuvers along a route. In some embodiments, the banners in the list view for each direction are of a variable height, and therefore the full instruction set is always used. Thus, the highest ranked set of instructions, “At the end of the road, turn right onto 1st St. towards B. St.” is used for the first maneuver in the list. As shown, this maneuver takes an extra line of text as compared to the next two maneuvers.
The fifth scenario 2425 illustrates turn-by-turn navigation in 3D mode. As compared to the first scenario 2405, some embodiments allot less room in the navigation sign for the instruction set when in 3D mode, in order for more of the 3D display to be viewable. As such, the application uses the third ranked instruction set, because this is the largest instruction that fits in the two lines using the given text size.
The seventh scenario 2510 is the same as the first scenario 2405, but explicitly indicates that the spoken navigation is turned off. This is provided here to contrast with the eighth scenario 2515, in which voice instructions are enabled during turn-by-turn navigation. For voice navigation, the application determines a maximum amount of time allowed for speaking the instructions, then determines the highest ranked set of instructions that can be spoken within this allotted time. In this case, the time allows the entirety of the highest ranked instruction set to be selected. In addition, when voice navigation is activated, the application reduces the size of the displayed navigation sign. As such, the application displays the third ranked instruction set within the display.
Finally, the mapping application of some embodiments may operate on different types of devices with different size display screens. For example, the application might operate on both smart phones and larger tablet computers. When operating on a larger device, some embodiments allow more room for the navigation sign. The ninth scenario 2520 illustrates turn-by-turn 3D navigation on a larger device (a tablet computer). Unlike in the fifth scenario 2425, the navigation sign provides enough room for the highest ranked instruction set to be used.
The above description describes some embodiments that generate several different instruction sets for a maneuver, rank the instruction sets, and then adaptively determine which of these instruction sets best fits into a particular space. In some embodiments, the application identifies a maximum number of characters available to use for the instruction display. The application then starts with the highest ranked instruction set and determines whether the instruction set fits into the identified number of characters. When the instruction set fits, the application selects and displays the instruction set. When the instruction set does not fit, the application moves to the next ranked instruction set and performs the same test. If none of the instruction sets fit, then the application uses the one that comes closest to fitting. Some embodiments then truncate the instruction set with an ellipsis to indicate that the instruction set does not completely fit within the space. This may result in elements being removed from the string.
In addition to text, some embodiments use text substitutes within the instruction sets. Specifically, for roads represented by shield signs (e.g., interstate freeways, state routes), the application uses the shield representation of the road rather than the road name (e.g., a blue and red shield with “I-5” inside of it instead of “Golden State Freeway” or “Interstate 5”. Some embodiments treat these signs as a fixed number of characters when assessing the different instruction sets.
The above description describes some embodiments of the mapping application in which the decision regarding which elements to use is performed primarily based on trying to use the maximum length instruction set. Some other embodiments factor in whether certain elements of an instruction set are presented to the user in a different visual manner, and may potentially remove these elements.
For instance, when displaying a detailed instructional arrow that makes clear a turn is a slight right turn, some embodiments shorten the instruction to remove the “slight” or even remove the entire reference to the turn, instead using instructions along the line of “CA-17 S towards Santa Cruz”. Similarly, if displaying a large road shield sign, then the “CA-17 S” portion of the instruction might be omitted.
B. Dynamic and Animated Presentation of Signs
The above-described situations of
1. Animated Removal and Presentation of Navigation Sign
The first stage 2605 illustrates a navigation sign 2625 indicating a maneuver of merging onto Main St. for the user to perform in 100 ft. The second stage 2610 illustrates the animation to remove the navigation sign 2625 as the user performs the maneuver. As the user physically merges onto Main St., the navigation sign 2625 enlarges and begins disappearing from the field of view, as would a road sign above a freeway. In some embodiments, the mapping application also applies a perspective tilt to the sign, to further mimic the appearance of the sign passing overhead.
At the third stage 2615, the subsequent navigation sign 2630 begins to appear from the horizon, or a closer approximation of the horizon. Some embodiments do not actually render the map all the way out to the horizon in 3D mode, and start animating the upcoming navigation sign from the distance at which the 3D rendering ends. This animation is meant to resemble the approach towards a road sign on the freeway, though often at a faster speed (in order to quickly bring the navigation sign to full size, and avoid the distraction of a lengthy animation). The fourth stage 2620 illustrates the resultant display, with the subsequent navigation sign 2630 displayed at the top of the screen in the normal position.
In addition to the animations shown in
2. Occasional Emphasis
In some cases, the mapping application may display a navigation sign well before the maneuver described by the navigation sign will be performed. For instance, if a user enters a freeway, and the next maneuver involves a freeway exit in 15 miles, the application may display a navigation sign indicating the upcoming freeway exit well before the user needs to begin preparing to actually exit the freeway. When it comes time to alert the user that the juncture at which to perform the maneuver is approaching, different embodiments use different techniques. Some embodiments include audio alerts, with the user device providing voice navigation to indicate that the juncture is approaching.
Some embodiments, either in conjunction with the audio alert or whenever the audio alert is turned off, provide a visual indication that the maneuver is upcoming through the display of the sign. For instance, in some embodiments the application modifies the color of the sign (e.g., from green to white or green to yellow) along with the color of the graphical indicator arrow (e.g., from white to black). Other embodiments display a less obtrusive shimmer over the navigation sign, intended to catch the user's attention without being overly obtrusive.
At the second stage 2710, the right turn is now only 500 ft. away. The application has judged that this is the appropriate distance at which to alert the user to the upcoming maneuver, and therefore has begun displaying a shimmer across the navigation sign 2725. The third and fourth stages 2715 and 2720 illustrate the continuation of this animation. In some embodiments, the animation resembles a light being moved across the sign from left to right. Other embodiments display a similar animation from right to left, or other such animations (e.g., a light radiating out from the center of the sign, etc.).
Some embodiments vary the distance from the maneuver at which the animation begins based on various factors, such as the speed at which the device is moving (based on location tracking information) and the speed limit of the road on which the user is currently traveling. For example, some embodiments have a set time before the intersection that the animation should be displayed, and use this speed information to calculate the appropriate distance. Some embodiments also vary the distance based on the type of maneuver being made (e.g., allowing more time for exiting a freeway than for making a right turn off of a one-lane road).
3. Secondary Signs
When a route requires two distinct maneuvers in rapid succession, some embodiments display the navigation sign for the second maneuver as stacked underneath the navigation sign for the first maneuver. This alerts the user to the impending nature of the second maneuver. When several maneuvers will be performed in succession, some embodiments stack more than two navigation signs on top of each other.
The second stage 2810 illustrates that the user has now traveled 900 feet, so that there are only 100 ft. from the left turn maneuver. Other than the updates to the distance in the navigation sign 2825 (and the movement of the 3D map), the display has not yet changed. The third stage 2815 illustrates the display immediately after the left turn maneuver has been performed onto East St. As shown, the second navigation sign 2830 is now a full-sized navigation sign with a complex graphical indicator arrow and additional textual information (a distance of 50 feet and text instructions to turn right). Some embodiments animate the transition from the smaller sign to the full-size sign, while other embodiments simply replace one with the other.
The fourth stage 2820 illustrates the display after the user has made the second maneuver (the right turn onto South St.). The application now displays a navigation sign 2835 for the next maneuver, a left turn onto West St. Because this maneuver is 2.8 miles away, the application did not stack sign 2835 under sign 2830. Because the navigation is in 3D mode, some embodiments do display the animation described above by reference to
In the above example, the application stacks signs for maneuvers that occur 50 feet apart, but does not stack signs for maneuvers that occur several maneuvers apart. The threshold distance for when to consider two maneuvers subsequent may depend on a variety of factors. Some embodiments store a set distance that is not variable. Other embodiments look at the type of roads involved in the maneuver (e.g., based on a functional road class variable that describes the road in back-end map data) or the speed limits, assume a likely speed for the user after the maneuver, and set the threshold distance based on this data (i.e., based on a threshold time between maneuvers, such as 30 seconds).
III. Navigation Instructions when not in Navigation Application
A. Instructions when Device is Unlocked and Navigation is Operating in Background
Some embodiments allow the navigation application to run in the background while other applications are running in the foreground. These embodiments provide unobtrusive navigation instructions in the foreground even while the main navigation application is running in the background and another application or an application launcher is running in the foreground. Examples of applications running in the foreground include voice-activated personal assistant, mail, browser, phone, calendar, or any other application available on the device.
The navigation application of some embodiments provides a navigation bar (sometimes called a “banner” or “navigation banner”) as well as a regular status bar on the screen. Some embodiments provide a navigation status bar when no navigation instructions are being provided and provide a navigation instruction bar when navigation instructions are being given.
In stage 2901, the display 2900 shows navigation application 2905, a status bar 2980, and a button 2915. The status bar 2980 shows different information such as battery level, time, reception bars, etc. In some embodiments, the status bar displays an indicator such as an arrow, which indicates that the navigation application or a map application is running. In this stage 2901, the navigation application 2905 is running in the foreground until the device receives a selection (e.g., a click) on button 2915 that switches from the navigation application to the application launch view, which can itself be characterized as an application launching application. In some embodiments, there are other controls instead of or in addition to the button that switch the navigation application to another application (e.g., the application launch view or other applications). The stage 2901 also shows that the road names are displayed on road signs and not in banners. As mentioned above, the mapping application of some embodiments may display the road names on the road and/or in the banners regardless of the mode in which the mapping application operates.
In stage 2902 application launcher 2975 is displayed in the foreground. The foreground application launcher 2975 has icons 2925 that have their normal functions (e.g., launching other applications) while the navigation application runs in the background. In stage 2902 a background navigation status bar 2910 is shown below the status bar 2980. Some embodiments display the status bar 2980 and/or the navigation status bar 2910 in a different color (e.g., green) when navigation is running in background (as shown in stage 2902) than the status bar color (e.g., gray) when navigation is not running in background (as shown in stage 2901). In other embodiments, the status bar 2980 is the same color when the navigation application is running in the background, the navigation application is off, or the navigation application is running in the foreground. In some embodiments, the thickness of the navigation status bar is the same or approximately the same (e.g., 75% to 125% of the thickness) as the thickness of the status bar when the navigation application is not currently displaying a direction in a navigation instruction bar.
The navigation status bar 2910 in some embodiments is both an indicator that the navigation application is running in the background and a control for bringing the navigation application to the foreground. The navigation status bar 2910 in some embodiments is not limited to being displayed only with the application launching screen 2975, but rather is displayed below the status bar 2980 at the top of any application that is running in the foreground.
In stage 2903, the navigation status bar 2910 is selected by touching the navigation status bar 2910 on the screen. Some embodiments also allow the selection of the navigation bar by other touch-based or motion-based input devices as well as non-touch based or motion-based input devices. Some devices used for selection in some embodiments include keyboards, mice, joysticks, touch-pads, and the like (e.g., selection can be by a click from a mouse). The selection of the navigation status bar 2910 (as shown in stage 2903) causes the navigation application 2905 to return to the foreground in stage 2904. In addition to utilizing navigation status bar 2910 to return to the navigation application (i.e., to bring the navigation application to foreground), in some embodiments the navigation bar has other functions. For instance, the navigation status bar 2910 is used in some embodiments to provide navigation instructions (e.g., turn-by-turn directions) while the navigation application itself is still in the background. In other embodiments, the navigation status bar is replaced at various times by a navigation instruction bar that provides instructions.
As shown in
One of ordinary skill in the art will understand that in some embodiments, a navigation bar (a navigation instruction bar and/or a navigation status bar) appears at the top of some or all foreground applications, not just the application launching application. The activation of one or more controls in some embodiments causes applications other than the launching application to move to the foreground. Furthermore, in some embodiments the navigation bar continues to appear above foreground applications after switching between one foreground application and another, and not just when switching directly from the navigation application to a particular foreground application. An example of a navigation bar being displayed above another application is shown in
Process 3000 then determines (at 3020) whether the user device is near a navigation point (e.g., at a waypoint turn). While the application determines (at 3020) that the device is not near a navigation point the display remains as shown in stage 3101 of
Stage 3101 shows the state of a device when the navigation application is active as a background application and the foreground application 3115 is the application launching screen. The navigation application has not been turned off, but instead has been left on in the background. The visible indication in stage 3101 of the navigation application being on in the background is the navigation status bar 3110. Also, some embodiments display the status bar 3180 in a different color from its usual color when navigation is running in the background. In some embodiments the status bar 3180 and the navigation status bar 3110 are shown in various shades of green. In some embodiments, the colors or shades of one or both of the status bar and the navigation bar change over time to draw attention to the fact that the navigation application is executing in the background.
At this stage 3101, the device (and the person or vehicle carrying the device) is far from the next navigation point. The application of some embodiments, including the one illustrated in
Referring back to
In some embodiments, the navigation bars in stage 3101 and 3102 are treated as separate entities that happen to occupy a similar place on the screen. In such embodiments the navigation bar of stage 3101 can be characterized as a “navigation status bar”, while the navigation bar with navigation instructions in stage 3102 can be characterized as a “navigation instruction bar” or a “navigation direction bar”. In some embodiments, the navigation instruction bar 3120 is thicker than the navigation status bar 3110 (e.g., twice the thickness or more) and covers up the status bar. In other embodiments, the navigation bar is treated as a single entity that expands (e.g., to twice its previous thickness or more) to cover or replace the status bar when the navigation bar displays navigation directions.
In stages 3103 and 3104, as the device moves closer to the navigation point, the distance to the navigation point is counted down in the navigation instructions in navigation instruction bars 3130 (100 feet) and 3140 (0 feet). In stage 3104, the instructions have begun to switch to the next instruction.
In stage 3104, the actual turn is taking place. The navigation instructions in navigation instruction bar 3150 (shown in stage 3105) are replacing the previous navigation point instructions in navigation instruction bar 3140 with the instructions for the next navigation point. In some embodiments, including the illustrated embodiment, the navigation instructions are switched in a simulation of a flipping sign with multiple faces. Accordingly, instruction 3140 shows the instruction “0 feet turn left” as it begins to flip. In some embodiments, the sign flips up, in some embodiments the sign flips down. In other embodiments, the device uses other transition methods to remove the old navigation instruction in navigation instruction bar 3140 and replace it with the new navigation instruction in navigation instruction bar 3150 (in stage 3105). For instance, some embodiments simulate a new instruction sliding up, down, or sideways while the old instruction slides in the same direction. Other embodiments simulate sliding the new instruction over the old instruction. Still other embodiments simply have the old instruction disappear to be replaced by the new instruction.
When a navigation point is reached, process 3000 determines (at 3040) whether the final destination has been reached. If the final destination has been reached, the navigation ends (this is illustrated in
Stage 3105 occurs just after the left turn has been completed. The navigation instruction in navigation instruction bar 3150 has fully replaced the navigation instruction in navigation instruction bar 3140. The new navigation instruction in navigation instruction bar 3150 indicates a significant distance to the next navigation point. As mentioned above, the applications of some devices are programmed to display navigation instructions primarily when the device is near a navigation point, not at all times. Accordingly, after displaying the next navigation instruction in navigation instruction bar 3150 for a pre-set period (or in some embodiments after a preset distance traveled), the application in some embodiments returns to showing navigation status bar 3110 in stage 3106 (and process 3000 returns to operation 3015). However, when the new navigation point is determined (at 3050 of
The second stage 3202 also shows that the user selects icon 3225 commanding that the application represented by icon 3225 (e.g., a web browser) be moved to the foreground and the navigation application be moved to the background. One of ordinary skill in the art will understand that this is just one of many ways that some embodiments switch the navigation application into the background and another application into the foreground. For example the user could switch to the application launching view and launch an application, which would then replace the application launching view as the foreground application.
The web browser 3230 that the device switches to the foreground is shown in stage 3203. At the top of the screen is a navigation instruction bar 3235 indicating that the navigation application is running in the background and directing the user to turn right in 50 feet. In some embodiments, the status bar and a navigation status bar (e.g., as shown in
After following the navigation instructions shown by the device, the user will reach his intended destination.
Stage 3302 illustrates the user device 3300 when the destination is approached. As shown in this stage, the navigation instruction bar 3310 indicates “Destination on the Left”. Stage 3303 illustrates the user device 3300 after the destination is reached. As shown, navigation instruction bar 3310 of stages 3301 and 3302 is removed from the screen to indicate that the navigation instructions are finished and status bar 3380 returns to the screen. In some embodiments, the navigation application remains on in the background, but not visibly displayed at this stage 3303. In other embodiments the navigation application switches itself off at this stage 3303. In still other embodiments, the device continues to display the navigation bar after the destination is reached. Furthermore, the navigation application of some embodiments identifies a location as the end of vehicular navigation and indicates that the rest of the journey must be completed on foot, which the navigation application directs (e.g., in the navigation instruction bar).
The stage 3303 also shows that the icons 3390 have not moved. However, in other embodiments, the icons 3390 may move up to occupy at least a portion of the space that used to be occupied by the navigation instruction bar 3310 at the previous stages in some embodiments, when the navigation instruction bar is removed from the screen.
As described above, the navigation status bar and the navigation instruction bar are treated as distinct components in some embodiments. The above described figures show the navigation status bar below a status bar. However, when the navigation application is running in the background, the status bar itself is replaced with a navigation banner in some embodiments. This navigation banner is twice the height of the regular status bar in some embodiments. The navigation banner of some embodiments displays some or all of the same information as the status bar it replaces. In some embodiments, the navigation banner displays that information when the device is not nearing a navigation point and does not display it when the device is nearing a navigation point. When the device is nearing a navigation point, some or all of the status information is removed so that a direction relevant to the upcoming navigation point can be seen more clearly.
Devices that execute navigation applications of some embodiments include telephonic devices. In some embodiments, when a telephone call is being processed by the device, and the navigation application is running in the background, data about the telephone call (e.g., call time) replaces a navigation status bar or the instruction bar with a telephone call status bar.
In some embodiments, the navigation instruction bar 3420 re-emerges and replaces the phone data under some circumstances. In stage 3402, the device is near a navigation point. Therefore, the navigation instruction bar 3420 replaces the call status bar 3415 and the status bar 3410. After the navigation point is passed, the call status bar 3415 and the status bar 3410 are redisplayed as shown in stage 3403. In the illustrated embodiment of
The stages 3302 and 3303 show that the icons 3390 have not moved. However, in other embodiments, the icons may move up or down to occupy different spaces depending on the presence of the call status bar 3415 and the navigation instruction bar 3420.
B. Instructions when Device is Locked
1. Layout
In some embodiments, devices with multiple functions (e.g., mobile phones that run multiple applications) can be placed into locked mode from various applications. In some embodiments, there are multiple ways to place a device into locked mode. The locked mode of some embodiments is a mode with most of the controls disabled and with limited functionality until the device is unlocked. This has the benefit in some embodiments of preventing the user from accidentally ending navigation mode prematurely. In some embodiments, unlocking the device requires a particular gestural command on a specific part of the screen.
Some devices have a button that switches the screen off and/or puts the device into locked mode. Some devices have a timeout function that switches the screen off and/or puts the device into locked mode after a certain time has elapsed between user commands. Regardless of the way that the applications get into locked mode, most such devices come out of locked mode with the same application running in the foreground as the application running in the foreground when locked mode was entered. However, in the devices of some embodiments, regardless of what application (or application launcher) is running in the foreground when the device is locked, if the navigation application is running in the background, then the application returns from locked mode directly into the navigation application.
In stage 3502, the device is in a locked mode (as indicated by the unlocking slider 3530 on the screen). In this stage, the map 3540 is shown on the locked screen and turn-by-turn directions are shown on the information bar 3550.
In stage 3503, the user has started to slide the unlocking slider 3530 to the right in order to unlock the device. In this stage, the map 3540 is displayed on the screen and turn-by-turn navigation directions are shown on the information bar 3550. In some embodiments (not shown), when the slider moves all the way to the right, the user is asked to enter a pass code to unlock the screen. After the user successfully enters the passcode, the screen is unlocked. In some embodiments, the directions and/or the map are not shown under some circumstances in locked mode. For example, an interface for answering an incoming call may be displayed when a call comes in to the device and an interface for dealing with a call may be displayed when a call is in progress. Such an interface may override the display of the directions in the information bar, the display of the map, or both. Similarly, in some embodiments, other display views may replace the information bar, the map, or both even though the navigation application is still running on the device.
However, after the screen is unlocked, the navigation map 3540 stays in the foreground (instead of displaying application 3520 that was running in the foreground prior to the locking of the screen). As shown in stage 3504, the navigation application appears in full screen in the foreground. In this stage the screen is unlocked and navigation instructions 3560 and the map 3540 are displayed on the screen. In some embodiments, the navigation application includes the map 3540 in the same position as the map 3540 in the locked-screen view. Accordingly, in some embodiments, even for devices that ordinarily use a transition (e.g., a wipe or expansion of the new screen view from the center of the screen) between locked-screen views and other views when returning from locked mode, the device in the transition from stage 3503 to stage 3504 leaves the map in place and switches the other elements in the screen. That is, the map is constantly displayed during the transition from stage 3503 to stage 3504, while the navigation bar 3510 and the unlocking slider 3530 disappear and the navigation instructions 3560 appear instead. As stage 3504 shows, the device has returned from locked mode directly into the navigation application, even though the navigation application was running in the background, not the foreground in stage 3501 before the device was locked.
In stage 3602, the device is placed into locked mode (as indicated by the unlocking slider 3630 on the screen). In this stage, the map 3640 is shown on the locked screen and turn-by-turn directions are shown on the information bar 3650.
In stage 3603, the user has started to slide the unlocking slider 3630 to the right in order to unlock the device. In this stage, the map 3640 is displayed on the screen and turn-by-turn navigation directions are shown on the information bar 3650. When the slider moves all the way to the right, the user is prompted (not shown) to enter the passcode to unlock the screen. After the user successfully enters the passcode, the screen is unlocked. As mentioned above with respect to
As shown in stage 3604, the navigation application appears in the foreground. In this stage the screen is unlocked and the map 3640 and the navigation instructions 3660 are displayed on the screen. In some embodiments, the navigation application includes the same map 3640 in the same position as in the lock-screen view. Accordingly, in some embodiments, even for devices that would have a transition screen (e.g., a wipe or expansion from the center) when returning from locked mode, the device in the transition from stage 3603 to stage 3604 leaves the map in place and, in some embodiments, switches the other elements in the screen. That is, the map is constantly displayed during the transition from stage 3603 to stage 3604, while the information bar 3650 and the unlocking slider 3630 disappear and the navigation instructions 3660 appear on the display. As stage 3604 shows, the device has returned from locked mode back into the navigation application.
In the preceding two figures, the user pushes a control to enter a locked mode. In some embodiments, the user pushes such a control to turn the display off. Later, when the display is turned back on, either by pressing the same control again, or by pressing another control, then the device shows the locked mode when the display turns on again. Similarly, in some embodiments, the device has a timeout function that turns the display off after some particular amount of time has passed without the device receiving a command. In some embodiments, the device is in locked mode when the display turns on after such a lockout.
In addition to (or in some embodiments instead of) giving navigation instructions on a navigation bar when other applications are in the foreground, the navigation applications of some embodiments also provide navigation instructions while the device is in a locked mode.
In stage 3701, the device is close to the next navigation point, therefore navigation bar 3710 displays instructions to turn right in 500 feet. In some embodiments (including the illustrated embodiment) the navigation bar 3710 is translucent, allowing feature of the map 3712 to be seen through the navigation bar 3710. The location indicator 3714 indicates the location of the device, relative to the features of map 3712. The map itself includes the road the device is on (Curb Road), and the road that the navigation application is directing the user towards (T Road). Also displayed is a dark line 3718 showing the directed travel of the device and a lighter line 3719 showing the previous locations of the device along the navigation application's selected route. The unlocking slider 3716, unlocks the device when activated. The unlocking slider 3716 is, however, unused in this figure.
As the device reaches a point 250 feet from the navigation point, the navigation bar changes instructions as displayed in navigation bar 3720 in stage 3702. The location indicator 3714 is at the same location, but the map 3712 has moved down relative to the location indicator 3714. The new location of the map relative to the location indicator 3714 is another way that the navigation application shows that the device has moved closer to the navigation point.
Similarly, in stage 3703, the navigation bar 3730 indicates that the navigation point is only 100 feet away and the location indicator 3714 is closer to the turn on the map. Finally, in stage 3704, the device has gone around the corner and navigation bar 3740 is displaying the next navigation instruction. Although the transition between navigation instructions is not shown in this figure, in some embodiments the transition is similar to the described transition in background mode (with one instruction seemingly flipping up as if on a one side of a sign and being replaced by another that seems to be on another side of the sign). In other embodiments, other transition methods are used to remove the old navigation instruction 3730 and replace it with the new navigation instruction 3740 (in stage 3704). For instance, some embodiments simulate a new instruction sliding up or sideways while the old instruction slides in the same direction. Other embodiments simulate sliding the new instruction over the old instruction. Still other embodiments simply have the old instruction disappear and be replaced by the new instruction.
The new instructions are not the only indication that the turn has been made. The map 3712 has rotated so that the direction that the device is traveling in (along T Road) is shown on the map 3712 as being up. The lighter line 3719 on the map 3712 now includes the corner that the device has just turned.
Although the location indicator 3714 is shown in
While operating in locked mode, the navigation application of some embodiments provides directions until the device reaches its destination.
Once the device reaches its destination in stage 3802, the navigation bar 3820 shows that the destination is on the right, darker line 3818 is no longer shown on the map 3840. In some embodiments, the device then displays a message that the device has “arrived” as shown in stage 3803. The navigation application then, in stage 3804, releases the locked screen to whatever its default configuration is when the navigation application is not providing navigation instructions. In the illustrated embodiment, the default configuration includes a time and date indicator 3830.
This figure illustrates the locked mode view in a 2D map. However, the mapping application of some embodiments may operate in the locked mode while showing the map in 3D.
2. Notification Management
In some embodiments, devices notify their users of incoming text messages and other noteworthy events. Even when such devices are in a locked mode, some such devices can still display notifications. However, leaving a notification on the screen for an extended period of time may distract from navigation instructions also being displayed on the screen. Accordingly, some embodiments briefly display a notification on the screen and then make the notification accessible, but not visible. In some embodiments, there is a visible but unobtrusive sign indicating that there is a notification item waiting to be read.
In stage 3901, the navigation bar 3910 is below the status bar 3980 at the top of the screen displaying a navigation instruction. A notification message 3912 is displayed on the screen over the map 3940 to indicate that a text message has been received. The actual text message is not displayed in the illustrated embodiment, but embodiments that display the actual text message are within the scope of the invention. Some embodiments display a name (if known) of the text message sender or a phone number from which the text message originated in notification message 3912.
The application of some embodiments displays the notification for a preset length of time before the notification disappears, leaving the full map 3940 visible again. Some applications display the notification for less than 5 seconds, some for 5 seconds, and some for more than 5 seconds. Once the notification disappears, a drawer control 3922 appears in stage 3902 in the navigation bar 3910. The application of some embodiments, including the illustrated application, allows the drawer control 3922 to be expanded (e.g., by a touch gesture that drags down on the drawer control) in order to open a list of received notification items. Applications of other embodiments allow the drawer control to be tapped to open the list, or double tapped to open the list. Similarly, other applications allow the drawer control to be selected by other means, (e.g., a selection such as a click on an associated cursor control device).
In the illustrated embodiment, the drawer 3934 is shown as open in stage 3903. In this stage 3903 the drawer, in this case including only one text message 3932 and one missed call 3933, is shown in a list which covers the map from the bottom of the navigation bar 3910 to the top of the unlocking slider 3915. However, in some embodiments the drawer is translucent, semi-transparent, or transparent, allowing the map to be seen through the list. In some embodiments, the drawer only partially covers the map 3940 (e.g., covers half the map, or only that portion of the map needed to show all the text messages and other notification items in the drawer). In some embodiments, if a new message or notification that would normally be sent to the drawer arrives while the drawer is open, the message will be added to the drawer right away (with or without displaying a pop up notification in various embodiments).
When the list of messages is too long to fit on the screen the list can be scrolled up and down if necessary in some embodiments. When the user is finished looking at the list of messages, the user can close the drawer by activating a control (e.g., a hardware or on screen control such as a control that turns off the display) in some embodiments. In some embodiments, the drawer will remain open until the user turns the display off, and then back on again. The control could also include any number of controls activated by a gestural command such as a tap on the list or elsewhere on the screen, a double-tap, or a sliding gesture (e.g., a sliding gesture up with part or all of the drawer as the control) in some embodiments. The control could also include a button or other component of a mouse or other cursor control device, etc., in some embodiments.
Also, in addition to or instead of having a control to close the drawer, some embodiments display the opened drawer for varying lengths of time before it disappears, leaving the full map 3940 visible again as shown in stage 3904. Stage 3904 includes drawer control 3922. However, in some embodiments, after the drawer 3934 is closed, the drawer control 3922 is not shown until a new message arrives.
After the drawer is closed, if and when another text message or notification arrives, the stages 3901-3904 repeat with that new message, assuming that the navigation is still active. In some embodiments stage 3904 happens only if the user closes the drawer. If the drawer remains open, then the display remains in stage 3903 in some embodiments. Furthermore, the drawer open stage 3903 may not immediately follow stages 3901 and 3902. In some embodiments, if the user does not open the drawer, stages 3901-3902 are repeated with each of multiple messages coming in and the drawer remaining closed with the drawer control 3922 displayed as the new message notifications appear.
In some cases, a user may decide to unlock the device before opening the drawer 3934. In some embodiments, the normal behavior of the device when coming out of locked mode with notifications is to list the notifications on the screen. However, in some embodiments, when the navigation application is running, opening into the navigation application takes priority over displaying the notification messages. Therefore the device of those embodiments unlocks and opens into the navigation application rather than opening into a list of notification messages. In some such embodiments, a user can choose to open the list of notification messages after the navigation application is opened.
In stage 4001, the navigation bar 4010 is below the status bar 4080 at the top of the screen displaying a navigation instruction. A notification message 4012 is displayed on the screen over the map 4040 to indicate that a text message has been received. The actual text message is not displayed in the illustrated embodiment, but embodiments that display the actual text message are within the scope of the invention. Some embodiments display the name of the sender, the phone number of the sender, or both in notification message 4012. The application of different embodiments displays the notification for varying lengths of time before it disappears, leaving the full map 4040 visible again. Some applications display the notification for less than 5 seconds, some for 5 seconds, and some for more than 5 seconds.
Once the notification disappears, a drawer control 4022 appears in stage 4002 in the navigation bar 4010. Stage 4001 is identical to stage 3901 of
The navigation application in some embodiments does not show a drawer control. However, by dragging the top center of the screen down (as shown in stage 4004) the user can cause the drawer 4044 to come down (as shown in stage 4005). In some embodiments, the drawer control 4022 appears under the dragging finger as the finger drags the drawer 4044 down. In other embodiments, when the navigation application is in the foreground, multiple drags must be employed. For example, one drag gesture at the top of the screen is used to expose the drawer control 4022 and a separate drag gesture on the drawer control 4022 is used to open the drawer in some embodiments. Stage 4005 shows the drawer 4044 fully extended and covering the entire screen. Text message 4052 appears at the top of the screen.
In some embodiments, the drawer stays open until the user either closes the drawer (at which point the navigation application appears again) or locks the device. In some embodiments, the drawer can be closed by pulling up the drawer control 4022. In other embodiments, the drawer cannot be closed by pulling up the drawer control up 4022, but can be closed by some other control (e.g., a button or a gestural command). For example the device can be locked, e.g., by activating a control 4090 which also closes the drawer in some embodiments. Some embodiments also automatically close the drawer after a pre-determined amount of time. In some embodiments, after the drawer is opened, either in locked mode or unlocked mode, once the drawer is closed the drawer is emptied and is no longer accessible from the locked mode view, as shown in stage 4006, in which the drawer control 4022 is no longer present. That is, the drawer control 4022 will only be displayed again when a new notification is received. However, in other embodiments, the drawer control 4022 is not removed, is only removed when certain methods of closing it are employed, or is removed if the drawer is opened in the unlocked mode, but not if the drawer is opened in the locked mode.
In some embodiments, the drawer displays messages of different types in separate areas. For example, some embodiments display text messages in a separate area from “missed call” messages. In some embodiments the drawer displays different types of messages in separate areas when it is opened in the unlocked mode, but the drawer in the locked mode does not display different types of messages in separate areas. In other embodiments the drawer displays different types of messages in separate areas when it is opened in the unlocked mode and the drawer in the locked mode also displays different types of messages in separate areas. In other embodiments the drawer in locked mode uses separate areas for different message types and the drawer in unlocked mode does not. In other embodiments neither drawer separates message types.
3. Dynamically Turn On
Power saving is a feature of some embodiments of the application. In some embodiments, the navigation application operating in locked mode switches the screen on only when the device is approaching a navigation point or receives a notification.
Process 4100 of
In some embodiments a device turns the screen off and enters locked mode when it has received no commands in a pre-specified amount of time (e.g., 5 minutes, 15 minutes, etc.). The process determines (at 4110) whether any controls have been activated in the amount of time pre-specified for locking the device and turning of the screen. If any controls have been activated (other than one that shuts down the display and/or locks the device right away) then the device resets its countdown to going into display off and locked mode.
When the process determines that enough time has passed, the process turns off (at 4115) the screen. In some embodiments, instead of or in addition to the timeout screen deactivation, there is a control that the user can select (e.g., a button) that puts the device into locked mode. In some embodiments, the timeout screen deactivation occurs when some applications are running, but not when other applications are running. For example, in some embodiments, when the navigation application is running in the foreground the device does not shut down the screen after a preset time. Furthermore, in some embodiments, the device doesn't timeout when the navigation application is running in the background either.
Operation 4115 is illustrated in stage 4202 of
In different embodiments, the device determines that it is near a navigation point when the device is 1000 feet from the navigation point, or 500 feet, or 250 feet, or any other particular distance. Once process 4100 determines (at 4120) that the device is near the navigation point, the process turns on (at 4125) an ambient light sensor. In some embodiments the ambient light sensor is part of a camera of the device. In other embodiments, the ambient light sensor is not part of a camera of the device. In some embodiments, the ambient light sensor is on at all times. In some embodiments, the ambient light sensor is a passive element that doesn't need to be powered on to function. The ambient light sensor determines how much light is present around the device. If there is a large amount of light, then the screen would have to be turned on at a high level of brightness to be seen against the existing light. However, if there if a low amount of ambient light, then the screen could be turned on at a dimmer level and still be bright enough to be seen in the lower ambient light.
Once the light level is determined, the process 4100 turns on (at 4130) the screen at a brightness level in accord with the ambient light levels detected by the ambient light sensor. The screen then displays (at 4135) a countdown to the next navigation point. This is illustrated in stage 4203 of
If the process 4100 determines (at 4155) that the next navigation point is near, then the process returns to operation 4135 and counts down to the next navigation point. However, that is not the case in
The above described figure shows the device switching the display on as it nears predetermined navigation points, and switching the display off when it is not nearing the preset navigation points. However, in some embodiments, the device also turns the display on if the user deviates from the prescribed route (e.g., the user takes a wrong turn). In some such embodiments, the device displays a “rerouting” message until the device has calculated a new route. In some embodiments, the device then displays the next navigation instruction and then turns off the display unless the next navigation point is within the threshold distance.
In a similar manner to the way the navigation application of some embodiments turns on the screen in locked mode when the device approaches a navigation point, the device of some embodiments turns on the screen when a notification is received while the navigation program is running.
The process then determines (at 4335) whether the drawer has been opened (e.g., by the user sliding a drawer control 3922) before a time limit. If the drawer has not been opened within the time limit then the process turns the screen off (at 4305) again. If the drawer has been opened before the time limit, then the messages are displayed (at 4340), e.g., as shown in
In some embodiments, if the process 4300 determines (at 4345) that the drawer remains open, then the process determines (at 4350) whether a timeout period has been reached. If the timeout period has not been reached, then the process continues to display (at 4340) the messages. If the time limit runs out before the drawer is closed by the user, then the process turns the screen off (at 4305). In some embodiments, if the user is sending commands to the device (e.g., scrolling through the messages) then the countdown to the time limit will not begin until the device stops receiving commands from the user.
One of ordinary skill in the art will understand that although the flowcharts for process 4300 of
As described above, the device in locked mode has a limited number of active controls. However, in some embodiments, while the locked mode is operative, the map on the lock screen can be moved to one side or up and down, to a greater or lesser degree, by a gestural command in the direction that the user wishes to move the map. In some embodiments, when the device is released, the map returns to its default position.
IV. Electronic System
Many of the above-described features and applications are implemented as software processes that are specified as a set of instructions recorded on a computer readable storage medium (also referred to as computer readable medium). When these instructions are executed by one or more computational or processing unit(s) (e.g., one or more processors, cores of processors, or other processing units), they cause the processing unit(s) to perform the actions indicated in the instructions. Examples of computer readable media include, but are not limited to, CD-ROMs, flash drives, random access memory (RAM) chips, hard drives, erasable programmable read-only memories (EPROMs), electrically erasable programmable read-only memories (EEPROMs), etc. The computer readable media does not include carrier waves and electronic signals passing wirelessly or over wired connections.
In this specification, the term “software” is meant to include firmware residing in read-only memory or applications stored in magnetic storage which can be read into memory for processing by a processor. Also, in some embodiments, multiple software inventions can be implemented as sub-parts of a larger program while remaining distinct software inventions. In some embodiments, multiple software inventions can also be implemented as separate programs. Finally, any combination of separate programs that together implement a software invention described here is within the scope of the invention. In some embodiments, the software programs, when installed to operate on one or more electronic systems, define one or more specific machine implementations that execute and perform the operations of the software programs.
A. Mobile Device
The mapping and navigation applications of some embodiments operate on mobile devices, such as smart phones (e.g., iPhones®) and tablets (e.g., iPads®).
The peripherals interface 4415 is coupled to various sensors and subsystems, including a camera subsystem 4420, a wireless communication subsystem(s) 4425, an audio subsystem 4430, an I/O subsystem 4435, etc. The peripherals interface 4415 enables communication between the processing units 4405 and various peripherals. For example, an orientation sensor 4445 (e.g., a gyroscope) and an acceleration sensor 4450 (e.g., an accelerometer) is coupled to the peripherals interface 4415 to facilitate orientation and acceleration functions.
The camera subsystem 4420 is coupled to one or more optical sensors 4440 (e.g., a charged coupled device (CCD) optical sensor, a complementary metal-oxide-semiconductor (CMOS) optical sensor, etc.). The camera subsystem 4420 coupled with the optical sensors 4440 facilitates camera functions, such as image and/or video data capturing. The wireless communication subsystem 4425 serves to facilitate communication functions. In some embodiments, the wireless communication subsystem 4425 includes radio frequency receivers and transmitters, and optical receivers and transmitters (not shown in
The I/O subsystem 4435 involves the transfer between input/output peripheral devices, such as a display, a touch screen, etc., and the data bus of the processing units 4405 through the peripherals interface 4415. The I/O subsystem 4435 includes a touch-screen controller 4455 and other input controllers 4460 to facilitate the transfer between input/output peripheral devices and the data bus of the processing units 4405. As shown, the touch-screen controller 4455 is coupled to a touch screen 4465. The touch-screen controller 4455 detects contact and movement on the touch screen 4465 using any of multiple touch sensitivity technologies. The other input controllers 4460 are coupled to other input/control devices, such as one or more buttons. Some embodiments include a near-touch sensitive screen and a corresponding controller that can detect near-touch interactions instead of or in addition to touch interactions.
The memory interface 4410 is coupled to memory 4470. In some embodiments, the memory 4470 includes volatile memory (e.g., high-speed random access memory), non-volatile memory (e.g., flash memory), a combination of volatile and non-volatile memory, and/or any other type of memory. As illustrated in
The memory 4470 also includes communication instructions 4474 to facilitate communicating with one or more additional devices; graphical user interface instructions 4476 to facilitate graphic user interface processing; image processing instructions 4478 to facilitate image-related processing and functions; input processing instructions 4480 to facilitate input-related (e.g., touch input) processes and functions; audio processing instructions 4482 to facilitate audio-related processes and functions; and camera instructions 4484 to facilitate camera-related processes and functions. The instructions described above are merely exemplary and the memory 4470 includes additional and/or other instructions in some embodiments. For instance, the memory for a smartphone may include phone instructions to facilitate phone-related processes and functions. Additionally, the memory may include instructions for a mapping and navigation application as well as other applications. The above-identified instructions need not be implemented as separate software programs or modules. Various functions of the mobile computing device can be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits.
While the components illustrated in
B. Computer System
The bus 4505 collectively represents all system, peripheral, and chipset buses that communicatively connect the numerous internal devices of the electronic system 4500. For instance, the bus 4505 communicatively connects the processing unit(s) 4510 with the read-only memory 4530, the GPU 4515, the system memory 4520, and the permanent storage device 4535.
From these various memory units, the processing unit(s) 4510 retrieves instructions to execute and data to process in order to execute the processes of the invention. The processing unit(s) may be a single processor or a multi-core processor in different embodiments. Some instructions are passed to and executed by the GPU 4515. The GPU 4515 can offload various computations or complement the image processing provided by the processing unit(s) 4510. In some embodiments, such functionality can be provided using CoreImage's kernel shading language.
The read-only-memory (ROM) 4530 stores static data and instructions that are needed by the processing unit(s) 4510 and other modules of the electronic system. The permanent storage device 4535, on the other hand, is a read-and-write memory device. This device is a non-volatile memory unit that stores instructions and data even when the electronic system 4500 is off. Some embodiments of the invention use a mass-storage device (such as a magnetic or optical disk and its corresponding disk drive, integrated flash memory) as the permanent storage device 4535.
Other embodiments use a removable storage device (such as a floppy disk, flash memory device, etc., and its corresponding drive) as the permanent storage device. Like the permanent storage device 4535, the system memory 4520 is a read-and-write memory device. However, unlike storage device 4535, the system memory 4520 is a volatile read-and-write memory, such a random access memory. The system memory 4520 stores some of the instructions and data that the processor needs at runtime. In some embodiments, the invention's processes are stored in the system memory 4520, the permanent storage device 4535, and/or the read-only memory 4530. For example, the various memory units include instructions for processing multimedia clips in accordance with some embodiments. From these various memory units, the processing unit(s) 4510 retrieves instructions to execute and data to process in order to execute the processes of some embodiments.
The bus 4505 also connects to the input and output devices 4540 and 4545. The input devices 4540 enable the user to communicate information and select commands to the electronic system. The input devices 4540 include alphanumeric keyboards and pointing devices (also called “cursor control devices”), cameras (e.g., webcams), microphones or similar devices for receiving voice commands, etc. The output devices 4545 display images generated by the electronic system or otherwise output data. The output devices 4545 include printers and display devices, such as cathode ray tubes (CRT) or liquid crystal displays (LCD), as well as speakers or similar audio output devices. Some embodiments include devices such as a touchscreen that function as both input and output devices.
Finally, as shown in
Some embodiments include electronic components, such as microprocessors, storage and memory that store computer program instructions in a machine-readable or computer-readable medium (alternatively referred to as computer-readable storage media, machine-readable media, or machine-readable storage media). Some examples of such computer-readable media include RAM, ROM, read-only compact discs (CD-ROM), recordable compact discs (CD-R), rewritable compact discs (CD-RW), read-only digital versatile discs (e.g., DVD-ROM, dual-layer DVD-ROM), a variety of recordable/rewritable DVDs (e.g., DVD-RAM, DVD-RW, DVD+RW, etc.), flash memory (e.g., SD cards, mini-SD cards, micro-SD cards, etc.), magnetic and/or solid state hard drives, read-only and recordable Blu-Ray® discs, ultra density optical discs, any other optical or magnetic media, and floppy disks. The computer-readable media may store a computer program that is executable by at least one processing unit and includes sets of instructions for performing various operations. Examples of computer programs or computer code include machine code, such as is produced by a compiler, and files including higher-level code that are executed by a computer, an electronic component, or a microprocessor using an interpreter.
While the above discussion primarily refers to microprocessor or multi-core processors that execute software, some embodiments are performed by one or more integrated circuits, such as application specific integrated circuits (ASICs) or field programmable gate arrays (FPGAs). In some embodiments, such integrated circuits execute instructions that are stored on the circuit itself. In addition, some embodiments execute software stored in programmable logic devices (PLDs), ROM, or RAM devices.
As used in this specification and any claims of this application, the terms “computer”, “server”, “processor”, and “memory” all refer to electronic or other technological devices. These terms exclude people or groups of people. For the purposes of the specification, the terms display or displaying means displaying on an electronic device. As used in this specification and any claims of this application, the terms “computer readable medium,” “computer readable media,” and “machine readable medium” are entirely restricted to tangible, physical objects that store information in a form that is readable by a computer. These terms exclude any wireless signals, wired download signals, and any other ephemeral signals.
V. Map Service Environment
Various embodiments may operate within a map service operating environment.
In some embodiments, a map service is implemented by one or more nodes in a distributed computing system. Each node may be assigned one or more services or components of a map service. Some nodes may be assigned the same map service or component of a map service. A load balancing node in some embodiments distributes access or requests to other nodes within a map service. In some embodiments a map service is implemented as a single system, such as a single server. Different modules or hardware devices within a server may implement one or more of the various services provided by a map service.
A map service in some embodiments provides map services by generating map service data in various formats. In some embodiments, one format of map service data is map image data. Map image data provides image data to a client device so that the client device may process the image data (e.g., rendering and/or displaying the image data as a two-dimensional or three-dimensional map). Map image data, whether in two or three dimensions, may specify one or more map tiles. A map tile may be a portion of a larger map image. Assembling together the map tiles of a map produces the original map. Tiles may be generated from map image data, routing or navigation data, or any other map service data. In some embodiments map tiles are raster-based map tiles, with tile sizes ranging from any size both larger and smaller than a commonly-used 256 pixel by 256 pixel tile. Raster-based map tiles may be encoded in any number of standard digital image representations including, but not limited to, Bitmap (.bmp), Graphics Interchange Format (.gif), Joint Photographic Experts Group (.jpg, .jpeg, etc.), Portable Networks Graphic (.png), or Tagged Image File Format (.tiff). In some embodiments, map tiles are vector-based map tiles, encoded using vector graphics, including, but not limited to, Scalable Vector Graphics (.svg) or a Drawing File (.drw). Some embodiments also include tiles with a combination of vector and raster data. Metadata or other information pertaining to the map tile may also be included within or along with a map tile, providing further map service data to a client device. In various embodiments, a map tile is encoded for transport utilizing various standards and/or protocols, some of which are described in examples below.
In various embodiments, map tiles may be constructed from image data of different resolutions depending on zoom level. For instance, for low zoom level (e.g., world or globe view), the resolution of map or image data need not be as high relative to the resolution at a high zoom level (e.g., city or street level). For example, when in a globe view, there may be no need to render street level artifacts as such objects would be so small as to be negligible in many cases.
A map service in some embodiments performs various techniques to analyze a map tile before encoding the tile for transport. This analysis may optimize map service performance for both client devices and a map service. In some embodiments map tiles are analyzed for complexity, according to vector-based graphic techniques, and constructed utilizing complex and non-complex layers. Map tiles may also be analyzed for common image data or patterns that may be rendered as image textures and constructed by relying on image masks. In some embodiments, raster-based image data in a map tile contains certain mask values, which are associated with one or more textures. Some embodiments also analyze map tiles for specified features that may be associated with certain map styles that contain style identifiers.
Other map services generate map service data relying upon various data formats separate from a map tile in some embodiments. For instance, map services that provide location data may utilize data formats conforming to location service protocols, such as, but not limited to, Radio Resource Location services Protocol (RRLP), TIA 801 for Code Division Multiple Access (CDMA), Radio Resource Control (RRC) position protocol, or LTE Positioning Protocol (LPP). Embodiments may also receive or request data from client devices identifying device capabilities or attributes (e.g., hardware specifications or operating system version) or communication capabilities (e.g., device communication bandwidth as determined by wireless signal strength or wire or wireless network type).
A map service may obtain map service data from internal or external sources. For example, satellite imagery used in map image data may be obtained from external services, or internal systems, storage devices, or nodes. Other examples may include, but are not limited to, GPS assistance servers, wireless network coverage databases, business or personal directories, weather data, government information (e.g., construction updates or road name changes), or traffic reports. Some embodiments of a map service may update map service data (e.g., wireless network coverage) for analyzing future requests from client devices.
Various embodiments of a map service may respond to client device requests for map services. These requests may be for a specific maps or portions of a map. Some embodiments format requests for a map as requests for certain map tiles. In some embodiments, requests also supply the map service with starting locations (or current locations) and destination locations for a route calculation. A client device may also request map service rendering information, such as map textures or style sheets. In at least some embodiments, requests are also one of a series of requests implementing turn-by-turn navigation. Requests for other geographic data may include, but are not limited to, requests for current location, wireless network coverage, weather, traffic information, or nearby points-of-interest.
A map service, in some embodiments, analyzes client device requests to optimize a device or map service operation. For instance, a map service may recognize that the location of a client device is in an area of poor communications (e.g., weak wireless signal) and send more map service data to supply a client device in the event of loss in communication or send instructions to utilize different client hardware (e.g., orientation sensors) or software (e.g., utilize wireless location services or Wi-Fi positioning instead of GPS-based services). In another example, a map service may analyze a client device request for vector-based map image data and determine that raster-based map data better optimizes the map image data according to the image's complexity. Embodiments of other map services may perform similar analysis on client device requests and, as such, the above examples are not intended to be limiting.
Various embodiments of client devices (e.g., client devices 4602a-4602c) are implemented on different portable-multifunction device types. Client devices 4602a-4602c utilize map service 4630 through various communication methods and protocols. In some embodiments, client devices 4602a-4602c obtain map service data from map service 4630. Client devices 4602a-4602c request or receive map service data. Client devices 4602a-4602c then process map service data (e.g., render and/or display the data) and may send the data to another software or hardware module on the device or to an external device or system.
A client device, according to some embodiments, implements techniques to render and/or display maps. These maps may be requested or received in various formats, such as map tiles described above. A client device may render a map in two-dimensional or three-dimensional views. Some embodiments of a client device display a rendered map and allow a user, system, or device providing input to manipulate a virtual camera in the map, changing the map display according to the virtual camera's position, orientation, and field-of-view. Various forms and input devices are implemented to manipulate a virtual camera. In some embodiments, touch input, through certain single or combination gestures (e.g., touch-and-hold or a swipe) manipulate the virtual camera. Other embodiments allow manipulation of the device's physical location to manipulate a virtual camera. For instance, a client device may be tilted up from its current position to manipulate the virtual camera to rotate up. In another example, a client device may be tilted forward from its current position to move the virtual camera forward. Other input devices to the client device may be implemented including, but not limited to, auditory input (e.g., spoken words), a physical keyboard, mouse, and/or a joystick.
Some embodiments provide various visual feedback to virtual camera manipulations, such as displaying an animation of possible virtual camera manipulations when transitioning from two-dimensional map views to three-dimensional map views. Some embodiments also allow input to select a map feature or object (e.g., a building) and highlight the object, producing a blur effect that maintains the virtual camera's perception of three-dimensional space.
In some embodiments, a client device implements a navigation system (e.g., turn-by-turn navigation). A navigation system provides directions or route information, which may be displayed to a user. Some embodiments of a client device request directions or a route calculation from a map service. A client device may receive map image data and route data from a map service. In some embodiments, a client device implements a turn-by-turn navigation system, which provides real-time route and direction information based upon location information and route information received from a map service and/or other location system, such as a Global Positioning Satellite (GPS). A client device may display map image data that reflects the current location of the client device and update the map image data in real-time. A navigation system may provide auditory or visual directions to follow a certain route.
A virtual camera is implemented to manipulate navigation map data according to some embodiments. In some embodiments, the client devices allow the device to adjust the virtual camera display orientation to bias toward the route destination. Some embodiments also allow the virtual camera to navigate turns by simulating the inertial motion of the virtual camera.
Client devices implement various techniques to utilize map service data from map service. Some embodiments implement some techniques to optimize rendering of two-dimensional and three-dimensional map image data. In some embodiments, a client device locally stores rendering information. For instance, a client stores a style sheet, which provides rendering directions for image data containing style identifiers. In another example, common image textures may be stored to decrease the amount of map image data transferred from a map service. Client devices in different embodiments implement various modeling techniques to render two-dimensional and three-dimensional map image data, examples of which include, but are not limited to: generating three-dimensional buildings out of two-dimensional building footprint data; modeling two-dimensional and three-dimensional map objects to determine the client device communication environment; generating models to determine whether map labels are seen from a certain virtual camera position; and generating models to smooth transitions between map image data. In some embodiments, the client devices also order or prioritize map service data in certain techniques. For instance, a client device detects the motion or velocity of a virtual camera, which if exceeding certain threshold values, lower-detail image data is loaded and rendered for certain areas. Other examples include: rendering vector-based curves as a series of points, preloading map image data for areas of poor communication with a map service, adapting textures based on display zoom level, or rendering map image data according to complexity.
In some embodiments, client devices communicate utilizing various data formats separate from a map tile. For instance, some client devices implement Assisted Global Positioning Satellites (A-GPS) and communicate with location services that utilize data formats conforming to location service protocols, such as, but not limited to, Radio Resource Location services Protocol (RRLP), TIA 801 for Code Division Multiple Access (CDMA), Radio Resource Control (RRC) position protocol, or LTE Positioning Protocol (LPP). Client devices may also receive GPS signals directly. Embodiments may also send data, with or without solicitation from a map service, identifying the client device's capabilities or attributes (e.g., hardware specifications or operating system version) or communication capabilities (e.g., device communication bandwidth as determined by wireless signal strength or wire or wireless network type).
In some embodiments, both voice and data communications are established over wireless network 4610 and access device 4612. For instance, device 4602a can place and receive phone calls (e.g., using voice over Internet Protocol (VoIP) protocols), send and receive e-mail messages (e.g., using Simple Mail Transfer Protocol (SMTP) or Post Office Protocol 3 (POP3)), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over wireless network 4610, gateway 4614, and WAN 4620 (e.g., using Transmission Control Protocol/Internet Protocol (TCP/IP) or User Datagram Protocol (UDP)). Likewise, in some implementations, devices 4602b and 4602c can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over access device 4612 and WAN 4620. In various embodiments, any of the illustrated client devices may communicate with map service 4630 and/or other service(s) 4650 using a persistent connection established in accordance with one or more security protocols, such as the Secure Sockets Layer (SSL) protocol or the Transport Layer Security (TLS) protocol.
Devices 4602a and 4602b can also establish communications by other means. For example, wireless device 4602a can communicate with other wireless devices (e.g., other devices 4602b, cell phones, etc.) over the wireless network 4610. Likewise devices 4602a and 4602b can establish peer-to-peer communications 4640 (e.g., a personal area network) by use of one or more communication subsystems, such as Bluetooth® communication from Bluetooth Special Interest Group, Inc. of Kirkland, Wash. Device 4602c can also establish peer to peer communications with devices 4602a or 4602b (not shown). Other communication protocols and topologies can also be implemented. Devices 4602a and 4602b may also receive Global Positioning Satellite (GPS) signals from GPS satellites 4660.
Devices 4602a, 4602b, and 4602c can communicate with map service 4630 over one or more wired and/or wireless networks, 4612 or 4610. For instance, map service 4630 can provide map service data to rendering devices 4602a, 4602b, and 4602c. Map service 4630 may also communicate with other services 4650 to obtain data to implement map services. Map service 4630 and other services 4650 may also receive GPS signals from GPS satellites 4660.
In various embodiments, map service 4630 and/or other service(s) 4650 are configured to process search requests from any of the client devices. Search requests may include but are not limited to queries for businesses, addresses, residential locations, points of interest, or some combination thereof. Map service 4630 and/or other service(s) 4650 may be configured to return results related to a variety of parameters including but not limited to a location entered into an address bar or other text entry field (including abbreviations and/or other shorthand notation), a current map view (e.g., user may be viewing one location on the multifunction device while residing in another location), current location of the user (e.g., in cases where the current map view did not include search results), and the current route (if any). In various embodiments, these parameters may affect the composition of the search results (and/or the ordering of the search results) based on different priority weightings. In various embodiments, the search results that are returned may be a subset of results selected based on specific criteria including but not limited to a quantity of times the search result (e.g., a particular point of interest) has been requested, a measure of quality associated with the search result (e.g., highest user or editorial review rating), and/or the volume of reviews for the search results (e.g., the number of times the search result has been review or rated).
In various embodiments, map service 4630 and/or other service(s) 4650 are configured to provide auto-complete search results that are displayed on the client device, such as within the mapping application. For instance, auto-complete search results may populate a portion of the screen as the user enters one or more search keywords on the multifunction device. In some cases, this feature may save the user time as the desired search result may be displayed before the user enters the full search query. In various embodiments, the auto complete search results may be search results found by the client on the client device (e.g., bookmarks or contacts), search results found elsewhere (e.g., from the Internet) by map service 4630 and/or other service(s) 4650, and/or some combination thereof. As is the case with commands, any of the search queries may be entered by the user via voice or through typing. The multifunction device may be configured to display search results graphically within any of the map display described herein. For instance, a pin or other graphical indicator may specify locations of search results as points of interest. In various embodiments, responsive to a user selection of one of these points of interest (e.g., a touch selection, such as a tap), the multifunction device is configured to display additional information about the selected point of interest including but not limited to ratings, reviews or review snippets, hours of operation, store status (e.g., open for business, permanently closed, etc.), and/or images of a storefront for the point of interest. In various embodiments, any of this information may be displayed on a graphical information card that is displayed in response to the user's selection of the point of interest.
In various embodiments, map service 4630 and/or other service(s) 4650 provide one or more feedback mechanisms to receive feedback from client devices 4602a-4602c. For instance, client devices may provide feedback on search results to map service 4630 and/or other service(s) 4650 (e.g., feedback specifying ratings, reviews, temporary or permanent business closures, errors etc.); this feedback may be used to update information about points of interest in order to provide more accurate or more up-to-date search results in the future. In some embodiments, map service 4630 and/or other service(s) 4650 may provide testing information to the client device (e.g., an A/B test) to determine which search results are best. For instance, at random intervals, the client device may receive and present two search results to a user and allow the user to indicate the best result. The client device may report the test results to map service 4630 and/or other service(s) 4650 to improve future search results based on the chosen testing technique, such as an A/B test technique in which a baseline control sample is compared to a variety of single-variable test samples in order to improve results.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. For instance, many of the figures illustrate various touch gestures (e.g., taps, double taps, swipe gestures, press and hold gestures, etc.). However, many of the illustrated operations could be performed via different touch gestures (e.g., a swipe instead of a tap, etc.) or by non-touch input (e.g., using a cursor controller, a keyboard, a touchpad/trackpad, a near-touch sensitive screen, etc.). In addition, a number of the figures conceptually illustrate processes. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Furthermore, the process could be implemented using several sub-processes, or as part of a larger macro process.
While the invention has been described with reference to numerous specific details, one of ordinary skill in the art will recognize that the invention can be embodied in other specific forms without departing from the spirit of the invention. In addition, a number of the figures conceptually illustrate processes. The specific operations of these processes may not be performed in the exact order shown and described. The specific operations may not be performed in one continuous series of operations, and different specific operations may be performed in different embodiments. Furthermore, the process could be implemented using several sub-processes, or as part of a larger macro process. Thus, one of ordinary skill in the art would understand that the invention is not to be limited by the foregoing illustrative details, but rather is to be defined by the appended claims.
This is a continuation of U.S. patent application Ser. No. 15/003,607, filed Jan. 21, 2016, which is a continuation application of U.S. patent application Ser. No. 14/691,523, filed Apr. 20, 2015, now issued as U.S. Pat. No. 9,243,924. U.S. patent application Ser. No. 14/691,523 is a continuation application of U.S. patent application Ser. No. 13/632,120, filed Sep. 30, 2012, now issued as U.S. Pat. No. 9,052,197. U.S. patent application Ser. No. 13/632,120 which claims the benefit of U.S. Provisional Patent Application 61/655,995, filed Jun. 5, 2012; U.S. Provisional Application 61/655,997, filed Jun. 5, 2012; U.S. Provisional Patent Application 61/656,015, filed Jun. 6, 2012; U.S. Provisional Application 61/656,032, filed Jun. 6, 2012; U.S. Provisional Application 61/656,043, filed Jun. 6, 2012; U.S. Provisional Patent Application 61/656,080, filed Jun. 6, 2012; U.S. Provisional Application 61/657,864, filed Jun. 10, 2012; U.S. Provisional Application 61/657,880, filed Jun. 10, 2012; U.S. Provisional Patent Application 61/699,842, filed Sep. 11, 2012; U.S. Provisional Application 61/699,855, filed Sep. 11, 2012; and U.S. Provisional Patent Application 61/699,851, filed Sep. 11, 2012, and U.S. Provisional Patent Application 61/699,857, filed Sep. 11, 2012. The above-mentioned applications are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 636314 | Billman | Nov 1899 | A |
| 4797836 | Witek et al. | Jan 1989 | A |
| 4914605 | Loughmiller et al. | Apr 1990 | A |
| 5031104 | Ikeda et al. | Jul 1991 | A |
| 5289572 | Yano | Feb 1994 | A |
| 5321161 | Vreugdenhil et al. | Jun 1994 | A |
| 5353319 | Challberg | Oct 1994 | A |
| 5359712 | Cohen et al. | Oct 1994 | A |
| 5406492 | Suzuki | Apr 1995 | A |
| 5459667 | Odagaki et al. | Oct 1995 | A |
| 5459702 | Greenspan | Oct 1995 | A |
| 5592173 | Lau | Jan 1997 | A |
| 5629854 | Schulte | May 1997 | A |
| 5654892 | Fujii et al. | Aug 1997 | A |
| 5692173 | Chew | Nov 1997 | A |
| 5717848 | Watanabe et al. | Feb 1998 | A |
| 5748194 | Chen | May 1998 | A |
| 5787233 | Akimoto | Jul 1998 | A |
| 5848375 | Nunobiki et al. | Dec 1998 | A |
| 5862511 | Croyle et al. | Jan 1999 | A |
| 5878368 | Degraaf | Mar 1999 | A |
| 5913918 | Nakano et al. | Jun 1999 | A |
| 5928308 | Nanba et al. | Jul 1999 | A |
| 5938718 | Morimoto et al. | Aug 1999 | A |
| 5966129 | Matsukuma et al. | Oct 1999 | A |
| 5990898 | Urano | Nov 1999 | A |
| 6029111 | Croyle | Feb 2000 | A |
| 6102253 | Gallina et al. | Aug 2000 | A |
| 6107961 | Takagi | Aug 2000 | A |
| 6141568 | Sakaguchi | Oct 2000 | A |
| 6141588 | Cox et al. | Oct 2000 | A |
| 6153269 | Gleason et al. | Nov 2000 | A |
| 6163269 | Millington et al. | Dec 2000 | A |
| 6173232 | Nanba et al. | Jan 2001 | B1 |
| 6176380 | Glories et al. | Jan 2001 | B1 |
| 6178380 | Millington | Jan 2001 | B1 |
| 6202026 | Nimura et al. | Mar 2001 | B1 |
| 6253151 | Dialer et al. | Jun 2001 | B1 |
| 6259446 | Matheny et al. | Jul 2001 | B1 |
| 6295503 | Inoue et al. | Sep 2001 | B1 |
| 6311125 | Okano et al. | Oct 2001 | B1 |
| 6321158 | Delorme et al. | Nov 2001 | B1 |
| 6321161 | Herbst et al. | Nov 2001 | B1 |
| 6360167 | Millington et al. | Mar 2002 | B1 |
| 6363145 | Shaffer et al. | Mar 2002 | B1 |
| 6363322 | Millington | Mar 2002 | B1 |
| 6374180 | Slominski et al. | Apr 2002 | B1 |
| 6381534 | Takayama et al. | Apr 2002 | B2 |
| 6396475 | Ellenby et al. | May 2002 | B1 |
| 6415224 | Wako et al. | Jul 2002 | B1 |
| 6434482 | Oshida et al. | Aug 2002 | B1 |
| 6480783 | Myr | Nov 2002 | B1 |
| 6487305 | Kambe et al. | Nov 2002 | B2 |
| 6496189 | Yaron et al. | Dec 2002 | B1 |
| 6526335 | Treyz et al. | Feb 2003 | B1 |
| 6538655 | Kubota | Mar 2003 | B1 |
| 6539300 | Myr | Mar 2003 | B2 |
| 6577946 | Myr | Jun 2003 | B2 |
| 6587784 | Okude et al. | Jul 2003 | B1 |
| 6597354 | Sakamoto et al. | Jul 2003 | B2 |
| 6597654 | Tosaki et al. | Jul 2003 | B2 |
| 6598016 | Zavoli et al. | Jul 2003 | B1 |
| 6600654 | Loebach | Jul 2003 | B2 |
| 6611753 | Millington | Aug 2003 | B1 |
| 6615130 | Myr | Sep 2003 | B2 |
| 6654024 | Voelkel | Nov 2003 | B1 |
| 6693564 | Niitsuma | Feb 2004 | B2 |
| 6704645 | Beesley et al. | Mar 2004 | B1 |
| 6710774 | Kawasaki et al. | Mar 2004 | B1 |
| 6792349 | Chen et al. | Sep 2004 | B1 |
| 6891525 | Ogoro | May 2005 | B2 |
| 6972757 | Arikawa et al. | Dec 2005 | B2 |
| 7054742 | Khavakh et al. | May 2006 | B2 |
| 7054745 | Couckuyt et al. | May 2006 | B1 |
| 7065448 | Gearhart | Jun 2006 | B1 |
| 7119819 | Robertson et al. | Oct 2006 | B1 |
| 7148908 | Riek et al. | Dec 2006 | B2 |
| 7149625 | Mathews et al. | Dec 2006 | B2 |
| 7158876 | Crook | Jan 2007 | B2 |
| 7194356 | Sano | Mar 2007 | B2 |
| 7242966 | Averkamp | Jul 2007 | B1 |
| 7373244 | Kreft | May 2008 | B2 |
| 7379811 | Rasmussen et al. | May 2008 | B2 |
| 7392133 | Maruyama et al. | Jun 2008 | B2 |
| 7413211 | Hendry et al. | Aug 2008 | B2 |
| 7433780 | Machino | Oct 2008 | B2 |
| 7437279 | Agrawala et al. | Oct 2008 | B2 |
| 7440875 | Cuthbert et al. | Oct 2008 | B2 |
| 7460565 | Dally et al. | Dec 2008 | B2 |
| 7460953 | Herbst et al. | Dec 2008 | B2 |
| 7467356 | Gettman et al. | Dec 2008 | B2 |
| 7480565 | Ikeuchi et al. | Jan 2009 | B2 |
| 7539606 | Comair et al. | May 2009 | B2 |
| 7542882 | Agrawala et al. | Jun 2009 | B2 |
| 7551172 | Yaron et al. | Jun 2009 | B2 |
| 7561169 | Carroll | Jul 2009 | B2 |
| 7589732 | Burtnyk et al. | Sep 2009 | B2 |
| 7620494 | Matthews et al. | Nov 2009 | B1 |
| 7623965 | Green | Nov 2009 | B2 |
| 7634352 | Soulchin et al. | Dec 2009 | B2 |
| 7692658 | Moore | Apr 2010 | B2 |
| 7697027 | McMahon et al. | Apr 2010 | B2 |
| 7698063 | Kim | Apr 2010 | B2 |
| 7701434 | Kreek et al. | Apr 2010 | B2 |
| 7702456 | Singh | Apr 2010 | B2 |
| 7706973 | McBride et al. | Apr 2010 | B2 |
| 7729854 | Muramatsu | Jun 2010 | B2 |
| 7734415 | Oumi et al. | Jun 2010 | B2 |
| 7743337 | Maeda et al. | Jun 2010 | B1 |
| 7746343 | Charaniya et al. | Jun 2010 | B1 |
| 7761227 | Kropp | Jul 2010 | B2 |
| 7830243 | Buckley et al. | Nov 2010 | B2 |
| 7831433 | Belvin et al. | Nov 2010 | B1 |
| 7831917 | Karam | Nov 2010 | B1 |
| 7860645 | Kim et al. | Dec 2010 | B2 |
| 7865306 | Mays | Jan 2011 | B2 |
| 7917285 | Rothschild | Mar 2011 | B2 |
| 7917288 | Cheung et al. | Mar 2011 | B2 |
| 7925427 | Zehler | Apr 2011 | B2 |
| 7933395 | Bailly et al. | Apr 2011 | B1 |
| 7945546 | Bliss et al. | May 2011 | B2 |
| 7949546 | Klieman et al. | May 2011 | B1 |
| 7957871 | Echeruo | Jun 2011 | B1 |
| 8010407 | Santoro et al. | Aug 2011 | B1 |
| 8031164 | Herz et al. | Oct 2011 | B2 |
| 8041503 | Choi et al. | Oct 2011 | B2 |
| 8102253 | Brady, Jr. | Jan 2012 | B1 |
| 8103440 | Sengoku et al. | Jan 2012 | B2 |
| 8103445 | Smith et al. | Jan 2012 | B2 |
| 8111258 | Ajioka et al. | Feb 2012 | B2 |
| 8115764 | Kameda et al. | Feb 2012 | B2 |
| 8151210 | Nezu et al. | Apr 2012 | B2 |
| 8190326 | Nezu et al. | May 2012 | B2 |
| 8195383 | Wipplinger et al. | Jun 2012 | B2 |
| 8200847 | Lebeau et al. | Jun 2012 | B2 |
| 8214142 | Cerecke et al. | Jul 2012 | B2 |
| 8237713 | Yaron et al. | Aug 2012 | B2 |
| 8237745 | Cornell et al. | Aug 2012 | B1 |
| 8249259 | Marumoto et al. | Aug 2012 | B2 |
| 8274524 | Cornell et al. | Sep 2012 | B1 |
| 8301371 | Sheha et al. | Oct 2012 | B2 |
| 8301378 | Nishibashi et al. | Oct 2012 | B2 |
| 8306730 | Nishibashi et al. | Nov 2012 | B2 |
| 8321126 | Mays | Nov 2012 | B2 |
| 8326444 | Classen et al. | Dec 2012 | B1 |
| 8335642 | Wipplinger et al. | Dec 2012 | B2 |
| 8335675 | Diverdi et al. | Dec 2012 | B1 |
| 8339403 | Zhao et al. | Dec 2012 | B2 |
| 8339990 | Tzamaloukas | Dec 2012 | B1 |
| 8355862 | Matas et al. | Jan 2013 | B2 |
| 8359389 | Cohen et al. | Jan 2013 | B1 |
| 8364398 | Rossio et al. | Jan 2013 | B2 |
| 8370060 | Rossio et al. | Feb 2013 | B2 |
| 8375325 | Wuttke | Feb 2013 | B2 |
| 8411087 | Wei et al. | Apr 2013 | B2 |
| 8428871 | Matthews et al. | Apr 2013 | B1 |
| 8438481 | Lau et al. | May 2013 | B2 |
| 8463289 | Shklarski et al. | Jun 2013 | B2 |
| 8464182 | Blumenberg et al. | Jun 2013 | B2 |
| 8489641 | Seefeld et al. | Jul 2013 | B1 |
| 8498812 | Ren et al. | Jul 2013 | B2 |
| 8515667 | Haatainen | Aug 2013 | B2 |
| 8515766 | Bringert et al. | Aug 2013 | B1 |
| 8583373 | Hicks | Nov 2013 | B2 |
| 8589069 | Lehman | Nov 2013 | B1 |
| 8589075 | Jones | Nov 2013 | B1 |
| 8595014 | Rychlik | Nov 2013 | B2 |
| 8600654 | Kishikawa et al. | Dec 2013 | B2 |
| 8606514 | Rowley et al. | Dec 2013 | B2 |
| 8606516 | Vertelney et al. | Dec 2013 | B2 |
| 8607167 | Matas et al. | Dec 2013 | B2 |
| 8612151 | Winkler et al. | Dec 2013 | B2 |
| 8635019 | Tertoolen | Jan 2014 | B2 |
| 8639654 | Vervaet et al. | Jan 2014 | B2 |
| 8645056 | Wipplinger et al. | Feb 2014 | B2 |
| 8645366 | Acharya | Feb 2014 | B1 |
| 8665112 | Chen | Mar 2014 | B2 |
| 8665278 | Zhao et al. | Mar 2014 | B2 |
| 8667562 | Lebeau et al. | Mar 2014 | B2 |
| 8676466 | Mudalige | Mar 2014 | B2 |
| 8681176 | Maurer et al. | Mar 2014 | B1 |
| 8694242 | Nagase | Apr 2014 | B2 |
| 8705892 | Aguilera et al. | Apr 2014 | B2 |
| 8738284 | Jones | May 2014 | B1 |
| 8739070 | Mullen | May 2014 | B2 |
| 8762048 | Kosseifi et al. | Jun 2014 | B2 |
| 8774470 | Schmidt et al. | Jul 2014 | B1 |
| 8798918 | Onishi et al. | Aug 2014 | B2 |
| 8818618 | Follmer et al. | Aug 2014 | B2 |
| 8825403 | Kadous et al. | Sep 2014 | B1 |
| 8849564 | Mutoh | Sep 2014 | B2 |
| 8880345 | Kazama et al. | Nov 2014 | B2 |
| 8880568 | Perczynski et al. | Nov 2014 | B2 |
| 8890863 | Lininger | Nov 2014 | B1 |
| 8933960 | Lindahl et al. | Jan 2015 | B2 |
| 8963702 | Follmer et al. | Feb 2015 | B2 |
| 8970592 | Petterson | Mar 2015 | B1 |
| 8983778 | McCarthy | Mar 2015 | B2 |
| 9043150 | Forstall et al. | May 2015 | B2 |
| 9052197 | Van et al. | Jun 2015 | B2 |
| 9147286 | Piemonte et al. | Sep 2015 | B2 |
| 9159153 | Chen et al. | Oct 2015 | B2 |
| 9212918 | Newlin et al. | Dec 2015 | B1 |
| 9230556 | Van et al. | Jan 2016 | B2 |
| 9243924 | Van et al. | Jan 2016 | B2 |
| 9250092 | Blumenberg et al. | Feb 2016 | B2 |
| 9266536 | Loria et al. | Feb 2016 | B2 |
| 9304008 | Poppen et al. | Apr 2016 | B2 |
| 9367959 | Forstall et al. | Jun 2016 | B2 |
| 9418672 | Pylappan et al. | Aug 2016 | B2 |
| 9465890 | Wilson | Oct 2016 | B1 |
| 9466127 | Lindahl et al. | Oct 2016 | B2 |
| 9588987 | Wailes et al. | Mar 2017 | B2 |
| 9741149 | Myung et al. | Aug 2017 | B2 |
| 20010028350 | Matsuoka et al. | Oct 2001 | A1 |
| 20010056325 | Pu et al. | Dec 2001 | A1 |
| 20020010655 | Kjallstrom | Jan 2002 | A1 |
| 20020059296 | Hayashi et al. | May 2002 | A1 |
| 20020103599 | Sugiyama et al. | Aug 2002 | A1 |
| 20020156556 | Ruffner | Oct 2002 | A1 |
| 20020156572 | Bullock et al. | Oct 2002 | A1 |
| 20020164998 | Younis | Nov 2002 | A1 |
| 20030016850 | Kaufman et al. | Jan 2003 | A1 |
| 20030018427 | Yokota et al. | Jan 2003 | A1 |
| 20030023350 | Tan et al. | Jan 2003 | A1 |
| 20030040864 | Stein | Feb 2003 | A1 |
| 20030083851 | Nagamune | May 2003 | A1 |
| 20030109266 | Rafiah et al. | Jun 2003 | A1 |
| 20030137515 | Cederwall et al. | Jul 2003 | A1 |
| 20030154079 | Ota et al. | Aug 2003 | A1 |
| 20030182183 | Pribe | Sep 2003 | A1 |
| 20030231190 | Jawerth et al. | Dec 2003 | A1 |
| 20040001114 | Fuchs et al. | Jan 2004 | A1 |
| 20040024524 | Miyazawa | Feb 2004 | A1 |
| 20040046600 | Fujimoto et al. | Mar 2004 | A1 |
| 20040048600 | Madour et al. | Mar 2004 | A1 |
| 20040048620 | Nakahara et al. | Mar 2004 | A1 |
| 20040070602 | Kobuya et al. | Apr 2004 | A1 |
| 20040128066 | Kudo et al. | Jul 2004 | A1 |
| 20040158395 | Yamada et al. | Aug 2004 | A1 |
| 20040169653 | Endo et al. | Sep 2004 | A1 |
| 20040172418 | Dorum et al. | Sep 2004 | A1 |
| 20040176908 | Senda et al. | Sep 2004 | A1 |
| 20040204840 | Hashima et al. | Oct 2004 | A1 |
| 20040212627 | Sumizawa et al. | Oct 2004 | A1 |
| 20040212827 | Otsuji et al. | Oct 2004 | A1 |
| 20040215389 | Hirose | Oct 2004 | A1 |
| 20040236498 | Le et al. | Nov 2004 | A1 |
| 20040236507 | Maruyama et al. | Nov 2004 | A1 |
| 20040257363 | Veach | Dec 2004 | A1 |
| 20050027705 | Sadri et al. | Feb 2005 | A1 |
| 20050049786 | Odachi | Mar 2005 | A1 |
| 20050055159 | Song et al. | Mar 2005 | A1 |
| 20050107993 | Cuthbert et al. | May 2005 | A1 |
| 20050125148 | Van et al. | Jun 2005 | A1 |
| 20050131631 | Nakano et al. | Jun 2005 | A1 |
| 20050137791 | Agrawala et al. | Jun 2005 | A1 |
| 20050143914 | Yamada et al. | Jun 2005 | A1 |
| 20050149261 | Lee et al. | Jul 2005 | A9 |
| 20050159945 | Otsuka et al. | Jul 2005 | A1 |
| 20050177305 | Han | Aug 2005 | A1 |
| 20050222760 | Cabral et al. | Oct 2005 | A1 |
| 20050228553 | Tryon | Oct 2005 | A1 |
| 20050243104 | Kinghorn | Nov 2005 | A1 |
| 20050251331 | Kreft | Nov 2005 | A1 |
| 20050273251 | Nix et al. | Dec 2005 | A1 |
| 20050273252 | Nix et al. | Dec 2005 | A1 |
| 20060015246 | Hui | Jan 2006 | A1 |
| 20060015249 | Gieseke | Jan 2006 | A1 |
| 20060025923 | Dotan et al. | Feb 2006 | A1 |
| 20060026521 | Hotelling et al. | Feb 2006 | A1 |
| 20060031786 | Hillis et al. | Feb 2006 | A1 |
| 20060041372 | Kubota et al. | Feb 2006 | A1 |
| 20060041379 | Brulle-Drews | Feb 2006 | A1 |
| 20060058849 | Chen et al. | Mar 2006 | A1 |
| 20060058949 | Fogel et al. | Mar 2006 | A1 |
| 20060074553 | Foo | Apr 2006 | A1 |
| 20060122872 | Stevens et al. | Jun 2006 | A1 |
| 20060135259 | Nancke-Krogh et al. | Jun 2006 | A1 |
| 20060161440 | Nakayama et al. | Jul 2006 | A1 |
| 20060184323 | Park | Aug 2006 | A1 |
| 20060195255 | Kim | Aug 2006 | A1 |
| 20060195257 | Nakamura | Aug 2006 | A1 |
| 20060195259 | Pinkus et al. | Aug 2006 | A1 |
| 20060217879 | Ikeuchi et al. | Sep 2006 | A1 |
| 20060224316 | Ishida et al. | Oct 2006 | A1 |
| 20060247845 | Cera et al. | Nov 2006 | A1 |
| 20060253245 | Cera et al. | Nov 2006 | A1 |
| 20060270025 | Zarur et al. | Nov 2006 | A1 |
| 20060284879 | Nagata et al. | Dec 2006 | A1 |
| 20060285743 | Oh et al. | Dec 2006 | A1 |
| 20060287818 | Okude et al. | Dec 2006 | A1 |
| 20070032912 | Jung et al. | Feb 2007 | A1 |
| 20070061071 | Torii | Mar 2007 | A1 |
| 20070076137 | Chiang | Apr 2007 | A1 |
| 20070080830 | Sacks | Apr 2007 | A1 |
| 20070088502 | Oumi et al. | Apr 2007 | A1 |
| 20070088897 | Wailes et al. | Apr 2007 | A1 |
| 20070140187 | Rokusek et al. | Jun 2007 | A1 |
| 20070150179 | Pinkus et al. | Jun 2007 | A1 |
| 20070150842 | Chaudhri et al. | Jun 2007 | A1 |
| 20070174006 | Kusumoto | Jul 2007 | A1 |
| 20070185650 | Yokota et al. | Aug 2007 | A1 |
| 20070192020 | Brulle-Drews et al. | Aug 2007 | A1 |
| 20070195089 | Furukado | Aug 2007 | A1 |
| 20070200674 | Moore et al. | Aug 2007 | A1 |
| 20070208502 | Sakamoto et al. | Sep 2007 | A1 |
| 20070208719 | Tran | Sep 2007 | A1 |
| 20070213092 | Geelen | Sep 2007 | A1 |
| 20070219706 | Sheynblat | Sep 2007 | A1 |
| 20070219718 | Pennock et al. | Sep 2007 | A1 |
| 20070233371 | Stoschek et al. | Oct 2007 | A1 |
| 20070245245 | Blue et al. | Oct 2007 | A1 |
| 20070265772 | Geelen | Nov 2007 | A1 |
| 20070273624 | Geelen | Nov 2007 | A1 |
| 20070273712 | O'Mullan et al. | Nov 2007 | A1 |
| 20070276596 | Solomon | Nov 2007 | A1 |
| 20070276597 | Kato et al. | Nov 2007 | A1 |
| 20070293958 | Stehle et al. | Dec 2007 | A1 |
| 20080016145 | Takase et al. | Jan 2008 | A1 |
| 20080032663 | Doyle | Feb 2008 | A1 |
| 20080040024 | Silva | Feb 2008 | A1 |
| 20080059061 | Lee | Mar 2008 | A1 |
| 20080059889 | Parker et al. | Mar 2008 | A1 |
| 20080062126 | Algreatly | Mar 2008 | A1 |
| 20080062173 | Tashiro | Mar 2008 | A1 |
| 20080068221 | Park | Mar 2008 | A1 |
| 20080068223 | Behr et al. | Mar 2008 | A1 |
| 20080077324 | Hatano et al. | Mar 2008 | A1 |
| 20080082225 | Barrett | Apr 2008 | A1 |
| 20080086356 | Glassman et al. | Apr 2008 | A1 |
| 20080091344 | Mikuriya et al. | Apr 2008 | A1 |
| 20080109404 | Holm | May 2008 | A1 |
| 20080114534 | Yamazaki et al. | May 2008 | A1 |
| 20080114541 | Shintani et al. | May 2008 | A1 |
| 20080122796 | Jobs et al. | May 2008 | A1 |
| 20080133124 | Sarkeshik | Jun 2008 | A1 |
| 20080140314 | Park | Jun 2008 | A1 |
| 20080154489 | Kaneda et al. | Jun 2008 | A1 |
| 20080167798 | Tertoolen | Jul 2008 | A1 |
| 20080167801 | Geelen et al. | Jul 2008 | A1 |
| 20080168396 | Matas et al. | Jul 2008 | A1 |
| 20080168398 | Geelen et al. | Jul 2008 | A1 |
| 20080171559 | Frank et al. | Jul 2008 | A1 |
| 20080174570 | Jobs et al. | Jul 2008 | A1 |
| 20080195307 | Raynaud et al. | Aug 2008 | A1 |
| 20080195638 | Winberry et al. | Aug 2008 | A1 |
| 20080198158 | Iwamura et al. | Aug 2008 | A1 |
| 20080204462 | Reed et al. | Aug 2008 | A1 |
| 20080208450 | Katzer | Aug 2008 | A1 |
| 20080215234 | Geelen | Sep 2008 | A1 |
| 20080228393 | Geelen et al. | Sep 2008 | A1 |
| 20080238941 | Kinnan et al. | Oct 2008 | A1 |
| 20080270025 | Wlotzka | Oct 2008 | A1 |
| 20080288884 | Daughtrey | Nov 2008 | A1 |
| 20080320419 | Matas | Dec 2008 | A1 |
| 20090005981 | Forstall et al. | Jan 2009 | A1 |
| 20090012708 | Wu et al. | Jan 2009 | A1 |
| 20090018764 | Ishibashi et al. | Jan 2009 | A1 |
| 20090028440 | Elangovan et al. | Jan 2009 | A1 |
| 20090037094 | Schmidt | Feb 2009 | A1 |
| 20090040240 | Grotjohn et al. | Feb 2009 | A1 |
| 20090043491 | Haatainen | Feb 2009 | A1 |
| 20090063041 | Hirose et al. | Mar 2009 | A1 |
| 20090063048 | Tsuji | Mar 2009 | A1 |
| 20090064014 | Nelson et al. | Mar 2009 | A1 |
| 20090074249 | Moed et al. | Mar 2009 | A1 |
| 20090082960 | Ramaswamy et al. | Mar 2009 | A1 |
| 20090093957 | Se | Apr 2009 | A1 |
| 20090096753 | Lim | Apr 2009 | A1 |
| 20090100018 | Roberts | Apr 2009 | A1 |
| 20090100342 | Jakobson | Apr 2009 | A1 |
| 20090105944 | Urano et al. | Apr 2009 | A1 |
| 20090119001 | Moussaeiff et al. | May 2009 | A1 |
| 20090143977 | Beletski et al. | Jun 2009 | A1 |
| 20090150373 | Davis et al. | Jun 2009 | A1 |
| 20090154666 | Rios et al. | Jun 2009 | A1 |
| 20090156234 | Sako et al. | Jun 2009 | A1 |
| 20090164115 | Kosakowski et al. | Jun 2009 | A1 |
| 20090171561 | Geelen | Jul 2009 | A1 |
| 20090171575 | Kim et al. | Jul 2009 | A1 |
| 20090171577 | Roumeliotis et al. | Jul 2009 | A1 |
| 20090171578 | Kim et al. | Jul 2009 | A1 |
| 20090171580 | Nezu | Jul 2009 | A1 |
| 20090177385 | Matas et al. | Jul 2009 | A1 |
| 20090181650 | Dicke | Jul 2009 | A1 |
| 20090182497 | Hagiwara | Jul 2009 | A1 |
| 20090187335 | Muhlfelder et al. | Jul 2009 | A1 |
| 20090198767 | Jakobson et al. | Aug 2009 | A1 |
| 20090207121 | Shih et al. | Aug 2009 | A1 |
| 20090216434 | Panganiban et al. | Aug 2009 | A1 |
| 20090216442 | Luert | Aug 2009 | A1 |
| 20090222199 | Nishiura | Sep 2009 | A1 |
| 20090228195 | Lutz et al. | Sep 2009 | A1 |
| 20090228841 | Hildreth | Sep 2009 | A1 |
| 20090237510 | Chen et al. | Sep 2009 | A1 |
| 20090244100 | Schwegler et al. | Oct 2009 | A1 |
| 20090248420 | Basir et al. | Oct 2009 | A1 |
| 20090254273 | Gill et al. | Oct 2009 | A1 |
| 20090262117 | Soulchin et al. | Oct 2009 | A1 |
| 20090267954 | Cupps | Oct 2009 | A1 |
| 20090273601 | Kim | Nov 2009 | A1 |
| 20090284478 | De et al. | Nov 2009 | A1 |
| 20090287408 | Gerdes et al. | Nov 2009 | A1 |
| 20090305742 | Caballero et al. | Dec 2009 | A1 |
| 20090306891 | Jeon et al. | Dec 2009 | A1 |
| 20090312942 | Froeberg | Dec 2009 | A1 |
| 20090326803 | Neef et al. | Dec 2009 | A1 |
| 20090326810 | Callaghan et al. | Dec 2009 | A1 |
| 20090327947 | Schreiner et al. | Dec 2009 | A1 |
| 20100002007 | Rajagopalan | Jan 2010 | A1 |
| 20100004852 | Kawamura | Jan 2010 | A1 |
| 20100017110 | Sengoku et al. | Jan 2010 | A1 |
| 20100030578 | Siddique et al. | Feb 2010 | A1 |
| 20100045703 | Kornmann et al. | Feb 2010 | A1 |
| 20100045704 | Kim | Feb 2010 | A1 |
| 20100057358 | Winer et al. | Mar 2010 | A1 |
| 20100074538 | Mishra et al. | Mar 2010 | A1 |
| 20100094533 | Wu | Apr 2010 | A1 |
| 20100100310 | Eich et al. | Apr 2010 | A1 |
| 20100100317 | Jones et al. | Apr 2010 | A1 |
| 20100104174 | Rohlf et al. | Apr 2010 | A1 |
| 20100110314 | Kusano | May 2010 | A1 |
| 20100115030 | Hong et al. | May 2010 | A1 |
| 20100118065 | Song et al. | May 2010 | A1 |
| 20100120471 | Uchikawa et al. | May 2010 | A1 |
| 20100123737 | Williamson et al. | May 2010 | A1 |
| 20100125386 | Ibrahim | May 2010 | A1 |
| 20100125410 | Hicks | May 2010 | A1 |
| 20100131189 | Geelen et al. | May 2010 | A1 |
| 20100134425 | Storrusten | Jun 2010 | A1 |
| 20100146436 | Jakobson et al. | Jun 2010 | A1 |
| 20100153010 | Huang | Jun 2010 | A1 |
| 20100185382 | Barker et al. | Jul 2010 | A1 |
| 20100190513 | Andreasson | Jul 2010 | A1 |
| 20100205060 | Athsani et al. | Aug 2010 | A1 |
| 20100207751 | Follmer et al. | Aug 2010 | A1 |
| 20100211199 | Naik et al. | Aug 2010 | A1 |
| 20100211632 | Saarinen | Aug 2010 | A1 |
| 20100225644 | Swope et al. | Sep 2010 | A1 |
| 20100232626 | Paquier et al. | Sep 2010 | A1 |
| 20100246889 | Nara et al. | Sep 2010 | A1 |
| 20100250536 | Broadbent | Sep 2010 | A1 |
| 20100253549 | Kim et al. | Oct 2010 | A1 |
| 20100256902 | Coch | Oct 2010 | A1 |
| 20100266161 | Kmiecik et al. | Oct 2010 | A1 |
| 20100280853 | Petralia et al. | Nov 2010 | A1 |
| 20100287024 | Ward et al. | Nov 2010 | A1 |
| 20100306191 | Lebeau et al. | Dec 2010 | A1 |
| 20100306659 | Shahine et al. | Dec 2010 | A1 |
| 20100309149 | Blumenberg et al. | Dec 2010 | A1 |
| 20100312466 | Katzer et al. | Dec 2010 | A1 |
| 20100312468 | Withanawasam | Dec 2010 | A1 |
| 20100313146 | Nielsen et al. | Dec 2010 | A1 |
| 20100324816 | Highstrom et al. | Dec 2010 | A1 |
| 20100324817 | Hansen et al. | Dec 2010 | A1 |
| 20100325104 | Kawauchi | Dec 2010 | A1 |
| 20100325194 | Williamson et al. | Dec 2010 | A1 |
| 20100328100 | Fujiwara et al. | Dec 2010 | A1 |
| 20100328316 | Stroila et al. | Dec 2010 | A1 |
| 20100332468 | Cantrell | Dec 2010 | A1 |
| 20110004589 | Rischar et al. | Jan 2011 | A1 |
| 20110006190 | Alameh et al. | Jan 2011 | A1 |
| 20110007000 | Lim | Jan 2011 | A1 |
| 20110022393 | Waeller et al. | Jan 2011 | A1 |
| 20110054772 | Rossio et al. | Mar 2011 | A1 |
| 20110055065 | Brenner | Mar 2011 | A1 |
| 20110055187 | Cai et al. | Mar 2011 | A1 |
| 20110060523 | Baron | Mar 2011 | A1 |
| 20110077852 | Ragavan et al. | Mar 2011 | A1 |
| 20110081889 | Gao et al. | Apr 2011 | A1 |
| 20110082616 | Small et al. | Apr 2011 | A1 |
| 20110083167 | Carpenter et al. | Apr 2011 | A1 |
| 20110098917 | Lebeau et al. | Apr 2011 | A1 |
| 20110098918 | Siliski et al. | Apr 2011 | A1 |
| 20110106439 | Huang et al. | May 2011 | A1 |
| 20110106534 | Lebeau et al. | May 2011 | A1 |
| 20110106595 | Vande Velde | May 2011 | A1 |
| 20110112750 | Lukassen | May 2011 | A1 |
| 20110112762 | Gruijters et al. | May 2011 | A1 |
| 20110118971 | Petzold et al. | May 2011 | A1 |
| 20110122126 | Han et al. | May 2011 | A1 |
| 20110130949 | Arrasvuori | Jun 2011 | A1 |
| 20110131376 | Fischer | Jun 2011 | A1 |
| 20110131500 | Ohazama | Jun 2011 | A1 |
| 20110137561 | Kankainen | Jun 2011 | A1 |
| 20110144904 | Pinkus et al. | Jun 2011 | A1 |
| 20110153186 | Jakobson | Jun 2011 | A1 |
| 20110159844 | Gillet et al. | Jun 2011 | A1 |
| 20110161843 | Bennett et al. | Jun 2011 | A1 |
| 20110163874 | Van Os | Jul 2011 | A1 |
| 20110164029 | King et al. | Jul 2011 | A1 |
| 20110167058 | Van Os | Jul 2011 | A1 |
| 20110173229 | Choudhury et al. | Jul 2011 | A1 |
| 20110193795 | Seidman et al. | Aug 2011 | A1 |
| 20110196610 | Waldman et al. | Aug 2011 | A1 |
| 20110202862 | Kramer et al. | Aug 2011 | A1 |
| 20110207446 | Iwuchukwu | Aug 2011 | A1 |
| 20110208421 | Sakashita | Aug 2011 | A1 |
| 20110218711 | Mathur et al. | Sep 2011 | A1 |
| 20110231086 | Montealegre et al. | Sep 2011 | A1 |
| 20110246203 | Byrne et al. | Oct 2011 | A1 |
| 20110249030 | Hirose et al. | Oct 2011 | A1 |
| 20110252364 | Anzures et al. | Oct 2011 | A1 |
| 20110264708 | Smartt | Oct 2011 | A1 |
| 20110270517 | Benedetti | Nov 2011 | A1 |
| 20110271230 | Harris et al. | Nov 2011 | A1 |
| 20110276264 | Plocher et al. | Nov 2011 | A1 |
| 20110282567 | Nortrup | Nov 2011 | A1 |
| 20110282759 | Levin et al. | Nov 2011 | A1 |
| 20110285717 | Schmidt et al. | Nov 2011 | A1 |
| 20110289506 | Trivi et al. | Nov 2011 | A1 |
| 20110291860 | Ozaki et al. | Dec 2011 | A1 |
| 20110291863 | Ozaki et al. | Dec 2011 | A1 |
| 20110301728 | Hamilton et al. | Dec 2011 | A1 |
| 20110302527 | Chen et al. | Dec 2011 | A1 |
| 20110313649 | Bales et al. | Dec 2011 | A1 |
| 20120016577 | Kim et al. | Jan 2012 | A1 |
| 20120016678 | Gruber et al. | Jan 2012 | A1 |
| 20120019513 | Fong et al. | Jan 2012 | A1 |
| 20120023097 | Lebeau et al. | Jan 2012 | A1 |
| 20120035924 | Jitkoff et al. | Feb 2012 | A1 |
| 20120036556 | Lebeau et al. | Feb 2012 | A1 |
| 20120041674 | Katzer | Feb 2012 | A1 |
| 20120044243 | Kim et al. | Feb 2012 | A1 |
| 20120047134 | Hansson et al. | Feb 2012 | A1 |
| 20120050489 | Gupta et al. | Mar 2012 | A1 |
| 20120059812 | Bliss et al. | Mar 2012 | A1 |
| 20120060121 | Goldberg et al. | Mar 2012 | A1 |
| 20120062602 | Vadhavana et al. | Mar 2012 | A1 |
| 20120062604 | Lobo et al. | Mar 2012 | A1 |
| 20120078870 | Bazaz | Mar 2012 | A1 |
| 20120081404 | MacLellan et al. | Apr 2012 | A1 |
| 20120084670 | Momchilov | Apr 2012 | A1 |
| 20120092325 | Katano | Apr 2012 | A1 |
| 20120092541 | Tuulos et al. | Apr 2012 | A1 |
| 20120096393 | Shim et al. | Apr 2012 | A1 |
| 20120099804 | Aguilera et al. | Apr 2012 | A1 |
| 20120109509 | Nesbitt et al. | May 2012 | A1 |
| 20120127170 | Varadhan | May 2012 | A1 |
| 20120130625 | Srivastava | May 2012 | A1 |
| 20120143504 | Kalai et al. | Jun 2012 | A1 |
| 20120150428 | Niem et al. | Jun 2012 | A1 |
| 20120158290 | Bharathan et al. | Jun 2012 | A1 |
| 20120159402 | Nurmi et al. | Jun 2012 | A1 |
| 20120162267 | Shimazu | Jun 2012 | A1 |
| 20120166281 | Sartipi | Jun 2012 | A1 |
| 20120197839 | Vervaet et al. | Aug 2012 | A1 |
| 20120198002 | Goulart | Aug 2012 | A1 |
| 20120200604 | Imaeda et al. | Aug 2012 | A1 |
| 20120206367 | Griffin et al. | Aug 2012 | A1 |
| 20120206469 | Hulubei et al. | Aug 2012 | A1 |
| 20120209518 | Nowak et al. | Aug 2012 | A1 |
| 20120214457 | Iaccarino | Aug 2012 | A1 |
| 20120216139 | Ording et al. | Aug 2012 | A1 |
| 20120223845 | Schumann | Sep 2012 | A1 |
| 20120233480 | Tanaka | Sep 2012 | A1 |
| 20120245849 | Spindler et al. | Sep 2012 | A1 |
| 20120249343 | Thomas | Oct 2012 | A1 |
| 20120253659 | Pu et al. | Oct 2012 | A1 |
| 20120254804 | Sheha et al. | Oct 2012 | A1 |
| 20120259539 | Sumizawa | Oct 2012 | A1 |
| 20120259541 | Downey et al. | Oct 2012 | A1 |
| 20120262592 | Rabii | Oct 2012 | A1 |
| 20120265433 | Viola et al. | Oct 2012 | A1 |
| 20120284247 | Jiang et al. | Nov 2012 | A1 |
| 20120284297 | Aguera-Arcas | Nov 2012 | A1 |
| 20120287114 | Hallock et al. | Nov 2012 | A1 |
| 20120290972 | Yook et al. | Nov 2012 | A1 |
| 20120303263 | Alam et al. | Nov 2012 | A1 |
| 20120303268 | Su et al. | Nov 2012 | A1 |
| 20120311438 | Cranfill et al. | Dec 2012 | A1 |
| 20120314040 | Kopf et al. | Dec 2012 | A1 |
| 20120316774 | Yariv et al. | Dec 2012 | A1 |
| 20120316780 | Huth | Dec 2012 | A1 |
| 20120316955 | Panguluri et al. | Dec 2012 | A1 |
| 20120322458 | Shklarski et al. | Dec 2012 | A1 |
| 20130006775 | Jordan et al. | Jan 2013 | A1 |
| 20130018867 | Regan et al. | Jan 2013 | A1 |
| 20130021382 | Morlock et al. | Jan 2013 | A1 |
| 20130030954 | Liu et al. | Jan 2013 | A1 |
| 20130035853 | Stout et al. | Feb 2013 | A1 |
| 20130046456 | Scofield et al. | Feb 2013 | A1 |
| 20130046967 | Fullerton et al. | Feb 2013 | A1 |
| 20130069987 | Choe | Mar 2013 | A1 |
| 20130076249 | Chuang et al. | Mar 2013 | A1 |
| 20130076784 | Maurer et al. | Mar 2013 | A1 |
| 20130078784 | Minamihaba et al. | Mar 2013 | A1 |
| 20130086028 | Hebert | Apr 2013 | A1 |
| 20130110633 | Waldman et al. | May 2013 | A1 |
| 20130132019 | Suzuno | May 2013 | A1 |
| 20130162632 | Varga et al. | Jun 2013 | A1 |
| 20130169579 | Havnor | Jul 2013 | A1 |
| 20130173654 | Lerman et al. | Jul 2013 | A1 |
| 20130176334 | Boldyrev et al. | Jul 2013 | A1 |
| 20130176384 | Jones et al. | Jul 2013 | A1 |
| 20130191020 | Emani et al. | Jul 2013 | A1 |
| 20130218450 | Miyamoto | Aug 2013 | A1 |
| 20130222378 | Koivusalo | Aug 2013 | A1 |
| 20130227473 | Corvo | Aug 2013 | A1 |
| 20130230804 | Sakakibara et al. | Sep 2013 | A1 |
| 20130230840 | Parkar | Sep 2013 | A1 |
| 20130253933 | Maruta | Sep 2013 | A1 |
| 20130261856 | Sharma et al. | Oct 2013 | A1 |
| 20130290400 | Zhou et al. | Oct 2013 | A1 |
| 20130297321 | Raux et al. | Nov 2013 | A1 |
| 20130304373 | Kuo et al. | Nov 2013 | A1 |
| 20130307875 | Anderson | Nov 2013 | A1 |
| 20130321400 | Van et al. | Dec 2013 | A1 |
| 20130321401 | Piemonte et al. | Dec 2013 | A1 |
| 20130321402 | Moore et al. | Dec 2013 | A1 |
| 20130322634 | Bennett et al. | Dec 2013 | A1 |
| 20130322665 | Bennett et al. | Dec 2013 | A1 |
| 20130322702 | Piemonte et al. | Dec 2013 | A1 |
| 20130324164 | Vulcano | Dec 2013 | A1 |
| 20130325319 | Moore et al. | Dec 2013 | A1 |
| 20130325339 | McCarthy | Dec 2013 | A1 |
| 20130325340 | Forstall et al. | Dec 2013 | A1 |
| 20130325341 | Van et al. | Dec 2013 | A1 |
| 20130325342 | Pylappan et al. | Dec 2013 | A1 |
| 20130325343 | Blumenberg et al. | Dec 2013 | A1 |
| 20130325481 | Van et al. | Dec 2013 | A1 |
| 20130326380 | Lai et al. | Dec 2013 | A1 |
| 20130326384 | Moore et al. | Dec 2013 | A1 |
| 20130326407 | Van et al. | Dec 2013 | A1 |
| 20130326425 | Forstall et al. | Dec 2013 | A1 |
| 20130326467 | Nair et al. | Dec 2013 | A1 |
| 20130328861 | Arikan et al. | Dec 2013 | A1 |
| 20130328862 | Piemonte | Dec 2013 | A1 |
| 20130328871 | Piemonte et al. | Dec 2013 | A1 |
| 20130328883 | Sethia | Dec 2013 | A1 |
| 20130328915 | Arikan et al. | Dec 2013 | A1 |
| 20130328916 | Arikan et al. | Dec 2013 | A1 |
| 20130328924 | Arikan et al. | Dec 2013 | A1 |
| 20130328937 | Pirwani et al. | Dec 2013 | A1 |
| 20130345959 | Van et al. | Dec 2013 | A1 |
| 20130345962 | Van et al. | Dec 2013 | A1 |
| 20130345975 | Vulcano et al. | Dec 2013 | A1 |
| 20130345980 | Van et al. | Dec 2013 | A1 |
| 20130345981 | Van et al. | Dec 2013 | A1 |
| 20140019036 | Lemay et al. | Jan 2014 | A1 |
| 20140025298 | Spindler et al. | Jan 2014 | A1 |
| 20140025973 | Schillings et al. | Jan 2014 | A1 |
| 20140057683 | Li | Feb 2014 | A1 |
| 20140071119 | Piemonte et al. | Mar 2014 | A1 |
| 20140071130 | Piemonte | Mar 2014 | A1 |
| 20140095066 | Bouillet et al. | Apr 2014 | A1 |
| 20140122911 | Gunn et al. | May 2014 | A1 |
| 20140123062 | Nguyen | May 2014 | A1 |
| 20140152670 | Miyamoto et al. | Jun 2014 | A1 |
| 20140156187 | Goddard | Jun 2014 | A1 |
| 20140221051 | Oguri | Aug 2014 | A1 |
| 20140358438 | Cerny et al. | Dec 2014 | A1 |
| 20150067008 | Kamath et al. | Mar 2015 | A1 |
| 20150142314 | Lemay et al. | May 2015 | A1 |
| 20150149080 | McCarthy | May 2015 | A1 |
| 20150161254 | Boswell | Jun 2015 | A1 |
| 20150300833 | Van et al. | Oct 2015 | A1 |
| 20150323342 | Forstall et al. | Nov 2015 | A1 |
| 20150353082 | Lee et al. | Dec 2015 | A1 |
| 20160028824 | Stenneth et al. | Jan 2016 | A1 |
| 20160055669 | Piemonte et al. | Feb 2016 | A1 |
| 20160084668 | Van et al. | Mar 2016 | A1 |
| 20160161254 | Nakajima et al. | Jun 2016 | A1 |
| 20160216127 | Van et al. | Jul 2016 | A1 |
| 20170038941 | Pylappan et al. | Feb 2017 | A1 |
| 20170052672 | Forstall et al. | Feb 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 2011218683 | Sep 2011 | AU |
| 2013272003 | Dec 2014 | AU |
| 2016213819 | Sep 2016 | AU |
| 1250300 | Apr 2000 | CN |
| 1382960 | Dec 2002 | CN |
| 1484205 | Mar 2004 | CN |
| 1854948 | Nov 2006 | CN |
| 1995917 | Jul 2007 | CN |
| 101097135 | Jan 2008 | CN |
| 101101217 | Jan 2008 | CN |
| 101257787 | Sep 2008 | CN |
| 101349569 | Jan 2009 | CN |
| 101408429 | Apr 2009 | CN |
| 101936740 | Jan 2011 | CN |
| 102211583 | Oct 2011 | CN |
| 102279710 | Dec 2011 | CN |
| 102388406 | Mar 2012 | CN |
| 202204518 | Apr 2012 | CN |
| 102840866 | Dec 2012 | CN |
| 102967304 | Mar 2013 | CN |
| 69628091 | Apr 2004 | DE |
| 69928387 | Aug 2006 | DE |
| 102007022226 | Nov 2008 | DE |
| 102007030226 | Jan 2009 | DE |
| 102008036748 | Oct 2009 | DE |
| 102008053547 | Apr 2010 | DE |
| 0461577 | Dec 1991 | EP |
| 0572129 | Dec 1993 | EP |
| 0822529 | Feb 1998 | EP |
| 1102037 | May 2001 | EP |
| 1626250 | Feb 2006 | EP |
| 1655677 | May 2006 | EP |
| 1788541 | May 2007 | EP |
| 1965172 | Sep 2008 | EP |
| 1995564 | Nov 2008 | EP |
| 2075542 | Jul 2009 | EP |
| 2075543 | Jul 2009 | EP |
| 2080985 | Jul 2009 | EP |
| 2194508 | Jun 2010 | EP |
| 2196892 | Jun 2010 | EP |
| 2213983 | Aug 2010 | EP |
| 2672223 | Dec 2013 | EP |
| 2672225 | Dec 2013 | EP |
| 2672226 | Dec 2013 | EP |
| 2672227 | Dec 2013 | EP |
| 2672228 | Dec 2013 | EP |
| 2672230 | Dec 2013 | EP |
| 2672231 | Dec 2013 | EP |
| 09-292830 | Nov 1997 | JP |
| 11-038868 | Feb 1999 | JP |
| 2001-165670 | Jun 2001 | JP |
| 2002-243480 | Aug 2002 | JP |
| 2007-057857 | Mar 2007 | JP |
| 2008-008838 | Jan 2008 | JP |
| 2008-039731 | Feb 2008 | JP |
| 2008-158842 | Jul 2008 | JP |
| 2009-154647 | Jul 2009 | JP |
| 2009-204590 | Sep 2009 | JP |
| 200424964 | Nov 2004 | TW |
| 200731173 | Aug 2007 | TW |
| 201017110 | May 2010 | TW |
| 8602764 | May 1986 | WO |
| 9843192 | Oct 1998 | WO |
| 2005103624 | Nov 2005 | WO |
| 2006015892 | Feb 2006 | WO |
| 2007056450 | May 2007 | WO |
| 2007101711 | Sep 2007 | WO |
| 2007115221 | Oct 2007 | WO |
| 2008056880 | May 2008 | WO |
| 2009069165 | Jun 2009 | WO |
| 2009115070 | Sep 2009 | WO |
| 2009117820 | Oct 2009 | WO |
| 2009151036 | Dec 2009 | WO |
| 2011025555 | Mar 2011 | WO |
| 2011045861 | Apr 2011 | WO |
| 2011059781 | May 2011 | WO |
| 2011076989 | Jun 2011 | WO |
| 2011084156 | Jul 2011 | WO |
| 2011095602 | Aug 2011 | WO |
| 2011124273 | Oct 2011 | WO |
| 2011141980 | Nov 2011 | WO |
| 2011146141 | Nov 2011 | WO |
| 2011149231 | Dec 2011 | WO |
| 2011151501 | Dec 2011 | WO |
| 2012007745 | Jan 2012 | WO |
| 2012034581 | Mar 2012 | WO |
| 2013018448 | Feb 2013 | WO |
| 2013184348 | Dec 2013 | WO |
| 2013184391 | Dec 2013 | WO |
| 2013184444 | Dec 2013 | WO |
| 2013184445 | Dec 2013 | WO |
| 2013184446 | Dec 2013 | WO |
| 2013184447 | Dec 2013 | WO |
| 2013184448 | Dec 2013 | WO |
| 2013184449 | Dec 2013 | WO |
| 2013184450 | Dec 2013 | WO |
| 2013184472 | Dec 2013 | WO |
| 2013184473 | Dec 2013 | WO |
| 2013184533 | Dec 2013 | WO |
| 2013184534 | Dec 2013 | WO |
| Entry |
|---|
| Author unknown, Maths—Angle between vectors, retrieved from https://web.archive.org/web/20061110112226/http://www.euclideanspace.com/maths/algebra/vectors/angleBetween/index.htm on Aug. 22, 2018, archived from http://www.euclideanspace.com/maths/algebra/vectors/angleBetween/index.htm on Nov. 10, 2006. |
| “Using Search in Google Maps”, Jan. 6, 2011 (Jan. 6, 2011), XP054975742, Retrieved from the Internet: URL:https://www.youtube.com/watch?v=ihlddF T7r3g [retrieved on Feb. 13, 2015]. |
| Springer, Antti Nurminen & Anth Oulasvirta, Designing Interactions for Navigation in 3D Mobile Maps, pp. 198-224, Winter 2008, published in Map-based Mobile Services: Design, Interaction and Usability. |
| SkylineGlobe Web Package, version 6.1, 2012, pp. 1-23. |
| Plvhal, “Google Earth Intro & 3D Buildings”, YouTube, Apr. 12, 2010, 1 page, retrieved on Aug. 9, 2013 from the Internet: https://www.youtube.com/watch?v=rGANAS0XMPA. |
| NATO Science and Technology Organization, Justin G. Hollands & Nada Ivanovic, Task Switching with 2D and 3D Displays of Geographic Terrain: The Role of Visual Momentum, p. 19-6, Sep. 10, 2002, published in RTO-MP-105. |
| Michael Siliski: “Fun on the Autobahn: Google Maps Navigation in 11 more Countries”, Google Mobile Blog, Jun. 9, 2010 (Jun. 9, 2010). |
| Huhtala, J., Sarjanoja, A.H., Mantyjarvi, J., Isomursu, M. and Hakkila, J., Aug. 2009. Mobile screen transition animations. In SIGGRAPH'09: Posters (p. 25). ACM. |
| Google, Google Earth 3D Tour, https://www.youtube.com/watch?v=7Byxke1 Daqk; Jun. 26, 2009. |
| Gareth Beavis: “Google Earth finally coming to Android phones”, Internet, Feb. 23, 2010 (Feb. 23, 2010). |
| YouTube video “Report a Problem with Google Maps” uploaded Oct. 27, 2009 https://www.youtube.com/watch?v=ByVdkytC8RE with screenshots 3 pages. |
| Unknown Author, Blaupunkt chooses NNG navigation software for new aftermarket product, May 24, 2011, telematicsnews.info, retreived from http://telematicsnews.info/2011/05/24/blaupunkt-chooses-nng-navigation-software-or-new-aftermarket-product_my2241/ on Feb 26, 2015. |
| Tauntingpanda, Ripple Effect Test in Unity 3d, https://www.youtube.com/watch?v=OaFfCJwnilM, May 18, 2009. |
| Tamar Weinberg “Move the Map Marker on Google Maps: A Screenshot Tour” Nov. 21, 2007 5 pages. |
| Qureshi, Khurram, “Garmin Nuvi 885T Voice Recognition & Command Demonstration,” Feb. 3, 2010, 1 page, available at http://www.youtube.com/watch?v=OOJKhTN6iMg. |
| Purdy, Kevin, “ChompSMS is a Handy Replacement for Android's SMS App,” Jul. 26, 2010, 10 pages, available at http://lifehacker.com/5596492/chompsms-is-a-handy-replacement-for-androids-sms-app. |
| Poullis, Charalambos, et al., “Delineation and geometric modeling of road networks”, ISPRS Journal of Photogrammetry and Remote Sensing, Month Unknown, 2010, pp. 165-181, vol. 65, Computer Graphics and Immersive Technologies Lab, Integrated Media Systems Center, University of Southern California, United States. |
| Ponderevo, George, “Grayed out”, Wikipedia, the free encyclopedia, Jun. 10, 2011, 2 pages. |
| Partial International Search Report for PCT/US2013/042933, dated Aug. 28, 2013, Apple Inc., Partial International Search Report for commonly owned PCT/US2013/042933. |
| Partala, Timo, et al. “Speed-dependent camera control in 3D mobile roadmaps.” Intelligent Interactive Assistance and Mobile Multimedia Computing. Springer Berlin Heidelberg, 2009. 143-154. |
| Orbitz Staff, The 3-tap app: Orbitz launches free app for iPad users, Jul. 6, 2011. |
| Nurminen, Antti, et al., “10 Designing Interactions for Navigation in 3D Mobile Maps,” Map-Based Mobile Services, Aug. 6, 2008, 31 pages, Springer, Berlin Heidelberg. |
| Magellan RoadMate Reference Manual Instructions for Operating the Magellan RoadMate 860T Copyright 2006 106 pages. |
| Lawrence, Steve, “Review: Sygic Mobile Maps 2009,” Jul. 23, 2009, 4 pages, available at http://www.iphonewzealand.co.nz/2009/all/review-sygic-mobile-maps-2009/. |
| Jiuxiang Hu et al.; “Road Network Extraction and Intersection Detection from Aerial Images by Tracking Road Footprints”; Dec. 2007; IEEE Transactions on Geoscience and Remote Sensing, pp. 4144-4157. |
| Jake Gaecke, Appletell reviews Sygic Mobile Maps 2009 North America for iPhone, Aug. 9, 2009, http://www.technologytell.com/apple/49215/appletell-reviews-sygic-mobile-maps-2009-north-america/. |
| IOS 4.2 user guide manufactured by Apple, Inc, released on Mar. 2011, 274 pages. |
| Invitation to Pay Additional Fees with Partial Search Report for PCT/US2013/043802, dated Oct. 12, 2015, Apple Inc., Invitation to Pay Additional Fees with Partial Search Report for commonly owned International Patent Application PCT/US2013/043802. |
| Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for PCT/US2013/043190, dated Dec. 4, 2013, Apple Inc. |
| Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for PCT/US2013/042945, dated Nov. 29, 2013, Apple Inc. |
| Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for PCT/US2013/042937, dated Nov. 29, 2013, Apple Inc. |
| Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for PCT/US2013/042931. |
| Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for PCT/US2013/042930, dated Nov. 29, 2013, Apple Inc., Invitation to Pay Additional Fees and, Where Applicable, Protest Fee for commonly owned International Patent Application PCT/US2013/042930. |
| International Search Report and Written Opinion of PCT/US2013/042933, dated Mar. 24, 2015, Apple Inc., International Search Report and Written Opinion of commonly owned International Patent Application PCT/US2013/042933, listed in the 1449 filed Feb. 23, 2015. |
| International Search Report and Written Opinion for PCT/US2013/043803, dated Nov. 22, 2013, Apple Inc. |
| International Search Report and Written Opinion for PCT/US2013/043197. |
| International Search Report and Written Opinion for PCT/US2013/043190, dated Feb. 21, 2014, Apple Inc. |
| International Search Report and Written Opinion for PCT/US2013/042945, dated Feb. 21, 2014, Apple Inc. |
| International Search Report and Written Opinion for PCT/US2013/042937, dated Mar. 6, 2014, Apple Inc. |
| International Search Report and Written Opinion for PCT/US2013/042936. |
| International Search Report and Written Opinion for PCT/US2013/042930, dated Feb. 20, 2014, Apple Inc., International Search Report and Written Opinion for commonly owned International Patent Application PCT/US2013/042930, listed in the 1449 dated Dec. 19, 2013. |
| International Search Report and Written Opinion for PCT/US2013/042929. |
| International Search Report and Written Opinion for PCT/US2013/042546, dated Nov. 6, 2013, Apple Inc. |
| International Search Report and Written Opinion for PCT/US2013/042029, dated Jan. 16, 2014, Apple Inc. |
| International Search report and Written Openion for PCT/US2013/042931. |
| International Preliminary Report on Patentability for PCT/US2013/042931, dated Dec. 18, 2014, Apple Inc. |
| International Preliminary Report on Patentability for PCT/US2013/042929. |
| Harrower, Mark, “A Look at the History and Future of Animated Maps”, Cartographica, Sep. 1, 2004, pp. 33-42, vol. 39, No. 3, University of Toronto Press, Canada. |
| Gus Class, “Custom Gestures for 3D Manipulation Using Windows”, Feb. 23, 2011, retrieved from http://www.codeproject.eom/Articles/161464/Custom-Gestures-for-D-Manipulation-Using-Windows on Mar. 16, 2016. |
| Greg Sterling Google Now Enables Maps Users to “Report a Problem” Oct. 8, 2009 4 pages. |
| Google operating System Unofficial news and tips about Google “Edit Locations in Google Maps” Nov. 19, 2007 2 pages. |
| Google Earth Blog Use StreetView to make Points of Interest more precise Mar. 10, 2010 7 pages. |
| Feng Yuten and Haiyan Fan, “Research on Dynamic Water Surface and Rippie Animation,” International Journal of Information Technology and Computer Science (IJITCS) 2,1 (2010): 18. |
| Dube, Ryan, “Use Google Maps Navigation for Turn-By-Turn GPS [Android]”, available at http://www.makeuseof.com/tag/google-maps-navigation-tumbyturn-gps-androi- d/, Jun. 24, 2010, 7 pages. |
| Dave Morg, “Google Navigation 5.3 will not allow the phone to sleep” https://productforums.google.eom/forum/#topic/maps/is54TSBVIUE, (posted Apr. 11, 2011, accessed Aug. 28, 2014). |
| Dal Poz, A.P., et al, “Automated Extraction of Road Network from Medium- and High-Resolution Images,” Pattern Recognition and Image Analysis, Apr.-Jun. 2006, pp. 239-248, vol. 16, No. 2, Pleiades Publishing, Inc. |
| Chris Runs. My Favorite Android Apps: Maps. 2011. [retrieved on Jan. 31, 2014]. Retrieved from the Internet:<URL: http://www,youtube,com/watch?v=v2aRkLkT3s>. entire document. |
| Chitu. More Suggestions in Google Maps. Unofficial news and tips about Google. Blog. Apr. 21, 2010. Retrieved on [Dec. 1, 2013]. Retrieved from the Internet: URL http://googlesystem. blogspot.com/2010/04/more-SuggestionS″ingoogle-maps.html Entire document. |
| Chitu, Alex, “Google Operating System: Unofficial News and Tips about Google”, Apr. 21, 2010, 2 pages, available at http://googlesystem.blogspot.com/2010/04/more-suggestions-in- google-maps.html. |
| Chen, Ching-Chien, et al., “Automatically Conflating Road Vector Data with Orthoimagery,” GeoInformatica, Mar. 2006, pp. 495-530, Springer Science + Business Media, LLC. |
| Haala N, Kada M. Panoramic scenes for texture mapping of 3D city models. International Archives of Photogrammet and Remote Sensing. Feb. 2005;36(Part 5/W8). |
| Rich Brooks How to Write a Review at Google Maps 2009 12 pages. |
| Meghan Kelly Google Maps rolls out business interiors in Street View Oct. 26, 2011 2 pages. |
| Kristi Hines 7 Creative Ways to Get Customer Testimonials, 2011 18 pages. |
| Himanshu Yadav 9 Awesome Google Maps Labs Features You SHould Know About Jun. 21, 2010 8 pages. |
| Greg Sterling New Google Maps Adds More Search Results to Info Window Dec. 3, 2013 6 pages. |
| Global, Touch surface screen with ripple effect at Lisbon's Oceanarium, Mar. 11, 2009, https://www.youtube.com/watch?v=O2b6VSKWPJM. |
| Charalambos Poullis et al.; “Delineation and geometric modeling of road networks”; Nov. 2009; ISPRS Journal of Photogrammetry and Remote Sensing; p. 165-181. |
| Author Unknown,“NILS Lockscreen Notifications,” Apr. 6, 2015, 3 pages, available at https://play.google.com/stores/apps/details?id=com.royman, android notificationswidget&hi=en. |
| Author Unknown, “The Next Generation of Mobile Maps,” availabel at http://googleblog,blogspolcom/2010/12/next-generation-of-mobile-maps,html.Dec. 16, 2010, 5 pages. |
| Author Unknown, Resolve Road Conflicts (Cartography), ARCGIS help 10,1, Nov. 11, 2011, 4 pages, Esn, available at http://help.arcgis.com/en/arcgisdesktop/10.0/help/index,html#11007000000019000000.htm. |
| Author Unknown, “(SC4) Sim City for Highways & Autobahns,” Aug. 12, 2011, pp. 1, 35 available at http://www.skyscrapercity.com/showthread.php?t=639496&page=14. |
| Author Unknown, “Tom Tom GO Live 1005 on the road Re-routing,” PocketGPS, Mar. 8, 2012, 1 page, available at http://www.youtube.com/watch?v=sJf_NOcqoNA. |
| Author Unknown, “Motorola XOOM: Google Maps,” TechHarvest, Feb. 25, 2011, 1 page, available at http://www.youtube.com/watch?v=adkl5zMp7W4. |
| Author Unknown, “Mazda: Navigation System—Owner's Manual”, available at http://download.tomtom.com/open/manuals/mazda/nva-sd8110/Full_Manual_EN.pdf, Jan. 1, 2009, 159 pages. |
| Author Unknown, “Magellan.RTM. RoadMate.RTM. GPS Receiver: 9020/9055 user Manual,” Month Unknown, 2010, 48 pages, MiTAC International Corporation, CA, USA. |
| Author Unknown, “Magellan RoadMate 9020 GPS Receiver 9055 User Manual,” Month Unknown 2010, 48 pages MITAC international Corporation, Santa Clara, USA. |
| Author Unknown, “Magellan RoadMate 2010 North America,” Application User Manual Month Unknown 2009, 24 pages, MITAC international Corporation, Santa, Clara, USA. |
| Author Unknown, “Lux Auto Brightness,” Dec. 26, 2014, 3 pages, available at https://play.google.com/store/apps/details?id=com.vito.lux&hl=en. |
| Author Unknown, “IOS 5: Notifications Center and LockScreen”, Jun. 9, 2011, available at http:///www.youtube.com/watch?v=eurhcjpXHwo. |
| Author Unknown, “Google Maps Voice Navigation in Singapore,” software2tech, Jul. 20, 2011, 1 page, available at http://www.youtube.com/watch?v=7B9JN7BkvME. |
| Author Unknown, “Google Maps—Two Finger Rotate in Nexus One,” androidapk, Apr. 9, 2011, 1 page, available at http://www.youtube.com/watch?v=f7VNoErYNt8. |
| Author Unknown, “Garmin. nuvi 1100/1200/1300/1400 series owner's manual,” Jan., 2011, 72 pages, Garmin Corporation, No. 68, Jangshu 2nd Road, Sijhih, Taipei County, Taiwan. |
| Author Unknown, “chompSMS—Change Log,” Jul. 16, 2010, 29 pages, Delicious, Inc., available at http://chompsms.com/main/changelog. |
| Author Unknown, “Blaupunkt chooses NNG navigation software for new aftermarket product,” May 24, 2011, 2 pages, available at http://telematicsnews.info/2011/05/24/blaupunkt-chooses-nng-navigation-software-for-new-aftermarket-product_my2241/. |
| Author Unknown, “Android 23.4 User's Guide”, May 20, 2011, pp. 1-384, Google, Inc. |
| Author Unknown, “3D Building Features on Google Maps Mobile App with 2 Fingers Tilt, Rotate, Zoom,” adistarone, Jul. 21, 2011, 1 page, available at http://www.youtube.com/watch?v=lqkKK1Xt8W0. |
| Author Unknown, “‘Touch & Go’ Owner's Manual,” Jul. 2011, 218 pages, Toyota, United Kingdom. |
| Assistance and Mobile Multimedia Computing, Month Unknown, 2009, pp. 143-154, Springer Berlin Heidelberg. |
| Android 2.14 User's Guide. Google. May 20, 2011. Retrieved on [Dec. 1, 2013]. Retrieved from the Internet: URL<http://static.google usercontent.com/media/www.google.com/en.us/help/hc/pdfs/mobile/AndroidUsersGuide- 2.3.4.pdf> entire document. |
| Agrawal et al.; “Geometry-based Mapping and Rendering of Vector Data over LOD Phototextured 3D Terrain Models”; 2006, pp. 1-8. |
| Access Ana, “Accessible Android”, http://accessibleandroid.blogspot.com/2010/09/how-do-i-set-or-change-default-home.html (posted Sep. 15, 2010, accessed Sep. 2014). |
| “Topic 2: Map Projections and Coordinates Systems” http://hosting.soonet.ca/eliris/remotesensing/bl130lec2.html. Archived on Sep. 23, 2007. Retrieved on Apr. 20, 2015 from <https://web.archive.Org/web/20070923035156/http://hosting.soonet.ca/eliris/remotesensing/bl130lec2.html>. |
| “Today's Navigation Standard” http://www.casanovasadventures.com/catalog/gps/p3034.htm Archived on Jan 6, 2005. Retrieved on May 28, 2015 from <http://web.archive.Org/web/20050106232808/http://www.casanovasadventures.com/catalog/gps/p3034.htm>. |
| “Google Earth API: Camera Control” https://developers.google.com/earth/documentation/camera_control. Archived on Mar. 26, 2012. Retrieved on May 30, 2015 from <https://web.archive.Org/web/20120326235132/https://developers. google.com/earth/documentation/camera_control>. |
| “Google Earth API” https://developers.google.com/earth/documentation/camera_control. Archived on Mar. 26, 2012. Retrieved on Apr. 20, 2015 from <https://web.archive.Org/web/20120326235132/https://developers.google.com/earth/documentation/camera_control>. |
| “Adaptive ArcGIS Server Tile Cache for Virtual Earth”, published on Jan. 17, 2008, retrieved from http://blog.davebouwman.com/2008/01/17/adaptive-arcgis-server-tile-cache-for-virtual-earth/on Dec. 21, 2015. |
| The Volpe Center “Visualization for Right-of-Way Acquisition” Nov. 2011 63 pages (Year: 2011). |
| Number | Date | Country | |
|---|---|---|---|
| 20180335311 A1 | Nov 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61655995 | Jun 2012 | US | |
| 61655997 | Jun 2012 | US | |
| 61656015 | Jun 2012 | US | |
| 61656032 | Jun 2012 | US | |
| 61656043 | Jun 2012 | US | |
| 61656080 | Jun 2012 | US | |
| 61657864 | Jun 2012 | US | |
| 61657880 | Jun 2012 | US | |
| 61699842 | Sep 2012 | US | |
| 61699855 | Sep 2012 | US | |
| 61699851 | Sep 2012 | US | |
| 61699857 | Sep 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15003607 | Jan 2016 | US |
| Child | 15824526 | US | |
| Parent | 14691523 | Apr 2015 | US |
| Child | 15003607 | US | |
| Parent | 13632120 | Sep 2012 | US |
| Child | 14691523 | US |
