Methods, apparatus and software for implementing enhanced data center congestion management for non-TCP traffic. Non-congested transmit latencies are determined for transmission of packets or Ethernet frames along paths between source and destination end-end-nodes when congestion along the paths is not present or minimal. Transmit latencies are similarly measured along the same source-destination paths during ongoing operations during which traffic congestion may vary. Based on whether a difference between the transmit latency for a packet or frame and the non-congested transmit latency for the path exceeds a threshold, the path is marked as congested or not congested. A rate at which the non-TCP packets are transmitted along the path is then managed as function of a rate at which the path is marked as congested. In one implementation, non-TCP traffic is managed by mimicking a Data Center TCP technique, under which the congestion marking status of the path is substituted as an input to a DCTP algorithm in place of the normally-used ECN-Echo flag input. The congestion window output by the DCTCP algorithm is then used to manage the rate at which non-TCP packets to be forwarded via the path are transmitted from a source end-node.

Device Assisted Services (DAS) for protecting network capacity is provided. In some embodiments, DAS for protecting network capacity includes monitoring a network service usage activity of the communications device in network communication; classifying the network service usage activity for differential network access control for protecting network capacity; and associating the network service usage activity with a network service usage control policy based on a classification of the network service usage activity to facilitate differential network access control for protecting network capacity.

Various methods and systems for implementing request scheduling and processing in a multi-tenant distributed computing environment are provided. Requests to utilize system resources in the distributed computing environment are stored in account queues corresponding to tenant accounts. If storing a request in an account queue would exceed a throttling threshold such as a limit on the number of requests stored per account, the request is dropped to a throttling queue. A scheduler prioritizes processing requests stored in the processing queue before processing requests stored in the account queues. The account queues can be drained using dominant resource scheduling. In some embodiments, a request is not picked up from an account queue if processing the request would exceed a predefined hard limit on system resource utilization for the corresponding tenant account. In some embodiments, the hard limit is defined as a percentage of threads the system has to process requests.

A system for provisioning an elastic computing infrastructure is provided. The system includes a memory and at least one processor coupled to the memory. The system also includes a management component executed by the at least one processor and configured to instantiate an objective object having a resource collection and instructions that specify processing performed by the objective object, the resource collection identifying at least one resource object that controls a capacity of at least one resource provided by at least one computer system, the capacity being sufficient for processing to be performed at a predetermined performance level.

A method and apparatus for transmitting a service flow based on a flexible Ethernet, where a bandwidth resource corresponding to a bundling group (BG) of a flexible Ethernet is divided into M timeslots, service data of a service flow is encapsulated in N timeslots in the M timeslots, and the method includes: when a first PHY in the BG fails, determining, based on a preconfigured first timeslot configuration table (TCT), a target timeslot (TTS) in the N timeslots that is mapped to the first PHY; searching the M timeslots for an idle timeslot (ITS) based on the first TCT; adjusting the first TCT when a quantity of ITSs is greater than or equal to a quantity of TTSs, so that all the N timeslots are mapped to PHYs other than the first PHY; and transmitting the service flow by using the mapped PHYs of the bundling group.

Device group partitions and a settlement platform are provided. In some embodiments, device group partitions (e.g., partitions of devices based on associated device groups) are provided. In some embodiments, a settlement platform service is provided. In some embodiments, a settlement platform service is provided for partitioned devices. In some embodiments, collecting device generated service usage information for one or more devices in wireless communication on a wireless network; and aggregating the device generated service usage information for a settlement platform for the one or more devices in wireless communication on the wireless network is provided. In some embodiments, a settlement platform implements a service billing allocation and/or a service/transactional revenue share among one or more partners. In some embodiments, service usage information includes micro-CDRs, which are used for CDR mediation or reconciliation that provides for service usage accounting on any device activity that is desired. In some embodiments, each device activity that is desired to be associated with a billing event is assigned a micro-CDR transaction code, and a service processor of the device is programmed to account for that activity associated with that transaction code. In some embodiments, a service processor executing on a wireless communications device periodically reports (e.g., during each heartbeat or based on any other periodic, push, and/or pull communication technique(s)) micro-CDR usage measures to, for example, a service controller or some other network element for CDR mediation or reconciliation.

Disclosed are various embodiments for customer-defined capacity limit plans in communication networks. In one embodiment, a request for a service from a radio-based network is received from a first client device. A network function in the radio-based network is determined to be at a capacity limit. Service from the network function to a second client device to the network function is suspended in response to determining that the network function in the radio-based network is at the capacity limit and based at least in part on a rule set specific to the radio-based network. The first client device is provided access to the network function instead of the second client device.

A system for provisioning an elastic computing infrastructure is provided. The system includes a memory and at least one processor coupled to the memory. The system also includes a management component executed by the at least one processor and configured to instantiate an objective object having a resource collection and instructions that specify processing performed by the objective object, the resource collection identifying at least one resource object that controls a capacity of at least one resource provided by at least one computer system, the capacity being sufficient for processing to be performed at a predetermined performance level.

Methods, apparatuses and computer programs are disclosed. The method of allocating network resources to a plurality of media flows in a communications network, the method comprising the steps of: determining a media content characteristic for the plurality of media flows; partitioning the plurality of media flows into one or more media flow groups based on the media content characteristic; initiating allocation of a separate network resource pool to the one or more media flow groups to be used by media flows belonging to respective media flow group.

Described herein is a system for automatically capturing configuration changes to the cloud computing resources. The system for automatically capturing configuration changes may detect changes to configurations of cloud computing resources across the geographic regions, in real-time. The changes may be stored in a central data storage device instantiated by a central cloud computing account. Furthermore, a relationship graph indicating the relationships between the different cloud computing resources may be generated.