Data packet header compression for unidirectional transmission

• US 6,032,197 A
• Filed: 09/25/1997
• Issued: 02/29/2000
• Est. Priority Date: 09/25/1997
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Panabaker, Ruston, Moran, Brian, Birdwell, Kenneth J., Feinleib, David
• Primary Examiner(s): Maung, Zarni
• Assistant Examiner(s): Cardone, Jason D.
• Application Number:
  US08/937,476
• Time in Patent Office: 887 Days
• Field of Search: 709/246, 709/247, 709/218, 709/231, 709/216, 709/217, 709/219, 709/223, 709/232, 370/477, 707/10
• US Class Current: 709/247
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A broadcast transmission system transmits data packets from a server to a client over a unidirectional broadcast network. The system transmits both full-length data packets, which have uncompressed headers, and reduced-length data packets, which have compressed headers derived from associated uncompressed headers. The server compresses the data packets by compressing the packet header. Compressed packet headers contain fewer header fields than their associated uncompressed headers. The server transmits a series of intermixed full-length and reduced-length packets to the client. As the packets are received, the client determines whether the packets are full-length or reduced-length. If the packet is full-length, the client stores the uncompressed header in a header table. If the packet is reduced-length, the client rebuilds the compressed header from its corresponding uncompressed headers in the header table.

Claims

1. A method for serving full-length and reduced-length data packets from a server to a client over a unidirectional broadcast medium, each full-length data packet having a data payload and an uncompressed header with multiple fields, the method comprising the following steps:

at the server;

compressing an uncompressed header to form an associated compressed header having a subset of one or more of the fields so that the fields that are common to the associated uncompressed and compressed headers are identical;

forming a reduced-length data packet having the compressed header and a data payload;

appending a compression key to each of the full-length and reduced-length data packets, the compression key specifying whether the appended data packet is full-length or reduced-length and whether the full-length and reduced-length data packets have associated uncompressed and compressed headers;

transmitting the full-length and reduced-length data packets from the server to the client over a unidirectional broadcast medium;

at the client;

extracting the uncompressed header from the full-length data packet;

storing the uncompressed header;

extracting the compressed header from the reduced-length data packet; and

decompressing the compressed headers by adding fields from the uncompressed header stored at the client that is indicated by the compression keys as being associated to the compressed header, the added fields restoring the subset of fields contained in the compressed header to said multiple fields contained in the uncompressed header.

2. A method as recited in claim 1, wherein the appending step comprises the step of appending a two-block compression key having a first block that specifies whether the appended data packet is full-length or reduced-length and a second block containing an index to a table at the client, whereby the associated uncompressed and compressed headers are indexed to a same location in the table.

3. A method as recited in claim 2, wherein the storing step comprises the step of storing the uncompressed header in the table, and further comprising the step of subsequently removing the uncompressed header from the table to make room for new uncompressed headers.

4. A method as recited in claim 1, further comprising the step of temporarily caching the compressed header in an event that the uncompressed header associated with the cached compressed header has not yet been received at the client.

5. A method as recited in claim 1, further comprising the step of transmitting a higher percentage of the reduced-length data packets in comparison to the full-length data packets.

6. A method as recited in claim 1, further comprising the step of forming and transmitting multiple groups of full-length and reduced-length data packets, wherein each said group of data packets is formatted according to a different transmission protocol.

7. Computer-readable media located at the server and the client having computer-executable instructions for performing the steps of the method as recited in claim 1.

8. A reduced-length data packet having a compressed header embodied on a transmission medium and constructed according to the steps performed at the server in the method as recited in claim 1.

9. A method for compressing a data packet for transmission over a broadcast medium, the data packet comprising a data payload and an uncompressed packet header having multiple fields, the method comprising the following steps:

forming a compressed packet header comprising at least one, but not all, of the fields from the uncompressed packet header;

appending the data payload to the compressed packet header; and

appending a compression key to the compressed packet header, the compression key having a first block containing information to inform a receiver that the appended packet header is a compressed packet header and a second block containing an index to a table at the receiver that identifies the memory location of the uncompressed packet header.

10. A method as recited in claim 9, further comprising the step of transmitting as a reduced-length data packet comprising the compressed packet header, the data payload, and the compression key.

