Methods, systems, and computer-readable media for providing reliable switching between different transport protocols (e.g., TCP and UDP) are presented herein. In some embodiments, a computing platform may stop transmission over a transport protocol. Subsequently, the computing platform may synchronize buffers between a client and a host. For example, the buffer may include acknowledgments for undelivered reliable packets between the client and the host. Next, the computing platform may resume transmission over a different transport protocol. In some embodiments, when establishing an initial connection between a client and a host, connections may be attempted in parallel over multiple transport protocols. After a connection over a first transport protocol is established, if a connection is later established over a second transport protocol, the connection may be transitioned to the second transport protocol. Also, ticketing semantics may be preserved in the switch between the different transport protocols.

An arrangement for a wireless communication device is disclosed. The arrangement is adapted to set up an application connection between an application of an application layer of the device and a remote server. The device comprises a modem subsystem (comprising the application layer, a remote socket client and a remote socket API between the application layer and the remote socket client), an application processor (comprising a remote socket server and an IP stack, wherein the application processor is associated with a wireless communication access unit and the IP stack is adapted to connect to a communication network using the access unit), and a remote socket protocol communication channel between the remote socket client and the remote socket server. The application is adapted to send an application connection setup request to the remote socket client via the remote socket API. The remote socket client, the remote socket server and the remote socket protocol communication channel are collectively adapted to use a remote socket protocol to set up a remote socket connection between the remote socket client and the remote server via the remote socket server and via the IP stack, using the remote socket protocol communication channel and the wireless communication access unit, and to establish the application connection based on the remote socket connection. The remote socket client is further adapted to (in response to the application connection being established) send an application connection setup response to the application via the remote socket API.

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The tunnel device is selected based on an attribute, such as IP Geolocation. A tunnel bank server stores a list of available tunnels that may be used, associated with values of various attribute types. The tunnel devices initiate communication with the tunnel bank server, and stays connected to it, for allowing a communication session initiated by the tunnel bank server. Upon receiving a request from a client to a content and for specific attribute types and values, a tunnel is selected by the tunnel bank server, and is used as a tunnel for retrieving the required content from the web server, using standard protocol such as SOCKS, WebSocket or HTTP Proxy. The client only communicates with a super proxy server that manages the content fetching scheme.

A solution for reducing transmission pathway lengths within a distributed network, as embodied in various systems, methods, and non-transitory computer-readable storage media, may include migrating a TCP socket from a request server to a data server. The solution may further include reprogramming one or more routers to recognize a new packet route based on the migrated socket. The solution may include the one or more routers subsequently communicating directly with the data server while bypassing the request server.

Layer 7 protocol (non-HTTP) client applications are executed in the browser. The non-HTTP layer 7 protocol client application connects to a compute server that proxies layer 4 packets to the origin network that has the non-HTTP layer 7 protocol service. As an example, an SSH client (a non-HTTP layer 7 protocol) can execute in the browser and the TCP packets (layer 4 packets) are proxied by a compute server to the origin network that has the appropriate SSH server. The non-HTTP layer 7 protocol client application allows users to run commands or otherwise interact with the client as if they were using a native application (one that is not executed within the browser) without any client-side configuration or agent.

Methods, systems, and computer-readable media for providing reliable switching between different transport protocols (e.g., TCP and UDP) are presented herein. In some embodiments, a computing platform may stop transmission over a transport protocol. Subsequently, the computing platform may synchronize buffers between a client and a host. For example, the buffer may include acknowledgments for undelivered reliable packets between the client and the host. Next, the computing platform may resume transmission over a different transport protocol. In some embodiments, when establishing an initial connection between a client and a host, connections may be attempted in parallel over multiple transport protocols. After a connection over a first transport protocol is established, if a connection is later established over a second transport protocol, the connection may be transitioned to the second transport protocol. Also, ticketing semantics may be preserved in the switch between the different transport protocols.

A system for offloading information transfer between a client and a server in a communications network is disclosed. The system includes a network agent to issue a data transfer offload command responsive to receiving a TCP (transmission control protocol) splice command from an application proxy. The system additionally includes a network controller to offload data transfer from a kernel space to a network responsive to the data transfer offload command.

A network device is configured to distribute audio streams and video streams among participant devices connected to the network device over a communication network. The network device collects respective audio streams from the participant devices, and ranks the participant devices based on the respective audio streams collected from the participant devices. Based on the ranking, the network device elects top-N participant devices among the participant devices as being associated with respective users who are active speakers, where N is one or more, and retrieves respective video streams only from the top-N participant devices. The network device receives from the participant devices respective requests for video streams from the top-N participant devices, and sends to the participant devices the video streams retrieved only from the top-N participant devices.

A system for optimizing dynamic multi-stream network connections and methods for making and using the same. In various embodiments, the system advantageously can use a full bandwidth available between two network appliances connected by a Transmission Control Protocol (TCP) network connection with well-defined round-trip time (RTT) latency and changing bandwidth, among other things.

An information processing system includes: a setting processing processor that registers, based on setting information acquired from a storage device through a first communication path, the storage device as a storage device capable of presenting specific information to a user terminal; an acquisition processing processor that acquires, when the storage device is registered by the setting processing processor, the specific information corresponding to a request acquired from the user terminal, through a second communication path different from the first communication path; and a presentation processing processor that presents the specific information acquired with the acquisition processing processor to the user terminal.