Bright Data Ltd.

Israel

Back to Profile

1-100 of 227 for Bright Data Ltd. Sort by
Query
Patent
United States - USPTO
Aggregations Reset Report
Date
New (last 4 weeks) 1
2024 June (MTD) 1
2024 May 4
2024 April 6
2024 March 4
See more
IPC Class
H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] 137
H04L 67/01 - Protocols 88
H04L 9/40 - Network security protocols 86
H04L 29/06 - Communication control; Communication processing characterised by a protocol 80
H04L 29/08 - Transmission control procedure, e.g. data link level control procedure 79
See more
Status
Pending 71
Registered / In Force 156
Found results for  patents
  1     2     3        Next Page

1.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18438541
Status Pending
Filing Date 2024-02-12
First Publication Date 2024-06-06
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

2.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18390343
Status Pending
Filing Date 2023-12-20
First Publication Date 2024-05-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

3.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18409847
Status Pending
Filing Date 2024-01-11
First Publication Date 2024-05-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

4.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18409849
Status Pending
Filing Date 2024-01-11
First Publication Date 2024-05-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

5.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18409845
Status Pending
Filing Date 2024-01-11
First Publication Date 2024-05-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

6.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18392023
Status Pending
Filing Date 2023-12-21
First Publication Date 2024-04-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

7.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18390397
Status Pending
Filing Date 2023-12-20
First Publication Date 2024-04-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

8.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18391972
Status Pending
Filing Date 2023-12-21
First Publication Date 2024-04-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

9.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18392043
Status Pending
Filing Date 2023-12-21
First Publication Date 2024-04-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

10.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18390366
Status Pending
Filing Date 2023-12-20
First Publication Date 2024-04-11
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

11.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18392001
Status Pending
Filing Date 2023-12-21
First Publication Date 2024-04-11
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

12.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18513673
Status Pending
Filing Date 2023-11-20
First Publication Date 2024-03-21
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks

13.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18513677
Status Pending
Filing Date 2023-11-20
First Publication Date 2024-03-21
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

14.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18513680
Status Pending
Filing Date 2023-11-20
First Publication Date 2024-03-14
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

15.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18513681
Status Pending
Filing Date 2023-11-20
First Publication Date 2024-03-14
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

16.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18378667
Status Pending
Filing Date 2023-10-11
First Publication Date 2024-02-01
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions

17.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18378673
Status Pending
Filing Date 2023-10-11
First Publication Date 2024-02-01
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

18.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18378676
Status Pending
Filing Date 2023-10-11
First Publication Date 2024-02-01
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

19.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18378671
Status Pending
Filing Date 2023-10-11
First Publication Date 2024-02-01
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions

20.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18378672
Status Pending
Filing Date 2023-10-11
First Publication Date 2024-02-01
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions

21.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18373310
Status Pending
Filing Date 2023-09-27
First Publication Date 2024-01-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions

22.

System providing faster and more efficient data communication

      
Application Number 18373304
Grant Number 11956299
Status In Force
Filing Date 2023-09-27
First Publication Date 2024-01-11
Grant Date 2024-04-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

23.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18241873
Status Pending
Filing Date 2023-09-03
First Publication Date 2023-12-21
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

24.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18241874
Status Pending
Filing Date 2023-09-03
First Publication Date 2023-12-21
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

25.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18229215
Status Pending
Filing Date 2023-08-02
First Publication Date 2023-11-23
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions

26.

Emulating Web Browser in a Dedicated Intermediary Box

      
Application Number 18211338
Status Pending
Filing Date 2023-06-19
First Publication Date 2023-11-16
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Kol, Ron
  • Lenchner, Or

Abstract

Anonymity and privacy of a client device that fetches a content from a web server are improved by using an intermediate device located along the communication path between the client device and the web server. The primary or exclusive function of the intermediate device may be to serve as an intermediate device, and may be implemented as a stand-alone dedicated client device located at a residential premises, or may be integrated with another device, such as a router or a sensor unit, and may communicate using wired communication (such as LAN) or wireless communication (such as WLAN). The intermediate device may modify a content request from the client device in order to avoid identification or blocking by a web server that uses web tracking, such as fingerprinting. The modification may use a web browser, such as a headless browser, for emulating a different device or user.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/957 - Browsing optimisation, e.g. caching or content distillation

