Conveying subscriber information to service chain services using tunnel protocol header encapsulation for mobile network applications in a network environment

Patent metadata

Field	Value
Publication number	US-9398486-B2
Application number	US-201414300865-A
Country	US
Kind code	B2
Filing date	Jun 10, 2014
Priority date	Jun 10, 2014
Publication date	Jul 19, 2016
Grant date	Jul 19, 2016

Abstract

A method provided in one embodiment includes receiving, at a first network element, a first data packet of a data flow, wherein the data flow is associated with a subscriber. The method further includes receiving subscriber information associated with the subscriber, and encapsulating the subscriber information with the first data packet to form an encapsulated data packet. The method still further includes determining a service chain including one or more services to which the encapsulated data packet is to be forwarded, and forwarding the encapsulated data packet to the service chain.

First claim

What is claimed is:

1. A method, comprising:
receiving, at a first network element, a first data packet of a data flow, wherein the data flow is associated with a subscriber;
receiving subscriber information associated with the subscriber;
encapsulating the subscriber information with the first data packet to form an encapsulated data packet;
determining a service chain including one or more services to which the encapsulated data packet is to be forwarded;
forwarding the encapsulated data packet to the service chain; and
receiving a second data packet from the service chain, the second data packet including an indication of one or more actions that are requested to be performed in association with the data flow.

2. The method of claim 1 , wherein the subscriber information includes policy information associated with the subscriber.

3. The method of claim 1 , wherein encapsulating the subscriber information further comprises including the subscriber information within a network service header.

4. The method of claim 3 , wherein the subscriber information is included within a context header of the network service header.

5. The method of claim 1 , further comprising routing the indication of the requested action to a network entity configured to perform the requested action upon the data flow.

6. The method of claim 1 , further comprising determining a subscriber identifier associated with the subscriber included in the first data packet.

7. The method of claim 6 , further comprising sending a request message including the subscriber identifier to a second network element, the request message including a request for the subscriber information associated with the subscriber.

8. The method of claim 1 , wherein the one or more services of the service chain are configured to extract the subscriber information and the first data packet from the encapsulated data packet and perform one or more operations upon the first data packet based upon the subscriber information.

9. Logic encoded in one or more non-transitory media that includes code for execution and when executed by a processor operable to perform operations comprising:
receiving, at a first network element, a first data packet of a data flow, wherein the data flow is associated with a subscriber;
receiving subscriber information associated with the subscriber;
encapsulating the subscriber information with the first data packet to form an encapsulated data packet;
determining a service chain including one or more services to which the encapsulated data packet is to be forwarded;
forwarding the encapsulated data packet to the service chain; and
receiving a second data packet from the service chain, the second data packet including an indication of one or more actions that are requested to be performed in association with the data flow.

10. The logic of claim 9 , wherein the subscriber information includes policy information associated with the subscriber.

11. The logic of claim 9 , wherein encapsulating the subscriber information further comprises including the subscriber information within a network service header.

12. The logic of claim 11 , wherein the subscriber information is included within a context header of the network service header.

13. The logic of claim 9 , wherein the operations further comprise routing the indication of the requested action to a network entity configured to perform the requested action upon the data flow.

14. The logic of claim 9 , wherein the operations further comprise determining a subscriber identifier associated with the subscriber included in the first data packet.

15. The logic of claim 14 , wherein the operations further comprise sending a request message including the subscriber identifier to a second network element, the request message including a request for the subscriber information associated with the subscriber.

16. The logic of claim 9 , wherein the one or more services of the service chain are configured to extract the subscriber information and the first data packet from the encapsulated data packet and perform one or more operations upon the first data packet based upon the subscriber information.

17. A network element, comprising:
a memory element configured to store electronic code;
a processor operable to execute instructions associated with the electronic code; and
a module coupled to the memory element and the processor, wherein the network element is configured for:
receiving a first data packet of a data flow, wherein the data flow is associated with a subscriber;
receiving subscriber information associated with the subscriber;
encapsulating the subscriber information with the first data packet to form an encapsulated data packet;
determining a service chain including one or more services to which the encapsulated data packet is to be forwarded;
forwarding the encapsulated data packet to the service chain; and
receiving a second data packet from the service chain, the second data packet including an indication of one or more actions that are requested to be performed in association with the data flow.

18. The network element of claim 17 , wherein the subscriber information includes policy information associated with the subscriber.

19. The network element of claim 17 , wherein encapsulating the subscriber information further comprises including the subscriber information within a network service header.

20. The network element of claim 19 , wherein the subscriber information is included within a context header of the network service header.

21. The network element of claim 17 , wherein the network element is further configured for routing the indication of the requested action to a network entity configured to perform the requested action upon the data flow.

22. The network element of claim 17 , wherein the one or more services of the service chain are configured to extract the subscriber information and the first data packet from the encapsulated data packet and perform one or more operations upon the first data packet based upon the subscriber information.

Assignees

• Cisco Tech Inc

Inventors

• La Roche Jr Humberto J
• Bosch Hendrikus G P
• Guichard James N
• Quinn Paul
• Kumar Surendra M
• Shatzkamer Kevin D

Classifications

• H04L45/306

  Route determination based on the nature of the carried application · CPC title

• H04L12/4633 Primary

  Interconnection of networks using encapsulation techniques, e.g. tunneling · CPC title

• H04L45/38

  Flow based routing · CPC title

• H04W28/0215 Primary

  based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51) · CPC title