A method for transmitting a data resource acquisition request includes: when transmitting an acquisition request for a first data resource, obtaining, by a first node, locally-stored traffic scheduling policies of a plurality of secondary nodes associated with a resource server to which the first data resource belongs, wherein the traffic scheduling policies are generated by each of the plurality of secondary nodes based on a local traffic load status; selecting, by the first node, a target node among the plurality of secondary nodes based on the traffic scheduling policies of the plurality of secondary nodes; and transmitting, by the first node, the acquisition request for the first data resource to the target node.

This invention is a bus communication protocol. A master device stores bus credits. The master device may transmit a bus transaction only if it holds sufficient number and type of bus credits. Upon transmission, the master device decrements the number of stored bus credits. The bus credits correspond to resources on a slave device for receiving bus transactions. The slave device must receive the bus transaction if accompanied by the proper credits. The slave device services the transaction. The slave device then transmits a credit return. The master device adds the corresponding number and types of credits to the stored amount. The slave device is ready to accept another bus transaction and the master device is re-enabled to initiate the bus transaction. In many types of interactions a bus agent may act as both master and slave depending upon the state of the process.

A transit device receives a target token request sent by a data transmit end, and sends the target token request to a data receive end. The data receive end may determine, based on the target token request, a target token packet corresponding to the target token request, and then send the target token packet to the transit device based on a priority identifier. The transit device determines a sending rate of the token packet based on a link bandwidth of the current device, a preset packet length of a token packet, and a preset packet length of the data packet, and sends the target token packet to the data transmit end based on the priority identifier and the sending rate of the token packet. The transit device may send the target data packet to the data receive end.

MPTCP connections and their corresponding TCP subfiows are routed by a load balancer toward backends. Each MPTCP connection is routed to a single backend and is able to include primary and secondary TCP subfiows. Routing includes performing, responsive to setting up a primary TCP subflow of an MPTCP connection, load balancing of the connection to select a backend for the connection. The MPTCP connections and their TCP subflows are tracked by the load balancer to route the MPTCP connections and their corresponding TCP subfiows to corresponding selected backends. A backend determines whether a request by a client to set up a primary TCP subflow of an MPTCP connection already includes a key used to generate a token used to uniquely identify the MPTCP connection from other MPTCP connections. The backend generates the token based on the key. The backend uses the token to distinguish subsequent communications for the MPTCP connection.

At an Edge Node, a method of handling data packets in order to mark the packets with respective packet values indicative of a level of importance. The method comprises implementing a variable rate token bucket to determine an estimated arrival rate of a flow of packets. The method comprises receiving a data packet, updating the estimated arrival rate to an updated arrival rate based on a token level of the token bucket and generating a random or pseudo-random number within a range with a limit determined by the updated arrival rate. The method further comprises identifying an operator policy which determines a level of service associated with the flow of packets, and a Throughput Value Function (TVF) associated with said policy, and then applying the TVF to the random number to calculate a packet value. The packet value is included in a header of the packet.

A network device for a communications network includes a port configured to transmit data to the network at a maximum transmit data rate. The device also includes a transmit buffer configured to buffer data units that are ready for transmission to the network, and a packet buffer configured to buffer data units before the data units are ready for transmission. The packet buffer is configured to output data units at a maximum packet buffer transmission rate faster than the maximum transmit data rate. The device includes a rate controller configured to control a transmission rate of data from the packet buffer to the transmit buffer so that averaged over a period, the transmission rate from the packet buffer to the transmit buffer is at most equal to the maximum transmit data rate, while allowing the transmission rate, at one or more time intervals, to exceed the maximum transmit data rate.

Packet forwarding includes creating a first lookup table for mapping packets to nodes based on the number of nodes in a first set of nodes. A received packet is mapped to a mapping value using a predetermined mapping function. The first lookup table is indexed using a first subset of bits comprising the mapping value. A second lookup table is created in response to adding a node to the first set of nodes. A subsequently received packet is mapped to a mapping value using the same predetermined mapping function to index the second lookup table using a second subset of bits comprising the mapping value.

Apparatus and methods are provided to enhance BSR and LCP procedures for the dual connectivity system. In one novel aspect, the BSR is handled for each MAC entity according to one or more allocation rules. In one embodiment, the allocation rule is configured by the network. In another embodiment, the allocation rule is determined by the UE based on historic statics. In yet another embodiment, the allocation rule is determined by the UE based on information from the network. In one embodiment, the allocation rule indicates percentage of traffic allocated to each MAC entity. In another novel aspect, LCP is performed independently for each MAC entity if the split bearer is configured and the prioritized bit rate (PBR) and the bucket size duration (BSD) are signaled for each eNB. In one embodiment, separate sets of LCG variables are maintained independently for each MAC entity.

Apparatuses and methods for managing jitter resulting from processing through a network interface pipeline are disclosed. In embodiments, a network traffic scheduler annotates packets to be transmitted over a bandwidth-limited network connection with time relationship information to ensure downstream bandwidth limitations are not violated. Following processing through a network interface pipeline, a jitter shaper inspects the annotated time relationship information and pipeline-imposed delays and, by imposing a variable delay, reestablishes bandwidth-complaint time relationships based upon the annotated time relationship information and configured tolerances.

This application provides a scheduling method and an apparatus. The method includes: determining, by an application processor, a type of a to-be-sent data packet, and putting, by the application processor, the to-be-sent data packet into a quality of service QoS data flow corresponding to the type of the to-be-sent data packet, where the type of the to-be-sent data packet is a GBR type or a non-GBR type; and scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the GBR type to send the to-be-sent data packet to a modem in a terminal in which the application processor is located, and after determining that a data transmission rate requirement of the GBR type is met, scheduling, by the application processor, a to-be-sent data packet in a QoS data flow corresponding to the non-GBR type to send the to-be-sent data packet to the modem.