BS ISO/IEC 10026-3:1998

1 Scope
2 Normative references
3 Definitions
4 Abbreviations
5 Conventions
6 Model of the PM
6.1 Overview
6.2 OSI TP Protocol structure
7 Execution Rules
7.1 Operation of the PM
7.2 Procedure rules
7.3 Definitions
7.4 Log records used by the PM
7.5 Recovery-context-handle
8 Use of ACSE, CCR and the Presentation Layer
8.1 Introduction
8.2 Use of ACSE Service primitives
8.3 Use of CCR Service primitives
8.4 Use of the Presentation Layer
8.5 Association Management
9 TP-ASE description
9.1 Introduction
9.2 AF Service Definition
9.3 AF-Services and TP APDUS: parameters and fields
      Mappings
9.4 Procedures
9.5 Mapping
10 SACF description
10.1 Introduction
10.2 SACF states
10.3 Service definitions for SAF service
10.4 Procedure for SAF primitives
10.5 Procedures for TP-ASE, CCR, ACSE, and Presentation
      Service Primitives
10.6 SACF internal events
10.7 Concatenation
10.8 Routeing
11 MACF description
11.1 Introduction
11.2 CAF service definition
11.3 Main procedures
11.4 Internal event procedures
11.5 Common Procedures
12 Structure and encoding of TP APDUs
12.1 Abstract syntax of the TP-ASE APDUs
12.2 Rules of extensibility
13 Conformance
13.1 Static conformance requirements
13.2 Dynamic conformance requirements
13.3 Protocol Implementation Conformance Statement
13.4 Receiving TP APDUs
14 Compliance
15 Precedence statement
16 Index of Actions and Events
Annexes
A OSI TP protocol - State tables
A.1 General
A.2 Introduction
A.3 Processing rules
A.4 MACF state tables
A.5 TPASE
A.6 SACF
A.7 Predicates
B Requirements for writing U-ASEs and application
      contexts
C Scenarios
C.1 Introduction
C.2 Scenarios with a single dialogue (successful cases)
C.3 Scenarios with a single dialogue (unsuccessful cases)
C.4 Scenarios with a single dialogue (failure cases)
C.5 Collision scenarios on a single dialogue
C.6 Tree with multiple dialogues (successful cases)
C.7 Tree with multiple dialogues (unsuccessful cases)
C.8 Heuristic decisions and reporting
C.9 Scenarios for SACP
C.10 Scenarios for CPM
C.11 Read-only scenarios
C.12 Early-exit scenarios
C.13 Static one-phase commitment scenarios
C.14 Implicit prepare scenarios
C.15 TP-ROLLBACK scenarios
C.16 Dynamic Commitment scenarios
C.17 Scenarios showing token movement during transaction termination
C.18 Recovery context handle on dialogue scenario
D Summary of assigned object identifier values
E Recovery from destruction of atomic action data
E.1 Introduction
E.2 Recovery actions
F TPPM transaction states
F.1 TPPM transaction states
G Managing association pools by inference
G.1 Introduction
G.2 Definitions
G.3 Rules
G.4 Benefits
G.5 Suggested System Management Objects

Covers a statement of the nature of the automation giving the necessary behaviour of each of the participating entities, which are providing the OSI TP Service, dealing with; receiving request and response primitives issued by a TP Service user invocation, result of certain events within the local system, receiving indication and confirm primitives issued by the presentation service-provider, result of interactions with other ASEs. Does not restrict or specify the implementation of possible interfaces within a computer system.