27.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18215430
Status Pending
Filing Date 2023-06-28
First Publication Date 2023-11-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/141 - Setup of application sessions
  • H04L 43/0864 - Round trip delays
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

28.

System and Method for Streaming Content from Multiple Servers

      
Application Number 18215406
Status Pending
Filing Date 2023-06-28
First Publication Date 2023-10-26
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system and a method for media streaming from multiple sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that may include multiple Content Delivery Networks (CDNs) and independent servers. Based on a pre-set criteria, such as the source delivery performance and cost, the client device partitions the content into parts, allocates a source to each part, and simultaneously receives media streams of the content parts from the allocated sources. The server may be a Video-on-Demand (VOD) server, and the content may be a single file of a video data, such as a movie. The delivery performance of the used sources is measured during the streaming for updating the partition or the allocation. The updated measured performance may be stored locally at the client device, or at a server for use by other clients. The client actions may be implemented as a client-side script.

IPC Classes  ?

  • H04N 21/61 - Network physical structure; Signal processing
  • H04L 65/80 - Responding to QoS
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04N 21/845 - Structuring of content, e.g. decomposing content into time segments
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

29.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18209193
Status Pending
Filing Date 2023-06-13
First Publication Date 2023-10-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

30.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18209837
Status Pending
Filing Date 2023-06-14
First Publication Date 2023-10-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

31.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18209218
Status Pending
Filing Date 2023-06-13
First Publication Date 2023-10-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

32.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18209815
Status Pending
Filing Date 2023-06-14
First Publication Date 2023-10-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

33.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 18209863
Grant Number 11956094
Status In Force
Filing Date 2023-06-14
First Publication Date 2023-10-12
Grant Date 2024-04-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 9/40 - Network security protocols
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

34.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18196091
Status Pending
Filing Date 2023-05-11
First Publication Date 2023-09-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

35.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18120377
Grant Number 12003605
Status In Force
Filing Date 2023-03-11
First Publication Date 2023-08-24
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

36.

System providing faster and more efficient data communication

      
Application Number 18138093
Grant Number 12003568
Status In Force
Filing Date 2023-04-23
First Publication Date 2023-08-24
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

37.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 18138100
Status Pending
Filing Date 2023-04-23
First Publication Date 2023-08-24
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

38.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 18138099
Status Pending
Filing Date 2023-04-23
First Publication Date 2023-08-17
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

39.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 18139364
Status Pending
Filing Date 2023-04-26
First Publication Date 2023-08-17
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

40.

System providing faster and more efficient data communication

      
Application Number 18138095
Grant Number 12003569
Status In Force
Filing Date 2023-04-23
First Publication Date 2023-08-17
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

41.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 18139361
Status Pending
Filing Date 2023-04-26
First Publication Date 2023-08-17
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

42.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18123273
Status Pending
Filing Date 2023-03-18
First Publication Date 2023-08-10
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

43.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18120378
Status Pending
Filing Date 2023-03-11
First Publication Date 2023-07-20
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

44.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18120376
Grant Number 11985212
Status In Force
Filing Date 2023-03-11
First Publication Date 2023-07-06
Grant Date 2024-05-14
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

45.

System providing faster and more efficient data communication

      
Application Number 18112578
Grant Number 12003567
Status In Force
Filing Date 2023-02-22
First Publication Date 2023-06-29
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

46.

System and Method for Streaming Content from Multiple Servers

      
Application Number 18099954
Status Pending
Filing Date 2023-01-22
First Publication Date 2023-06-29
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system and a method for media streaming from multiple sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that may include multiple Content Delivery Networks (CDNs) and independent servers. Based on a pre-set criteria, such as the source delivery performance and cost, the client device partitions the content into parts, allocates a source to each part, and simultaneously receives media streams of the content parts from the allocated sources. The server may be a Video-on-Demand (VOD) server, and the content may be a single file of a video data, such as a movie. The delivery performance of the used sources is measured during the streaming for updating the partition or the allocation. The updated measured performance may be stored locally at the client device, or at a server for use by other clients. The client actions may be implemented as a client-side script.