11. A reduced-length data packet embodied on a transmission medium and constructed according to the steps performed at the server in the method as recited in claim 10.

12. A compressed data packet embodied on a computer-readable medium constructed according to the steps performed at the server in the method as recited in claim 9.

13. A computer programmed to perform the steps of the method as recited in claim 9.

14. A computer-readable medium having computer-executable instructions for performing the steps of the method as recited in claim 9.

15. A method for compressing an uncompressed packet header of a UDP/IP data packet to be transmitted over a broadcast medium, the uncompressed packet header having an IP portion containing multiple IP fields and a UDP portion containing multiple UDP fields, the method comprising the following steps:

forming a compressed packet header comprising at least one, but not all, of the IP fields in the uncompressed packet header; and

appending a compression key to the compressed packet header, the compression key comprising a first block containing information to inform a receiver that the appended packet header is a compressed packet header and a second block containing an index to a table at the receiver that identifies where the uncompressed packet header is or will be stored.

16. A method as recited in claim 15, wherein the IP fields include a packet identification field and a fragment field, the forming step comprises the step of forming a compressed packet header consisting of the packet identification field and the fragment field.

17. A method as recited in claim 15, wherein the IP fields include a packet identification field and a fragment field, further comprising the following steps:

forming a 32-bit compressed packet header consisting of the packet identification field and the fragment field;

appending a 7-bit index value to the compressed packet header, the index value containing an index to a table at a receiver that identifies where the uncompressed packet header is or will be stored; and

appending a one-bit compression flag to the index value that is used to inform the receiver that the appended packet header is a compressed packet header.

18. A method as recited in claim 15, further comprising the step of appending a data payload to the compressed packet header.

19. A method as recited in claim 18, further comprising the step of transmitting as a reduced-length data packet comprising the compressed packet header, the data payload, and the compression key.

20. A reduced-length data packet embodied on a transmission medium and constructed according to the steps performed at the server in the method as recited in claim 19.

21. A compressed data packet embodied on a computer-readable medium constructed according to the steps performed at the server in the method as recited in claim 15.

22. A computer programmed to perform the steps of the method as recited in claim 15.

23. A computer-readable medium having computer-executable instructions for performing the steps of the method as recited in claim 15.

24. A broadcast transmission system for transmitting full-length and reduced-length data packets from a server to a client over a broadcast medium, comprising:

a packet header compressor resident at the server to compress an uncompressed header with multiple fields into an associated compressed header with at least one, but not all, of the fields from an associated uncompressed header;

a packet encoder resident at the server to form full-length and reduced-length data packets, the full-length data packets including a data payload and an uncompressed header and the reduced-length data packets including a data payload and a compressed header, the packet encoder further including with each full-length data packet a header index value, the packet encoder further including with each reduced-length data packet the header index value of the full-length data packet that contains the uncompressed header that is associated with the compressed header within the reduced-length data packet;

wherein the packet encoder appends a first bit value to the full-length data packets and a second bit value to the reduced-length data packets to differentiate the full-length and reduced-length data packets;

a transmitter at the server to transmit the full-length and reduced-length data packets over the broadcast medium;

a receiver at the client to receive the full-length and reduced-length data packets from the distribution medium; and

a packet decoder at the client to extract the header index values from the full-length data packets and store the uncompressed headers of the full-length data packets in memory locations referenced by corresponding header index values; and

a packet header decompressor at the client to reconstruct uncompressed headers from the compressed headers in the reduced-length data packets, the packet header decompressor utilizing the header index values from the reduced-length data packets to reference the memory locations containing the associated uncompressed headers and reconstruct missing fields in the compressed headers from the fields in the associated uncompressed headers.

25. A broadcast transmission system as recited in claim 24, wherein the packet decoder stores the uncompressed headers in a table at an entry identified by the corresponding header index values.

26. A broadcast transmission system as recited in claim 24, wherein the packet decoder stores the uncompressed headers in a table according to a first-in-first-out protocol.

27. A broadcast transmission system as recited in claim 24, wherein the packet decoder stores the uncompressed headers in a table, the stored uncompressed headers being considered expired after a predetermined time period elapses.

