BRPI0708355A2 - partner system for navigation devices - Google Patents

Abstract

PARTNER SYSTEM FOR NAVIGATION DEVICES A partner system for navigation systems is revealed. In addition to the partner system, a user of a navigation device can locate other users of navigation devices within a selected neighborhood. The partner system also includes lists of partners compiled from some of the navigation devices grouped according to a common feature. The feature can be a relationship between the users of the navigation devices, the location of the navigations, and the like. Navigation systems are listed within partner lists according to geographic location and identification. Navigation systems, with lists of partners stored therein, can be induced to navigate towards a selected partner. In addition, in addition to the partner system, a navigation system can communicate with another via text and voice messages.

Description

"PARTNER SYSTEM FOR NAVIGATION DEVICES"

PRIORITY STATEMENT

This application claims priority in accordance with 35 USC § 119 in each of United Kingdom Patent Application numbers 0604709.6 filed March 8, 2006; 0604708.8 filed March 8, 2006; 0604710.4 filed March 8, 2006; 0604704.7 filed March 8, 2006; and 0604706.2 deposited March 8, 2006, the complete contents of which are incorporated herein by reference.

FIELD

The present application relates to the field of navigation systems and more specifically to a navigation system partner system, an arrangement to operate the navigation system partner system, and a navigation system configured to perform partner system operation.

BACKGROUND

Navigation systems are used herein to refer to devices enabling a user to navigate from a current location to a destination location. Navigation systems may be arranged to provide user exit in the form of a map showing where arrows or other signals indicate an appropriate route between the current and destination locations. Maps may be renewed based, for example, on current location as determined by an appropriate satellite, GPS, and / or Internet connection. With the new maps come renewed visual cues as for an appropriate next step along the route between the current location and the destination. Alternatively, map renewal may occur gradually. Other user output may include voice direction taken together or independent of the map display. A common voice command can be to make a specific turn at a forward intersection.

Navigation systems may comprise an internal processor communicating with an internal memory, media, power media and video. The processor may comprise software or other programming to perform the generation of the above marked maps and user exit. The internal memory may include map data upon which the process may elaborate. Additionally, the processor may be arranged to communicate with a remote server via the communication medium. The server can be a dedicated or non-dedicated server with the default direct and / or wireless communication medium.

The navigation system can be additionally arranged to receive user input via a touch screen, buttons, voice activation and the like. The processor may further be programmed to receive user input, determine a current location via GPS and the like, and display the current location on a map obtained from memory. In addition, when provided with a destination location, the processor may be programmed to determine a selected route and / or the best route between the location! Act! and the loca! and further issue such better through a series of outgoing voice commands in conjunction with revamped map displays.

Current navigation systems come in a variety of forms. One form - personal navigation device - can be handheld or otherwise portable / or integrated into a motor vehicle such as a car, boat, or airplane. Among the many features of navigation systems is the ability to direct the user to a specific destination or point of interest (such as the next gas station, favorite restaurant, and the like). Such destinations are geographically static and typically known in advance. For example, a user may pre-program their device to identify a favorite bar in advance at the beginning of a trip to the bar. When boarding the bar, the user only needs to enter the name or location of the bar.

A common functionality that does not exist in navigation systems is the ability to route a user to a mobile destination. Additionally, another nonexistent feature is the ability to locate other navigation system users. Such functionality is especially useful for answering important questions such as "where is my wife?", "Where are my colleagues?" or "Where are my friends?" Such questions become even more important not only in a personal context for meeting friends or family, but also in a professional context of a central office trying to locate colleagues on the move, such as delivery vehicles, similar taxis.

SUMMARY

The present invention therefore relates to the previously untreated need for art, that is, the provision of location, navigation towards and / or communication with other users of navigation systems. The present system for such provision is referred to herein as a partner system. The present invention, therefore, relates to the partner system, a system for providing the partner system, and navigation systems programmed or otherwise arranged to use the partner system.

The partner system itself is a system through which a navigation system can locate or select another navigation system or systems. The partner system of the present invention provides users with the functionality of selecting users of navigation systems according to predetermined common attributes of the selected users. For example, the partner system allows a user to locate other navigation system users or partners at a specific location, that is, all partners located at or around the χ point. The location of the partners with respect to the χ point can be varied. Additionally, the partner system provides in the sense of locating selected partners belonging to a specific professional organization, ie selected taxis (or all) in a larger city area or selected delivery trucks (or all) currently operating regardless of location, etc. . The location of partners can also be limited to friends, family and the like, that is, the location of a person's children. Partner groups can of course overlap and include one or more of the above. These and other partner groupings are detailed below.

