Спецификация протокола Profibus
Подождите немного. Документ загружается.
Page 391
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Connection for Cyclic Data Transfer with no Slave Initiative (MSCY)
Connections for Cyclic Data Transfer with no Slave Initiative are particularly
suited for application processes with the following requirements:
- Contents of variables (process data) have to be available quickly (short re-
sponse times).
- Frequent access to variables.
- Relief of the application by polling within the communication and time optimi-
zed data transfer.
- Cyclic access to exactly one variable per connection.
- Slave shall be polled cyclically.
Data is transferred cyclically between a master and a slave over this connec-
tion. This kind of connection allows a particularly time optimal and efficient
data transfer by storing FMS PDUs in an Image Data Memory, thus avoiding multi-
ple transmissions of the same data. A confirmed FMS service request in the mas-
ter is executed cyclically until a new confirmed FMS service request occurs or
the connection is released by the master or the slave (Abort). During the data
transfer phase only the confirmed FMS services Read and Write may be used. Addi-
tionally all unconfirmed FMS services for event handling with low or high prior-
ity (e.g. InformationReport) may be used in the master.
Connections for Cyclic Data Transfer with no Slave Initiative are characterized
as follows:
- The master is "requester" for all allowed FMS services.
- The slave is "responder" for all allowed confirmed FMS services.
- The slave is "receiver" for all unconfirmed FMS services.
- On a connection only one confirmed FMS service is allowed at any particular
time.
- Optimized data transfer, intermediate storage of PDUs
- All allowed confirmed FMS services and all unconfirmed FMS services with low
priority are mapped onto the cyclic Layer 2 service CSRD with low priority.
- All unconfirmed FMS services with high priority are mapped onto the Layer 2
service SRD with high priority.
- The frequency of service execution is determined by the poll cycle within Lay-
er 2 and the reaction time of the remote user.
- Implicit connection monitoring exists.
Connections for Cyclic Data Transfer with no Slave Initiative use the following
addressing in Layer 2:
- In the master the Remote Addresses / Remote LSAPs of all connections for Cy-
clic Data Transfer with no Slave Initiative are entered into the Poll List of
Layer 2. The Poll List is loaded into the Poll List LSAP.
- Each connection requires a LSAP in the slave.
- Several connections for Cyclic Data Transfer with no Slave Initiative may
exist between a master and a slave, if several confirmed FMS services shall
be executed at the same time. In this case the connections shall be assigned
distinct LSAPs in the slave.
Connections for Cyclic Data Transfer with no Slave Initiative shall use LLI
SAP0.
The execution of FMA7 services is not permitted on connections for Cyclic Data
Transfer with no Slave Initiative.
Connection for Cyclic Data Transfer with Slave Initiative (MSCY_SI)
Connections for Cyclic Data Transfer with Slave Initiative are particularly
suited for application processes with the following requirements:
- Contents of variables (process data) have to be available quickly (short re-
sponse times).
- Frequent access to variables.
Page 392
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
- Relief of the application by polling within the communication and time optimi-
zed data transfer.
- Cyclic access to exactly one variable per connection.
- Slave shall be polled cyclically.
- Slave shall indicate events.
Data is transferred cyclically between a master and a slave over this connec-
tion. This kind of connection allows a particularly time optimal and efficient
data transfer by storing FMS PDUs in an Image Data Memory, thus avoiding multi-
ple transmissions of the same data. A confirmed FMS service request in the mas-
ter is executed cyclically until a new confirmed FMS service request occurs or
the connection is released by the master or the slave (Abort). During the data
transfer phase only the confirmed FMS services Read and Write may be used. Addi-
tionally all unconfirmed FMS services for event handling with low or high prior-
ity (e.g. InformationReport) may be used in the master and the slave.
Connections for Cyclic Data Transfer with Slave Initiative are characterized as
follows:
- The master is "requester" for all allowed confirmed FMS services.
- The slave is "responder" for all allowed confirmed FMS services.
- Master and slave are either "requester" or "receiver" or both for all uncon-
firmed FMS services.
- On a connection only one confirmed FMS service is allowed at any time.
- Optimized data transfer, intermediate storage of PDUs
- All allowed confirmed FMS services and all unconfirmed FMS services with low
priority are mapped onto the cyclic Layer 2 service CSRD with low priority.
- All unconfirmed FMS services with high priority are mapped onto the Layer 2
service SRD with high priority.
- The frequency of service execution is determined by the poll cycle within Lay-
er 2 and the reaction time of the remote user.
- Implicit connection monitoring exists.
Connections for Cyclic Data Transfer with Slave Initiative use the following ad-
dressing in Layer 2:
- In the master the Remote Addresses / Remote LSAPs of all connections for Cy-
clic Data Transfer with Slave Initiative are entered into the Poll List of
Layer 2. The Poll List is loaded into the Poll List LSAP.
- Each connection requires a LSAP in the slave.
- Several connections for Cyclic Data Transfer with Slave Initiative may exist
between a master and a slave, if several confirmed FMS services shall be exe-
cuted at the same time. In this case the connections shall be assigned di-
stinct LSAPs in the slave.
Connections for Cyclic Data Transfer with Slave Initiative shall use LLI SAP 0.
The execution of FMA7 services is not allowed on connections for Cyclic Data
Transfer with Slave Initiative.
Connection for Acyclic Data Transfer with no Slave Initiative (MSAC)
Connections for Acyclic Data Transfer with no Slave Initiative are particularly
suited for application processes with the following characteristics:
- Parallel LLI user services over a connection.
- Rare access to process data (process start, diagnostic device, programming de-
vice etc.)
- Reaction time uncritical.
- Polling done by the application.
- Sporadic service request from the LLI user of the master.
- Frequently changing LLI user services over a connection.
- Transmission of diagnostic and configuration data.
Page 393
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Data is transferred acyclically between a master and a slave over this connec-
tion. Each service request of the LLI user leads to a single independent data
exchange with a slave. All confirmed and unconfirmed LLI user services are al-
lowed in the master. In the slave the Abort services are allowed.
Connections for Acyclic Data Transfer with no Slave Initiative are characterized
as follows:
- The master is "requester" for all LLI user services.
- The slave is "responder" for all confirmed LLI user services.
- The slave is "receiver" for all unconfirmed LLI user services.
- Several confirmed and / or unconfirmed LLI user services are allowed on a con-
nection at the same time (parallel requests).
- All confirmed LLI user services and all unconfirmed LLI user services with low
priority are mapped onto the cyclic Layer 2 service CSRD with low priority.
- All unconfirmed LLI user services with high priority are mapped onto the Layer
2 service SRD with high priority.
- Explicit connection monitoring is possible.
Connections for Acyclic Data Transfer with no Slave Initiative use the following
addressing in Layer 2:
- In the master the Remote Addresses / Remote LSAPs of all connections for Acy-
clic Data Transfer with no Slave Initiative are entered into the Poll List of
Layer 2. The Poll List is loaded into the Poll List LSAP.
- Each connection requires a LSAP in the slave.
- Several connections for Acyclic Data Transfer with no Slave Initiative may
exist between a master and a slave at the same time. In this case the connec-
tions shall be assigned distinct LSAPs in the slave.
Connection for Acyclic Data Transfer with Slave Initiative (MSAC_SI)
Connections for Acyclic Data Transfer with Slave Initiative are particularly
suited for application processes with the following characteristics:
- Parallel LLI user services over a connection.
- Rare access to process data (process start, diagnostic device, programming de-
vice etc.)
- Reaction time uncritical.
- Polling done by the application.
- Sporadic service request from the LLI user of the master.
- Frequently changing LLI user services over a connection.
- Slave shall indicate events.
Data is transferred acyclically between a master and a slave over this connec-
tion. Each service request leads to a single independent data exchange with a
slave. All confirmed LLI user services are allowed in the master. All uncon-
firmed LLI user services are allowed in the master and the slave.
Connections for Acyclic Data Transfer with Slave Initiative are characterized as
follows:
- The master is "requester" for all confirmed LLI user services.
- The slave is "responder" for all confirmed LLI user services.
- Master and slave are either "requester" or "receiver" or both for all uncon-
firmed LLI user services.
- Several confirmed and / or unconfirmed LLI user services are allowed over a
connection at the same time (parallel requests).
- All confirmed LLI user services and all unconfirmed LLI user services with low
priority are mapped onto the cyclic Layer 2 service CSRD with low priority.
- All unconfirmed LLI user services with high priority are mapped onto the Layer
2 service SRD with high priority.
- Explicit connection monitoring is possible.
Page 394
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Connections for Acyclic Data Transfer with Slave Initiative use the following
addressing in Layer 2:
- In the master the Remote Addresses / Remote LSAPs of all connections for Acy-
clic Data Transfer with Slave Initiative are entered into the Poll List of
Layer 2. The Poll List is loaded into the Poll List LSAP.
- Each connection requires a LSAP in the slave.
- Several connections for Acyclic Data Transfer with Slave Initiative may exist
between a master and a slave at the same time. In this case the connections
shall be assigned distinct LSAPs in the slave.
Connections for Acyclic Data Transfer with Slave Initiative shall use LLI SAP 0.
The execution of FMA7 services is not permitted on connections for Acyclic Data
Transfer with Slave Initiative.
6.3.1.2 Master-Master Communication Relationship
For a master-master communication relationship the following kind of connection
is possible:
- Connection for Acyclic Data Transfer.
If a connection for Cyclic Data Transfer is to be established between two mas-
ters, one of these two masters (Responder / Receiver) shall emulate a slave for
this communication relationship. In this case this communication relationship is
looked upon as a master-slave communication relationship. It is declared as a
connection for Cyclic Data Transfer with or with no Slave Initiative and is de-
scribed below. Slave emulation is marked specific to the connection in the CRL
by not entering the Poll List LSAP into the attribute "Local LSAP" for this con-
nection (see also Header of CRL definition before).
Connection for Acyclic Data Transfer (MMAC)
Data is exchanged between masters over this connection. Each service request of
the LLI user leads to a single independent data exchange. All confirmed and un-
confirmed LLI user services are allowed.
Connections for Acyclic Data Transfer are particularly suited for application
processes with the following characteristics:
- Application processes in complex PROFIBUS stations which require mutual, par-
allel and priority controlled data transfer.
- Rare access to process data (process start, diagnostic device, programming de-
vice etc.)
- Reaction time uncritical.
- Polling done by the application.
- Sporadic service request from the LLI user of the master.
- Frequently changing LLI user services over a connection.
- Transmission of diagnostic and configuration data.
Connections for Acyclic Data Transfer are characterized as follows:
- Each master may be "requester" and / or "responder" and / or "receiver" for
all LLI user services.
- Several confirmed and / or unconfirmed LLI user services are allowed on a con-
nection at the same time - not only parallel but also mutual.
- All LLI user services are mapped onto the Layer 2 service SDA.
- Explicit connection monitoring is possible.
Connections for Acyclic Data Transfer use the following addressing in Layer 2:
- Each master-master connection requires a LSAP.
- Several connections for Acyclic Data Transfer may exist between two masters at
the same time. In this case the connections shall be assigned distinct LSAPs.
Page 395
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
6.3.2 Connection Establishment
Connection establishment is used to install a logical connection between two
communication partners for connection-oriented communication relationships. If
no connection establishment has been completed for a connection-oriented commu-
nication relationship, the communication partners are not in the data transfer
phase and no data exchange between the users is permissible. In this situation
the LLI accepts only a request to establish the connection from its own LLI user
or from the communication partner (ASS.req resp. ASS_REQ_PDU).
The FMS user may use the Initiate service of FMS to establish connections. FMS
maps this service onto the Associate service (ASS) of LLI.
The FMA7 user may use the FMA7 Initiate service of FMA7 to establish connec-
tions. FMA7 maps this service onto the Associate service (ASS) of LLI.
Connection establishment within LLI is executed in the same way for the two LLI
users FMS and FMA7.
The sequence charts and specifications below use the following symbols and ab-
breviations:
Legend for the following sequence charts and specifications:
IVIDn : Invoke ID with number n
INFO : InformationReport
R+ : positive response, Result(+)
R- : negative response, Result(-)
CN : Connection
# n : communication reference
[...] : PDU (Protocol Data Unit)
]---> : A service primitive is called by LLI
[<--- : Service primitive is not forwarded
(--- : immediate confirmation
(---
---> : Direction of service primitives and PDU resp.
<---
\ : Event or condition
" : Action
* : Level of a PDU
(...) : Service primitive (FDL) For the FDL service primitives the values
of parameters are not shown, with the exception of <High> and
<Low>.)
<...> : Parameters or values of parameters of a service primitive. The
parameters at the LLI user - LLI interface are shown completely.
At all other interfaces only those parameters are shown that are
necessary for the understanding of the working of LLI.
INI.req : Initiate.req / FMA7-Initiate.req
INI.ind : Initiate.ind / FMA7-Initiate.ind
INI.res : Initiate.res / FMA7-Initiate.res
INI.con : Initiate.con / FMA7-Initiate.con
INI_REQ_PDU : INITIATE_REQ_PDU / FMA7-INITIATE_REQ_PDU
INI_RES_PDU : INITIATE_RES_PDU / FMA7-INITIATE_RES_PDU
INI_ERR_PDU : INITIATE_ERROR_PDU / FMA7-INITIATE_ERROR_PDU
ABO.req : Abort.req / FMA7-Abort.req
ABO.ind : Abort.ind / FMA7-Abort.ind
The LLI user maps a request from the user to establish a connection (Initi-
ate.req from FMS user, FMA7-Initiate.req from FMA7 user) onto the LLI service
primitive ASS.req (see overview of services before). The LLI of the requester
starts the monitoring of connection establishment (see connection establishment
definition below) and generates an Associate Request PDU (ASS_REQ_PDU). This PDU
contains the LLI context and the PDU of the LLI user. If the connection to be
established is an open connection in the requester (Connection Attribute = "I"),
then the assigned LSAP shall be activated with access protection (parameter Ac-
Page 396
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
cess = Remote Address) before the ASS_REQ_PDU is passed to Layer 2 (see also the
formal description of the formal state machine below).
The LLI of the responder compares the local with the remote LLI context upon re-
ceipt of the ASS_REQ_PDU. If the LLI contexts of both communication partners are
compatible, an ASS.ind is passed to the LLI user which contains the INI_REQ_PDU
of the remote LLI user. Additionally, the monitoring of connection establishment
is started. For the establishment of an open connection in the responder (Con-
nection Attribute = "O") the LLI of the responder shall additionally activate
the assigned LSAP with access protection (parameter Access = Actual Remote Ad-
dress). The LLI service primitive ASS.ind is mapped onto an Initiate.ind by FMS
or onto a FMA7-Initiate.ind by FMA7 and is passed to the user (see also: de-
scription of the formal state machine below).
The LLI user maps the positive response of the user (INI.res<R+>) onto the LLI
service primitive ASS.res<R+>. The LLI of the responder generates an
ASS_RES_PDU, which contains the INI_RES_PDU and passes it to Layer 2 for trans-
mission to the remote partner. After the transmission the connection is estab-
lished (status "OPEN") and is in the data transfer phase. The monitoring of con-
nection establishment is stopped and the monitoring of data transfer is started,
if configured.
If the user of the responder rejects the request to establish a connection
(INI.res<R->), the LLI user maps this onto the LLI service primitive ASS.res<R-
>. If the LLI user detects an error such as incompatible context, it also passes
an ASS.res<R-> to the LLI. LLI generates an ASS_NRS_PDU, which contains the
INI_ERRPDU, and passes it to Layer 2 for transmission to the remote partner. The
connection is not established. For an open connection in the responder (Connec-
tion Attribute = "O") LLI shall activate the assigned LSAP with parameter Access
= All after transmission of the ASS_NRS_PDU.
If the LLI of the responder detects an error during connection establishment,
the connection shall not be established, but a connection release shall be per-
formed. LLI starts the monitoring of connection release (T2, connection release
definition below), generates an ABT_REQ_PDU and enters the reason for the con-
nection release into the field Reason Code (RC, see LLI PDU definition). If the
LLI contexts are incompatible, the field Additional Detail (AD) contains the LLI
context of the responder. For an open connection in the responder (Connection
Attribute = "O") LLI shall activate the assigned LSAP with parameter Access =
All after transmission of the ABT_REQ_PDU.
After receipt of an ASS_RES_PDU from the responder the LLI of the requester
stops monitoring the connection establishment and passes an ASS.con<R+>, which
contains the INI_RES_PDU, to the LLI user. The connection is now established
(status "OPEN") and is in the data transfer phase. The monitoring of data trans-
fer is started, if configured (see data transfer definition). FMS maps the
ASS.res<R+> onto an Initiate.con(+) and passes it to the user. FMA7 maps the
ASS.res<R+> onto a FMA7-Initiate.con(+) and passes it to the user.
If the requester receives an ASS_NRS_PDU, then the responder has rejected the
request to establish a connection. LLI stops monitoring the connection estab-
lishment and passes an ASS.con<R->, which contains the INI_ERR_PDU, to the LLI
user. The connection is not established, but a local connection release, which
is monitored, is performed. For an open connection in the requester (Connection
Attribute = "I") LLI shall deactivate the assigned LSAP. FMS maps the ASS.con<R-
> onto an Initiate.con(-) and passes it to the user. FMA7 maps the ASS.con<R->
onto a FMA7-Initiate.con(-) and passes it to the user.
If the requester receives an ABT_REQ_PDU, the connection establishment is
stopped and a local connection release, which is monitored, is started. The rea-
son for rejecting the request to establish a connection shall be found in the
field RC.
If the reason for this rejection was an incompatibility of the LLI contexts,
then the field AD contains the remote LLI context. LLI passes an ABT.ind to the
LLI user (see definition of interface between LL user and LLI). For an open con-
Page 397
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
nection in the requester (Connection Attribute = "I") LLI shall deactivate the
assigned LSAP. FMS maps the ABT.ind of the LLI onto an Abort.ind and passes it
to the user. FMA7 maps the ABT.ind onto a FMA7-Abort.ind and passes it to the
user.
If a connection is in the data transfer phase and an ASS_REQ_PDU is received on
this connection or an ASS.req is performed by the LLI user, then LLI performs a
connection release (see connection release definition).
6.3.2.1 Monitoring Connection Establishment
For time monitoring of connection establishment the timer T1 is used. It is con-
nection specific and mandatory for master and slave devices. The interval for
monitoring connection establishment is configured in the header of the LLI CRL.
In the requester the timer T1 controls the arrival of the response from the re-
mote partner (ASS_RES_PDU, ASS_NRS_PDU, ABT_REQ_PDU) after having sent the
ASS_REQ_PDU. The timer T1 is started before the ASS_REQ_PDU is sent and is
stopped upon receipt of the response of the remote partner.
In the responder the timer T1 controls the response of the local LLI user to the
request to establish a connection from the remote partner as well as the sending
of the response to the requester. The timer T1 is started after the ASS_REQ_PDU
has been received and is stopped after having sent the response to the remote
partner.
If the timer T1 expires in the requester or the responder, a connection release
is performed (see connection release definition).
6.3.2.2 Associate for Master-Slave Communication Relationships
For master-slave communication relationships the master shall always take the
initiative for connection establishment.
The LLI maps the Associate service onto the cyclic Layer 2 service CSRD. The LLI
in the master shall start the Layer 2 polling to the related slave
(Rem_add/DSAP). Thereby the Layer 2 service primitive FDL_CYC_POLL_ENTRY.req
with parameter Marker : "unlock" is used.
For a master-slave connection for acyclic data transfer with no Slave Initiative
the LLI in the master shall stop the Layer 2 polling to the related slave after
connection establishment. Thereby the Layer 2 service primitive
FDL_CYC_POLL_ENTRY.req with parameter Marker : "lock" is used. For all other
types of master-slave connections the Layer 2 polling to the related slave re-
mains unlocked after successful connection establishment.
EXAMPLE: The following sequence charts show examples of possible connection es-
tablishment sequences.
Page 398
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Master/Requester . Slave/Responder
.
FMA7/ . FMA7/
User!FMS LLI FDL BUS FDL LLI FMS !User
=====!====!=============!======.======!=============!====!=====
INI.req ! ! ! !
<#7> ! ! ! !
----> ! ! ! !
[INI_REQ_ ! ! ! !
PDU] ! ! ! !
! ! ! !
ASS.req ! ! ! !
<#7,LLI ! ! ! !
SAP, INI_! ! ! !
REQ_PDU> ![ASS_REQ_PDU]! ! !
---->!"start T1 ! ! !
!(FDL_SEND_ ! ! !
! UPDATE.req) ! ! !
! ]------->!--) ! !
! [<-------!--) ! !
!(FDL_SEND_ ! ! !
! UPDATE.con) ! ! !
!"enable ! ! !
! Polling ! ! !
!(FDL_CYC_POLL! ! !
! _ENTRY.req) ! ! !
! ]------>!--) ! !
! [<------!--) ! !
!(FDL_CYC_POLL! ! !
! _ENTRY.con) !**INI_REQ_PDU! !
! !*ASS_REQ_PDU !(FDL_DATA_ !
! ![SRD_REQ_PDU]! REPLY.ind) !
! ! ]------->!------->] !
! [<------!<-----------/! !
!(FDL_CYC_DATA![SRD_RES_PDU]!\LLI-LLI !
! _REPLY.con) !*no Data ! Context Test!
! ! ! positive !
! ! !"start T1 !
! ! !\CN open: !
! ! !"activate !
! ! ! FDL Access !ASS.ind
! ! ! Protection !<#9,LLI
! ! ! !SAP, INI_
! ! ! !REQ_PDU>
! ! ! ]------->!---->
! ! ! !
! ! ! ! INI.ind
! ! ! ! <#9>
! ! ! ! ---->
Figure 37. Master-Slave Communication Relationship / all Connection Types /
Connection Establishment / Request / LLI-LLI Context Test positive
Page 399
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Master/Requester . Slave/Responder
.
FMA7/ . FMA7/
User!FMS LLI FDL BUS FDL LLI FMS!User
=====!====!=============!======.======!=============!====!=====
! ! ! ! INI.res
! ! ! ! <#9,R+>
! ! ! ! <----
! ! ! ![INI_RES_
! ! ! ! PDU]
! ! ! !ASS.res
! ! ! !<#9,R+,
! ! ! ! LLI SAP,
! ! ! ! INI_RES_
! ! ! ! PDU>
! ! ![ASS_RES_PDU]!<----
! ! !(FDL_REPLY_ !
! ! ! UPDATE.req) !
! ! (--!<------[ !
ASS.con ! ! (--!------>] !
<#7,R+, ! ! !(FDL_REPLY_ !
LLI SAP,! !*no Data ! UPDATE.con) !
INI_RES_! ![SRD_REQ_PDU]! !
PDU> ! ! ]------->!----->] !
<----!<------------!<-----------/!(FDL_DATA_ !
!(FDL_CYC_DATA![SRD_RES_PDU]! REPLY.ind) !
! _REPLY.con) !*ASS_RES_PDU ! !
! !**INI_RES_PDU! "stop T1 !
INI.con ! ! ! !
<#7,R+> !"disable ! ! !
<---- ! Polling ! ! !
!(FDL_CYC_POLL! ! !
! _ENTRY.req) ! ! !
! ]------>!--) ! !
! [<------!--) ! !
!(FDL_CYC_POLL! ! !
! _ENTRY.con) ! ! !
! ! ! !
!"stop T1 ! ! !
! ! ! !
Figure 38. Master-Slave Communication Relationship / Connection for Acyclic
Data Transfer with no Slave Initiative / Connection Establishment /
Positive Response
Page 400
PROFIBUS-Specification-Normative-Parts-6:1997
Copyright by PNO 1997 - all rights reserved
Master/Requester . Slave/Responder
.
User!FMS LLI FDL BUS FDL LLI FMS!User
=====!====!=============!======.======!=============!====!=====
! ! ! ! INI.res
! ! ! ! <#9,R+>
! ! ! ! <----
! ! ! ![INI_RES_
! ! ! ! PDU]
! ! ! !ASS.res
! ! ! !<#9,R+,
! ! ! !LLI SAP,
! ! ! !INI_RES_
! ! ! !PDU>
! ! ![ASS_RES_PDU]!<----
! ! !(FDL_REPLY_ !
! ! ! UPDATE.req) !
! ! (--!<------[ !
ASS.con ! ! (--!------>] !
<#7,R+, ! ! !(FDL_REPLY_ !
LLI SAP,! !*no Data ! UPDATE.con) !
INI_RES_! ![SRD_REQ_PDU]! !
PDU> ! ! ]------->!----->] !
<----!<------------!<-----------/!(FDL_DATA_ !
!(FDL_CYC_DATA![SRD_RES_PDU]! REPLY.ind) !
! _REPLY.con) !*ASS_RES_PDU ! !
! !**INI_RES_PDU! "stop T1 !
!"stop T1 ! ! !
! ! ! !
INI.con ! ! ! !
<#7,R+> ! ! ! !
<---- ! ! ! !
! ! ! !
! !*no Data ! !
! ![SRD_REQ_PDU]! !
! ! ]------>]! !
! ![<---------/ ! !
! ![SRD_RES_PDU]! !
! !*no Data ! !
! ! ! !
! ! ! !
Figure 39. Master-Slave Communication Relationship / Connection for Acyclic
Data Transfer with Slave Initiative or Connection for Cyclic Data
Transfer / Connection Establishment / Positive Response