An edge termination point (ETP) transport protocol between two or more ETPs in a network, such as a Layer 2 transport network, may be provided. A device may receive an incoming internet protocol (IP) transaction at an edge termination point (ETP) in a network. The device may terminate the received incoming IP transaction at the ETP. The device may map the terminated incoming IP transaction onto an ETP-to-ETP communication. The device may control the ETP-to-ETP communication. For example, the device may control the ETP-to-ETP communication based on a resource management regime. The device may map the ETP-to-ETP communication onto one or more outgoing IP transactions at the ETP. The device may map the IP transaction onto an ETP-ETP communication. The ETP-ETP communication may include one or more ETP flows and one or more ETP transactions.

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 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 system having scalable sockets to support User Datagram Protocol (UDP) connections identifies a plurality of UDP connections, wherein a plurality of remote clients connect to corresponding ones of the plurality of UDP connections. Each one of a plurality of UDP sockets is associated with a corresponding one of the plurality of UDP connections. A network stack lookup for UDP packets in network traffic is performed using a network stack to identify the UDP socket corresponding to the remote client associated with each of the UDP packet. The UDP packets are buffered with a send buffer and a receive buffer for the UDP socket corresponding to the remote client associated with the UDP packets as determined by the network stack lookup to support communication over the plurality of UDP connections using the plurality of UDP sockets. The system thereby operates more efficiently and/or is more scalable.

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 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 broadcast signal transmission method comprises outputting an RoHC channel that includes one or more RoHC streams and a signaling table that includes information related to header compression by performing header compression for Internet Protocol (IP) packets, which include broadcast data, in accordance with an adaptation mode, a header of each IP packet including an IP header and a User Datagram Protocol (UDP) header, generating at least one first link layer packet that includes the RoHC channel and generating at least one second link layer packet that includes the signaling table, and physical layer processing the at least one first link layer packet and the at least one second link layer packet and transmitting through one or more Physical Layer Pipes (PLPs), wherein the signaling table includes adaptation mode information indicating the adaptation mode, and each RoHC stream in the RoHC channel includes RoHC packets.

A broadcast signal transmission method comprises outputting an RoHC channel that includes one or more RoHC streams and a signaling table that includes information related to header compression by performing header compression for Internet Protocol (IP) packets, which include broadcast data, in accordance with an adaptation mode, a header of each IP packet including an IP header and a User Datagram Protocol (UDP) header, generating at least one first link layer packet that includes the RoHC channel and generating at least one second link layer packet that includes the signaling table, and physical layer processing the at least one first link layer packet and the at least one second link layer packet and transmitting through one or more Physical Layer Pipes (PLPs), wherein the signaling table includes adaptation mode information indicating the adaptation mode, and each RoHC stream in the RoHC channel includes RoHC packets.

A terrestrial terminal enables communications, over a network connection, between a local host of one or more connected local hosts and a remote host. The terrestrial terminal is configured to perform operations comprising: receiving, from the remote host, a network packet for the local host; obtaining, from the network packet, an included TCP segment; determining, from the TCP segment, a receive window size advertised by the remote host; computing, using one or more characteristics of the network connection, a target receive window size; comparing the target receive window size with the advertised receive window size; and in response to determining that the target receive window size is different from the advertised receive window size: modifying the TCP segment by replacing the advertised receive window size with the target receive window size, and forwarding the network packet with the modified TCP segment to the local host.

A bridge circuit includes an NVMe device controller, a network subsystem, and a data transfer circuit. The NVMe device controller is arranged to communicate with a host via a PCIe bus. The network subsystem is arranged to communicate with an NVMe-TCP device via a network. The data transfer circuit is coupled between the NVMe device controller and the network subsystem, and is arranged to deal with data transfer associated with the NVMe-TCP device without intervention of the host.