ISO/IEC 10026-1:1998 PDF
Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 1: OSI TP Model
Information technology — Open Systems Interconnection — Distributed Transaction Processing — Part 1: OSI TP Model
- Статус документа:
- Действующий
- Формат:
- Электронный (PDF)
- Количество страниц:
- 39
- Дата публикации:
- 15 октября 1998 г.
- Издание:
- ISO/IEC IS 10026 edition 2 version 1
- ICS:
- 35.100.70
Abstract
Overview
ISO/IEC 10026-1:1998 - Information technology - Open Systems Interconnection - Distributed Transaction Processing - Part 1: OSI TP Model defines the conceptual model and service requirements for Distributed Transaction Processing (OSI TP) within the Application Layer of the OSI Reference Model. This second edition (1998) provides a framework for coordinating transactions that span multiple open systems, including terminology, service boundaries, and high-level behaviour needed to support the ACID properties (Atomicity, Consistency, Isolation, Durability) as referenced in ISO/IEC 9804. The part is intended to coexist with other Application Service Elements (e.g., RDA, ROSE) and does not prescribe internal local-resource interfaces.
Key Topics and Requirements
- OSI TP Model and Concepts
- Definitions of transaction concepts: transaction, distributed transaction, transaction branch/tree, dialogue/tree, channel, handshake, hinterland.
- Naming, data transfer, and dialogue/transaction tree rules.
- Service and Protocol Requirements
- Requirements that OSI TP Service must satisfy to support distributed transactions across multiple nodes.
- Support for commitment procedures including two‑phase commit and one‑phase options depending on bound data.
- Coordination, Recovery, Concurrency
- Coordination of resources and commitment coordination roles (commit master/slave, commitment coordinator).
- Recovery phases and log/update behaviour; failure types and restoration rules.
- Concurrency control and deadlock handling (tutorial material provided in annexes).
- Security and Interoperability
- Security considerations aligned with OSI security architecture; coexistence with other Application Layer services.
- Normative Structure
- Includes definitions, normative references, modelling requirements, and informative annexes (A–E) covering relationship to Application Layer structure, tutorials, and changes in the edition.
Practical Applications
Who uses ISO/IEC 10026-1 and why:
- Systems architects and middleware designers - to design transaction managers and distributed transaction middleware that interoperate across vendors and networks.
- Protocol and standards engineers - to specify or validate OSI TP Service and Protocol implementations.
- Database and application developers - to understand ACID support and distributed commitment models when integrating heterogeneous systems.
- Enterprise integration specialists - to align multi-system transaction workflows, recovery, and concurrency policies.
Practical scenarios include distributed commit coordination across multiple servers, cross-domain transaction recovery, and designing transaction-aware application protocols in heterogeneous open systems.
Related Standards
- ISO/IEC 10026 (Parts 2–6) - OSI TP Service, Protocol specification, PICS proforma, application context guidance, unstructured data transfer.
- ISO/IEC 9804 - Commitment, concurrency and recovery service element (ACID definitions).
- ISO/IEC 7498-x series - OSI Reference Model and security/naming/addressing foundations (context for Application Layer services).
Keywords: ISO/IEC 10026-1, OSI TP Model, distributed transaction processing, OSI TP, ACID, two‑phase commit, recovery, concurrency control, Application Layer.
Технические детали
- Технический комитет
- ISO/IEC JTC 1 - Information technology
- SKU
- ISO/IEC 10026-1:1998
Похожие стандарты
Стандарты, упомянутые в описании
BS ISO/IEC 9804:1998
ДействующийInformation technology. Open systems interconnection. Service definition for the commitment, concurrency and…
1 Scope This Recommendation International Standard is intended for reference by other specifications when the functionality of commitment , concurrency and recovery is required. It can be referenced…