IPC Classes  ?

  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04N 21/61 - Network physical structure; Signal processing
  • H04L 65/80 - Responding to QoS
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04N 21/845 - Structuring of content, e.g. decomposing content into time segments
  • H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

47.

System providing faster and more efficient data communication

      
Application Number 18112587
Grant Number 11962636
Status In Force
Filing Date 2023-02-22
First Publication Date 2023-06-22
Grant Date 2024-04-16
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

48.

System providing faster and more efficient data communication

      
Application Number 18112572
Grant Number 12003566
Status In Force
Filing Date 2023-02-22
First Publication Date 2023-06-22
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

49.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18099982
Grant Number 11924307
Status In Force
Filing Date 2023-01-23
First Publication Date 2023-05-25
Grant Date 2024-03-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

50.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 18099980
Status Pending
Filing Date 2023-01-23
First Publication Date 2023-05-25
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

51.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18099984
Grant Number 11979475
Status In Force
Filing Date 2023-01-23
First Publication Date 2023-05-18
Grant Date 2024-05-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

52.

System and Method for Streaming Content from Multiple Servers

      
Application Number 18099956
Status Pending
Filing Date 2023-01-22
First Publication Date 2023-05-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system and a method for media streaming from multiple sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that may include multiple Content Delivery Networks (CDNs) and independent servers. Based on a pre-set criteria, such as the source delivery performance and cost, the client device partitions the content into parts, allocates a source to each part, and simultaneously receives media streams of the content parts from the allocated sources. The server may be a Video-on-Demand (VOD) server, and the content may be a single file of a video data, such as a movie. The delivery performance of the used sources is measured during the streaming for updating the partition or the allocation. The updated measured performance may be stored locally at the client device, or at a server for use by other clients. The client actions may be implemented as a client-side script.

IPC Classes  ?

  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04N 21/61 - Network physical structure; Signal processing
  • H04L 65/80 - Responding to QoS
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04N 21/845 - Structuring of content, e.g. decomposing content into time segments
  • H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

53.

System and method for streaming content from multiple servers

      
Application Number 18099958
Grant Number 12003562
Status In Force
Filing Date 2023-01-22
First Publication Date 2023-05-18
Grant Date 2024-06-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system and a method for media streaming from multiple sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that may include multiple Content Delivery Networks (CDNs) and independent servers. Based on a pre-set criteria, such as the source delivery performance and cost, the client device partitions the content into parts, allocates a source to each part, and simultaneously receives media streams of the content parts from the allocated sources. The server may be a Video-on-Demand (VOD) server, and the content may be a single file of a video data, such as a movie. The delivery performance of the used sources is measured during the streaming for updating the partition or the allocation. The updated measured performance may be stored locally at the client device, or at a server for use by other clients. The client actions may be implemented as a client-side script.

IPC Classes  ?

  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
  • H04L 65/80 - Responding to QoS
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04N 21/61 - Network physical structure; Signal processing
  • H04N 21/845 - Structuring of content, e.g. decomposing content into time segments

54.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18099988
Status Pending
Filing Date 2023-01-23
First Publication Date 2023-05-18
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

55.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 18081988
Status Pending
Filing Date 2022-12-15
First Publication Date 2023-04-20
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

56.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 18082011
Status Pending
Filing Date 2022-12-15
First Publication Date 2023-04-20
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

57.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18073170
Grant Number 11949756
Status In Force
Filing Date 2022-12-01
First Publication Date 2023-04-13
Grant Date 2024-04-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

58.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 18073137
Status Pending
Filing Date 2022-12-01
First Publication Date 2023-04-13
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 9/40 - Network security protocols
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

59.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18073195
Grant Number 11924306
Status In Force
Filing Date 2022-12-01
First Publication Date 2023-04-06
Grant Date 2024-03-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

60.