To perform the aforementioned groupings, a predefined partner list, or partner list, is created. When done, partner identification and location in the partner list can be done. Since partners are also navigation system users, the partner list can also include the geographic location of the navigation system and therefore the partner using the localized navigation system. A navigation system tends to be used by users on the go, partner lists can be renewed or updated periodically to stay current.

When located, the requesting user may wish to navigate to one or more partners in the partner list as well as to communicate with one or more of them. Communication can take the form of voice or text communication. The partner system is therefore directed in addition to the use of such related functionality.

The inventive system for realizing the partner system comprises a dedicated server in communication with one or more navigation systems. The system may follow the known client-server architecture, with the additional features and functionality for use by the present partner system. In addition, or as an alternative to a dedicated system, other properly configured partner client systems, that is, dedicated and / or non-dedicated servers, may be employed. Navigation system communication to the navigation system may be by means of non-hierarchical configuration or via the dedicated and / or non-dedicated server.

The present invention further relates to a navigation system for a partner system. The present navigation system may comprise a processor programmed to use the functionality noted above. Additionally, the present navigation system includes input / output means for exchanging information with a user. Such an input / output medium may include a touchscreen, speaker / microphone, buttons, lights and the like with appropriate support functionality within the navigation system itself and / or remotely located on at least one of the dedicated and non-dedicated servers. mentioned dedicated devices, remote computers, remote navigation systems and the like. Through a properly programmed processor, the user can be prompted with a series of graphical interfaces to manually enter the desired functionality. Input can be manual, voice activated and the like. Desired functionality may include the previously mentioned partner location, partner list creation, navigating toward a partner, communicating with a partner, and the like.

The present system further further relates to a method for implementing the aforementioned partner system.

Although described above in the form of navigation systems, the application of the partner system is not limited to navigation systems and may include implementation on handheld or desktop computers, personal digital assistants, mobile phones and any other devices including at least the above mentioned features and functionality. above.

BRIEF DESCRIPTION OF DRAWINGS

The present application will be described in more detail below using exemplary embodiments, which will be explained with the aid of the drawings, in which:

Figure 1 illustrates the partner system of the present invention by means of a first navigation system querying the location of another partner system;

Figure 2 is a flowchart illustrating a method for realizing the present partner system in a navigation system;

Figures 3-12 illustrate a series of screen images that can be presented to a user using the partner system of the present invention in a navigation system.

DETAILED DESCRIPTION OF EXAMPLE

The terminology used herein is for the purpose of describing specific embodiments only and is not intended to be limiting of the present invention. As used herein, the singular forms "one", "one", and "o" are also intended to include plural forms unless the context clearly indicates otherwise. It will further be understood that the terms "includes" and / or "including", when used in this descriptive report, specify the presence of declared characteristics, completeness, steps, operations, elements, and / or components, but do not preclude the presence or adding one or more different characteristics, integrals, steps, operations, elements, components, and / or groups thereof.

In the description of exemplary embodiments illustrated in the drawings, specific terminology employed for the purpose of clarity. However, the disclosure of this patent specification is not intended to be limited to the specific terminology thus selected and it should be understood that each specific element includes all technical equivalents which operate in a similar manner.

With reference to the drawings, in which like reference numerals designate identical or corresponding parts throughout the various views, exemplary embodiments of the present patent application are hereinafter described. Similar numbers refer to similar elements from beginning to end. As used herein, the term "and / or" includes any and all combinations of one or more of the related related items.

The present invention will be discussed with respect to a handheld navigation device (PND) with the understanding that the present invention may be applied to any navigation system or other device including the functionality discussed herein.

Figure 1 illustrates a typical client server arrangement 15 comprising a server 10 communicating with a generic user 14 and a digitizing tablet 12 and a personal navigation device (PND) 16. Each of the foregoing includes a means of communication, It is known in the art and not illustrated in the figure, arranged to facilitate communication 18 with server 10. Further, each of them may comprise input / output means for exchanging information with a user. Such an input / output means may include a touch screen 17 on which a map 19 is displayed and touch screen commands entered as shown in the personal navigation device 16. Touch screen can also be used to display graphical interfaces (detailed below) prompting for user commands. Other input / output means include speaker / microphone arrangements for receiving and broadcasting voice commands; buttons to receive tactile warnings and / or display a warning by flickering or the like; and other means of input / output as may be anticipated by those skilled in the art. The present invention is not limited to the number or type of client interacting with the server and the aforementioned generic user, the tablet and the personal navigation device are illustrated by way of non-limiting example.

