H04L69/16

Transmission control protocol (TCP) and/or user datagram protocol (UDP) receive offloading

Various aspects of the present disclosure generally relate to wired and/or wireless communication. In some aspects, a device may receive a plurality of data packets at a modem of the device. The device may group, at the modem of the device, payloads of a first subset of the plurality of data packets into a container. The device may transfer, to a processor of the device and using the modem, the container via a first interface channel. The device may transfer, to the processor and using the modem, a second subset of the plurality of data packets via a second interface channel. Numerous other aspects are provided.

Invoking a random linear network coding communications protocol
11528342 · 2022-12-13 · ·

A technology is provided for invoking a random linear network coding (RLNC) communications protocol between a client and server in a network. In one example, a synchronize message requesting a network connection to a server can contain an indication that a client supports the RLNC communications protocol to encode and decode data packets using random linear network coding. The server can analyze the synchronize message for the indication that the client supports the RLNC communications protocol and send an acknowledge message to the client indicating that the server supports the RLNC communications protocol. Thereafter, the server can listen on a communications channel for a connection request sent by the client to communicate with the server using the RLNC communications protocol.

Auto discovery of network proxies

According to one or more embodiments of the disclosure, techniques herein provide for auto discovery of network proxies. In particular, in one embodiment, a controller in a computer network receives, from both source devices and destination devices, corresponding Transmission Control Protocol/Internet Protocol (TCP/IP) information and associated transaction identifiers (IDs) for packets sent by the source devices and for packets received at the destination devices. The controller may then correlate particular source TCP/IP information to particular destination TCP/IP information based on associated transaction IDs being the same, and can compare the correlated source TCP/IP information and destination TCP/IP information in order to determine whether a proxy device exists (e.g., and which particular type of proxy device exists) between the source device and the destination device.

Auto discovery of network proxies

According to one or more embodiments of the disclosure, techniques herein provide for auto discovery of network proxies. In particular, in one embodiment, a controller in a computer network receives, from both source devices and destination devices, corresponding Transmission Control Protocol/Internet Protocol (TCP/IP) information and associated transaction identifiers (IDs) for packets sent by the source devices and for packets received at the destination devices. The controller may then correlate particular source TCP/IP information to particular destination TCP/IP information based on associated transaction IDs being the same, and can compare the correlated source TCP/IP information and destination TCP/IP information in order to determine whether a proxy device exists (e.g., and which particular type of proxy device exists) between the source device and the destination device.

Multipath data transmission processing method and network device

Embodiments of this application relate to a multipath data transmission processing method and a network device. A first network device receives a packet from a first host device, and determines a first connection identifier between the first network device and a second network device based on the packet. The first network device encapsulates the packet based on the first connection identifier. The first network device sends the encapsulated packet to the second network device through one of a plurality of subflows between the first network device and the second network device. According to the embodiments of this application, multipath data transmission is implemented, a data transmission rate is increased, and a host device does not perceive a plurality of paths. The embodiments of this application can be applied to any existing communications system.

Multipath data transmission processing method and network device

Embodiments of this application relate to a multipath data transmission processing method and a network device. A first network device receives a packet from a first host device, and determines a first connection identifier between the first network device and a second network device based on the packet. The first network device encapsulates the packet based on the first connection identifier. The first network device sends the encapsulated packet to the second network device through one of a plurality of subflows between the first network device and the second network device. According to the embodiments of this application, multipath data transmission is implemented, a data transmission rate is increased, and a host device does not perceive a plurality of paths. The embodiments of this application can be applied to any existing communications system.

Multi-stride packet payload mapping for robust transmission of data
11522816 · 2022-12-06 · ·

Systems and methods for packet payload mapping for robust transmission of data are described. For example, methods may include receiving, using a network interface, packets that each respectively include a primary frame and one or more preceding frames from the sequence of frames of data that are separated from the primary frame in the sequence of frames by a respective multiple of a stride parameter; storing the frames of the packets in a buffer with entries that each hold the primary frame and the one or more preceding frames of a packet; reading a first frame from the buffer as the primary frame from one of the entries; determining that a packet with a primary frame that is a next frame in the sequence has been lost; and, responsive to the determination, reading the next frame from the buffer as a preceding frame from one of the entries.

Multi-stride packet payload mapping for robust transmission of data
11522816 · 2022-12-06 · ·

Systems and methods for packet payload mapping for robust transmission of data are described. For example, methods may include receiving, using a network interface, packets that each respectively include a primary frame and one or more preceding frames from the sequence of frames of data that are separated from the primary frame in the sequence of frames by a respective multiple of a stride parameter; storing the frames of the packets in a buffer with entries that each hold the primary frame and the one or more preceding frames of a packet; reading a first frame from the buffer as the primary frame from one of the entries; determining that a packet with a primary frame that is a next frame in the sequence has been lost; and, responsive to the determination, reading the next frame from the buffer as a preceding frame from one of the entries.

METHOD AND APPARATUS FOR COMPRESSION PROFILE DISTRIBUTION
20220385745 · 2022-12-01 ·

Header compression/decompression profiles are stored in a central registry, or database, and provided on demand, on initialisation of a new device, from time to time, or otherwise, to gateways communicating with one or more endpoints in accordance with the profile in question. The profile to be retrieved is selected on the basis of an identity value included in a message transmitted from the endpoint. The identity may be unique to a particular endpoint, or a type or class of endpoints using a particular profile, or correspond directly to the profile, or otherwise. Distributed registry structures, possibly including private and public registers, are proposed. Different classes of information may be associated with each profile, which may be subject to varying degrees of protection, and or varying access conditions.

METHOD AND APPARATUS FOR COMPRESSION PROFILE DISTRIBUTION
20220385745 · 2022-12-01 ·

Header compression/decompression profiles are stored in a central registry, or database, and provided on demand, on initialisation of a new device, from time to time, or otherwise, to gateways communicating with one or more endpoints in accordance with the profile in question. The profile to be retrieved is selected on the basis of an identity value included in a message transmitted from the endpoint. The identity may be unique to a particular endpoint, or a type or class of endpoints using a particular profile, or correspond directly to the profile, or otherwise. Distributed registry structures, possibly including private and public registers, are proposed. Different classes of information may be associated with each profile, which may be subject to varying degrees of protection, and or varying access conditions.