Routing messages

• US 20060120362A1
• Filed: 02/19/2004
• Published: 06/08/2006
• Est. Priority Date: 02/19/2003
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Lahtinen, Lauri, Bajko, Gabor, Bertenyi, Balazs, Westman, Ilkka, Kiss, Krisztian, Beres, Ervin
• Application Number:
  US10/521,772
• Publication Number:
  US 20060120362A1
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 2101/395 Internet protocol multimedia private identity [IMPI]; Internet protocol multimedia public identity [IMPU]
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/72 Routing based on the source address
• CPC Class Codes: H04L 45/74 Address processing for routing
• CPC Class Codes: H04L 47/00 Traffic control in data switching networks arrangements for detecting or preventing errors in the information received H04L1/00
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/18 End to end
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/4541 Directories for service discovery
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 61/4588 containing mobile subscriber information, e.g. home subscriber server [HSS]
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1066 Session management
• 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: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 40/00 : Communication routing or communication path finding
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 8/02 : Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/08 : Mobility data transfer
• CPC Class Codes: H04W 84/18 : Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

This invention relates to a method of routing for a message via an IMS system is disclosed. A message is received at an ICSCF. Address information is obtained for one of an application server, server or gateway for which said message is intended. The message is sent to said application server, server or gateway in accordance with said address information.

Claims

1. A method of routing for a message via an IMS system comprising the steps of:

receiving a message at an I-CSCF;

obtaining address information for a network function for which said message is intended; and

sending said message to said network function in accordance with said address information.

2. A method as claimed in claim 1, wherein said message is sent directly to the network function via a proxy or gateway element.

3. A method as claimed in claim 1, wherein said obtaining step comprises querying a database.

4. A method as claimed in claim 3, wherein said database comprises a SLF.

5. A method as claimed in claim 3, wherein said database provides said address information for said network function.

6. A method as claimed in claim 3, wherein said database provides information identifying a further database.

7. A method as claimed in claim 6, wherein said further database comprises one of a HSS, UMS or SSR.

8. A method as claimed in claim 6, wherein said further database contains said address information.

9. A method as claimed in claim 6, wherein said further database contains configuration information of said network function.

10. A method as claimed in claim 1, comprising the step of determining if said message is for an IMS target or a non-IMS target.

11. A method as claimed in claim 10, wherein said steps of claim 1 are followed if it is determined that said message is for a non-IMS target.

43. A method as claimed in claim 1, wherein said network function comprises a server, said server being arranged to send a message for at least one user via a S-CSCF and to send a message for a least one user via an I-CSCF.

12. A method of routing a message from a network function via an IMS system comprising the steps of:

originating a message from an network function;

determining the address of a proxy entity to which said message is to be sent;

routing said message to said proxy entity; and

routing said message from said proxy entity to an entry point of a target network.

13. A method as claimed in claim 12, wherein said entry point is in the same network as said AS.

14. A method as claimed in claim 12, wherein said entry point is in a different network to said AS.

15. A method as claimed in claim 12, wherein said originating step comprises originating one of a session and a transaction.

16. A method as claimed in claim 12, wherein said determining step comprises the step of querying one of a database, table, file and a list.

17. A method as claimed in claim 12, wherein said determining step comprises determining the proxy entity from information contained in said function.

18. A method as claimed in claim 12, comprising the step of determining the entry point to which said message is to be routed.

19. A method as claimed in claim 12, wherein said proxy entity is arranged to determine the target entry point to which said message is to be sent.

20. A method as claimed in claim 19, wherein said proxy entity is arranged to determine the target entry point to which said message is to be sent by accessing a database.

21. A method as claimed in claim 20, wherein said database comprises a DNS.

22. A method of routing a message from a network function via an IMS system comprising the steps of:

originating a message from a network function;

determining the I-CSCF to which said message is to be sent;

routing said message directly to said I-CSCF if said I-CSCF is in a same network as said network function.

23. A method of routing a message from a network function via an IMS system comprising the steps of:

originating a message from a network function;

determining the I-CSCF to which said message is to be sent;

routing said message directly to said I-CSCF if said I-CSCF is in a trusted network.

24. A method of routing a message from a network function via an IMS system, said method comprising the steps of:

