Optimal routing when two or more network elements are integrated in one element

• US 20050013285A1
• Filed: 05/28/2001
• Published: 01/20/2005
• Est. Priority Date: 05/28/2001
• Status: Abandoned Application

• Current Assignee: Nokia Corporation
• Original Assignee: Nokia Corporation
• Inventors: Westman, Iikka
• Application Number:
  US10/479,051
• Publication Number:
  US 20050013285A1
• Time in Patent Office: Days
• US Class Current: 370/351
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04Q 3/0037 involving call modelling techniques, e.g. modifications to the basic call state model [BCSM]
• CPC Class Codes: H04W 76/10 Connection setup

Abstract

A call is routed between at least two logical network elements each performing a logical functionality on the call, the logical functionalities of the at least two logical network elements being accommodated in one physical control entity in an IP communication network system. When a call is received at the physical control entity as a first logical functionality, call-related processing is performed in the physical control entity as the first logical functionality, thereby obtaining a content of a first data structure. Then, a second logical functionality is invoked in the physical control entity, wherein the content of the first data structure is supplied inside the physical control entity to a second data structure of the second logical functionality so that the content of the second data structure is substantially similar too a content obtained at the same stage in said second logical functionality by external routing between logical network elements.

Claims

1. A method of routing a call between at least two logical network elements each performing a logical functionality on said call, said logical functionalities of said at least two logical network elements being accommodated in one physical control entity in an IP communication network system, said method comprising the steps of:

receiving a call at said physical control entity as a first logical functionality;

performing call-related processing in said physical control entity as said first logical functionality, thereby obtaining a content of a first data structure; and

invoking a second logical functionality in said physical control entity, wherein said content of said first data structure is supplied inside said physical control entity to a second data structure of said second logical functionality so that the content of said second data structure is substantially similar to a content obtained at the same stage in said second logical functionality by external routing between logical network elements.

2. A method according to claim 1, wherein said content of said first data structure is supplied within one call state model for a beginning of a functionality and an ending of a functionality.

3. A method according to claim 1, wherein said content of said first data structure is supplied by sending a message inside said physical control entity from a call state model for an ending of a functionality to a call state model for a beginning of a functionality.

4. A method according to claim 1, wherein said content of said first data structure is supplied by sending a first message from a call state model for an ending of a functionality to a first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, sending a second message from said first adapter process to a second adapter process for supplying said content of said inter network element sending signaling data structure to a data structure of an inter network element receiving signaling, so that the content of said inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, and sending a third message from said second adapter process to a call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

5. A method according to claim 1, wherein said content of said first data structure is supplied by sending a first message from a call state model for an ending of a functionality to a first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, performing processing on the content of said inter network element sending signaling data structure, thereby obtaining a content of a processed inter network element sending signaling data structure, sending a second message from said first adapter process to a second adapter process for supplying said content of said processed inter network element sending signaling data structure to a data structure of a processed inter network element receiving signaling, so that the content of said processed inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, performing processing on said content of said processed inter network element receiving signaling data structure, thereby obtaining a content of an inter network element receiving signaling data structure and sending a third message from said second adapter process to a call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

6. A method according to claim 1, wherein said content of said first data structure is supplied by sending a first message from a call state model for an ending of a functionality to a first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, performing processing on the content of said inter network element sending signaling data structure, thereby obtaining a content of a processed inter network element sending signaling data structure, performing looping from said first adapter process to a second adapter process via a protocol level below the used signaling protocol between network elements for supplying said content of said processed inter network element sending signaling data structure to a data structure of a processed inter network element receiving signaling, so that the content of said processed inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, performing processing on said content of said processed inter network element receiving signaling data structure, thereby obtaining a content of an inter network element receiving signaling data structure and sending a third message from said second adapter process to a call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

7. A method according to claim 3, wherein, when said message is received at said call state model for a beginning of a functionality, an identification of the logical network element performing said second logical functionality is added to a record-route field in said message.

8. A method according to claim 3, wherein, when said message is received at said call state model for a beginning of a functionality, no identification of the logical network element performing said second logical functionality is added to a field of said message, which indicates a path taken by a request so far.

