# US 2004/0081202 A1 · Communications processor

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

- Number: US 2004/0081202 A1
- Document ID: US20040081202A1
- Status: Published application
- Kind: A1
- Application number: 10/470,365
- Filed: 2003-07-25
- Published: 2004-04-29
- Earliest claimed: 2003-07-25
- Assignees: NVIDIA Corporation
- Inventors: John S Minami; Michael Ward Johnson
- Web page: https://patentgrep.com/patent/US20040081202A1

## CPC

- H04L 43/00: Arrangements for monitoring or testing data switching networks
- H04L 9/40: Network security protocols
- H04L 69/12: Protocol engines
- H04L 69/18: Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
- H04L 69/22: Parsing or analysis of headers
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A communication processor of a class, such as an Internet tuner, provides such desirable features (FIG. 2) as LAN support, an SPI interface (128), a dedicated port (56), and ADPCM (22) for audio applications. The invention provides a low-cost, low-power, easily manufactured, small form-factor network access module which has a low memory demand and provides a highly efficient protocol decode. The invention comprises a hardware-integrated system that both decodes multiple network protocols in a streaming manner concurrently and processes packet data in one pass, thereby reducing system memory and form factor requirements, while also eliminating software CPU overhead.

## Claims

### Claim 1

An apparatus for decoding and encoding network protocols and processing data, comprising:
a network stack for receiving and transmitting packets and for encoding and decoding packets; and
one or more programmable protocol engines associated with said network stack;
wherein said network stack comprise corresponding hardware structures that are implemented in gate-level circuitry and wherein such hardware structures are dedicated solely to performing functions of the network stack.

### Claim 2 (depends on 1)

The apparatus of claim 1, further comprising:
at least one dedicated processing engine for encoding, decoding, and processing packets;
wherein said at least one dedicated processing engine comprises corresponding hardware structures that are implemented in gate-level circuitry and wherein such hardware structures are dedicated solely to performing functions of the processing engines.

### Claim 3

A communications processor, comprising:
a network stack, that both decodes and encodes any of multiple network protocols in a streaming manner concurrently, and that processes packet data in one pass; and
a programmable protocol engine associated with said communications processor for extending network stack functionality.

### Claim 4 (depends on 3)

The communications processor of claim 3, further comprising:
at least one dedicated processing engines for offloading protocol processing and/or data processing.

### Claim 5 (depends on 3)

The communications processor of claim 3, further comprising:
a hardware state machine, incorporated into said network stack, for any of optimized protocol processing and data processing.

### Claim 6 (depends on 3)

The communications processor of claim 3, wherein said network stack and said
protocol engine are integrated into a common gate cover hardware structure.

### Claim 7 (depends on 3)

The communications processor of claim 3, further comprising:
a set of peripherals for said protocol engine;
a network stack core;
a set of data processing engines;
an external controller interface;
a memory interface; and
a plurality of auxiliary serial ports.

### Claim 8 (depends on 3)

The communications processor of claim 3, further comprising:
one or more state machines, associated with said network state, a network stack for supporting any one or more of PPP, LAN, TCP/UDP, and IP protocols.

### Claim 9 (depends on 3)

The communications processor of claim 3, further comprising:
a plurality of generic sockets having send and receive buffers.

### Claim 10 (depends on 3)

The communications processor of claim 3, further comprising:
any of Ethernet and serial links.

### Claim 11 (depends on 3)

The communications processor of claim 3, further comprising any of:
an external controller interface;
an SPI interface;
a parallel interface;
a CPU bypass mode;
a direct data access mode;
a serial modem interface;
a dedicated port which allows one or more devices to use Internet connectivity in said network stack, wherein said one or more devices can connect to the Internet without requiring its own networking hardware or Internet physical connection;
an auxiliary serial port;
a memory interface for external memory;
an MII interface for 10/100 BT PHY;
a data link SPI interface for external MAC and raw IP modes; and
general purpose I/O pins.

### Claim 12 (depends on 3)

The communications processor of claim 3, said data processing engine further comprising any of:
ITU T.37 compatibility;
a Base64 accelerator;
a G3 and/or text rasterizer accelerators;
support transport of JPEG encoded color images;
MIME string search accelerator; and
ADPCM compression/decompression.

### Claim 13 (depends on 3)

The communications processor of claim 3, wherein said communication processor supports an automatic client configuration protocol.

### Claim 14 (depends on 3)

The communications processor of claim 3, wherein said communications processor operates in either of:
a normal mode; and
a CPU bypass mode.

