Management of multiple user identities in a communication system

• US 7,620,391 B2
• Filed: 02/24/2006
• Issued: 11/17/2009
• Est. Priority Date: 01/21/2005
• Status: Active Grant

• Current Assignee: Oracle Israel Limited (Oracle Corporation)
• Original Assignee: Convergin Israel Ltd.
• Inventors: Livyatan, Tzach, Itzkovitz, Ayal, Zoller, Tal
• Primary Examiner(s): Taylor; Barry W
• Application Number:
  US11/361,839
• Publication Number:
  US 20060234690A1
• Time in Patent Office: 1,362 Days
• Field of Search: 455/435.1, 455/445, 455/416, 455/432.1, 455/432.3, 455/433, 455/461
• US Class Current: 455/416
• CPC Class Codes: H04L 61/4547 for personal communications, i.e. using a personal identifier
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 61/5092 by self-assignment, e.g. picking addresses at random and testing if they are already in use
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1095 Inter-network session transfer or sharing
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 2207/20 hybrid systems
• CPC Class Codes: H04M 3/42272 whereby the subscriber registers to the terminals for personalised service provision
• CPC Class Codes: H04M 7/0075 Details of addressing, directories or routing tables
• CPC Class Codes: H04M 7/123 where the packet-switched network is an Internet Protocol Multimedia System-type network
• CPC Class Codes: H04M 7/1235 where one of the core networks is a wireless network
• CPC Class Codes: H04M 7/127 where the session control protocols comprise SIP and SS7
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04W 76/11 Allocation or use of connection identifiers
• CPC Class Codes: H04W 76/16 : Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
• CPC Class Codes: H04W 8/26 : Network addressing or numbering for mobility support
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices

Abstract

A computer-implemented method for communication includes assigning to at least first and second communication terminals (22) of a communication system (20) at least respective first and second private identities and a common public identity different from at least the first and second private identities. Registrations of the public identity and of at least the first and second private identities are simultaneously maintained in the communication system (20). A request is received to set up a call in which the public identity serves as one of a source and a destination of the call. The call is established between a third communication terminal and one of at least the first and second communication terminals (22) using the simultaneously-maintained registrations.

Claims

1. A computer-implemented method for communication, comprising:

assigning to at least first and second communication terminals of a communication system at least respective first and second private identities and a common public identity different from at least the first and second private identities;

storing an association between the private identities and the common public identity in a Convergence Server (CS) connected to the communication system;

maintaining at least one of first and second registration records, which respectively represent the first and second private identities, in a database of the communication system that is separate from the CS;

simultaneously with the at least one of the first and second registration records, maintaining in the database an additional registration record, which represents the common public identity and comprises an identification of the CS as a Visitor Location Register (VLR) of the common public identity;

receiving at the database a request to set up a call in which the public identity serves as one of a source and a destination of the call;

based on the identification of the CS as the VLR of the common public identity by the additional registration record, querying the association stored in the CS in order to identify one or more of the private identities that is to participate in the call; and

establishing the call between a third communication terminal and one of at least the first and second communication terminals using the registration records of the private identities identified using the queried association.

2. The method according to claim 1, wherein the first communication terminal communicates with a first network conforming to a first communication domain, and wherein the second communication terminal communicates with a second network conforming to a second communication domain different from the first communication domain.

3. The method according to claim 2, wherein establishing the call comprises invoking a first service platform in the first network to provide a first call service and invoking a second service platform in the second network to provide a second call service, the first and second call services associated with the public identity.

4. The method according to claim 1, wherein receiving the request comprises receiving an incoming call destined to a subscriber associated with the public identity, and wherein establishing the call comprises selecting a terminal from among the first and second communication terminals, and routing the incoming call to one of the first and second private identities that is assigned to the selected terminal.

5. The method according to claim 4, wherein routing the incoming call comprises routing the incoming call to the selected terminal via the CS.

6. The method according to claim 5, wherein routing the incoming call comprises assigning to the received incoming call a first temporary routable number (TRN) associated with the CS in order to cause the incoming call to be routed to the CS.

7. The method according to claim 6, wherein routing the incoming call further comprises assigning to the incoming call routed to the CS a second TRN so as to cause the incoming call to be routed from the CS to the selected terminal.

8. The method according to claim 6, wherein assigning the first TRN comprises caching at the CS a linkage between the first TRN and the public identity and, when the incoming call routed to the CS does not carry the public identity, determining the public identity responsively to the cached linkage.

9. The method according to claim 1, wherein receiving the request comprises receiving an outgoing call initiated by an initiating terminal comprising one of the first and second communication terminals, the outgoing call addressed to a destination, and wherein establishing the call comprises routing the outgoing call to the destination via the CS.

10. The method according to claim 9, wherein routing the outgoing call comprises replacing in the outgoing call a private identity of the initiating terminal with the public identity.

11. The method according to claim 9, wherein routing the outgoing call via the CS comprises assigning to the received outgoing call a temporary routable number (TRN) associated with the CS, so as to cause the outgoing call to be routed to the CS, and subsequently routing the outgoing call from the CS to the destination.

12. The method according to claim 11, wherein assigning the TRN comprises caching at the CS a linkage between the assigned TRN and one of the first and second private identities associated with the initiating terminal, and, when the outgoing call routed to the CS does not carry the private identity of the initiating terminal, determining the private identity of the initiating terminal responsively to the cached linkage.

13. The method according to claim 1, wherein establishing the call comprises invoking a call service associated with the public identity.

14. The method according to claim 1, wherein establishing the call comprises handing-off the call from the one of the first and second communication terminals to another of the first and second communication terminals.

