PATENT DOCUMENT

Publication Number: US-8762056-B2
Application Number: US-2675108-A
Country: US
Kind Code: B2

Title: Route reference

Abstract:
A user input is received on a wireless device specifying a starting location. The position of the wireless device is tracked from the starting location in response to the user input. A user input is received on the wireless device specifying an ending location, and a route is generated from the tracking of the wireless device from the starting location to the ending location. A first reference is associated with the route, wherein the route is retrievable by a selection of the first reference.

Claims:
The invention claimed is: 
     
       1. A method, comprising:
 receiving, through a user interface implemented by a mobile device, a first input specifying a starting location, wherein the mobile device is a handheld device that includes telephony and a display for displaying a route in the user interface; 
 tracking a position of the mobile device from the starting location in response to receiving the first input; 
 receiving, through the user interface implemented by the mobile device, a second input specifying a first ending location; 
 generating a route from the tracking of the mobile device from the starting location to the ending location; 
 associating a first reference with the route, wherein the route is retrievable by a selection of the first reference; 
 saving the route and the associated first reference on the mobile device; 
 retrieving the saved route in response to receiving a third input specifying the first reference; 
 displaying the route in the user interface of the mobile device display; 
 while navigating the route, receiving a fourth input indicating that the route is to be edited; and 
 in response to receiving the fourth input, modifying the route by tracking the position of the mobile device from a location of the mobile device on the route when the fourth input was received to a second ending location. 
 
     
     
       2. The method of  claim 1 , wherein the first ending location is different than the second ending location. 
     
     
       3. The method of  claim 1 , further comprising:
 associating the modified route with a second reference; and 
 saving the modified route and the associated second reference on the mobile device. 
 
     
     
       4. The method of  claim 1 , further comprising:
 receiving information indicative of real-time traffic information. 
 
     
     
       5. The method of  claim 4 , further comprising:
 receiving a user input specifying an edit location indicator; 
 displaying the real-time traffic information; and 
 modifying the route based on the real-time traffic information. 
 
     
     
       6. The method of  claim 1 , wherein the first reference is associated with one or more names. 
     
     
       7. The method of  claim 1 , wherein the mobile device is GPS-enabled. 
     
     
       8. The method of  claim 1 , wherein the mobile device is adapted to communicate with a vehicular on-board navigation system. 
     
     
       9. The method of  claim 1 , wherein the first input is determined automatically based on a current position of the mobile device and displayed in the user interface. 
     
     
       10. The method of  claim 6 , wherein the first reference and the second reference each comprise one or more parameters associated with the route. 
     
     
       11. The method of  claim 1 , further comprising:
 displaying the route and the first reference as an overlay on a map displayed in the user interface of the mobile device display. 
 
     
     
       12. The method of  claim 1 , wherein generating the route comprises:
 retrieving data representing user preferences from a data store; and 
 generating the route based in part on the retrieved data. 
 
     
     
       13. The method of  claim 1 , further comprising sending the route to another mobile device in an SMS message. 
     
     
       14. A system, comprising:
 one or more processors; and 
 a computer-readable medium including one or more sequences of instructions which, when executed by the one or more processors, causes: 
 receiving, through a user interface implemented by a mobile device, a first input specifying a starting location, wherein the mobile device is a handheld device that includes telephony and a display for displaying a route in the user interface; 
 tracking a position of the mobile device from the starting location in response to receiving the first input; 
 receiving, through the user interface implemented by the mobile device, a second input specifying a first ending location; 
 generating a route from the tracking of the mobile device from the starting location to the ending location; 
 associating a first reference with the route, wherein the route is retrievable by a selection of the first reference; 
 saving the route and the associated first reference on the mobile device; 
 retrieving the saved route in response to receiving a third input specifying the first reference; 
 displaying the route in the user interface of the mobile device display; 
 while navigating the route, receiving a fourth input indicating that the route is to be edited; and 
 in response to receiving the fourth input, modifying the route by tracking the position of the mobile device from a location of the mobile device on the route when the fourth input was received to a second ending location. 
 
     
     
       15. The system of  claim 14 , wherein the first ending location is different than the second ending location. 
     
     
       16. The system of  claim 14 , wherein the instructions cause:
 associating the modified route with a second reference; and 
 saving the modified route and the associated second reference on the mobile device. 
 
     
     
       17. The system of  claim 14 , wherein the instructions cause:
 receiving information indicative of real-time traffic information. 
 
     
     
       18. The system of  claim 17 , wherein the instructions cause:
 receiving a user input specifying an edit location indicator; 
 displaying the real-time traffic information; and 
 modifying the route based on the real-time traffic information. 
 
     
     
       19. The system of  claim 14 , wherein the first reference is associated with one or more names. 
     
     
       20. The system of  claim 14 , wherein the mobile device is GPS-enabled. 
     
     
       21. The system of  claim 14 , wherein the mobile device is adapted to communicate with a vehicular on-board navigation system. 
     
     
       22. The system of  claim 14 , wherein the first input is determined automatically based on a current position of the mobile device and displayed in the user interface. 
     
     
       23. The system of  claim 19 , wherein the first reference and the second reference each comprise one or more parameters associated with the route. 
     
     
       24. The system of  claim 14 , wherein the instructions cause:
 displaying the route and the first reference as an overlay on a map displayed in the user interface of the mobile device display. 
 
     
     
       25. The system of  claim 14 , wherein the instructions that cause generating the route comprise instructions that cause:
 retrieving data representing user preferences from a data store; and 
 generating the route based in part on the retrieved data. 
 
     
     
       26. The system of  claim 14 , wherein the instructions cause sending the route to another mobile device in an SMS message.

