USRE39017E1 - Internet upstream request compression - Google Patents

Internet upstream request compression Download PDF

Info

Publication number
USRE39017E1
USRE39017E1 US09/927,778 US92777801A USRE39017E US RE39017 E1 USRE39017 E1 US RE39017E1 US 92777801 A US92777801 A US 92777801A US RE39017 E USRE39017 E US RE39017E
Authority
US
United States
Prior art keywords
upstream
request
internet
information
processor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
US09/927,778
Inventor
Joseph Smallcomb
Ray Allen Daniel
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ITT Manufacturing Enterprises LLC
RPX Corp
Original Assignee
ITT Manufacturing Enterprises LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ITT Manufacturing Enterprises LLC filed Critical ITT Manufacturing Enterprises LLC
Priority to US09/927,778 priority Critical patent/USRE39017E1/en
Application granted granted Critical
Publication of USRE39017E1 publication Critical patent/USRE39017E1/en
Assigned to RPX CORPORATION reassignment RPX CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: Exelis Inc.
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H03—ELECTRONIC CIRCUITRY
    • H03M—CODING; DECODING; CODE CONVERSION IN GENERAL
    • H03M7/00—Conversion of a code where information is represented by a given sequence or number of digits to a code where the same, similar or subset of information is represented by a different sequence or number of digits
    • H03M7/30—Compression; Expansion; Suppression of unnecessary data, e.g. redundancy reduction
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols

Definitions

  • This invention relates to interactive information requests over the internet.
  • a client To gain access to the internet, a client (user) will typically login into an Internet Service Provider (ISP) via a telephone or ISDN modem.
  • ISP Internet Service Provider
  • This connection is typically a medium data rate (i.e., 9.6 to 28.8 kbps), symmetrical connection.
  • the client is typically searching for information, which leads to asymmetric communications.
  • a client (user) requesting a file download will send a small upstream request (e.g., 200 bytes) but receive a large file (e.g. 200 kbytes) in return from the server.
  • the downstream channel i.e., return link
  • the bottleneck i.e., return link
  • the typical volume of downstream data to upstream data ratio is from 10:1 to 20:1.
  • asymmetrical channel services are being deployed (e.g., satellite broadcast, cable modems, ADSL, etc.) to take advantage of this ratio and reduce this downstream bottleneck.
  • These services typically increase the downstream channel capacity by using a media with wider bandwidth (e.g., co-axial cable), and maintain or allocate a smaller bandwidth connection for the upstream user request channel.
  • a media with wider bandwidth e.g., co-axial cable
  • an upstream channel path independent of the downstream channel path, is utilized.
  • the Internet is a packet switch network, where the defacto protocol standard is TCP/IP.
  • IP Internet Protocol
  • IP provides the basic addressing scheme for internet routing (where the information goes).
  • TCP Transmission Control Protocol
  • TCP is very robust protocol designed for error-free bulk data transfer and error detection and correction.
  • PPP PPP or SLIP
  • ISP ISP
  • WWW World Wide Web
  • HTTP HyperText Transfer Protocol
  • a user sends an HTTP request for a Web Page to a particular server on the internet and the server responds with requested information.
  • This transaction takes several phases (i.e., Connect, Request, Response, Close) to complete.
  • the requested information from the server is most commonly an HTTP file which references graphical images, audio files, and/or additional text.
  • the browser will then automatically request the additional information (unless the user has manually selected to filter out certain high bandwidth file requests from being made). It is not uncommon for an initial request of a web page to trigger 20 more requests which are required to complete the transaction and build the image seen through the browser.
  • the upstream traffic between the Client and the Upstream Gateway is compressed and reduced with the bulk of the internet communication performed at the Upstream and (in some cases) Downstream Gateway.
  • This allows more users to be placed on multiple access upstream channels and/or reduce the user cost on a charge-by-the-byte upstream channel.
  • This invention exploits the architecture of the Indirect Network Connection that is utilized in an asymmetrical internet connection as well as the characteristic that the upstream channel from the Client to the Upstream Gateway is a point-to-point connection.
  • This invention utilizes four types of compression to reduce upstream channel traffic so that the ratio of downstream to upstream channel traffic is increased significantly beyond the 20:1 ratio that is now experienced:
  • the typical browser request contains ASCII symbols with characters and patterns that are commonly repeated. For example, in the request: http://www.cnn.com/SPORTS/FOOTBALL/college/96/news.usarate.html “/” and “.” are the most common characters. Patterns like “http://”, “www”, “.com”, and “.html” are also common.
  • a simple statistical compression or linear predication scheme could reduce the number of bytes required for a request and would be appropriate for this real-time compression application.
  • the packet overhead of TCP and IP are not necessarily required.
  • Software running at the Client site would operate beneath the browser to bypass the TCP/IP packet formation after the initial connection is established.
  • the Upstream Gateway would then take the requests and add the TCP/IP overhead prior to transmission to the Internet.
  • a large database could be implemented at the Upstream Gateway which stores a Client's previous data requests.
  • Software running at the Client site would operate beneath the browser to send a short address reference message to the Upstream Gateway to indicate a previously requested site instead of sending an entire request sequence.
  • the Upstream Gateway in turn, would look up the short address reference in the database for that Client in order to send out the complete data request to the Internet. This could be implemented with a “Go back “N” requests” scheme or a Bookmark scheme similar to those on a typical browser.
  • the gateways could be programmed to receive the first request response from a server and automatically make all of the subsequent file requests for the Client. Each of the requested files would then be downloaded to the Client on the downstream channel as they are received. This makes it possible to have only one data request to be sent by the Client on the upstream channel (instead of a multitude) to assemble a web page.
  • the gateways could also handle the lower HTTP level of connection, request, response, and close messages with the Internet so that the Client would not be required to send all of these separate messages on the upstream channel.
  • the Upstream and Downstream Gateways could operate in concert for this service, or they could operate independently with one gateway or the other managing the proxy requests.
  • the compression management software running at the Client site would operate beneath the browser to manage these compression functions.
  • the compression management software could send a message to the gateways to indicate this and only the desired files would be automatically requested by the gateways.
  • FIG. 1 (prior art) is a diagrammatic illustration of a typical indirect internet connection
  • FIG. 2 is a block diagram of the client processor for internet browsing with a compressed upstream channel
  • FIG. 3 is a block diagram illustrating a first compression technique incorporated in the invention
  • FIG. 4 is a block diagram of a second compression technique incorporating the invention
  • FIG. 5 is a block diagram illustrating a third compression technique incorporated in the invention.
  • FIG. 6 is a block diagram illustrating a fourth compression technique incorporated in the invention.
  • FIG. 1 illustrates all the basic elements of an Indirect Internet Connection where the upstream and downstream data paths are asymmetric and different in their implementation.
  • a Client i.e., user
  • ( 1 ) requests information from a Server 7 (e.g., home page) somewhere on the internet. It sends the request on the Upstream Channel ( 2 ) to the Upstream Gateway.
  • the Upstream Gateway forwards the request onto the Internet ( 5 ) over a higher speed link ( 4 ) and it eventually arrives at the addressed server ( 7 ).
  • Server 7 responds to the request by addressing the Downstream Gateway ( 10 ) and the Client ( 1 ).
  • FIG. 2 shows an exploded view of the Client Processor CP and the relevant elements that would be needed for internet web browsing with a compressed upstream channel (for simplicity, only the upstream path is shown) according to the invention.
  • the User ( 11 ) initiates an information request to the Internet Browser ( 13 ) through the User Interface ( 12 ) (e.g., a query to a web page).
  • the Internet Browser ( 13 ) sends a request message to the appropriate drivers (e.g. TCP/IP, PPP, SLP) of the operating system (e.g. Windows 95, Solaris, MacOS) where the request message is formatted for transportation to and on the internet.
  • drivers e.g. TCP/IP, PPP, SLP
  • the operating system e.g. Windows 95, Solaris, MacOS
  • the Custom Compression Application (the subject of this invention) intercepts the request message and performs the appropriate compression techniques (explained below) prior to delivery to the H/W Interface Driver ( 16 ), Communication Interface ( 17 ) and the Communication Path ( 18 ) for transmission to the Upstream Gateway ( 23 ) (FIG. 3 ), where the request message decompression takes place.
  • FIG. 3 shows a description of the first compression technique where the ASCII message format is compressed.
  • a software application will run on the Client ( 20 ), “below” the internet browser, so that all messages sent from the browser will pass through the compression software and the ASCII text strings will be reduced by efficiently coding the repeating or redundant characters real-time or near real-time (using a simple statistical compression or linear predication scheme), then passed on to the drivers that transmit the message on the Communication Channel ( 12 ) to the Upstream Gateway ( 23 ).
  • the complementary software running at the Upstream Gateway ( 23 ) receives the messages from the Communication Channel ( 22 ) and reconstructs the full ASCII text string prior to delivery to transmission on the Communication Channel ( 24 ) to the Internet.
  • FIG. 4 shows a description of the second compression technique where the TCP and IP packetizing and overhead is added at the Upstream Gateway ( 23 ′).
  • a software application will run on the Client ( 20 ′), “below” the internet browser, so that all messages sent from the browser will be intercepted by the compression software and the unnecessary TCP/IP overhead are not added.
  • the complementary software running at the Upstream Gateway ( 23 ′) receives the messages from the Communication Channel ( 22 ) and reads (then removes) the client ID so that the appropriate TCP/IP overhead can then be added prior to delivery to transmission on the Communication Channel ( 24 ) to the Internet.
  • FIG. 5 shows a description of the third compression technique where a short web address reference message is sent to the Upstream Gateway ( 23 ′′).
  • a software application will run on the Client ( 20 ′′), “below” the internet browser, which follows the user's web browsing and notes frequently visited sites and also bookmarks that the user enters.
  • the software can then exchange information with the Upstream Gateway ( 23 ′′) so that a web site address is stored in a user profile database, and referenced by the Client software by a short coded reference message from the Client ( 20 ′′) to the Upstream Gateway ( 23 ′′) instead of the complete web site address.
  • the user could manually set up a number of sites that are to be referenced using this shortcut.
  • FIG. 6 illustrates the fourth compression technique where the Upstream Gateway ( 23 ′′′) requests all additional web page graphics, images, etc. automatically.
  • a software application will run on the Client ( 20 ′′′), “below” the internet browser, so that the browser is inhibited from automatically requesting any subsequent graphics or image files that may be referenced in the initial web page HTML file response.
  • the Upstream Gateway ( 23 ′′′) will receive a copy of the initial web page HTML file and make all of the subsequent file requests for the Client ( 20 ′′′) thereby acting as an internet proxy for the Client ( 20 ′′′).
  • a setting could be sent from the Client ( 20 ′′′) to the Upstream Gateway ( 23 ′′′) which would set up the Upstream Gateway software to not make the requests.
  • the upstream channel traffic from a Client can be significantly reduced, increasing the number of users on a multiple access upstream channel or reducing the required bandwidth for a single user. This is accomplished by:
  • One or more of these techniques may be used to “compress” data traffic on the upstream request channel.

Abstract

Interactive internet activities are a very popular means for gathering information for business, personal, medical, entertainment and other purposes. Most internet interaction is asymmetrical in nature in that a client's requests for information are much smaller (in data size) than the resulting information delivered by the server. Although the client/internet link is inherently asymmetrical, there remains a great deal of interaction and overhead required between the client and the server that increases the bandwidth needs for the client's upstream request channel. There are many advantages to reducing this upstream traffic volume and thereby making the internet interaction even more asymmetrical. Such compression of request data could allow more clients to utilize a single upstream data path instead of separate paths.

Description

