ISO/IEC 9040:1997
(Main)Information technology — Open Systems Interconnection — Virtual Terminal Basic Class Service
Information technology — Open Systems Interconnection — Virtual Terminal Basic Class Service
Technologies de l'information — Interconnexion de systèmes ouverts (OSI) — Service de classe de base de terminal virtuel
General Information
Relations
Standards Content (Sample)
ISO/IEC
INTERNATIONAL
9040
STANDARD
Second edition
1997-06-I 5
Information technology - Open Systems
- Virtual Terminal Basic
Interconnection
Class Service
In terconnexion de sys t&mes ouverts
Technologies de / ‘information -
(OSI) - Service de classe de base de terminal virtue/
Reference number
lSO/IEC 9040:1997(E)
---------------------- Page: 1 ----------------------
ISO/lEC 9040:1997(E)
Contents
1
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
1 Scope
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm8m8 1
2 Normative references
2
3 Definitions l mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
2
3.1 Global OSI definitions. .
2
.................
3.2 Association Control Service Element definitions
........................... 2
3.3 Virtual Terminal Service definitions
5
l mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmommmmmmm
4 Abbreviations
4.1General. 5
5
4.2 Modes of operation .
4.3 VTE model components . 5
............................................. 6
4.4Access-rules
6
5 Conventions mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
6
6 General features l mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
6
6.1lntroduction .
............. 6
6.2 Features of the Virtual Terminal Basic Class Service
................... 7
6.3 VT Environment (VTE) and VTE-parameters.
......................... 7
6.4 Virtual Terminal Environment Profiles
7
6.5 Dialogue Control .
l mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm 7
7 Communication facilities
7
7.1 Establishment facility .
7
........................................
7.2 Termination facility
7
7.3 Negotiation facility .
7
7.4 Data Transfer facility. .
.................................... 7
7.5 Delivery Control facility.
7.6 Dialogue Management facility . 7
7
7.7 Interrupt facilities .
7
7.8 Exception Reporting facility .
0 ISO/IEC 1997
All rights reserved. Unless otherwise specified no part of this publication may be reproduced
or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm, without permission in writing from the publisher.
ISO/lEC Copyright Office l Case Postale 56 l CH-1211 GenWe 20 . Switzerland
Printed in Switzerland
ii
---------------------- Page: 2 ----------------------
ISOAEC 9040:1997(E)
0 ISO/IEC
8 Modes of operation .mmmm.mmm.mmmmmmmmmmmmmmmm.m.mmmmmmmm. 8
8.lS-mode.8
8=2A=mode.8
9 Access-rules mmmmmmmmmmmmmmmmmmmmmmmmmm.mmmmommmmmmmmmm. 8
IO VT functional units l mmmmmmmmmmmmmmmmmmmmmmm.mmmmmmmm.mmm 9
10.1 Negotiation functional units . 9
10.2 Negotiated Release functional unit . IO
IO
10.3 Urgent Data functional unit. .
IO
10.4 Break functional unit. .
....................... IO
10.5 Enhanced Access-rules functional unit
IQ.6 Structured Control Objects functional unit. . IO
10.7 Blocks functional unit. . IO
10.8 Fields functional unit . IO
10.9 Reference Information Objects functional unit . IO
10.10 Ripple functional unit . IO
10.11 Exceptions functional unit . IO
10.12 Context Retention functional unit. . 11
11 VT Environment Profiles (VTE-profiles) l mmmmmmmmmmmmmmmmmm 11
12 The VTE Model .mmmmmmmmmmmmmmmmmmmmm.mmmm.mmmmmmmmmmmm 11
mmmm.mmmmmmmmm.mmmmmmmmmmmmmmmmmmmmmmmm 12
13 Display Objects
13.1 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
13.2 Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm 16
14 Control objects
14.1 CO structure facilities and related restrictions . 17
......
14.2 Standard control objects for fields and controlled data entry. 17
14.3 Standard control object for dynamic termination conditions . 18
14.4 Standard control object for notifying termination . 18
......................
14.5 Standard control object for echo control 18
14.6 Standard control object for ripple mode editing . 18
m.mmmmmmmmmmmmmmmmmmmmm.mm 18
15 Reference Information Objects
15.1 Structure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
15.2 Generation and use of RlOs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
mm.mmmmmmmm.mmmmm.mmmmm.mmmm.mmmmmm.mmmm 19
16 Device objects
17 VTE Parameters and directed graph . 19
19
17.1 Directed graph of VTE-parameters .
19
17.2 VTE consistency rules .
.......................... 22
18 Display Object VTE-parameters
18.1 PrimaryVTE-parameters. . .22
.............................. .22
18.2 Secondary VTE-parameters.
.25
18.3TertiaryVTE.parameter .
........................... 26
19 Operations on display objects
19.1 Addressing operations. . .26
19.2 Ripple operations . 30
19.3 Logical ripple operations . .31
31
19.4 Update operations .
19.5 Access control over display object. . 38
. . .
III
---------------------- Page: 3 ----------------------
0 ISO/IEC
ISO/IEC 9040: 1997(E)
..........................
20 Control object VTE-parameters 39
...........
20.1 Usage and effects of control object VTE-parameters 40
........... 41
20.2 Usage and effects of data element VTE-parameters.
................................. 41
20.3 Standard control objects.
21 Reference Information Object VTE-parameters. m . l l l l l . n l . l 46
46
21.1 Availability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21.2 VTE-parameters for RlOs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
l mmmmmmmmmmmmmmmmmmmmmmmmmmm.mmmmmm 47
22 Operations on RlOs
.............................................
22.1 Availability 47
22.2 Identification of RIO and RIO records . 47
................................... 47
22.3 RIO update operations
................................ 47
22.4 RlO reference operations.
23 Device object VTE-parameters l mm.mmmmmmmm.mmmmmmmmmm.mm 48
...................... 48
23.1 Default control object VTE-parameters
.......................... 48
23.2 Minimum Length VTE-parameters
23.3 Device object VTE-parameters for Attributes. . 48
............................. 49
23.4 Termination VTE-parameters.
23.5 Interaction between use of TCCO or FDCO and
........ 50
device object VTE-parameters.
24 Delivery control, synchronisation and net-effecting. . 50
...................................... 50
24.1 No delivery-control
..................................
24.2 Simple delivery-control. 51
...............................
24.3 Quarantine delivery-control 51
........................................ 51
24.4 implicit delivery.
........................
24.5 Update queues and priority handling 51
25 Communication Model l mm.mmmmmmmmmmm.m.m.mmmmmmmmmmmmm 53
l mmmmmmmm.m.mmmmmmmmmmmmmmmmmmmmmmmmmm 53
26 VT Services
27 VT service sequences . .mm.mm.m.m.mm.m . 55
27.1Phases . 55
27.2 Phase transitions . 55
......................
27.3 Ownership of the WAVAR access-right 56
27.4 Availability and usage conditions of VT services. . 56
27.5 Service collisions in A-mode . 57
28 Establishment facility m.mmmmmm.mmmm.mmmmm.mmmmmmmmmmmmmm 57
57
28.1 VT-ASSOCIATE service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.................................... 60
29 Termination facility
29.1Sewices . 60
................................... 60
29.2 VT-RELEASE service.
................................... 60
29.3 VT-U-ABORT service.
................................... 61
29.4 VT-P-ABORT service.
................................... 61
30 Negotiation facilities
30.1 Switch Profile negotiation. . 61
............................ 62
30.2 Multiple interaction negotiation.
30.3 Sequence control for multiple interaction negotiation . 65
31 Data Transfer facility .mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm 66
31 .I VT-DATA service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
iv
---------------------- Page: 4 ----------------------
ISO/IEC 9040:1997(E)
0 ISOllEC
67
32 Delivery Control facility l mmmmmmmmmmmmmmmmmmmmmmmmmmmmmm88
32.1 VT-DELIVER service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
32.2 VT-ACK-RECEIPT service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
68
33 Dialogue Management facility mmmmmmmmmmmmmmmmmmmmmmmmmmm
33.1 VT-GIVE-TOKENS service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
33.2 VT-REQUEST-TOKENS service . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
68
34 Destructive Interrupt facility l mmmmmmmmmmmmmmmmmmmmmmmmmmmm
34.1 VT-BREAK service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
69
l mmmmmmmmmmmmmmmmmmmmmmmmmmmm
35 Exception reporting facility
35.1 VT-P-EXCEPTION service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69
71
l mmmmmmmmmmmmmmmmmmmmmmmmmmmmm
Annex A Default VTE-profiles
......................... 71
A.1 Introduction to VTE-profile definitions
......................... 71
A.2 Notation for definition of VTE-profiles
....................... 72
A.3 S-mode Default VTE-profile, vt-b-spr-sd
.......................
72
A.4 A-mode Default VTE-profile, vt-b-spr-ad
74
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
Annex B Explanatory notes
...................... .74
B.l Types of VT communication supported.
................. 74
B.2 Aid to understanding the role of display objects
....................... 74
8.3 Relation of update-window to buffering.
................................. .74
B.4 Control object semantics
..7 4
8.5Echoing .
..7 4
B.6Echocontrol
..........................................
................................... .75
B.7 Echo control algorithm
................................... .75
B.8 Termination conditions
........................... 75
B.9 Synchronisation of update delivery
............................ 76
B.10 Multiple Interaction Negotiation
............................. .76
B.ll Semantics of display objects
........................................... .76
B.12 Repertoires
............. 76
B.13 Use of IS0 6429 Additional Controls in repertoires
......................... .77
B.14 Font Assignment VTE-parameters
..........................................
.77
B.15 Net-effecting
....................................... .77
B.16 Interrupt facilities
..................................... .77
B.17 Emphasis attribute.
........... 79
B.18 Supplementary explanatory material on field facilities
.......... 83
B.19 Supplementary explanatory material on block facilities
................. 85
Annex C ASN.1 OBJECT IDENTIFIER values.
................. 85
C.l For identification of this International Standard.
.................
85
C.2 For identification of attribute assignment types
n n n n n n n n n n n n n n n n n n n n n n 86
Annex D Size of urgent control objects
V
---------------------- Page: 5 ----------------------
lSO/lEC 9040: 1997(E) 0 ISO/IEC
Foreword
IS0 (the International Organization for Standardization) and IEC (the International
Electrotechnical Commission) form the specialized system for worldwide stand-
ardization. National bodies that are members of IS0 and IEC participate in the
development of International Standards through technical committees established by
the respective organization to deal with particular fields of technical activity. IS0 and
IEC technical committees collaborate in fields of mutual interest. Other international
organizations, governmental and non-governmental, in liaison with IS0 and IEC, also
take part in the work.
In the field of information technology, IS0 and IEC have established a joint technical
committee, ISO/IEC JTCl . Draft International Standards adopted by the joint technical
committee are circulated to national bodies for voting. Publication as an International
Standard requires approval by at least 75% of the national bodies casting a vote.
International Standard ISO/IEC 9040 was prepared by Joint Technical Committee
ISO/IEC JTCl , information technology, Subcommittee SC21, Open systems intercon-
nection, data management and open distributed processing.
This second edition cancels and replaces the first edition (IS0 9040:1990), which has
been technically revised. It also incorporates Amendment 2:1992, Technical Corri-
gendum 1:1991, Technical Corrigendum 2:1992 and Technical Corrigendum 3:1993.
Annexes
A and C form an integral part of this lnte rnationa ,I Standard.
Annexes B and D are for i nformation on .
IY
vi
---------------------- Page: 6 ----------------------
0 lSO/IEC ISOAEC 9040:1997(E)
Introduction
This lnternational Standard is one of a set of standards produced to facilitate the
interconnection of computer systems. It is related to other International Standards in
the set as defined in the Reference Model for Open Systems Interconnection (lSO/lEC
7498-l). The Reference Model subdivides the area of standardization into a series of
layers of specification, each of manageable size.
The purpose of this International Standard (lSO/lEC 9040) is to define the service
provided in the Application Layer by the Virtual Terminal (VT) Basic Class Service.
The Virtual Terminal Basic Class Service is provided by the Virtual Terminal Basic
Class Protocol specified in ISO/IEC 9041 and making use of services available from
the Association Control Service Element (ACSE) in the Application Layer and the
Presentation Service.
vii
---------------------- Page: 7 ----------------------
This page intentionally left blank
---------------------- Page: 8 ----------------------
ISOnEC 9040 : 1997(E)
INTERNATIONAL STANDARD 0 ISO/IEC
Information technology - Open Systems Interconnection -
Virtual Terminal Basic Class Service
of ASN.l Object Identifiers for the objects defined in this
1 Scope
International Standard and for use in a register of virtual
terminal objects.
This International Standard defines, in an abstract way, the
externally visible Basic Class Virtual Terminal Service within
This International Standard does not specify individual imple-
the OSI Application Layer in terms of
mentations or products, nor does it constrain the implementa-
a) a model defining the interaction between users of the
tion of entities and interfaces within a computer system. There
service;
is, therefore, no requirement for conformance to this Interna-
tional Standard.
b) the primitive actions and events of the service;
c) the parameter data associated with each primitive action
This International Standard applies to interactive applications
and event;
requiring terminal oriented communication expressed in terms
of the transmission and manipulation of graphical images
d) the relationship between, and the valid sequences of, these
having the following characteristics:
actions and events.
e) the images are composed of character-box graphic ele-
The service defined in this International Standard is that which
ments organised into a one, two or three dimensional
is provided by the OSI Basic Class Virtual Terminal Protocol
structure;
(in conjunction with the Association Control Sewice Element
and the Presentation Service) and which may be used by any
f) attributes may be associated with any graphic element to
user including other Application Service Elements. The rela- qualify its mode of display.
tionship between the standards for Virtual Terminal Service,
Virtual Terminal Protocol, ACSE, Presentation Layer Service Control information for the communication can be modelled
and the user of the Virtual Terminal Service is shown in
using virtual terminal control objects, and multiple devices can
figure 1. be modelled using virtual terminal device objects linked to the
other virtual terminal objects.
This International Standard also defines two standard default
virtual terminal environment profiles and describes the form of
registered virtual terminal environment profiles and control
2 Normative references
objects. Virtual terminal environment profiles define sets of
virtual terminal environment parameters for use in the estab
The following standards contain provisions which, through
lishment of virtual terminal associations and subsequent ne-
reference in this text, constitute provisions of this International
gotiation. This International Standard also defines a structure
Standard. At the time of publication, the editions indicated
were valid. All standards are subject to revision, and parties to
agreements based on this International Standard are encour-
VT-user
aged to investigate the possibility of applying the most recent
Virtual Terminal Service
editions of the standards indicated below. Members of IEC and
IS0 maintain registers of currently valid International Stand-
Crprovides service
ards.
1 based on service provided
ISO/IEC 646: 1991, lnfommtion technology - IS0 7-bit coded
by ACSE service
character set for information interchange.
ACSE
and Presentation Service ISOIIEC 2022:1994, Information technology - Character
Presentation
code structure and extension techniques.
Protocol
I
ISO/IEC 2375: 1985, Data processing - Procedure for regis-
tra tion of escape sequences.
ISO/IEC 6429: 1992, lnfotmation technology - Control func-
Figure 1 - Relationship of this International Standard
tions for coded character sets.
to other OS1 Application Layer Standards
1
---------------------- Page: 9 ----------------------
ISO/IEC 9040:1997(E) 0 ISOAEC
ISO/IEC 7498.1:1994, information technology - Open Sys- k) confirm (primitive);
tems interconnection - Basic Reference Model : The Basic
I) confirmed service;
Model.
m) non-confirmed service;
ISO/IEC 8649: 1996, information technology - Open Systems
n) provider-initiated service.
- Sewice definition for Association Control
Interconnection
Service Element.
3.2 Association Control Service Element
ISOIIEC 8824: 1990, information technology - Open Systems definitions
interconnection - Specification for Abstract Syntax Notation
One (ASN. I).
This International Standard makes use of the following terms
defined in ISO/IEC 8649:
ISO/IEC 8825: 1990, information technology - Open Systems
a) application association;
Interconnection - Specikation of Basic Encoding Rules for
b) application entity title;
Abstract Syntax Notation One (ASN. I).
c) application control service element (ACSE).
ISOIIEC 9041-I: 1997, Information technology - Open Sys-
tems interconnection - Virtual Terminal Basic Class Protocol
- Part I: Specification. 3.3 Virtual Terminal Service definitions
ISO/IEC 9834.4:1991, information technology - Open Sys- For the purposes of this International Standard, the following
tems interconnection - Procedures for the operation of OS1
definitions apply:
Registration Authorities - Part 4: Register of VTE Profiles
3.3.1 VT-user: A user of the Virtual Terminal Sewice.
ISOIIEC 9834-5:1991, information technology - Open Sys-
tems interconnection - Procedures for the operation of OS1
3.3.2 Application VT-user: The unique VT-user which can
Registration Authorities - Part 5: Register of VT Control Object
update the FDCO; if either VT-user can update this control
Definitions
object then neither VT-user has this designation.
ISOII EC 10731: 1994, information technology - Open Sys-
3.3.3 Terminal VT-user: If one VT-user has the designation
tems interconnection -Basic Reference Model- Conventions
Application VT-user then the peer VT-user has the designation
for the Definition of OS1 Services.
Terminal VT-user.
The International Register of Coded Character Sets to be used
3.3.4 character-repertoire: A set of objects which can be
with Escape Sequences. ‘)
represented by primary attribute values; one such object,
represented by its primary attribute value, can occupy an array
element in a display object when the character-repertoire is in
3 Definitions
use for that array element. A control object of character-string
category also has an associated repertoire.
3.1 Global OSI definitions
3.3.5 character-box graphic element: An atomic element of
a character-repertoire where use of the repertoire has been
This International Standard is based on the concepts devel-
agreed through negotiation by the VT-users.
oped in ISO/IEC 7498-l and makes use of the following terms
defined in it:
3.3.6 primary attribute: The attribute of an array element of
a) application entity;
a display object which is a coded representation of the char-
acter-box graphic element assigned to that array element.
b) Application Layer;
c) service data unit;
3.3.7 secondary attribute: The secondary attributes of an
d) service access point.
array element comprise the character-repertoire, see 3.3.4,
and the rendition attributes.
It also makes use of the following terms defined in ISO/IEC
10731:
3.3.8 rendition attributes: Those secondary attributes of an
array element which qualify the character-box graphic element
e) service primitive;
and provide information specifying how it is intended to be
f) service provider;
presented.
g) primitive;
3.3.9 explicit modal default: The value for a secondary
h) request (primitive);
attribute, defined in a VTE, which is used by the text operation
i) indication (primitive);
to update an array element if no other value is provided or
j) response (primitive); already present; may also be used by the erase operation.
1) Available from the European Computer Manufacturers Association (ECMA), 114 rue du Rh6ne, CH-1204 GetWe, Switzerland.
---------------------- Page: 10 ----------------------
0 ISOllEC lSO/IEC 9040:1997(E)
3.3.10 display object: An abstract object, defined in this
3.3.23 VTE-parameter: An individual parameter of a VTE.
International Standard, for modelling the exchange of graphic Each VTE-parameter is given a unique name in the service
information. It consists of a number of components, see 13.1.
which is used as the identifier for the VTE-parameter.
3.3.11 array element: That part of a display object which can
3.3.24 full-VTE: A VTE that is a complete directed graph of
hold one character-box graphic element including its primary
VTE-parameters in which all node parameters and terminal
and secondary attribute values.
leaf parameters implied by all existing nodes from the root of
the tree have values.
3.3.12 primitive display pointer: A set of one to three coor-
dinate values which identify a particular element in a display
3.3.25 VT-context-value: A collective term for the set of
object.
object instances, their assigned values and the current-VTE
for a particular VT-association. A VT-context-value exists only
3.3.13 extended display pointer: A set of two to four coor-
during the lifetime of the VT-association and is normally
dinate values which identify a particular array element in a
changing continuously during this time interval.
block defined on a display object.
3.3.26 reset-context: The VT-context-value which will result
3.3.14 display pointer: Used to refer to either the primitive
after a VT-BREAK service. This context value is the context
display pointer or the extended display pointer; whether or not
after the last successful current-VTE establishment; all objects
blocks are in use determines which is implied.
will have their initial values. If no full-VTE has been estab
lished, there is no reset-context.
3.3.15 logical pointer: A set of two or three coordinate values
which identify a particular array element in a field defined on
3.3.27 WAVAR access-right: An access-right which can be
a display object.
held by at most one VT-user at any time. It is used to ensure
NOTE -The primitive display pointer and extended display pointer do that control and display objects cannot be updated by both
not both exist simultaneously. However, when a logical pointer exists,
VT-users simultaneously.
it is in addition to either a display pointer or an extended display
pointer.
3.3.28 access-rule: A characteristic defined for an object in
a VTE which determines which VT-users can update the object
3.3.16 control object: An abstract object, of a type defined
at a particular time.
in generic terms in this International Standard, for modelling
the exchange of unstructured information.
3.3.29 net-effecting: The conversion of a sequence of items,
NOTE - The primary application of a control object is for modelling representing the content of one or more update operations
the exchange of information of a control nature, as understood by the
(see 24.3), into a different, usually shorter sequence, which
VT-users; the VT Service does not constrain the interpretation of this
results in the same final states of the objects being updated.
information.
3.330 concatenation: The connection of a sequence of
3.3.17 device object: An abstract object used to model cer-
queued update items (see 24.3) to form a single, new, queued
tain logical characteristics of real devices, and to link the
update item.
various objects of a virtual terminal environment together
and/or to real devices.
3.3.31 segmentation: The division of a single, queued up-
date ite m (see 24.3) into a sequence of
new, queued update
3.3.18 object updating device: A real device capable of
items.
generating values which (possibly after undergoing a transfor-
mation) are used by one of the peer VT-users to update either
3.3.32 A-mode (Asynchronous mode): A mode of opera-
a display object or control object (or possibly both).
tion using two display objects, one of which is updatable by
the VT-user which initiated the VT-association and the other
3.3.19 VT-association: An application association between
by the peer VT-user.
two peer VT-users.
3.3.33 S-mode (Synchronous mode): A mode of operation
3.320 VT-environment (VTE): A set of parameters that to-
using one two-way-alternate dialogue supporting one display
gether define the data structuring and operational charac-
object; at any time, the display object may only be updated by
teristics for a particular VT-association. The VTE exists only
the single VT-user which owns the WAVAR access-right.
during the lifetime of that VT-association. The parameters of
the set are mutually related by a directed graph structure. The
3.3.34 service: A distinct part of the total VT Service that is
VTE may be modified during the existence of the VT-associa-
composed of a sequence of primitives taken from the set
tion by negotiation.
{request primitive, indication primitive, response primitive,
confirm primitive}.
3.3.21 current-VTE: The single VIE which exists during the
Data Handling phase or the Negotiation Quiescent phase; in
3.3.35 sequenced service: A Service for which an indication
the Data Handling phase it is a full-VTE whereas in the
(or confirm) primitive resulting from a corresponding request
Negotiation Quiescent phase it is not a full-VTE.
(or response) primitive is initiated in sequence with all pre-
3.3.22 draft-VTE: The VTE, if any, under negotiation. During viously initiated sequenced indications (or confirms) and their
negotiation, the draft-VTE is not necessarily a full-VTE. corresponding requests (or responses).
3
---------------------- Page: 11 ----------------------
0 ISOllEC
ISO/IEC 9040:1997(E)
3.3.36 non-sequenced service: A Service for which an indi- 3.3.49 VTE-profile argument: An argument of a parameter-
ised VTE-profile which must be given a value to enable a
cation (or confirm) primitive resulting from a corresponding
request (or response) primitive is not necessarily initiated in full-VTE to be made from the VTE-profile. It can be a normal
VTE-profile argument or a special VTE-profile argument. Each
sequence with all previously initiated indications (or confirma-
tions) and their corresponding requests (or responses). registered VTE-profile defines the applicable arguments and
their semantics.
3.3.37 conditionally sequenced service: A Service for
which 3.3.50 normal VTE-profile argument: A VTEprofile argu-
ment which corresponds exactly to a VTE-parameter and
certain values ‘for parameters of the service primitives result
a)
assumes the same identifier. A VTE-profile may also specify
in sequenced operation, and
that other VTE-parameters are also defined by the value of
b) other values for parameters of the service primit
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.