User-location service for ad hoc, peer-to-peer networks

• US 20050138119A1
• Filed: 12/23/2003
• Published: 06/23/2005
• Est. Priority Date: 12/23/2003
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Saridakis, Titos
• Application Number:
  US10/745,961
• Publication Number:
  US 20050138119A1
• Time in Patent Office: Days
• US Class Current: 709/204
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04W 8/26 Network addressing or numbering for mobility support
• CPC Class Codes: H04W 80/00 Wireless network protocols or protocol adaptations to wireless operation
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

The present invention relates to a method, a terminal and a system for handling information about the presence of users in an ad hoc, peer-to-peer network. Mapping lists are stored in local repositories of terminals present in the network. The mapping list comprise mappings of user-addresses of the users to network addresses of the terminals present in the network. The mapping lists in the terminals present in the network are updated with respect to the terminals present in said network at a given instance.

Claims

1. A method of handling information about the presence of users in an ad hoc, peer-to-peer network, comprising:

storing, in local repositories of terminals present in said network, mapping lists comprising mappings of user-addresses of said users to network addresses of the terminals present in the network; and

updating said mapping lists in the terminals present in the network with respect to the terminals present in said network at a given instance.

2. The method of claim 1, wherein the updating is performed coordinated between the terminals present in said network in response to terminals joining said network and terminals leaving said network.

3. The method of claim 2, wherein one terminal of the terminals present in said network is a coordinating terminal, and wherein the updating comprises:

receiving, in said coordinating terminal, indications of terminals joining said network and of terminals leaving said network;

updating the mapping list in the local repository of said coordinating terminal with respect to the terminals joining said network and the terminals leaving said network;

sending, from said coordinating terminal to the terminals present in said network, the updates of the mapping list in the local repository of said coordinating terminal; and

updating the mapping lists in the local repositories in the terminals present in said network in accordance with the updates of the mapping list in the local repository of said coordinating terminal.

4. The method of claim 1, wherein said updating is done individually in a first terminal of the terminals present in said network in response to the invalidity in the mapping list in said first terminal of the mapping of the user-address to the network address of a second terminal.

5. The method of claim 4, wherein said updating comprises:

requesting, in response to the invalidity in the mapping list in said first terminal of the mapping of the user-address to the network address said second terminal, an update with respect to the mapping of the user-address to the network address of said second terminal from the terminals present in said network;

receiving in said first terminal said update with respect to the mapping of the user-address to the network address of said second terminal; and

updating the mapping list in said first terminal, in accordance with the received update.

6. The method of claim 1, wherein said mappings of user-addresses to network addresses in said mapping lists are mappings of SIP-addresses to network addresses.

7. A terminal adapted for handling information about the presence of users in an ad hoc, peer-to-peer network, comprising:

a local repository for storing a mapping list comprising mappings of user-addresses of said users to network addresses of terminals present in said network; and

a repository manager for updating said mapping list with respect to the terminals present in said network at a given instance.

8. The terminal of claim 7, wherein said repository manager is arranged to update said mapping list in response to terminals joining said network and terminal leaving said network.

9. The terminal of claim 8, further comprising:

a receiver for receiving indications of terminals joining said network and of terminals leaving said network; and

a sender for sending, from the terminal to said terminals present in said network, the updates of the mapping list.

10. The terminal of claim 7, further comprising:

a receiver for receiving updates of the mapping list of a terminal present in said network,

wherein said repository manager is arranged to update said mapping list in response to received updates.

11. The terminal of claim 7, wherein said repository manager is arranged to update said mapping list in response to the invalidity in said mapping list of the mapping of a user-address to a network address.

12. The terminal of claim 11, further comprising:

a sender for sending, in response to the invalidity in said mapping list of the mapping of the user-address to the network address, a request for an update with respect to the mapping of the user-address to the network address; and

a receiver for receiving said update with respect to the mapping of the user-address to the network address of said second terminal,

wherein said repository manager is arranged to update the mapping list, in accordance with the received update.

13. The terminal of claim 7, wherein said user-addresses are SIP addresses, further comprising:

a SIP User Agent for creating SIP requests including SIP addresses and for sending them to a local SIP Proxy;

said local SIP Proxy for receiving SIP requests from said SIP User Agent, for extracting said SIP addresses, for requesting and receiving the mapping of SIP addresses to network addresses from a local SIP Registrar, and for forwarding said SIP requests to the terminals having said network addresses; and

said local SIP Registrar for resolving the mapping of SIP addresses to network addresses by means of lookup in said local repository in the terminal.

14. A system adapted for handling information about the presence of users in an ad hoc, peer-to-peer network, comprising:

a first terminal comprising;

a first local repository for storing a first mapping list comprising mappings of user-addresses of said users to network addresses of terminals present in said network; and

a first repository manager for updating said first mapping list with respect to the terminals present in said network at a given instance; and

a second terminal comprising;

a second local repository for storing a second mapping list comprising mappings of user-addresses of said users to network addresses of the terminals present in said network; and

a second repository manager for updating said second mapping list with respect to the terminals present in said network at a given instance.

15. The system of claim 14, wherein said first repository manager is arranged to update said mapping list in response to terminals joining said network and terminal leaving said network, and said first terminal further comprises:

a first receiver for receiving indications of terminals joining said network and of terminals leaving said network; and

a first sender for sending, from the first terminal to the terminals present in said network, the updates of the mapping list, and

wherein said second terminal further comprises;

a second receiver for receiving said updates, and

said second repository manager is arranged to update the second local repository with respect to received updates.

16. The system of claim 14, wherein said first terminal further comprises:

a first sender for sending, in response to the invalidity in said mapping list of the mapping of the user-address to the network address of the second terminal, a request for an update with respect to the mapping of the user-address to the network address of the second terminal to the terminals present in the network; and

a first receiver for receiving said update with respect to the mapping of the user-address to the network address of said second terminal, and

said first repository manager is arranged to update the mapping list, in accordance with the received update, and

wherein said second terminal further comprises;

a second receiver for receiving said request; and

a second sender for sending said update.

17. The system of claim 14, wherein said user-addresses are SIP addresses, and said first terminal further comprising:

a first SIP User Agent for creating SIP requests including SIP addresses and for sending them to a first local SIP Proxy;

said first local SIP Proxy for receiving SIP requests from said first SIP User Agent, for extracting said SIP addresses, for requesting and receiving the mapping of SIP addresses to network addresses from a first local SIP Registrar, and for forwarding said SIP requests to the terminals having said network addresses; and

said first local SIP Registrar for resolving the mapping of SIP addresses to network addresses by means of lookup in said first local repository in the first terminal,

and said second terminal further comprising;

a second SIP User Agent for creating SIP requests including SIP addresses and for sending them to a second local SIP Proxy;

said second local SIP Proxy for receiving SIP requests from said second SIP User Agent, for extracting said SIP addresses, for requesting and receiving the mapping of SIP addresses to network addresses from a second local SIP Registrar, and for forwarding said SIP requests to the terminals having said network addresses; and

said second local SIP Registrar for resolving the mapping of SIP addresses to network addresses by means of lookup in said second local repository in the second terminal.