A device establishes flows associated with one or more applications using control plane signaling. A gateway device obtains a request for a network token during the control plane signaling. The gateway device derives the network token and sends it to the device and/or an access node during the control plane signaling. The device and/or access node obtain the network token, where the network token is associated with a first flow of the one or more flows, a first application of the one or more applications, and provisioned to the device or access node via the control plane signaling. The network token may be included in a packet sent in the user plane from the device. The network token may be verified at the access node and/or the gateway device using a cryptographic function and sent to its destination based on the results of the verification.

A digital data communications network that supports efficient, scalable routing of data and use of network resources by combining a recursive division of the network into hierarchical sub-networks with repeating parameterized general purpose link communication protocols and an addressing methodology that reflects the physical structure of the underlying network hardware. The sub-division of the network enhances security by reducing the amount of the network visible to an attack and by insulating the network hardware itself from attack. The fixed bandwidth range at each sub-network level allows quality of service to be assured and controlled. The routing of data is aided by a topological addressing scheme that allows data packets to be forwarded towards their destination based on only local knowledge of the network structure, with automatic support for mobility and multicasting. The repeating structures in the network greatly simplify network management and reduce the effort to engineer new network capabilities.

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.

A method for transmitting packets includes: determining, by a transmitting device based on a length of a packet, whether a quantity of tokens in a first token bucket meets a requirement for transmitting the packet, where a token injection rate of the first token bucket is set based on bandwidth of a first link. If the quantity of tokens in the first token bucket meets the requirement for transmitting the packet, a quantity of tokens required for transmitting the packet is obtained, and the packet is transmitted using the first link. If the quantity of tokens in the first token bucket does not meet the requirement for transmitting the packet, determining whether a second link is congested. If the second link is not in a congested state, the transmitting device transmits the packet by using the second link.

This application provides a packet scheduling method and a related device. The method includes: An access device receives a to-be-scheduled packet, and obtains an actual packet length of the to-be-scheduled packet; the access device determines a first compensation value and a second compensation value based on the to-be-scheduled packet, and determines a first packet length and a second packet length; and the access device schedules the to-be-scheduled packet based on the first packet length and the second packet length. By implementing the method in this application, the access device estimates a packet length of a packet received by each device on a packet forwarding path, and then schedules the packet based on the estimated packet length of the packet received by each device, so that the access device can manage bandwidth of each device on a network more accurately.

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.

An ingress packet processor in a device corresponds to a group of ports and receives network packets from ports in its port group. A traffic manager in the device manages buffers storing packet data for transmission to egress packet processors. An ingress arbiter is associated with a port group and connects the port group to an ingress packet processor coupled to the ingress arbiter. The ingress arbiter determines a traffic rate at which the associated ingress packet processor transmits packets to the traffic manager. The ingress arbiter controls an associated traffic shaper to generate a number of tokens that are assigned to the port group. Upon receiving packet data from a port in the group, the ingress arbiter determines, using information from the traffic shaper, whether a token is available. Conditioned on determining that a token is available, the ingress arbiter forwards the packet data to the ingress packet processor.

This disclosure provides a data transmission method and apparatus. The method includes: determining a data flow mapped onto a data radio bearer (DRB); and controlling a transmission rate of the data flow based on the transmission rate of the data flow and a first rate threshold of the data flow. This disclosure provides the data transmission method and apparatus, to control the transmission rate of the data flow mapped onto the DRB.

An improved autonegotiation approach includes determining that a negotiated rate between a first network device and a second network device exceeds data transfer capacity over a network path downstream of the second network device. In response, a configuration message is generated and transmitted to the first network device. When received by the first network device, the configuration message causes the first network device to limit data transfer between the first network device and the second network device to no more than the downstream data transfer capacity.

Ingress packet processors in a device receive network packets from ingress ports. A crossbar in the device receives, from the ingress packet processors, packet data of the packets and transmits information about the packet data to a plurality of traffic managers in the device. Each traffic manager computes a total amount of packet data to be written to buffers across the plurality of traffic managers, where each traffic manager manages one or more buffers that store packet data. Each traffic manager compares the total amount of packet data to one or more threshold values. Upon determining that the total amount of packet data is equal to or greater than a threshold value, each traffic manager drops a portion of the packet data, and writes a remaining portion of the packet data to the buffers managed by the traffic manager.