System and method for improving internet communication by using intermediate nodes

      
Application Number 18073112
Grant Number 11838388
Status In Force
Filing Date 2022-12-01
First Publication Date 2023-03-30
Grant Date 2023-12-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

61.

SYSTEM PROVIDING FASTER AND MORE EFFICIENT DATA COMMUNICATION

      
Application Number 17943245
Status Pending
Filing Date 2022-09-13
First Publication Date 2023-01-19
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/50 - Network services
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/563 - Data redirection of data network streams
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

62.

System providing faster and more efficient data communication

      
Application Number 17943255
Grant Number 11811849
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-19
Grant Date 2023-11-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/01 - Protocols
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

63.

System and Method for Streaming Content from Multiple Servers

      
Application Number 17943233
Status Pending
Filing Date 2022-09-13
First Publication Date 2023-01-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system and a method for media streaming from multiple sources are disclosed. A content requesting client device accesses a server to receive a list of available sources that may include multiple Content Delivery Networks (CDNs) and independent servers. Based on a pre-set criteria, such as the source delivery performance and cost, the client device partitions the content into parts, allocates a source to each part, and simultaneously receives media streams of the content parts from the allocated sources. The server may be a Video-on-Demand (VOD) server, and the content may be a single file of a video data, such as a movie. The delivery performance of the used sources is measured during the streaming for updating the partition or the allocation. The updated measured performance may be stored locally at the client device, or at a server for use by other clients. The client actions may be implemented as a client-side script.

IPC Classes  ?

  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04N 21/61 - Network physical structure; Signal processing
  • H04N 21/845 - Structuring of content, e.g. decomposing content into time segments
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04L 65/65 - Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/80 - Responding to QoS

64.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17943236
Grant Number 11838386
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-05
Grant Date 2023-12-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

65.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17943241
Grant Number 11870874
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-05
Grant Date 2024-01-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

66.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 17943280
Status Pending
Filing Date 2022-09-13
First Publication Date 2023-01-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • G06F 9/54 - Interprogram communication
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • H04L 61/59 - Network arrangements, protocols or services for addressing or naming using proxies for addressing
  • H04L 67/56 - Provisioning of proxy services

67.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 17943294
Status Pending
Filing Date 2022-09-13
First Publication Date 2023-01-05
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/01 - Protocols
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • G06F 9/54 - Interprogram communication
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 61/59 - Network arrangements, protocols or services for addressing or naming using proxies for addressing
  • H04L 67/56 - Provisioning of proxy services

68.

System providing faster and more efficient data communication

      
Application Number 17943242
Grant Number 11916993
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-05
Grant Date 2024-02-27
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

69.

System providing faster and more efficient data communication

      
Application Number 17943249
Grant Number 11949729
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-05
Grant Date 2024-04-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data

70.

System providing faster and more efficient data communication

      
Application Number 17943262
Grant Number 11811850
Status In Force
Filing Date 2022-09-13
First Publication Date 2023-01-05
Grant Date 2023-11-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/01 - Protocols
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

71.

System providing faster and more efficient data communication

      
Application Number 17882547
Grant Number 11811848
Status In Force
Filing Date 2022-08-06
First Publication Date 2022-12-01
Grant Date 2023-11-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/01 - Protocols
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]

72.

SYSTEM AND METHOD FOR URL FETCHING RETRY MECHANISM

      
Application Number 17861386
Status Pending
Filing Date 2022-07-11
First Publication Date 2022-11-17
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for overcoming intermittent, temporary, or other fetching failures by using multiple attempts for retrieving a content from a web server to a client device is disclosed. The URL fetching may use direct or non-direct fetching schemes, or a combination thereof. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. Upon sensing a failure of a fetching action, the action is repeated using the same or different parameters or attributes, such as by using different intermediate devices, selected based on different parameters or attributes, such as different countries. The repetitions are limited to a pre-defined maximum number or attempts. The fetching attempts may be performed by the client device, by an intermediate device in a non-direct fetching scheme, or a combination thereof. Various fetching schemes may be used sequentially until the content is retrieved.

