ISO 11898-1:2015 道路車両—コントローラーエリアネットワーク（CAN）—パート1：データリンク層と物理信号 | ページ 6

4.1

arbitration phase

phase where the nominal bit time is used

4.2

bit stuffing

frame coding method providing bus state changes required for periodic resynchronization when using an NRZ bit representation

Note 1 to entry: Whenever the transmitting logic encounters a certain number (stuff width) of consecutive bits of equal value in the data, it automatically stuffs a bit of complementary value—a stuff bit—into the outgoing bit stream. Receivers de-stuff the Data Frames and the Remote Frames, i.e. the inverse procedure is carried out.

4.3

bus

topology of a communication network ここで, all nodes are reached by passive links which allow transmission in both directions

4.4

bus comparator

electronic circuit converting physical signals used for transfer across the communication medium back into logical information or data signals

4.5

bus driver

electronic circuit converting information or data signals into physical signals so that these signals can be transferred across the communication medium

4.6

bus state

one of two complementary logical states: dominant or recessive

Note 1 to entry: The dominant state represents the logical 0, and the recessive state represents the logical 1. During simultaneous transmission of dominant and recessive bits, the resulting bus state is dominant. When no transmission is in progress, the bus is idle. During idle time, it is in recessive state

4.7

Classical Base Frame Format

format for Data Frames or Remote Frames using an 11-bit identifier, which are transmitted with one single bit rate and up to and including 8 data bytes

4.8

Classical Extended Frame Format

format for Data Frames or Remote Frames using a 29-bit identifier, which are transmitted with one single bit rate and up to and including 8 data bytes

4.9

Classical Frame

Data Frame or Remote Frame using the Classical Base Frame Format or the Classical Extended Frame Format

4.10

content-based arbitration

CSMA arbitration procedure resolving bus-contention when multiple nodes simultaneously access the bus

4.11

data bit rate

number of bits per time during data phase, independent of bit encoding/decoding

4.12

data bit time

duration of one bit in data phase

4.13

Data Frame

frame containing user data (e.g. one or more signals or one or more suspect parameters of one or more process data)

4.14

data phase

phase where the data bit time is used

4.15

edge

difference in bus-states between two consecutive time quanta

4.16

Error Frame

frame indicating the detection of an error condition

4.17

FD enabled

able to receive and to transmit FD Frames, as well as Classical Frames

4.18

FD Base Frame Format

format for Data Frames using an 11-bit identifier, which are transmitted with a flexible bit rate and up to and including 64 data bytes

4.19

FD Extended Frame Format

format for Data Frames using a 29-bit identifier, which are transmitted with a flexible bit rate and up to and including 64 data bytes

4.20

FD Frame

Data Frame using the FD Base Frame Format or FD Extended Frame Format

4.21

FD intolerant

only able to receive or to transmit Classical Frames, disturbing FD Frames

4.22

FD tolerant

not able to receive or to transmit FD Frames but not disturbing them

4.23

frame

Protocol Data Unit of the data link layer specifying the arrangement and meaning of bits or bit fields in the sequence of transfer across the transmission medium

4.24

handle

hardware object label of one or multiple LLC frames (LPDU)

4.25

higher-layer protocol

protocol above the Data Link Layer protocol according to the Open System Interconnection model

[SOURCE:ISO/IEC 7498‑1]

4.26

identifier

does not indicate the destination of the frame but reflects the priority of a particular frame and denotes the meaning of the data

4.27

idle

state of the network, when there is recessive state after the completion of a frame

4.28

idle condition

detection of a sequence of eleven consecutive sampled recessive bits

4.29

integrating

status of a node waiting on an idle condition after it has started the protocol operation during bus-off recovery or after a protocol exception event

4.30

minimum time quantum

smallest time quantum that can be configured for the specific implementation

4.31

multicast

addressing where a single frame is addressed to a group of nodes simultaneously

Note 1 to entry: Broadcast is a special case of multicast, whereby a single frame is addressed to all nodes simultaneously.

4.32

multi master

network with several nodes where every node is able to temporarily control the action of other nodes

4.33

node

assembly, linked to a communication network, capable of communicating across the network according to a communication protocol specification

Note 1 to entry: A CAN node is a node communicating across a CAN network.

4.34

node clock

time base to coordinate the bit-time-related state machines in CAN implementations

4.35

nominal bit rate

number of bits per time during arbitration phase, independent of the bit encoding/decoding

4.36

nominal bit time

duration of one bit in arbitration phase

4.37

Non-Return-to-Zero

method of representing binary signals, i.e. within one and the same bit time, the signal level does not change ここで, a stream of bits having the same logical value provides no edges

4.38

Overload Frame

frame indicating an overload condition

4.39

priority

attribute to a frame controlling its ranking during the arbitration

Note 1 to entry: A high priority increases the probability that a frame wins the arbitration process.

4.40

protocol

formal set of conventions or rules for the exchange of information between nodes, including the specification of frame administration, frame transfer and PL

4.41

protocol exception event

exception from the formal set of conventions or rules to be able to tolerate future new frame formats

4.42

receiver

any node that is not transmitter or integrating when the bus is not idle

4.43

Remote Frame

frame that requests the transmission of a dedicated Data Frame

4.44

stuff bit count

number of stuff bits in a frame before the CRC field, not including fixed stuff bits

4.45

time-triggered communication

option where a frame can be transmitted in a defined time slot, which also provides a network-wide synchronization of clocks, as well as disabling of the automatic retransmission of frames, so that dedicated data and remote frames avoid collisions with data and remote frames transmitted by other nodes

4.46

transceiver

electronic circuit that connects a CAN node to a CAN network, consisting of a bus comparator and a bus driver

4.47

transmitter

node originating a data frame or remote frame, and stays transmitter until the bus is idle again or until the node loses arbitration