Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 10035 — Open Systems Interconnection Connectionless ACSE Protocol Standard Series (OSI ACSE)
Information Technology — Open Systems Interconnection — Connectionless Protocol for the Association Control Service Element
🌐 BS ISO/IEC 10035 is an Open Systems Interconnection (OSI) protocol standard jointly developed by ISO and IEC and adopted by the British Standards Institution (BSI) as a UK national standard. It specifies the connectionless Association Control Service Element (ACSE) protocol and its Protocol Implementation Conformance Statement (PICS) proforma. The standard is technically equivalent to ITU-T Recommendations X.237 and X.257, and is widely used for connectionless data exchange in OSI application-layer services such as network management, directory services, and message handling.
💡 The value of connectionless ACSE lies in the “fire-and-forget” data transfer mode: user data can be sent directly between application processes without first establishing an association — ideal for query, event-notification, and alarm-reporting applications.
1. Series Overview and Positioning 📌
The Association Control Service Element (ACSE) is one of the fundamental service elements of the OSI application layer, responsible for establishing, maintaining, and releasing application associations. Connectionless ACSE omits the establishment phase and directly provides the A-UNIT-DATA transfer service. The two parts in this batch form a complete “protocol + conformance statement” combination:
| Standard | Title | Year | Core Content |
|---|---|---|---|
| BS ISO/IEC 10035-1:1995 | Connectionless ACSE protocol specification (ITU-T X.237) | 1995 | A-UNIT-DATA transfer procedure, abstract syntax, state table, object identifiers |
| BS ISO/IEC 10035-2:1995 | Protocol Implementation Conformance Statement (PICS) proforma (ITU-T X.257) | 1995 | Structure of the conformance statement, support items and parameter tables, identification of implementation |
⚠️ This series supersedes and withdraws the earlier BS ISO/IEC 10035:1991. Verify the version and corrigenda in use to avoid referencing withdrawn text.
2. Protocol Specification (Part 1) 🔧
Part 1 defines the behaviour of the connectionless ACSE protocol machine, centred on the A-UNIT-DATA (AUDT) transfer procedure:
- AUDT APDU: the application-protocol-data-unit carrying user data between application processes.
- Direct mapping: the AUDT APDU maps directly onto the P-UNIT-DATA request/indication parameters of the connectionless presentation service.
- Collisions and interactions: rules for handling collisions and interactions during concurrent transfer.
- Extensibility rules: how protocol fields may be extended while remaining backward-compatible.
The standard also provides the abstract syntax definition (ASN.1) and a state table, which fully describes the state transitions and actions of the protocol machine under each input event — the basis for implementation and testing.
| Clause | Content | Role |
|---|---|---|
| A-UNIT-DATA transfer | AUDT APDU fields and procedure | Connectionless user-data exchange |
| Abstract syntax definition | ASN.1 definition of APDUs | Basis for encoding and interoperability |
| Mapping to presentation service | P-UNIT-DATA parameter mapping | Liaison with lower-layer service |
| State table (Annex A) | Event-state transition table | Protocol implementation and testing |
| Object identifiers (Annex B) | Summary of assigned OID values | Unique protocol identification |
3. PICS Conformance Statement (Part 2) 📋
Part 2 provides a Protocol Implementation Conformance Statement (PICS) proforma for implementers to declare their product’s support for the protocol:
- Identification of implementation: records the date, vendor, protocol identification, and implemented technical corrigenda.
- Global statement of conformance: declares whether the implementation conforms overall to the protocol specification.
- Support tables: lists support for the UD APDU and the parameters supported by sender and receiver.
- Instructions for completion: defines the status column (mandatory/optional/not applicable) and support column (implemented/not implemented) rules.
💡 A PICS is the “language of conformance”: it turns abstract protocol requirements into an inspectable checklist of options, establishing a traceable bridge between supplier declarations and third-party testing.
4. Key Technical Requirements ⚙️
- Connectionless ACSE shall use the connectionless presentation service (P-UNIT-DATA) directly, without establishing or maintaining an application association.
- AUDT APDU fields shall be encoded strictly per the abstract syntax definition to ensure cross-implementation interoperability.
- The protocol machine shall follow the Annex A state table, correctly handling collisions and concurrent transfer.
- Implementers should declare their support scope through the PICS so third-party tests can verify conformance.
⚠️ Connectionless mode provides no error recovery or acknowledgement: the sender cannot know whether the receiver actually received the data. For applications requiring reliable delivery, use connection-oriented ACSE or add application-layer acknowledgement.
5. Engineering Practice 🛠️
- Network management: event and alarm reporting commonly use connectionless ACSE to reduce connection overhead.
- Directory and naming services: query-type operations can use connectionless mode for better response efficiency.
- Interoperability testing: derive test cases from the PICS proforma to verify conformance of protocol implementations.
- System integration: in mixed OSI and TCP/IP environments, connectionless ACSE can serve as a lightweight application-layer data channel.
6. Frequently Asked Questions ❓
❓ Q: What is “connectionless” ACSE, and how does it differ from “connection-oriented” ACSE?
A: Connectionless ACSE transfers data directly without establishing an association; connection-oriented ACSE first establishes, then transfers, then releases the association. Connectionless saves handshake overhead but does not guarantee reliable delivery.
A: Connectionless ACSE transfers data directly without establishing an association; connection-oriented ACSE first establishes, then transfers, then releases the association. Connectionless saves handshake overhead but does not guarantee reliable delivery.
❓ Q: How does the A-UNIT-DATA service use the presentation service?
A: The A-UNIT-DATA request/indication maps directly onto the P-UNIT-DATA parameters of the connectionless presentation service, with encoding and transport handled by the lower presentation layer.
A: The A-UNIT-DATA request/indication maps directly onto the P-UNIT-DATA parameters of the connectionless presentation service, with encoding and transport handled by the lower presentation layer.
❓ Q: What is a PICS and why does it matter?
A: A PICS is the “Protocol Implementation Conformance Statement”, a standardised template declaring which protocol options an implementation supports. It makes supplier declarations and third-party conformance testing traceable and comparable.
A: A PICS is the “Protocol Implementation Conformance Statement”, a standardised template declaring which protocol options an implementation supports. It makes supplier declarations and third-party conformance testing traceable and comparable.
🔍 Q: Which applications suit connectionless ACSE?
A: Query, event-notification, and alarm-reporting “fire-and-forget” applications. For reliable delivery, use connection-oriented ACSE or add application-layer acknowledgement.
A: Query, event-notification, and alarm-reporting “fire-and-forget” applications. For reliable delivery, use connection-oriented ACSE or add application-layer acknowledgement.