IPC Classes  ?

  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 16/909 - Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using geographical or spatial information, e.g. location
  • G06F 9/54 - Interprogram communication
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/146 - Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
  • H04L 1/00 - Arrangements for detecting or preventing errors in the information received
  • H04L 69/40 - Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
  • H04L 67/01 - Protocols
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching

73.

SYSTEM AND METHOD FOR MANAGING NON-DIRECT URL FETCHING SERVICE

      
Application Number 17862473
Status Pending
Filing Date 2022-07-12
First Publication Date 2022-11-17
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for providing and managing non-direct URL fetching service for retrieving a content from a web server to a client device is disclosed, such as for overcoming geo-blocking or a Man-In-The-Middle (MITM) attack. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. A URL request may be sent in parallel using both direct and non-direct fetching schemes, in order to verify the need for using the non-direct fetching service. Direct or non-direct fetching scheme may be selected by using a file that associates a fetching scheme to the requested URL. The selection of the fetching mechanism may use dynamically in real-time updating of a Proxy Auto-Configuration (PAC) file. As part of an accounting scheme, quotas may be applied to a cumulative received data or a time duration of using a non-direct fetching service.

IPC Classes  ?

  • H04L 9/40 - Network security protocols
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]

74.

System and method for managing non-direct URL fetching service

      
Application Number 17862457
Grant Number 12010101
Status In Force
Filing Date 2022-07-12
First Publication Date 2022-11-10
Grant Date 2024-06-11
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for providing and managing non-direct URL fetching service for retrieving a content from a web server to a client device is disclosed, such as for overcoming geo-blocking or a Man-In-The-Middle (MITM) attack. The non-direct fetching method may use intermediate devices, such as proxy server, Data-Center proxy server, tunnel devices, or any combination thereof. A URL request may be sent in parallel using both direct and non-direct fetching schemes, in order to verify the need for using the non-direct fetching service. Direct or non-direct fetching scheme may be selected by using a file that associates a fetching scheme to the requested URL. The selection of the fetching mechanism may use dynamically in real-time updating of a Proxy Auto-Configuration (PAC) file. As part of an accounting scheme, quotas may be applied to a cumulative received data or a time duration of using a non-direct fetching service.

IPC Classes  ?

  • G06F 15/16 - Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols

75.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 17861355
Status Pending
Filing Date 2022-07-11
First Publication Date 2022-11-03
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 49/40 - Constructional details, e.g. power supply, mechanical construction or backplane
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics

76.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17861367
Status Pending
Filing Date 2022-07-11
First Publication Date 2022-10-27
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

77.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17828379
Status Pending
Filing Date 2022-05-31
First Publication Date 2022-09-15
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

78.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17828423
Status Pending
Filing Date 2022-05-31
First Publication Date 2022-09-15
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

79.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17828340
Grant Number 11902400
Status In Force
Filing Date 2022-05-31
First Publication Date 2022-09-15
Grant Date 2024-02-13
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04L 43/0864 - Round trip delays
  • H04L 67/141 - Setup of application sessions
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable

80.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17681758
Grant Number 11758018
Status In Force
Filing Date 2022-02-26
First Publication Date 2022-09-08
Grant Date 2023-09-12
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

81.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17717086
Status Pending
Filing Date 2022-04-10
First Publication Date 2022-08-25
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

82.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17681755
Status Pending
Filing Date 2022-02-26
First Publication Date 2022-08-04
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

83.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17681754
Grant Number 11985210
Status In Force
Filing Date 2022-02-26
First Publication Date 2022-08-04
Grant Date 2024-05-14
Owner BRIGHT DATA LTD. (USA)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

84.

System providing faster and more efficient data communication

      
Application Number 17714475
Grant Number 11888922
Status In Force
Filing Date 2022-04-06
First Publication Date 2022-07-21
Grant Date 2024-01-30
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

85.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17714185
Grant Number 12010196
Status In Force
Filing Date 2022-04-06
First Publication Date 2022-07-21
Grant Date 2024-06-11
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi
  • H04W 4/029 - Location-based management or tracking services