TECHNICAL FIELD
This invention relates to interactive information requests over the internet.
BACKGROUND ART
To gain access to the internet, a client (user) will typically login into an Internet Service Provider (ISP) via a telephone or ISDN modem. This connection is typically a medium data rate (i.e., 9.6 to 28.8 kbps), symmetrical connection. However, the client is typically searching for information, which leads to asymmetric communications. For example, a client (user) requesting a file download will send a small upstream request (e.g., 200 bytes) but receive a large file (e.g. 200 kbytes) in return from the server. In these types of connection the downstream channel (i.e., return link) is the bottleneck.
The typical volume of downstream data to upstream data ratio is from 10:1 to 20:1. Currently, asymmetrical channel services are being deployed (e.g., satellite broadcast, cable modems, ADSL, etc.) to take advantage of this ratio and reduce this downstream bottleneck. These services typically increase the downstream channel capacity by using a media with wider bandwidth (e.g., co-axial cable), and maintain or allocate a smaller bandwidth connection for the upstream user request channel. In some cases (such as satellite broadcast), an upstream channel path, independent of the downstream channel path, is utilized.
The Internet is a packet switch network, where the defacto protocol standard is TCP/IP. The Internet Protocol (IP) provides the basic addressing scheme for internet routing (where the information goes). Transmission Control Protocol (TCP) is very robust protocol designed for error-free bulk data transfer and error detection and correction. On top of TCP/IP, an additional serial interface, protocol (e.g., PPP or SLIP) is used for connection with an ISP. From the standpoint of upstream channel efficiency, a typical internet request has a high degree of packet overhead to accommodate the layers of protocol, the error correction, and the data coding scheme.
Browsing on the World Wide Web (WWW) (one of the most popular activities on the internet) also leads to inefficient use of the upstream channel. This browsing is based on the HyperText Transfer Protocol (HTTP). Typically, a user sends an HTTP request for a Web Page to a particular server on the internet and the server responds with requested information. This transaction takes several phases (i.e., Connect, Request, Response, Close) to complete. In addition, the requested information from the server is most commonly an HTTP file which references graphical images, audio files, and/or additional text. The browser will then automatically request the additional information (unless the user has manually selected to filter out certain high bandwidth file requests from being made). It is not uncommon for an initial request of a web page to trigger 20 more requests which are required to complete the transaction and build the image seen through the browser.
THE PRESENT INVENTION
Although the implementation of asymmetrical internet connections has made internet interaction more efficient, there is yet more compression that can occur to make the upstream channel even more compact.
In this invention, the upstream traffic between the Client and the Upstream Gateway is compressed and reduced with the bulk of the internet communication performed at the Upstream and (in some cases) Downstream Gateway. This allows more users to be placed on multiple access upstream channels and/or reduce the user cost on a charge-by-the-byte upstream channel. This invention exploits the architecture of the Indirect Network Connection that is utilized in an asymmetrical internet connection as well as the characteristic that the upstream channel from the Client to the Upstream Gateway is a point-to-point connection.
This invention utilizes four types of compression to reduce upstream channel traffic so that the ratio of downstream to upstream channel traffic is increased significantly beyond the 20:1 ratio that is now experienced:
(1) Format compression of request packets.
The typical browser request contains ASCII symbols with characters and patterns that are commonly repeated. For example, in the request:
http://www.cnn.com/SPORTS/FOOTBALL/college/96/news.usarate.html
“/” and “.” are the most common characters. Patterns like “http://”, “www”, “.com”, and “.html” are also common. A simple statistical compression or linear predication scheme could reduce the number of bytes required for a request and would be appropriate for this real-time compression application.
Software running at the Client site could operate beneath the browser to compress the ASCII text requests prior to their TCP/IP formatting and the full, uncompressed, request would be regenerated at the Upstream Gateway.
(2) Perform TCP and IP packetizinq at the Upstream Gateway rather than at the Client:
Since the upstream channel between the Client and the Upstream Gateway is a point-to-point link, the packet overhead of TCP and IP are not necessarily required. Software running at the Client site would operate beneath the browser to bypass the TCP/IP packet formation after the initial connection is established. The Upstream Gateway would then take the requests and add the TCP/IP overhead prior to transmission to the Internet.
(3) Keep a User Profile at the Upstream Gateway:
A large database could be implemented at the Upstream Gateway which stores a Client's previous data requests. Software running at the Client site would operate beneath the browser to send a short address reference message to the Upstream Gateway to indicate a previously requested site instead of sending an entire request sequence. The Upstream Gateway, in turn, would look up the short address reference in the database for that Client in order to send out the complete data request to the Internet. This could be implemented with a “Go back “N” requests” scheme or a Bookmark scheme similar to those on a typical browser.
(4) Automatically generate additional HTTP requests:
The fact that a single web page likely requires multiple data requests from the Client is the largest contributor to upstream data traffic. Instead of the Client system sending the automatic subsequent requests for additional data (referenced by the initial HTTP file delivered from the Server), the gateways could be programmed to receive the first request response from a server and automatically make all of the subsequent file requests for the Client. Each of the requested files would then be downloaded to the Client on the downstream channel as they are received. This makes it possible to have only one data request to be sent by the Client on the upstream channel (instead of a multitude) to assemble a web page.
In addition to the higher HTTP level compression, the gateways could also handle the lower HTTP level of connection, request, response, and close messages with the Internet so that the Client would not be required to send all of these separate messages on the upstream channel.
The Upstream and Downstream Gateways could operate in concert for this service, or they could operate independently with one gateway or the other managing the proxy requests.
Software running at the Client site would operate beneath the browser to manage these compression functions. In addition, should the Client wish to filter out the request of certain files (e.g. to speed up their internet session or to reduce downstream bandwidth), the compression management software could send a message to the gateways to indicate this and only the desired files would be automatically requested by the gateways.
BRIEF DESCRIPTION OF THE DRAWINGS
The above and other objects, advantages and features of the invention will become more clear when considered with the following description and accompanying drawings, wherein:
FIG. 1 (prior art) is a diagrammatic illustration of a typical indirect internet connection,
FIG. 2 is a block diagram of the client processor for internet browsing with a compressed upstream channel,
FIG. 3 is a block diagram illustrating a first compression technique incorporated in the invention,
FIG. 4 is a block diagram of a second compression technique incorporating the invention,
FIG. 5 is a block diagram illustrating a third compression technique incorporated in the invention, and
FIG. 6 is a block diagram illustrating a fourth compression technique incorporated in the invention.
 DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 illustrates all the basic elements of an Indirect Internet Connection where the upstream and downstream data paths are asymmetric and different in their implementation. A Client (i.e., user) (1) requests information from a Server 7 (e.g., home page) somewhere on the internet. It sends the request on the Upstream Channel (2) to the Upstream Gateway. The Upstream Gateway forwards the request onto the Internet (5) over a higher speed link (4) and it eventually arrives at the addressed server (7). Server 7 responds to the request by addressing the Downstream Gateway (10) and the Client (1). The response arrives at the Downstream Gateway 10 from the Internet (5) over a high speed link (9) and the Downstream Gateway forwards the request to the Client over the Downstream Channel (11). (In most internet service configurations, the two gateways are typically co-located (e.g., dial-up ISP, cable headend, etc.), but it is also possible for the two gateways (and associated upstream and downstream paths) to be separate and independent (e.g., satellite broadcast downstream, telephone line upstream).) FIG. 2 shows an exploded view of the Client Processor CP and the relevant elements that would be needed for internet web browsing with a compressed upstream channel (for simplicity, only the upstream path is shown) according to the invention. The User (11) initiates an information request to the Internet Browser (13) through the User Interface (12) (e.g., a query to a web page). The Internet Browser (13) sends a request message to the appropriate drivers (e.g. TCP/IP, PPP, SLP) of the operating system (e.g. Windows 95, Solaris, MacOS) where the request message is formatted for transportation to and on the internet. For the Internet Drivers (14), the Custom Compression Application (15) (the subject of this invention) intercepts the request message and performs the appropriate compression techniques (explained below) prior to delivery to the H/W Interface Driver (16), Communication Interface (17) and the Communication Path (18) for transmission to the Upstream Gateway (23) (FIG. 3), where the request message decompression takes place.