15. The method according to claim 1, wherein the database comprises a Home Location Register (HLR).

16. A Convergence Server (CS), comprising:

a registry, which is arranged to hold an association between at least first and second private identities of at least respective first and second communication terminals of a communication system and a common public identity different from at least the first and second private identities; and

a processor, which is arranged to cause an identity database of the communication system that is separate from the CS to maintain at least one of first and second registration records, which respectively represent the first and second private identities, to cause the identity database to maintain, simultaneously with the at least one of the first and second registration records, an additional registration record, which represents the common public identity and comprises an identification of the CS as a Visitor Location Register (VLR) of the common public identity, to receive a request to set up a call in which the public identity serves as one of a source and a destination of the call, to query the association stored in the CS in response to the identification of the CS as the VLR of the common public identity by the additional registration record, in order to identify one or more of the private identities that is to participate in the call, and to establish the call between a third communication terminal and one of at least the first and second communication terminals using the registration records of the private identities identified using the queried association.

17. The convergence server according to claim 16, wherein the first communication terminal communicates with a first network conforming to a first communication domain, wherein the second communication terminal communicates with a second network conforming to a second communication domain different from the first communication domain, and wherein the CS is connected to the first and second networks.

18. The convergence server according to claim 17, wherein the processor is arranged to invoke a first service platform in the first network to provide a first call service and to invoke a second service platform in the second network to provide a second call service, the first and second call services associated with the public identity.

19. The convergence server according to claim 16, wherein the processor is arranged to receive an incoming call destined to a subscriber associated with the public identity, to select a terminal from among the first and second communication terminals and to route the incoming call to one of the first and second private identities that is assigned to the selected terminal.

20. The convergence server according to claim 19, wherein the processor is arranged to cause the incoming call to be routed to the selected terminal via the convergence server.

21. The convergence server according to claim 20, wherein the processor is arranged to assign to the received incoming call a first temporary routable number (TRN) associated with the CS in order to cause the incoming call to be routed to the CS.

22. The convergence server according to claim 21, wherein the processor is further arranged to assign to the incoming call routed to the CS a second TRN so as to cause the incoming call to be routed from the CS to the selected terminal.

23. The convergence server according to claim 21, and comprising a redirection proxy arranged to store call contexts, wherein the processor is arranged to cache in the redirection proxy a linkage between the first TRN and the public identity and, when the incoming call routed to the CS does not carry the public identity, to determine the public identity responsively to the cached linkage.

24. The convergence server according to claim 16, wherein the processor is arranged to receive an outgoing call initiated by an initiating terminal comprising one of the first and second communication terminals, the outgoing call addressed to a destination, and to cause the outgoing call to be routed to the destination via the CS.

25. The convergence server according to claim 24, wherein the processor is arranged to replace in the outgoing call a private identity of the initiating terminal with the public identity.

26. The convergence server according to claim 24, wherein the processor is arranged to assign to the received outgoing call a temporary routable number (TRN) associated with the CS, so as to cause the outgoing call to be routed to the CS, and to subsequently route the outgoing call from the CS to the destination.

27. The convergence server according to claim 26, and comprising a redirection proxy arranged to store call contexts, wherein the processor is arranged to cache in the redirection proxy a linkage between the assigned TRN and one of the first and second private identities associated with the initiating terminal, and, when the outgoing call routed to the CS does not carry the private identity of the initiating terminal, to determine the private identity of the initiating terminal responsively to the cached linkage.

28. The convergence server according to claim 16, wherein the processor is arranged to invoke a call service associated with the public identity.

29. The convergence server according to claim 16, wherein the processor is arranged to hand-off the call from the one of the first and second communication terminals to another of the first and second communication terminals.

30. The convergence server according to claim 16, wherein the identity database comprises a Home Location Register (HLR).

31. A communication system, comprising:

at least first and second communication terminals having at least respective first and second private identities;

an identity database; and

a convergence server (CS), which is coupled to assign to at least the first and second communication terminals a common public identity different from at least the first and second private identities, to hold an association between the private identities and the common public identity, to cause the identity database to maintain at least one of first and second registration records, which respectively represent the first and second private identities, to cause the identity database to maintain, simultaneously with the at least one of the first and second registration records, an additional registration record, which represents the common public identity and comprises an identification of the CS as a Visitor Location Register (VLR) of the common public identity, to receive a request to set up a call in which the public identity serves as one of a source and a destination of the call, to query the association stored in the CS in response to the identification of the CS as the VLR of the common public identity by the additional registration record, in order to identify one or more of the private identities that is to participate in the call, and to establish the call between a third communication terminal and one of at least the first and second communication terminals using the registration records of the private identities identified using the queried association.

32. A computer software product for communication, the product comprising a tangible computer-readable medium, in which program instructions are stored, which instructions, when read by a computer, cause the computer to hold an association between at least first and second private identities of at least respective first and second communication terminals and a common public identity different from at least the first and second private identities, to cause an identity database to maintain at least one of first and second registration records, which respectively represent the first and second private identities, to cause the identity database to maintain, simultaneously with the at least one of the first and second registration records, an additional registration record, which represents the common public identity and comprises an identification of the CS as a Visitor Location Register (VLR) of the common public identity, to receive a request to set up a call in which the public identity serves as one of a source and a destination of the call, to query the association stored in the CS in response to the identification of the CS as the VLR of the common public identity by the additional registration record, in order to identify one or more of the private identities that is to participate in the call, and to establish the call between a third communication terminal and one of at least the first and second communication terminals using the registration records of the private identities identified using the queried association.