System and method for managing VoIP session continuity information using logical scalable units

• US 10,523,545 B2
• Filed: 07/06/2018
• Issued: 12/31/2019
• Est. Priority Date: 05/29/2012
• Status: Active Grant

• Current Assignee: Openet Telecom Limited (Amdocs Ltd.)
• Original Assignee: Openet Telecom Limited (Amdocs Ltd.)
• Inventors: Haraszti, Peter, Davoren, David, Forde, Brian J., Andreucetti, Ross, Doolin, Tony, O'Connell, Niall
• Primary Examiner(s): Chea, Philip J
• Assistant Examiner(s): Ahmed, Mohammed
• Application Number:
  US16/028,733
• Publication Number:
  US 20180316589A1
• Time in Patent Office: 543 Days
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/0897 by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
• CPC Class Codes: H04L 43/0888 Throughput
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Logical scalable units (LSU) can be used within a single network data center to provide stateful scalability. However, LSUs are not suitable for operating across multiple network data centers in order to provide geographical redundancy in active-active scenarios while providing high availability. This is because the latencies associated with replicating full session information are unacceptably slow. An additional component in the LSU (known as an LSU Frontend) can be used to replicate a small subset of session information between LSUs. This subset of session information may be enough to enable LSUs to process requests in an acceptable way rather than outright failing. This may be particularly advantageous in scenarios where the requests relate to Voice over LTE calls, because outright failure is very perceivable to subscribers, and it causes resource leakage within the telecommunications network.

Claims

1. A method of communicating messages in a communication system, comprising:

receiving a first message from a first client component, wherein the received first message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoIP call;

extracting first information from the received first message, using the extracted first information to obtain a common key, and using the obtained common key to;

identify an application component, and

retrieve session continuity information from a cache memory, wherein the session continuity information includes information for maintaining session continuity for select services in the event of a failure without replicating session stores, including at least one of a session continuation (SC) parameter or a Session-Continuity Attribute-Value-Pair (AVP);

generating a second message that includes the retrieved session continuity information and sending the second message to the identified application component;

receiving a third message from the identified application component and forwarding the received third message to the first client component;

receiving a fourth message that includes updated session continuity information from the identified application component, extracting second information from the received fourth message, and determining the common key based on the extracted second information;

using the determined common key to identify the cache memory that stores the session continuity information;

updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message; and

sending the received fourth message to a second client component.

2. The method of claim 1, wherein:

the first message is an Authentication Authorization Request (AAR) message;

the second message is an updated AAR message;