### Claim 15 (depends on 14)

The communications processor of claim 14, wherein when configured for CPU bypass mode, a protocol engine is disabled, and an external controller can communicate directly to a network stack via a register set; and
wherein when said protocol engine is enabled, said external controller communicates via various registers.

### Claim 16 (depends on 3)

The communications processor of claim 3, comprising:
a test index mode for allowing said protocol engine to control a network stack while said protocol engine is still enabled.

### Claim 17 (depends on 3)

The communications processor of claim 3, wherein said protocol engine supports any of an internal MAC and an external MAC.

### Claim 18 (depends on 3)

The communications processor of claim 3, said protocol engine further comprising:
means for supporting router-functions.

### Claim 19 (depends on 18)

The communications processor of claim 18, said protocol engine further means for supporting router functions further comprising:
means for determining an appropriate source IP address to use in a data packet based upon a destination IP address; and
means for passing said source IP address back to a calling engine.

### Claim 20 (depends on 18)

The communications processor of claim 18, said means for supporting router functions further comprising:
means for steering a transmitted packet to an appropriate data link based upon a destination IP address.

### Claim 21 (depends on 3)

The communications processor of claim 3, said protocol engine further comprising:
an IP filter for supporting NAT and IP masquerading.

### Claim 22 (depends on 21)

The communications processor of claim 21, said protocol engine further comprising;
means for supporting forwarding functions, further comprising the ability to substitute packet parameters, recalculate checksums, and either receive the packet or forward the packet out to the network.

### Claim 23 (depends on 3)

The communications processor of claim 3, further comprising:
an Internet protocol (IP) router engine for routing information.

### Claim 24 (depends on 3)

The communications processor of claim 3, further comprising:
an address resolution protocol (ARP) engine for resolving an Ethernet hardware address from any given Internet protocol (IP) address and for automatic replies to valid ARP requests.

### Claim 25 (depends on 3)

The communications processor of claim 3, further comprising:
a media access controller (MAC) module integrated into a network stack for enabling Ethernet access for devices.

### Claim 26 (depends on 3)

The communications processor of claim 3, further comprising:
an internal protocol engine.

### Claim 27 (depends on 3)

The communications processor of claim 3, further comprising:
an interface for communicating with any of the following peripherals:
a memory management unit (MMU);
a DMA controller (DMAC);
a timer;
an interrupt controller (INTC);
an integrated debugger;
a bus controller (BUSC); and
a watchdog timer (WATCH).

### Claim 28 (depends on 3)

The communications processor of claim 3, further comprising:
a Base64 encoding module for transmitting binary data over Internet connections.

### Claim 29 (depends on 3)

The communications processor of claim 3, further comprising:
a text rasterization module for converting incoming network data to a bitmap format.

### Claim 30 (depends on 3)

The communications processor of claim 3, further comprising:
a G3 encoder for encoding data to format said data for a fax controller.

### Claim 31 (depends on 3)

The communications processor of claim 3, further comprising:
a MIME string search engine.

### Claim 32 (depends on 3)

The communications processor of claim 3, further comprising:
an ADPCM accelerator for providing compression and decompression functions.

### Claim 33

An apparatus for augmenting functionality of a network stack, implemented in gate level circuitry, and dedicated solely to performing network stack functions that both decodes and encodes multiple network protocols in a streaming manner concurrently, and that processes packet data in one pass, said apparatus comprising:
a protocol engine, associated with said network stack for implementing said communications functionality in addition to that of said network stack concurrently with said network stack performing protocol operations.

### Claim 34

A method for decoding and encoding network protocols and data, comprising the steps of:
providing a network stack for receiving and transmitting network packets and for encoding and decoding network packet bytes which comprise packet data;
providing at least one data processing engine that is optimized for one or more application protocols;
providing at least one state machine module that is optimized for one or more network protocols; and
providing a programmable protocol engine for extending said network stack functionality;
wherein said network stack, said data processing engine, said state machine module, and said protocol engine comprise corresponding hardware structures that are implemented in gate level circuitry.

### Claim 35

A communications method, comprising the steps of:
providing a network stack that both decodes and encodes multiple network protocols in a streaming manner concurrently, and that processes packet data in one pass;
providing a set of data processing engines which are optimized to application data processing; and
providing a programmable protocol engine, integrated in a common gate level hardware structure with said network stack, for extending functionality of said network stack and said data processing engines.

### Claim 36 (depends on 35)

