ISO Transport Protocol

Transport

Transport

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.1

Contents: Page

Protocol Classes in EN ISO/IEC 8073 ........................................................................................ 2

ISO 8073 Transport Protocol Classes......................................................................................... 3
Transport Protocol Sequences.................................................................................................... 4
Establishing a Connection: Three-Way Handshake .................................................................... 6
Establishing a Connection: Addressing Transport Components................................................... 7
Acknowledging Data Units.......................................................................................................... 8
Explicit Flow Control................................................................................................................... 9
Acknowledging Expedited Data .................................................................................................. 10
Clearing a Connection ................................................................................................................ 11
Structure of the Transport Data Unit (TPDU) .............................................................................. 12
TPDU Code Table ...................................................................................................................... 13
Parameter Code Table ............................................................................................................... 14
Protocol Examples ..................................................................................................................... 15

Siemens AG Page 1 KO-7KETHER

Training Center Transport Protocol
 Protocol Classes in EN ISO/IEC 8073

ISO 8072

ISO 8073
ISO 8073
ISO 8073
class ISO
4 8073
class ISO
3 8073
class 2
class 1
class 0
ISO 8602

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.2

The Transport Many local area networks (LANs) use standard protocols within ISO
Layer in Layer 4 (Transport Layer) to handle the transport functions and
Industrial Ethernet ensure security of data transfer.

Industrial Ethernet conforms to the ISO standards frequently used for industrial
applications

ISO 8072 Transport service definition;

ISO 8073 Connection oriented transport protocol

ISO 8602 Protocol for providing the connectionless mode
transport service

ISO 8072 ISO 8072 gives a general list of the services and functions to be provided by
EN ISO/IEC 8072 the Transport Layer

ISO 8073 ISO 8073 describes the implementation of the services required by ISO
EN ISO/IEC 8073 8072 and defines 5 protocol classes:
– Class 0: Simple class
– Class 1: Basic error recovery class
– Class 2: Multiplexing class
– Class 3: Error recovery and multiplexing class
– Class 4: Error detection and recovery class
In Industrial Ethernet:
ISO 8073 class 4!

ISO/IEC 8602 ISO 8602 describes connectionless data transport.

Siemens AG Page 2 KO-7KETHER

Training Center Transport Protocol
 ISO 8073 Transport Protocol Classes

Class Class Class Class Class

0 1 2 3 4

Recovery of errors reported

by Layer 3 • • •
Detection and Recovery of
errors not detected by Layer 3 •
Multiplexing
• • •
Flow control
• • • •
Segmenting
• • • • •
Priority data, Expedited data
• • • •
Network type A B A B C

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.3

Siemens AG Page 3 KO-7KETHER

Training Center Transport Protocol
 Transport Protocol Sequences (1)

TC1
TC2
Eth. addr.: 08 00 06 01 0006 Eth. addr.: 08 00 06 01 0010
CP (TC1)
CP
443-1 443-1

Connection Request TPDU

CR
Establishing the Connection Confirm TPDU
connection CC
Data Acknowledgement TPDU
AK

Data TPDU
DT
Data transfer Data Acknowledgement TPDU
AK

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.4

Siemens AG Page 4 KO-7KETHER

Training Center Transport Protocol
 Transport Protocol Sequences (2)

TC1
TC2
Eth. addr.: 08 00 06 01 0006 Eth. addr.: 08 00 06 01 0010
CP (TC1)
CP
443-1 443-1

Clearing the Disconnect Request TPDU

connection DR
Disconnect Confirm TPDU
DC

TC1 Transport connection 1

TC2 Transport connection 2 The procedure is repeated for TC2!

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.5

Siemens AG Page 5 KO-7KETHER

Training Center Transport Protocol
 Establishing a Connection: Three-Way Handshake

I want to establish a transport connection with you! I want to use expedited data
transmission. I would like the maximum length of a transport protocol data unit to be
1024 bytes. I want to use Extended TPDU Format, etc.

I confirm the connection, but with the following conditions:

I agree to expedited data transmission, but the maximum length of the TPDUs
should be 512 bytes. I agree to Extended Format, etc.

OK!

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.6

Initiator The first step in establishing a transport connection is when an "active" transport
entity (initiator) sends a CR TPDU (Connection Request Transport Protocol Data
Unit).

CR TPDU The CR TPDU notifies the partner of certain parameter values, e.g.

Desired TPDU size

TPDU format

Protocol class

Etc.

Some of the parameter values must be accepted by the partner, whilst others can
be ignored or changed.

Responder If the "passive" transport entity (responder) accepts the connection request, it
sends back a CC TPDU (Connection Confirm Transport Protocol Data Unit).

CC TPDU In the CC TPDU, parameter proposals made in the CR TPDU can be confirmed
or alternative or compromise suggestions made.

AK TPDU The connection is considered established when the initiator sends the responder
an AK TPDU (Data Acknowledgement Transport Protocol Data Unit).

Three-Way This procedure is known as a three-way handshake.

Handshake

Siemens AG Page 6 KO-7KETHER

Training Center Transport Protocol
 Establishing a Connection: Addressing Transport Components

Hallo, TSAP ID "BBBB", this is TSAP ID "AAAA"; I want to establish a transport

connection with you. My reference for this connection is 'A775'! I want to use
expedited data trasmission, ...

Hallo, TSAP ID "AAAA", this is TSAP ID "BBBB". I confirm the connection with your
reference 'A775'. My reference for this connection is B810. I agree to expedited data
transmission, ...

Re: Your ref. 'B810': OK!

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.7

Addressing One transport entity can maintain connections with various other transport
Transport entities.
Components
To ensure clarity in complex situations and prevent defective transport
connections from interfering with those which are operating correctly, ISO
8072/73 divides the transport entity into several subcomponents.

TSAP These subcomponents are called TSAPs (Transport Service Access Point).
TSAP ID TSAPs are identified by logical addresses (TSAP lD = TSAP Identifier).

References Every connection established is given a local reference, of which the partner is
notified during the connection establishment phase.

When data frames are subsequently transmitted using the connection, the
connection reference allocated by the partner always appears in the Level 4
header.

Siemens AG Page 7 KO-7KETHER

Training Center Transport Protocol
 Acknowledging Data Units

Data unit No. 0

I'm waiting for unit No. 1

Data unit No. 1

I'm waiting for unit No. 2

Data unit No. 2

Data unit No. 3

I'm waiting for unit No. 4

Data unit No. 4

Time out
Data unit No. 4

I'm waiting for unit No. 5

Time out
Data unit No. 4

I'm waiting for unit No. 5

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.8

Siemens AG Page 8 KO-7KETHER

Training Center Transport Protocol
 Explicit Flow Control

AK (YR-TU NO = 4, CDT = 2)

DT (TPDU NO = 4)

DT (TPDU NO = 5)
AK (YR-TU NO = 6, CDT = 0)

AK (YR-TU NO = 6, CDT = 1)

AK (YR-TU NO = X, CDT = Y, FCC = 6, 1)

DT (TPDU NO = 6)

AK (YR-TU NO = 4, CDT = 3)
DT (TPDU NO = 7)

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.9

Explicit If a fast sender sends a slow receiver too many data units, this could
Flow Control result in a loss of data at the receiving end or increase the load on the bus
unnecessarily by retransmitting units that have not been received. To prevent
this, flow control is usually practised at the receiving end (optional parameter
'Explicit Flow Control' in the CR TPDU).

The following basic rules apply to explicit flow control:

Flow Control
The receiver notifies the sender of the maximum number of
by Transmission unacknowledged data units it is allowed to send by issuing a transmission
Credit credit (CDT field in an AK TPDU).

If a sender receives an AK TPDU with YR-TU NO = X and CDT = Y, it is

Transmission allowed to send DT TPDUs starting with unit number X and ending with unit
Window number (X+ Y-1).
The range of numbers from YR-TU NO and YR-TU NO+CDT is also
referred to as the transmission window.

