Network accelerator for controlled long delay links

• US 9,888,470 B2
• Filed: 02/19/2016
• Issued: 02/06/2018
• Est. Priority Date: 11/19/2004
• Status: Active Grant

• Current Assignee: ViaSat Incorporated
• Original Assignee: ViaSat Incorporated
• Inventors: Eidenschink, Thomas
• Primary Examiner(s): Crutchfield, Christopher
• Application Number:
  US15/048,895
• Publication Number:
  US 20160270044A1
• Time in Patent Office: 718 Days
• CPC Class Codes: H04B 7/185 Space-based or airborne stations; Stations for satellite systemsH04B7/204 takes precedence
• CPC Class Codes: H04B 7/18513 Transmission in a satellite or space-based system
• CPC Class Codes: H04L 2012/5608 Satellite
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/781 Centralised allocation of resources
• CPC Class Codes: H04L 47/822 Collecting or measuring resource availability data
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04L 47/826 Involving periods of time
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04L 65/1036 at the edge
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/535 Tracking the activity of the user network monitoring arrangements H04L43/00; recording of computer activity G06F11/34
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/564 Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04W 72/044 based on the type of the allocated resource
• CPC Class Codes: H04W 72/56 based on priority criteria
• CPC Class Codes: H04W 74/004 : in the uplink, i.e. towards network

Abstract

A communication system for providing network access over a shared communication link is disclosed. The communication system includes a user access point, a network access point and a communications link. The user access point is coupled to one or more user terminals that access a remote network. The network access point is coupled to the remote network. The communications link couples the user access point and the network access point. The communications link is at least partially controlled by the network access point, which monitors information passed between the remote network and the user access point to create an estimate of future usage of the communications link by the user access point based on the information. The network access point allocates communications link resources for the user access point based on the estimate.

Claims

1. A satellite communication system comprising:

a user access point; and

a network access point coupled to the user access point via a satellite communication link having a forward channel and a return channel, the network access point to;

store usage history associated with a first uniform resource locator (URL), wherein the usage history is based on resources of the return channel that were used following previous requests for the first URL;

receive a request for a second URL from the user access point;

determine that the second URL matches the first URL; and

in response to the determination, allocate resources of the return channel for the user access point based on the stored usage history associated with the first URL.

2. The satellite communication system of claim 1, wherein the usage history is based on resources of the return channel used by other users.

3. The satellite communication system of claim 1, the network access point further to:

store usage history associated with each of a plurality of URLs including the first URL;

receive a request for a third URL from the user access point;

determine that the third URL does not match any of the plurality of URLs; and

in response to the determination that the third URL does not match any of the plurality of the URLs, allocate resources of the return channel for the user access point based on usage history of a group of one or more URLs of the plurality of URLs.

4. The satellite communication system of claim 3, wherein the group of one or more URLs have the same domain as that of the third URL.

5. The satellite communication system of claim 3, wherein the group of one or more URLs each have a portion matching that of the third URL.

6. The satellite communication system of claim 1, wherein the second URL is not an exact match to the first URL.

7. The satellite communication system of claim 6, wherein the second URL and the first URL have different metadata.

8. The satellite communications system of claim 1, the network access point further to update the stored usage history associated with the first URL based on resources of the return channel used by the user access point following the request.

9. The satellite communication system of claim 8, wherein the resources of the return channel used by the user access point are due to requests for embedded objects within a web page corresponding to the first URL.

10. The satellite communications system of claim 1, wherein the allocated resources of the return channel vary over a time frame.

11. The satellite communications system of claim 10, wherein variation of the allocated resources of the return channel coincide with events associated with receiving a web page corresponding to the first URL.

12. The satellite communications system of claim 1, wherein the usage history is biased toward recent requests.

13. The satellite communications system of claim 1, wherein the allocated resources are relative to a time when the user access point receives a web page corresponding to the first URL.

14. A method comprising:

storing usage history associated with a first uniform resource locator (URL), wherein the usage history is based on resources of a return channel of a satellite communication link that were used following previous requests for the first URL;

receiving a request for a second URL from a user access point via the return channel;

determining that the second URL matches the first URL; and

in response to the determination, allocating resources of the return channel for the user access point based on the stored usage history associated with the first URL.

15. The method of claim 14, further comprising:

storing usage history associated with each of a plurality of URLs including the first URL;

receiving a request for a third URL from the user access point;

determining that the third URL does not match any of the plurality of URLs; and

in response to the determination that the third URL does not match any of the plurality of the URLs, allocating resources of the return channel for the user access point based on usage history of a group of one or more URLs of the plurality of URLs.

16. The method of claim 15, wherein the group of one or more URLs have the same domain as that of the third URL.

17. The method of claim 14, further comprising updating the stored usage history associated with the first URL based on resources of the return channel used by the user access point following the request.

18. The method of claim 14, wherein the allocated resources of the return channel vary over a time frame.

19. The method of claim 14, wherein the usage history is biased toward recent requests.