28. A broadcast transmission system as recited in claim 24, wherein the packet header decompressor temporarily caches a compressed header in an event that the uncompressed header associated with the cached compressed header has not yet been received at the client.

29. A broadcast transmission system as recited in claim 24, wherein the transmitter transmits a higher percentage of the reduced-length data packets in comparison to the full-length data packets.

30. A broadcast transmission system as recited in claim 24, wherein groups of the full-length and reduced-length data packets are formatted according to different transmission protocols.

31. A broadcast transmission system as recited in claim 24, wherein the data packets are formatted according to an UDP/IP protocol, the uncompressed headers have an IP portion containing multiple IP fields and a UDP portion containing multiple UDP fields and the compressed headers have at least one, but not all, of the IP fields in the associated uncompressed header.

32. A broadcast transmission system as recited in claim 31, wherein the IP fields include a packet identification field and a fragment field and the compressed headers comprises the packet identification field and the fragment field.

33. A data packet compressor for compressing a data packet for transmission over a broadcast medium, the data packet comprising a data payload and an uncompressed packet header having multiple fields, comprising:

a packet header compressor to form a compressed packet header having at least one, but not all, of the fields from the uncompressed packet header;

a packet encoder to append a header index value to the compressed packet header, the header index value identifying for a recipient the uncompressed packet header from which the compressed packet header is formed; and

wherein the packet encoder appends a bit value to the header index value to indicate that the appended header is compressed;

the packet encoder further appending a data payload to the compressed packet header.

34. A data packet compressor as recited in claim 33, wherein the data packet is formatted according to an UDP/IP protocol, the uncompressed header has an IP portion containing multiple IP fields and a UDP portion containing multiple UDP fields and the compressed headers has at least one, but not all, of the IP fields in the associated uncompressed header.

35. A data packet compressor as recited in claim 34, wherein the IP fields include a packet identification field and a fragment field and the compressed header comprises the packet identification field and the fragment field.

36. A data packet compressor as recited in claim 34, wherein the IP fields include a packet identification field and a fragment field, further comprising:

the packet header compressor forms a 32-bit compressed packet header consisting of the packet identification field and the fragment field; and

the packet encoder appends a 7-bit index value to the compressed packet header and a one-bit compression flag to inform the recipient that the appended packet header is compressed.

37. A software program embodied on a computer-readable medium having code which implements the data packet compressor as recited in claim 33.

38. A data packet decompressor for decompressing a compressed data packet received from a broadcast medium, the compressed data packet comprising a data payload, a compressed packet header with one or more fields, a header index value, and a bit value to the header index value to indicate that the appended header is compressed, comprising:

a packet decoder to extract the compressed header from the compressed data packet;

a packet header decompressor to access a memory location referenced by the header index value, the memory location holding a full uncompressed packet header having multiple fields that include the fields in the compressed data packet and other fields missing from the compressed data packet; and

the packet header decompressor rebuilding a decompressed packet header from the compressed packet header by adding the missing fields from the memory location to the fields in the compressed data packet.

39. An operating system embodied on a computer-readable medium having code which implements the data packet decompressor as recited in claim 38.

40. A network packet structure embodied on a computer-readable medium, comprising:

a full-length data packet type comprising;

a data payload;

an uncompressed header appended to the data payload, the uncompressed header having multiple fields;

a header index value to reference a memory location at a destination to hold the uncompressed header;

a first bit value to identify the packet as the full-length data packet type; and

,

a reduced-length data packet type derived from the full-length data packet type comprising;

a data payload;

a compressed header appended to the data payload, the compressed header having at least one, but not all, of the fields found in the uncompressed header;

the header index value; and

a second bit value to identify the packet as the reduced-length data packet type.

41. A network packet structure as recited in claim 40, wherein:

the uncompressed header is a UDP/IP header having an IP portion containing multiple IP fields and a UDP portion containing multiple UDP fields; and

the compressed header has at least one, but not all, of the IP fields in the associated uncompressed header.

42. A network packet structure as recited in claim 40, wherein:

the uncompressed header is a UDP/IP header that includes a packet identification field and a fragment field; and

the compressed header consists of the packet identification field and the fragment field.