Colloquial or user-favored route based navigation instructions
Claim Score by NHIP
Abstract
A route between start and destination locations is generated, and a navigation device presents navigation instructions to a user describing the route. The navigation instructions can be colloquial navigation instructions, which are instructions that are more humanized (e.g., more conversational in language and format, or consistent with the manner in which people typically talk to one another in familiar or informal conversation). The route that is generated can be based on one or more user-favored routes. A user-favored route is a route between two locations that is determined to be desired, preferred, or otherwise favored by a user over other routes. The route that is generated can be generated to include at least part of one or more user-favored routes.

Term
Projected expiry 12 September 2034.
- Priority and filed
- Published
- Today
- Projected expiry
20 claims: 3 independent, 17 dependent
- 1A method implemented in a navigation device, the method comprising:generating a route between a start location and a destination location;identifying, by analyzing the route, colloquial navigation instructions describing at least part of the route, the colloquial navigation instructions identifying a number of blocks in situations in which locations of roads along the route correspond to city blocks;and presenting the colloquial navigation instructions.
- 12Broadest claimClaim Score 79, broad(NHIP)A method implemented in a navigation device, the method comprising:receiving a request for a route between a start location and a destination location;identifying one or more user-favored routes of a user of the navigation device;generating, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location;and presenting navigation instructions for the route.
- 18A navigation device comprising:a global navigation satellite system, implemented at least in part in hardware, configured to determine a position of the navigation device;a user-favored route based route identification module configured to receive a request for a route between a start location and a destination location, identify one or more user-favored routes of a user of the navigation device, and generate, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location;and a colloquial instruction generation module configured to identify, by analyzing the route, colloquial navigation instructions describing at least part of the route, and play back the colloquial navigation instructions audibly as the user travels along the route.
Independent claims3
103 paragraphs in 4 sections, as filed
BACKGROUND
0001As computing technology has advanced, people have come to increasingly rely on their computing devices for various functionality. One type of functionality people rely on is navigation, such as using dedicated devices or their smartphones to receive instructions in their car to navigate to a destination. Although such functionality is very useful, it is not without its problems. One such problem is that the navigation functionality oftentimes provides instructions that are difficult for users to fully comprehend, or that require additional thought or attention by the user to comprehend, which can be frustrating for users.
SUMMARY
0002This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
0003In accordance with one or more aspects, in a navigation device a route between a start location and a destination location is generated. Colloquial navigation instructions describing at least part of the route are identified by analyzing the route and are presented, the colloquial navigation instructions identifying a number of blocks in situations in which locations of roads along the route correspond to city blocks.
0004In accordance with one or more aspects, in a navigation device a request for a route between a start location and a destination location is received and one or more user-favored routes of a user of the navigation device are identified. A route between the start location and the destination location is generated based on the start location, the destination location, and the one or more user-favored routes, and navigation instructions for the route are presented.
0005In accordance with one or more aspects, a navigation device includes a global navigation satellite system, a user-favored route based route identification module, and a colloquial instruction generation module. The global navigation satellite system, implemented at least in part in hardware, is configured to determine a position of the navigation device. The user-favored route based route identification module is configured to receive a request for a route between a start location and a destination location, identify one or more user-favored routes of a user of the navigation device, and generate, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location. The colloquial instruction generation module is configured to identify, by analyzing the route, colloquial navigation instructions describing at least part of the route, and play back the colloquial navigation instructions audibly as the user travels along the route.
BRIEF DESCRIPTION OF THE DRAWINGS
0006The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.
0007<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example navigation device implementing the colloquial or user-favored route based navigation instructions in accordance with one or more embodiments.
0008<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating an example process for generating and presenting colloquial navigation instructions in accordance with one or more embodiments.
0009<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example of a route and map-related features along the route in accordance with one or more embodiments.
0010<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example user interface presenting colloquial navigation instructions in accordance with one or more embodiments.
0011<figref idref="DRAWINGS">FIG. 5</figref> illustrates an example user interface presenting colloquial navigation instructions and visual aids in accordance with one or more embodiments.
0012<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating an example process for generating routes that are based on one or more other user-favored routes in accordance with one or more embodiments.
0013<figref idref="DRAWINGS">FIGS. 7A</figref>, <b>7</b>B, and <b>7</b>C illustrate an example of generating a route based on one or more user-favored routes in accordance with one or more embodiments.
0014<figref idref="DRAWINGS">FIG. 8</figref> illustrates an example user interface that can be displayed to a user of a device to allow the user to select whether position data for that device will be recorded in accordance with one or more embodiments.
0015<figref idref="DRAWINGS">FIG. 9</figref> illustrates an example system that includes an example computing device that is representative of one or more systems and/or devices that may implement the various techniques described herein.
DETAILED DESCRIPTION
0016Colloquial or user-favored route based navigation instructions are discussed herein. A route between start and destination locations is generated, and navigation instructions are presented to the user as he or she travels along the route. The navigation instructions can be colloquial navigation instructions, which refer to instructions that are humanized (consistent in language and format with the manner in which people typically talk to one another in familiar or informal conversation). For example, rather than an instruction to “turn left in 200 meters”, a colloquial instruction would be to “turn left in 3 blocks”, or “turn right at the second stoplight”. The presentation of colloquial navigation instructions advantageously improves usability of a navigation device by providing navigation instructions that are more consistent with informal conversation and that can typically be comprehended more quickly by the user. For example, users are typically able to more quickly comprehend how far 3 blocks is than 200 meters.
0017Additionally or alternatively, the route that is generated can be based on one or more user-favored routes. A user-favored route refers to a route between two locations that is determined to be desired, preferred, or otherwise favored by the user over other routes. The route that is generated can be generated to include at least part of one or more user-favored routes. Generation of the route to include at least part of one or more user-favored routes advantageously improves usability of a navigation device by providing a route that includes portions of other routes that the user is familiar with, prefers, or otherwise desires or favors.
0018<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram illustrating an example navigation device <b>100</b> implementing the colloquial or user-favored route based navigation instructions in accordance with one or more embodiments. Navigation device <b>100</b> can be a variety of different types of devices, such as a cellular or other wireless phone (e.g., a smartphone), a laptop or netbook computer, a tablet or notepad computer, a phablet computer, a wearable device (e.g., eyeglasses, watch), a mobile station, an entertainment appliance, a dedicated or standalone navigation device, an automotive computer, and so forth. Thus, navigation device <b>100</b> may range from full resource devices with substantial memory and processor resources (e.g., laptop computers, tablet computers) to low-resource devices with limited memory and/or processing resources (e.g., dedicated or standalone navigation devices).
0019Navigation device <b>100</b> includes a user input module <b>102</b>, an output module <b>104</b>, and a navigation system <b>106</b>. The user input module <b>102</b> receives user inputs from a user of the navigation device <b>100</b>. User inputs can be provided in a variety of different manners, such as by pressing one or more keys of a keypad or keyboard of the device <b>100</b>, pressing a particular portion of a touchpad or touchscreen of the device <b>100</b>, making a particular gesture on a touchpad or touchscreen of the device <b>100</b>, an action that can be recognized by a motion detection or other component of the device <b>100</b> (such as shaking the device <b>100</b>, rotating the device <b>100</b>, bending or flexing the device <b>100</b>, etc.), combinations thereof, and so forth. User inputs can also be provided in other manners, such as via voice or other audible inputs to a microphone, via motions of hands or other body parts observed by an image capture device, and so forth.
0020The output module <b>104</b> generates, manages, and/or outputs content for display, playback, and/or other presentation. This content can be created by the output module <b>104</b> or obtained from other modules of the navigation device <b>100</b>. This content can be, for example, a display or audible playback portion of navigation instructions to a particular destination. The content can be displayed or otherwise played back by components of the navigation device <b>100</b> (e.g., speakers, interactive display devices, etc.). Alternatively, the output module <b>104</b> can generate one or more signals that are output to other devices or components (e.g., speakers, display devices, etc.) that are separate from the navigation device <b>100</b> (e.g., speakers in a vehicle in which the navigation device <b>100</b> is situated).
0021The navigation system <b>106</b> includes a Global Navigation Satellite System (GNSS) system <b>112</b>, a colloquial instruction generation module <b>114</b>, and a user-favored route based route identification module <b>116</b>. The GNSS system <b>112</b> implements GNSS functionality for the device <b>100</b>, determining a geographic position of the device <b>100</b> based on one or more satellites from which the GNSS system <b>112</b> can receive signals or otherwise communicate. This determined position is typically latitude and longitude coordinates, although the position can alternatively be specified in other manners. The GNSS system <b>112</b> can implement the GNSS functionality using a variety of different technologies, such as the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou (or Compass) navigation system, the Galileo positioning system, combinations thereof, and so forth. Although illustrated as part of the navigation device <b>100</b>, the GNSS system <b>112</b> can alternatively be situated at least in part separate from the navigation device <b>100</b>. For example, one or more components of the GNSS system <b>112</b> can be implemented by a vehicle in which the navigation device <b>100</b> is situated.
0022The colloquial instruction generation module <b>114</b> generates colloquial navigation instructions. Navigation instructions (also referred to herein as simply instructions) refer to the information presented by the navigation system <b>106</b> along the route to the destination. Colloquial navigation instructions (also referred to as simply colloquial instructions) refer to navigation instructions that are humanized—instructions that are conversational or use language and formats that are consistent with the manner in which people typically converse with one another in familiar or informal conversation. For example, rather than an instruction to turn in 300 meters, a colloquial instruction would be to turn in 3 blocks, or turn at the second stoplight.
0023The navigation instructions, whether colloquial navigation instructions or non-colloquial navigation instructions, include directional guidance to direct a user to the destination, such as information regarding which roads to turn onto, which exits to take, how long until a turn is to be made, directions to make turns, and so forth. The instructions can be presented audibly or in other manners.
0024The user-favored route based route identification module <b>116</b> identifies routes from start locations to destination locations (also referred to as simply the start or destination). The routes are identified based on user-favored routes. A user-favored route refers to a route between two locations that is determined to be desired, preferred, or otherwise favored by a user of the navigation device <b>100</b> over other routes. Favorite routes of the user can be specified by the user (e.g., saved in a “favorites” list) or in other manners as discussed in more detail below.
0025The techniques discussed herein can apply to various different modes of transportation, such as walking, bicycling, vehicle (e.g., in a car or truck), mass transit, and so forth. Although references may be made herein to particular modes of transportation (e.g., roads or driving), it should be noted that the techniques discussed with such references apply analogously to other modes of transportation and other types of paths (e.g., sidewalks or bike paths rather than roads).
0026<figref idref="DRAWINGS">FIG. 2</figref> is a flowchart illustrating an example process <b>200</b> for generating and presenting colloquial navigation instructions in accordance with one or more embodiments. Process <b>200</b> is carried out by a device, such as navigation device <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>, and can be implemented in software, firmware, hardware, or combinations thereof. Process <b>200</b> is shown as a set of acts and is not limited to the order shown for performing the operations of the various acts. Process <b>200</b> is an example process for generating and presenting colloquial navigation instructions; additional discussions of generating and presenting colloquial navigation instructions are included herein with reference to different figures.
0027In process <b>200</b>, a request for a route between a start location and a destination location is received (act <b>202</b>). The request can be received as a user input, or alternatively the request can be received from another component, module, device, and so forth. The start location is typically a current location of the navigation device <b>100</b>, but can alternatively be other locations. The start and destination locations each refer to any geographic position, and can be identified in any of a variety of different manners. For example, a start or destination location can be identified by a user input (e.g., a user input entering an address, selecting a stored or favorite address), by an indication from another component, module, or device, and so forth.
0028A route between the start location and the destination location is determined (act <b>204</b>). The route can be determined using any of a variety of public or proprietary techniques. The route determined in act <b>204</b> can optionally be based on one or more user-favored routes as discussed in more detail below, but need not be based on any user-favored routes.
0029Colloquial navigation instructions describing the determined route are identified (act <b>206</b>). As discussed above, colloquial navigation instructions are instructions that are consistent with the manner in which people typically talk to one another in familiar or informal conversation. By way of example, colloquial navigation instructions give distances in units that people typically give instructions in (e.g., a number of city blocks, a number of intersections), whereas non-colloquial navigation instructions give distances in more formal units (e.g., meters, feet). Generally, the colloquial navigation instructions are generated by analyzing the route and identifying one or more colloquial navigation instructions for presentation (e.g., as the user travels along the route). Colloquial navigation instructions for presentation for the entire route can be generated, or alternatively colloquial navigation instructions for presentation for one or more parts of the route can be generated (and non-colloquial navigation instructions (e.g., turn right in 300 meters) can be generated for presentation for other parts of the route).
0030Colloquial navigation instructions can be generated based on personalization, map characteristics, combinations thereof, and so forth. Personalization refers to using landmarks as a basis for navigation instructions. The navigation system maintains or has access to a set of landmarks and their locations (e.g., geographic coordinates or other location identifiers). A landmark refers to a structure, geological formation, or other object readily identifiable by users. The set of landmarks can include global landmarks, personal landmarks, or a combination thereof. A global landmark refers to a landmark that most people (e.g., at least a threshold number of people) familiar with an area would know, such as the location of main chain stores or services, transit landmarks (e.g., bus stops or train stations), unique structures, and so forth. For example, global landmarks can include the Empire State Building, Bellevue Square shopping center, the Louvre Museum, King's Cross railway station, and so forth. A personal landmark refers to a landmark that the user is expected to know even if other people familiar with an area may not know the landmark. For example, personal landmarks can be a friend's house, a family member's house, a building where the user works, a store that the user shops at regularly, a theater that the user has been to at least a threshold number of times, and so forth.
0031The colloquial navigation instructions can refer to one or more of these landmarks, identifying one or more landmarks rather than distances or other instructions. For example, assume that a route involves traveling along a <b>2</b>-kilometer stretch of road the passes the Louvre Museum. Rather than presenting an instruction of “stay on this road for 2 kilometers”, a colloquial navigation instruction can be generated that is “stay on this road and pass the Louvre Museum”. By way of another example, assume that a route involves turning left on a particular street, and that a theater (e.g., the 5<sup>th </sup>Avenue Theatre) that the user regularly attends is on the corner where the left turn occurs. Rather than presenting an instruction of “turn left in 300 meters”, a colloquial navigation instruction can be generated that is “turn left at the 5<sup>th </sup>Avenue Theatre”.
0032Map characteristics refer to features along the route that are related to a map of the geographic area that includes the route. These map-related features can be, for example, the layout of roads or other travel paths (e.g., train tracks or other railways, sidewalks or bike paths), locations of buildings, locations of geographic features (e.g., streams or rivers), locations of bridges or other roadway structures, and so forth. In one or more embodiments, the colloquial instruction generation module analyzes the route and determines one or more map-related features along the route that can be used for colloquial instructions.
0033The analysis of a route to determine map-related features can be performed in a variety of different manners, and is based at least in part on the information available in the map. The information available in the map can include information that is displayed when the map is displayed (e.g., locations of roads and buildings) as well as information that may not be displayed when the map is displayed (e.g., speed limits). Different information or data can be included in the map, this information or data describing various characteristics of the geographic area described by the map. For example, in situations in which the map includes the locations of stoplights, the location of stoplights along the route can be analyzed and colloquial navigation instructions generated based on those locations. By way of another example, in situations in which the map includes the locations of roads, the location of roads along the route can be analyzed and colloquial navigation instructions generated based on those locations.
0034In one or more embodiments, the colloquial instruction generation module analyzes the locations of roads along the route to determine whether the locations of the roads correspond to city blocks (also referred to as simply blocks). If the locations of roads along a particular part of the route correspond to city blocks, then colloquial navigation instructions that refer to city blocks (e.g., “turn right in 3 blocks”) are generated for that particular part of the route. A number of cross-roads between two locations, which corresponds to a number of city blocks between those two locations, can be readily determined and used as the number of blocks to identify in the colloquial navigation instructions. However, if the locations of roads along the particular part do not correspond to city blocks, then colloquial navigation instructions that refer to city blocks are not generated for that particular part of the route.
0035Whether the locations of the roads along a particular part of a route correspond to city blocks can be determined by analyzing various characteristics of the locations of the roads. Roads that are laid out in a city block configuration have certain characteristics, such as having cross-roads located at particular intervals (e.g., at least a first threshold distance between roads but less than a second threshold distance between roads), having particular speed limits (e.g., less than a threshold speed limit), having cross-roads intersect approximately (e.g., within a threshold number of degrees of) perpendicularly, and so forth. If the characteristics of the locations of the roads along a particular part of the route correspond to (e.g., match or are the same as) characteristics of roads that are laid out in a city block configuration, then the locations of the roads along the particular part of the route are determined to correspond to city blocks.
0036<figref idref="DRAWINGS">FIG. 3</figref> illustrates an example of a route and map-related features along the route in accordance with one or more embodiments. <figref idref="DRAWINGS">FIG. 3</figref> illustrates a map <b>302</b> having multiple different roads, each illustrated as a line in the map <b>302</b>. The route passes through the geographic area described by the map <b>302</b> along the roads <b>304</b>, <b>306</b>, and <b>308</b>, each illustrated as a dashed line in <figref idref="DRAWINGS">FIG. 3</figref>. For one part of the route, shown as part <b>310</b>, the characteristics of the locations of the roads along the route correspond to characteristics of roads that are laid out in a city block configuration. Thus, colloquial navigation instructions that refer to city blocks (e.g., “turn right in 3 blocks”) are generated for the part <b>310</b> of the route. However, for another part of the route, shown as part <b>312</b>, the characteristics of the locations of the roads along the route do not correspond to characteristics of roads that are laid out in a city block configuration. Thus, colloquial navigation instructions that refer to city blocks (e.g., “turn right in 3 blocks”) are not generated for the part <b>312</b> of the route. Rather, other colloquial navigation instructions or non-colloquial navigation instructions can be generated for the part <b>312</b>.
0037Returning to <figref idref="DRAWINGS">FIG. 2</figref>, in one or more embodiments the colloquial instruction generation module analyzes the locations of stoplights (also referred to as traffic control signals or traffic lights) along the route. A number of stoplights between two locations can be readily determined and used in the colloquial navigation instructions (e.g., “turn right at the second stoplight”).
0038Additionally, or alternatively, the colloquial instruction generation module can analyze the locations of various other map-related features along the route. A number of any one or more of these various other map-related features between two locations can be readily determined and used in colloquial navigation instructions. These various other map-related features can include, for example, locations of bodies of water (e.g., rivers, streams, lakes), locations of bridges, locations of stop signs (or other traffic control signs), locations of other pathways (e.g., sidewalks, bike paths, alleyways, etc.), locations of traffic circles or roundabouts, locations of one-way streets, locations of dead-end streets, locations of particular types or classes of roads (e.g., highways, boulevards, 2-lane roads, 4-lane roads, etc.), locations of off-ramps or on-ramps, locations of driveways, locations of buildings, descriptions of buildings (e.g., color, height, material (e.g., glass and steel, brick), etc.), and so forth. This analysis can lead to various different colloquial navigation instructions, such as “turn left after the river”, “turn right before the bridge”, “turn left at the second stop sign”, “turn left on the first street after the alley”, “turn into the third driveway on the right”, “turn left after the fourth building”, “turn right after the pink building”, and so forth.
0039Thus, in one or more embodiments, the colloquial navigation instructions are navigation instructions that include or reference a landmark as discussed above, a map-related feature as discussed above, or combination thereof. Further, in such embodiments the colloquial navigation instructions are navigation instructions that include or reference such a landmark and/or map-related feature rather than a distance given in a more formal unit (e.g., units of measure in the metric system such as meters or kilometers, or units of measure in US customary units such as yards or miles).
0040The colloquial navigation instructions identified in act <b>206</b> are presented (act <b>208</b>). The colloquial navigation instructions can be presented at various times, such as while the user travels along the route, prior to the user beginning travel along the route, and so forth. The colloquial navigation instructions can also be presented without the user traveling along the route (e.g., for the user to review regardless of whether he or she travels along the route). The colloquial navigation instructions can be played back audibly or alternatively can be presented in other manners.
0041The colloquial navigation instructions can be presented in act <b>208</b> in place of non-colloquial instructions describing the route, or alternatively in conjunction with non-colloquial instructions describing the route. For example, the colloquial instruction of “in 3 blocks turn right onto 156<sup>th </sup>Avenue” can be presented in place of, or in conjunction with, the non-colloquial instruction of “in 300 meters turn right”.
0042<figref idref="DRAWINGS">FIG. 4</figref> illustrates an example user interface presenting colloquial navigation instructions in accordance with one or more embodiments. <figref idref="DRAWINGS">FIG. 4</figref> includes a navigation device <b>400</b>, which can be a navigation device <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>. A map <b>402</b> is displayed by the navigation device <b>400</b>, including various streets and an arrow <b>404</b> indicating a current location of the user. An audible colloquial navigation instruction <b>406</b> is played back to the user, instructing the user to “turn right in three blocks”. The usability of the navigation device <b>400</b> is advantageously improved because the user is presented with colloquial instructions rather than more computerized instructions (e.g., turn right in 100 meters).
0043Returning to <figref idref="DRAWINGS">FIG. 2</figref>, in addition to or in place of audible colloquial navigation instructions, various different colloquial navigation instructions can be displayed by the navigation device in act <b>208</b>. The colloquial navigation instructions can be, for example, text versions of the audible colloquial navigation instructions (e.g., displaying the phrase “turn right in three blocks”). The colloquial navigation instructions can be displayed on a screen or other display device, can be printed out on paper or other hard copy made, and so forth.
0044Various additional visual aids can also be displayed to emphasize or identify colloquial navigation instruction. These visual aids can be, for example, a display of particular characteristics of a building, landmark, or other structure. The visual aids need not be photo-realistic, but nonetheless can identify the characteristic. For example, if a building is situated at a corner where the route indicates a right turn is to be made, and the building has particular characteristics (e.g., is pink in color), those characteristics can be displayed by the navigation device. For example, the building on the corner can be displayed by the navigation device as pink.
0045<figref idref="DRAWINGS">FIG. 5</figref> illustrates an example user interface presenting colloquial navigation instructions and visual aids in accordance with one or more embodiments. <figref idref="DRAWINGS">FIG. 5</figref> is similar to <figref idref="DRAWINGS">FIG. 4</figref>, and includes a navigation device <b>400</b>, a map <b>402</b> including various streets and an arrow <b>404</b> indicating a current location of the user. <figref idref="DRAWINGS">FIG. 5</figref> differs from <figref idref="DRAWINGS">FIG. 4</figref>, however, in that a different audible colloquial navigation instruction <b>502</b> is played back to the user (“turn right in three blocks at the pink building”), and a visual aid <b>504</b> is displayed in <figref idref="DRAWINGS">FIG. 5</figref>. The visual aid <b>504</b> is a building on the map displayed with the characteristics of the building (e.g., displayed as pink) as indicated by the cross-hatching of visual aid <b>504</b>. The usability of the navigation device <b>500</b> is advantageously improved because the user is presented with colloquial instructions rather than more computerized instructions, and visual aids that reinforce the colloquial instructions are also displayed to the user.
0046<figref idref="DRAWINGS">FIG. 6</figref> is a flowchart illustrating an example process <b>600</b> for generating routes that are based on one or more other user-favored routes in accordance with one or more embodiments. Process <b>600</b> is carried out by a device, such as navigation device <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>, and can be implemented in software, firmware, hardware, or combinations thereof. Process <b>600</b> is shown as a set of acts and is not limited to the order shown for performing the operations of the various acts. Process <b>600</b> is an example process for generating routes that are based on one or more other user-favored routes; additional discussions of generating routes that are based on one or more other user-favored routes are included herein with reference to different figures.
0047In process <b>600</b>, a request for a route between a start location and a destination location is received (act <b>602</b>). The request can be received as a user input, or alternatively the request can be received from another component, module, device, and so forth. The start location is typically a current location of the navigation device <b>100</b>, but can alternatively be other locations. The start and destination locations each refer to any geographic position, and can be identified in any of a variety of different manners. For example, a start or destination location can be identified by a user input (e.g., a user input entering an address, selecting a stored or favorite address), by an indication from another component, module, or device, and so forth.
0048One or more user-favored routes are identified (act <b>604</b>). A user-favored route refers to a route between two locations that is determined to be desired, preferred, or otherwise favored over other routes. Which routes are user-favored routes can be determined in a variety of different manners. In one or more embodiments, a user input is received identifying a route as a user-favored route. The user input can be any of a variety of different user inputs as discussed above. Whenever a route is generated by the navigation device, a user input can be received to identify the route as user-favored. For example, the user can provide a user input to save the route to a “favorites” list, a user input to star or “like” the route, and so forth.
0049Additionally or alternatively, user-favored routes can be determined automatically by a component or module (e.g., by a module of the navigation system <b>106</b>). User-favored routes can be determined automatically in a variety of different manners. For example, a route that is taken between start and destination locations at least a threshold number of times (or at least a threshold percentage of the number of times the user travels between the start and destination locations) can be automatically determined to be a user-favored route. By way of another example, a route that is taken between start and destination locations that is different than the route generated by the navigation device can be automatically determined to be a user-favored route.
0050A route between the start and location destinations (as indicated in act <b>602</b>) is generated based on the identified one or more user-favored routes (act <b>606</b>). The generated route in act <b>606</b> is effectively “snapped to” a user-favored route, using at least part of a user-favored route. This route generation based on one or more user-favored routes advantageously improves usability of the navigation device by allowing a user to have a route generated in act <b>606</b> that includes portions of one or more other routes that the user is familiar with, prefers, or otherwise desires or favors.
0051The generation of a route based on one or more user-favored routes can be performed in various manners. Situations oftentimes arise in which multiple different routes can be generated between the start and destination locations, these multiple different routes having minor differences in travel times or travel distances. In such situations, the route having the most parts (e.g., the longest travel time along, or the longest distance) in common with a user-favored route is the route generated in act <b>606</b>. For example, if a first route indicates 15 minutes travel time (e.g., based on the speed limit(s) along the route) along one or more user-favored routes and a second route indicates 25 minutes travel time along one or more user-favored routes, then the second route is the route generated in act <b>606</b>. By way of another example, if a first route includes 5 kilometers along one or more user-favored routes and a second route includes 10 kilometers along one or more user-favored routes, then the second route is the route generated in act <b>606</b>.
0052Additionally, situations can arise in which a route can be generated between the start and destination locations, and the route passes near (e.g., within a threshold distance of, such as within one kilometer of) a part of a user-favored route. In such situations, the route being generated can be changed so that the route does include that part of the user-favored route. In one or more embodiments, the route is changed only if the change would result in at least a threshold amount of time or distance (e.g., at least five minutes, at least two times the threshold distance used to determine whether the route passes near part of a user-favored route, etc.) along the user-favored route.
0053<figref idref="DRAWINGS">FIGS. 7A</figref>, <b>7</b>B, and <b>7</b>C illustrate an example of generating a route based on one or more user-favored routes in accordance with one or more embodiments. <figref idref="DRAWINGS">FIGS. 7A</figref>, <b>7</b>B, and <b>7</b>C each illustrate a map <b>702</b> having multiple different roads, each illustrated as a line in the map <b>702</b>. An arrow <b>704</b> identifies a start location for a route to be generated, and a star <b>706</b> identifies a destination location for the route to be generated.
0054Assume that a user-favored route between another start location and another destination route includes various roads in the map <b>702</b>, illustrated by the dashed line <b>708</b> in <figref idref="DRAWINGS">FIG. 7A</figref>. In generating the route from the arrow <b>704</b> to the star <b>706</b>, a first route illustrated by dashed line <b>710</b> in <figref idref="DRAWINGS">FIG. 7B</figref> could be generated, or a second route illustrated by dashed line <b>712</b> in <figref idref="DRAWINGS">FIG. 7C</figref> could be generated. The route illustrated by the dashed line <b>712</b> in <figref idref="DRAWINGS">FIG. 7C</figref> is the route generated in act <b>606</b> because the route illustrated by the dashed line <b>712</b> in <figref idref="DRAWINGS">FIG. 7C</figref> is the one of the two routes that includes the most parts in the user-favored route illustrated by the dashed line <b>708</b> in <figref idref="DRAWINGS">FIG. 7A</figref>.
0055Returning to <figref idref="DRAWINGS">FIG. 6</figref>, navigation instructions for the route generated in act <b>606</b> are presented (act <b>608</b>). The navigation instructions can be presented at various times, such as while the user travels along the route, prior to the user beginning travel along the route, and so forth. The navigation instructions can also be presented without the user traveling along the route (e.g., for the user to review regardless of whether he or she travels along the route). The navigation instructions can be presented in different manners, such as by being played back audibly, being displayed on a screen or other display device, being printed out on paper or other hard copy made, and so forth.
0056Processes <b>200</b> and <b>600</b> are illustrated as separate flowcharts in <figref idref="DRAWINGS">FIGS. 2 and 6</figref>. It should be noted that the embodiments described in <figref idref="DRAWINGS">FIGS. 2 and 6</figref> can be used individually or alternatively in combination. For example, act <b>204</b> of <figref idref="DRAWINGS">FIG. 2</figref> can be implemented as acts <b>604</b> and <b>606</b> of <figref idref="DRAWINGS">FIG. 6</figref>. E.g., the route generated in act <b>204</b> of <figref idref="DRAWINGS">FIG. 2</figref> can be generated by identifying one or more user-favored routes in act <b>604</b> and generating a route between the start and location destinations based on the identified one or more user-favored routes in act <b>606</b>.
0057Returning to <figref idref="DRAWINGS">FIG. 1</figref>, in one more embodiments, the user-favored route based route identification module <b>116</b> records various data indicating the position of the navigation device <b>100</b> at various times to be used in various manners, such as to identify user-favored routes as discussed above, personal landmarks as discussed above, and so forth. The recording of data indicating the position of the device <b>100</b> is performed after receiving user consent to do so. This user consent can be an opt-in consent, where the user takes an affirmative action to request that the position data be recorded before the navigation device <b>100</b> performs any recording of data for the device <b>100</b>. Alternatively, this user consent can be an opt-out consent, where the user takes an affirmative action to request that the position data not be recorded; if the user does not choose to opt out of this recording of the position data, then it is an implied consent by the user to record the position data.
0058<figref idref="DRAWINGS">FIG. 8</figref> illustrates an example user interface that can be displayed to a user of a device to allow the user to select whether position data for that device will be recorded in accordance with one or more embodiments. A position recording control window <b>800</b> is displayed including a description <b>802</b> explaining to the user why the position of the device is being recorded. A link <b>804</b> to a privacy statement is also displayed. If the user selects link <b>804</b>, a privacy statement is displayed, explaining to the user how the recorded position data is kept confidential.
0059Additionally, the user is able to select a radio button <b>806</b> to opt-in to the position recording, or a radio button <b>808</b> to opt-out of the position recording. Once a radio button <b>806</b> or <b>808</b> is selected, the user can select an “OK” button <b>810</b> to have the selection saved. It is to be appreciated that radio buttons and an “OK” button are only examples of user interfaces that can be presented to a user to opt-in or opt-out of the position recording, and that a variety of other conventional user interface techniques can alternatively be used. The device then proceeds to record or not record the device position in accordance with the user's selection.
0060Although particular functionality is discussed herein with reference to particular modules, it should be noted that the functionality of individual modules discussed herein can be separated into multiple modules, and/or at least some functionality of multiple modules can be combined into a single module. Additionally, a particular module discussed herein as performing an action includes that particular module itself performing the action, or alternatively that particular module invoking or otherwise accessing another component or module that performs the action (or performs the action in conjunction with that particular module). Thus, a particular module performing an action includes that particular module itself performing the action and/or another module invoked or otherwise accessed by that particular module performing the action.
0061In the discussions herein, various different embodiments are described. It is to be appreciated and understood that each embodiment described herein can be used on its own or in connection with one or more other embodiments described herein.
0062Further aspects of the techniques discussed herein relate to one or more of the following embodiments.
0063A method implemented in a navigation device comprises generating a route between a start location and a destination location; identifying, by analyzing the route, colloquial navigation instructions describing at least part of the route, the colloquial navigation instructions identifying a number of blocks in situations in which locations of roads along the route correspond to city blocks; and presenting the colloquial navigation instructions.
0064In the above described method, the identifying further includes: analyzing the route to identify map-related features along the route; and identifying the colloquial navigation instructions based at least in part on the map-related features.
0065In any one or more of the above described methods, the map-related features comprise the locations of roads, the analyzing includes determining based on the locations of roads that the locations of roads along a particular part of the route correspond to city blocks, and the colloquial navigation instructions identify a number of blocks until a turn is to be made.
0066In any one or more of the above described methods, the map-related features comprise locations of stoplights, and the colloquial navigation instructions identify a number of stoplights until a turn is to be made.
0067In any one or more of the above described methods, the map-related features comprise one or more features selected from the following: locations of bodies of water, locations of bridges, locations of driveways, locations of buildings, locations of off-ramps, and locations of on-ramps.
0068In any one or more of the above described methods, the identifying further includes analyzing the route to identify one or more landmarks along the route; and identifying the colloquial navigation instructions based at least in part on the landmarks along the route.
0069In any one or more of the above described methods, the one or more landmarks include a global landmark known to people familiar with the geographic area that includes the route.
0070In any one or more of the above described methods, the one or more landmarks include a personal landmark known to a user of the navigation device despite not being generally known by people familiar with the geographic area that includes the route.
0071In any one or more of the above described methods, the presenting the colloquial navigation instructions comprises playing back the colloquial navigation instructions audibly, and the method further comprises displaying a visual aid on a map that includes the route, the visual aid being an indication of one or more characteristics of a structure referred to in a colloquial navigation instruction.
0072In any one or more of the above described methods, the displaying the visual aid comprises displaying a structure on the map with a color of the structure as indicated by the one or more characteristics of the structure.
0073In any one or more of the above described methods, the generating the route comprises identifying one or more user-favored routes of a user of the navigation device; and generating, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location.
0074A method implemented in a navigation device comprises receiving a request for a route between a start location and a destination location; identifying one or more user-favored routes of a user of the navigation device; generating, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location; and presenting navigation instructions for the route.
0075In any one or more of the above described methods, the navigation instructions comprise colloquial navigation instructions, and the presenting comprises playing back the colloquial navigation instructions audibly.
0076In any one or more of the above described methods, the method further comprising receiving a user input indicating that a particular route is favored by the user; and saving, in response to the user input, an indication that the particular route is a user-favored route of the user.
0077In any one or more of the above described methods, the method further comprising automatically determining that a particular route is favored by the user; and saving, in response to the user input, an indication that the particular route is a user-favored route of the user.
0078In any one or more of the above described methods, the generating comprises identifying multiple different routes between the start location and the destination location; and selecting, as the route between the start location and the destination location, one of the multiple different routes having a largest number of parts in common with one of the one or more user-favored routes.
0079In any one or more of the above described methods, the generating comprises changing a route to include at least part of a user-favored route.
0080A navigation device comprises a global navigation satellite system, implemented at least in part in hardware, configured to determine a position of the navigation device; a user-favored route based route identification module configured to receive a request for a route between a start location and a destination location, identify one or more user-favored routes of a user of the navigation device, and generate, based on the start location, the destination location, and the one or more user-favored routes, a route between the start location and the destination location; and a colloquial instruction generation module configured to identify, by analyzing the route, colloquial navigation instructions describing at least part of the route, and play back the colloquial navigation instructions audibly as the user travels along the route.
0081In the above described navigation device, the navigation device further comprising a user input module configured to receive a user input indicating that a particular route is favored by the user, and the user-favored route based route identification module being further configured to save, in response to the user input, an indication that the particular route is a user-favored route of the user.
0082In any one or more of the above described navigation devices, the user-favored route based route identification module being further configured to: automatically determine that a particular route is favored by the user; and save, in response to the user input, an indication that the particular route is a user-favored route of the user.
0083<figref idref="DRAWINGS">FIG. 9</figref> illustrates an example system generally at <b>900</b> that includes an example computing device <b>902</b> that is representative of one or more systems and/or devices that may implement the various techniques described herein. The computing device <b>902</b> may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and/or any other suitable computing device or computing system. The computing device <b>902</b> can be, for example, a navigation device <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>.
0084The example computing device <b>902</b> as illustrated includes a processing system <b>904</b>, one or more computer-readable media <b>906</b>, and one or more I/O Interfaces <b>908</b> that are communicatively coupled, one to another. Although not shown, the computing device <b>902</b> may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.
0085The processing system <b>904</b> is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system <b>904</b> is illustrated as including hardware elements <b>910</b> that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements <b>910</b> are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.
0086The computer-readable media <b>906</b> is illustrated as including memory/storage <b>912</b>. The memory/storage <b>912</b> represents memory/storage capacity associated with one or more computer-readable media. The memory/storage <b>912</b> may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage <b>912</b> may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media <b>906</b> may be configured in a variety of other ways as further described below.
0087Input/output interface(s) <b>908</b> are representative of functionality to allow a user to enter commands and information to computing device <b>902</b>, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a mouse), a microphone (e.g., for voice inputs), a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to detect movement that does not involve touch as gestures), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device <b>902</b> may be configured in a variety of ways as further described below to support user interaction.
0088Computing device <b>902</b> also includes a navigation system <b>914</b>. Navigation system <b>914</b> provides various navigation and guidance functionality as discussed herein. Navigation system <b>914</b> can be, for example, navigation system <b>106</b> of <figref idref="DRAWINGS">FIG. 1</figref>.
0089Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms “module,” “functionality,” and “component” as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of computing platforms having a variety of processors.
0090An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device <b>902</b>. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media.”
0091“Computer-readable storage media” refers to media and/or devices that enable persistent storage of information and/or storage that is tangible, in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.
0092“Computer-readable signal media” refers to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device <b>902</b>, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.
0093As previously described, hardware elements <b>910</b> and computer-readable media <b>906</b> are representative of instructions, modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein. Hardware elements may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware devices. In this context, a hardware element may operate as a processing device that performs program tasks defined by instructions, modules, and/or logic embodied by the hardware element as well as a hardware device utilized to store instructions for execution, e.g., the computer-readable storage media described previously.
0094Combinations of the foregoing may also be employed to implement various techniques and modules described herein. Accordingly, software, hardware, or program modules and other program modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements <b>910</b>. The computing device <b>902</b> may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of modules as a module that is executable by the computing device <b>902</b> as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements <b>910</b> of the processing system. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices <b>902</b> and/or processing systems <b>904</b>) to implement techniques, modules, and examples described herein.
0095As further illustrated in <figref idref="DRAWINGS">FIG. 9</figref>, the example system <b>900</b> enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.
0096In the example system <b>900</b>, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one or more embodiments, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.
0097In one or more embodiments, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one or more embodiments, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.
0098In various implementations, the computing device <b>902</b> may assume a variety of different configurations, such as for computer <b>916</b>, mobile <b>918</b>, and television <b>920</b> uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device <b>902</b> may be configured according to one or more of the different device classes. For instance, the computing device <b>902</b> may be implemented as the computer <b>916</b> class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.
0099The computing device <b>902</b> may also be implemented as the mobile <b>918</b> class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device <b>902</b> may also be implemented as the television <b>920</b> class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on.
0100The techniques described herein may be supported by these various configurations of the computing device <b>902</b> and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented all or in part through use of a distributed system, such as over a “cloud” <b>922</b> via a platform <b>924</b> as described below.
0101The cloud <b>922</b> includes and/or is representative of a platform <b>924</b> for resources <b>926</b>. The platform <b>924</b> abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud <b>922</b>. The resources <b>926</b> may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device <b>902</b>. Resources <b>926</b> can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.
0102The platform <b>924</b> may abstract resources and functions to connect the computing device <b>902</b> with other computing devices. The platform <b>924</b> may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources <b>926</b> that are implemented via the platform <b>924</b>. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system <b>900</b>. For example, the functionality may be implemented in part on the computing device <b>902</b> as well as via the platform <b>924</b> that abstracts the functionality of the cloud <b>922</b>.
0103Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Contents4
12 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2023373478A1 | Cited by | United States of America | Search report |
| US10146770B2 | Cited by | United States of America | Applicant |
| US11821747B2 | Cited by | United States of America | Applicant |
| CN112368546A | Cited by | China | Search report |
| US11231291B2 | Cited by | United States of America | Applicant |
| US11650068B2 | Cited by | United States of America | Applicant |
| US11118929B2 | Cited by | United States of America | Search report |
| US12240453B2 | Cited by | United States of America | Search report |
| US10528674B2 | Cited by | United States of America | Applicant |
| US9970776B2 | Cited by | United States of America | Search report |
| US11879746B2 | Cited by | United States of America | Applicant |
| US12442653B2 | Cited by | United States of America | Applicant |
| US2009143984A1 | Cites | United States of America | Pre-grant |
| US2009150156A1 | Cites | United States of America | Pre-grant |
| WO2010081549A1 | Cites | World Intellectual Property Organization (WIPO) | Pre-grant |
| US2010174479A1 | Cites | United States of America | Pre-grant |
| US2011276267A1 | Cites | United States of America | Pre-grant |
| US2013035852A1 | Cites | United States of America | Pre-grant |
| US2014156188A1 | Cites | United States of America | Pre-grant |
| US2014274107A1 | Cites | United States of America | Pre-grant |
| US2015088407A1 | Cites | United States of America | Pre-grant |
| GB2492390A | Cites | United Kingdom | Pre-grant |
| US7680749B1 | Cites | United States of America | Pre-grant |
| US9256615B2 | Cites | United States of America | Pre-grant |
1 member in 1 office; this record represents the family
Members1
| Document | Office | Kind | |
|---|---|---|---|
| US2016076902A1 | United States of America | A1 |
101 transactions on the USPTO file
Abandoned after 3 non-final rejections, 3 final rejections and 2 RCEs.
- Non-final rejections
- 3
- Final rejections
- 3
- RCEs
- 2
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Correspondence Address ChangeC.ADB | C.ADB | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Abandonment for Failure to Respond to Office ActionAbandonedMABN2 | MABN2 | |
| Aband. for Failure to Respond to O. A.AbandonedABN2 | ABN2 | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| After Final Consideration Program Additional Consideration and/or updated searchAFAC | AFAC | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| PILOT- Request for After Final Consideration ProgramRAFC | RAFC | |
| Response after Final ActionA.NE | A.NE | |
| Email NotificationEML_NTR | EML_NTR | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Applicant Initiated Interview SummaryMEXIA | MEXIA | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Interview Summary- Applicant InitiatedEXIA | EXIA | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Interview Summary - Applicant Initiated - TelephonicMEXAT | MEXAT | |
| Interview Summary - Applicant Initiated - TelephonicEXAT | EXAT | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Email NotificationEML_NTR | EML_NTR | |
| Email NotificationEML_NTR | EML_NTR | |
| Filing Receipt - CorrectedFLRCPT.C | FLRCPT.C | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response to Election / Restriction FiledELC. | ELC. | |
| Email NotificationEML_NTR | EML_NTR | |
| Application ready for PDX access by participating foreign officesCCRDY | CCRDY | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Restriction RequirementMCTRS | MCTRS | |
| Restriction/Election RequirementCTRS | CTRS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Oath or Declaration Filed (Including Supplemental)C602 | C602 | |
| Email NotificationEML_NTR | EML_NTR | |
| Application Is Now CompleteCOMP | COMP | |
| Application Is Now CompleteCOMP | COMP | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Sent to Classification ContractorPGPC | PGPC | |
| FITF set to YES - revise initial settingFTFS | FTFS | |
| Cleared by L&R (LARS)L128 | L128 | |
| Referred to Level 2 (LARS) by OIPE CSRL198 | L198 | |
| Patent Term Adjustment - Ready for ExaminationPTA.RFE | PTA.RFE | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Entity status set to undiscounted (initial default setting or status change)BIG. | BIG. |
5 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTIONSTCB | STCB | |
| Information on status: patent application and granting procedure in generalADVISORY ACTION MAILEDSTPP | STPP | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20160076902
- Application
- 14485445
Titles
- English
- COLLOQUIAL OR USER-FAVORED ROUTE BASED NAVIGATION INSTRUCTIONS
Classification
- CPC, 6
- G01C21/3626
- G01C21/3641
- G01C21/3629
- G01C21/26
- G01C21/3484
- G01C21/36
- IPC, 1
- G01C21 36