the third message is an Authentication Authorization Answer (AAA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

3. The method of claim 1, wherein:

the first message is a Session Termination Request (STR) message;

the second message is an updated STR message;

the third message is a Session-Termination-Answer (STA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

4. The method of claim 1, further comprising:

generating a message that includes all the information included in the received fourth message except for the updated session continuity information,

wherein sending the fourth message to the second client component comprises sending the generated message that excludes the updated session continuity information to the second client component.

5. The method of claim 1, wherein:

using the obtained common key to retrieve session continuity information from the cache memory comprises using the obtained common key to retrieve policy session information identifying;

a policy session; and

an enforcement component associated with the policy session; and

generating the second message that includes the retrieved session continuity information comprises generating the second message to include;

policy session information; and

the common key obtained using the extracted first information.

6. The method of claim 5, wherein generating the second message that includes the retrieved session continuity information further comprises generating the second message to include application function session information.

7. The method of claim 1, wherein receiving fourth message that includes updated session continuity information from the identified application component comprises receiving a message that includes application function session information, wherein the application function session information identifies:

an application function session,

an enforcement component associated with the application function session, and

one or more rules associated with the identified enforcement component.

8. The method of claim 1, wherein updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message comprises deleting information from the identified cache memory.

9. The method of claim 8, wherein deleting information from the identified cache memory comprises delaying deletion for a period of time.

10. The method of claim 1, further comprising:

receiving the second message in the identified application component;

determining whether session information relating to the second message may be obtained from a session store;

extracting the session continuity information from the second message in response to determining that session information relating to the first message may not be obtained from a session store;

using the extracted session continuity information to make a policy decision; and

generating the updated session continuity information based on the policy decision.

11. A server computing device, comprising:

cache memory;

a processor coupled to the cache memory, wherein the processor is configured with processor-executable instructions to perform operations comprising;

receiving a first message from a first client component, wherein the received first message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoIP call;

extracting first information from the received first message, and using the extracted first information to obtain a common key;

using the obtained common key to;

identify an application component, and

retrieve session continuity information from a cache memory, wherein the session continuity information includes information for maintaining session continuity for select services in the event of a failure without replicating session stores, including at least one of a session continuation (SC) parameter or a Session-Continuity Attribute-Value-Pair (AVP);

generating a second message that includes the retrieved session continuity information and sending the second message to the identified application component;

receiving a third message from the identified application component and forwarding the received third message to the first client component;

receiving a fourth message that includes updated session continuity information from the identified application component, extracting second information from the received fourth message, and determining the common key based on the extracted second information;

using the determined common key to identify the cache memory that stores the session continuity information;

updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message; and

sending the received fourth message to a second client component.

12. The server computing device of claim 11, wherein:

the first message is an Authentication Authorization Request (AAR) message;

the second message is an updated AAR message;

the third message is an Authentication Authorization Answer (AAA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

13. The server computing device of claim 11, wherein:

the first message is a Session Termination Request (STR) message;

the second message is an updated STR message;

the third message is a Session-Termination-Answer (STA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

14. The server computing device of claim 12, wherein:

the processor is configured with processor-executable instructions to perform operations further comprising generating a message that includes all the information included in the received fourth message except for the updated session continuity information; and

the processor is configured with processor-executable instructions to perform operations such that sending the fourth message to the second client component comprises sending the generated message that excludes the updated session continuity information to the second client component.

15. The server computing device of claim 11, wherein the processor is configured with processor-executable instructions to perform operations such that:

using the obtained common key to retrieve session continuity information from the cache memory comprises using the obtained common key to retrieve policy session information identifying;

a policy session; and

an enforcement component associated with the policy session; and

generating the second message that includes the retrieved session continuity information comprises generating the second message to include;

policy session information; and

the common key obtained using the extracted first information.

16. The server computing device of claim 15, wherein the processor is configured with processor-executable instructions to perform operations such that generating the second message that includes the retrieved session continuity information further comprises generating the second message to include application function session information.

17. The server computing device of claim 11, wherein the processor is configured with processor-executable instructions to perform operations such that receiving fourth message that includes updated session continuity information from the identified application component comprises receiving a message that includes application function session information, wherein the application function session information identifies:

an application function session,

an enforcement component associated with the application function session, and

one or more rules associated with the identified enforcement component.

18. The server computing device of claim 11, wherein the processor is configured with processor-executable instructions to perform operations such that updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message comprises deleting information from the identified cache memory.

19. The server computing device of claim 18, wherein the processor is configured with processor-executable instructions to perform operations such that deleting information from the identified cache memory comprises delaying deletion for a period of time.

20. A non-transitory computer readable storage medium having stored thereon processor-executable software instructions configured to cause a processor of a server computing device to perform operations comprising, comprising:

receiving a first message from a first client component, wherein the received first message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoIP call;

extracting first information from the received first message, and using the extracted first information to obtain a common key;

using the obtained common key to;

identify an application component, and

retrieve session continuity information from a cache memory, wherein the session continuity information includes information for maintaining session continuity for select services in the event of a failure without replicating session stores, including at least one of a session continuation (SC) parameter or a Session-Continuity Attribute-Value-Pair (AVP);

generating a second message that includes the retrieved session continuity information and sending the second message to the identified application component;

receiving a third message from the identified application component and forwarding the received third message to the first client component;

receiving a fourth message that includes updated session continuity information from the identified application component, extracting second information from the received fourth message, and determining the common key based on the extracted second information;

using the determined common key to identify the cache memory that stores the session continuity information;

updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message; and

sending the received fourth message to a second client component.

21. The non-transitory computer readable storage medium of claim 20, wherein:

the first message is an Authentication Authorization Request (AAR) message;

the second message is an updated AAR message;

the third message is an Authentication Authorization Answer (AAA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

22. The non-transitory computer readable storage medium of claim 20, wherein:

the first message is a Session Termination Request (STR) message;

the second message is an updated STR message;

the third message is a Session-Termination-Answer (STA) message; and

the fourth message is a Re-Authorization Request (RAR) message.

23. The non-transitory computer readable storage medium of claim 20, wherein:

the stored processor-executable software instructions are configured to cause a processor to perform operations further comprising generating a message that includes all the information included in the received fourth message except for the updated session continuity information,

the stored processor-executable software instructions are configured to cause a processor to perform operations such that sending the fourth message to the second client component comprises sending the generated message that excludes the updated session continuity information to the second client component.

24. The non-transitory computer readable storage medium of claim 20, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that:

using the obtained common key to retrieve session continuity information from the cache memory comprises using the obtained common key to retrieve policy session information identifying;

a policy session; and

an enforcement component associated with the policy session; and

generating the second message that includes the retrieved session continuity information comprises generating the second message to include;

policy session information; and

the common key obtained using the extracted first information.

25. The non-transitory computer readable storage medium of claim 24, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that generating the second message that includes the retrieved session continuity information further comprises generating the second message to include application function session information.

26. The non-transitory computer readable storage medium of claim 20, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that receiving fourth message that includes updated session continuity information from the identified application component comprises receiving a message that includes application function session information, wherein the application function session information identifies:

an application function session,

an enforcement component associated with the application function session, and

one or more rules associated with the identified enforcement component.

27. The non-transitory computer readable storage medium of claim 20, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that updating the information stored in the identified cache memory based on the updated session continuity information included in the received fourth message comprises deleting information from the identified cache memory.

28. The non-transitory computer readable storage medium of claim 27, wherein the stored processor-executable software instructions are configured to cause a processor to perform operations such that deleting information from the identified cache memory comprises delaying deletion for a period of time.