The server comprises a partner list 11 composed of a plurality of partners 13. As detailed below, the partners may be organized and selectively identified by either or both geographic location and identification. The server may be a dedicated or non-dedicated server. The server can be an independent server or part of a larger network. Communication with the server may be used by means known to those skilled in the art. The present invention is not limited by the client-server architecture or the type of client or server.

Because the partner list can be populated by partners within a certain radius of the requester, the server can maintain a master list of available partners and their current locations. Consequently, as detailed below, a user when connecting to the partner system may be required to allow disclosure of their current position. Additionally, the server further includes available processing means for calculating a current requester position, applying a certain geographic range of action to the current position, and selecting among potential partners, among other criteria, for partners within the radius. Figures 2a-c illustrate flowcharts illustrating a method of using this partner system in a navigation system. The illustrated method highlights inter-device and user interaction, including the user selection uses of specific functionality. The present invention is not limited to the specific order illustrated. The method will be discussed with respect to application in a personal navigation device (PND) with the understanding that the present method can be applied to any client. The method steps will be discussed below with screenshots illustrating icons for use of the method steps discussed.

A top menu may comprise a map 19 illustrated in Figure 1. Bringing it on the map or otherwise engaging in the PND will bring up a main menu. The present partner system may be part of a typical feature provided by the navigation software, the feature appearing as one of the many main menu icons. Alternatively, the partner system may be a supplementary system provided in addition to a core functionality. This is offered by assignee TOMTOM intitu-IadoPLUS.

As part of the PND, the Partner System first becomes noticeable through a main menu icon as illustrated in Figure 3. Figure 3 illustrates a higher level icon 300 introducing partner functionality to the user. The functionality may be part of a navigation software package for a navigation system or a complement to existing packages through an enhancement. Turning on the 300 icon causes partner system menus to appear. Activation also corresponds to the beginning 20 of the flow chart of Figures 2a-2c.

In a first step 22, prior to displaying the partner system menu or simultaneously with it, a partner list request is sent by the PNDao server.

The partner list comprises a grouping of navigation device users, the grouping based on a pre-existing relationship established by the user. The partner list comprises current user names and / or geographic locations of users. An illustration of a list of partners is presented below. Partner lists are maintained by a central server and periodically renewed. As will be detailed below, the user can selectively renew the transferred partner list saved in his PND. Different categories or groupings of partners, as suggested above, may be based on a relationship to the user (eg family, profession, etc.) or randomly (eg any other users of partner systems). The partner list may be further limited by geographic location, such as a radius of selection for a current or selection location.

In step 24, the server communicates the requested partner list to the PND. In step 26, the PND creates a local partner list work / shadow list.

In step 28, the server records the client request. The above steps may take place automatically without the user's direct knowledge.

The following queries are illustrated as icons in a first of two partner system menus. Specific pictorial illustration and corresponding text may vary by application and are illustrated in the figures as exemplary icons only. The first partner system menu 400 is illustrated in Figure 4, the menu comprising a number of icons corresponding to the queries discussed in conjunction with the flowchart below.

Returning to Figure 2a, in step 30, the user is asked if he or she includes his or her geographic name in other partner lists stored on the server or if the user wants to remain anonymous. The 440 icon in Figure 4 corresponds to this query. If you want to remain anonymous (32), it will appear to other users as you have turned off your device. Icon 440 may additionally be induced to change this mode indicating that the user is hiding his identity and location. Such an icon may include a crosshair through the icon as shown in Figure 4. Uuser unavailability is used by sending an unavailability / Set Status message to the server from the user PND. The result returned by the server is processed properly.

If the user decides to have his / her name included in the list (34), the appropriate list or partner lists stored on the server will be updated with the user information in step 36. This will be done by sending an available / Establish- Status to server from user PND. The result returned by the server is processed as detailed below. Subsequently, the first Partner System 400 menu, Figure 4, will be required for the user.