If the receipt of an AK TPDU causes a transmission window which was

FCC Parameter previously "closed" to be "opened", the sender must confirm this action by
sending an AK TPDU. In this AK TPDU, the sender informs the receiver
with the FCC parameter (Flow Control Confirmation) that it has taken note
of the extension of credit.
The FCC parameter specifies the sender's current values for the bottom and
the width of the transmission window.

Siemens AG Page 9 KO-7KETHER

Training Center Transport Protocol
 Acknowledging Expedited Data

ED (ED TPDU NO = 20)

EA (YR-TU NO = 20)

ED (ED TPDU NO = 21)

Time out ED (ED TPDU NO = 21)

EA (YR-TU NO = 21)

Time out ED (ED TPDU NO = 21)

EA (YR-TU NO = 21)

ED (ED TPDU NO = 22)

EA (YR-TU NO = 22)

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.10

Expedited Data Alongside normal data transmission, it is also possible to send expedited
Transfer data via a transport connection (ED TPDU = Expedited Data Transport Protocol
Data Unit).

There is no explicit flow control mechanism for expedited data transfer. This
means for the sender:
It must not send a new unit of expedited data until the last one has been
acknowledged!

The following rules apply to the acknowledgement of expedited data units:

Expedited data units (ED TPDUs) are numbered independently of the

normal data units.

The unit numbers (ED TPDU NO) start from zero and are counted up in
unbroken sequence.

An expedited data unit with the ED TPDU NO = X is regarded as
acknowledged when an expedited data acknowledgement TPDU (EA
TPDU) with the YR-TU NO = X is received.

Siemens AG Page 10 KO-7KETHER

Training Center Transport Protocol
 Clearing a Connection

DR

T1 DT

DR
DC

DR
T1
DR
T1 DR

DR

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.11

Clearing a When a data transfer has been completed, a data connection can be
Connection cleared. The resources used for this connection are then released.

Disconnect Request Connection clearance is initiated by a Disconnect Request (DR). The reason for
disconnection can be specified in a particular field in the transport header.

Disconnect Confirm The passive partner informs the active partner that it has taken note of the
disconnection by sending a Disconnect Confirm (DC).

Siemens AG Page 11 KO-7KETHER

Training Center Transport Protocol
 Structure of the Transport Data Unit (TPDU)

Byte
1 2 ... n n+1 p p+1 End

LI Fixed part Variable part Data field

Header

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.12

LI Length indicator
= Header length - 1

Fixed Part The length is governed by the TPDU code.

Variable Part May be omitted.

If it is present, it contains one or more parameters.

Structure:

Byte n+1 Parameter code

n+2 Parameter length, e.g. m One or more
n+3 Parameter value
to
n+2+m

Data Field May be omitted.

Contains transparent user data.
Size limits are noted for each TPDU.

Siemens AG Page 12 KO-7KETHER

Training Center Transport Protocol
 TPDU Code Table
Name TPDU Code
CR Connection Request 1110 XXXX ≡ EXH
CC Connection Confirm 1101 XXXX ≡ DXH
DR Disconnect Request 1000 0000 ≡ 80H
DC Disconnect Confirm 1100 0000 ≡ C0H
DT Data 1111 0000 ≡ F0H
ED Expedited Data 0001 0000 ≡ 10H
AK Data Acknowledgement 0110 0000 ≡ 60H
XXXX:
EA Expedited Data Acknowledgement 0010 0000 ≡ 20H Used for issuing credit in the
connection establishment phase
ER TPDU Error 0101 0000 ≡ 50H
(normally = 0000).
UD Unit Data 0100 0000 ≡ 40H

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.13

Siemens AG Page 13 KO-7KETHER

Training Center Transport Protocol
 Parameter Code Table
Name Parameter Code
TPDU size (max.) C0H
Calling TSAP (identifier) C1H
Called TSAP (identifier) C2H
Checksum parameter C3H
Version number C4H
Protection parameters C5H
Additional option selection C6H
Alternative protocol class C7H
Acknowledge time 85H
Residual error rate 86H
Priority 87H
Transit delay 88H
Throughput 89H
Subsequence number 8AH
Reassignment time 8B H
Flow control confirmation 8CH
Additional clearing information E0H
Invalid TPDU C1H

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.14