FIG. 3 shows a description of the first compression technique where the ASCII message format is compressed. A software application will run on the Client (20), “below” the internet browser, so that all messages sent from the browser will pass through the compression software and the ASCII text strings will be reduced by efficiently coding the repeating or redundant characters real-time or near real-time (using a simple statistical compression or linear predication scheme), then passed on to the drivers that transmit the message on the Communication Channel (12) to the Upstream Gateway (23). The complementary software running at the Upstream Gateway (23) receives the messages from the Communication Channel (22) and reconstructs the full ASCII text string prior to delivery to transmission on the Communication Channel (24) to the Internet.
FIG. 4 shows a description of the second compression technique where the TCP and IP packetizing and overhead is added at the Upstream Gateway (23′). A software application will run on the Client (20′), “below” the internet browser, so that all messages sent from the browser will be intercepted by the compression software and the unnecessary TCP/IP overhead are not added. The complementary software running at the Upstream Gateway (23′) receives the messages from the Communication Channel (22) and reads (then removes) the client ID so that the appropriate TCP/IP overhead can then be added prior to delivery to transmission on the Communication Channel (24) to the Internet.
FIG. 5 shows a description of the third compression technique where a short web address reference message is sent to the Upstream Gateway (23″). A software application will run on the Client (20″), “below” the internet browser, which follows the user's web browsing and notes frequently visited sites and also bookmarks that the user enters. The software can then exchange information with the Upstream Gateway (23″) so that a web site address is stored in a user profile database, and referenced by the Client software by a short coded reference message from the Client (20″) to the Upstream Gateway (23″) instead of the complete web site address. In addition, the user could manually set up a number of sites that are to be referenced using this shortcut.
FIG. 6 illustrates the fourth compression technique where the Upstream Gateway (23′″) requests all additional web page graphics, images, etc. automatically. A software application will run on the Client (20′″), “below” the internet browser, so that the browser is inhibited from automatically requesting any subsequent graphics or image files that may be referenced in the initial web page HTML file response. Instead, when a web page is addressed for delivery by the Client (20′″), the Upstream Gateway (23′″) will receive a copy of the initial web page HTML file and make all of the subsequent file requests for the Client (20′″) thereby acting as an internet proxy for the Client (20′″). Should the user not wish for the subsequent files to be requested (e.g. in order to save downstream bandwidth), a setting could be sent from the Client (20′″) to the Upstream Gateway (23′″) which would set up the Upstream Gateway software to not make the requests.
FEATURES OF THE INVENTION
The upstream channel traffic from a Client can be significantly reduced, increasing the number of users on a multiple access upstream channel or reducing the required bandwidth for a single user. This is accomplished by:
    • 1. Compressing the data between the Client and Upstream Gateway.
    • 2. Having the Upstream Gateway perform protocol overhead functions.
    • 3. Keeping a user profile at the Upstream Gateway.
    • 4. Automatically generating new request at the gateway for the client.
One or more of these techniques may be used to “compress” data traffic on the upstream request channel.
While the invention has been described in relation to preferred embodiments of the invention, it will be appreciated that other embodiments, adaptations and modifications of the invention will be apparent to those skilled in the art.

Claims (57)

1. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) means for interfacing with the user,
(b) an internet browser module connected to said interfacing means,
(c) internet driver means connected to said internet browser means,
(d) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway includes means for storing a profile of the users connected thereto.
2. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) means for interfacing with the user,
(b) an internet browser module connected to said interfacing means,
(c) internet driver means connected to said internet browser means,
(d) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway is adapted to perform protocol overhead functions and includes means for storing a profile of the users connected thereto.
3. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) means for interfacing with the user,
(b) an internet browser module, connected to said interfacing means,
(c) internet driver means connected to said internet browser means,
(d) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway includes means for automatically generating a new data request for a given user.
4. The information distribution system defined in claim 2 wherein said upstream gateway includes means for automatically generating a new data request for a given user.
5. The information distribution system defined in claim 1 wherein said upstream gateway includes means for automatically generating a new data request for a given user.
6. A method of reducing upstream request data from a client to request information from a server, the method comprising:
receiving an upstream request;
compressing the upstream request data using an internet driver, thereby generating a compressed upstream request; and
outputting the compressed upstream request using a connection-oriented communication protocol, wherein the compressed upstream request is output on an upstream channel and the requested information is received on a downstream channel having a substantially larger capacity than the upstream channel, wherein a ratio of downstream channel traffic to upstream channel traffic is increased beyond a 20:1 ratio.
7. The method of claim 6, wherein the upstream request is compressed using format compression.
8. The method of claim 7, wherein said format compression is a statistical compression.
9. The method of claim 7, wherein said format compression is a linear prediction compression.
10. The method of claim 6, wherein the upstream request is compressed by intercepting said upstream request prior to the addition of network communications protocol information, and generating the compressed upstream request that does not include network communications protocol information.
11. The method of claim 10, wherein said communications protocol is TCP/IP.
12. The method of claim 6, wherein the upstream request is compressed by replacing a previously used string with a short coded reference.
13. The method of claim 12, wherein said previously used string is a web site address.
14. The method of claim 6, further comprising reducing the number of subsequent upstream requests output from said client.
15. The method of claim 14, wherein said reducing the number of subsequent upstream requests is performed by inhibiting generation of automatic upstream requests based on embedded references contained within the information received in response to outputting the compressed upstream request.
16. The method of claim 14, wherein said client provides criteria to a gateway for generating requests based on the embedded references contained within the information received in response to outputting the compressed upstream request.
17. A method of reducing upstream request data from a client to request information from a server, the method comprising:
receiving a compressed upstream request according to a connection-oriented communication protocol, the compressed upstream request being compressed using an internet driver, wherein a ratio of downstream channel traffic to upstream channel traffic exceeds a ratio of 20:1;
decompressing said compressed upstream request to reconstruct an upstream request from the client;
outputting the upstream request upon a communications network; and
automatically generating a new data request for a given user.
18. The method of claim 17, wherein the compressed upstream request is decompressed using format decompression.
19. The method of claim 18, wherein said format decompression is a statistical decompression.
20. The method of claim 18, wherein said format decompression is a linear prediction decompression.
21. The method of claim 17, wherein the compressed upstream request is decompressed by adding network communications protocol information to the compressed upstream request.
22. The method of claim 21, wherein said communications protocol is TCP/IP.
23. The method of claim 17, wherein the compressed upstream request is decompressed by replacing a short coded reference within the compressed upstream request with a predetermined string.
24. The method of claim 23, wherein said predetermined string is a web site address contained in a previously received upstream request.
25. The method of claim 17, further comprising:
receiving the information from the server in response to outputting the upstream request;
generating a request for additional information based on a reference identified within the received information;
outputting the generated request upon said communications network.
26. The method as defined in claim 25, wherein said upstream request is an HTTP request for a web page, the information received from the server is the requested web page, and the additional information is a file referenced by the web page.
27. The method of claim 26, wherein generating the request for the file referenced by the web page is controlled by criteria provided by said client.
28. The method of claim 17, wherein said decompressing is performed by an upstream gateway having stored therein a profile of users connected to the upstream gateway.
29. A client processor for requesting information from a server in a communications network, the client processor comprising a compression unit configured to receive an upstream request, to compress the received request using an internet driver, thereby generating a compressed upstream request, and to output the compressed upstream request using a connection-oriented communication protocol, wherein client processor is connected to an upstream and a downstream channel, and the compressed upstream request is output on the upstream channel and the requested information is received on the downstream channel and a ratio of downstream traffic to upstream traffic is increased beyond a 20:1 ratio.
30. The client processor of claim 29, wherein the compression unit by compressing the upstream request reduces traffic on the upstream channel, thereby increasing a ratio of downstream to upstream traffic beyond a ratio of 20:1.
31. The client processor of claim 30, wherein the downstream channel has a substantially larger capacity than the upstream channel.
32. The client processor of claim 30, wherein the compression unit compresses the upstream request by using format compression.
33. The client processor of claim 32, wherein said format compression is a statistical compression.
34. The client processor of claim 32, wherein said format compression is a linear prediction compression.
35. The client processor of claim 30, wherein the compression unit compresses the upstream request by intercepting said upstream request prior to the addition of network communications protocol information and generating the compressed request in a manner that the compressed request does not include network communications protocol information.
36. The client processor of claim 35, wherein said communications protocol is a TCP/IP.
37. The client processor of claim 30, wherein the compression unit compresses the upstream request by replacing a string within the upstream request with a short coded reference.
38. The client processor of claim 37, wherein said predetermined string is a web site address contained in a previously output upstream request.
39. The client processor of claim 30, wherein the compression unit reduces the number of subsequent requests output from said client.
40. The client processor of claim 39, wherein the compression unit reduces the number of subsequent upstream requests by inhibiting generation of automatic upstream requests based on embedded references contained within the information received in response to outputting the compressed upstream request.
41. The client processor of claim 39, wherein said client provides criteria to a gateway for generating requests based on the embedded references contained within the information received in response to outputting the compressed upstream request.
42. An upstream processor coupled to a client processor via an upstream channel and to a server via a communication network, the upstream processor comprising a decompression unit configured to receive from the client processor a compressed upstream request for information from the server, the compressed upstream request being compressed using an internet driver, wherein a ratio of downstream channel traffic to upstream channel traffic exceeds a ratio of 20:1, and to decompress the compressed upstream request to reconstruct an upstream request from the client, wherein the decompression unit is configured to receive the compressed upstream request according to a connection-oriented communication protocol, wherein said decompression unit is configured to automatically generate a new data request for a given user.
43. The upstream processor of claim 42, wherein the decompression unit decompresses the compressed upstream request by using format decompression.
44. The upstream processor of claim 43, wherein said format decompression is a statistical decompression.
45. The upstream processor of claim 43, wherein said format decompression is a linear prediction decompression.
46. The upstream processor of claim 42, wherein the decompression unit decompresses the compressed upstream request by adding network communications protocol information to the compressed request.
47. The upstream processor of claim 46, wherein said communications protocol is TCP/IP.
48. The upstream processor of claim 42, wherein the decompression unit decompresses the compressed upstream request by replacing a short coded reference within the compressed upstream request with a predetermined string.
49. The upstream processor of claim 48, further comprising a user profile database having recorded therein the predetermined string in association with the short coded reference.
50. The upstream processor of claim 48, wherein said predetermined string is a web site address contained in a previously received upstream request.
51. The upstream processor of claim 42, the decompression unit comprising:
means for receiving the information from the server in response to outputting the upstream request;
means for generating a request for additional information based on a reference within the received information; and
means for outputting the generated request upon said communications network.
52. The upstream processor of claim 51, wherein said upstream request is an HTTP request for a web page, the information received from the server is the requested web page, and the additional information is a file referenced by the web page.
53. The upstream processor of claim 51, wherein the means for generating the request for the file referenced by the web page is controlled by criteria provided by said client.
54. The upstream processor of claim 42, further comprising a storage unit having stored therein a profile of users connected to the upstream gateway.
55. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) an internet browser module,
(b) internet driver means connected to said internet browser module,
(c) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway includes means for storing a profile of the users connected thereto.
56. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) an internet browser module,
(b) internet driver means connected to said internet browser module,
(c) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway is adapted to perform protocol overhead functions and includes means for storing a profile of the users connected thereto.
57. In an interactive internet information distribution system in which user stations are connected to the internet by an internet server through an upstream gateway for transmission of information requests to said internet server and downstream gateways for transmission of information from the internet server to the user stations, the improvement wherein each user station includes a processor, said processor including:
(a) an internet browser module,
(b) internet driver means connected to said internet browser module,
(c) compression module connected to said internet driver means for reducing the upstream traffic whereby the ratio of downstream to upstream channel traffic is increased beyond a 20:1 ratio and wherein said upstream gateway includes means for automatically generating a new data request for a given user.
US09/927,778 1997-02-14 2001-08-15 Internet upstream request compression Expired - Lifetime USRE39017E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US09/927,778 USRE39017E1 (en) 1997-02-14 2001-08-15 Internet upstream request compression

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/799,352 US5938737A (en) 1997-02-14 1997-02-14 Internet upstream request compression
US09/927,778 USRE39017E1 (en) 1997-02-14 2001-08-15 Internet upstream request compression

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US08/799,352 Reissue US5938737A (en) 1997-02-14 1997-02-14 Internet upstream request compression

