|
The ISO Remote Operations Service Element Protocol(ROSE) is a protocol that provides remote operation capabilities, allows interaction between entities in a distributed application, and upon receiving a remote operations service request, allows the receiving entity to attempt the operation and report the results of the attempt to the requesting entity. The ROSE protocol itself is only a vehicle for conveying the arguments and results of the operation as defined by the application. In the OSI environment, communication between application processes is represented in terms of communication between a pair of application entities (AEs) using the presentation service. Communication between some application entities are inherently interactive. Typically, one entity requests that a particular operation be performed; the other entity attempts to perform the operation and then report the outcome of the attempt. The generic structure of an operation is an elementary request/reply interaction. Operations are carried out within the context of an application-association. Operations invoked by one AE (the invoker) are performed by the other AE (the performer). Operations may be classified according to whether the performer of an operation is expected to report its outcome. Operations may also be classified according to two possible operation modes: synchronous, in which the invoker requires a reply from the performer before invoking another operation; an asynchronous, in which the invoker may continue to invoke further operations without awaiting a reply. The remote-operation-protocol-machine (ROPM) communicates with its service-user by means of primitives. Each invocation of the ROPM controls a single application-association. The ROPM is driven by ROSE service request primitives from its service-user, and by indication and confirm primitives of the RTSE services, or the presentation-service. The ROPM, in turn, issues indication primitives to its service-user, and request primitives on the used RTSE services, or the presentation-service. The reception of an ROSE service primitive, or of an RTSE service or of a presentation-service primitive, and the generation of dependent actions are considered to be individual. During the exchange of APDUs, the existence of both, the association-initiating AE and the association- responding AE is presumed. During the execution of operations, the existence of an application-association between the peer AEs is presumed. ROSE services summary |
| Service | Type |
| RO-INVOKE
RO-RESULT RO-ERROR RO-REJECT-U RO-REJECT-P |
Non-confirmed Non-confirmed Non-confirmed Non-confirmed Provider-initiated |
 |
Protocol Structure - ISO ROSE: Remote Operations Service Element Protocol (X.229, ISO 9072) |
| ROSE Incoming event list: |
| Abbreviated name | Source | Name and description |
| AA-ESTAB
RO-INVreq RO-RESreq RO-ERRreq RO-RJUreq ROIV RORS ROER RORJu RORJp
APDUua TRANSind TRANSreq P-DATAind RT-TRind RT-TRcnf+ RT-TRcnf- RT-TPind RT-TGind AA-REL
AA-ABreq AA-ABind ABORTind |
RTSE
ACSE
ROSE-user ROSE-user ROSE-user ROSE-user ROPM-peer ROPM-peer ROPM-peer ROPM-peer ROPM-peer
ROPM-peer ROPM-TR ROPM PS-provider RTSE RTSE RTSE RTSE RTSE RTSE ACSE ROPM ROPM-TR RTSE ACSE |
positive RT-OPEN response primitive or positive RT-OPEN
confirm primitive positive A-ASSOCIATE response primitive or positive A-ASSOCIATE confirm-primitive RO-INVOKE request primitive RO-RESULT request primitive RO-ERROR request primitive RO-REJECT-U request primitive valid RO-INVOKE APDU as user data on a TRANSind event valid RO-RESULT APDU as user data on a TRANSind event valid RO-ERROR APDU as user data on a TRANSind event valid RO-REJECT APDU (user -reject) as user data on a TRANSind event valid RO-REJECT APDU (provider-reject with General-problem) as user data on a TRANSind event unacceptable APDU as user data on a TRANSind event transfer indication of an APDU transfer request for an APDU P-DATA indication primitive RT-TRANSFER indication primitive positive RT-TRANSFER confirm primitive negative RT-TRANSFER confirm primitive RT-TURN-PLEASE indication primitive RT-TURN-GIVE indication primitive RT-CLOSE response primitive or RT-CLOSE confirm primitive positive A-RELEASE response primitive or A-RELEASE confirm primitive abort application-association application-association aborted RT-P-ABORT indication primitive or the RT-U-ABORT indication primitive A-ABORT indication primitive or A-P-ABORT indication primitive |
| ROSE Outgoing event list: |
| Abbreviated name | Target | Name and description |
| RO-INVind
RO-RESind RO-ERRind RO-RJUind RO-RJPind ROIV RORS ROER RORJu RORJp TRANSreq TRANSind P-DATAreq RT-TRreq RT-TPreq RT-TGreq AA-ABreq AA-ABind ABORTreq |
ROSE-user
ROSE-user ROSE-user ROSE-user ROSE-user ROPM-peer ROPM-peer ROPM-peer ROPM-peer ROPM-peer ROPM-TR ROPM PS-provider RTSE RTSE RTSE ROPM-TR ROPM RTSE ACSE
|
RO-INVOKE indication primitive
RO-RESULT indication primitive RO-REJECT-U indication primitive RO-REJECT-P indication primitive RO-INVOKE APDU as user data on a TRANSreq event RO-RESULT APDU as user data on a TRANSreq event RO-ERROR APDU as user data on a TRANSreq event RO-REJECT user-reject APDU as user-data on a TRANSreq event RO-REJECT provider-reject APDU as user data on a TRANSreq event transfer request for an APDU transfer indication of an APDU P-DATA request primitive RT-TRANSFER request primitive RT-TURN-PLEASE request primitive RT-TURN-GIVE request primitive abort application-association application-association aborted RT-U-ABORT request primitive A-ABORT request primitive |
Related protocols:ISO Session Protocol, ISO Presentation Protocol
Sponsor Source:
The ROSE protocol is defined in ISO (http://www.iso.org) documents 9072 and ITU (http://www.itu.org) documents X.219 and X.229.
Reference:http://www.doc.ua.pt/arch/itu/rec/product/X.htm:
X.219: Remote Operations: Model, notation and service definition
X.229: Remote Operations: Protocol specification