IEC 13712-3-00 (2001): Technical Overview of Remote Operations Service Element — Part 3: OSI Realizations

This technical article provides a detailed examination of IEC 13712-3-00 (2001), an international standard that specifies the OSI realizations of the Remote Operations Service Element (ROSE). Formally designated as ISO/IEC 13712-3:2001, this standard is part of the ISO/IEC 13712 series, which defines the application-layer protocol for remote operations in open systems interconnection (OSI) environments. The third part focuses on mapping the ROSE services and protocol to the lower layers of the OSI model, especially using Association Control Service Element (ACSE) and Reliable Transfer Service Element (RTSE).

Scope and Overview

IEC 13712-3-00 (2001) covers the protocol specification that enables remote operation invocation across a distributed system. The standard is designed for use in contexts such as X.400 message handling, X.500 directory services, and Common Management Information Protocol (CMIP). It defines:

• the abstract syntax and transfer syntax for Remote Operations (RO) protocol data units (PDUs);
• the mapping of ROSE service primitives onto ACSE and RTSE services;
• the conformance requirements for implementations claiming to support the ROSE OSI realization.

This edition (2001) supersedes the 1995 version and introduces clarifications on the use of ASN.1 encoding rules and improved interoperability guidance.

Technical Requirements and Protocol Specification

Protocol Data Units (PDUs) and Data Types

The standard defines four PDU types using ASN.1 notation:

Each PDU includes an invoke ID to correlate requests and responses. The mapping of these PDUs onto ACSE and RTSE services is described in the standard’s normative annexes.

Service Primitives and Layer Mapping

The ROSE service primitives (RO-INVOKE, RO-RESULT, RO-ERROR, RO-REJECT) are mapped to ACSE A-ASSOCIATE, A-RELEASE, etc., or RTSE RT-OPEN, RT-CLOSE depending on whether reliable transfer is required. The following table summarizes the primary mappings for normal operation:

For each mapping, the standard specifies which fields of the service primitives are conveyed and how to encode them using the specified ASN.1 transfer syntax (usually BER or PER).

Implementation Highlights

Implementing IEC 13712-3-00 requires careful attention to the following aspects:

• ASN.1 Encoding: The standard mandates use of ASN.1 basic encoding rules (BER) or packed encoding rules (PER) as per ISO/IEC 8825-1 and -2. Syntax errors during encoding/decoding are a common source of interoperation problems.
• Invoke ID Management: Each remote operation must be assigned a unique invoke ID within the application association. The standard recommends a cyclic counter but allows implementation-defined schemes as long as uniqueness is guaranteed.
• Association Establishment: ROSE relies on ACSE to set up and tear down application associations. The application-context-name field in the A-ASSOCIATE request must match the context defined by the application profile that uses ROSE.
• Error Handling: The standard defines a repertoire of errors (e.g., PDU error, cancelled operation) and requires that any unrecognized error code be treated as a reject.
• Timeouts: While not explicitly mandated, the standard suggests setting a response timer for each invocation; absence of a result or error within the timeout should lead to a reject.

Sample implementations often include a protocol machine that processes the finite-state machine (FSM) described in Annex A of the standard. The FSM ensures that only valid sequences of PDUs are exchanged.

Compliance and Conformance

Conformance to IEC 13712-3-00 (2001) is assessed through a Protocol Implementation Conformance Statement (PICS) proforma included in Annex C. The key conformance requirements are:

• The implementation must support at least one of the specified mapping categories (ACSE-only or ACSE with RTSE).
• All mandatory PDUs (RO-IV-PDU, RO-RES-PDU, RO-ER-PDU, RO-REJ-PDU) must be supported both as transmitter and receiver, unless the application profile explicitly excludes one or more (e.g., a client-only node may not need to send RO-RES-PDU).
• The ASN.1 type definitions and encoding rules must be strictly followed; deviations must be declared in the PICS.
• Error handling procedures, including automatic generation of RO-REJ-PDU for invalid PDUs, must be implemented.

Testing for conformance typically involves executing a test suite that checks correct state transitions, proper encoding of PDUs, and appropriate reactions to protocol errors. The standard also references the use of generic conformance testing methodology as described in ISO/IEC 9646.

Organizations seeking certification should also verify that the application-context-name registered with the appropriate authority (e.g., ITU-T) is used correctly in the ACSE association establishment.

Frequently Asked Questions