Description:
CROSS-REFERENCE TO RELATED APPLICATION 
     This application claims priority to U.S. Provisional Patent Application Ser. No. 60/946,771 filed Jun. 28, 2007, and entitled “ROUTE REFERENCE,” the contents of which are incorporated herein by reference. 
    
    
     BACKGROUND 
     This disclosure relates to navigation using a mobile device. 
     Navigation systems have historically provided little intelligence other than the ability to navigate from an origination point to a destination point. Some navigation systems include functionality for using traffic information in navigating from the origination point to the destination point. Other systems have also provided more than one route for a user based on an origination and destination point, and allowed the user to select one of the routes. However, these systems do not allow the users to interact with the routes nor change the routes in any way. 
     Thus, the navigation system adds little value outside of providing a map to the user. Such problems with navigation systems can undermine a user&#39;s desire to use the navigation system. 
     SUMMARY 
     Disclosed herein are systems and methods for generating a route. In one implementation, a user input is received on a wireless device specifying a starting location. The position of the wireless device is tracked from the starting location in response to the user input. A user input is received on the wireless device specifying an ending location, and a route is generated from the tracking of the wireless device from the starting location to the ending location. A first reference is associated with the route, wherein the route is retrievable by a selection of the first reference. 
     In another implementation, an input is received specifying a first location, and an input is received specifying a second location. A travel route is computed between the first and second locations. An edit is received associated with the travel route, and the travel route is edited on the wireless device in accordance with the edit. 
     In another implementation, a user input is received on a wireless device specifying a starting location. A user input is received on the wireless device specifying an ending location. One or more routes are generated from the starting location to the ending location. User input is received on the wireless device selecting one or the one or more routes. A first reference is associated with the selected route, wherein the selected route is retrievable by a selection of the first reference. 
     In another implementation, a system includes a location engine for a wireless device that produces information indicative of a plurality of locations. The system also includes a route engine that receives information indicative of a first location, tracks a position of the wireless device from the first location in response to the information, receives information indicative of a second location, generates a route from the first location to the second location in accordance with the tracking of the wireless device, receives information indicative of en edit, and edits the route by tracking the position of the wireless device to the second location, wherein the route is associated with a reference. 
    
    
     
       DESCRIPTION OF DRAWINGS 
         FIG. 1  is a block diagram of an example mobile device. 
         FIG. 2  is a block diagram of an example network operating environment for the mobile device of  FIG. 1 . 
         FIG. 3  is a block diagram of an example implementation of the mobile device of  FIG. 1 . 
         FIG. 4  is a block diagram illustrating an example operation of routing instructions. 
         FIG. 5  is a block diagram of an example mobile device using a route reference. 
         FIG. 6  is an example process for generating a route. 
         FIG. 7  is another example process for generating a route. 
         FIG. 8  is an example process for editing a route. 
     
    
    
     DETAILED DESCRIPTION 
       FIG. 1  is a block diagram of an example mobile device  100 . The mobile device  100  can be, for example, a handheld computer, a personal digital assistant, a cellular telephone, a network appliance, a camera, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a network base station, a media player, a navigation device, an email device, a game console, or a combination of any two or more of these data processing devices or other data processing devices. 
     Mobile Device Overview 
     In some implementations, the mobile device  100  includes a touch-sensitive display  102 . The touch-sensitive display  102  can implement liquid crystal display (LCD) technology, light emitting polymer display (LPD) technology, or some other display technology. The touch-sensitive display  102  can be sensitive to haptic and/or tactile contact with a user. 
     In some implementations, the touch-sensitive display  102  can comprise a multi-touch-sensitive display  102 . A multi-touch-sensitive display  102  can, for example, process multiple simultaneous touch points, including processing data related to the pressure, degree and/or position of each touch point. Such processing facilitates gestures and interactions with multiple fingers, chording, and other interactions. Other touch-sensitive display technologies can also be used, e.g., a display in which contact is made using a stylus or other pointing device. Some examples of multi-touch-sensitive display technology are described in U.S. Pat. Nos. 6,323,846, 6,570,557, 6,677,932, and U.S. Patent Publication 2002/0015024A1, each of which is incorporated by reference herein in its entirety. 
     In some implementations, the mobile device  100  can display one or more graphical user interfaces on the touch-sensitive display  102  for providing the user access to various system objects and for conveying information to the user. In some implementations, the graphical user interface can include one or more display objects  104 ,  106 . In the example shown, the display objects  104 ,  106 , are graphic representations of system objects. Some examples of system objects include device functions, applications, windows, files, alerts, events, or other identifiable system objects. 
     Exemplary Mobile Device Functionality 
     In some implementations, the mobile device  100  can implement multiple device functionalities, such as a telephony device, as indicated by a phone object  110 ; an e-mail device, as indicated by the e-mail object  112 ; a network data communication device, as indicated by the Web object  114 ; a Wi-Fi base station device (not shown); and a media processing device, as indicated by the media player object  116 . In some implementations, particular display objects  104 , e.g., the phone object  110 , the e-mail object  112 , the Web object  114 , and the media player object  116 , can be displayed in a menu bar  118 . In some implementations, device functionalities can be accessed from a top-level graphical user interface, such as the graphical user interface illustrated in  FIG. 1 . Touching one of the objects  110 ,  112 ,  114  or  116  can, for example, invoke corresponding functionality. 
     In some implementations, the mobile device  100  can implement network distribution functionality. For example, the functionality can enable the user to take the mobile device  100  and its associated network while traveling. In particular, the mobile device  100  can extend Internet access (e.g., Wi-Fi) to other wireless devices in the vicinity. For example, mobile device  100  can be configured as a base station for one or more devices. As such, mobile device  100  can grant or deny network access to other wireless devices. 
     In some implementations, upon invocation of device functionality, the graphical user interface of the mobile device  100  changes, or is augmented or replaced with another user interface or user interface elements, to facilitate user access to particular functions associated with the corresponding device functionality. For example, in response to a user touching the phone object  110 , the graphical user interface of the touch-sensitive display  102  may present display objects related to various phone functions; likewise, touching of the email object  112  may cause the graphical user interface to present display objects related to various e-mail functions; touching the Web object  114  may cause the graphical user interface to present display objects related to various Web-surfing functions; and touching the media player object  116  may cause the graphical user interface to present display objects related to various media processing functions. 
     In some implementations, the top-level graphical user interface environment or state of  FIG. 1  can be restored by pressing a button  120  located near the bottom of the mobile device  100 . In some implementations, each corresponding device functionality may have corresponding “home” display objects displayed on the touch-sensitive display  102 , and the graphical user interface environment of  FIG. 1  can be restored by pressing the “home” display object. 
     In some implementations, the top-level graphical user interface can include additional display objects  106 , such as a short messaging service (SMS) object  130 , a calendar object  132 , a photos object  134 , a camera object  136 , a calculator object  138 , a stocks object  140 , a weather object  142 , a maps object  144 , a notes object  146 , a clock object  148 , an address book object  150 , and a settings object  152 . Touching the SMS display object  130  can, for example, invoke an SMS messaging environment and supporting functionality; likewise, each selection of a display object  132 ,  134 ,  136 ,  138 ,  140 ,  142 ,  144 ,  146 ,  148 ,  150  and  152  can invoke a corresponding object environment and functionality. 
     Additional and/or different display objects can also be displayed in the graphical user interface of  FIG. 1 . For example, if the device  100  is functioning as a base station for other devices, one or more “connection” objects may appear in the graphical user interface to indicate the connection. In some implementations, the display objects  106  can be configured by a user, e.g., a user may specify which display objects  106  are displayed, and/or may download additional applications or other software that provides other functionalities and corresponding display objects. 
     In some implementations, the mobile device  100  can include one or more input/output (I/O) devices and/or sensor devices. For example, a speaker  160  and a microphone  162  can be included to facilitate voice-enabled functionalities, such as phone and voice mail functions. In some implementations, a loud speaker  164  can be included to facilitate hands-free voice functionalities, such as speaker phone functions. An audio jack  166  can also be included for use of headphones and/or a microphone. 
     In some implementations, a proximity sensor  168  can be included to facilitate the detection of the user positioning the mobile device  100  proximate to the user&#39;s ear and, in response, to disengage the touch-sensitive display  102  to prevent accidental function invocations. In some implementations, the touch-sensitive display  102  can be turned off to conserve additional power when the mobile device  100  is proximate to the user&#39;s ear. 
     Other sensors can also be used. For example, in some implementations, an ambient light sensor  170  can be utilized to facilitate adjusting the brightness of the touch-sensitive display  102 . In some implementations, an accelerometer  172  can be utilized to detect movement of the mobile device  100 , as indicated by the directional arrow  174 . Accordingly, display objects and/or media can be presented according to a detected orientation, e.g., portrait or landscape. In some implementations, the mobile device  100  may include circuitry and sensors for supporting a location determining capability, such as that provided by the global positioning system (GPS) or other positioning systems (e.g., systems using Wi-Fi access points, television signals, cellular grids, Uniform Resource Locators (URLs)). In some implementations, a positioning system (e.g., a GPS receiver) can be integrated into the mobile device  100  or provided as a separate device that can be coupled to the mobile device  100  through an interface (e.g., port device  190 ) to provide access to location-based services. 
     The mobile device  100  can also include a camera lens and sensor  180 . In some implementations, the camera lens and sensor  180  can be located on the back surface of the mobile device  100 . The camera can capture still images and/or video. 
     The mobile device  100  can also include one or more wireless communication subsystems, such as an 802.11b/g communication device  186 , and/or a Bluetooth™ communication device  188 . Other communication protocols can also be supported, including other 802.x communication protocols (e.g., WiMax, Wi-Fi, 3G), code division multiple access (CDMA), global system for mobile communications (GSM), Enhanced Data GSM Environment (EDGE), etc. 
     In some implementations, a port device  190 , e.g., a Universal Serial Bus (USB) port, or a docking port, or some other wired port connection, can be included. The port device  190  can, for example, be utilized to establish a wired connection to other computing devices, such as other communication devices  100 , network access devices, a personal computer, a printer, or other processing devices capable of receiving and/or transmitting data. In some implementations, the port device  190  allows the mobile device  100  to synchronize with a host device using one or more protocols, such as, for example, the TCP/IP, HTTP, UDP and any other known protocol. In some implementations, a TCP/IP over USB protocol can be used. 
     Network Operating Environment 
       FIG. 2  is a block diagram of an example network operating environment  200  for the mobile device  100  of  FIG. 1 . The mobile device  100  of  FIG. 1  can, for example, communicate over one or more wired and/or wireless networks  210  in data communication. For example, a wireless network  212 , e.g., a cellular network, can communicate with a wide area network (WAN)  214 , such as the Internet, by use of a gateway  216 . Likewise, an access point  218 , such as an 802.11g wireless access point, can provide communication access to the wide area network  214 . In some implementations, both voice and data communications can be established over the wireless network  212  and the access point  218 . For example, the mobile device  100   a  can place and receive phone calls (e.g., using VoIP protocols), send and receive e-mail messages (e.g., using POP3 protocol), and retrieve electronic documents and/or streams, such as web pages, photographs, and videos, over the wireless network  212 , gateway  216 , and wide area network  214  (e.g., using TCP/IP or UDP protocols). Likewise, the mobile device  100   b  can place and receive phone calls, send and receive e-mail messages, and retrieve electronic documents over the access point  218  and the wide area network  214 . In some implementations, the mobile device  100  can be physically connected to the access point  218  using one or more cables and the access point  218  can be a personal computer. In this configuration, the mobile device  100  can be referred to as a “tethered” device. 
     The mobile devices  100   a  and  100   b  can also establish communications by other means. For example, the wireless device  100   a  can communicate with other wireless devices, e.g., other wireless devices  100 , cell phones, etc., over the wireless network  212 . Likewise, the mobile devices  100   a  and  100   b  can establish peer-to-peer communications  220 , e.g., a personal area network, by use of one or more communication subsystems, such as the Bluetooth™ communication device  188  shown in  FIG. 1 . Other communication protocols and topologies can also be implemented. 
     The mobile device  100  can, for example, communicate with one or more services  230 ,  240 ,  250 , and  260  and/or one or more content publishers  270  over the one or more wired and/or wireless networks  210 . For example, a navigation service  230  can provide navigation information, e.g., map information, location information, route information, and other information, to the mobile device  100 . In the example shown, a user of the mobile device  100   b  has invoked a map functionality, e.g., by pressing the maps object  144  on the top-level graphical user interface shown in  FIG. 1 , and has requested and received a map for the location “1 Infinite Loop, Cupertino, Calif.” 
     A messaging service  240  can, for example, provide e-mail and/or other messaging services. A media service  250  can, for example, provide access to media files, such as song files, movie files, video clips, and other media data. One or more other services  260  can also be utilized by the mobile device  100 . 
     The mobile device  100  can also access other data and content over the one or more wired and/or wireless networks  210 . For example, content publishers, e.g., content publisher(s)  270 , such as news sites, RSS feeds, web sites, blogs, social networking sites, developer networks, etc., can be accessed by the mobile device  100 . Such access can be provided by invocation of a web browsing function or application (e.g., a browser) in response to a user touching the Web object  114 . 
     Exemplary Mobile Device Architecture 
       FIG. 3  is a block diagram  300  of an example implementation of the mobile device  100  of  FIG. 1 . The mobile device  100  can include a memory interface  302 , one or more data processors, image processors and/or central processing units  304 , and a peripherals interface  306 . The memory interface  302 , the one or more processors  304  and/or the peripherals interface  306  can be separate components or can be integrated in one or more integrated circuits. The various components in the mobile device  100  can be coupled by one or more communication buses or signal lines. 
     Sensors, devices and subsystems can be coupled to the peripherals interface  306  to facilitate multiple functionalities. For example, a motion sensor  310 , a light sensor  312 , and a proximity sensor  314  can be coupled to the peripherals interface  306  to facilitate the orientation, lighting and proximity functions described with respect to  FIG. 1 . Other sensors  316  can also be connected to the peripherals interface  306 , such as a positioning system (e.g., GPS receiver), a temperature sensor, a biometric sensor, or other sensing device, to facilitate related functionalities. 
     In some implementations, the mobile device can receive positioning information from a positioning system  318 . The positioning system  318 , in various implementations, can be located on the mobile device, or can be coupled to the mobile device (e.g., using a wired connection or a wireless connection). In some implementations, the positioning system  318  can include a global positioning system (GPS) receiver and a positioning engine operable to derive positioning information from received GPS satellite signals. In other implementations, the positioning system  318  can include a compass and an accelerometer, as well as a positioning engine operable to derive positioning information based on dead reckoning techniques. In still further implementations, the positioning system  318  can use wireless signals to determine location information associated with the mobile device. Other positioning systems are possible. In still other implementations, the user can enter a set of position coordinates (e.g., latitude, longitude) for the mobile device. For example, the position coordinates can be typed into the phone (e.g., using a virtual keyboard) or selected by touching a point on a map. Position coordinates can also be acquired from another device (e.g., a car navigation system) by syncing or linking with the other device. 
     A camera subsystem  320  and an optical sensor  322 , e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, can be utilized to facilitate camera functions, such as recording photographs and video clips. 
     Communication functions can be facilitated through one or more wireless communication subsystems  324 , which can include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. The specific design and implementation of the communication subsystem  324  can depend on the communication network(s) over which the mobile device  100  is intended to operate. For example, a mobile device  100  may include communication subsystems  324  designed to operate over a GSM network, a GPRS network, an EDGE network, a Wi-Fi or WiMax network, and a Bluetooth™ network. In particular, the wireless communication subsystems  324  may include hosting protocols such that the device  100  may be configured as a base station for other wireless devices. 
     An audio subsystem  326  can be coupled to a speaker  328  and a microphone  330  to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions. 
     The I/O subsystem  340  can include a touch screen controller  342  and/or other input controller(s)  344 . The touch-screen controller  342  can be coupled to a touch screen  346 . The touch screen  346  and touch screen controller  342  can, for example, detect contact and movement or break thereof using any of a plurality of touch sensitivity technologies, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen  346 . 
     The other input controller(s)  344  can be coupled to other input/control devices  348 , such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) can include an up/down button for volume control of the speaker  328  and/or the microphone  330 . 
     In one implementation, a pressing of the button for a first duration may disengage a lock of the touch screen  346 ; and a pressing of the button for a second duration that is longer than the first duration may turn power to the mobile device  100  on or off. The user may be able to customize a functionality of one or more of the buttons. The touch screen  346  can, for example, also be used to implement virtual or soft buttons and/or a keyboard. 
     In some implementations, the mobile device  100  can present recorded audio and/or video files, such as MP3, AAC, and MPEG files. In some implementations, the mobile device  100  can include the functionality of an MP3 player, such as an iPod™. The mobile device  100  may, therefore, include a 36-pin connector that is compatible with the iPod. Other input/output and control devices can also be used. 
     The memory interface  302  can be coupled to memory  350 . The memory  350  can include high-speed random access memory and/or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, and/or flash memory (e.g., NAND, NOR). The memory  350  can store an operating system  352 , such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or an embedded operating system such as VxWorks. The operating system  352  may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, the operating system  352  can be a kernel (e.g., UNIX kernel). 
     The memory  350  may also store communication instructions  354  to facilitate communicating with one or more additional devices, one or more computers and/or one or more servers. The memory  350  may include graphical user interface instructions  356  to facilitate graphic user interface processing; sensor processing instructions  358  to facilitate sensor-related processing and functions; phone instructions  360  to facilitate phone-related processes and functions; electronic messaging instructions  362  to facilitate electronic-messaging related processes and functions; web browsing instructions  364  to facilitate web browsing-related processes and functions; media processing instructions  366  to facilitate media processing-related processes and functions; GPS/Navigation instructions  368  to facilitate GPS and navigation-related processes and instructions; camera instructions  370  to facilitate camera-related processes and functions; and/or other software instructions  372  to facilitate other processes and functions. 
     Each of the above identified instructions and applications can correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures or modules. The memory  350  can include additional instructions or fewer instructions. Furthermore, various functions of the mobile device  100  may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits. 
       FIG. 4  is a block diagram illustrating example routing instructions to facilitate proving navigation guidance to a user. The routing instructions can include a route engine  410 , a presentation engine  420 , an editor engine  430 , a map system  440 , a user interface  450 , and a positioning system  318 . The routing instructions  372  can receive input specifying a starting location  460  and an ending location  462  can generate a route using the starting location  460  and ending location  462 . The routing instructions  372  can, for example, associate a reference with the generated route to be used in, for example, storing and retrieving the generated route. In one implementation, the routing instructions  372  can edit a previously created route. 
     In one implementation, a user input can, for example, be received on a mobile device  100  specifying a starting location for a route. The input can, for example, be received on the user interface  450 . The mobile device  100  can, for example, provide the route to a user of the mobile device  100 . The starting location  460  can, for example, correspond to a geographic location that is used to generate a route, and can be input manually by a user of the mobile device  100  based on the starting location. The input can, for example, be received on the user interface  450 . The user can, for example, input an address corresponding to the starting location  460 . The address can, for example, include a street number, street name, city, state and zip code. In one implementation, the starting location  460  can be indicated by a landmark, e.g., an airport or airport code. 
     In one implementation, the route engine  410  can automatically derive the starting location information using the current location as the starting location  460 . For example, the user of the mobile device  100  can decide to navigate to a particular location from a current location. The mobile device  100  can receive an indication as to whether automatically derive the starting location  460  information. The route engine  410  can derive starting information using the positioning system  318  when the indication is received to use the current location as the starting location  460 . 
     In one implementation, the positioning system  318  can be a global positioning system (GPS) device. In other implementations, the positioning system  318  can be provided by an accelerometer and a compass using dead reckoning techniques. In such implementations, the positioning system can be reset by marking the device&#39;s presence at a known location (e.g., landmark, intersection, etc.). In still further implementations, the positioning system  318  can be provided by using wireless signal strength and one or more locations of known wireless signal sources to provide current location. Wireless signal sources can include access points and/or cellular towers. Other positioning systems are possible. For example, a user may be driving in a car with the mobile device  100  and decide to use the mobile device  100  to generate a route to a specific destination. The route engine  410  can automatically derive the starting location  460  of the mobile device  100  by the positioning system  318 . The mobile device  100  can automatically derive the starting location  460  information in response to a user input. 
     In one implementation, the route engine  410  can track a position of the mobile device  100  from the starting location  460  in response to the user input. The position of the mobile device  100  can, for example, be tracked in conjunction with the positioning system  318 . In various implementations, the positioning system  318  can be provided by a separate device coupled to the mobile device (e.g., mobile device  100  of  FIG. 1 ). In other implementations, the positioning system  318  can be provided internal to the mobile device. 
     The route engine  410  can, for example, start tracking the position of the mobile device  100  until an indication is received to stop tracking. For example, as the user in the above example moves from the starting location  460 , the route engine  410  tracks the position of the mobile device  100  until an indication is received to end tracking of the mobile device  100 . 
     In one implementation, user input can be received on the mobile device  100  specifying an ending location  462 . The route engine  410  can stop tracking the mobile device  100  upon receipt of the user input specifying the ending location  462 . The ending location  462  can, for example, be input manually by the user of the mobile device  100 . The mobile device  100  can, for example, receive an address corresponding to the ending location  462  in response to a user input. In one implementation, the ending location  462  can, for example, be automatically derived by the route engine  410 . The mobile device  100  can receive the ending location  462  as the current location of the mobile device  100  in response to a user input. The route engine  410  can derive the ending location  462  using the current location and the positioning system  318 . 
     A route can include route guidelines including streets distances, landmarks, etc. that were taken while navigating from the starting location  460  to the ending location  462 . Based on the complexity of a route, the route can include many route guidelines. Route guidelines, in some implementations, can include a discrete length of road which comprises a route. The route can, for example, include navigating directions from the starting location  460  to the ending location  462 . 
     The route engine  410  can provide the route tracked to a presentation engine  420 . The presentation engine can, for example, communicate with a map system  440 . In some implementations, the map system  440  can be provided, for example, by a navigation service (e.g., navigation service  230  of  FIG. 2 ). In other implementations, the map system  440  can be provided by a map store residing on the mobile device (e.g., mobile device  100  of  FIG. 1 ). The presentation engine  420  can use the map provided by the map system  440  to overlay the route information. 
     In other implementations, the route can be overlayed on a map provided by a local map information store. In some implementations, the map includes a number of road representations. The road representations, for example, can be overlayed by traffic information  464  associated with respective route progressions. Traffic information  464  can be indicated, for example, by color coding on or alongside road representations, pushpin messages associated with road representations, traffic animations associated with road representation, etc. The presentation of the route can enable a user of the mobile device to navigate from a current location to an ending location  462 . For example, the route the user took from the starting location  460  to the ending location  462  can be saved by the route engine  410  and displayed on the presentation engine  420 . 
     In some implementations, the one or more routes can be generated based upon user preferences retrieved from a data store in conjunction with the user specified starting locations  460  and ending locations  462 . User preference information  466 , for example, might indicate a user preference for types of roads, distance, traffic, traffic control devices (e.g., traffic lights, stop signs, rotaries, etc.), time, preferred routes, neighborhoods, etc. 
     In one implementation, the route engine  410  can generate one or more routes based upon traffic information  464 . The traffic information  464  can be retrieved, for example, from a traffic information  464  service. In some implementations, the traffic information  464  service can be provided by a government or commercial service provider. 
     In one implementation any of the generated routes can be selected as the route to navigate. The route engine  410  can, for example, provide the route selected to a presentation engine  420 . The presentation engine  420  can, for example, communicate with a map system  440 . In some implementations, the map system  440  can be provided, for example, by a navigation service (e.g., navigation service  230  of  FIG. 2 ). In other implementations, the map system  440  can be provided by a map store residing on the mobile device (e.g., mobile device  100  of  FIG. 1 ). The presentation engine  420  can use the map provided by the map system  440  to overlay the route information. 
     In one implementation, the route engine  410  can associate a reference with each of the routes generated. In another implementation, the route engine  410  can associate a reference with each route determined by tracking the mobile device  100 . The reference can, for example, include one or more parameters associated with the route. The parameters can be associated with the names of the starting location  460  and ending location  462 . The parameters can also be associated with user specified parameters associated with the route. The route engine  410  can, for example, save the route under the reference in the mobile device  100 . The mobile device  100  can, for example, at any time, retrieve the saved route using the reference in response to a user input. 
     For example, suppose the starting location  460  of the route was indicated at the grocery store. Suppose also that the ending location  462  is the grocery store. The route can be saved with the reference “home to grocery,” or if the route was a scenic route, the route can be saved with the reference “scenic route.” In one implementation, the same route can be associated with one or more reference names. Therefore, the route in the above example can be associated with the reference “home to grocery,” as well as “scenic route.” 
     In another example, suppose an address of the user&#39;s house is indicated as the starting location  460  and the address of a friend&#39;s house is indicated as the ending location  462 . The route engine  410  can generate a route from the user&#39;s house to the friend&#39;s house and display it for the user. A reference can be associated with this route and the route can be retrieved at a later time using the reference. 
     In one implementation, the mobile device  100  can be used in conjunction with an on-board navigation system for a vehicle. The mobile device  100  can provide route information to a user of the navigation system. 
     In one implementation, any route generated by the route engine  410  can be edited by an editor engine  430 . A route can, for example, be edited by an editor engine  430  if it was created by tracking the mobile device  100  as described above. A route can also be edited if created by the route engine  410  by receiving a starting location  460  and an ending location  462  and the route engine  410  generating the route. In other implementations, any route previously created or saved by the route engine  410  or received from a peer through the mobile device  100 , e.g., an SMS message describing the route, can be edited. 
     For example, a saved route can be retrieved by indicating the reference of the route. The route engine  410  can retrieve the saved route using the reference input by the user. While navigating according to the route guidelines, the mobile device  100  can receive an indication to edit the route. For example, a different road can be selected than the current road indicated on the route, or a different ending location  462  can be selected other than the one indicated on the route. Upon receipt of an edit, the editor engine  430  can track the position of the route to the ending location  462 . In one implementation, the route engine  410  can associate the same reference with the edited route. In other implementations, the route engine  410  can, for example, associate the new route with a second reference. In one implementation, upon receipt of an edit location indicator, the editor engine  430  can track the position of the route to the ending location  462 . 
     For example, suppose a route referenced as “back roads home from work” is selected. The mobile device  100  can retrieve the route using the reference “back roads home from work” and display the route for the user. An alternate road can be selected than the one indicated on the retrieved route at a certain point during the route. The mobile device  100  can receive an indication that the route “back roads home from work” is to be edited. The editor engine  430  can therefore start tracking the changes in the route from the point in time of receipt of the edit indication. At the ending location  462 , the mobile device  100  can receive an indication that the ending location  462  has been reached. The route engine  410  save the edited route as “back roads home from work” and save this new route information. The route engine  410  can also select a new reference for the edited route, e.g., “back roads home from work not using highway.” 
     In one implementation, the route engine  410  can retrieve real time traffic information on the mobile device  100  as described above. The traffic information  464  can, for example, be related to a universe of area roads can be communicated to one or more mobile devices (e.g., mobile devices  100  of  FIG. 1 ), and the route engine  410  can parse the signal to obtain traffic information  464  for route guidelines. 
     In one implementation, the current route can be edited based on the traffic information  464 . The mobile device  100  can receive an edit location indicator and the route can be edited based on the traffic information  464 . Editing the route can, for example, include receiving input of a different road than the current one displayed on the mobile device  100 . For example, suppose a saved route is retrieved by the mobile device  100  by receiving an indication of a reference route A. The route includes directions from point A to point B. While navigating from point A to B according to “Route A,” the mobile device  100  receives traffic information  464  indicating heavy traffic where “Route A” indicates the next turn should occur. The mobile device  100  can then edit “Route A” by receiving an input of an edit location indicator. An alternative road can be selected from the current location. At any time, an indication can be received on the mobile device  100  to start tracking “Route A” from the current location. The editor engine  430  can track the mobile device  100  from the new location to the ending location  462 . The route engine  410  can associate a new reference with the edited route, e.g., “alternative Route A,” or associate the same reference “Route A” with the edited route. 
     In some implementations, if a route is retrieved by a reference, the routing instructions  372  can continue to analyze a current route to monitor for changing conditions. For example, an accident between the start of navigation of a route and the end of navigation of the route might change the analysis associated with recommending the current route. In such situations, the routing instructions  372  using the route engine  410  can calculate alternative routes. In some implementations, the routing instructions  372  can automatically communicate a new route through the presentation engine  420 . Such automatic rerouting can be provided with notification of the change or without notification of the change. In other implementations, the routing instructions  372  can present the estimated navigation times associated with alternative routes through the presentation engine  420 . An alternative route can be selected based upon the estimated navigation times. The selection, in various implementations, can be indicated by selecting a route using an I/O device (e.g., touch screen  346  of  FIG. 3 ), or by navigating one of the alternative routes, among others. Once the route changes, a new reference can be associated with the route. In other implementations, the same reference can be associated with the edited route. 
     In one implementation, the route engine  410  can learn to use a specific route when determining a route from a starting to an ending location. The route engine  410  can, for example, analyze all previous routes generated and navigated, and determine that one particular route is often used. In another example, the route engine  410  can keep a log entry every time a user edits a route and determine whether the route is edited to use a particular road. The route engine  410  can use this particular road the next time the route is generated. 
       FIG. 5  is a block diagram of an example mobile device using a route reference. The mobile device  100  can receive a map representation  500  from a navigation service (e.g., navigation service  230  of  FIG. 2 ) of a reference  502 . The map representation  500  can, for example, include route from a starting location  460  to an ending location  462 . 
       FIG. 6  is a flow diagram of an example process  600  for generating a route. The process  600  can, for example, be implemented in the mobile device  100  of  FIG. 1 . 
     At stage  602  a user input is received on a mobile device specifying a starting location  460 . The user input can, for example, be received by a mobile device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358  of  FIG. 3 ) and GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 1 ) operating in conjunction with a wireless communication ( 324  of  FIG. 3 ). The starting location  460  can be input manually by a user or be automatically determined by a positioning system (e.g., the positioning system  318 ). 
     At stage  604 , a position of the mobile device is tracked from the starting location  460  in response to the user input. The position of the mobile device can, for example, be tracked by a positioning system (e.g., the positioning system  318  of  FIG. 3 ) in conjunction GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). 
     At stage  606  a user input is received on the mobile device specifying an ending location  462 . The user input can, for example, be received by a mobile device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions  358  and GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). The ending location  462  can be input manually by a user or be automatically determined by a positioning system (e.g., the positioning system  318 ). 
     At stage  608  a route is generated from the tracking of the mobile device from the starting location  460  to the ending location  462 . Alternatively, the route can be generated without tracking that is based on a request to progress from a starting location to a destination without movement (e.g., prior to commencing the travel). The route can, for example, be generated by a route engine (e.g., route engine  410  of  FIG. 4 ) in conjunction with GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). The route can include directions from the starting location  460  to the ending location  462 . 
     At stage  610  a first reference is associated with the route, wherein the route is retrievable by a selection of the first reference. The first reference can, for example, be associated with the route by a route engine (e.g., route engine  410  of  FIG. 4 ) in conjunction with GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). 
       FIG. 7  is an example process for associating a reference with a travel route. The process  700  can, for example, be implemented in the mobile device  100  of  FIG. 1 . 
     At stage  702  an input is received specifying a first location. The input can, for example, be received by a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). The first location can correspond to a first geographic location. 
     At stage  704  input is received specifying a second location. The input can, for example, be received by a mobile device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). The second location can correspond to a second geographic location. 
     At stage  706  a travel route is computed between the first and second geographic locations. The travel route can, for example, be computed by route engine (e.g., route engine  410  of  FIG. 4 ) in conjunction with GPS/Navigation instructions (e.g., GPS/Navigation instructions  368  of  FIG. 3 ). 
     At stage  708  an input is received indicating an edit. The input can, for example, be received by a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation). 
     At stage  710  the travel route is edited on a wireless in accordance with the edit. The travel route can, for example, be edited on a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with GPS/Navigation instructions (e.g., GPS/Navigation). 
       FIG. 8  is an example process for editing a route. The process  800  can, for example, be implemented in the mobile device  100  of  FIG. 1 . 
     At stage  802  a user input is received specifying a first reference. The input can, for example, be received by a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation). 
     At stage  804  a route is displayed on a wireless device. The route can, for example, be displayed on a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation). 
     At stage  806  a user input is received specifying an edit. The input can, for example, be received by a wireless device (e.g., mobile device  100  of  FIG. 1 ) in conjunction with sensor processing instructions (e.g., sensor processing instructions  358 ) and GPS/Navigation instructions (e.g., GPS/Navigation). 
     At stage  808  the route is edited by tracking the position of the wireless device to the ending location. The route can, for example, be edited by an editor engine (e.g., editor engine  430 ) in conjunction with GPS/Navigation instructions (e.g., GPS/Navigation). 
     The systems and methods disclosed herein may use data signals conveyed using networks (e.g., local area network, wide area network, internet, etc.), fiber optic medium, carrier waves, wireless networks (e.g., wireless local area networks, wireless metropolitan area networks, cellular networks, etc.), etc. for communication with one or more data processing devices (e.g., mobile devices). The data signals can carry any or all of the data disclosed herein that is provided to or from a device. 
     The methods and systems described herein may be implemented on many different types of processing devices by program code comprising program instructions that are executable by one or more processors. The software program instructions may include source code, object code, machine code, or any other stored data that is operable to cause a processing system to perform methods described herein. 
     The systems and methods may be provided on many different types of computer-readable media including computer storage mechanisms (e.g., CD-ROM, diskette, RAM, flash memory, computer&#39;s hard drive, etc.) that contain instructions for use in execution by a processor to perform the methods&#39; operations and implement the systems described herein. 
     The computer components, software modules, functions and data structures described herein may be connected directly or indirectly to each other in order to allow the flow of data needed for their operations. It is also noted that software instructions or a module can be implemented for example as a subroutine unit of code, or as a software function unit of code, or as an object (as in an object-oriented paradigm), or as an applet, or in a computer script language, or as another type of computer code or firmware. The software components and/or functionality may be located on a single device or distributed across multiple devices depending upon the situation at hand. 
     This written description sets forth the best mode of the invention and provides examples to describe the invention and to enable a person of ordinary skill in the art to make and use the invention. This written description does not limit the invention to the precise terms set forth. Thus, while the invention has been described in detail with reference to the examples set forth above, those of ordinary skill in the art may effect alterations, modifications and variations to the examples without departing from the scope of the invention. 
     These and other implementations are within the scope of the following claims.

Metadata:
Filing Date: 20080206
Publication Date: 20140624
Grant Date: 20140624
Priority Date: 20070628
Inventors: FORSTALL SCOTT
CHRISTIE GREGORY N.
BORCHERS ROBERT E.
TIENE KEVIN
Assignee: APPLE INC
CPC Classifications: [{"code": "G01C21/3484", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01C21/3691", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01C21/3407", "inventive": false, "first": false, "tree": "[]"}, {"code": "G01C21/3484", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01S5/0009", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01C21/34", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01S5/0009", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01C21/3691", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01C21/34", "inventive": true, "first": true, "tree": "[]"}, {"code": "G01C21/00", "inventive": true, "first": false, "tree": "[]"}, {"code": "G01C21/3407", "inventive": false, "first": false, "tree": "[]"}]
Family ID: 40161568