Siemens AG Page 14 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (1)

DECODING TO LAYER 2A ACTIVITY OF TWO NODES

-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 0 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3: SOURCE ADDRESS : 080006017172 H

DEST. ADDRESS : 0B0006010101 H
LENGTH FIELD : 020C H

0 :FE FE 03 00 27 E0 00 00 77 75 42 C2 08 53 35 30 .... wuB..S50

16 :31 41 50 30 30 C1 08 53 43 37 32 41 50 30 30 C0 1AP00..SC72AP00.
32 :01 0A C6 01 02 C4 01 01 C3 02 ES 5E 54 45 .......... TE

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.15

FRAME NO.:0 SIPRA H1 internal frame number. The first frame read is assigned the
number 0.

LENGTH: 46 Bytes MAC data field length, also specified by SIPRA H1. 46 bytes were transmitted
after the length field (excluding the FCS field, which is not printed out by SIPRA
H1).

FRAME CORRECT SIPRA H1 reports that the FCS field (which was not printed out) was correct.

IEEE 802.3 Header The data read begins with the decoded MAC header. The preamble and SFD
field are not shown. The LENGTH FIELD: 002C H indicates the length of the
following, relevant data field. (44 bytes are relevant, the rest is padding).

IEE 802.2-Header In most of the Siemens Industrial Ethernet interface modules the default for the
LSAPs is FE H. Industrial Ethernet uses class 1 of IEEE 802.2. The CONTROL
byte of all frames therefore remains =03 H. The P/F bit in the CONTROL byte is
not relevant for IEEE 802.2
class 1.

ISO 8473 Header Byte 00 H stands for the inactive ISO Layer 3 (meaning: the Network Header is
00 bytes long).

Siemens AG Page 15 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (2)

DECODING TO LAYER 2A ACTIVITY OF TWO NODES

-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 0 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3: SOURCE ADDRESS : 080006017172 H

DEST. ADDRESS : 0B0006010101 H
LENGTH FIELD : 020C H

0 :FE FE 03 00 27 E0 00 00 77 75 42 C2 08 53 35 30 .... wuB..S50

16 :31 41 50 30 30 C1 08 53 43 37 32 41 50 30 30 C0 1AP00..SC72AP00.
32 :01 0A C6 01 02 C4 01 01 C3 02 ES 5E 54 45 .......... TE

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.16

ISO 8073 Header Here is a brief explanation of the structure of the Transport Header.
Fixed Part of the Header:
27 The next 39 bytes belong to the Layer 4 Header.
E identifier for Connection Request.
0 The partner is not issued with credit for any normal data units.
00 00 The partner's reference for the connection is not yet known (in this case
therefore: 00 00 H).
77 75 The sender's reference for the connection is 77 75 H.
4 Proposed transport protocol class (negotiable).
2 EXTENDED FORMAT is proposed for the Transport Header (negotiable).
Variable Part of the Header
C2 Identifier for: "The called TSAP now follows".
08 The called TSAP is 8 bytes long.
53 35 30 31 41 50 30 30 The designation of the called TSAP is: "S501AP00".
C1 Identifier for:" The calling TSAP now follows".
08 The calling TSAP is 8 bytes long.
53 43 37 32 41 50 30 30 The designation of the calling TSAP is: "SC72AP00"
C0 Identifier for: "The proposed maximum TPDU size now follows (incl. Transport
Header)".
01 The next byte contains the proposed TPDU size.
0A Proposed maximum TPDU size: 1024 bytes (negotiable).
C6 Identifier for: "An additional option selection now follows".
01 The next byte contains the additional options.
02 Option 1: Additional security for the Transport Header should not be provided
by a checksum.
Option 2: The connection should not allow expedited data transfer.
C4 Identifier for: "The transport protocol version now follows".
01 The next byte contains the transport protocol version".
01 Transport protocol version.
C3 Identifier for: "The transport checksum now follows".
02 The next two bytes contain the checksum.
E55E Checksum (Although deselected above, the checksum must be included
End of Transport Header in the CR TPDU).
PAD 54 45 H are filler bytes (padding to make up the minimum frame length).

