Various examples and schemes pertaining to simple Ethernet header compression are described. A first network node transmits a first packet with a full header to a second network node. The first network node determines whether a header compression context for the full header has been established by the second network node. In response to determining that the header compression context for the full header has been established by the second network node, the first network node transmits a second packet with a compressed header to the second network node. In response to determining that the header compression context for the full header has not been established by the second network node, the first network node transmits the second packet or a third packet with the full header to the second network node.
Legal claims defining the scope of protection, as filed with the USPTO.
3. The method of claim 2, wherein the determining that the header compression context for the full header has been established by the second network node comprises receiving, from the second network node, a feedback with the first context ID.
4. The method of claim 2, wherein the transmitting of the second packet with the compressed header to the second network node comprises removing the one or more header fields from the full header to generate the compressed header.
5. The method of claim 4, wherein the removing of the one or more header fields from the full header to generate the compressed header comprises removing a plurality of header fields comprising a destination address field, a source address field, a 802.1Q tag field, and a length or type field.
7. The method of claim 6, wherein the determining that the header compression context for the full header has not been established by the second network node comprises receiving, from the second network node, no feedback or a feedback associated with a different full header.
9. The method of claim 8, wherein the receiving of the first packet with the full header comprises receiving a first context ID and the first packet with the full header.
10. The method of claim 9, wherein the transmitting of the feedback comprises transmitting the feedback with the first context ID.
11. The method of claim 8, wherein the establishing of the header compression context for the full header comprises storing one or more header fields of the full header of the first packet.
12. The method of claim 11, wherein the storing of the one or more header fields of the full header of the first packet comprises storing a plurality of header fields comprising a destination address field, a source address field, a 802.1Q tag field, and a length or type field.
16. The apparatus of claim 15, wherein, in determining that the header compression context for the full header has been established by the second network node, the processor receives, from the second network node, a feedback with the first context ID.
17. The apparatus of claim 15, wherein, in transmitting the second packet with the compressed header to the second network node, the processor removes the one or more header fields from the full header to generate the compressed header, and wherein, in removing the one or more header fields from the full header to generate the compressed header, the processor removes a plurality of header fields comprising a destination address field, a source address field, a 802.1Q tag field, and a length or type field.
18. The apparatus of claim 14, wherein, in determining that the header compression context for the full header has not been established by the second network node, the processor receives, from the second network node, no feedback or a feedback associated with a different full header.
20. The apparatus of claim 19, wherein, in transmitting the feedback, the processor transmits the feedback with the second context ID, and wherein, in storing the one or more header fields of the second full header of the second packet, the processor stores a plurality of header fields comprising a destination address field, a source address field, a 802.1Q tag field, and a length or type field.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
February 14, 2020
January 24, 2023
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.