1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - L - M - N - O - P - Q - R - S - T - U - V
DR
Click on the red underlined text to get to the source
... CC TPDU Connection confirm TPDU
DR TPDU Disconnect request TPDU
DC TPDU Disconnect confirm TPDU
...
...
b) an RJ TPDU or a retransmitted CR or DR TPDU during the
resynchronization (see 6.14) and reassignment after
failure (see 6.12) procedures; or
...
... transmission of the final TPDU of a transport connection -
either a DR TPDU in response to CR TPDU or a DC TPDU in
...
... CR TPDU or a DC TPDU in
response to DR TPDU. An appropriate delay will allow the
TPDU concerned to reach the other transport entity ...
...
b) no more than one TPDU from the following list: CR, DR,
CC, DT, ED TPDUs; if this TPDU is present, it shall be
...
... The procedure makes use of the following TPDUs and parameters:
a) DR TPDU;
- SRC-REF;
...
... responder shall
respond to the CR TPDU with a DR TPDU. The reason shall indicate
why the connection was not accepted. The source reference field
...
... why the connection was not accepted. The source reference field
in the DR TPDU shall be set to zero to indicate an unassigned
reference.
...
... The procedure makes use of the following TPDUs and parameters:
a) DR TPDU;
- clearing reason;
...
... a) if it has previously sent or received a CC TPDU (see note
1), shall send a DR TPDU. It shall ignore all
subsequently received TPDUs other than a DR or DC ...
... 1), shall send a DR TPDU. It shall ignore all
subsequently received TPDUs other than a DR or DC TPDU.
On receipt of a DR ...
...
2) For class 4 either send a DR TPDU with a zero value in
the DST-REF field or follow the procedure in
...
... DR TPDU shall
c) if it has previously sent a DR TPDU for the same transport
connection, consider the transport connection released;
...
... transport
entity does not receive acknowledgement of a DR TPDU
within time TS2, it should either reset or disconnect the
network connection ...
... entity is waiting for a CC TPDU before
sending a DR TPDU and the network connection is reset or
released, it should consider the transport connection ...
... transport entity shall respond on the same network
connection with a DR TPDU if the TPDU is a CC TPDU, with a
DC ...
... CC TPDU, with a
DC TPDU if the TPDU is a DR TPDU and shall ignore the TPDU
if neither a DR TPDU nor CC ...
... DC TPDU if the TPDU is a DR TPDU and shall ignore the TPDU
if neither a DR TPDU nor CC TPDU. No association with a
...
... DC TPDU is ignored.
d) If the TPDU is a DR TPDU then there are three cases:
1) if the SRC-REF is not as expected then a DC ...
... DC TPDU with
DST-REF equal to the SRC-REF of the received DR TPDU
is sent back and no association is made;
...
...
2) if a CR TPDU is unacknowledged then the DR TPDU is
associated with the transport connection, regardless
...
... of the value of its SRC-REF parameter;
3) otherwise, the DR TPDU is associated with the
transport connection identified by the DST ...
... been previously received), and the SRC-REF in the CC TPDU
does not match the remote reference, then a DR TPDU is
sent back with DST-REF equal to the SRC-REF of the
...
... 6.18).
c) if a DR TPDU is retained and the TTR timer has not run
out, then follow the actions in either 6.12.3.a or
...
... restart TS1 or TS2 if necessary when the
corresponding TPDU (CR TPDU or DR TPDU respectively is
repeated);
...
... DR, DT and ED TPDUs
except that if a DR is sent in response to a CR TPDU there is no
need to retain a copy of the DR ...
... DR is sent in response to a CR TPDU there is no
need to retain a copy of the DR TPDU.
In the confirmation of receipt variant, applicable only in Class ...
... a valid TPDU which commence resynchronization (i.e. CR or DR or
RJ TPDU) the transport connection is considered as released and
...
... actions, depending on the TPDU:
a) if it is a DR TPDU, then the transport entity shall send a
...
... protocol error;
2) if a DR TPDU is unacknowledged (whether or not a CC
TPDU is unacknowledged): retransmit the DR ...
... DR TPDU is unacknowledged (whether or not a CC
TPDU is unacknowledged): retransmit the DR TPDU, but
setting the source reference to zero;
...
... transport entity,
unless an RJ or DR TPDU has already been received; if a DR
TPDU is received the transport ...
... entity,
unless an RJ or DR TPDU has already been received; if a DR
TPDU is received the transport entity ...
... entity receives a DC TPDU in response
to a DR TPDU which it has sent (see note 2);
b) when the transport ...
... - TPDU in error.
b) DR TPDU;
- reason code.
...
... class. The timer should be stopped when a DR TPDU or an
N-DISCONNECT indication is received.
...
... CR TPDU shall respond to the corresponding
CC TPDU by immediately sending a DT, ED, DR or AK
TPDU;
...
... is in the frozen state. The response to such a TPDU
shall be a DR TPDU;
5) the retransmission ...
... Connection Confirm | x | x | x | x | x | 13.4 |1101 xxxx|
|-----------------------|---|---|---|---|---|-------|---------|
|DR Disconnect Request | x | x | x | x | x | 13.5 |1000 0000|
|-----------------------|---|---|---|---|---|-------|---------|
|DC ...
... rules (see 6.5).
13.5 Disonnect Request (DR) TPDU
13.5.1 Structure
...
... 13.5.1 Structure
The structure of the DR TPDU shall be as follows:
1 2 3 4 5 6 7 8 p p+1 ...end
...
... 1 2 3 4 5 6 7 8 p p+1 ...end
+--+---------+----+-----+----+-----+------+--------+----------+
|LI| DR | DST-REF. | SRC-REF. |REASON|VARIABLE| USER |
...
... Parameter code: 1110 0000
Parameter length: Any value provided that the length of
the DR TPDU does not exceed the maximum
agreed TPDU size or 128 when the DR
...
... the DR TPDU does not exceed the maximum
agreed TPDU size or 128 when the DR
TPDU is used during the connection
...
... user data. The successful transfer of this data is not
guaranteed by the transport protocol. When a DR TPDU is used in
Class 0 it shall not contain this field.
...