In addition to the above, the user may be asked if he intends to adopt a special name that will be used instead of the generic device identification. If so selected, the user will store the personally selected name for the user. Also, if the partner list requested from the server is empty, the icon to hide their positions (below) will be overshadowed.

According to the first Partner System menu, the user is presented with additional options, including: guided tour 38 (icon 432), showing the partner's location on a map 40 (icon 434), update (the partner list) now 42 (icon 436), invite a new partner to partner list 44 (icon 438), proceed to the second menu 46 (icon 438) and complete 48 (icon 440). The first Partner System 400 menu may include additional displayed information, including current time 442, indicating when a last update was performed 444, and an indication of which of the two Partner System menus is displayed 446. Returning to Figure 2a, if the oriented script option 38 is selected 50, the PND user is provided with a partner system oriented script 52. The oriented script can comprise a multimedia script including visual and verbal feedback to the user. The script can be additionally instructional and interactive. Software used to implement and use the guided tour may be stored locally on the navigation system or remotely on the server or similar and downloaded when connected by the user. Tour details are a matter of design.

Queries and / or options can be connected or selected by donating to press, for example, the icon in the PND video, the video being touch sensitive. Other user input means include voice activation, buttons and the like.

Returning to Figure 2a, if Show Partner 40 is selected 54, a map view (500, Figure 5) is displayed in the PND 55 video, the map illustrating the location of a specific partner in question with the exact current location. (as shown by the server) highlighted with signs. An additional step may be notifying the displayed partner that their location has been requested by the user. As an example, a map is illustrated in the PND of Figure 1.

Figure 5 illustrates an exemplary map view of Amsterdam 500, with a particular partner in question 502 illustrated therein 504. The map view includes other functionality including: Find 504, Options 506 and Finished 508; which will be discussed in more detail below.

Returning to Figure 2a, the update now option 42 (icon 436, Figure 4) actually comprises two options: an Update Now option and an Update or Update Partner option. Alternatively, the Update Partner option may be displayed through the individual query through the icon (as in the case with step 74). When Act Now 42 or Update Partner option 74 is selected 56 and 58 respectively, the server is requested via a renewal message that updates the identities and locations of people in the received partner list 60 and 62. respectively.

Process 62 will be discussed in more detail below. The result returned by the server is processed and the user is presented with a first menu screen or list of new user PND partners. According to the Update Now option 42, the current state and last known geographical positions (when available) of all partners in the partner list are retrieved by the server.

Figure 6 illustrates a typical partner list 600. As illustrated, the partner list comprises a plurality of partners 602 identified by e-mail address 604 and partner icons 606. In addition to the present invention, each partner can be identified by a specific icon having specific meaning, different partner icons are illustrated in Figure 7. Partner list 600 also includes a time stamp 608, a title 610, and three options: find 612, update 614, and cancel 616. According to In the find 612 option, the user is presented with an interface for locating a specific partner from the partner list via a search function, the search function being known in the art. The 614 refresh function, when enabled, updates the partner list with the most current partner information available, the information originating from the user's PND or server. The cancellation function 616 closes the partner list and returns the user either to the first partner system menu or to the PND main menu.

Figures 7a-7e each illustrate a partner icon. Icons can be color coders for easier identification. The first partner icon 702 is used to indicate that the respective partner is available and their position is current. By present, it is meant that the position is no more than 15 minutes in existence. Alternatively, other current time definitions may apply. When this partner is current and available, his position can be seen on the map (eg 502, Figure 5).

Secondly, partner icon 704 is used to indicate that the respective partner is available even though his position is out of date. In other words, this partner's apposition was known, but has since become old. An old position can be one that is between 15 and 60 minutes old. Alternatively, other time settings may apply. This partner could still be shown in the map.

The third partner icon 706 is used to indicate that the partner is available although their position is old, ie more than 60 minutes. Here too, time may vary depending on the application. This partner could still be illustrated on the map.

The fourth partner icon 708 is used to indicate that the partner is unavailable and the server is waiting for a response to an invitation for the partner to join the partner list. This partner has not yet responded to an invitation to become a partner. As a result, this partner or potential partner is visible only in the partner list.

The fifth partner icon 710 is used to indicate that the partner is unavailable and the partner position cannot be determined because the partner did not accept the invitation to become one of the partners. Additionally, the partner may have deleted the user from their partner list.