86.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17714180
Grant Number 11799985
Status In Force
Filing Date 2022-04-06
First Publication Date 2022-07-21
Grant Date 2023-10-24
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

87.

System providing faster and more efficient data communication

      
Application Number 17714423
Grant Number 11770435
Status In Force
Filing Date 2022-04-06
First Publication Date 2022-07-21
Grant Date 2023-09-26
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

88.

System providing faster and more efficient data communication

      
Application Number 17714455
Grant Number 11902351
Status In Force
Filing Date 2022-04-06
First Publication Date 2022-07-21
Grant Date 2024-02-13
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A system designed for increasing network communication speed for users, while lowering network congestion for content owners and ISPs. The system employs network elements including an acceleration server, clients, agents, and peers, where communication requests generated by applications are intercepted by the client on the same machine. The IP address of the server in the communication request is transmitted to the acceleration server, which provides a list of agents to use for this IP address. The communication request is sent to the agents. One or more of the agents respond with a list of peers that have previously seen some or all of the content which is the response to this request (after checking whether this data is still valid). The client then downloads the data from these peers in parts and in parallel, thereby speeding up the Web transfer, releasing congestion from the Web by fetching the information from multiple sources, and relieving traffic from Web servers by offloading the data transfers from them to nearby peers.

IPC Classes  ?

  • H04L 67/01 - Protocols
  • H04L 41/046 - Network management architectures or arrangements comprising network management agents or mobile agents therefor
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/564 - Enhancement of application control based on intercepted application data
  • H04L 67/1001 - Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/1061 - Peer-to-peer [P2P] networks using node-based peer discovery mechanisms
  • H04L 67/1023 - Server selection for load balancing based on a hash applied to IP addresses or costs
  • H04L 67/1074 - Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L 67/50 - Network services
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

89.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17717084
Status Pending
Filing Date 2022-04-10
First Publication Date 2022-07-21
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

90.

System and Method for Improving Internet Communication by Using Intermediate Nodes

      
Application Number 17681759
Status Pending
Filing Date 2022-02-26
First Publication Date 2022-06-09
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers

91.

System and method for improving internet communication by using intermediate nodes

      
Application Number 17681761
Grant Number 11949755
Status In Force
Filing Date 2022-02-26
First Publication Date 2022-06-09
Grant Date 2024-04-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

A method for fetching a content from a web server to a client device is disclosed, using tunnel devices serving as intermediate devices. The client device accesses an acceleration server to receive a list of available tunnel devices. The requested content is partitioned into slices, and the client device sends a request for the slices to the available tunnel devices. The tunnel devices in turn fetch the slices from the data server, and send the slices to the client device, where the content is reconstructed from the received slices. A client device may also serve as a tunnel device, serving as an intermediate device to other client devices. Similarly, a tunnel device may also serve as a client device for fetching content from a data server. The selection of tunnel devices to be used by a client device may be in the acceleration server, in the client device, or in both. The partition into slices may be overlapping or non-overlapping, and the same slice (or the whole content) may be fetched via multiple tunnel devices.

IPC Classes  ?

  • H04L 67/60 - Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
  • H04L 9/40 - Network security protocols
  • H04L 43/0864 - Round trip delays
  • H04L 65/612 - Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for unicast
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/06 - Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/567 - Integrating service provisioning from a plurality of service providers
  • H04L 67/59 - Providing operational support to end devices by off-loading in the network or by emulation, e.g. when they are unavailable
  • H04N 21/462 - Content or additional data management e.g. creating a master electronic program guide from data received from the Internet and a Head-end or controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabi

92.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672762
Grant Number 11902044
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-02-13
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 67/141 - Setup of application sessions
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

93.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 17672770
Status Pending
Filing Date 2022-02-16
First Publication Date 2022-06-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 49/40 - Constructional details, e.g. power supply, mechanical construction or backplane
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/01 - Protocols
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 12/46 - Interconnection of networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/56 - Provisioning of proxy services

94.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672775
Grant Number 11876612
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-01-16
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04W 48/18 - Selecting a network or a communication service
  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

