The possible overall sequences of primitives at a DLCEP are defined in the state transition diagram, Figure 15. In the diagram:
a) DL-Disconnect stands for either the request or the indication form of the primitive in all cases;
b) the labeling of the states “local DLS-user initiated reset pending” (6) and “other reset pending” (7) indicate the party that started the local interaction, and does not necessarily reflect the value of the originator parameter;
c) the “idle state” (1) reflects the absence of a DLCEP. It is the initial and final state of any sequence, and once it has been re-entered the DLCEP is released;
d) the use of a state transition diagram to describe the allowable sequences of service primitives does not impose any requirements or constraints on the internal organization of any implementation of the service.
j) Queued Data Transfer to Publisher
S P
DL-DATA
request DL-DATA indication DL-DATA
confirm
k) Buffer Data Transfer to Publisher
S P
DL-BUFFER-SENT indication
indication
DL-BUFFER-RECEIVED h) DLS Provider
Invoked Reset
P S i) Simultaneous DLS User and
DLS Provider Invoked Reset DL-RESET
request
DL-RESET confirm
S P
DL-RESET indication
DL-RESET response
DL-RESET-COMPLETED indication
Figure 15 – State transition diagram for sequences of DL-connection-mode service primitives at a DLCEP
Idle Outgoing
Connection Pending Data Transfer
Ready DL-CONNECT request
1
DL-CONNECT confirm
Incoming Connection Pending DL-CONNECT indication
DL-CONNECT response
2 5
3
Local DLS-user Initiated Reset Pending
DL-RESET request
DL-RESET confirm 6
Other Reset Pending
DL-RESET indication DL-RESET-COMPLETED indication
7 DL-DISCONNECT
request or indication DL-DISCONNECT request or indication DL-DISCONNECT request or indication DL-DISCONNECT request or indication
DL-DATA request, indication, or confirm
DL-SUBSCRIBER-QUERY request or confirm
DL-DISCONNECT request or indication
Connection Completion Pending
DL-CONNECTION-ESTABLISHED indication
4
DL-DISCONNECT request or indication
DL-BUFFER-SENT indication
DL-DISCONNECT request or indication
Reset CompletionPending
DL-RESET response 8
DL-BUFFER-RECEIVED indication DL-CONNECT response
(non-merger)
(merged into another DLC)
Connection establishment phase 6.5
Function 6.5.1
The DLC / DLCEP establishment service primitives can be used to establish a DLCEP, and possibly a DLC.
NOTE This function may also be provided by local DL-management actions, which are beyond the scope of this standard.
Simultaneous DL-CONNECT request primitives at the two DLSAPs may be merged into one DLC by the concurrently requesting-and-responding DLS-users as indicated in Figure 21 and Figure 22.
Types of primitives and parameters 6.5.2
Table 13 and Table 14 indicate the types of primitives and the parameters needed for DLC/DLCEP establishment.
Table 13 – DLC / DLCEP establishment primitives and parameters (portion 1)
DL-CONNECT Request Indication Response Confirm
Parameter name input output output input output
DLCEP DLS-user-identifier M M
DLCEP DL-identifier M M
Called address M M (=)
Calling address M M (=)
Responding address M M (=)
Calling DLCEP-address CU CU
QoS parameter set
DLCEP class U M (=) U (1) M (=)
DLCEP data delivery features
from requestor to responder(s) U M (=, 2) U (=, 2) M (=)
from responder(s) to requestor U M (=, 2) U (=, 2) M (=)
DLL priority U M (=) U (≤) M (=)
Maximum confirm delay
on DL-CONNECT, DL-RESET and
DL-SUBSCRIBER-QUERY U M (=) U M (=)
on DL-DATA U M (=) U M (=)
DLPDU-authentication U M (≥, 3) U M (≥, 3)
Residual activity
as sender U M (=) U (≤, 4) M (=)
as receiver U M (=) U (≤, 4) M (=)
DL-scheduling-policy U U
Maximum DLSDU sizes (5)
from requestor CU M (≤) CU (≤) M (=)
from responder CU M (≤) CU (≤) M (=)
Buffer-and-queue bindings (5)
as sender CU CU
as receiver CU CU
Sender timeliness (5)
DL-timeliness-class CU M (=) CU M (=)
Time window size (∆T) CU CU
Synchronizing DLCEP CU CU
Time-of-production CU C(=) CU C (=)
Receiver timeliness (5)
DL-timeliness-class CU M (=) CU M (=)
Time window size (∆T) CU CU
Synchronizing DLCEP CU CU
DLS-user-data U M (=) U M (=)
NOTE 1 The DLCEP classes should match, peer with peer, and publisher with subscriber.
NOTE 2 The DLCEP data delivery feature unordered may be upgraded to ordered, and disordered may be upgraded to classical.
NOTE 3 Subclause 6.3.2.5 specifies that DLPDU-authentication may be upgraded from ordinary to source to maximal.
NOTE 4 Subclause 6.3.2.6 specifies that a residual activity value of false may be upgraded to true.
NOTE 5 These parameters are conditional on the negotiated directions of data delivery, and in the case of timeliness, on the specified timeliness class.
NOTE 6 The method by which a confirm primitive is correlated with its corresponding preceding request primitive, or a response primitive is correlated with its corresponding preceding indication primitive, is a local matter.
Table 14 – DLC / DLCEP establishment primitives and parameters (portion 2)
DL-CONNECTION-ESTABLISHED Indication
Parameter name output
DLCEP DLS-user-identifier M (1)
(1) The DLCEP DLS-user-identifier equals the DLS-user-identifier specified in the corresponding DL-CONNECT response primitive.