Publications (1)

Publication Number Publication Date
USRE39017E1 true USRE39017E1 (en) 2006-03-14

Family

ID=25175671

Family Applications (2)

Application Number Title Priority Date Filing Date
US08/799,352 Ceased US5938737A (en) 1997-02-14 1997-02-14 Internet upstream request compression
US09/927,778 Expired - Lifetime USRE39017E1 (en) 1997-02-14 2001-08-15 Internet upstream request compression

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US08/799,352 Ceased US5938737A (en) 1997-02-14 1997-02-14 Internet upstream request compression

Country Status (6)

Country Link
US (2) US5938737A (en)
EP (1) EP1015991A1 (en)
JP (1) JP2001511984A (en)
AU (1) AU733295B2 (en)
CA (1) CA2278300A1 (en)
WO (1) WO1998036362A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090231998A1 (en) * 2008-03-17 2009-09-17 Microsoft Corporation Selective filtering of network traffic requests
US20160366241A1 (en) * 2012-11-16 2016-12-15 International Business Machines Corporation Saving bandwidth in transmission of compressed data

Families Citing this family (46)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6339787B1 (en) * 1995-11-30 2002-01-15 Stampede Technologies, Inc. Apparatus and method for increasing speed in a network file/object oriented server/client system
US6226642B1 (en) 1997-09-11 2001-05-01 International Business Machines Corporation Content modification of internet web pages for a television class display
US6493766B1 (en) * 1998-06-30 2002-12-10 Motorola, Inc. Method, client device, server and article of manufacture for compressing universal resource identifiers using left/right string substitution
US6624761B2 (en) 1998-12-11 2003-09-23 Realtime Data, Llc Content independent data compression method and system
US6601104B1 (en) 1999-03-11 2003-07-29 Realtime Data Llc System and methods for accelerated data storage and retrieval
US6604158B1 (en) 1999-03-11 2003-08-05 Realtime Data, Llc System and methods for accelerated data storage and retrieval
US6345307B1 (en) * 1999-04-30 2002-02-05 General Instrument Corporation Method and apparatus for compressing hypertext transfer protocol (HTTP) messages
WO2000072155A1 (en) * 1999-05-20 2000-11-30 Motorola Inc. Method for establishing communication in a packet network
JP3478200B2 (en) * 1999-09-17 2003-12-15 日本電気株式会社 Two-way communication system between server and client
IL133039A (en) 1999-11-18 2007-12-03 Eyeblaster Inc Full duplex re-transmitter
US6449658B1 (en) * 1999-11-18 2002-09-10 Quikcat.Com, Inc. Method and apparatus for accelerating data through communication networks
US7068381B1 (en) 2000-02-02 2006-06-27 Raja Tuli Portable high speed internet access device
US20020115477A1 (en) * 2001-02-13 2002-08-22 Raja Singh Portable high speed internet access device with scrolling
US7356570B1 (en) 2000-08-29 2008-04-08 Raja Tuli Portable high speed communication device
US7023572B2 (en) 2000-02-02 2006-04-04 Raja Singh Tuli Portable high speed internet access device
US7289244B2 (en) 2000-02-02 2007-10-30 Raja Singh Tuli Portable high speed internet access device
US6633314B1 (en) 2000-02-02 2003-10-14 Raja Tuli Portable high speed internet device integrating cellular telephone and palm top computer
US20020030843A1 (en) * 2000-02-02 2002-03-14 Tuli Raja Singh Portable high speed internet access device
US20010047473A1 (en) 2000-02-03 2001-11-29 Realtime Data, Llc Systems and methods for computer initialization
US6941382B1 (en) 2000-02-07 2005-09-06 Raja Tuli Portable high speed internet or desktop device
US6874009B1 (en) 2000-02-16 2005-03-29 Raja Tuli Portable high speed internet device with user fees
US6772026B2 (en) 2000-04-05 2004-08-03 Therics, Inc. System and method for rapidly customizing design, manufacture and/or selection of biomedical devices
US7120676B2 (en) * 2000-04-28 2006-10-10 Agilent Technologies, Inc. Transaction configuration system and method for transaction-based automated testing
US7114008B2 (en) 2000-06-23 2006-09-26 Cloudshield Technologies, Inc. Edge adapter architecture apparatus and method
US6728785B1 (en) 2000-06-23 2004-04-27 Cloudshield Technologies, Inc. System and method for dynamic compression of data
US8204082B2 (en) 2000-06-23 2012-06-19 Cloudshield Technologies, Inc. Transparent provisioning of services over a network
US7032031B2 (en) * 2000-06-23 2006-04-18 Cloudshield Technologies, Inc. Edge adapter apparatus and method
US6829654B1 (en) * 2000-06-23 2004-12-07 Cloudshield Technologies, Inc. Apparatus and method for virtual edge placement of web sites
US7003555B1 (en) * 2000-06-23 2006-02-21 Cloudshield Technologies, Inc. Apparatus and method for domain name resolution
US9444785B2 (en) 2000-06-23 2016-09-13 Cloudshield Technologies, Inc. Transparent provisioning of network access to an application
US7191211B2 (en) 2000-10-03 2007-03-13 Raja Tuli Portable high speed internet access device priority protocol
US6842777B1 (en) 2000-10-03 2005-01-11 Raja Singh Tuli Methods and apparatuses for simultaneous access by multiple remote devices
US9143546B2 (en) 2000-10-03 2015-09-22 Realtime Data Llc System and method for data feed acceleration and encryption
US8692695B2 (en) 2000-10-03 2014-04-08 Realtime Data, Llc Methods for encoding and decoding data
US6915327B1 (en) 2000-10-30 2005-07-05 Raja Singh Tuli Portable high speed communication device peripheral connectivity
US6976075B2 (en) * 2000-12-08 2005-12-13 Clarinet Systems, Inc. System uses communication interface for configuring a simplified single header packet received from a PDA into multiple headers packet before transmitting to destination device
US6928461B2 (en) 2001-01-24 2005-08-09 Raja Singh Tuli Portable high speed internet access device with encryption
US7386046B2 (en) 2001-02-13 2008-06-10 Realtime Data Llc Bandwidth sensitive data compression and decompression
US7210022B2 (en) * 2001-05-15 2007-04-24 Cloudshield Technologies, Inc. Apparatus and method for interconnecting a processor to co-processors using a shared memory as the communication interface
US7082502B2 (en) * 2001-05-15 2006-07-25 Cloudshield Technologies, Inc. Apparatus and method for interfacing with a high speed bi-directional network using a shared memory to store packet data
US20030078964A1 (en) * 2001-06-04 2003-04-24 Nct Group, Inc. System and method for reducing the time to deliver information from a communications network to a user
US7372871B2 (en) * 2002-03-27 2008-05-13 Intel Corporation Techniques to reduce information loss and translation costs in a system populated with data sources and sinks communicating with multiple data representations
US8176428B2 (en) 2002-12-03 2012-05-08 Datawind Net Access Corporation Portable internet access device back page cache
US7796526B2 (en) * 2003-10-31 2010-09-14 Acterna Versatile communication network test apparatus and methods
US20050144648A1 (en) * 2003-10-31 2005-06-30 Gotwals Michael D. Communication network analysis apparatus with internetwork connectivity
US7403486B2 (en) * 2003-10-31 2008-07-22 Acterna Signal level measurement and data connection quality analysis apparatus and methods

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5136291A (en) * 1990-11-30 1992-08-04 Unisys Corporation Transmitting binary data files using electronic mail
US5307413A (en) * 1991-07-19 1994-04-26 Process Software Corporation Method and apparatus for adding data compression and other services in a computer network
US5534913A (en) * 1994-03-31 1996-07-09 At&T Corp. Apparatus and method for integrating downstream data transfer over a cable television channel with upstream data carrier by other media
US5535199A (en) * 1994-09-06 1996-07-09 Sun Microsystems, Inc. TCP/IP header compression X.25 networks
US5555377A (en) * 1993-12-20 1996-09-10 International Business Machines Corporation System for selectively compressing data transferred in network in response to produced first output when network utilization exceeds first threshold and data length over limit
US5557749A (en) * 1992-10-15 1996-09-17 Intel Corporation System for automatically compressing and decompressing data for sender and receiver processes upon determination of a common compression/decompression method understood by both sender and receiver processes
US5627829A (en) * 1993-10-07 1997-05-06 Gleeson; Bryan J. Method for reducing unnecessary traffic over a computer network
US5668737A (en) * 1995-03-22 1997-09-16 Pixel Magic, Inc. High-speed data processor and coding method
US5673392A (en) * 1994-04-26 1997-09-30 Murata Mfg. Co., Ltd. Method of executing communication program in modem apparatus
US5673322A (en) * 1996-03-22 1997-09-30 Bell Communications Research, Inc. System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks
US5732219A (en) * 1995-03-17 1998-03-24 Vermeer Technologies, Inc. Computer system and computer-implemented process for remote editing of computer files
US5732216A (en) * 1996-10-02 1998-03-24 Internet Angles, Inc. Audio message exchange system
US5742773A (en) * 1996-04-18 1998-04-21 Microsoft Corporation Method and system for audio compression negotiation for multiple channels
US5867112A (en) * 1997-05-14 1999-02-02 Kost; James F. Software method of compressing text and graphic images for storage on computer memory
US6115384A (en) * 1996-06-20 2000-09-05 Fourelle Systems, Inc Gateway architecture for data communication bandwidth-constrained and charge-by-use networks

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5136291A (en) * 1990-11-30 1992-08-04 Unisys Corporation Transmitting binary data files using electronic mail
US5307413A (en) * 1991-07-19 1994-04-26 Process Software Corporation Method and apparatus for adding data compression and other services in a computer network
US5557749A (en) * 1992-10-15 1996-09-17 Intel Corporation System for automatically compressing and decompressing data for sender and receiver processes upon determination of a common compression/decompression method understood by both sender and receiver processes
US5627829A (en) * 1993-10-07 1997-05-06 Gleeson; Bryan J. Method for reducing unnecessary traffic over a computer network
US5555377A (en) * 1993-12-20 1996-09-10 International Business Machines Corporation System for selectively compressing data transferred in network in response to produced first output when network utilization exceeds first threshold and data length over limit
US5534913A (en) * 1994-03-31 1996-07-09 At&T Corp. Apparatus and method for integrating downstream data transfer over a cable television channel with upstream data carrier by other media
US5673392A (en) * 1994-04-26 1997-09-30 Murata Mfg. Co., Ltd. Method of executing communication program in modem apparatus
US5535199A (en) * 1994-09-06 1996-07-09 Sun Microsystems, Inc. TCP/IP header compression X.25 networks
US5732219A (en) * 1995-03-17 1998-03-24 Vermeer Technologies, Inc. Computer system and computer-implemented process for remote editing of computer files
US5668737A (en) * 1995-03-22 1997-09-16 Pixel Magic, Inc. High-speed data processor and coding method
US5673322A (en) * 1996-03-22 1997-09-30 Bell Communications Research, Inc. System and method for providing protocol translation and filtering to access the world wide web from wireless or low-bandwidth networks
US5742773A (en) * 1996-04-18 1998-04-21 Microsoft Corporation Method and system for audio compression negotiation for multiple channels
US6115384A (en) * 1996-06-20 2000-09-05 Fourelle Systems, Inc Gateway architecture for data communication bandwidth-constrained and charge-by-use networks
US5732216A (en) * 1996-10-02 1998-03-24 Internet Angles, Inc. Audio message exchange system
US5867112A (en) * 1997-05-14 1999-02-02 Kost; James F. Software method of compressing text and graphic images for storage on computer memory

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090231998A1 (en) * 2008-03-17 2009-09-17 Microsoft Corporation Selective filtering of network traffic requests
US20160366241A1 (en) * 2012-11-16 2016-12-15 International Business Machines Corporation Saving bandwidth in transmission of compressed data
US10659558B2 (en) * 2012-11-16 2020-05-19 International Business Machines Corporation Saving bandwidth in transmission of compressed data