Siemens AG Page 16 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (3)
DECODING TO LAYER 4 ACTIVITY OF TWO NODES
-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 0 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3 : SOURCE ADDRESS : 080006017172 H

DEST. ADDRES5 : 080006010101 H
LENGTH FIELD : 020C H
IEEE 802.2 : DLSAP : FE H SLSAP : FE H
CONTROL : 03 H P/F BIT : 0 UNNUMBERED INFORM
ISO 8473 : CODE : 00 H LENGTH : 00 H INACTIVE
ISO 8073 : LENGTH : 27 H
TPDU CODE : E H CREDIT : 0 H CONNECTION REQUEST
DEST. REF : 0000 H SRC. REF: 7775 H
CLASS/OPT : 4 / 2 EXTENDED FORMAT
VAR. PART : LENGTH : 21 H
PARAM CODE : C2 H LENGTH : 08 H ID.OF THE CALLED TSAP
VALUE : 53 35 30 31 41 50 30 30
H
PARAM CODE : C1 H LENGTH : 08 H ID.OF THE CALLING TSAP
VALUE : 53 43 37 32 41 50 30 30
H
PARAM CODE : CO H LENGTH : 01 H TPDU SIZE (MAX.)
VALUE : 0A H 1024 OCTETS
PARAM CODE : C6 H LENGTH : 01 H ADD. OPTION SELECTION
VALUE : 02 H
CHECKSUMS ARE NOT TO BE USED IN CLASS 4
NO USE OF EXPEDITED DATA TRANSFER SERVICE
PARAM CODE : C4 H LENGTH : O1 H VERSION NUMMER
VALUE : 01 H
PARAM CODE : C3 H LENGTH : 02 H CHECKSUM
VALUE : E5 5E H
0 : 54 45 TE

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.17

Siemens AG Page 17 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (4)

DECODING TO LAYER 2A ACTIVITY OF TWO NODES

-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 1 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3: SOURCE ADDRESS : 080006010101 H

DEST. ADDRESS : 0B0006017172 H
LENGTH FIELD : 0205 H

0 :FE FE 03 00 20 D0 77 75 F6 2B 42 C2 08 53 35 30 .... wuB..S50

16 :31 41 50 30 30 C1 08 53 43 37 32 41 50 30 30 C0 1AP00..SC72AP00.
32 :01 09 C6 01 02 00 00 00 00 00 53 44 41 54 .......... SDAT

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.18

This data unit (CC TPDU) is Node A's reply to the previous connection
establishment message frame

ISO 8073 Header The Transport Header begins after the sequence FE FE 03 00 H. Here is a brief
explanation:

Fixed Part of the

Header
20 The next 32 bytes belong to the Layer 4 Header.
D Identifier for Connection Confirm.
0 The partner is not issued with credit for any normal data units.
77 75 Partner's reference (see Frame No. 0)
F6 2B The sender's reference for the connection is F62B H.
4 Selected transport protocol class.
2 EXTENDED FORMAT is accepted for the Transport Header.

Variable Part of the

Header: Apart from the maximum TPDU size, for which 512 bytes is selected, all the other
parameter selections are adopted. The parameters "Version Number" and
"Checksum" are omitted.

PAD The last 9 bytes are padding.

Siemens AG Page 18 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (5)
DECODING TO LAYER 4 ACTIVITY OF TWO NODES
-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 1 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3 : SOURCE ADDRESS : 080006010101 H

DEST. ADDRES5 : 080006017172 H
LENGTH FIELD : 020C H
IEEE 802.2 : DLSAP : FE H SLSAP : FE H
CONTROL : 03 H P/F BIT : 0 UNNUMBERED INFORM

ISO 8473 : CODE : 00 H LENGTH : 00 H INACTIVE

