# US 6,732,254 B1 · Can device featuring advanced can filtering and message acceptance

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

- Number: US 6,732,254 B1
- Document ID: US6732254B1
- Status: Granted
- Kind: B1
- Application number: 09/630,666
- Filed: 2000-08-01
- Granted: 2004-05-04
- Earliest claimed: 1999-09-15
- Assignees: Koninklijke Philips Electronics N.V.
- Inventors: William J. Slivkoff; Neil Edward Birns; Hong Bin Hao; Richard Fabbri
- Web page: https://patentgrep.com/patent/US6732254B1

## CPC

- G06F 15/78: comprising a single central processing unit
- H04L 1/16: in which the return channel carries supervisory signals, e.g. repetition request signals
- H04L 12/4135: {using bit-wise arbitration}
- H04L 47/2408: for supporting different services, e.g. a differentiated services [DiffServ] type of service
- H04L 47/32: by discarding or delaying data units, e.g. packets or frames
- H04L 47/621: {Individual queue per connection or flow, e.g. per VC}
- H04L 49/90: Buffering arrangements
- H04L 67/12: specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
- H04L 1/1664: {the supervisory signal being transmitted together with payload signals; piggybacking}
- H04L 2001/0094: {Bus}
- H04L 2012/40215: {Controller Area Network CAN}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A CAN device that supports a plurality n (where n≧3) of message objects, including a plurality of registers associated with each message object, including at least one object match ID register that contains a multi-bit object match ID field, and at least one object mask register that contains a multi-bit object mask field; and, a CAN/CAL module that processes incoming messages. The CAN/CAL module assembles a multi-bit screener ID from selected bits of each incoming message to be acceptance filtered, compares the bits comprising the screener ID with corresponding bits of the object match ID field associated with each of at least designated ones of the plurality n of message objects, disregarding any bits of each object match ID field that are masked by corresponding bits of the associated object mask field, and then determines whether any of the comparisons results in a match. Any selected one or more bits of the object match ID field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’, and any selected one or more bits of the object mask field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’ in order to mask any selected one or more bits of the associated object match ID field, whereby the combination of the object match ID field and the object mask field associated with each of the plurality n of message objects constitutes a fully programmable match and mask filter. The CAN/CAL module has the capability to perform acceptance filtering on incoming messages constituting either standard or extended CAN frames. If more than one match is detected, a lowest-numbered (or, alternatively, highest-numbered) one of the message objects is designated to be the matching message object.

## Claims

### Claim 1

A CAN device that supports a plurality n of message objects, comprising:
a plurality of registers associated with each message object, including at least one object match ID register that contains a multi-bit object match ID field, and at least one object mask register that contains a multi-bit object mask field;
a CAN/CAL module that processes incoming messages, wherein the CAN/CAL module:
assembles a multi-bit screener ID from selected bits of each incoming message to be acceptance filtered;
compares the bits comprising the screener ID with corresponding bits of the object match ID field associated with each of at least designated ones of the plurality n of message objects, disregarding any bits of each object match ID field that are masked by corresponding bits of the associated object mask field; and,
determines whether any of the comparisons results in a match;
wherein any selected one or more bits of the object match ID field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’, and any selected one or more bits of the object mask field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’ in order to mask any selected one or more bits of the associated object match ID field, whereby the combination of the object match ID field and the object mask field associated with each of the plurality n of message objects comprises a fully programmable match and mask filter; and,
wherein n≧3.

### Claim 2 (depends on 1)

The CAN device as set forth in claim 1, wherein:
a received message to be acceptance filtered comprises a standard CAN frame; and,
the screener ID field comprises 11 bits of a CAN ID field of a header portion of the standard CAN frame, 8 bits of a first data byte of the standard CAN frame, 8 bits of a second data byte of the standard CAN frame, two don't care bits, and an IDE bit.

### Claim 3 (depends on 2)

The CAN device as set forth in claim 2, wherein the IDE bit is not maskable, and the two don't care bits are required to be masked.

### Claim 4 (depends on 1)

The CAN device as set forth in claim 1, wherein:
a received message to be acceptance filtered comprises an extended CAN frame; and,
the screener ID field comprises 29 bits of a CAN ID field of a header portion of the standard CAN frame, and an IDE bit.

### Claim 5 (depends on 4)

The CAN device as set forth in claim 4, wherein the IDE bit is not maskable.

### Claim 6 (depends on 1)

The CAN device as set forth in claim 1, wherein the CAN/CAL module has the capability to perform acceptance filtering on incoming messages comprising either standard or extended CAN frames.

### Claim 7 (depends on 1)

The CAN device as set forth in claim 1, wherein the plurality of registers further include a control register associated with each message object, wherein the control register associated with each message object contains an object enable field that is programmable for the purpose of enabling or disabling the associated message object.