Information may be retrieved by the server from a database, the maintenance of which may be done by the server in addition to known technical procedures. In addition, for the Update Partners option 74, the server is prompted to request a specific partner to return its current geographic location via an inbound channel or the like. The following interactions occur based on the status of the partner in question. The update can also occur from the partner list screen option 614.

If a partner state is unavailable / unknown, when a message may be displayed to the user along the lines of: TOMTOM BUDDIES, <Name> is not a PLUS user - PLUS being an enhanced service available for navigation systems from. assignee of this TOMTOM application, the service including the present partner system. Another language can be used for the effect that the requested partner is not a member of the partner system.

If the partner state is unavailable / deleted (ie the partner has deleted the user from the partner list), then a message may be displayed to the user along the lines of: "TOMTOM BUDDIES, <Name> deleted you from your partner list ".

If the partner state was unavailable / invited and is now available (that is, the partner has accepted the user's invite to become one of the partners), then a message is displayed to the user along with the lines of: TOMTOM BUDDIES, < Name> agreed to become your partner.

If the partner state was unavailable / invited and is now unavailable / declined (ie the partner declined the user's invitation to become one of the partners), then the message is displayed to the user along the lines of: TOMTOM BUDDIES, <Name> declined to become your partner.

If the partner state is invited / reply-to-invitation (ie the partner has invited the user to become partners) then the user is presented with the following text message: TOMTOM BUDDIES, <Name> invited you to become partners. The user is additionally presented with a pair of buttons to accept or decline the invitation. If the user selects Accept, a Reply-to-Invitation / Accepted message is sent to the server. If the user declines, a Reply-to-Invitation / Declined message is sent to the server.

On the server, in response to the Reply-to-Invitation / Accepted message: the status threatening a partner in the inviting partner's partner list is changed to available from unavailable / guest; the inviting partner state to the partner list of the accepting partners is changed to available (was invited / invitation-response) · in response to the Reply-to-invitation / rejected message - the partner status that decline in partner list of inviting partner is changed to unavailable / declined; The inviting user is deleted from the partner list of the declining partner, and the local partner list is updated.

Partner list updating can be done automatically at a user-adjusted time delay. This can be adjusted manually by the user by engaging in partner change preferences 64. If engaged 66, the user is presented with an update screen 800 shown in Figure 8. According to Figure 8, the user is shown the text 802 indicating a partner list auto update mode and 801 conference box checked when auto update mode is employed. In addition, the update screen 800 includes a time indication 804 and title806. The user is also presented with an option to terminate the function (Completed, 808) that takes the user back to the first partner system menu. If check box 801 is not checked, a second update screen is displayed to the user, the second screen including a numeric editor 900, Figure 9, which facilitates user input of a selected time delay between 907 minute updates. The editor900 also includes a 902 indent function, a 904 cancel function returning the user to the first partner system menu, and a 906 completed function taking the user back to the first update screen. As with the first update screen, the second update screen includes a 908 time indication and title 910.

Returning to Figure 2a, if invite new partner 44 is selected 58, the user identifies a specific partner and requests the server to add the identified partner to a user-specified partner list 62. To use a new partner identification for In the partner list, the user is presented with a standard alphabet screen 1000, Figure 10, including alphanumeric characters as well as options to cancel1010 and completed 1012. New partners can be identified by email address 1014 or another identifier. To perform the addition, an invite message is sent to the server by the user PND and the result returned by the server is processed. Then the partner menu or first menu is displayed again. As with the above stars, the alphabet editor screen includes a clock 1016 and title 1018.

On the server side, a determination is made as to whether the user exists and is otherwise available or known. If user status is available, the user is added to the partner list via an invite / invitation response step. The intended partner is informed of the invitation via a message notification which can be customized by the user or comprise pre-written text available from a memory and sent automatically as part of this step. If the partner is unknown, then the status of the partner becomes unavailable / unknown and the user is informed accordingly. If the user is not available, the partner state becomes unavailable / invited and the user is then informed. If partner is available, partner status becomes available.

The server may additionally contact the identified partner and consult the same for permission to add him (with or without current location) to the user-specified list of partners. Alternatively, the foregoing can be accomplished without confirmation or entry of the identified partner. Returning to Figure 2a, if the user chooses to exit partner system 66 in addition to option 48, the user leaves partner system 68 and is returned to map view or main menu of your PND.

If proceeding to the next menu 40 is chosen 62, the first menu will be replaced by a second menu presenting the option with the additional options discussed below. As with the first menu, each of the second menu queries can be presented simultaneously on one screen. An alternative number of queries may be displayed depending on schedule, screen size and the like. This invention is not limited by the number of graphical user interface queries presented on any screen at any given time.

If in addition to option 46, the user chooses to proceed to the next partner system menu 70, the user is then presented with the second partner system menu 1100 as shown in Figure 11. Figure 11 comprises a series of icons related to the method steps presented in Figure 2a.

Returning to Figure 2a, the user is presented with a series of queries or options (via icons from the second partner system menu 1100), including: sending the partner a message 78 (icon 1102); change partner preferences 64 (icon 1110), delete partner 72 (icon 1104), update partner 74 (icon 1108) and read messages 76 (icon 1106). The user is additionally provided with the option to proceed by returning to the previous menu 80 (icon 1112) and end 81 (icon 1114).

If the option to send partner a message 78 is chosen 82, the send message to partner / menu 1200 screen is displayed to the user, the screen shown in Figure 12and the process continuing in step 2b. The user is presented with various options or queries, including: sending the partner a message 88 (icon 1204); send partner a location 90 (icon 1202); send your partner your position 92 (icon 1206); and completed86 (icon 1208).

If sending message to partner 88 (icon 1204, Figure 12) 98 is chosen, the user's PND transmits a message to a selected partner 104. The message may comprise text, voice, images, combinations of the above mentioned and may be transmitted via the non-hierarchically.The message may additionally be a message pre-stored within the server and available for transmission upon user request in the PND. Details of exchange of messages in general are presented below.

If the option to send partner a location 90 is chosen 96, a user-selected geographic location is transmitted to the partner in question 106 along the same lines as the message above. An exemplary message 1300 is illustrated in Figure 13. The message comprises text identifying the selected geographic location 1302 and GPS position 1304 for the location. The message further comprises two options, that is, proceed to a navigation to menu 1306 and return to the main map or main menu of PND 1308. The message may further include a time 1310 and a title indicating the sender and telephone number thereof. 1312.

The partner must have an available status and therefore a list of partners to which such a message could be sent may be limited in advance by the PND only to those with the cited state. A send partner location screen can be displayed to the user in conjunction with this option, the send partner location screen including a GPS icon making it easy to determine a position. GPS Icon Selection displays a location menu screen through which a location can be selected or otherwise entered. One possible location is the current position of the user. When a location is selected and entered by the user, a Send Position message is sent to the server. The message may include callout or predetermined custom text. The result returned by the server is processed and the first menu is displayed to the user.

Once received on the partner navigation device, the transmitted geographic location can be displayed as a text and / or as a location in a map. The user's selected geographic location or address can be created by typing in alphanumeric characters of a displayed alphabet; tactively indicating on a displayed map the location, or other means of entry. This can be provided by means of a location selector in a text message. The location now entered is transformed into a message and transmitted either through the server or directly to the partner navigation system.

If the user chooses to send partner 94's current location according to step 92, a request is sent from the PND to the server to partner 108's current location. The server then finds the record corresponding to the partner's current location. (as may be available according to a partner list, renewed or automatically obtained or by permission from the partner) and transmits the location to the PND which in turn displays the location either as text or signs on a map. An example of a map illustrating a partner is shown in Figure 5.

If cancel 86 is selected 100, the method proceeds 102 back to the previous menu. Alternatively, the method may proceed to the end.

Returning to Figure 2a, if changing partner preferences 64 (icon1110, Figure 11) is selected 110, a change partner preferences screen (discussed above) is brought up and displayed on user PND video 84. According to this screen, The user is provided with an option to select an automatic update from the partner list from the server, the update comprising the current partner names (ie partners who have currently activated their navigation devices and agreed to be part of the partner list) as well. as the current locations of current partner as otherwise obtained from partner navigation systems as discussed above. According to an additional automatic updated partner list screen, the user is presented with the option to selectively update the partner list every number of minutes, ranging from 1 to 99. To facilitate the entry of the update time interval, it is presented to the user a series of numbers 1-9 along with cancel, complete and return to a previous menu (as detailed below). According to the partner list update, the user's PND will be induced to send the current user ID and geographic location to the server for appropriate partner list inclusion (s).

If delete partners (icon 1104) is selected 114, the user is presented with a text requiring confirmation of the deletion. The text may say, "Are you sure you want to delete <Name>?". Other text can be used through the design option. The user can optionally be presented with a yes and no selection option. This option can be a button, icon, voice activation medium and the like. If the user selects "yes", the partner is deleted from the local partner list (in user PND or remotely stored), a Delete Partner message is sent to the server and the result returned by the server is processed. . On the server, the partner to be deleted is removed from the user's partner list, the status of the deleted partner is set to unavailable / deleted, and the partner list is displayed to the user in their PND video. Similarly, the user is deleted from the partner list belonging to the now deleted partner.

If the option to update partner position 74 (icon 1108) is selected 58, a determination is made of all partners having an available state and a Get Position message is sent by the user's PND to the server - the position being that of the available partners 62. The result returned by the server is processed and the first menu or partner menu is displayed to the user. On the server, if the status of the desired partner whose position is being updated is available, a Provide Position message is sent to the intended partner (for example, via Inbound) and the partner returns their current position. The partner position on the server is additionally updated.

If the user chooses to read messages 118 according to the read messages76 option (icon 1106), the user is presented with a text message 120. The text message 120 may comprise the user's position and identification as detailed below with respect to In accordance with the message displayed in step 120, the user is presented with a step of additional options 122 presented by the flowchart of Figure 2c.

As shown in Figure 13, message 1300 comprises a location1302 and partner ID 1304 presented herein as text. Other message formats may be used as intended by those skilled in the art, including images, sound and other media. Message 1300 further includes an indication of the sender1310 displayed therein. The sender can be identified by name and phone number.

As illustrated, message 1300 was sent by John who has the telephone number + 31653354300 (1310). The current time (1312) can also be displayed. Exact presentation of sender information and timing is a matter of design choice. Alternatively, other related information may be displayed within the message, including: Actual Date, Custom Sender ID, and the like.

According to message 1300, the user is presented with the option to exit message (completed) 1306 which if selected exits the functionality of the partner system and returns to a main map display or other high level display. According to message 1300, the user is presented with options 1308 which if enabled present a navigation screen menu 1400 illustrated in Figure 14 corresponding to the flow chart of Figure 2c.

Returning to Figure 2c, the user is presented with some options, namely: na-vegar 126 (icon 1402, Figure 14), display a map 128 (icon 1404, Figure 4), add as a favorite 130 (icon 1406, Figure 14) and cancel 124 (icon 1410, Figure 14). The aforementioned options operate in conjunction with the possession of a third party address.

If the user chooses to cancel 138 in addition to the cancel 124 option, the method reverts 140 to the second partner system menu, a screenshot of which is illustrated in Figure 12.

If navigate 126 (icon 1402, Figure 14) is selected 136, the user PND will navigate to the specific geographic location 132. Initially, the user will be asked about a specific arrival time step 148 ( 1500, Figure 15). If a specific arrival time (1502, Figure 15) is selected by user 166, a route is calculated to the partner location by the PND software which will effect the desired arrival time from the user. Similarly, a best route will be calculated if no specific arrival time 168 (1504) is selected by user 156. Use can be made by determining a best route from the user's current location to the specific geographic location as be used by appropriate navigation software such as NAVCORE software from TOMTOM assignee of that patent. The best route can also be displayed on the user's PND as well as accompanied by voice commands and the like.

If the user chooses to have a partner location displayed on a map 134 according to query 128, the SNE is prompted to decipher the partner location as it may have been received according to a previous query and display it (step 144) in a map as shown in Figure 5. Prior to display, the partner state for display is confirmed to be available. If available partner information is taken from the local list and displayed in the PND. The display may include a specific icon to highlight 502, Figure 5. The user is presented with the option to return to the main map display or main menu by selecting the 508 icon. A route can be calculated from the user's current location to partner by activating the find icon 504. Similarly, the previously mentioned navigation menu options step 122, Figure 2c, can be accessed by activating the 506 icon.

If the user chooses to add a partner location to their favorites132 according to option 130, the PND is required to store the specific location 146 by entering partner identification according to an alphanumeric editor screen as shown in Figure 10 and discussed above. If the entry already exists within the favorites list, the user will have the option to overwrite the existing entry as illustrated by screen image 1600 in Figure 16 (see 150, Figure 2c). Such messages can be instant messaging. Screenshot 1600 includes an option1602 rather than 1604. In case the user chooses to make a replacement (154, Figure 2c), the previous entry of the same location is replaced with a new location (156, Fig. 2c) inside. from the favorites list. If the user chooses not to overwrite (158, Fig. 2c), the step ends and screen 1700 is presented to the user (152, Fig. 2c) giving him the option to set the current location as a location. domestic. Screen 1700 includes a yes 1702 and no 1704 option. If yes 1702 is selected (160, Figure 2c), the PND is moved to change the current home location to that illustrated in window 1700 (162, Figure 2c). If the user chooses not to overwrite the current home location (164, Figure 2c), the user is taken back to navigation screen 1200 (140, Figure2c) as shown in Figure 12.

In case cancel option 118 (icon 1214, Figure 12) is chosen 138, a previous minus 116 is illustrated 116 or the method terminates.

Returning to Figure 2a, if the user elects to proceed to a previous menu83 (1112, Figure 11) according to option 80, the method reverts back (step 102) to the first partner system menu as illustrated in Figure 4. If the user chooses to complete 85 (1114, Figure 11) according to option 81, the method ends (step 160).

Message exchanges with the server will generally be discussed now and server-managed data will also be delineated.

All messages sent by the client to the server contain the following elements:

• own status: available or unavailable • own current position if status is available · otherwise empty.

All server replies to messages sent by the client contain these elements:

• partner item list

There are 2 communication paths between partners. One is the client client server message protocol, the other is the text message exchange. The partner client-server message protocol about requests such as add partner, remove partner, update. A response received from the server is the result of a manual action by the user: selecting a menu icon. A server response may cause a notification dialog to be displayed on the client. Text message exchange covers ordinary text, which may contain a position recognized by the application. These text messages could be read as normal text if received on a device that does not interpret them correctly. Messages could be typed manually. It doesn't matter if they originate as an SMS, a server message, or a partner message. The visual notification referred to is the indication that a text message has arrived (AFAIK ie general message exchange functionality). The server sends a ready text message when a user is invited to become a partner (that is, when they receive an Add Partner request).

Claims (20)

1. Server Characterized for comprising means for communicating a list of partners to at least one navigation device. Server according to claim 1, characterized in that the partner list comprises a name and location of at least one navigation device. Server according to claim 2, characterized in that the partner list comprises at least one navigation device having at least one selected feature. Server according to claim 3, characterized in that it further comprises at least one means for grouping, updating, and storage records related to the feature. Server according to claim 4, characterized in that the feature comprises at least one of: a place, interest, an activity, a job and an interpersonal relationship. Server according to claims 1-5, further comprising means for receiving a request from at least one navigation device and communicating the partner list in response to the request. Server according to claim 4, characterized in that it further comprises means for querying the at least one navigation device for current location and identification information. Server according to claim 7, characterized in that the name to update further comprises means for updating the partner list according to the current location information. Server according to claims 1-8, characterized in that it further comprises communication means arranged to use communication between at least two navigation devices. 10. Navigation system partner system, FEATURED by understanding: - at least one partner list comprising a number of navigation devices grouped according to a common characteristic, and- means for communicating at least one partner to the navigation devices. Communication. Navigation system partner system according to claim 10, characterized by the fact that navigation devices are listed on a partner list by name and geographical location. Navigation system partner system according to claim 11, characterized by the fact that the geographical location is provided by the navigation devices. 13. Navigation device, characterized by comprising means of communication arranged to send and receive system messages from partners. Navigation device according to claim 11, characterized in that the messages are communicated between at least one of the navigation devices and a server. Navigation device according to claim 11, characterized in that messages comprising a request to a server to transmit a list of partners to the navigation device. Navigation device according to claim 13, characterized in that the partner list comprises a number of navigation devices identified by name and geographical location. Navigation device according to claim 14, characterized in that it further comprises means for issuing navigation instructions from a current location to a geographical location. Navigation device according to claim 17, characterized in that the instructions comprise at least one of audio instructions and visual instructions illustrated on a map background. Navigation device according to claim 13, further comprising means for determining which of the related navigation devices in a list of selected partners is located within a radius of a selected geographical location. A navigation device according to claim 19, further comprising means for displaying the navigation devices listed in a list of selected partners that are located within a radius of a selected geographic location; and a half to edit the partner list.