sending a request from the network function to an I-CSCF;

determining at the I-CSCF the S-CSCF to which a message from said network function is to be sent; and

sending said message to the determined S-CSCF.

25. A method as claimed in claim 24, wherein said network function comprises a PLS.

26. A method as claimed in claim 24, wherein said determining step comprises querying a database.

27. A method as claimed in claim 24, wherein said determining step comprises querying a HSS.

28. A method of routing a message from a first network function via an IMS system, said method comprising the steps of:

sending a request from the first network function to an I-CSCF;

determining at the I-CSCF a second network function to which a message from said first network function is to be sent; and

sending said message directly from the I-CSCF to said second network function.

29. A method as claimed in claim 28, wherein said network function comprises a network entity.

30. A method as claimed in claim 28, wherein said network function comprises one of application server, server and gateway.

31. A method as claimed in claim 28, wherein said network function provides an adaptation functionality.

32. A method of routing a message comprising the steps of:

receiving a message in accordance with a first protocol;

converting said message to a second protocol;

querying a database using identification information in said message to obtain new identification information; and

using said new identification information to route the message to a proxy.

33. A method as claimed in claim 32, wherein said proxy is arranged to route said message.

34. A method as claimed in claim 32, wherein said proxy is arranged to obtain a translation of said identity.

35. A method as claimed in claim 32, wherein said proxy routes the message to another network.

36. A method as claimed in claim 35, wherein the proxy routes the message to an I-CSCF.

37. A method as claimed in claim 32, wherein an I-CSCF is arranged to query said database.

38. A method as claimed in claim 37, wherein said I-CSCF is arranged to route said message to said proxy.

39. A method as claimed in claim 38, wherein an entity receiving said message is arranged to route said message to said proxy.

40. A method as claimed in claim 32, wherein said second protocol is SIP.

41. A method as claimed in claim 32, wherein said proxy is arranged to route said message to a gateway.

42. A method of routing for a message via an IMS system comprising the steps of:

sending a message to an I-CSCF from a network function based on address information obtained by said network function;

obtaining address information at said I-CSCF for said message; and

sending said message from said I-CSCF in accordance with said address information.

44. A server arrangement for providing a service via a network to at least one entity, said server comprising:

a server for offering services to at least one subscriber via said network; and

a database storing information about said at least one subscriber.

45. A server arrangement as claimed in claim 44, wherein said database is part of said server.

46. An arrangement as claimed in claim 44, wherein said database is separate from said server.

47. A server arrangement as claimed in claim 44, wherein in use, said server is operated independently of said network

48. A server arrangement as claimed in claim 44, wherein said network is operated by a network provider and said server is operated by a service provider, said network provider and said service provider being different.

49. A server arrangement as claimed in claim 44, wherein said server and said database are operated by a common service provider.

50. A server arrangement as claimed in claim 44, wherein said network is used for routing between said server and at least one subscriber.

51. A method of providing a service to a subscriber from a server via a network, said method comprising the steps of:

Providing service information for a subscriber, said service information being provided by a server arrangement, said server arrangement comprising a server and at least one database containing subscriber information; and

Routing said service information via a network.

52. A method as claimed in claim 51, wherein at least one database is part of said server.

53. A method as claimed in claim 51, wherein said server arrangement is operated by a service provider, different to an operator providing said network.

54. A method as claimed in claim 51, wherein said network is an IMS network.

55. A method as claimed in claim 51, wherein said at least one subscriber is an IMS subscriber.

58. A call session control function, said call session control function having a first mode in which said call session control function provides a call session control function and a second mode in which said call session control function provides an outbound proxy function.

59. A call session control function as claimed in claim 58, wherein said call session control function comprises one of a serving call session control function, an interrogating call session control function and a proxy call session control function.

60. A call session control function as claimed in claim 58, wherein said modes are selected in response to a signal received by said call session control function.

61. A call session control function as claimed in claim 60, wherein the mode is controlled in response to information contained in an address of said call session control function.

62. A call session control function as claimed in claim 60, wherein the mode is controlled in response to information provided separately from the address of said call session control function.

63. A call session control function as claimed in claim 61, wherein said information is provided in at least one of a separate header and payload.