System and method for shaping traffic

• US 7,788,386 B2
• Filed: 05/12/2006
• Issued: 08/31/2010
• Est. Priority Date: 11/04/2005
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Svensson, Jan Thomas
• Primary Examiner(s): Avellino; Joseph E
• Assistant Examiner(s): NGUYEN, THAI
• Application Number:
  US11/432,934
• Publication Number:
  US 20070104208A1
• Time in Patent Office: 1,572 Days
• Field of Search: 709/226, 709227-229, 370/230, 370/395, 370/401
• US Class Current: 709/229
• 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 email H04Q2213/13375
• 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 shaping traffic. These mechanisms and methods for shaping traffic can enable embodiments to control traffic flow at a network gatekeeper based upon policies implementing service level agreements dictating traffic characteristics permitted to applications and/or by network node. The ability of embodiments to provide service level agreement based control of network traffic can enable control of traffic flow by application and/or by network node.

Claims

1. A telecommunications system, comprising:

a gateway that controls access to one or more network resources within a mobile device network, the gateway including a policy engine embodied on a tangible machine-readable non-transitory storage medium and executed by one or more processors, said policy engine assigning a priority to each one of a plurality of service requests received from a particular application the service requests being directed to access the network resources, the priority selected by the policy engine based upon a service level agreement (SLA) according to a number of the service requests previously received from said application to access the network resources within a defined time period,

wherein the policy engine assigns a high priority to the service requests while the number of the service requests received from the application within said time period is under a guaranteed threshold level, and

wherein the policy engine assigns a lower priority to the service requests while the number of said service requests received from the application within said time period is between the guaranteed threshold level and a restriction threshold level, and

wherein when the number of the service requests received from the application within said time period exceeds the restriction threshold level, said service requests are automatically rejected;

wherein the gateway is connected to network nodes in the mobile device network through one or more plug-ins that are assigned a node identifier;

a manager that schedules each one of the plurality of service requests between a plurality of sub-queues at a priority level corresponding to the priority assigned to each service request; and

a dispatcher that randomly assigns each one of a plurality of read operations between the plurality of sub-queues, weighted by bandwidth fraction of each priority level, to select a queue from which to de-queue;

wherein the gateway performs network node-level enforcement by determining a node identifier for each plug-in;

comparing current load on the node with restrictions in a global node contract of the gateway and with the node contract in the SLA; and

if the load levels have been exceeded, removing the plug-in associated with the node identifier from a list of available plug-ins for the service request.

2. The telecommunications system of claim 1, wherein the policy engine assigning a priority to each one of a plurality of service requests received from at least one application further includes:

the policy engine assigning the priority to each one of the plurality of service requests received from the application, the priority selected according to a policy implementing the service level agreement (SLA).

3. The telecommunications system of claim 1, wherein the manager that schedules each one of the plurality of service requests between a plurality of sub-queues at a priority level corresponding to the priority assigned to each service request further includes:

the manager rejecting a service request when the corresponding priority sub-queue is determined to be full.

4. The telecommunications system of claim 1, wherein the dispatcher that randomly assigns each one of a plurality of read operations between the plurality of sub-queues, weighted by bandwidth fraction of each priority level, to select a queue from which to de-queue further includes:

the dispatcher attempting to de-queue from a highest priority queue first and then to queues of lesser priority when the selected queue is empty.

5. The telecommunications system of claim 1, further comprising:

a resource element coupled to the dispatcher to provide a mechanism for moving information through the network to one or more end user services.

6. The telecommunications system of claim 5, wherein the resource element coupled to the dispatcher to provide a mechanism for moving information through the network to one or more end user services includes:

a resource element including at least one of;

a Parlay (protocol) gateway, an IMS (IP multi-media subsystem), an SMSCs (short-message-service-center) and an MMSCs (multi-media messaging service center).

13. The telecommunication system of claim 1, further comprising:

a priority task manager that synchronizes current distribution to a network node from the plurality of sub-queues by way of a global counter, such that once a maximum rate for the network node is reached, the dispatcher stops dispatching until the counter has been reset.

14. The telecommunication system of claim 13, wherein node level restrictions are enforced on each network node in a cluster.

15. The telecommunications system of claim 1, wherein traffic counters are employed for one or more of:

global node traffic for a service capability;

application traffic for a service capability; and

application traffic for a service capability and node identifier.

7. A method for shaping traffic in a telecommunications environment, the method comprising:

assigning a priority to each one of a plurality of service requests received from a particular application to a gateway that controls access to one or more network resources within a mobile device network, the priority selected based upon a service level agreement (SLA) according to a number of service requests previously received from said application to access the network resources within a defined time period,

wherein a high priority is assigned to the service requests while the number of the service requests received from the application within said time period is under a guaranteed threshold level, and

wherein a lower priority is assigned to the service requests while the number of said service requests received from the application within said time period is between the guaranteed threshold level and a restriction threshold level, and

wherein when the number of the service requests received from the application within said time period exceeds the restriction threshold level, said service requests are automatically rejected;

wherein the gateway is connected to network nodes in the mobile device network through one or more plug-ins that are assigned a node identifier;

scheduling each one of the plurality of service requests between a plurality of sub-queues and at a priority level corresponding to the priority assigned to each service;

assigning randomly each one of a plurality of read operations between the plurality of sub-queues, weighted by bandwidth fraction of each priority level, to select a queue from which to de-queue; and

performing network node-level enforcement by determining a node identifier for each plug-in in the gateway;

comparing current load on the node with restrictions in a global node contract of the gateway and with the node contract in the SLA; and

if the load levels have been exceeded, removing the plug-in associated with the node identifier from a list of available plug-ins for the service request.

8. The method of claim 7, wherein assigning a priority to each one of a plurality of service requests received from at least one application further includes:

assigning the priority to each one of the plurality of service requests received from the application, the priority selected according to a policy implementing the service level agreement (SLA).

9. The method of claim 7, wherein scheduling each one of the plurality of service requests between a plurality of sub-queues and at a priority level corresponding to the priority assigned to each service includes:

rejecting a service request when the corresponding priority sub-queue is determined to be full.

10. The method of claim 7, wherein assigning randomly each one of a plurality of read operations between the plurality of sub-queues, weighted by bandwidth fraction of each priority level, to select a queue from which to de-queue includes:

attempting to de-queue from a highest priority queue first and then to queues of lesser priority when the selected queue is empty.

11. The method of claim 7, further comprising:

moving information through a network to one or more end user services after dequeue.

12. An apparatus for shaping traffic in a telecommunications system, the apparatus comprising:

a processor; and

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

assigning a priority to each one of a plurality of service requests received from a particular application to a gateway that controls access to one or more network resources within a mobile device network, the priority selected based upon a service level agreement (SLA) according to a number of service requests previously received from said application to access the network resources within a defined time period,

wherein a high priority is assigned to the service requests while the number of the service requests received from the application within said time period is under a guaranteed threshold level, and

wherein a lower priority is assigned to the service requests while the number of said service requests received from the application within said time period is between the guaranteed threshold level and a restriction threshold level, and

wherein when the number of the service requests received from the application within said time period exceeds the restriction threshold level, said service requests are automatically rejected;

wherein the gateway is connected to network nodes in the mobile device network through one or more plug-ins that are assigned a node identifier;

scheduling each one of the plurality of service requests between a plurality of sub-queues and at a priority level corresponding to the priority assigned to each service;

assigning randomly each one of a plurality of read operations between the plurality of sub-queues, weighted by bandwidth fraction of each priority level, to select a queue from which to de-queue; and

performing network node-level enforcement by determining a node identifier for each plug-in in the gateway;

comparing current load on the node with restrictions in a global node contract of the gateway and with the node contract in the SLA; and

if the load levels have been exceeded, removing the plug-in associated with the node identifier from a list of available plug-ins for the service request.