The communications method of claim 35, further comprising the steps of:
providing a set of peripherals for said protocol engine;
providing a network stack core;
providing an external controller interface;
providing a set of data processing engines;
providing a memory interface; and
providing a plurality of auxiliary serial ports.

### Claim 37 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing at least one network stack state machine for supporting at least one of PPP, LAN, TCP/UDP, and IP protocols.

### Claim 38 (depends on 35)

The communications method of claim 35, further comprising:
providing a plurality of generic sockets having send and receive buffers.

### Claim 39 (depends on 35)

The communications method of claim 35, further comprising:
providing any of Ethernet and serial links.

### Claim 40 (depends on 35)

The communications method of claim 35, further comprising:
providing any of:
an external controller interface;
an SPI interface;
a parallel interface;
a CPU bypass mode;
a direct data access mode;
a serial modem interface;
a dedicated port which allows one or more devices to use Internet connectivity in said network stack, wherein said one or more devices can connect to the Internet without requiring its own networking hardware or Internet physical connection;
an auxiliary serial port;
a memory interface for external memory;
an MII interface for 10/100 BT PHY;
a data link SPI interface for external MAC and raw IP modes; and
general purpose I/O pins.

### Claim 41 (depends on 35)

The communications method of claim 35, said step of providing said protocol engine further comprising the step or steps of providing any of:
ITU T.37 compatibility;
a Base64 accelerator;
a G3 and/or text rasterizer accelerators;
support transport of JPEG encoded color images;
MIME string search accelerator; and
ADPCM compression/decompression.

### Claim 42 (depends on 35)

The communications method of claim 35, wherein said communication processor supports an automatic client configuration protocol.

### Claim 43 (depends on 35)

The communications method of claim 35, wherein said communications processor operates in either of:
a normal mode; and
a CPU bypass mode.

### Claim 44 (depends on 43)

The communications method of claim 43, wherein when configured for CPU bypass mode, a protocol engine is disabled, and an external controller can communicate directly a the network stack via a register set; and
wherein when said protocol engine is enabled, said external controller communicates via various registers.

### Claim 45 (depends on 35)

The communications method of claim 35, comprising the step of:
providing a test index mode for allowing said protocol engine to control a network stack while said protocol engine is still enabled.

### Claim 46 (depends on 35)

The communications method of claim 35, wherein said protocol engine supports any of an internal MAC and an external MAC.

### Claim 47 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing an IP filter for supporting NAT and IP masquerading.

### Claim 48 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing an Internet protocol (IP) router engine for routing information.

### Claim 49 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing an address resolution protocol (ARP) engine for resolving an Ethernet hardware address from any given Internet protocol (IP) address, and for generating automatic replies to valid ARP requests.

### Claim 50 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a media access controller (MAC) module integrated into a network stack for enabling Ethernet access for devices.

### Claim 51 (depends on 35)

The communications method of claim 35, further comprising the step of: providing an internal protocol engine.

### Claim 52 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing an interface for communicating with any of the following peripherals:
a memory management unit (MMU);
a DMA controller (DMAC);
a timer;
an interrupt controller (INTC);
an integrated debugger;
a bus controller (BUSC); and
a watchdog timer (WATCH).

### Claim 53 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a Base64 encoding module for transmitting binary data over Internet connections.

### Claim 54 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a text rasterization module for converting incoming network data to a bitmap format.

### Claim 55 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a G3 encoder for encoding data in a proper format for a fax controller.

### Claim 56 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a MIME string search engine.

### Claim 57 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing an ADPCM accelerator for providing compression and decompression functions.

### Claim 58 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a master SPI port.

### Claim 59

A method for augmenting functionality of a network stack that both decodes and encodes multiple network protocols in a streaming manner concurrently, and that processes packet data in one pass, said method comprising the steps of:
providing a programmable protocol engine, integral to said network stack, and for concurrently extending the functionality of said network stack;
implementing said protocol engine in a hardware structure that comprises a common gate level circuitry with said network stack.

### Claim 60 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a separate PPP buffer to enable said network stack to process data from either a LAN or serial interfaces at the same speed.

### Claim 61 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing a raw IP data path for connecting to any arbitrary data link.

### Claim 62 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing battery backed internal RAM for said protocol engine for non-volatile data or code storage.

### Claim 63 (depends on 35)

The communications method of claim 35, further comprising the step of:
providing means for said protocol engine regulating its own clock frequency based upon current activities to conserve power.