95.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672781
Grant Number 11909547
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-02-20
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 9/40 - Network security protocols
  • H04L 67/141 - Setup of application sessions
  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 12/46 - Interconnection of networks
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

96.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672792
Grant Number 11962430
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-04-16
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

97.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672805
Grant Number 11979249
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-05-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number

98.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 17672830
Status Pending
Filing Date 2022-02-16
First Publication Date 2022-06-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 49/40 - Constructional details, e.g. power supply, mechanical construction or backplane
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/01 - Protocols
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 12/46 - Interconnection of networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/56 - Provisioning of proxy services

99.

System and Method for Improving Content Fetching by Selecting Tunnel Devices

      
Application Number 17672856
Status Pending
Filing Date 2022-02-16
First Publication Date 2022-06-02
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 61/256 - NAT traversal
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • H04L 49/40 - Constructional details, e.g. power supply, mechanical construction or backplane
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 9/40 - Network security protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 67/01 - Protocols
  • G06F 7/58 - Random or pseudo-random number generators
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 12/46 - Interconnection of networks
  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/56 - Provisioning of proxy services

100.

System and method for improving content fetching by selecting tunnel devices

      
Application Number 17672818
Grant Number 11979250
Status In Force
Filing Date 2022-02-16
First Publication Date 2022-06-02
Grant Date 2024-05-07
Owner BRIGHT DATA LTD. (Israel)
Inventor
  • Shribman, Derry
  • Vilenski, Ofer

Abstract

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.

IPC Classes  ?

  • H04L 61/4511 - Network directories; Name-to-address mapping using standardised directory access protocols using domain name system [DNS]
  • G06F 7/58 - Random or pseudo-random number generators
  • G06F 8/71 - Version control ; Configuration management
  • G06F 9/455 - Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
  • G06F 9/48 - Program initiating; Program switching, e.g. by interrupt
  • G06F 16/955 - Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • H04L 9/40 - Network security protocols
  • H04L 12/28 - Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L 12/46 - Interconnection of networks
  • H04L 47/283 - Flow control; Congestion control in relation to timing considerations in response to processing delays, e.g. caused by jitter or round trip time [RTT]
  • H04L 61/256 - NAT traversal
  • H04L 61/2575 - NAT traversal using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
  • H04L 61/2585 - NAT traversal through application level gateway [ALG]
  • H04L 61/2589 - NAT traversal over a relay server, e.g. traversal using relay for network address translation [TURN]
  • H04L 61/2592 - Translation of Internet protocol [IP] addresses using tunnelling or encapsulation
  • H04L 61/5007 - Internet protocol [IP] addresses
  • H04L 67/01 - Protocols
  • H04L 67/02 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
  • H04L 67/025 - Protocols based on web technology, e.g. hypertext transfer protocol [HTTP] for remote control or remote monitoring of applications
  • H04L 67/133 - Protocols for remote procedure calls [RPC]
  • H04L 67/141 - Setup of application sessions
  • H04L 67/142 - Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
  • H04L 67/288 - Distributed intermediate devices, i.e. intermediate devices for interaction with other intermediate devices on the same level
  • H04L 67/2885 - Hierarchically arranged intermediate devices, e.g. for hierarchical caching
  • H04L 67/56 - Provisioning of proxy services
  • H04L 67/563 - Data redirection of data network streams
  • H04L 67/568 - Storing data temporarily at an intermediate stage, e.g. caching
  • H04L 67/5681 - Pre-fetching or pre-delivering data based on network characteristics
  • H04L 67/63 - Routing a service request depending on the request content or context
  • H04L 69/16 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
  • H04L 69/167 - Adaptation for transition between two IP versions, e.g. between IPv4 and IPv6
  • H04L 69/168 - Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
  • H04W 4/80 - Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
  • H04W 48/18 - Selecting a network or a communication service
  • H04W 84/10 - Small scale networks; Flat hierarchical networks
  • H04W 84/18 - Self-organising networks, e.g. ad hoc networks or sensor networks
  • H04L 101/69 - Types of network addresses using geographic information, e.g. room number
  1     2     3        Next Page