System and method for managing VoLTE session continuity information using logical scalable units
First Claim
1. A method of communicating messages in a communication system, comprising:
- receiving at least one of an Authentication Authorization Request (AAR) message or a Session Termination Request (STR) message from a first client component, wherein the received message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoLTE call;
extracting first information from the received message, and using the extracted first information to obtain a common key;
using the obtained common key to;
identify an application component, andretrieve session continuity information from a cache memory, wherein the session continuity information includes at least one of Gx session information, a session continuation (SC) parameter, or a VoLTE-Session-Continuity Attribute-Value-Pair (AVP);
generating an updated AAR or STR message that includes the retrieved session continuity information and sending the updated message to the identified application component;
receiving an Authentication Authorization Answer (AAA) message or an Session-Termination-Answer (STA) message from the identified application component and forwarding the received message to the first client component;
receiving a Re-Authorization Request (RAR) message that includes updated session continuity information from the identified application component, extracting second information from the received RAR 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 RAR message; and
sending the received RAR message to a second client component.
1 Assignment
0 Petitions
Accused Products
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.
33 Citations
25 Claims
-
1. A method of communicating messages in a communication system, comprising:
-
receiving at least one of an Authentication Authorization Request (AAR) message or a Session Termination Request (STR) message from a first client component, wherein the received message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoLTE call; extracting first information from the received 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 at least one of Gx session information, a session continuation (SC) parameter, or a VoLTE-Session-Continuity Attribute-Value-Pair (AVP); generating an updated AAR or STR message that includes the retrieved session continuity information and sending the updated message to the identified application component; receiving an Authentication Authorization Answer (AAA) message or an Session-Termination-Answer (STA) message from the identified application component and forwarding the received message to the first client component; receiving a Re-Authorization Request (RAR) message that includes updated session continuity information from the identified application component, extracting second information from the received RAR 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 RAR message; and sending the received RAR message to a second client component. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 21, 22, 23, 24)
-
-
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 at least one of an Authentication Authorization Request (AAR) message or a Session Termination Request (STR) message from a first client component, wherein the received message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoLTE call; extracting first information from the received 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 the cache memory, wherein the session continuity information includes at least one of Gx session information, a session continuation (SC) parameter, or a VoLTE-Session-Continuity Attribute-Value-Pair (AVP); generating an updated AAR or STR message that includes the retrieved session continuity information and sending the updated message to the identified application component; receiving an Authentication Authorization Answer (AAA) message or an Session-Termination-Answer (STA) message from the identified application component and forwarding the received first message to the first client component; receiving a Re-Authorization Request (RAR) message that includes updated session continuity information from the identified application component, extracting second information from the received RAR 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 RAR message; and sending the received RAR message to a second client component. - View Dependent Claims (12, 13, 14, 15)
-
-
16. 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:
-
receiving at least one of an Authentication Authorization Request (AAR) message or a Session Termination Request (STR) message from a first client component, wherein the received message was sent in response to the first client component determining that a user equipment set-up, modified, or terminated a VoLTE call; extracting first information from the received 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 at least one of Gx session information, a session continuation (SC) parameter, or a VoLTE-Session-Continuity Attribute-Value-Pair (AVP); generating an updated AAR or STR message that includes the retrieved session continuity information and sending the updated message to the identified application component; receiving an Authentication Authorization Answer (AAA) message or an Session-Termination-Answer (STA) message from the identified application component and forwarding the received message to the first client component; receiving a Re-Authorization Request (RAR) message that includes updated session continuity information from the identified application component, extracting second information from the received RAR 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 RAR message; and sending the received RAR message to a second client component. - View Dependent Claims (17, 18, 19, 20)
-
-
25. A system, comprising:
-
a first client component comprising at least one of a router agent (RA) component, an enforcement component, or an application function (AF) component; a second client component; and a logical scalable unit (LSU) component comprising; a LSU frontend component; one or more session stores; and one or more policy management system (PMS) components, wherein a client processor in the first client component is configured with processor-executable instructions to perform operations comprising; determining whether a user equipment device accepted an incoming VoLTE call request; and sending one or more Rx messages to the LSU component in response to determining that the user equipment device accepted the incoming VoLTE call request, wherein the one or more Rx messages include an Rx Authentication Authorization Request (Rx AAR) message; wherein the LSU frontend processor is configured with processor-executable instructions to perform operations comprising; receiving the Rx AAR message from the first client component; using information included in the received Rx AAR message to obtain a common key, using the obtained common key to identify a PMS component, and using the obtained common key to retrieve at least one of Gx session information, a session continuation (SC) parameter, or a VoLTE-Session-Continuity Attribute-Value-Pair (AVP) from a session store in the one or more session stores; generating an updated Rx AAR message that includes the Gx session information, the SC parameter or the VoLTE-Session-Continuity APV, and sending the updated Rx AAR message to the identified PMS component; receiving a Rx Authentication Authorization Answer (Rx AAA) message from the identified PMS component and forwarding the received Rx AAA message to the first client component; receiving from the identified PMS component a Gx Re-Authorization Request (Gx RAR) message that includes an Rx session identifier that identifies the relevant Rx session, an enforcement identifier that identifies an enforcement component associated with the relevant Rx session, and one or more rules associated with the identified enforcement component; identifying the common key based on the Rx session identifier included in the received RAR message, and using the identified common key to identify the session store in the one or more session stores that stores the at least one of Gx session information, SC parameter, or VoLTE-Session-Continuity APV; updating the information stored in the identified session store based on the information included in the received Gx RAR message; and sending the received Gx RAR message to the second client component.
-
Specification