An apparatus is provided which comprises: a first network interface (NI) to receive data from a source; a second NI coupled to a target; and a circuitry to generate a sequence of source timestamps and a sequence of target timestamps, wherein the first NI is to receive the sequence of source timestamps, and associate a first source timestamp of the sequence of source timestamps with the data, and wherein the second NI is to receive: the data with the first source timestamp from the first NI and the sequence of target timestamps from the circuitry, the second NI to generate a timestamp for the data, based at least in part on the first source timestamp and a first target timestamp of the sequence of target timestamps.

Disclosed are methods lossless traffic forwarding using distributed delay offset matching. The lossless traffic forwarding method includes calculating a delay offset between a first forwarding path between a transmitting node and a receiving node and a second forwarding path between the transmitting node and the receiving node, and controlling a buffer resource by an extent of the delay offset to delay packets to be forwarded on the first forwarding path.

Systems and methods for communications network failure detection and remediation utilizing link probes are disclosed. Exemplary methods include: receiving first communications from a first client; authenticating the first user of the first client; creating a registration for the first client in a registration database; establishing a connection to the first client; detecting the connection to the first client has failed, the detecting comprising using a link probe to test connectivity of the first client and utilizing a voting scheme, based on the plurality of connectivity test results, to determine that the connection to the first client has failed; receiving second communications from the second client; authenticating the first user of the second client using the telephone number and the security credential; removing the registration for the first client from the registration database; creating a registration for the second client; and establishing a connection to the second client.

A domain name access method and a device are described. As described herein, a domain name server (DNS) server performs resolution on a domain name requested by the terminal device. The DNS server may then send an internet protocol (IP) address of an application server obtained through the resolution and use condition information to the terminal device. With this, communication efficiency of the terminal device can be improved, and waste of transmission resources in a communications system is also avoided.

A distributed computing system uses dynamically calculates a subset size for each of a plurality of load balancers. Each of a plurality of load balancers logs requests from client devices for connections to back-end servers and periodically sends a request report to a traffic aggregator, which aggregates the report requests from the load balancers in the corresponding zone. Each traffic aggregator sends the aggregated request data to a traffic controller, which aggregates the request data to determine a total number of requests received at the system. The total request data is transmitted through each traffic aggregator to each load balancer instance, which calculates a percentage of the total number of requests produced by the load balancer and determines a subset size based on the calculated percentage.

Aspects of the present disclosure include a content delivery network (CDN) for delivering content associated with a plurality of different types of applications/devices. Using a CDN flow application, a plurality of network flow parameters are generated for content delivery unique to different types of applications or devices. The network flow parameters include customized data transmission rates. The network flow parameters include predetermined settings for transmission control protocol (TCP) connections between the CDN and devices using a TCP flow control mechanism. Upon receiving a content request, the CDN fulfills the content request based upon first network flow parameters. The network flow parameters may be adjusted for each of the plurality of different types of applications/devices. The network flow parameters may be generated based upon requests or based upon the performance of each of the plurality of applications/devices.

This application provides a packet processing method and apparatus, to avoid chain impact of an abnormal packet caused by an abnormal underlying latency on an uncertain target flow. The method includes: receiving, by a first device, a first packet sent by a second device, where the first packet carries a first label, and the first label is determined based on a cycle in which the second device sends the first packet; determining, by the first device based on the first label, whether the first packet is a normal packet; if determining that the first packet is a normal packet, determining, by the first device, a second packet based on the first packet, where the second packet carries a second label; and sending, by the first device, the second packet to a third device in a first cycle, where the second label is determined based on the first cycle.

Apparatus and methods are provided for a wireless device and an access node connected with each other over a wireless connection that has a configured packet delay budget and that transports a packet flow established between the wireless device and another device. In response to determining that the packet delay budget of the wireless connection should be adjusted based on end-to-end packet delay measurement performed by the wireless device communication, the wireless device sends an adjustment indication to the access node, where the adjustment indication includes an adjustment value to be applied by the access node in order to change the packet delay budget of the wireless connection. The adjustment value is provided for power saving operation or coverage enhancement of the wireless device.

Methods and apparatus for memory allocation and reallocation in networking stack infrastructures. Unlike prior art monolithic networking stacks, the exemplary networking stack architecture described hereinafter includes various components that span multiple domains (both in-kernel, and non-kernel). For example, unlike traditional “socket” based communication, disclosed embodiments can transfer data directly between the kernel and user space domains. A user space networking stack is disclosed that enables extensible, cross-platform-capable, user space control of the networking protocol stack functionality. The user space networking stack facilitates tighter integration between the protocol layers (including TLS) and the application or daemon. Exemplary systems can support multiple networking protocol stack instances (including an in-kernel traditional network stack). Due to this disclosed architecture, physical memory allocations (and deallocations) may be more flexibly implemented.

A packet processing device includes: a non-priority packet storage that stores the non-priority packet; a gate provided on an output side of the non-priority packet storage; plural priority packet storages that respectively store the priority packet; a distributer that guides a received priority packet to a priority packet storage corresponding to a delay time of a route through which the received priority packet is transmitted; a timing setting unit that sets different read cycles to respective priority packet storages; a read controller that reads priority packets from the plural priority packet storages according to the read cycles; and a gate controller that controls the gate according to the timings on which the read priority packets are output. When the read controller reads a first priority packet from one of the priority packet storages, the read controller reads a second priority packet from another priority packet storage.