# US 2017/0289316 A1 · System and method for compressing content centric networking messages

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0289316 A1
- Document ID: US20170289316A1
- Status: Published application
- Kind: A1
- Application number: 15/090,248
- Filed: 2016-04-04
- Published: 2017-10-05
- Earliest claimed: 2016-04-04
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Ignacio Solis
- Web page: https://patentgrep.com/patent/US20170289316A1

## CPC

- H04L 69/04: Protocols for data compression, e.g. ROHC
- H04L 67/568: Storing data temporarily at an intermediate stage, e.g. caching
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 69/329: in the application layer [OSI layer 7]
- H04L 69/22: Parsing or analysis of headers
- H04L 2012/5652: {Cell construction, e.g. including header, packetisation, depacketisation, assembly, reassembly}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A computer system can compress or decompress a type-length-value (TLV) component in a message. During operation, the computer can select a compression table associated with a network interface used to send and/or to receive the message, and can search the compression table for an entry that includes a prefix of a value from type-length-value (TLV) component being compressed or decompressed. If compressing the message, the computer may generate a compressed block that corresponds to a compressed version of the TLV component, such that the compressed block includes the compression encoding in place of the prefix in the TLV component's value. The computer can also generate a compressed message that includes the compressed block in place of the TLV component, without a compression table.

## Claims

### Claim 1

A method, comprising:
selecting, by a computer and from a message, a type-length-value (TLV) component to compress;
searching a compression table for an entry that includes a prefix of the TLV component's value;
obtaining a compression encoding for the TLV value from the compression table entry;
generating a compressed block that corresponds to a compressed version of the TLV component, wherein the compressed block includes the compression encoding in place of the prefix in the TLV component's value; and
generating a compressed message that includes the compressed block in place of the TLV component.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
determining an interface for forwarding the message, based on the message's name; and
selecting the compression table that corresponds to the interface.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
in response to generating the compressed message, forwarding the compressed message via the interface.

### Claim 4 (depends on 1)

The method of claim 1, wherein generating the compressed block involves:
determining that the compression encoding corresponds to a subset of the TLV's value; and
setting a continuation field of the compressed block, wherein the continuation field indicates that additional data follows the compressed block.

### Claim 5 (depends on 4)

The method of claim 4, wherein generating the compressed block further involves:
in response to determining that a suffix of the TLV component's value does not have a matching entry in the compression table:
determining a size of the suffix;
appending, to the end of the compressed block, a size field that includes the suffix's size; and
appending the suffix to the size field.

### Claim 6 (depends on 4)

The method of claim 4, wherein generating the compressed block further involves:
in response to determining that a sequence of characters following the TLV component's value have a matching entry in the compression table:
appending, to the compressed block, a size field with a zero value; and
appending, to the size field, one or more additional compressed blocks that compress a remaining portion of the TLV component's value.

### Claim 7

A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method, the method comprising:
selecting, from a message, a type-length-value (TLV) component to compress;
searching a compression table for an entry that includes a prefix of the TLV component's value;
obtaining a compression encoding for the TLV value from the compression table entry;
generating a compressed block that corresponds to a compressed version of the TLV component, wherein the compressed block includes the compression encoding in place of the prefix in the TLV component's value; and
generating a compressed message that includes the compressed block in place of the TLV component.

### Claim 8 (depends on 7)

The non-transitory computer-readable storage medium of claim 7, further comprising:
determining an interface for forwarding the message, based on the message's name; and
selecting the compression table that corresponds to the interface.

### Claim 9 (depends on 8)

The non-transitory computer-readable storage medium of claim 8, further comprising:
in response to generating the compressed message, forwarding the compressed message via the interface.

### Claim 10 (depends on 7)

The non-transitory computer-readable storage medium of claim 7, wherein generating the compressed block involves:
determining that the compression encoding corresponds to a subset of the TLV's value; and
setting a continuation field of the compressed block, wherein the continuation field indicates that additional data follows the compressed block.

### Claim 11 (depends on 10)

The non-transitory computer-readable storage medium of claim 10, wherein generating the compressed block further involves:
in response to determining that a suffix of the TLV component's value does not have a matching entry in the compression table:
determining a size of the suffix;
appending, to the end of the compressed block, a size field that includes the suffix's size; and
appending the suffix to the size field.

### Claim 12 (depends on 10)

The non-transitory computer-readable storage medium of claim 10, wherein generating the compressed block further involves:
in response to determining that a sequence of characters following the TLV component's value have a matching entry in the compression table:
appending, to the compressed block, a size field with a zero value; and
appending, to the size field, one or more additional compressed blocks that compress a remaining portion of the TLV component's value.

### Claim 13

A method, comprising:
receiving, by a computing device via a network interface, a compressed message;
selecting a compression table associated with the interface;
decompressing a message portion from a respective compressed block of the compressed message, using the compression table;
in response to determining that the respective compressed block corresponds to a TLV component:
computing a length of the message portion; and
recreating the TLV component using the message portion and the computed length; and
generating a decompressed message, which includes the TLV component in place of the compressed block.

### Claim 14 (depends on 13)

The method of claim 13, further comprising:
synchronizing entries of the compression table with a computer node accessible via the interface.

### Claim 15 (depends on 13)

The method of claim 13, wherein decompressing the message portion from the respective compressed block involves:
detecting that a continuation field of the compressed block indicates that additional data follows the compressed block; and
reading a size field following the compressed block in the compressed message.

### Claim 16 (depends on 15)

The method of claim 15, wherein decompressing the message portion from the respective compressed block further involves:
in response to determining that the size field includes a non-zero value:
reading a number of bytes that follow the compressed block, corresponding to the size to obtain a data suffix; and
appending the data suffix to the message portion.

### Claim 17 (depends on 15)

The method of claim 15, wherein decompressing the message portion from the respective compressed block further involves:
in response to determining that the size field includes a zero value:
decompressing a second compressed block that follows the respective compressed block in the compressed message, to obtain a second message portion; and
appending the second message portion to the message portion.

### Claim 18 (depends on 13)

The method of claim 13, wherein decompressing the message portion from the respective compressed block involves:
detecting that a continuation field of the compressed block indicates that additional data does not follow the compressed block; and
appending the decompressed message portion to the decompressed message.