ISO 8073 : LENGTH : 20 H

TPDU CODE : D H CREDIT : 0 H CONNECTION CONFIRM
DEST. REF : 7775 H SRC. REF: F62B H
CLASS/OPT : 4 / 2 EXTENDED FORMAT
VAR. PART : LENGTH : 1A H

PARAM CODE : C2 H LENGTH : 08 H ID.OF THE CALLED TSAP

VALUE : 53 35 30 31 41 50 30 30
H
PARAM CODE : C1 H LENGTH : 08 H ID.OF THE CALLING TSAP
VALUE : 53 43 37 32 41 50 30 30
H
PARAM CODE : CO H LENGTH : 01 H TPDU SIZE (MAX.)
VALUE : 0A H 512 OCTETS
PARAM CODE : C6 H LENGTH : 01 H ADD. OPTION SELECTION
VALUE : 02 H
CHECKSUMS ARE NOT TO BE USED IN CLASS 4
NO USE OF EXPEDITED DATA TRANSFER SERVICE

0 : 00 00 00 00 00 53 44 41 54 .....SDAT

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.19

Siemens AG Page 19 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (6)

DECODING TO LAYER 2A ACTIVITY OF TWO NODES

-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 2 LENGTH : 46 BYTES FRAME CORRECT

IEEE 8021.3: SOURCE ADDRESS : 080006017172 H

DEST. ADDRESS : 0B0006010101 H
LENGTH FIELD : 000E H

0 :FE FE 03 00 09 60 F6 2B 00 00 00 00 00 00 8C 08 .... .+.........

16 :00 00 00 00 00 00 00 01 43 37 32 41 50 30 30 C0 ........C72AP00.
32 :01 0A C6 01 02 C4 01 01 C3 02 09 3C 4C 4F ...........<L0

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.20

This data unit (AK TPDU) completes the establishment of the connection
(three-way handshake).

LENGTH FIELD The next 14 bytes of the MAC data field are relevant.

ISO 8073 Header The Transport Header begins after the sequence FE FE 03 00 H. Here is a brief
explanation:

Fixed Part of the

Header:
09 The next 9 bytes belong to the Layer 4 Header.
6 Identifier for Normal Data Acknowledgement.
0 Since EXTENDED TPDU Format was agreed during establishment of the
connection, the CREDIT field must be = 0!
F62B Partner's reference
00 00 00 00 Number of the next data unit expected = 0
00 00 Credit extended = 0

PAD The sequence 8C 08 4F is padding

Siemens AG Page 20 KO-7KETHER

Training Center Transport Protocol
 Protocol Example (7)
DECODING TO LAYER 4 ACTIVITY OF TWO NODES
-------------------------------------------------------------------------
ACTIVITY BETWEEN NODES A : 080006010101 H / B : 080006017172 H
FRAME NO. : 2 LENGTH : 46 BYTES FRAME CORRECT

IEEE 802.3 : SOURCE ADDRESS : 080006017172 H

DEST. ADDRES5 : 080006010101 H
LENGTH FIELD : 000E H

IEEE 802.2 : DLSAP : FE H SLSAP : FE H

CONTROL : 03 H P/F BIT : 0 UNNUMBERED INFORM

ISO 8473 : CODE : 00 H LENGTH : 00 H INACTIVE

ISO 8073 : LENGTH : 09 H

TPDU CODE : 6 H CREDIT : 0 H DATA ACK.
DEST. REF : F62B H
YR-TU-NR. : 00000000 H EXT.-CDT: 0000 H
VAR. PART : LENGTH : 21 H

16 :8C 08 00 00 00 00 00 00 00 01 43 37 32 41 50 30 ........C72AP00
32 :30 C0 01 0A C6 01 02 C4 01 01 C3 02 09 3C 4C 4F 0...........<L0

SIMATIC NET Industrial Ethernet

Siemens AG 1999. All rights reserved.
Date: 01.09.99
File No.: 7KE_tp.21

Siemens AG Page 21 KO-7KETHER

Training Center Transport Protocol