BS-ISO-IEC-TR-11589-1995.pdf

BRITISH STANDARD BS ISO/IEC TR 11589:1995 Implementation of ISO/IEC TR 11589:1995 Information technology Open Systems Interconnection LOTOS description of the CCR service Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 11589:1995 This British Standard, having been prepared under the direction of the Information Systems Technology Assembly, was published under the authority of the Standards Board and comes into effect on 15 January 1996 © BSI 02-2000 The following BSI references relate to the work on this standard: Committee reference IST/21 Draft for comment 94/641265 DC ISBN 0 580 25231 0 Committees responsible for this British Standard The preparation of this British Standard was entrusted to Technical Committee IST/21, Open Systems Interconnection, data management and open distributed processing, upon which the following bodies were represented: British Computer Society British Telecommunications plc CCTA (the Government Centre for Information Systems) Department of Trade and Industry IT Standards Unit (ITD6A) Digital Equipment Co. Ltd. IBM United Kingdom Ltd. International Computers Limited Joint Information Systems Committee Level 7 Ltd. Logica UK Ltd. National Computing Centre Ltd. National Health Services Nine Tiles Computer Systems Ltd. PSC International Ltd. Rank Xerox Ltd. Salford Software Services SEMA Group Systems Ltd. X Open Company Ltd. Amendments issued since publication Amd. No.DateComments Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 11589:1995 © BSI 02-2000i Contents Page Committees responsibleInside front cover National forewordii Forewordiii Text of ISO/IEC TR 115891 Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI BS ISO/IEC TR 11589:1995 ii © BSI 02-2000 National foreword This British Standard reproduces verbatim ISO/IEC TR 11589:1995 and implements it as the UK national standard. This British Standard is published under the direction of the Information Systems Technology Assembly whose Technical Committee IST/21 has the responsibility to: aid enquirers to understand the text; present to the responsible international committee any enquiries on interpretation, or proposals for change, and keep UK interests informed; monitor related international and European developments and promulgate them in the UK. NOTEInternational and European Standards, as well as overseas standards, are available from Customer Services, BSI, 389 Chiswick High Road, London W4 4AL. A British Standard does not purport to include all the necessary provisions of a contract. Users of British Standards are responsible for their correct application. Compliance with a British Standard does not of itself confer immunity from legal obligations. Summary of pages This document comprises a front cover, an inside front cover, pages i and ii, the ISO/IEC TR title page, pages ii to iv, pages 1 to 22 and a back cover. This standard has been updated (see copyright date) and may have had amendments incorporated. This will be indicated in the amendment table on the inside front cover. Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) ii © BSI 02-2000 Contents Page Forewordiii Introduction1 1Scope1 2Normative references1 3Definitions1 4Symbols and abbreviations1 5Conventions2 6Introduction to the formal description2 6.1Model2 6.2Structure2 6.3Service overview5 7Global constraints of the CCR service5 8Service primitives6 8.1Basic construction6 8.2CSP classification9 8.3CSP parameter selectors11 8.4CSP parameters12 8.4.1 Atomic Action Identifier12 8.4.2 Branch Identifier12 8.4.3 User Data12 8.4.4 Recovery State12 8.5Others13 9Constraints of the superior side13 9.1Normal sequence of the superior13 9.2Recovery sequence of the superior15 10Constraints of the subordinate side16 10.1Normal sequence of the subordinate16 10.2Recovery sequence of the subordinate18 11Constraints of the relation between superior and subordinate18 11.1Service Primitive Queue19 11.2CCEPRelation21 Figure 1 CCR service model2 Figure 2 Relationship among the processes3 Figure 3 Relationship among the types4 Table 1 Service Primitives and Parameters5 Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) © BSI 02-2000iii Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization. The main task of technical committees is to prepare International Standards. In exceptional circumstances a technical committee may propose the publication of a Technical Report of one of the following types: type 1, when the required support cannot be obtained for the publication of an International Standard, despite repeated efforts; type 2, when the subject is still under technical development or where for any other reason there is the future but not immediate possibility of an agreement on an International Standard; type 3, when a technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example). Technical Reports of types 1 and 2 are subject to review within three years of publication, to decide whether they can be transformed into International Standards. Technical Reports of type 3 do not necessarily have to be reviewed until the data they provide are considered to be no longer valid or useful. ISO/IEC TR 11589, which is a Technical Report of type 2, was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 21, Open systems interconnection, data management and open distributed processing. Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI iv blank Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) © BSI 02-20001 Introduction This Technical Report gives a LOTOS specification of CCR Service Definition defined in ISO/IEC 9804. LOTOS is a formal description technique(FDT) to define behavior of systems with a formal syntax and semantics. Aim of this Technical Report is to give an unambiguous, precise, and self-contained description of ISO/IEC 9804. However, in case of inconsistency between ISO/IEC 9804 and this Technical Report, ISO/IEC 9804 takes precedence over this Technical Report. 1 Scope This Technical Report focuses on one atomic action branch and covers the relevant service primitives with their types and parameters, and the behaviour as to how these service primitives can be issued and received by the CCR service provider. Service primitives and its parameters are defined in clause 8. The sequential rules on superior side is defined in clause 9, and on subordinate side is defined in clause 10. The relation of the events that occur on the superior and subordinate sides is described in clause 11. This Technical Report does not cover the following items in ISO/IEC 9804. Clause 6: concept. Because formal language can not describe this kind of semantics. CCR service-user rules (Annex A), Relationship of CCR to the Application Layer Structure (Annex B). Description to manage more than one atomic action branch. 2 Normative references The following standards contain provisions which, through reference in this text, constitute provisions of this Technical Report. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this Technical Report are encouraged to investigate the possibility of applying the most recent editions of the standards listed below. Members of IEC and ISO maintain registers of currently valid International Standards. ISO/IEC 9804:1994, Information technology Open Systems Interconnection Service definition for the Commitment, Concurrency and Recovery service element. ISO/IEC 9805-1:1994, Information technology Open Systems Interconnection Protocol for the Commitment, Concurrency and Recovery service element: Protocol Specification. ISO 8807:1989, Information processing systems Open Systems Interconnection LOTOS A formal description technique based on the temporal ordering of observational behaviour. 3 Definitions For the purposes of this Technical Report the definitions given in ISO/IEC 9804 apply. There is not a term “CCR connection end point” in ISO/IEC 9804. This term is used in this Technical Report to represent the point at which the CCR user recieved the service from CCR provider. 4 Symbols and abbreviations The abbreviations given in ISO/IEC 9804 apply. The abbreviation “LOTOS” is defined in ISO 8807. The following additional abbreviations are employed in this Technical Report. CCEPCCR Connection End Point CSPCCR Service Primitive Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) 2 © BSI 02-2000 5 Conventions An action for a combination of an event and a state not defined in the state table is left to implementer as “a local matter” by ISO/IEC 9804. Such undefined events are not specified in the LOTOS specification at all. This is not an exact representation of natural language specification, because deadlock will occur when the CCR user insists to taking an undefined event. Events not defined in this LOTOS specification are expected to be treated as a local matter. Clauses 7 through 11 of this Technical Report constitute LOTOS text. All explanatory descriptions are caught between “(*” and “*)”. symbols and are treated as comments of the LOTOS text. ISO/IEC 10731 (Service Conventions) is adopted, but the service primitive names and parameter names may be simplified or modified. 6 Introduction to the formal description 6.1 Model CCR service is modeled in Figure 1. 6.2 Structure The relationship among the processes are shown in Figure 2, and the relationship among the types are shown in Figure 3. In these figures, “*” means that “the definition has already listed above”. Figure 1 CCR service model Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) © BSI 02-20003 Figure 2 Relationship among the processes Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) 4 © BSI 02-2000 Figure 3 Relationship among the types Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) © BSI 02-20005 6.3 Service overview CCR service primitives and parameters are summarized in Table 1. Table 1 Service Primitives and Parameters The symbols in the table represent the following semantics; In the table, notation (=) indicates that the parameter value is semantically equal to the value to its left in the table. 7 Global constraints of the CCR service CCR service is represented in terms of type definitions and process definitions. The static attribute, i.e. the type of the service primitives and their parameters are described in type definitions. The behavior i.e. the service primitives issuing/receiving procedures are described in process definitions. Service Primitives and ParametersReqIndRspCnf C-BEGIN Atomic Action Identifier Masters Name Atomic Action Identifier Suffix Branch Identifier Superiors Name Branch Identifier Suffix User Data C-PREPARE User Data C-READY User Data C-COMMIT User Data C-ROLLBACK User Data C-RECOVER Recovery State Atomic Action Identifier Masters Name Atomic Action Identifier Suffix Branch Identifier Superiors Name Branch Identifier Suffix User Data M M M M U U U U U M M M M M U M(=) M(=) M(=) M(=) C(=) C(=) C(=) C(=) C(=) M(=) M(=) M(=) M(=) M(=) C(=) U U U M M M M M U C(=) C(=) C(=) M(=) M(=) M(=) M(=) M(=) C(=) blanknot applicable Cconditional Mmandatory Uuser option Licensed Copy: sheffieldun sheffieldun, na, Wed Nov 22 06:58:47 GMT+00:00 2006, Uncontrolled Copy, (c) BSI ISO/IEC TR 11589:1995(E) 6 © BSI 02-2000 Issuing and receiving of service primitives are represented as the events at the gates. Formal data types, FBoolean, Boolean, NaturalNumber, Element, Set, OctetString, NatRepresentations, and DecDigit are imported from LOTOS standard library. specification CCR_Service sup,sub : noexit library FBoolean, Boolean, NaturalNumber, Element, Set, OctetString endlib CCR service defines the behavior of one atomic action branch. Constraints beyond one atomic action branch are described in Annex A of ISO/IEC 9804, but they are not included in this Technical Report. behavior Branch sup,sub where process Branch sup,sub : noexit := aBranchsup,sub Branchsup,sub where CCR service are defined through the following three view points; behavior local at superior, not restricted by remote behavior, behavior local at subordinate, not restricted by remote behavior, and end-to-end relations which result from the exchange of information via the CCR service provider. These are described in SupCCEP, SubCCEP, and CCEPRelation respectively. process aBranchsup,sub : exit := SupCCEPsup |sub| CCEPRelationsup,sub |sub| SubCCEPsub where 8 Service primitives 8.1 Basic construction ISO/IEC 9804 defines 6 service primitives, C-BEGIN, C-PREPARE, C-READY, C-COMMIT, C-ROLLBACK, C-RECOVER. These are represented by the following names respectively; BEG(or Beg), PRP(or Prp), RDY(or Rdy), COMM(or Comm), ROLL(or Roll), REC(or Rec). Each of these service primitives has 4 primitive types, request, indication, response, confirm. These are represented as follows; req, ind, rsp, cnf. C-BEGIN service primitive may be concatenated with C-COMMIT service primitive or C-ROLLBACK service primitive. Therefore, these concatenated service primitives are included in the BasicCSP type. Parameter attributes (mandatory, conditional, user option etc.) are not treated in this Technical Report. See 6.3. type CSPName is Boolean, NaturalNumber sorts CSPName opns Beg, Prp, Rdy, Comm, Roll, Rec, Comm_plus_Beg, Roll_plus_Beg: CSPName _eq_, _ne