Also Published As

Publication number Publication date
US5938737A (en) 1999-08-17
EP1015991A1 (en) 2000-07-05
WO1998036362A1 (en) 1998-08-20
AU6157098A (en) 1998-09-08
CA2278300A1 (en) 1998-08-20
JP2001511984A (en) 2001-08-14
AU733295B2 (en) 2001-05-10

Similar Documents

Publication Publication Date Title
USRE39017E1 (en) Internet upstream request compression
US6449658B1 (en) Method and apparatus for accelerating data through communication networks
KR100324974B1 (en) Internet convolution audio/video server
FI114265B (en) Methods and arrangements for realizing effective data transmission over a speed-limited communication link
US7444418B2 (en) Transcoding multimedia information within a network communication system
US7370120B2 (en) Method and system for reducing network latency in data communication
US7013322B2 (en) System and method for rewriting a media resource request and/or response between origin server and client
US20020078241A1 (en) Method of accelerating media transfer
US20030051055A1 (en) System and method for modifying a data stream using element parsing
US20010027493A1 (en) Method for providing streaming media data in a network-based environment
US20020040404A1 (en) System and method for performing broadcast-enabled disk drive replication in a distributed data delivery network
US20020042817A1 (en) System and method for mirroring and caching compressed data in a content distribution system
US20030149792A1 (en) System and method for transmission of data through multiple streams
US7640362B2 (en) Adaptive compression in an edge router
WO2000072517A1 (en) System and method for streaming media over an internet protocol system
EP1325604A2 (en) Speed sensitive content delivery in a client-server network
Iren et al. Network-conscious compressed images over wireless networks
Tan et al. Wireless messaging services for mobile users
WO2001037516A2 (en) Method and apparatus for accelerating data through private enterprise networks
Clausen et al. Internet services via direct broadcast satellites
Liang et al. A bandwidth effective streaming of JPEG2000 images using HyperText Transfer Protocol
US20040073722A1 (en) System and method for data re-compression for communication over ip
CA2272590A1 (en) System and method for streaming media over an internet protocol system
Raman et al. An Image Transport Protocol for the Internet Ѓ
WO1997021167A1 (en) Method of transmitting video and audio data over the internet

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 8

FPAY Fee payment

Year of fee payment: 12

FEPP Fee payment procedure

Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: RPX CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EXELIS INC.;REEL/FRAME:030146/0905

Effective date: 20130322