Method and system for providing reminders about points of interests while traveling
Claim Score by NHIP
Abstract
A navigation system includes a feature that allows a user to specify a type of point of interest (or business chain) and then receive a reminder when the user is in proximity to a location of the point of interest of the specified type (or business chain) while traveling in a geographic region.

Term
Term ended
Projected expiry passed 14 March 2020, 6.5 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
34 claims: 3 independent, 31 dependent
- 1A method of operation for a navigation system, the method comprising the steps of:accepting identification by the user of a category of location type about which a reminder is desired;while the user is traveling in a geographic region to a location other than a location of the identified category of location type, determining when the navigation system is in proximity to a location of the category of location type identified by the user;and informing the user when in proximity to a location of the identified category of location type.
- 22Broadest claimClaim Score 87, broad(NHIP)A method of operation for a navigation system, the method comprising the steps of:while a user of the navigation system is traveling in a geographic region without being guided to a destination by the navigation system, determining when the user is in proximity to a location of a type previously specified by the user;and informing the user that the user is in proximity to a location of the type previously specified by the user.
- 23A method of operation for a navigation system, the method comprising the steps of:accepting an identification by the user of a business chain about which a reminder is desired when the user is in proximity thereto;while the user is traveling in a geographic region, determining when the user is in proximity to a location of the business chain;and informing the user when in proximity to a location of the business chain.
Independent claims3
74 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
[0001] The present invention relates to navigation systems and more particularly the present invention relates to a feature in a navigation system that facilitates making stops at points of interest of a specified type while traveling.
[0002] Navigation systems are available that provide end users (such as drivers and passengers of the vehicles in which the in-vehicle navigation systems are installed) with various navigation-related functions and features. For example, some navigation systems are able to determine an optimum route to travel by roads between locations in a geographic region. Using input from the end user, and optionally from equipment that can determine one's physical location (such as a GPS system), a navigation system can examine various routes between two locations to determine an optimum route to travel from a starting location to a destination location in a geographic region. The navigation system may then provide the end user with information about the optimum route in the form of guidance that identifies the driving maneuvers required to be taken by the end user to travel from the starting location to the destination location. The guidance may take the form of visual and/or audio instructions that are provided along the way as the end user is traveling the route. Some navigation systems are able to show detailed maps on computer displays outlining routes to destinations, the types of maneuvers to be taken at various locations along the routes, locations of certain types of features, and so on.
[0003] In order to provide these and other navigating functions, navigation systems use geographic data. The geographic data may be in the form of one or more databases that include data that represent physical features in a geographic region. The geographic database may include data representing the roads and intersections in a geographic region and also may include information relating to the represented roads and intersections in the geographic region, such as turn restrictions at intersections, speed limits along the roads, street names of the various roads, address ranges along the roads, and so on.
[0004] Although navigation systems provide many important features, there continues to be room for new features or other improvements. One area in which there is room for improvement relates to making travel more convenient. A person can use a navigation system to identify points of interest of a particular type (e.g., restaurants) that are close to the person's location and receive guidance for traveling to any of the identified points of interest. This type of usage represents one kind of travel that persons commonly make but there are various other kinds of travel. For example, some kinds of locations do not have to be visited immediately. As an example, a person might want to stop at a post office (or other type of point of interest) sometime within the next several days when it is convenient to do so but would rather not make a special trip. Ideally, the person would prefer to make the stop at the post office while in route to another destination if the stop can be made without taking a significant additional amount of time.
[0005] Accordingly, there is a need for a feature in a navigation system that provides guidance about making stops at locations at the convenience of the user.
SUMMARY OF THE INVENTION
[0006] To address these and other objectives, the present invention comprises a method, system, and/or programming for providing a feature in a navigation system that allows a user to specify a type of point of interest and then receive a reminder when the user is in proximity to a point of interest of the specified type while traveling in a geographic region. The reminder is provided while the user is traveling to a location other than a point of interest of the specified type. This feature allows a user to make stops at points of interest of a particular type at the convenience of the user and when the user is close to the point of interest of a particular type, thereby minimizing travel time.
BRIEF DESCRIPTION OF THE DRAWINGS
P-0007[0007]FIG. 1 is a block diagram showing components of an exemplary navigation system used in conjunction with a first embodiment of a feature that provides reminders about points of interest of a specified type while traveling.
P-0008[0008]FIG. 2 is a block diagram showing portions of the navigation application programming in FIG. 1.
P-0009[0009]FIG. 3 is a block diagram illustrating some of the types of data contained in the geographic database shown in FIGS. 1 and 2.
P-0010[0010]FIG. 4 is a block diagram illustrating some of the components of the point of interest data shown in FIG. 3.
P-0011[0011]FIG. 5 is a block diagram illustrating some of the components of the routing data shown in FIG. 3.
P-0012[0012]FIG. 6 shows the navigation system display screen of FIG. 1 with a menu for selecting the point of interest reminder feature.
P-0013[0013]FIG. 7 shows the display screen of the navigation system with a menu for selecting a category of points of interest for which reminders are desired.
P-0014[0014]FIG. 8 shows the navigation system display screen of FIG. 1 with a menu for configuring the threshold of the point of interest reminder feature.
P-0015[0015]FIG. 9 is a flowchart showing steps performed by the point of interest reminder routine in FIG. 2.
P-0016[0016]FIG. 10 shows the display screen of the navigation system with a presentation of data provided by the point of interest reminder routine according to the process of FIG. 9.
P-0017[0017]FIG. 11 shows the display screen of the navigation system with a message provided by the point of interest reminder routine of FIG. 9 prompting the user to select a point of interest to which route guidance is to be provided.
DETAILED DESCRIPTION OF THE PRESENTLY PREFERRED EMBODIMENTS
P-0018[0018] I. Navigation System—Overview
P-0019[0019] For purposes of this disclosure, a “navigation system” is understood to mean a navigation system used in a vehicle (i.e., an in-vehicle navigation system). A “navigation system” is also understood to mean any software application installed on a computer platform that provides navigation-related features and uses geographic data, including applications that are installed on personal computers, networks, portable electronic devices, and so on.
P-0020[0020] Referring to FIG. 1, there is a block diagram of a navigation system <b>110</b>. The navigation system <b>110</b> is installed in a vehicle <b>111</b>, such as a car, bus, or truck, although in alternative embodiments, the navigation system <b>110</b> may be located outside of a vehicle or may be implemented in various other platforms or environments, as described below. The navigation system <b>110</b> is a combination of hardware and software components. In one embodiment, the navigation system <b>110</b> includes a processor <b>112</b>, a drive <b>114</b> connected to the processor <b>112</b>, and a non-volatile memory storage device <b>116</b> for storing programming <b>118</b> and possibly other information. The processor <b>112</b> may be of any type used in navigation systems.
P-0021[0021] The navigation system <b>110</b> may also include a positioning system <b>124</b>. The positioning system <b>24</b> may utilize GPS-type technology, a dead reckoning-type system, or combinations of these or other systems, all of which are known in the art. The positioning system <b>124</b> may include suitable sensing devices <b>125</b> that measure the traveling distance, speed, direction, and so on, of the vehicle. The positioning system <b>124</b> may also include appropriate technology to obtain a GPS signal in a manner which is known in the art. The positioning system <b>124</b> provides an output to the processor <b>112</b>. The output from the positioning system <b>124</b> is used by the software <b>118</b> that is run on the processor <b>112</b> to determine the location, direction, speed, etc., of the navigation system <b>110</b>.
P-0022[0022] The navigation system <b>110</b> also includes a user interface <b>131</b>. The user interface <b>131</b> includes appropriate equipment that allows the end user to input information into the navigation system. This input information may include a request to use the navigation features of the navigation system. For example, the input information may include a request for a route to a desired destination. The input information may also include other kinds of information. The equipment used to input information into the navigation system may include an input panel <b>130</b>, such as a keypad, a keyboard, buttons, switches, etc., or a microphone <b>128</b>, etc., as well as appropriate software, such as voice recognition programming. The user interface <b>131</b> also includes suitable equipment that provides information back to the end user. This equipment may include a display <b>132</b>, speakers <b>133</b>, or other means.
P-0023[0023] The programming <b>118</b> is loaded from the non-volatile memory <b>116</b> into a RAM <b>134</b> associated with the processor <b>112</b> in order to operate the navigation system. Referring to FIG. 2, the programming <b>118</b> includes navigation-related application software <b>119</b> that provides for the navigating functions and features of the navigation system <b>110</b>. The navigation-related application software <b>119</b> uses geographic data <b>140</b>, possibly in conjunction with the output from the positioning system <b>124</b>, to provide various navigation features and functions. The navigation-related application software <b>119</b> may include separate component applications (also referred to as programs, subprograms, routines, or tools) that provide these various navigation-related features and functions.
P-0024[0024]FIG. 2 shows some of the component applications for one embodiment of the navigation-related software <b>119</b> included in the navigation system <b>110</b> of FIG. 1. These component applications may include a geo-coding application <b>141</b> (used for destination selection), a route calculation application <b>142</b>, a route guidance <b>144</b> application (wherein detailed directions are provided for reaching a desired destination), a map display application <b>146</b>, and a vehicle positioning application <b>148</b> (wherein a vehicle position is related to the geographic data <b>140</b>). The applications <b>119</b> may include a point of interest reminder selection routine <b>340</b> and a point of interest reminder presentation routine <b>400</b> (which are explained in more detail below). The navigation-related software applications <b>119</b> may also include other component applications <b>152</b>.
P-0025[0025] The component applications of the programming <b>118</b> may work together through defined programming interfaces. The navigation-related application software <b>119</b> may access the geographic data <b>140</b> directly, or alternatively, the navigation application software <b>119</b> accesses the geographic data <b>140</b> through an interface layer <b>154</b> and operating system <b>156</b>. The interface layer <b>154</b> and operating system <b>156</b> may be part of the programming <b>118</b> or may be provided separately.
P-0026[0026] In addition to the navigation-related applications <b>119</b>, the programming <b>118</b> may also include manager application software <b>155</b>. The manager application software <b>155</b> provide interfaces to the hardware in the user interface <b>131</b> and the positioning system <b>124</b>. The manager application software <b>155</b> may also coordinate requests for data from the navigation-related applications <b>119</b>.
P-0027[0027] In one embodiment, the separate applications of the programming <b>118</b> are written in the C programming language although in alternative embodiments other programming languages may be used, such as C++, Java, Visual Basic, and so on.
P-0028[0028] II. The Geographic Map Database
P-0029[0029] A. Overview.
P-0030[0030] Referring to FIG. 2, the geographic data <b>140</b> is organized into one or more databases <b>162</b> and stored on a storage medium <b>164</b>. The storage medium <b>164</b> is installed in the drive <b>114</b> so that the geographic data <b>140</b> can be read and used by the navigation system. The storage medium <b>164</b> may be removable and replaceable so that a storage medium with an appropriate database <b>162</b> for the geographic region in which the vehicle is traveling can be used. In addition, the storage medium <b>164</b> may be replaceable so that geographic data <b>140</b> on it can be updated easily.
P-0031[0031] In one embodiment, the geographic data are provided by Navigation Technologies Corporation of Rosemont, Ill. However it is understood that the inventive concepts disclosed herein are not restricted to any particular source of data.
P-0032[0032] In one embodiment, the storage medium <b>164</b> is a CD-ROM disk. In an alternative embodiment, the storage medium <b>164</b> may be a PCMCIA card in which case the drive <b>114</b> would be replaced with a PCMCIA slot. Various other storage media may be used, including fixed or hard disks, DVD disks or other currently available storage media, as well as storage media that may be developed in the future. The storage medium <b>164</b> and the geographic data <b>140</b> do not have to be physically provided at the location of the navigation system. In alternative embodiments, the storage medium <b>164</b>, upon which some or all of the geographic data <b>140</b> are stored, may be located remotely from the rest of the navigation system and portions of the geographic data provided via a communications link, as needed.
P-0033[0033] The map database <b>162</b> contains information about the roadway network in the geographic region. In one embodiment, the map database <b>162</b> includes node data and segment data. These data represent components of the physical road network. Node data represent physical locations in the geographic region (such as roadway intersections and other positions) and segment data represent portions of roadways between the physical locations represented by nodes. (The terms “nodes” and “segments” represent only one terminology for describing these physical geographic features and other terminology for describing these features is intended to be encompassed within the scope of these concepts.)
P-0034[0034] Because a navigation system uses geographic data in certain known and expected ways to perform known functions, the geographic data can be organized, structured, and/or arranged in ways that facilitate their use by the navigation system. Some of the ways that geographic data <b>140</b> can be can be organized, structured, or arranged in a geographic database are described in U.S. Pat. Nos. 5,968,109, 5,974,419, and 5,953,722, the entire disclosures of which are incorporated by reference herein.
P-0035[0035]FIG. 3 illustrates an organization of the geographic database <b>162</b>. The organization shown in FIG. 3 represents one way that geographic data <b>140</b> can be organized in a database. Various other arrangements are possible and can be used. In FIG. 3, the geographic database <b>162</b> is shown to be comprised of separate subsets <b>164</b> of data. These subsets <b>164</b> include routing data <b>166</b>, cartographic data <b>167</b> (for map display), maneuver data <b>168</b> (for route guidance), point-of-interest data <b>169</b> (for identifying specific points of interest, such as hotels, restaurants, museums, stadiums, airports, etc.), name data <b>170</b> (identifying the names of roads, places and other features), places <b>171</b> (e.g., cities, states, counties), postal codes <b>172</b> and other kinds of data <b>173</b>. The geographic database <b>162</b> may be defined with different data types or with fewer or more data types.
P-0036[0036] Each subset <b>164</b> of geographic data <b>160</b> includes the data and associated attributes required to perform a particular navigation function but excludes data and attributes which are not needed to perform the function. There is some overlap of data between each of these subsets, with the result that some information may be included in more than one subset. For example, a data entity representing a road segment in the routing data <b>166</b> and a data entity representing the same road segment in the cartographic data <b>167</b> may include attributes identifying the nodes located at the ends of the road segment. Although this duplication may result in a larger overall data storage requirement, each of the navigation functions (i.e., the applications <b>119</b> in FIG. 2) benefits from the resultant efficiency of handling smaller amounts of data.
P-0037[0037] Although the organization of the geographic data <b>140</b> into different types provides for efficient use of the data by the different navigation functions, it is necessary to provide that the different functions that use these different data types work together. To permit these types <b>164</b> of data to work together, indexes <b>176</b> are included as part of the geographic database <b>162</b>. The indexes <b>176</b> provide cross references, search trees, and/or other data finding techniques. The indexes <b>176</b> can be located external of any of the data types <b>164</b> or the indexes <b>176</b> may be located within any of the types <b>164</b> of data. In this embodiment of the geographic database <b>164</b>, both internal and external indexes are used.
P-0038[0038]FIG. 4 shows some of the kinds of information included in the point of interest data <b>169</b>. The point of interest data <b>169</b> includes a plurality of data records <b>269</b> each of which includes data about a separate point of interest located in the coverage area of the geographic database <b>162</b>. A point of interest record <b>269</b> includes a point of interest ID <b>269</b>(<b>1</b>), name data <b>269</b>(<b>2</b>), street data <b>269</b>(<b>3</b>), location data <b>269</b>(<b>4</b>), facility type data <b>269</b>(<b>5</b>), administrative zone data <b>269</b>(<b>6</b>), postal code data <b>269</b>(<b>7</b>), phone number data <b>269</b>(<b>8</b>), chain ID data <b>269</b>(<b>9</b>), and possibly other data <b>269</b>(<b>10</b>). The point of interest ID <b>269</b>(<b>1</b>) includes a number or code by which the point of interest record <b>269</b> can be identified in the database <b>162</b>. The name data <b>269</b>(<b>2</b>) contains the name of the represented point of interest. The street data <b>269</b>(<b>3</b>) contains the street address of the represented point of interest. The location data <b>269</b>(<b>4</b>) contains an identification of a road segment data record in the routing data <b>166</b> that represents the road segment along which the represented point of interest is located or alternatively, the location data <b>269</b>(<b>4</b>) may contain the geographic coordinates of the represented point of interest. The facility type data <b>269</b>(<b>5</b>) contains data indicating the type of facility or business the represented point of interest is, e.g., restaurant, post office, antique store, city hall, convention center, automobile repair shop, gas station, ATM, sports facility, hotel, and so on. Within some of these types, the point of interest may include further classification data, e.g., type of restaurant (Chinese, Italian, etc.). The administrative zone data <b>269</b>(<b>6</b>) contains the name of the municipality (e.g., city or town) and state of the represented point of interest. The postal code data <b>269</b>(<b>7</b>) contains the appropriate postal code information (e.g., zip code in the U.S.) of the represented point of interest. The phone number data <b>269</b>(<b>8</b>) contains the phone number of the represented point of interest. If the represented point of interest is part of a business chain, the point of interest record contains data in a chain ID data <b>269</b>(<b>9</b>) that identifies the business chain.
P-0039[0039]FIG. 5 shows some of the kinds of information included in the routing data (<b>166</b> in FIG. 3). The routing data <b>166</b> includes a plurality of road segment data records <b>258</b> each of which includes data about a separate road segment located in the coverage area of the geographic database <b>162</b>. A road segment record <b>258</b> includes a segment ID <b>258</b>(<b>1</b>) by which the data record can be identified in the geographic database <b>162</b>. The road segment data record <b>258</b> may also include data <b>258</b>(<b>2</b>) that indicates the restrictions, if any, on the direction of vehicular travel permitted on the represented road segment. The road segment data record <b>258</b> includes data <b>258</b>(<b>3</b>) that indicates a speed limit or speed category (i.e., the maximum permitted vehicular speed of travel on the represented road segment). The road segment data record <b>258</b> may also include data <b>258</b>(<b>4</b>) indicating whether the represented road segment is part of a controlled access road (such as an expressway), a ramp to a controlled access road, a bridge, a tunnel, a toll road, a ferry, and so on. The road segment data record <b>258</b> may also include data <b>258</b>(<b>5</b>) indicating a travel time which indicates an estimated amount of time to travel along the road segment. The travel time data <b>258</b>(<b>5</b>) may be expressed in seconds or may be expressed in arbitrary units. The travel time data <b>258</b>(<b>5</b>) may include separate travel times for each direction of travel along the segment. The travel time data <b>258</b>(<b>5</b>) may include separate travel times for different times of day, day of week, etc.
P-0040[0040] The road segment data record <b>258</b> also includes data <b>258</b>(<b>7</b>) providing the geographic coordinates (e.g., the latitude and longitude) of the endpoints of the road segment. In one embodiment, these data <b>258</b>(<b>7</b>) contain references to the node data records <b>260</b>(<b>1</b>) and <b>260</b>(<b>2</b>) that represent the nodes corresponding to the endpoints of the represented road segment.
P-0041[0041] The road segment record <b>258</b> may also include or be associated with other data <b>258</b>(<b>6</b>) that refer to various other attributes of the represented road segment. For example, the road segment data record may include data identifying what turn restrictions exist at each of the nodes which correspond to intersections at the ends of the road portion represented by the road segment, the name or names by which the represented road segment is known, the street address ranges along the represented road segment, and so on. The various attributes associated with a road segment may be included in a single road segment record, or preferably are included in more than one type of road segment record which are cross-referenced to each other.
P-0042[0042] III. Proximity Convenience Reminders
P-0043[0043] A. Overview.
P-0044[0044] Embodiments of the disclosed navigation system feature provide reminders (audible, visual, or both) to a navigation system user when the user is close to a point of interest (e.g., type of business, facility, location, etc.) of a type that had been previously identified by the user. These reminders are provided while the user is traveling in a geographic area. These reminders are provided regardless of whether the navigation system is being used to receive driving instructions to travel to a destination. Thus, the user may be following his/her own route and not receiving driving instructions from the navigation system. Alternatively, the user may be receiving driving instructions to travel to a destination other than a point of interest of the previously identified type. Reminders may be accompanied with an option to provide route guidance to one of the points of interest of the specified type that are identified as being close to the user's current location.
P-0045[0045] B. Selecting Point of Interest Types for Reminders.
P-0046[0046]FIG. 6 shows a menu <b>320</b> on the display <b>132</b> of the navigation system <b>110</b>. The menu <b>320</b> presents a plurality of available features <b>327</b>. The user is prompted by a message <b>326</b> to choose one of the available features <b>327</b>. One of the features is highlighted with an outlining box <b>330</b>. The user can manually press a toggle <b>332</b> on the keypad <b>130</b> of the user interface <b>131</b> to move the outlining box <b>330</b> up or down in order to change the feature highlighted with the outlining box <b>330</b>. When the outlining box <b>330</b> is on the feature that the user wants to choose, the user presses another key to select the highlighted feature. For example, the user may press a “SELECT” key <b>336</b>. In FIG. 6, the feature labeled “ADD PROXIMITY REMINDER” is highlighted with the outlining box <b>330</b> and the user can select this item by pressing the “SELECT” key <b>336</b>. (Other features that are available on this menu <b>320</b> include calculating a new route to a new destination and calculating alternative routes to the existing destination.) When the user selects the feature “ADD PROXIMITY REMINDER”, the point of interest selection routine (<b>340</b> in FIG. 2) is called. The point of interest selection routine <b>340</b> is included among the applications <b>119</b> in the navigation system <b>110</b>.
P-0047[0047]FIG. 7 shows a menu <b>360</b> on the display <b>132</b>. The <b>360</b> menu includes a list of a plurality <b>362</b> of different categories (or types) of points of interest. The list of point of interest categories is generated by the point of interest selection routine <b>340</b> using the facility type data (<b>269</b>(<b>5</b>) in FIG. 4) from the point of interest data <b>169</b> from the geographic database <b>162</b>. The point of interest selection routine <b>340</b> also provides a message <b>364</b> prompting the user to select a category (or type) of point of interest. One of the categories is highlighted with an outlining box <b>366</b>. In the embodiment of FIG. 7, the “POST OFFICES” category is highlighted with the outlining box <b>366</b>. If the user wishes to change the category highlighted with the outlining box <b>366</b>, the user can manually press the toggle <b>332</b> of the user interface <b>131</b> to move the outlining box <b>366</b> up or down. In response to the message <b>364</b>, the user operates the controls on the user interface <b>131</b> (e.g., pressing the “SELECT” key <b>336</b>) to select one of the types of points of interest for which proximity reminders are desired. Referring to FIG. 1, when a point of interest category type is selected, the point of interest selection routine <b>340</b> causes data indicating this point of interest type to be stored in a user data portion <b>372</b> of the non-volatile storage <b>116</b> of the navigation system <b>110</b>. These data <b>370</b> remain in the non-volatile storage <b>116</b> even when the navigation system and vehicle are turned off so that the data <b>370</b> are available whenever the navigation system is being used.
P-0048[0048] According to one embodiment, the user may select the points of interest for which reminders are provided by chain instead of by point of interest type. If the user chooses to have point of interest reminders provided by chain, reminders will be provided whenever the user is in proximity to a location of an establishment of that particular chain. For example, the user may want to be reminded when he/she is close to a McDonald's restaurant. When point of interest reminders are selected by chain, the chain ID data (<b>269</b>(<b>9</b>) in FIG. 4) are used by the point of interest selection routine <b>340</b> in a similar manner as the facility type data were used, as described above.
P-0049[0049] C. Selecting Thresholds.
P-0050[0050] According to some embodiments, the proximity reminder feature is configured with a threshold parameter. The threshold parameter may be a threshold distance. When configured with a threshold distance, the navigation system identifies all the points of interest of the specified type to the user that are within the threshold distance of the present location of the user while the user is traveling in the geographic area.
P-0051[0051] According to other embodiments, the threshold parameter is a threshold travel time. When configured with a threshold travel time, the navigation system identifies all the points of interest of the specified type to the user that can be reached within the threshold travel time from the present location of the user while the user is traveling in a region taking into account the travel times of roads located around the user.
P-0052[0052] In addition to distance thresholds and travel time thresholds, other types of threshold parameters may be used. For example, a threshold parameter may combine distance and travel time. According to this alternative, a point of interest which is close (as the crow flies), would be eliminated if the amount of time required to reach it exceeded a time of travel threshold.
P-0053[0053] In alternative embodiments, a dynamic threshold parameter can be used. A dynamic threshold parameter takes into account current factors when determining whether any points of interest of the specified type are in proximity to the user's current position. For example, a dynamic threshold may take into account the type of road that the vehicle is traveling on, the vehicle's current speed, the time of day, the day of week, the hours of operation of the point of interest, and so on. The dynamic threshold may also take into account the duration of time for which the reminder has been set.
P-0054[0054] According to some embodiments, the threshold parameters (e.g., distance and/or travel time) may be user-configurable. FIG. 8 shows a menu <b>380</b> on the display <b>132</b> that can be used for configuring the threshold parameter and/or threshold travel time. If the user does not specify a threshold parameter, a default threshold parameter may be used.
P-0055[0055] According to one embodiment, a user can specify different thresholds for different types of points of interest. For example, a 1 mile distance threshold can be set for post offices and a 5 mile distance threshold can be set for gas stations.
P-0056[0056] Referring to FIG. 1, when a threshold of any type is selected, data <b>374</b> indicating the threshold are stored in the user data portion <b>372</b> of the non-volatile storage <b>116</b> of the navigation system <b>110</b>. These data <b>374</b> remain in the non-volatile storage <b>116</b> even when the navigation system and vehicle are turned off.
P-0057[0057] D. Operation.
P-0058[0058] As stated above, after the user has selected a point of interest category type (or chain) and, optionally, a threshold, data <b>370</b> and <b>374</b> indicating these selections are stored in the non-volatile memory <b>116</b>. When these data <b>370</b> and <b>374</b> are stored in the non-volatile memory <b>116</b>, the point of interest (POI) proximity reminder routine (<b>400</b> in FIG. 2) is run. A flowchart showing a general process of the POI proximity reminder routine <b>400</b> is shown in FIG. 9. The POI proximity reminder routine <b>400</b> runs in the background and is configured so as not to interfere with other higher priority processes that are being performed by the navigation system <b>110</b>.
P-0059[0059] Referring to FIG. 9, a first step <b>410</b> of the POI proximity reminder routine <b>400</b> obtains the POI category type selection data <b>370</b> and the threshold data <b>374</b>, if any, from the user data <b>372</b>. Then, the routine obtains data indicating the current vehicle position (Step <b>420</b>). Data indicating the current vehicle position are obtained from the vehicle positioning application <b>148</b> (shown in FIGS. 2 and 9). Using the POI category type data <b>370</b>, the threshold data <b>374</b>, and the vehicle position data, the process searches the point of interest data <b>169</b> in the geographic database <b>162</b> to identify all the points of interest of the selected type that are within the specified threshold of the current vehicle position (Step <b>430</b>). (Note that if a travel time threshold or other type of threshold other than a distance threshold is used, the process may call other routines to identify the points of interest of the selected type that are within the applicable threshold from the current vehicle position.)
P-0060[0060] If there are no points of interest of the selected type within the threshold from the current vehicle position, the process loops back to the step of obtaining an updated vehicle position (Step <b>436</b>). However, if there are points of interest of the selected type within the threshold from the current vehicle position, the process <b>400</b> displays information to the user identifying the points of interest and requests the user whether route guidance to any of the identified points of interest is desired (Step <b>440</b>). FIG. 10 shows an image <b>500</b> provided by the POI proximity reminder routine <b>400</b> on the display <b>132</b> of the navigation system <b>110</b> for these purposes.
P-0061[0061] In FIG. 10, the image <b>500</b> contains a map <b>504</b> of the roads in the area around the vehicle. An image <b>506</b> of the vehicle is superimposed on the map image <b>504</b>. Also superimposed on the map image <b>504</b> are images <b>520</b> indicating the locations of points of interest of the specified type relative to the road network and the vehicle. Associated with each image of the location of the points of interest are data <b>530</b> indicating data about the respective point of interest. For example, the data <b>530</b> may indicate the distance to the point of interest from the current position of the vehicle and/or the travel time to the point of interest from the current position of the vehicle.
P-0062[0062] The image <b>500</b> also includes a message <b>540</b> indicating to the user that one or more points of interest of the specified type are in proximity to the current position of the vehicle. The message <b>540</b> may also include an indication of the type of point of interest category being displayed. In the example shown in FIG. 10, the message <b>540</b> states “REMINDER! POST OFFICES IN PROXIMITY.”
P-0063[0063] In the embodiment of FIG. 10, the image <b>500</b> also includes a message <b>550</b> prompting the user to indicate whether he/she would like route guidance to any of the indicated points of interest. If the user wants route guidance to one of the indicated points of interest, he/she can so indicate by pressing the “SELECT” key <b>336</b>. Otherwise, the user can indicate that he/she does not want route guidance to any of the indicated points of interest by pressing the “CANCEL” key or by waiting a few seconds without responding which is taken by the POI reminder routine <b>400</b> as a negative response.
P-0064[0064] Referring again to FIG. 9, if the user does not want to be guided to any of the indicated points of interest, the POI proximity reminder routine <b>400</b> obtains an indication from the user whether reminders about additional points of interest of the specified type should be provided during the current driving session if any such additional points of interest of the specified type are encountered (Step <b>460</b>). If the user indicates that no more reminders are desired, the POI proximity reminder routine <b>400</b> stops operating for the remainder of the driving session or until it is restarted (Step <b>470</b>). On the other hand, if the user indicates that reminders about additional points of interest are desired, the process loops back to the step (Step <b>420</b>) to obtain a new vehicle position.
P-0065[0065] Referring back to Step <b>456</b> in FIG. 9, if the user responds positively to the message (<b>550</b> in FIG. 10) indicating that he/she wants route guidance to one of the indicated points of interest, the POI proximity selection routine <b>400</b> prompts the user to select one of the points of interest to which route guidance will be provided. FIG. 11 shows an image <b>600</b> provided by the POI proximity reminder routine <b>400</b> on the display <b>132</b> of the navigation system <b>110</b> for this purpose. In FIG. 11, the image <b>600</b> contains the map <b>504</b>, the image <b>506</b> of the vehicle, and images <b>520</b> of the points of interest.
P-0066[0066] The image <b>600</b> also includes a message <b>616</b> indicating to the user that one point of interest of the specified type is to be selected. In the example shown in FIG. 11, the message <b>616</b> states “CHOOSE ONE POST OFFICE FOR ROUTE GUIDANCE.” Associated with an image of one of the point of interest locations is a highlighting box <b>620</b>. The highlighting box <b>620</b> can be moved from one image <b>520</b> of a point of interest to another by appropriate manipulation of the user interface controls (e.g., toggle <b>332</b>). In the embodiment of FIG. 11, the image <b>600</b> also includes a message <b>650</b> indicating to the user to press the “SELECT” key <b>336</b> to obtain route guidance for the point of interest associated with the highlighting box <b>620</b>.
P-0067[0067] When the highlighting box <b>620</b> is associated with the desired point of interest, the user selects the point of interest by pressing the “SELECT” key <b>336</b>. When the user has selected one of the points of interest, the POI proximity reminder routine <b>400</b> calls the route calculation application <b>142</b> and the route guidance application <b>144</b> to provide the user with guidance for traveling to the selected point of interest. After the user has been guided to the selected point of interest, the POI proximity reminder routine <b>400</b> obtains input from the user indicating whether the user would like to continue obtaining reminders about this type of point of interest. If the user indicates positively, the POI proximity reminder routine <b>400</b> loops back to the step of obtaining a new vehicle position. Otherwise, if the user indicates negatively, the POI proximity reminder routine <b>400</b> stops. In addition, if the user had been receiving guidance for traveling to a destination before receiving the reminder about being in proximity to a POI of a selected type, the POI proximity reminder routine <b>400</b> obtains input from the user indicating whether the user would like to resume traveling to the destination. If the user responds affirmatively, the POI proximity reminder routine <b>400</b> calls the route calculation application <b>142</b> and the route guidance application <b>144</b> to calculate a route from the location of the POI to the destination and provide the user with guidance for following the route.
P-0068[0068] If only one point of interest of the specified type is found in proximity to the current vehicle position, the step of having the user choose one point of interest for which route guidance is to be provided can be omitted.
P-0069[0069] In alternative embodiments, the POI proximity reminder routine <b>400</b> can be used to obtain reminder about more than one type of point of interest. If reminders are desired about more than one type of point of interest, the different types of points of interest can be displayed together or alternatively, the different types of points of interest can be displayed separately, e.g., one after the other.
P-0070[0070] E. Alternative Embodiments
P-0071[0071] The POI proximity reminder feature is described as being included in a navigation system. A navigation system can be a vehicle navigation system or any software application installed on a computer platform that provides navigation-related features and that uses geographic data. The POI proximity reminder feature can be provided on platforms including personal computers, networks (including wireless networks and the Internet), personal digital assistants, PalmPilot®-type devices, cellular telephones (including any type of portable telephone that uses any type of technology, such as PCS/GSM, and so on), pagers and other portable electronic devices.
P-0072[0072] The equipment that determines the location of the device that provides the POI proximity reminder feature can be located locally with the device or remotely. As described above, the equipment that determines the location of the device that provides the POI proximity reminder feature can include GPS equipment located locally with the device. Alternatively, the location of the device that provides the POI proximity reminder feature can be determined remotely using technologies like those used for determining locations of cellular phones in an area. There are various available technologies that provide this feature. Some of the companies that provide this type of technology include ArrayComm, Inc., Harris Corporation, Corsair Communications, Lockheed Martin Corporation, CELLTRAX, Inc., TruePosition, Inc., Cell-Loc Inc., KSI Inc., and U.S. Wireless Corporation. Some of these technologies can be used to locate a cellular phone user who dials an emergency number, e.g., “911.” Any such technology that is presently available or that becomes available in the future may be suitable.
P-0073[0073] In another alternative embodiment, a proximity reminder feature in a navigation system can incorporate real-time information. With real-time information, the proximity reminder feature can provide a user with reminders about aspects of places that change relatively quickly. For example, according to this embodiment, the proximity reminder feature in a navigation system can be used to provide a user with a reminder when the user is close to a gas station at which the gasoline price is less than a certain user-specified amount. To incorporate real-time information, the navigation system receives real-time data from a data provider. The navigation system may receive this data via a wireless communications link. The real-time data relate to points of interest or other places in a geographic area. The points of interest or other places to which the real-time data relate may already be represented in the database used by the navigation system or alternatively, the real-time data may relate to new points of interest or places that are not already represented in the database used by the navigation system. The proximity reminder feature uses the real-time data in conjunction with the data indicating the locations of places to which the real-time data relate to determine when the user is close to a location to which the real-time data relate. For example, if the real-time information indicates the price of gasoline at gas stations in an area, the proximity reminder feature filters the data representing gas station points of interest to determine those gas stations offering gasoline below the user's specified threshold price and then provides a reminder to the user when the user is in proximity to one of the gas stations. Real-time information can be used by the proximity reminder feature in a navigation system for various other changeable aspects of points of interest. For example, real-time information can be used by the proximity reminder feature in a navigation system to remind the user when he/she is close to a hotel room less than a specified price. Real-time information can also be used by the proximity reminder feature in a navigation system to remind the user when he/she is close to a cinema at which a user-specified movie is showing. Real-time information can also be used by the proximity reminder feature in a navigation system to remind the user when he/she is close to a business at which a sale is underway.
P-0074[0074] It is intended that the foregoing detailed description be regarded as illustrative rather than limiting and that it is understood that the following claims including all equivalents are intended to define the scope of the invention.
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 |
|---|---|---|---|
| US8554477B2 | Cited by | United States of America | Applicant |
| WO2007115221A2 | Cited by | World Intellectual Property Organization (WIPO) | Search report |
| US2011077860A1 | Cited by | United States of America | Pre-grant |
| US8244278B2 | Cited by | United States of America | Applicant |
| US10827330B2 | Cited by | United States of America | Applicant |
| US2008186209A1 | Cited by | United States of America | Pre-grant |
| US9182895B1 | Cited by | United States of America | Applicant |
| US9891055B2 | Cited by | United States of America | Applicant |
| US7805150B2 | Cited by | United States of America | Search report |
| US2009187340A1 | Cited by | United States of America | Pre-grant |
| KR20200040927A | Cited by | Republic of Korea | Search report |
| US8731821B2 | Cited by | United States of America | Search report |
| US2008221787A1 | Cited by | United States of America | Pre-grant |
| US2019141494A1 | Cited by | United States of America | Search report |
| US2009037098A1 | Cited by | United States of America | Pre-grant |
| US2013110393A1 | Cited by | United States of America | Pre-grant |
| US12228411B2 | Cited by | United States of America | Applicant |
| US2014206397A1 | Cited by | United States of America | Pre-grant |
| US2010076674A1 | Cited by | United States of America | Pre-grant |
| US2004203840A1 | Cited by | United States of America | Pre-grant |
| US2011072005A1 | Cited by | United States of America | Pre-grant |
| US2008270468A1 | Cited by | United States of America | Pre-grant |
| US10038974B2 | Cited by | United States of America | Applicant |
| CN113226883A | Cited by | China | Search report |
| US10635287B2 | Cited by | United States of America | Applicant |
| USRE47985E | Cited by | United States of America | Search report |
| US2006041556A1 | Cited by | United States of America | Pre-grant |
| US11419092B2 | Cited by | United States of America | Applicant |
| US2014247348A1 | Cited by | United States of America | Pre-grant |
| US9074898B2 | Cited by | United States of America | Search report |
| US2007136259A1 | Cited by | United States of America | Pre-grant |
| US10508921B2 | Cited by | United States of America | Applicant |
| US8572077B2 | Cited by | United States of America | Applicant |
| US2008262728A1 | Cited by | United States of America | Pre-grant |
| US11819735B2 | Cited by | United States of America | Applicant |
| USRE47107E | Cited by | United States of America | Search report |
| US10458800B2 | Cited by | United States of America | Applicant |
| US12250262B2 | Cited by | United States of America | Applicant |
| US10955558B2 | Cited by | United States of America | Applicant |
| DE102010021933A1 | Cited by | Germany | Search report |
| US7743056B2 | Cited by | United States of America | Search report |
| US2007165474A1 | Cited by | United States of America | Pre-grant |
| US9752890B2 | Cited by | United States of America | Applicant |
| US10571577B2 | Cited by | United States of America | Applicant |
| US9625485B2 | Cited by | United States of America | Applicant |
| US2010088023A1 | Cited by | United States of America | Pre-grant |
| US2009187342A1 | Cited by | United States of America | Pre-grant |
| US11779810B2 | Cited by | United States of America | Applicant |
| US2004203847A1 | Cited by | United States of America | Pre-grant |
| US12114284B2 | Cited by | United States of America | Applicant |
| US8473193B2 | Cited by | United States of America | Search report |
| US8725176B2 | Cited by | United States of America | Applicant |
| US2007233658A1 | Cited by | United States of America | Pre-grant |
| US8219317B2 | Cited by | United States of America | Applicant |
| US2008249983A1 | Cited by | United States of America | Pre-grant |
| US8060499B2 | Cited by | United States of America | Search report |
| US9612126B2 | Cited by | United States of America | Search report |
| US2015312713A1 | Cited by | United States of America | Pre-grant |
| US7835863B2 | Cited by | United States of America | Applicant |
| US7941160B2 | Cited by | United States of America | Applicant |
| US10999802B2 | Cited by | United States of America | Applicant |
| US9818173B2 | Cited by | United States of America | Applicant |
| US9867014B2 | Cited by | United States of America | Applicant |
| US11070949B2 | Cited by | United States of America | Applicant |
| US9234762B2 | Cited by | United States of America | Applicant |
| US10062297B2 | Cited by | United States of America | Applicant |
| US2010248745A1 | Cited by | United States of America | Pre-grant |
| US12020588B2 | Cited by | United States of America | Applicant |
| US8069165B2 | Cited by | United States of America | Search report |
| US11272318B2 | Cited by | United States of America | Applicant |
| US10334532B2 | Cited by | United States of America | Applicant |
| US7406665B2 | Cited by | United States of America | Search report |
| US11040246B2 | Cited by | United States of America | Applicant |
| US11217341B2 | Cited by | United States of America | Applicant |
| US2008147319A1 | Cited by | United States of America | Pre-grant |
| US12105208B2 | Cited by | United States of America | Applicant |
| US8554476B2 | Cited by | United States of America | Applicant |
| DE102007028761A1 | Cited by | Germany | Search report |
| US2005107949A1 | Cited by | United States of America | Pre-grant |
| US2008065319A1 | Cited by | United States of America | Pre-grant |
| US8583365B2 | Cited by | United States of America | Search report |
| US8135538B2 | Cited by | United States of America | Search report |
| US2008086455A1 | Cited by | United States of America | Pre-grant |
| US7546202B2 | Cited by | United States of America | Search report |
| WO2013063480A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US11150354B2 | Cited by | United States of America | Applicant |
| US9618358B2 | Cited by | United States of America | Applicant |
| WO2013107669A1 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| US6973318B2 | Cited by | United States of America | Search report |
| US2003154022A1 | Cited by | United States of America | Pre-grant |
| US10064158B2 | Cited by | United States of America | Applicant |
| US2009070293A1 | Cited by | United States of America | Pre-grant |
| US10952180B2 | Cited by | United States of America | Applicant |
| US2009018770A1 | Cited by | United States of America | Pre-grant |
| US7461528B2 | Cited by | United States of America | Search report |
| US2014142842A1 | Cited by | United States of America | Pre-grant |
| US2012149395A1 | Cited by | United States of America | Pre-grant |
| US10509129B2 | Cited by | United States of America | Applicant |
| US2008009275A1 | Cited by | United States of America | Pre-grant |
| US2009182498A1 | Cited by | United States of America | Pre-grant |
3 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 52570100 | United States of America | A | |
| 52570100 | United States of America | A | |
| 40261003 | United States of America | A | |
| 09525701 | – | – | – |
| US20000525701 | – | – | – |
| US20030402610 | – | – | – |
Members3
| Document | Office | Kind | |
|---|---|---|---|
| US6587782B1 | United States of America | B1 | |
| US2003191578A1 | United States of America | A1 | |
| US6850837B2 | United States of America | B2 |
33 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Receipt into PubsR1021 | R1021 | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Receipt into PubsR1021 | R1021 | |
| Receipt into PubsR1021 | R1021 | |
| Workflow - File Sent to ContractorSENT | SENT | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Mail Paralegal TD AcceptedMP574 | MP574 | |
| Mail Examiner's AmendmentMEX.A | MEX.A | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Paralegal or electronic terminal disclaimer approvedP574 | P574 | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Terminal Disclaimer FiledDIST | DIST | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow incoming amendment IFWWAMD | WAMD | |
| Correspondence Address ChangeC.ADB | C.ADB | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Preliminary AmendmentA.PE | A.PE | |
| Initial Exam Team nnIEXX | IEXX |
10 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 2003191578
- Publication, EPODOC
- US2003191578
- Application
- 10402610
- Application, DOCDB
- 40261003
- Application, EPODOC
- US20030402610
Titles
- English
- Method and system for providing reminders about points of interests while traveling
Patent term adjustment
- A delay
- +6 daysthe office missed an examination deadline
- Applicant delay
- −92 days
- Net adjustment
- 0 days
Classification
- CPC, 2
- G01C21/3682
- G01C21/3614
- IPC, 1
- G01C21 36
- USPC, 2
- 701438000
- 340995240