System and method for controlling data flow based upon a temporal policy

• US 7,953,877 B2
• Filed: 05/15/2006
• Issued: 05/31/2011
• Est. Priority Date: 11/04/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Forsberg, Anders Lars-Goran, Svensson, Jan Thomas, Vemula, Narendra
• Primary Examiner(s): Moore; Ian N
• Assistant Examiner(s): NGUYEN, THAI
• Application Number:
  US11/434,022
• Publication Number:
  US 20070106808A1
• Time in Patent Office: 1,842 Days
• Field of Search: 709/220, 709/230, 709/310, 709223-226, 370/230.1, 370/352, 455/466
• US Class Current: 709/230
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 12/189 in combination with wireless systems selective distribution or broadcast in wireless communication networks H04W4/06
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 Policy-based network configuration management
• CPC Class Codes: H04L 41/5022 by giving priorities, e.g. assigning classes of service
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/22 Traffic shaping
• CPC Class Codes: H04L 47/2425 for supporting services specification, e.g. SLA
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 47/30 in combination with information about buffer occupancy at either end or at transit nodes
• CPC Class Codes: H04L 47/50 Queue scheduling
• CPC Class Codes: H04L 47/522 Dynamic queue service slot or variable bandwidth allocation
• CPC Class Codes: H04L 47/6215 Individual queue per QOS, rate or priority
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/745 Reaction in network
• CPC Class Codes: H04L 47/781 Centralised allocation of resources
• CPC Class Codes: H04L 47/805 QOS or priority aware
• CPC Class Codes: H04L 47/821 Prioritising resource allocation or reservation requests
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04Q 2213/13098 : Mobile subscriber
• CPC Class Codes: H04Q 2213/1313 : Metering, billing
• CPC Class Codes: H04Q 2213/13176 : Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13196 : Connection circuit/link/trunk/junction, bridge, router, gateway
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/13336 : Store & forward, messaging systems
• CPC Class Codes: H04Q 2213/13348 : Channel/line reservation
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements

Abstract

In accordance with embodiments, there are provided mechanisms and methods for controlling data flow based on a temporal policy. These mechanisms and methods for controlling data flow based on a temporal policy can enable embodiments to provide a different service level agreement to control network traffic selected from a plurality of service level agreements based upon one or more temporal conditions. The ability of embodiments to provide different service level agreement to control network traffic can enable embodiments to control one or more of access to network resources and traffic flow coordination to enhance efficient usage of the network resources.

Claims

1. A telecommunications system comprising:

one or more processors and a non-transitory storage medium containing instructions, which when executed by the one or more processors, cause the one or more processors to implement;

a service capability module, residing on the non-transitory storage medium, that receives a request from an application that resides in an untrusted domain, said request being directed to a subscriber device in a telecommunications network;

a plug-in manager that retrieves one or more plug-ins to handle the request, wherein each of the one or more plug-ins represents a particular network device in the telecommunications network, device including at least one of the following;

a short messaging service center (SMS-C), a multimedia messaging service center (MMS-C), and a parlay gateway of the telecommunications network;

a first Policy Enforcement Point (PEP) residing on the service capability module to enforce service capabilities, wherein the first PEP determines whether to grant to deny the request according to a service being invoked by the request and according to at least one temporal condition;

a second PEP residing on the plug-in manager to enforce network protection by coordinating traffic among the network devices to enhance network traffic efficiency, wherein the second PEP routes the request to a selected network device;

a policy engine containing a set of policy rules loaded into memory of said policy engine, wherein the policy rules can be added and updated at runtime;

a Policy Decision Point (PDP) residing on the policy engine, wherein said PDP makes a policy decision by employing the set of policy rules;

wherein upon receiving the request from the application, the first PEP forwards data in the request to the PDP in the policy engine that evaluates the request, modifies or adds new data to the request, and informs the first PEP of the policy decision, wherein the first PEP then enforces said policy decision on the request and queries the plug-in manager for a list of possible plug-ins to handle the request; and

wherein upon receiving the request from the first PEP, the plug-in manager retrieves the list of possible plug-ins based on an address plan and destination address of the request and sends the list of possible plug-ins to the policy engine,

wherein the policy engine makes a decision based on one or more of;

request data, general network gatekeeping rules, specific data in the service provider traffic service level agreement (SLA) or additional data from external databases,

wherein the policy engine returns the list of possible plug-ins that have passed the decision to the plug-in manager or informs the plug-in manager that no plug-in has passed the decision, wherein the plug-in manager selects a plug-in from the list of possible plug-ins and sends the plug-in to the service capability module, and

wherein the service capability module routes the request to said plug-in.

2. The telecommunications system of claim 1, wherein the policy engine selects from a plurality of different service level agreements, a service level agreement to control network traffic based upon said at least one temporal condition to control at least one of access to network resources and traffic flow coordination based upon the selected service level agreement.

3. The telecommunications system of claim 1, wherein the plug-in includes at least one of an SMPP protocol adapter, a PDP protocol adapter, and MM7 protocol adapter.

