SYSTEM AND METHOD FOR ENABLING COMMUNICATION SESSIONS IN A NETWORK ENVIRONMENT

• US 20100082557A1
• Filed: 09/19/2008
• Published: 04/01/2010
• Est. Priority Date: 09/19/2008
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Gao, Yifan, Andrieux, Laure F., Besrour, Hymed, Aziz, Zaheer
• Granted Patent: US 8,694,658 B2
• Time in Patent Office: Days
• US Class Current: 707/694
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

A method is provided in one example implementation and the method includes receiving a query for a policy (e.g., a multi-media session) that pertains to a selected one of first and second endpoints. Each endpoint interfaces with their respective session initiation protocol entity, which interacts with a session border controller (SBC). The method further includes negotiating credentials via a policy element and a selected SBC and determining, via a selected policy within the policy element, whether a requested communication session is prohibited or conducted between the endpoints. In more specific embodiments, each SBC makes a mapping between signaling entity information and pre-configured SBC virtual private network (VPN) information used for dynamic configuration of the communication session, and wherein a SIP [or other communication protocol] adjacency configuration is created, where adjacency characteristics are defined for each enterprise in which the endpoints reside.

Claims

1. An apparatus, comprising:

a policy element operable to receive a query for a policy that pertains to a selected one of first and second endpoints, wherein each endpoint interfaces with their respective session border controller (SBC) that communicates with a respective session initiation protocol entity, wherein credential negotiation occurs between the policy element and a selected SBC such that a selected policy within the policy element determines whether a requested communication session is prohibited or conducted between the endpoints.

2. The apparatus of claim 1, wherein the messages contain specific information about the SIP signaling entity and include an IP address for the signaling entity, and characteristics of respective endpoints.

3. The apparatus of claim 1, wherein each SBC makes a mapping between signaling entity information and pre-configured SBC virtual private network (VPN) information used for dynamic configuration of the communication session.

4. The apparatus of claim 1, wherein a SIP adjacency configuration is created, where adjacency characteristics are defined for each enterprise in which the endpoints reside.

5. The apparatus of claim 1, wherein a selected SBC checks in its local database for a log of an existing configuration between two of the endpoints for the communication session requested.

6. The apparatus of claim 5, wherein if an entry exists in the local database, an expired timer will be reset and the communication session will be authorized.

7. The apparatus of claim 1, wherein the selected policy includes a payment plan or a prepayment policy.

8. The apparatus of claim 1, wherein session routing configuration is created and applied in a selected SBC for selected endpoints when the call is authorized via the policy element.

9. The apparatus of claim 1, wherein the selected policy that is accessed provides parameters that include maximum bandwidth, maximum number of sites, or quality of service (QoS) classifications.

10. The apparatus of claim 1, wherein based on a policy result, a selected SBC will elect whether or not to dynamically build and add an input in a session routing table configuration.

11. The apparatus of claim 1, wherein once a configuration is successfully pushed from the policy element, a routing and session table cache entry can be stored on a selected SBC with a timer.

12. The apparatus of claim 1, wherein a selected SBC searches its session routing table to find a route for the communication session, and wherein the selected SBC performs call admission control (CAC) operations such as bandwidth, number of calls, call rate being limited.

13. The apparatus of claim 1, wherein if the communication session is authorized, billing records are generated, or events and alarms are logged.

14. A method, comprising:

receiving a query for a policy that pertains to a selected one of first and second endpoints, wherein each endpoint interfaces with their respective session initiation protocol entity, which interacts with a session border controller (SBC);

negotiating credentials via a policy element and a selected SBC; and

determining via a selected policy within the policy element whether a requested communication session is prohibited or conducted between the endpoints.

15. The method of claim 14, wherein each SBC makes a mapping between signaling entity information and pre-configured SBC virtual private network (VPN) information used for dynamic configuration of the communication session, and wherein a SIP adjacency configuration is created, where adjacency characteristics are defined for each enterprise in which the endpoints reside.

16. The method of claim 14, wherein a selected SBC checks in its local database for a log of an existing configuration between two of the endpoints for the communication session requested, and wherein if an entry exists in the local database, an expired timer will be reset and the communication session will be authorized.

17. Logic encoded in one or more tangible media for execution and when executed by a processor operable to:

receive a query for a policy that pertains to a selected one of first and second endpoints, wherein each endpoint interfaces with their respective session initiation protocol entity, which interacts with a session border controller (SBC);

negotiate credentials via a policy element and a selected SBC; and

determine via a selected policy within the policy element whether a requested communication session is prohibited or conducted between the endpoints.

18. The logic of claim 17, wherein each SBC makes a mapping between signaling entity information and pre-configured SBC virtual private network (VPN) information used for dynamic configuration of the communication session, and wherein a SIP adjacency configuration is created, where adjacency characteristics are defined for each enterprise in which the endpoints reside.

19. The logic of claim 17, wherein a selected SBC checks in its local database for a log of an existing configuration between two of the endpoints for the communication session requested, and wherein if an entry exists in the local database, an expired timer will be reset and the communication session will be authorized.

20. The logic of claim 17, wherein session routing configuration is created and applied in a selected SBC for selected endpoints when the call is authorized via the policy element, and wherein the selected policy that is accessed provides parameters that include maximum bandwidth, maximum number of sites, or quality of service (QoS) classifications, and wherein based on a policy result, a selected SBC will elect whether or not to dynamically build and add an input in a session routing table configuration, and wherein once a configuration is successfully pushed from the policy element, a routing and session (establishment) entry can be stored on a selected SBC with a timer.

21. A system, comprising:

means for receiving a query for a policy that pertains to a selected one of first and second endpoints, wherein each endpoint interfaces with their respective session initiation protocol entity, which interacts with a session border controller (SBC);

means for negotiating credentials via a policy element and a selected SBC; and

means for determining via a selected policy within the policy element whether a requested communication session is prohibited or conducted between the endpoints, wherein each SBC makes a mapping between signaling entity information and pre-configured SBC virtual private network (VPN) information used for dynamic configuration of the communication session, and wherein a SIP adjacency configuration is created, where adjacency characteristics are defined for each enterprise in which the endpoints reside.