Abstract: A boost is provided in an overloaded system by distinguishing nodes with a “bad” traffic history from nodes with a “good” traffic history. In so doing, a core network node is able to apply additional resources to the node(s) having a “good” history in the form of a boost factor. Based on a system capacity and a working point, e.g., a critical number of active nodes with a “bad” traffic history, the core network node may determine a throughput history limit belonging to the “bad” traffic history. Responsive to expected requirements for a newly active node (i.e., a node having a “good” traffic history), the core network node determines a boost factor for the newly active node, applies the boost factor to the average resources allocated to the nodes with the “bad” traffic history to determine boosted resources, and allocates the boosted resources to the newly active node.

Abstract: To support quality of service fairness in a communication network, a network node determines a maximum bucket size, for a token bucket controlling a transmission rate from the network node over a transport line between a radio access network and a core network, based on a drop precedence and a given timescale.

Abstract: Regulating transmission of data packets between a first network and a second network over a datalink. Embodiments include determining a first plurality of token bucket rate (TBR) parameters, each TBR parameter corresponding to a one of a first plurality of packet drop precedence (DP) levels and one of a first plurality of timescales (TS). The determination of the first plurality of bucket rate parameters is based on a peak rate requirement, the data link capacity, and a nominal speed requirement associated with the data link. Embodiments also include determining a second plurality of TBR parameters based on the first plurality of TBR parameters and a guaranteed rate requirement, the second plurality comprising a further DP level than the first plurality. Embodiments also include regulating data packets sent between the first network and the second network via the data link based on the second plurality of TBR parameters.

Abstract: To support quality of service fairness in a communication network, a network node determines a maximum bucket size, for a token bucket controlling a transmission rate from the network node over a transport line between a radio access network and a core network, based on a drop precedence and a given timescale.

Abstract: Regulating transmission of data packets between a first network and a second network over a datalink. Embodiments include determining a first plurality of token bucket rate (TBR) parameters, each TBR parameter corresponding to a one of a first plurality of packet drop precedence (DP) levels and one of a first plurality of timescales (TS). The determination of the first plurality of bucket rate parameters is based on a peak rate requirement, the data link capacity, and a nominal speed requirement associated with the data link. Embodiments also include determining a second plurality of TBR parameters based on the first plurality of TBR parameters and a guaranteed rate requirement, the second plurality comprising a further DP level than the first plurality. Embodiments also include regulating data packets sent between the first network and the second network via the data link based on the second plurality of TBR parameters.

Abstract: The invention concerns an efficient strategy for sharing link bandwidth in a mixed rigid-elastic traffic environment, as well as a strategy for sharing bandwidth among elastic traffic flows. The idea according to the invention is to sharing the link bandwidth among rigid and elastic traffic by dividing the link bandwidth into a first common part CCOM for elastic as well as rigid traffic and a second part CELA dedicated for elastic traffic. Subsequently, one or more admission control parameters for the elastic traffic are determined in order to restrict the number of elastic traffic flows simultaneously present on the link. In particular, by formulating a call-level model for elastic traffic and determining a maximum number NELA of admissible elastic traffic flows based on call-level constraints for the elastic traffic related to throughput and/or blocking, the so-called throughput-to-blocking trade-off for elastic traffic can be fully considered.