9. A method according to claim 4, wherein, when said second message is received, an identification of the logical network element performing said second logical functionality is added to a record-route field in said second message.

10. A method according to claim 4, wherein, when said second message is received, no identification of the logical network element performing said second logical functionality is added to a field of said second message, which indicates a path taken by a request so far.

11. A method according to claim 6, wherein, when performing looping from said first adapter process to said second adapter process, an identity of a local host and/or a loopback address are used.

12. A method according to claim 6, wherein, when the looped content is received at said second adapter process, an identification of the logical network element performing said second logical functionality is added to a record-route field in said looped content.

13. A method according to claim 6, wherein, when the looped content is received at said second adapter process, no identification of the logical network element performing said second logical functionality is added to a field of said looped content, which indicates a path taken by a request so far.

14. A method according to claim 6, wherein, when the looped content is received at said second adapter process, a previous entry of a record-route field in said looped content is used as identification of the logical network element performing said second logical functionality in said record-route field.

15. A method according to claim 3, wherein in the message supplied to said call state model for a beginning of a functionality a service required in the next network element is indicated.

16. A method according to claim 3, wherein the internal messages are call control protocol messages.

17. A method according to claim 1, wherein it is determined by said first logical functionality whether the second logical functionality can be invoked at the same physical control entity by analyzing destination information for the call.

18. A method according to claim 17, wherein said first logical functionality is a serving call state control function of an IP multimedia system.

19. A method according to claim 17, wherein said second logical functionality is an interrogating call state control function of an IP multimedia system.

20. A method according to claim 17, wherein said first logical functionality is a proxy call state control function of an IP multimedia system.

21. A method according to claim 17, wherein said second logical functionality is a serving call state control function of an IP multimedia system.

22. A method according to claim 17, wherein the destination information for the call comprises an FQDN.

23. A method according to claim 17, wherein the destination information for the call comprises the IP-address obtained by performing a DNS resolution procedure for at least part of a target identification.

24. A method according to claim 23, wherein the identification comprises an FQDN.

25. A control entity for routing a call between at least two logical network elements each performing a logical functionality on said call, said logical functionalities of said at least two logical network elements being accommodated in said control entity in an IP communication network system, said control entity being arranged to:

receiving a call as a first logical functionality;

performing call-related processing as said first logical functionality, thereby obtaining a content of a first data structure; and

invoking a second logical functionality,

wherein said content of said first data structure is supplied inside said control entity to a second data structure of said second logical functionality so that the content of said second data structure is substantially similar to a content obtained at the same stage in said second logical functionality by external routing between logical network elements.

26. A control entity according to claim 25, comprising one call state model for a beginning of a functionality and an ending of a functionality, wherein said content of said first data structure is supplied within said one call state model.

27. A control entity according to claim 25, comprising;

a call state model for an ending of a functionality; and

a call state model for a beginning of a functionality,

wherein said content of said first data structure is supplied by sending a message from said call state model for an ending of a functionality to said call state model for a beginning of a functionality.

28. A control entity according to claim 25, comprising:

a call state model for an ending of a functionality;

a call state model for a beginning of a functionality;

a first adapter process communicating with said call state model for an ending of a functionality; and

a second adapter process communicating with said call state model for a beginning of a functionality,

wherein, for supplying said content of said first data structure, said call state model for an ending of a functionality sends a first message to said first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, said first adapter process sends a second message to said second adapter process for supplying said content of said inter network element sending signaling data structure to a data structure of an inter network element receiving signaling, so that the content of said inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, and said second adapter process sends a third message to said call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

29. A control entity according to claim 25, comprising:

a call state model for an ending of a functionality;

a call state model for a beginning of a functionality;

a first adapter process communicating with said call state model for an ending of a functionality; and

a second adapter process communicating with said call state model for a beginning of a functionality,