### Claim 8 (depends on 7)

The CAN device as set forth in claim 7, wherein the control register associated with each message object further contains an object designation field that is programmable for the purpose of designating the associated message object as a receive or transmit message object, whereby the designated ones of the plurality n of message objects comprise all message objects that have been enabled and designated as a receive message object.

### Claim 9 (depends on 1)

The CAN device as set forth in claim 1, wherein:
the message objects are uniquely numbered; and,
if more than one match is detected, designating a lowest-numbered one of the message objects to be the matching message object.

### Claim 10 (depends on 1)

The CAN device as set forth in claim 1, wherein the plurality of registers further include an RTR register associated with each message object, wherein the RTR register associated with each message object contains an RTR handling enable field that is programmable for the purpose of enabling or disabling the associated message object to detect receipt of an incoming message that comprises an Remote Transmit Request frame and/or to transmit a Remote Transmit Request frame.

### Claim 11 (depends on 1)

The CAN device as set forth in claim 1, wherein:
the CAN/CAL module has the capability of automatically assembling incoming messages that comprise multi-frame, fragmented messages;
the plurality of registers further include a fragmented message handling enable register associated with each message object, wherein the fragmented message handling enable register associated with each message object contains a fragmented message handling enable field that is programmable for the purpose of enabling or disabling the associated message object to receive multi-frame, fragmented messages for automatic assembly by the CAN/CAL module; and,
all of the designated ones of the plurality n of message objects are disabled to receive multi-frame, fragmented messages, and thus, are enabled only to receive single-frame, non-fragmented messages.

### Claim 12 (depends on 1)

The CAN device as set forth in claim 1, wherein the plurality of registers comprise memory-mapped registers.

### Claim 13 (depends on 1)

The CAN device as set forth in claim 1, further comprising a data memory space, wherein the plurality of memory-mapped registers are mapped to a respective portion of the data memory space.

### Claim 14 (depends on 1)

The CAN device as set forth in claim 1, further comprising a data memory space, wherein the plurality of memory-mapped registers are mapped to a respective dedicated RAM portion of the data memory space.

### Claim 15 (depends on 1)

The CAN device as set forth in claim 1, further comprising:
a data memory space;
a plurality of message buffers associated with respective ones of the message objects, the plurality of message buffers being located in the data memory space;
a DMA engine that enables the CAN/CAL module to directly access the message buffers.

### Claim 16 (depends on 15)

The CAN device as set forth in claim 15, wherein the plurality of memory-mapped registers are mapped to a respective portion of the data memory space.

### Claim 17 (depends on 15)

The CAN device as set forth in claim 15, wherein the plurality of memory-mapped registers are mapped to a respective dedicated RAM portion of the data memory space.

### Claim 18 (depends on 1)

The CAN device as set forth in claim 1, wherein the CAN device is a CAN microcontroller.

### Claim 19 (depends on 18)

The CAN device as set forth in claim 18, further comprising a processor core that runs CAN applications.

### Claim 20 (depends on 19)

The CAN device as set forth in claim 19, further comprising:
a data memory space;
a plurality of message buffers associated with respective ones of the message objects, the plurality of message buffers being located in the data memory space;
a DMA engine that enables the CAN/CAL module to directly access the message buffers without interrupting the processor core.

### Claim 21 (depends on 20)

The CAN device as set forth in claim 20, wherein an incoming message for which a match is detected is stored by the DMA engine in the message buffer associated with the matching message object.

### Claim 22 (depends on 21)

The CAN device as set forth in claim 21, wherein:
the message objects are uniquely numbered; and,
if more than one match is detected, designating a lowest-numbered one of the message objects to be the matching message object.

### Claim 23 (depends on 15)

The CAN device as set forth in claim 15, wherein an incoming message for which a match is detected is stored by the DMA engine in the message buffer associated with the matching message object.

### Claim 24 (depends on 23)

The CAN device as set forth in claim 23, wherein:
the message objects are uniquely numbered; and,
if more than one match is detected, designating a lowest-numbered one of the message objects to be the matching message object.

### Claim 25

A CAN microcontroller that supports a plurality n of message objects, comprising:
a processor core that runs CAN applications;
a data memory space;
a plurality of message buffers associated with respective ones of the message objects, the plurality of message buffers being located in the data memory space;
a plurality of registers associated with each message object, including at least one object match ID register that contains a multi-bit object match ID field, and at least one object mask register that contains a multi-bit object mask field;
a CAN/CAL module that processes incoming messages, wherein the CAN/CAL module:
assembles a multi-bit screener ID from selected bits of each incoming message to be acceptance filtered;
compares the bits comprising the screener ID with corresponding bits of the object match ID field associated with each of at least designated ones of the plurality n of message objects, disregarding any bits of each object match ID field that are masked by corresponding bits of the associated object mask field; and,
determines whether any of the comparisons results in a match;
a DMA engine that enables the CAN/CAL module to directly access the message buffers without interrupting the processor core;
wherein an incoming message for which a match is detected is stored by the DMA engine in the message buffer associated with the matching message object;
wherein any selected one or more bits of the object match ID field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’, and any selected one or more bits of the object mask field associated with each of the plurality n of message objects can be set to ‘1’ or ‘0’ in order to mask any selected one or more bits of the associated object match ID field, whereby the combination of the object match ID field and the object mask field associated with each of the plurality n of message objects comprises a fully programmable match and mask filter; and,
wherein n≧3.

