A bandwidth allocation device includes a buffer device, a main scheduler, an oversubscription scheduler, a multiplexer and a detecting device. The buffer device is arranged to receive first data units from first ports and second data units from second ports and accordingly output these data units. The main scheduler is configured to schedule the first data units and accordingly output the first data units in sequence. The oversubscription scheduler is configured to schedule the second data units and accordingly output the second data units in sequence. The multiplexer is controlled by the main scheduler to select the first data units outputted by the main scheduler and the second data units outputted by the oversubscription scheduler for outputting. The detecting device is arranged to generate power-related information which the main scheduler relies on to control the multiplexer.

A method for analyzing traffic in a communications network includes sampling data packets at a plurality of network interconnection points, wherein sampling the data packets includes generating a plurality of sampled packet data in one or more standardized formats, converting the sampled packet data from the one or more standardized formats into a neutral format, and aggregating the sampled packet data in the neutral format from the plurality of network interconnection points. A system includes a communications node operable to sample data packets flowing through and generate sample packet data in a specified format, a collector node operable to convert the sampled packet data into a neutral format, the collector node further operable to map IP addresses of the sampled packet data to corresponding prefixes in a routing table; and an aggregator node operable to aggregate neutrally formatted sampled packet data from a plurality of collector nodes.

Implementations are provided herein for organizing present and future reads from a tiered streaming data storage layer. Implementations allow for access to multi-tiered streaming data organized in different append-only segments, some of which may be related to each other. Streaming data can be read from fast local tier 1 storage, streaming data can be retrieved from fold tier 2 storage, and registrations can be made to read streaming data that has not yet been written to the storage layer.

Implementations are provided herein for atomically committing related stream data across multiple, distributed resources. Transactions can be established that are distributed across multiple hosts, and their data can be made to appear atomic to an observing process. A master status for the transaction can be used to flag to other processes that the transaction is being committed. A stream to which the transaction is being appended to can be locked until the transaction data is committed in full. It can be appreciated that one an event to a transaction is acknowledged, and the transaction is merged, its commitment is guaranteed.

In one embodiment, an apparatus includes: a transmitter to send first data to a device coupled to the apparatus via a physical link; a receiver to receive second data from the device via the physical link; and a control circuit to control the transmitter to send the first data at a first effective rate during a link activation interval of a data transfer interval and to control the receiver to receive the second data at a second effective rate during the link activation interval, the second effective rate different than the first effective rate. Other embodiments are described and claimed.

Embodiments enable clients to have read-write access to a stream where all other clients are aware of all changes being made to the stream. A pravega node can track the data that has been written to the stream. The clients can dynamically read the stream. A client among the clients can update the stream by sending a request to the pravega node that includes the update and a total length of the stream that was written to the stream at the time of the last read update by the client. If the total length of the stream received from the client matches the actual length of the stream maintained by the pravega node, the pravega node will update the stream. If not, a failure message can be sent to the client and the client can process more reads to the stream before making another attempt to update the stream.

Implementations are provided herein for managing streaming data that appended and multiplexed into a durable write ahead replicated log. By writing data in the durable log, large amounts of small writes can be processed quickly. Data in the durable log can be de-multiplexed and packaged into segment containers. Segment containers can serialize stream segment specific data and can be stored in long term storage. Data that has been stored in long term storage can be truncated from the durable write ahead log making room for new data.

A system and method for handling a digital electronic flow between a first and second entity in which a flow policy is determined that is to be applied to the flow and the flow is then directed along a path in accordance with the policy. An ID is supplied for each flow and a tag associated with each flow which indicates the policy to be applied to its associated flow. Flows are also associated with one another, with associated flows having associated policies. In particular the flow may be processed or forwarded. The path may include a graph structure and virtual applications.

A system for packet-based scheduling for Transmission Control Protocol (TCP) sessions or User Datagram Protocol (UDP) sessions includes: a first bonding module comprising a first scheduling module and at least two access interfaces connected to at least one transport network, wherein the first bonding module is configured to be connected to a user device, wherein a TCP tunnel is configured via each of the access interfaces which terminates at a second bonding module, and wherein the first scheduling module is configured to schedule and distribute data packets via the TCP tunnels towards the second bonding module. The second bonding module comprises a second scheduling module and at least one access interface connected to each of the at least one transport network, wherein the second bonding module is configured to be connected to a server and to schedule and distribute data packets via the TCP tunnels towards the first bonding module.

Implementations are provided herein for managing streaming data that appended and multiplexed into a durable write ahead replicated log. By writing data in the durable log, large amounts of small writes can be processed quickly. Data in the durable log can be de-multiplexed and packaged into segment containers. Segment containers can serialize stream segment specific data and can be stored in long term storage. Data that has been stored in long term storage can be truncated from the durable write ahead log making room for new data.