wherein, for supplying said content of said first data structure, said call state model for an ending of a functionality sends a first message to said first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, said first adapter process performs processing on the content of said inter network element sending signaling data structure, thereby obtaining a content of a processed inter network element sending signaling data structure, and sends a second message to said second adapter process for supplying said content of said processed inter network element sending signaling data structure to a data structure of a processed inter network element receiving signaling, so that the content of said processed inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, said second adapter process performs processing on said content of said processed inter network element receiving signaling data structure, thereby obtaining a content of an inter network element receiving signaling data structure, and sends a third message to said call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

30. A control entity according to claim 25, comprising:

a call state model for an ending of a functionality;

a call state model for a beginning of a functionality;

a first adapter process communicating with said call state model for an ending of a functionality; and

a second adapter process communicating with said call state model for a beginning of a functionality,

wherein, for supplying said content of said first data structure, said call state model for an ending of a functionality sends a first message to said first adapter process for translating said content of said first data structure to a data structure of an inter network element sending signaling, said first adapter process performs processing on the content of said inter network element sending signaling data structure, thereby obtaining a content of a processed inter network element sending signaling data structure, and performs looping to said second adapter process via a protocol level below the used signaling protocol between network elements for supplying said content of said processed inter network element sending signaling data structure to a data structure of a processed inter network element receiving signaling, so that the content of said processed inter network element receiving signaling data structure is substantially similar to a content obtained at the same stage in said second adapter process by external routing between logical network elements, said second adapter process performs processing on said content of said processed inter network element receiving signaling data structure, thereby obtaining a content of an inter network element receiving signaling data structure, and sends a third message to said call state model for a beginning of a functionality, for translating said content of said inter network element receiving signaling data structure to said second data structure.

31. A control entity according to claim 27, wherein, when said call state model for a beginning of a functionality receives said message, said control entity adds an identification of the logical network element performing said second logical functionality to a record-route field in said message.

32. A control entity according to claim 27, wherein, when said call state model for a beginning of a functionality receives said message, said control entity adds no identification of the logical network element performing said second logical functionality to a field of said message, which indicates a path taken by a request so far.

33. A control entity according to claim 28, wherein, when said second message is received, said control entity adds an identification of the logical network element performing said second logical functionality to a record-route field in said second message.

34. A control entity according to claim 28, wherein, when said second message is received, said control entity adds no identification of the logical network element performing said second logical functionality to a field of said second message, which indicates a path taken by a request so far.

35. A control entity according to claim 30, wherein, when said first adapter process performs looping to said second adapter process, said control entity uses an identity of a local host and/or a loopback address.

36. A control entity according to claim 30, wherein, when said second adapter process receives the looped content, said control entity adds an identification of the logical network element performing said second logical functionality to a record-route field in said looped content.

37. A control entity according to claim 30, wherein, when said second adapter process receives the looped content, said control entity adds no identification of the logical network element performing said second logical functionality to a field of said looped content, which indicates a path taken by a request so far.

38. A control entity according to claim 30, wherein, when said second adapter process receives the looped content, said control entity uses a previous entry of a record-route field in said looped content as identification of the logical network element performing said second logical functionality in said record-route field.

39. A control entity according to claim 27, wherein said control entity indicates, in the message supplied to said call state model for a beginning of a functionality, a service required in the next network element.

40. A control entity according to claim 27, wherein the internal messages are call control protocol messages.

41. A control entity according to claim 25, wherein said first logical functionality determines whether the second logical functionality can be invoked at the same physical control entity by analyzing destination information for the call.

42. A control entity according to claim 41, wherein said first logical functionality is a serving call state control function of an IP multimedia system.

43. A control entity according to claim 41, wherein said second logical functionality is an interrogating call state control function of an IP multimedia system.

44. A control entity according to claim 41, wherein said first logical functionality is a proxy call state control function of an IP multimedia system.

45. A control entity according to claim 41, wherein said second logical functionality is a serving call state control function of an IP multimedia system.

46. A control entity according to claim 41, wherein the destination information for the call comprises an FQDN.

47. A control entity according to claim 41, wherein the destination information for the call comprises the IP-address obtained by performing a DNS resolution procedure for at least part of a target identification.

48. A control entity according to claim 47, wherein the identification comprises an FQDN.