System and method for offloading data in a communication system

• US 9,030,991 B2
• Filed: 07/10/2011
• Issued: 05/12/2015
• Est. Priority Date: 10/05/2010
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Andreasen, Flemming S., Leung, Kent K., Khouderchah, Michel, Iyer, Jayaraman R., Stammers, Timothy P.
• Primary Examiner(s): Algahaim, Helal A
• Assistant Examiner(s): ISMAIL, MAHMOUD S
• Application Number:
  US13/179,540
• Publication Number:
  US 20120082094A1
• Time in Patent Office: 1,402 Days
• Field of Search: 370/329, 370/338, 370/237, 370/218, 370/328, 375/257, 455/557, 455/574
• US Class Current: 370/328
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/243 using M+N parallel active paths
• CPC Class Codes: H04L 45/26 Route discovery packet
• CPC Class Codes: H04L 61/2514 between local and global IP addresses
• CPC Class Codes: H04W 28/0226 based on location or mobility handoff or reselection H04W36/00; mobile application services making use of the location of users or terminals H04W4/02
• CPC Class Codes: H04W 40/24 Connectivity information management, e.g. connectivity discovery or connectivity update
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information

Abstract

A method is provided in one example embodiment and includes receiving a downstream data packet transported on a backhaul link at a first network element, the downstream data packet is associated with a user equipment; identifying whether a downstream tunnel used to communicate the data packet to the user equipment has become dormant; and communicating an in-band message to a second network element that the downstream tunnel is dormant. In other examples, the method can include dropping the data packet when a network address port translation binding has expired or does not exist. In certain implementations, the method can include identifying the downstream tunnel as dormant when an activity timer has expired, or identifying the downstream tunnel as dormant based on a stale state setting.

Claims

1. A method implemented by a network element, the method comprising:

receiving a downstream data packet transported on a backhaul link at the network element;

identifying whether a downstream tunnel from the network element has become dormant;

buffering the downstream data packet in response to identifying that the downstream tunnel is dormant;

communicating a message using a generic routing encapsulation tunnel in response to an identification that the downstream tunnel is dormant, the identification at least in part based on an expiration of an inactivity timer, a setting of a stale state, or a reception of an error message;

receiving, as a response to the message, a tunnel identification binding that identifies a second tunnel; and

communicating the downstream data packet from the network element using the second tunnel.

2. The method of claim 1, further comprising:

dropping the downstream data packet when a network address port translation binding has expired or does not exist.

3. The method of claim 1, further comprising:

identifying the downstream tunnel as dormant when the inactivity timer has expired.

4. The method of claim 1, further comprising:

identifying the downstream tunnel as dormant based on the stale state setting.

5. The method of claim 1, wherein the communicating the downstream data packet communicates the downstream data packet to user equipment.

6. The method of claim 1, further comprising:

identifying that an upstream tunnel to communicate a data packet from user equipment is dormant; and

receiving an in-band message at the network element that the upstream tunnel is dormant.

7. Logic, encoded in one or more non-transitory media, that includes code for execution and, when executed by a processor, is operable to perform operations comprising:

receiving a downstream data packet transported on a backhaul link at a network element;

identifying whether a downstream tunnel from the network element has become dormant;

buffering the downstream data packet in response to identifying that the downstream tunnel is dormant;

communicating a message using a generic routing encapsulation tunnel in response to an identification that the downstream tunnel is dormant, the identification at least in part based on an expiration of an inactivity timer, a setting of a stale state, or a reception of an error message;

receiving, as a response to the message, a tunnel identification binding that identifies a second tunnel; and

communicating the downstream data packet from the network element using the second tunnel.

8. The logic of claim 7, the operations further comprising:

dropping the downstream data packet when a network address port translation binding has expired or does not exist.

9. The logic of claim 7, the operations further comprising:

identifying the downstream tunnel as dormant when the inactivity timer has expired.

10. The logic of claim 7, the operations further comprising:

identifying the downstream tunnel as dormant based on the stale state setting.

11. The logic of claim 7, wherein the communicating the downstream data packet communicates the downstream data packet to user equipment.

12. The logic of claim 7, the operations further comprising:

identifying that an upstream tunnel used to communicate a data packet from user equipment is dormant; and

receiving an in-band message at the network element that the upstream tunnel is dormant.

13. An apparatus, comprising:

a memory element configured to store data;

a processor operable to execute instructions associated with the data; and

a traffic offload module configured to interface with the memory element and the processor, wherein

the apparatus is configured to

receive a downstream data packet transported on a backhaul link;

identify whether a downstream tunnel from the apparatus has become dormant;

buffer the downstream data packet in response to identifying that the downstream tunnel is dormant;

communicate a message using a generic routing encapsulation tunnel in response to an identification that the downstream tunnel is dormant, the identification at least in part based on an expiration of an inactivity timer, a setting of a stale state, or a reception of an error message;

receive, as a response to the message, a tunnel identification binding that identifies a second tunnel; and

communicate the downstream data packet from the apparatus using the second tunnel.

14. The apparatus of claim 13, the apparatus further configured to drop the downstream data packet when a network address port translation binding has expired or does not exist.

15. The apparatus of claim 13, the apparatus further configured to identify the downstream tunnel as dormant when the inactivity timer has expired.

16. The apparatus of claim 13, the apparatus further configured to identify the downstream tunnel as dormant based on the stale state setting.

17. The apparatus of claim 13, wherein the apparatus is further configured to communicate the downstream data packet to user equipment using the second tunnel.