### Claim 26 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein:
the message objects are uniquely numbered; and,
if more than one match is detected, designating a lowest-numbered one of the message objects to be the matching message object.

### Claim 27 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein the plurality of registers comprise memory-mapped registers.

### Claim 28 (depends on 27)

The CAN microcontroller as set forth in claim 27, wherein the plurality of memory-mapped registers are mapped to a respective portion of the data memory space.

### Claim 29 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein:
a received message to be acceptance filtered comprises a standard CAN frame; and,
the screener ID field comprises 11 bits of a CAN ID field of a header portion of the standard CAN frame, 8 bits of a first data byte of the standard CAN frame, 8 bits of a second data byte of the standard CAN frame, two don't care bits, and an IDE bit.

### Claim 30 (depends on 29)

The CAN microcontroller as set forth in claim 29, wherein the IDE bit is not maskable, and the two don't care bits are required to be masked.

### Claim 31 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein:
a received message to be acceptance filtered comprises an extended CAN frame; and,
the screener ID field comprises 29 bits of a CAN ID field of a header portion of the standard CAN frame, and an IDE bit.

### Claim 32 (depends on 31)

The CAN microcontroller as set forth in claim 31, wherein the IDE bit is not maskable.

### Claim 33 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein the CAN/CAL module has the capability to perform acceptance filtering on incoming messages comprising either standard or extended CAN frames.

### Claim 34 (depends on 25)

The CAN microcontroller as set forth in claim 25, wherein the CAN/CAL module has the capability to perform acceptance filtering on incoming messages comprising Remote Transmit Request frames.

### Claim 35

In a CAN device that supports a plurality n of message objects each of which has an associated message buffer, at least one associated match ID register, and at least one associated mask register, a method for acceptance filtering incoming CAN frames, the method including the steps of:
programming the at least one match ID register associated with each of at least designated ones of the message objects by selectively setting each of the bits in a multi-bit match ID field contained therein to ‘1’ or ‘0’;
programming the at least one mask register associated with each of the at least designated ones of the message objects by selectively setting each of the bits in a multi-bit mask field contained therein to ‘1’ or ‘0’;
extracting a multi-bit screener ID field from a received CAN frame;
comparing the extracted screener ID field to the multi-bit match ID field stored in the at least one match ID register associated with each of the at least designated ones of the message objects, excluding from the comparison any bits of the match ID field masked by corresponding bits of the associated mask field stored in the at least one associated mask register; and,
if a match if found as a result of the comparing step, storing data bytes of the received CAN frame in the message buffer associated with the matching message object;
wherein n≧3.

### Claim 36 (depends on 35)

The method as set forth in claim 35, wherein the designated ones of the message objects comprise all enabled message objects that have been designated as receive message objects.

### Claim 37 (depends on 35)

The method as set forth in claim 35, wherein:
the message objects are uniquely numbered; and,
if more than one match is detected, designating a lowest-numbered one of the message objects to be the matching message object.

### Claim 38 (depends on 35)

The method as set forth in claim 35, wherein:
a received message to be acceptance filtered comprises a standard CAN frame; and,
the screener ID field comprises 11 bits of a CAN ID field of a header portion of the standard CAN frame, 8 bits of a first data byte of the standard CAN frame, 8 bits of a second data byte of the standard CAN frame, two don't care bits, and an IDE bit.

### Claim 39 (depends on 38)

The method as set forth in claim 38, wherein the IDE bit is not maskable, and the two don't care bits are required to be masked.

### Claim 40 (depends on 35)

The method as set forth in claim 35, wherein:
a received message to be acceptance filtered comprises an extended CAN frame; and,
the screener ID field comprises 29 bits of a CAN ID field of a header portion of the standard CAN frame, and an IDE bit.

### Claim 41 (depends on 40)

The method as set forth in claim 40, wherein the IDE bit is not maskable.

### Claim 42 (depends on 35)

The method as set forth in claim 35, wherein:
the CAN device is a CAN microcontroller that includes a processor core that runs CAN applications; and,
the step of storing data bytes of the received CAN frame in the message buffer associated with the matching message object is performed without interrupting the processor core.
