System and method for handling stray session requests in a network environment

• US 9,420,607 B1
• Filed: 08/19/2014
• Issued: 08/16/2016
• Est. Priority Date: 05/28/2014
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Yadav, Chitresh, Guntupalli, Ravi K., Jain, Paras, Srivastava, Vimal
• Primary Examiner(s): Alam, Fayyaz
• Application Number:
  US14/463,500
• Time in Patent Office: 728 Days
• Field of Search: 455/509, 455/515, 455/516, 455/435.1
• US Class Current: 1/1
• CPC Class Codes: H04L 45/745 Address table lookup; Address filtering
• CPC Class Codes: H04L 61/503 using an authentication, authorisation and accounting [AAA] protocol, e.g. remote authentication dial-in user service [RADIUS] or Diameter
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols
• CPC Class Codes: H04W 4/025 using location based information parameters
• CPC Class Codes: H04W 40/248 Connectivity information update
• CPC Class Codes: H04W 72/53 based on regulatory allocation policies
• CPC Class Codes: H04W 74/004 in the uplink, i.e. towards network
• CPC Class Codes: H04W 76/18 Management of setup rejection or failure
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]
• CPC Class Codes: H04W 80/10 adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 88/02 Terminal devices
• CPC Class Codes: H04W 88/08 Access point devices
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.

Claims

1. A method comprising:

receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count;

determining whether the session request is a stray session request based on the timestamp and the retry count; and

maintaining session information for an existing session for the UE at the node when the session request is a stray session request.

2. The method of claim 1, wherein the session request is an Internet Protocol connectivity access network (IP-CAN) create session request.

3. The method of claim 1, wherein the node is at least one of:

a Policy and Charging Rules Function (PCRF); and

an Authentication, Authorization and Accounting (AAA) element.

4. The method of claim 1, wherein the timestamp is a User Location Information (ULI) timestamp.

5. The method of claim 1, further comprising:

determining if a current session exists for the UE; and

storing the timestamp and retry count received for the UE if a session does not exist for the UE.

6. The method of claim 1, wherein the determining whether the received session request is a stray session request further comprises:

comparing a timestamp stored for the existing session for the UE to the timestamp received in the session request; and

identifying the received session request as a stray request if the timestamp received in the session request is less than the timestamp stored for the existing session for the UE.

7. The method of claim 6, wherein the determining whether the received session request is a stray session request further comprises:

comparing a retry count stored for the existing session for the UE to the retry count received in the session request if the timestamp received in the session request is equal to the timestamp stored for the existing session for the UE; and

identifying the received session request as a stray session request if the retry count received in the session request is less than or equal to the retry count stored for the existing session for the UE.

8. The method of claim 1, further comprising:

appending, by a first Mobility Management Entity (MME), a create session request communicated to a first packet data network gateway (PGW), with the timestamp for the UE and the retry count.

9. The method of claim 8, wherein the first MME increments the retry count each time the first MME re-sends a create session request to another PGW different from the first PGW unless the UE has transitioned to the first MME from another MME.

10. One or more non-transitory tangible media encoding logic that includes instructions for execution that when executed by a processor, is operable to perform operations comprising:

receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count;

determining whether the session request is a stray session request based on the timestamp and the retry count; and

maintaining session information for an existing session for the UE at the node when the session request is a stray session request.

11. The media of claim 10, wherein the session request is an Internet Protocol connectivity access network (IP-CAN) create session request.

12. The media of claim 10, wherein the node is at least one of:

a Policy and Charging Rules Function (PCRF); and

an Authentication, Authorization and Accounting (AAA) element.

13. The media of claim 10, wherein the timestamp is a User Location Information (ULI) timestamp.

14. The media of claim 10, further comprising:

determining if a current session exists for the UE; and

storing the timestamp and retry count received for the UE if a current session does not exist for the UE.

15. The media of claim 10, wherein the determining whether the received session request is a stray session request further comprises:

comparing a timestamp stored for the existing session for the UE to the timestamp received in the session request; and

identifying the received session request as a stray request if the timestamp received in the session request is less than the timestamp stored for the existing session for the UE.

16. The media of claim 15, wherein the determining whether the received session request is a stray session request further comprises:

comparing a retry count stored for the existing session for the UE to the retry count received in the session request if the timestamp received in the session request is equal to the timestamp stored for the existing session for the UE; and

identifying the received session request as a stray session request if the retry count received in the session request is less than or equal to the retry count stored for the existing session for the UE.

17. An apparatus, comprising:

a memory element for storing data; and

a processor to execute instructions associated with the data that, when executed, the apparatus is configured to;

receive a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count;

determine whether the session request is a stray session request based on the timestamp and retry count; and

maintain session information for an existing session for the UE at the node when the session request is a stray session request.

18. The apparatus of claim 17, wherein the timestamp is a User Location Information (ULI) timestamp.

19. The apparatus of claim 17, wherein to determine whether the received session request is a stray session request further comprises the apparatus being configured to:

compare a timestamp stored for the existing session for the UE to the timestamp received in the session request; and

identify the received session request as a stray request if the timestamp received in the session request is less than the timestamp stored for the existing session for the UE.

20. The apparatus of claim 19, wherein to determine whether the received session request is a stray session request further comprises the apparatus being configured to:

compare a retry count stored for the existing session of the UE to the retry count received in the session request if the timestamp received in the session request is equal to the timestamp stored for the existing session of the UE; and

identify the received session request as a stray session request if the retry count received in the session request is less than or equal to the retry count stored for the existing session for the UE.