SYSTEM AND METHOD FOR PROVIDING LOCATION AND ACCESS NETWORK INFORMATION SUPPORT IN A NETWORK ENVIRONMENT

• US 20110103266A1
• Filed: 01/10/2011
• Published: 05/05/2011
• Est. Priority Date: 02/15/2008
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Brockners, Frank, Andreasen, Flemming S., Vucetic, Vojislav
• Granted Patent: US 8,711,847 B2
• Time in Patent Office: Days
• US Class Current: 370/259
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 47/20 Traffic policing
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 4/24 Accounting or billing
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

A method is provided in one example embodiment and includes communicating location and access network information for an end user to a policy and charging rules function (PCRF) element that is coupled to a network element. The network element receives packets for a communications flow from the end user if the flow is initiated through a wireless network and through a wireline network. In more specific embodiments, the location and access network information is used to initiate one or more applications for the end user. The method could also include communicating to an application function that the end user has attached to one of the networks, has been assigned an Internet Protocol (IP) address, and the location and access network information for the end user.

Claims

1-24. -24. (canceled)

25. A method, comprising:

communicating location and access network information for an end user associated with a session in a network environment; and

receiving packets at a network element for a communications flow for the end user, wherein the flow can be initiated through a wireless network and through a wireline network, and wherein a network address translation (NAT) is performed for at least a portion of the packets associated with the wireless network.

26. The method of claim 25, wherein the network element is configured to participate in a session initiation protocol (SIP) registration that uses an Internet Protocol (IP) address of the end user.

27. The method of claim 25, further comprising:

allocating resources associated with unicast and multicast sessions associated with the end user.

28. The method of claim 25, wherein the network element is configured to participate in a resource reservation push activity in which a connection admission control (CAC) request is originated from a service layer during a SIP session establishment.

29. The method of claim 25, wherein the network element is configured to participate in a resource reservation pull activity in which a CAC request is originated from a transport layer.

30. The method of claim 25, wherein the location information is configured for use in an emergency call associated with the end user.

31. The method of claim 25, wherein the location information is inserted into a SIP header, and wherein the location information is leveraged in order to skip an authentication activity associated with a SIP protocol.

32. An apparatus, comprising:

a network element that includes a processor and a memory element, the network element being configured for;

communicating location and access network information for an end user associated with a session in a network environment; and

receiving packets at a network element for a communications flow for the end user, wherein the flow can be initiated through a wireless network and through a wireline network, and wherein a network address translation (NAT) is performed for at least a portion of the packets associated with the wireless network.

33. The apparatus of claim 32, wherein the network element is configured to participate in a session initiation protocol (SIP) registration that uses an Internet Protocol (IP) address of the end user.

34. The apparatus of claim 32, wherein the network element is further configured for:

allocating resources associated with unicast and multicast sessions involving the end user.

35. The apparatus of claim 32, wherein the network element is configured to participate in a resource reservation push activity in which a connection admission control (CAC) request is originated from a service layer during a SIP session establishment.

36. The apparatus of claim 32, wherein the network element is configured to participate in a resource reservation pull activity in which a CAC request is originated from a transport layer.

37. The apparatus of claim 32, wherein the location information is inserted into a SIP header, and wherein the location information is leveraged in order to skip an authentication activity associated with a SIP protocol.

38. Logic encoded in non-transitory media that includes code for execution and when executed by a processor operable to perform operations comprising:

communicating location and access network information for an end user associated with a session in a network environment; and

receiving packets at a network element for a communications flow for the end user, wherein the flow can be initiated through a wireless network and through a wireline network, and wherein a network address translation (NAT) is performed for at least a portion of the packets associated with the wireless network.

39. The logic of claim 38, the operations further comprising:

facilitating a session initiation protocol (SIP) registration that uses an Internet Protocol (IP) address of the end user.

40. The logic of claim 38, the operations further comprising:

allocating resources associated with unicast and multicast sessions involving the end user.

41. The logic of claim 38, the operations further comprising:

facilitating a resource reservation push activity in which a connection admission control (CAC) request is originated from a service layer during a SIP session establishment.

42. The logic of claim 38, the operations further comprising:

facilitating a resource reservation pull activity in which a CAC request is originated from a transport layer.

43. The logic of claim 38, wherein the location information is configured for use in an emergency call associated with the end user.

44. The logic of claim 38, wherein the location information is inserted into a SIP header, and wherein the location information is leveraged in order to skip an authentication activity associated with a SIP protocol.