Layers: OpenLCB, the OSI Model and the TCP/IP Model

This note discusses now OpenLCB relates to the OSI networking model.

OSI model



Application

Network Process to Application

User Data

Presentation

Data Representation and Encryption

Encoded User Data

Session

Interhost Communication

Sessions

Transport

End-to-End Connections and Reliability

Datagrams/Segments

Network

Path Determination and Logical Addressing

Datagrams/Packets

Data Link

MAC and LLC (Physical Addressing)

Frames

Physical

Media, Signal and Binary Transmission

Bits



http://www.tcpipguide.com/free/t_OSIReferenceModelLayerSummary.htm


TCP/IP model (the Internet)

Applications

Application


Transport

(Host-to-Host) transport


Network

Internet


Subnetwork

(Network Interface)




http://www.tcpipguide.com/free/t_TCPIPArchitectureandtheTCPIPModel-2.htm

http://www.davidchappell.com/HTML_email/Opinari_No9_01_04.html



CAN wire protocol

CAN by itself is generally thought to implement “most of the lower two layers of this reference model”. The higher OSI levels are provided by protocols such as DeviceNet, CANopen, etc. For info on CAN and OSI, please see:

Microchip application node AN713

http://www.parallax.com/dl/docs/prod/comm/cantechovew.pdf

http://www.mjschofield.com/osimodel.htm

(Would like to have something from a standards body, but haven't found anything linkable)

Application

CDI, Display, P/C control

Presentation

Memory Configuration

Session

Stream (parts)

Transport

Event Exchange, Datagram, Streams (parts)

Network

Message Exchange (e.g MTI transport, etc), Routing note

Data Link

CAN at 125 kHz

Physical

UTP



Everything above transport is, well, transport independent. For example, the datagram protocol can be CAN specific vs TCP/IP specific, but the configuration protocol, configuration definition information, etc, aren't.




Site hosted by

This is SVN $Revision: 914 $