4. The telecommunications system of claim 1, wherein the Policy Decision Point (PDP) selects from a plurality of different service level agreements, the service level agreement to control network traffic based upon said at least one temporal condition selected from a time of day and a day of the week to control at least one of access to network resources and traffic flow coordination based upon the selected service level agreement.

5. A method for controlling data flow based on a temporal policy in a telecommunications environment, the method comprising:

receiving at least one of a plurality of service requests from at least one application that resides in an untrusted domain to a service capability module on a computing device, said request being directed to a subscriber device in a telecommunications network;

providing a plug-in manager that retrieves one or more plug-ins to handle the service requests, wherein the one or more plug-ins establish a connection with network devices over a particular communications protocol, the network devices including at least one of the following;

a short messaging service center (SMS-C), a multimedia messaging service center (MMS-C) and a parlay gateway of a telecommunications network;

providing a first Policy Enforcement Point (PEP) residing on the service capability module to enforce service capabilities, wherein the first PEP determines whether to grant to deny the request according to a service being invoked by the request and according to at least one temporal condition;

providing a second PEP residing on the plug-in manager to enforce network protection by coordinating traffic among the network devices to enhance network traffic efficiency, wherein the second PEP routes the request to a selected network device;

providing a policy engine containing a set of policy rules loaded into memory of said policy engine, wherein the policy rules can be added and updated at runtime; and

employing the policy rules by a policy decision point residing on the policy engine in order to control traffic flow based upon at least one temporal condition;

wherein upon receiving the request from the application, the first PEP forwards data in the request to the PDP in the policy engine that evaluates the request, modifies or adds new data to the request, and informs the first PEP of the policy decision, wherein the first PEP then enforces said policy decision on the request and queries the plug-in manager for a list of possible plug-ins to handle the request; and

wherein upon receiving the request from the first PEP, the plug-in manager retrieves the list of possible plug-ins based on an address plan and destination address of the request and sends the list of possible plug-ins to the policy engine,

wherein the policy engine makes a decision based on one or more of request data, general network gatekeeping rules, specific data in the service provider traffic service level agreement (SLA) or additional data from external databases,

wherein the policy engine returns the list of possible plug-ins that have passed the decision to the plug-in manager or informs the plug-in manager that no plug-in has passed the decision, wherein the plug-in manager selects a plug-in from the list of possible plug-ins and sends the plug-in to the service capability module, and

wherein the service capability module routes the request to said plug-in.

6. The method of claim 5, wherein making a policy decision further includes:

selecting from a plurality of different service level agreements, a service level agreement to control network traffic based upon said at least one temporal condition selected from a time of day and a day of the week to control at least one of access to network resources and traffic flow coordination based upon the selected service level agreement.

7. The method of claim 5, wherein the plug-in includes one or more of:

an SMPP protocol adapter, a PDP protocol adapter, and MM7 protocol adapter and an IMAP protocol adapter.

8. A non-transitory computer-readable storage medium storing one or more sequences of instructions for controlling data flow based on a temporal policy in a telecommunications environment, wherein execution of said instructions causes one or more processors to carry out the steps of:

receiving at least one of a plurality of service requests from at least one application that resides in an untrusted domain to a service capability module residing on the non-transitory computer-readable storage medium, said request being directed to a subscriber device in a telecommunications network;

providing a plug-in manager that retrieves one or more plug-ins to handle the service requests, wherein the one or more plug-ins establish a connection with network devices over a particular communications protocol, the network devices including at least one of the following;

a short messaging service center (SMS-C), a multimedia messaging service center (MMS-C) and a parlay gateway of a telecommunications network;

providing a first Policy Enforcement Point (PEP) residing on the service capability module to enforce service capabilities, wherein the first PEP determines whether to grant to deny the request according to a service being invoked by the request and according to at least one temporal condition;

providing a second PEP residing on the plug-in manager to enforce network protection by coordinating traffic among the network devices to enhance network traffic efficiency, wherein the second PEP routes the request to a selected network device;

providing a policy engine containing a set of policy rules loaded into memory of said policy engine, wherein the policy rules can be added and updated at runtime; and

employing the policy rules by a policy decision point residing on the policy engine in order to control traffic flow based upon at least one temporal condition;

wherein upon receiving the request from the application, the first PEP forwards data in the request to the PDP in the policy engine that evaluates the request, modifies or adds new data to the request, and informs the first PEP of the policy decision,

wherein the first PEP then enforces said policy decision on the request and queries the plug-in manager for a list of possible plug-ins to handle the request; and

wherein upon receiving the request from the first PEP, the plug-in manager retrieves the list of possible plug-ins based on an address plan and destination address of the request and sends the list of possible plug-ins to the policy engine,

wherein the policy engine makes a decision based on one or more of request data, general network gatekeeping rules, specific data in the service provider traffic service level agreement (SLA) or additional data from external databases,

wherein the policy engine returns the list of possible plug-ins that have passed the decision to the plug-in manager or informs the plug-in manager that no plug-in has passed the decision, wherein the plug-in manager selects a plug-in from the list of possible plug-ins and sends the plug-in to the service capability module, and

wherein the service capability module routes the request to said plug-in.