Abstract: A service level agreement may be imposed by a service provider, such as an Internet service provider, that may include, e.g., a volume limitation and a bandwidth limitation. One or more limitations of the service level agreement may be enforced or modified in response to a triggering event. For example, a bandwidth limitation on a network subscriber may be enforced or modified based on how much data is consumed by the subscriber.

Abstract: IP packets are scheduled at source devices such as cell phones on a private network that connect to the Internet at an edge device. A private traffic controller by the edge device detects pre-Internet congestion on the private network. The private traffic controller uses in-band piggybacked signaling of policy changes by intercepting return packets to the source devices and modifying bits such as DSCP bits in the header. Source traffic controllers in the source devices read the modified DSCP bits and implement specified policy changes, dropping or delaying packets at the source device before transmission. Congestion on RF links from cell phones is reduced by the source traffic controllers dropping packets before transmission. The source device limits or drops future packets in response to the policies signaled by the DSCP bits. Rather than indicate the existing packet's priority, private DSCP bits signal policy changes to the source device.

Abstract: A service level agreement may be imposed by a service provider, such as an Internet service provider, that may include, e.g., a volume limitation and a bandwidth limitation. One or more limitations of the service level agreement may be enforced or modified in response to a triggering event. For example, a bandwidth limitation on a network subscriber may be enforced or modified based on how much data is consumed by the subscriber.

Abstract: Low-level network services are provided by network-service-provider plugins. These plugins are controlled by an extensible service provider that is layered above the TCP layer but below the Winsock-2 library and API. The extensible service provider orders the plugins based on the function performed by each plugin and on ordering hints. Plugins that redirect the protocol or socket are executed first. Plugins that examine packets or block entire packets are executed before plugins that modify packets. Plugins that compress or encrypt data are executed last for outgoing packets. Ordering hints cause a plugin to be executed before or after others in its functional class. Ordering allows examining plugins that simply read data get to the packets before an encrypting or compressing plugin renders the data unreadable. The extensible service provider has a plugin manager that orders and controls execution of the plugins. A filter manager evaluates one or more packet-filters.

Abstract: Low-level network services are provided by network-service-provider plugins. These plugins are controlled by an extensible service provider that is layered above the TCP or other protocol layer but below the Winsock-2 library and API. Policy servers determine priority of network traffic through control points on a network. Examining packets passing through these control points provides limited data such as the source and destination IP address and TCP ports. Many applications on a client machine may use the same IP address and TCP ports, so packet examination is ineffective for prioritizing data from different applications on one client machine. Often some applications such as videoconferencing or data-entry for corporate sales are more important than other applications such as web browsing. A application-classifier plugin to the extensible service provider intercepts network traffic at above the client's TCP/IP stack and associates applications and users with network packets.