The operation of the OS1 RPC architecture is as
follows. When an RPC user invokes an RPC
request to the RPC ASO, the CF within the RPC
AS0 maps it to a request to the Signature ASE. The
Signature ASE builds an APDU and passes it back
to the CE. The CF maps the APDU to a request to
the RPC ASB-association Service Element, which
builds an APDU and passes it back to the CF. The
CF maps the APDU to a request to ACSE or the
Presentation Layer, which waits for the response
from the peer entity. Once the response arrives, the
CF maps it to an APDU to the RPC ASOassociation
Service Element, which decodes the
APDU and delivers a confirmation or indication to
the CF. The CF maps it to an APDU to the
Signature ASE, which decodes the APDU and
delivers an indication to the CF. The CF maps it to
an indication to the RPC user.
The operation of the OS1 RPC architecture is asfollows. When an RPC user invokes an RPCrequest to the RPC ASO, the CF within the RPCAS0 maps it to a request to the Signature ASE. TheSignature ASE builds an APDU and passes it backto the CE. The CF maps the APDU to a request tothe RPC ASB-association Service Element, whichbuilds an APDU and passes it back to the CF. TheCF maps the APDU to a request to ACSE or thePresentation Layer, which waits for the responsefrom the peer entity. Once the response arrives, theCF maps it to an APDU to the RPC ASOassociationService Element, which decodes theAPDU and delivers a confirmation or indication tothe CF. The CF maps it to an APDU to theSignature ASE, which decodes the APDU anddelivers an indication to the CF. The CF maps it toan indication to the RPC user.
การแปล กรุณารอสักครู่..
