ETSI ETS 300 134 ed.1 (1992-12)
Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities Application Part (TCAP)
Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities Application Part (TCAP)
T/S 43-05
Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija CCITT št. 7 - Aplikacijski del za transakcijske zmožnosti (TCAP)
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST ETS 300 134:199
01-PDrHF-199
Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija CCITT št. 7 -
Aplikacijski del za transakcijske zmožnosti (TCAP)
Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction
Capabilities Application Part (TCAP)
Ta slovenski standard je istoveten z: ETS 300 134 E1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
SIST ETS 300 134:199 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
PSIST ETS 300 134:1996
---------------------- Page: 2 ----------------------
PSIST ETS 300 134:1996
EUROPEAN ETS 300 134
TELECOMMUNICATION December 1992
STANDARD
Source: ETSI TC-SPS Reference: T/S 43-05
ICS: 33.080
ISDN, CCITT SS No.7, TCAP
Key words:
Integrated Services Digital Network (ISDN);
CCITT Signalling System No.7
Transaction Capabilities Application Part (TCAP)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1992. All rights reserved.
New presentation - see History box
---------------------- Page: 3 ----------------------
PSIST ETS 300 134:1996
Page 2
ETS 300 134: December 1992
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
---------------------- Page: 4 ----------------------
PSIST ETS 300 134:1996
Page 3
ETS 300 134: December 1992
Contents
Foreword.5
1 Scope .7
2 Normative references .7
3 General exceptions and clarifications to CCITT Recommendations Q.771 to Q.775.7
3.1 Support of TC by terminal equipment.7
3.2 Services assumed from a connectionless network layer .7
3.3 TC based on a connection-oriented network.8
3.4 Support of real-time/less real-time sensitive data.8
3.5 Management of address information by the Transaction sub-layer .8
4 Specific exceptions and clarifications to CCITT Recommendation Q.771 .8
4.1 Primitives for dialogue handling - Q.771, subclause 3.1.1, table 1/Q.771 .9
4.2 Primitives for component handling - Q.771, subclause 3.1.1, table 2/Q.771 .9
4.3 Overview of the Component sub-layer primitives - Q.771, subclause 3.1.1 .9
4.4 Definition of parameters within dialogue handling primitives - Q.771, subclause 3.1.2.1.9
4.4.1 Address parameters.9
4.4.2 "Components Present" parameter.9
4.4.3 "Parameters" parameter .9
4.4.4 "Quality of Service" parameter .9
4.4.5 "Report Cause" parameter.9
4.5 Dialogue facilities - Q.771, subclause 3.1.2.2.10
4.5.1 TC-NOTICE.10
4.5.2 Quality of Service.10
4.6 Unstructured dialogue - Q.771, subclause 3.1.2.2.1, table 3/Q.771.11
4.7 End of a dialogue - Q.771, subclause 3.1.2.2.2.3.b .11
4.8 Report of success primitives - Q.771, subclause 3.1.3.3, table 9/Q.771.12
4.9 Cancel of an operation - Q.771, subclause 3.1.3.6 & figure 8/Q.771.12
4.10 Reject of a component by the Component sub-layer - Q.771, subclause 3.1.4.1 .12
4.11 Primitives for transaction handling - Q.771, subclause 3.2.1, table 15/Q.771 .12
4.12 Definition of parameters within Transaction sub-layer primitives - Q.771, subclause
3.2.1.12
4.12.1 "Quality of Service" parameter .12
4.12.2 "Reason" parameter. 12
4.12.3 "Report Cause" parameter.13
4.13 Transaction facilities - Q.771, subclauses 3.2.3 - 3.2.5 .13
4.13.1 TR-NOTICE.13
4.13.2 "Quality of Service". 13
4.14 Transaction Abort by the TR-user - Q.771, subclause 3.2.5.3.14
5 Specific exceptions and clarifications to CCITT Recommendation Q.772 .15
5.1 Example reasons for generating P-ABORT causes - Q.772, subclause 2.3.15
5.2 Operation code - Q.772, subclause 3.4 .16
5.3 Example reasons for generating General Problem reject components - Q.772,
subclause 3.8.1.16
5.4 Mistyped parameters - Q.772, subclauses 3.8.2.3, 3.8.3.3 & 3.8.4.5.16
5.4.1 Invoke problem - mistyped parameter.17
5.4.2 Return Result problem - mistyped parameter.17
5.4.3 Return Error problem - mistyped parameter .17
6 Specific exceptions and clarifications to CCITT Recommendation Q.773 .17
6.1 Structure of the Transaction Portion - Q.773, subclause 5.1.17
---------------------- Page: 5 ----------------------
PSIST ETS 300 134:1996
Page 4
ETS 300 134: December 1992
6.2 Structure of the Component Portion - Q.773, subclause 6.1.17
6.3 Parameters Tag - Q.773, subclause 6.1, tables 16-18/Q.773.17
6.4 Reject Component - Q.773, subclause 6.1, table 19/Q.773 .19
6.5 Corrections to the Abstract Syntax Notation (ASN) - Q.773 Annex A .19
7 Specific exceptions and clarifications to CCITT Recommendation Q.774.22
7.1 Delivery of components to the remote TC-user - Q.774, subclause 3.2.1.1.1 .22
7.2 Operation classes - CANCEL - Q.774, subclause 3.2.1.1.3 .22
7.3 Operation classes - Invocation Time-out - Q.774, subclause 3.2.1.1.3.22
7.4 Dialogue control - Q.774, subclause 3.2.2.1.22
7.5 Action taken on protocol errors in the Component Portion - Q.774 table 4/Q.774 .22
7.6 Abnormal procedures relating to transaction control - Q.774, subclause 3.3.4.23
8 Exceptions and clarifications to CCITT Recommendation Q.774 Annex A (SDLs) .23
8.1 Transaction sub-layer - Q.774 figure A-3/Q.774 .23
8.1.1 Handling of the SCCP N-NOTICE indication primitive - Q.774 figure A-
3/Q.774 Sheets 1/6, 3/6 and 4/6 .23
8.1.2 Receipt of an ABORT message - Q.774 figure A-3/Q.774 Sheet 3/6.23
8.1.3 Abnormal situations - Q.774 figure A-3/Q.774 Sheet 6/6 .24
8.2 Dialogue handling - Q.774 figure A-4/Q.774 .24
8.2.1 Handling of the TR-NOTICE indication primitive - figure A-4/Q.774 sheet
1/2 .24
8.2.2 Terminating state machines at the end of a dialogue - figure A-4/Q.774
sheets 1/2 & 2/2.24
8.3 Component co-ordinator - Q.774 figure A-5/Q.774.24
8.3.1 Receipt of a TC-U-Cancel request primitive - figure A-5/Q.774 Sheet 1/4 .24
8.3.2 Validation of invocation state machines - figure A-5/Q.774 Sheets 2/4 &
3/4 .24
8.3.3 Return Error Component - figure A-5/Q.774 Sheet 2/4 .24
8.3.4 Discard of all subsequent components in a message - figure A-5/Q.774
Sheet 2/4.24
8.3.5 Receipt of a malformed Reject Component - figure A-5/Q.774 Sheet 2/4.24
8.3.6 Reporting of class 4 invocation time-outs - figure A-6/Q.774 Sheet 6/6.34
9 Specific exceptions and clarifications to CCITT Recommendation Q.775.36
9.1 Reject of a component by TC - Q.775, subclauses 2.4.4 & 3.2.1.3 .36
9.2 Use of the external data type for UserAbortInformation (see subclause 6.5) .36
Annex A (informative): Symbols and abbreviations .37
Annex B (informative): Bibliography.38
History .39
---------------------- Page: 6 ----------------------
PSIST ETS 300 134:1996
Page 5
ETS 300 134: December 1992
Foreword
This European Telecommunication Standard (ETS) has been produced by the Signalling Protocols &
Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).
This ETS details exceptions and clarifications to CCITT Recommendations Q.771-Q.775 [1] - [5] defining
the Transaction Capabilities (TC) of the Transaction Capabilities Application Part (TCAP) for inter-network
dialogues on services such as the pan European Cellular Digital Radio System and Integrated Services
Digital Network (ISDN).
---------------------- Page: 7 ----------------------
PSIST ETS 300 134:1996
Page 6
ETS 300 134: December 1992
Blank page
---------------------- Page: 8 ----------------------
PSIST ETS 300 134:1996
Page 7
ETS 300 134: December 1992
1 Scope
This ETS defines the Transaction Capabilities (TC) signalling requirements in and between networks, for
non circuit related services which use the CCITT Signalling System No.7, for inter-network dialogues. Only
those parts of TC need to be provided which are used by the above services.
This standard is based on CCITT Recommendations Q.771 to Q.775, normative references [1] to [5], as
specified in the 1988 Blue Book. The requirements of these recommendations shall apply unless modified
by the exception statements and clarifications contained in this standard.
For historical reasons, the terms TC and TCAP are used interchangeably.
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These normative
references are cited at the appropriate places in the text and the publications listed hereafter. For dated
references subsequent amendments to, or revisions of, any of these publications apply to this ETS only
when incorporated in it by amendment or revision. For undated references the latest edition of the
publication referred to applies.
[1] CCITT Recommendation Q.771 (1988): "Specifications of Signalling System
No.7; Functional description of transaction capabilities".
[2] CCITT Recommendation Q.772 (1988): "Specifications of Signalling System
No.7; Transaction capabilities information element definitions".
[3] CCITT Recommendation Q.773 (1988): "Specifications of Signalling System
No.7; Transaction capabilities formats and encoding".
[4] CCITT Recommendation Q.774 (1988): "Specifications of Signalling System
No.7; Transaction capabilities procedures".
[5] CCITT Recommendation Q.775 (1988): "Specifications of Signalling System
No.7; Guidelines for using transaction capabilities".
[6] CCITT Recommendation Q.711 (1988): "Specifications of Signalling System
No.7; Functional description of the signalling connection control part".
[7] CCITT Recommendation X.229 (1988): "Open Systems Interconnection (OSI);
Remote operations: Protocol specification".
[8] CCITT Recommendation X.208 (1988): "Open Systems Interconnection (OSI);
Model and Notation: Service definition: Specification of Abstract Syntax Notation
One (ASN.1)".
3 General exceptions and clarifications to CCITT Recommendations Q.771 to
Q.775
3.1 Support of TC by terminal equipment
The support of TC by terminal equipment is outside the scope of this ETS.
3.2 Services assumed from a connectionless network layer
There is no requirement for TC to work over any network layer other than CCITT Signalling System No.7
Message Transfer Part (MTP) or Signalling Connection Control Part (SCCP).
The services assumed from the SCCP are provided via the N-UNITDATA and N-NOTICE primitives.
Specific details of how TCAP processes the N-NOTICE indication are given in the following sections.
---------------------- Page: 9 ----------------------
PSIST ETS 300 134:1996
Page 8
ETS 300 134: December 1992
It is also assumed that the N-UNITDATA indication primitive shall contain the SCCP "Return Option" and
"Sequence Control" parameters in addition to those parameters defined in the CCITT Recommendation
Q.711 [6].
3.3 TC based on a connection-oriented network
TC based on a connection-oriented network service is outside the scope of this ETS.
3.4 Support of real-time/less real-time sensitive data
All data transfer by TC shall be considered as real-time sensitive.
3.5 Management of address information by the Transaction sub-layer
The procedures relating to address information (e.g. CCITT Recommendation Q.774 [4], subclause 3.3)
are undefined in CCITT Recommendations Q.771 to Q.775 [1] to [5]. Although TC does not convey
address information in any of its messages, the Transaction sub-layer must provide any necessary
address information to the SCCP in every N-UNITDATA request primitive (e.g. global title and sub-system
number with a "Global Title routing required" indication).
The procedures are intended to be analogous with those relating to Transaction IDs:
i) The calling address information received in the first N-UNITDATA indication primitive in
each direction of a transaction, shall be used as called address in all subsequent
messages to the peer within that transaction.
ii) Each SCCP user is responsible for providing its own address in the calling address
information of every N-UNITDATA request primitive. This shall not change during the
life of the transaction and shall be in a form which can be used by the SCCP to return
messages, e.g. from the distant node.
iii) Once the transaction is established, the address information shall remain constant for
the life of the transaction. TCAP shall use the address information for that transaction
rather than that received in subsequent N-UNITDATA indication primitives for that
transaction.
NOTE 1: In particular the above rules allow the B-SCCP-User to provide its own address as
calling address information instead of the received called address information in the
first N-UNITDATA indication primitive.
NOTE 2: The encoding of calling and called party address parameter in a SCCP message must
follow the rules defined in CCITT Recommendation Q.713 (1992) (see also ETS 300
009).
4 Specific exceptions and clarifications to CCITT Recommendation Q.771
NOTE: The following notation is used in the tables included in this Clause:
M indicates a mandatory parameter;
O indicates an optional parameter;
(=) indicates that the parameter must have the same value in a request
primitive and in the corresponding indication primitive.
---------------------- Page: 10 ----------------------
PSIST ETS 300 134:1996
Page 9
ETS 300 134: December 1992
4.1 Primitives for dialogue handling - Q.771, subclause 3.1.1, table 1/Q.771
In addition to the dialogue handling primitives identified in table 1/Q.771, the Component sub-layer shall
support the TC-NOTICE indication primitive.
NOTE: TC-NOTICE informs the TC-user that the service provider has been unable to provide
the requested service.
4.2 Primitives for component handling - Q.771, subclause 3.1.1, table 2/Q.771
The TC-R-REJECT in table 2/Q.771 shall be used to inform the local TC-user that a component was
rejected by the remote component sub-layer.
4.3 Overview of the Component sub-layer primitives - Q.771, subclause 3.1.1
The abstract syntax of parameters included in primitives must contain sufficient information to enable the
concrete syntax to be encoded from the parameters supplied e.g. whether an operation/error code is local
or global.
4.4 Definition of parameters within dialogue handling primitives - Q.771, subclause 3.1.2.1
The following exceptions and clarifications are made to the parameters within the Component sub-layer
dialogue handling primitives.
4.4.1 Address parameters
In addition to the CCITT definition of address parameters, it shall also indicate the address type, for
example a global title and sub-system number.
4.4.2 "Components Present" parameter
The reference to Q.771, subclause 3.1.3.8 should read as Q.771, subclause 3.1.3.7.
The "Components Present" parameter indicates whether or not components are present. If components
are present they are delivered by TC to the TC-user in the order received from the originating TC-user.
4.4.3 "Parameters" parameter
The "Parameters" parameter is not used in any dialogue handling primitive.
4.4.4 "Quality of Service" parameter
The Quality of Service parameter shall indicate the SCCP sequence control and return option, for the
SCCP connectionless network layer service as defined in CCITT Recommendation Q.711 [6].
4.4.5 "Report Cause" parameter
The "Report Cause" parameter contains information indicating the reason for the exception report, for
example that the message was returned by the SCCP with the reason as specified in CCITT
Recommendation Q.711 [6]. This parameter is in addition to those defined in Q.771, subclause 3.1.2.1,
and is required for the TC-NOTICE indication primitive.
---------------------- Page: 11 ----------------------
PSIST ETS 300 134:1996
Page 10
ETS 300 134: December 1992
4.5 Dialogue facilities - Q.771, subclause 3.1.2.2
4.5.1 TC-NOTICE
In addition to the dialogue facilities mentioned in Q.771, subclause 3.1.2.2, the ability for TC-users to be
notified of non-delivery of user data shall be provided by the TC-NOTICE indication primitive.
A TC-NOTICE indication primitive is only passed to the TC-user if the service requested cannot be
provided (i.e. the network layer cannot deliver the message to the remote node) and the TC-user
requested the return option in the "Quality of Service" parameter.
Table 1: TC-NOTICE primitive
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ ‡ Primitive : TC-NOTICE ‡
‡ Parameter ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ ‡ Indication ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Dialogue ID ‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Report Cause ‡ M ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
4.5.2 Quality of Service
The "Quality of Service" parameter shall be optionally provided in all TC dialogue request primitives and not
just the TC-BEGIN primitive as stated in Q.771.
In addition to the parameters defined by CCITT for the TC dialogue primitives (see Q.771 tables 4/Q.771,
5/Q.771, 6/Q.771, 7/Q.771 and 14/Q.771) the "Quality of Service" parameter shall be provided as
indicated below, in table 2.
Table 2: "Quality of Service" requirements for TC-primitives
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ Quality of Service ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-primitive ‡ Table ‡ Request ‡ Indication ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-BEGIN ‡ 4/Q.771 ‡ O (NOTE)‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-CONTINUE ‡ 5/Q.771 ‡ O (NOTE)‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-END ‡ 6/Q.771 ‡ O (NOTE)‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-U-ABORT ‡ 7/Q.771 ‡ O (NOTE)‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-P-ABORT ‡14/Q.771 ‡ ‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜·
‡ TC-NOTICE ‡ ‡ ‡ ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜�
NOTE: When the "Quality of Service" parameter is not present in a dialogue request primitive,
the Component sub-layer shall not request a quality of service to the Transaction sub-
layer. The Transaction sub-layer shall request SCCP Class 0 and no return option to
the SCCP.
---------------------- Page: 12 ----------------------
PSIST ETS 300 134:1996
Page 11
ETS 300 134: December 1992
4.6 Unstructured dialogue - Q.771, subclause 3.1.2.2.1, table 3/Q.771
The "Components Present" parameter should not be present in the TC-UNI request primitive. Table 3
shows the parameters that are required in the TC-UNI request and indication primitive.
Table 3: TC-UNI primitives
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ ‡ Primitive : TC-UNI ‡
‡ Parameter ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ ‡ Request ‡ Indication ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Quality of Service ‡ O (NOTE)‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Destination Address ‡ M ‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Originating Address ‡ M ‡ M (=) ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Dialogue ID ‡ M ‡ ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Components Present ‡ ‡ M ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
NOTE: When the "Quality of Service" parameter is not present in a dialogue request primitive,
the Component sub-layer shall not request a quality of service to the Transaction sub-
layer. The Transaction sub-layer shall request SCCP class 0 and no return option to
the SCCP.
4.7 End of a dialogue - Q.771, subclause 3.1.2.2.2.3.b
Components are delivered to the Component sub-layer and not directly to the Transaction sub-layer as
stated in the first bullet item of Q.771, subclause 3.1.2.2.2.3.b. The text should therefore read:
"The basic scenario uses the TC-END primitives for two purposes:
- delivery of any component(s) for which transmission is pending;
- indication that no more components will be exchanged for this dialogue in either
direction."
---------------------- Page: 13 ----------------------
PSIST ETS 300 134:1996
Page 12
ETS 300 134: December 1992
4.8 Report of success primitives - Q.771, subclause 3.1.3.3, table 9/Q.771
The operation code in the Return Result (Last/Not Last) components shall be included in both the request
and indication primitives as shown in table 4.
Table 4: Report of success primitives
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ ‡ Primitive ‡
‡ ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Parameter ‡ TC-RESULT-L ‡ TC-RESULT-L ‡
‡ ‡ TC-RESULT-NL ‡ TC-RESULT-NL ‡
‡ ‡ Request ‡ Indication ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Dialogue ID ‡ M ‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Invoke ID ‡ M ‡ M (=) ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Operation ‡ O (NOTE)‡ O (=) ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Parameters ‡ O ‡ O (=) ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Last Component ‡ ‡ M ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
NOTE: Mandatory when the primitive contains the "Parameters" parameter.
4.9 Cancel of an operation - Q.771, subclause 3.1.3.6 & figure 8/Q.771
The invocation timer is run for all classes as a local matter, but the reporting for class 4 operations is an
implementation dependent matter.
4.10 Reject of a component by the Component sub-layer - Q.771, subclause 3.1.4.1
When an invalid or corrupt component is received in an END message, it is not possible to return a
REJECT component and so the remote TC-user is not informed.
4.11 Primitives for transaction handling - Q.771, subclause 3.2.1, table 15/Q.771
In addition to the transaction handling primitives identified in table 15/Q.771, the Transaction sub-layer shall
support the TR-NOTICE indication primitive:
NOTE: TR-NOTICE informs the TR-user that the service provider has been unable to provide
the requested service.
4.12 Definition of parameters within Transaction sub-layer primitives - Q.771, subclause 3.2.1
The following exceptions and clarifications are made to the parameters within the Transaction sub-layer
primitives.
4.12.1 "Quality of Service" parameter
The "Quality of Service" parameter shall indicate the SCCP sequence control and return option, for the
SCCP connectionless network layer service, as defined in CCITT Recommendation Q.711 [6].
4.12.2 "Reason" parameter
The "Reason" parameter is not used in any transaction primitives.
---------------------- Page: 14 ----------------------
PSIST ETS 300 134:1996
Page 13
ETS 300 134: December 1992
4.12.3 "Report Cause" parameter
The "Report Cause" parameter contains information indicating the reason for the exception report, i.e. that
the message was returned by the SCCP with the reason as specified in CCITT Recommendation Q.711
[6]. This parameter is in addition to those defined in Q.771, subclause 3.2.1, and is required for the TR-
NOTICE indication primitive.
4.13 Transaction facilities - Q.771, subclauses 3.2.3 - 3.2.5
4.13.1 TR-NOTICE
In addition to the transaction facilities mentioned in Q.771, subclause 3.2, the ability for TR-users to be
notified of non-delivery of user data shall be provided by the TR-NOTICE indication primitive. TR-NOTICE
indication is given only if the transaction exists, derived from the originating Transaction ID of the returned
message.
A TR-NOTICE indication primitive is only passed to the TR-user if the service requested cannot be
provided (i.e. the network layer cannot deliver the message to the remote node) and the TR-user
requested the return option in the quality of service parameter.
Table 5: TR-NOTICE primitive
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ ‡ Primitive : TR-NOTICE ‡
‡ Parameter ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ ‡ Indication ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Transaction ID ‡ M ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¯˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜·
‡ Report Cause ‡ M ‡
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜`˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜�
4.13.2 "Quality of Service"
The "Quality of Service" parameter shall be optionally provided in all TR transaction request primitives and
not just the TR-BEGIN primitive as stated in Q.771. When the "Quality of Service" parameter is absent,
the Transaction sub-layer shall request SCCP Class 0 and no return option to the SCCP.
In addition to the parameters defined by CCITT for the TR transaction primitives (see tables 17/Q.771,
18/Q.771, 19/Q.771, 20/Q.771 and 21/Q.771) the "Quality of Service" parameter shall be provided as
indicated in table 6.
---------------------- Page: 15 ----------------------
PSIST ETS 300 134:1996
Page 14
ETS 300 134: December 1992
Table 6: "Quality of Service" requirements for TR-primitives
�˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜˜¿
‡ Quality of Service ‡
ˆ˜˜˜˜˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜´˜˜˜˜˜˜˜˜˜˜˜·
‡ TR-PRIMITIVE ‡ Table ‡ Request
...
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Digitalno omrežje z integriranimi storitvami (ISDN) - Signalizacija CCITT št. 7 - Aplikacijski del za transakcijske zmožnosti (TCAP)Integrated Services Digital Network (ISDN); Signalling System No.7; Transaction Capabilities Application Part (TCAP)33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 134 E1PSIST ETS 300 134:1996en01-november-1996PSIST ETS 300 134:1996SLOVENSKI
STANDARD
PSIST ETS 300 134:1996
EUROPEANETS 300 134TELECOMMUNICATIONDecember 1992STANDARDSource: ETSI TC-SPSReference: T/S 43-05ICS:33.080Key words:ISDN, CCITT SS No.7, TCAPIntegrated Services Digital Network (ISDN);CCITT Signalling System No.7Transaction Capabilities Application Part (TCAP)ETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1992. All rights reserved.PSIST ETS 300 134:1996
Page 2ETS 300 134: December 1992Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.PSIST ETS 300 134:1996
Page 3ETS 300 134: December 1992ContentsForeword.51Scope.72Normative references.73General exceptions and clarifications to CCITT Recommendations Q.771 to Q.775.73.1Support of TC by terminal equipment.73.2Services assumed from a connectionless network layer.73.3TC based on a connection-oriented network.83.4Support of real-time/less real-time sensitive data.83.5Management of address information by the Transaction sub-layer.84Specific exceptions and clarifications to CCITT Recommendation Q.771.84.1Primitives for dialogue handling - Q.771, subclause 3.1.1, table 1/Q.771.94.2Primitives for component handling - Q.771, subclause 3.1.1, table 2/Q.771.94.3Overview of the Component sub-layer primitives - Q.771, subclause 3.1.1.94.4Definition of parameters within dialogue handling primitives - Q.771, subclause 3.1.2.1.94.4.1Address parameters.94.4.2"Components Present" parameter.94.4.3"Parameters" parameter.94.4.4"Quality of Service" parameter.94.4.5"Report Cause" parameter.94.5Dialogue facilities - Q.771, subclause 3.1.2.2.104.5.1TC-NOTICE.104.5.2Quality of Service.104.6Unstructured dialogue - Q.771, subclause 3.1.2.2.1, table 3/Q.771.114.7End of a dialogue - Q.771, subclause 3.1.2.2.2.3.b.114.8Report of success primitives - Q.771, subclause 3.1.3.3, table 9/Q.771.124.9Cancel of an operation - Q.771, subclause 3.1.3.6 & figure 8/Q.771.124.10Reject of a component by the Component sub-layer - Q.771, subclause 3.1.4.1.124.11Primitives for transaction handling - Q.771, subclause 3.2.1, table 15/Q.771.124.12Definition of parameters within Transaction sub-layer primitives - Q.771, subclause3.2.1.124.12.1"Quality of Service" parameter.124.12.2"Reason" parameter.124.12.3"Report Cause" parameter.134.13Transaction facilities - Q.771, subclauses 3.2.3 - 3.2.5.134.13.1TR-NOTICE.134.13.2"Quality of Service".134.14Transaction Abort by the TR-user - Q.771, subclause 3.2.5.3.145Specific exceptions and clarifications to CCITT Recommendation Q.772.155.1Example reasons for generating P-ABORT causes - Q.772, subclause 2.3.155.2Operation code - Q.772, subclause 3.4.165.3Example reasons for generating General Problem reject components - Q.772,subclause 3.8.1.165.4Mistyped parameters - Q.772, subclauses 3.8.2.3, 3.8.3.3 & 3.8.4.5.165.4.1Invoke problem - mistyped parameter.175.4.2Return Result problem - mistyped parameter.175.4.3Return Error problem - mistyped parameter.176Specific exceptions and clarifications to CCITT Recommendation Q.773.176.1Structure of the Transaction Portion - Q.773, subclause 5.1.17PSIST ETS 300 134:1996
Page 4ETS 300 134: December 19926.2Structure of the Component Portion - Q.773, subclause 6.1.176.3Parameters Tag - Q.773, subclause 6.1, tables 16-18/Q.773.176.4Reject Component - Q.773, subclause 6.1, table 19/Q.773.196.5Corrections to the Abstract Syntax Notation (ASN) - Q.773 Annex A.197Specific exceptions and clarifications to CCITT Recommendation Q.774.227.1Delivery of components to the remote TC-user - Q.774, subclause 3.2.1.1.1.227.2Operation classes - CANCEL - Q.774, subclause 3.2.1.1.3.227.3Operation classes - Invocation Time-out - Q.774, subclause 3.2.1.1.3.227.4Dialogue control - Q.774, subclause 3.2.2.1.227.5Action taken on protocol errors in the Component Portion - Q.774 table 4/Q.774.227.6Abnormal procedures relating to transaction control - Q.774, subclause 3.3.4.238Exceptions and clarifications to CCITT Recommendation Q.774 Annex A (SDLs).238.1Transaction sub-layer - Q.774 figure A-3/Q.774.238.1.1Handling of the SCCP N-NOTICE indication primitive - Q.774 figure A-3/Q.774 Sheets 1/6, 3/6 and 4/6.238.1.2Receipt of an ABORT message - Q.774 figure A-3/Q.774 Sheet 3/6.238.1.3Abnormal situations - Q.774 figure A-3/Q.774 Sheet 6/6.248.2Dialogue handling - Q.774 figure A-4/Q.774.248.2.1Handling of the TR-NOTICE indication primitive - figure A-4/Q.774 sheet1/2.248.2.2Terminating state machines at the end of a dialogue - figure A-4/Q.774sheets 1/2 & 2/2.248.3Component co-ordinator - Q.774 figure A-5/Q.774.248.3.1Receipt of a TC-U-Cancel request primitive - figure A-5/Q.774 Sheet 1/4.248.3.2Validation of invocation state machines - figure A-5/Q.774 Sheets 2/4 &3/4.248.3.3Return Error Component - figure A-5/Q.774 Sheet 2/4.248.3.4Discard of all subsequent components in a message - figure A-5/Q.774Sheet 2/4.248.3.5Receipt of a malformed Reject Component - figure A-5/Q.774 Sheet 2/4.248.3.6Reporting of class 4 invocation time-outs - figure A-6/Q.774 Sheet 6/6.349Specific exceptions and clarifications to CCITT Recommendation Q.775.369.1Reject of a component by TC - Q.775, subclauses 2.4.4 & 3.2.1.3.369.2Use of the external data type for UserAbortInformation (see subclause 6.5).36Annex A (informative):Symbols and abbreviations.37Annex B (informative):Bibliography.38History.39PSIST ETS 300 134:1996
Page 5ETS 300 134: December 1992ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols &Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).This ETS details exceptions and clarifications to CCITT Recommendations Q.771-Q.775 [1] - [5] definingthe Transaction Capabilities (TC) of the Transaction Capabilities Application Part (TCAP) for inter-networkdialogues on services such as the pan European Cellular Digital Radio System and Integrated ServicesDigital Network (ISDN).PSIST ETS 300 134:1996
Page 6ETS 300 134: December 1992Blank pagePSIST ETS 300 134:1996
Page 7ETS 300 134: December 19921ScopeThis ETS defines the Transaction Capabilities (TC) signalling requirements in and between networks, fornon circuit related services which use the CCITT Signalling System No.7, for inter-network dialogues.
Onlythose parts of TC need to be provided which are used by the above services.This standard is based on CCITT Recommendations Q.771 to Q.775, normative references [1] to [5], asspecified in the 1988 Blue Book.
The requirements of these recommendations shall apply unless modifiedby the exception statements and clarifications contained in this standard.For historical reasons, the terms TC and TCAP are used interchangeably.2Normative referencesThis ETS incorporates by dated or undated reference, provisions from other publications.
These normativereferences are cited at the appropriate places in the text and the publications listed hereafter.
For datedreferences subsequent amendments to, or revisions of, any of these publications apply to this ETS onlywhen incorporated in it by amendment or revision.
For undated references the latest edition of thepublication referred to applies.[1]CCITT Recommendation Q.771 (1988): "Specifications of Signalling SystemNo.7; Functional description of transaction capabilities".[2]CCITT Recommendation Q.772 (1988): "Specifications of Signalling SystemNo.7; Transaction capabilities information element definitions".[3]CCITT Recommendation Q.773 (1988): "Specifications of Signalling SystemNo.7; Transaction capabilities formats and encoding".[4]CCITT Recommendation Q.774 (1988): "Specifications of Signalling SystemNo.7; Transaction capabilities procedures".[5]CCITT Recommendation Q.775 (1988): "Specifications of Signalling SystemNo.7; Guidelines for using transaction capabilities".[6]CCITT Recommendation Q.711 (1988): "Specifications of Signalling SystemNo.7; Functional description of the signalling connection control part".[7]CCITT Recommendation X.229 (1988): "Open Systems Interconnection (OSI);Remote operations: Protocol specification".[8]CCITT Recommendation X.208 (1988): "Open Systems Interconnection (OSI);Model and Notation: Service definition: Specification of Abstract Syntax NotationOne (ASN.1)".3General exceptions and clarifications to CCITT Recommendations Q.771 toQ.7753.1Support of TC by terminal equipmentThe support of TC by terminal equipment is outside the scope of this ETS.3.2Services assumed from a connectionless network layerThere is no requirement for TC to work over any network layer other than CCITT Signalling System No.7Message Transfer Part (MTP) or Signalling Connection Control Part (SCCP).The services assumed from the SCCP are provided via the N-UNITDATA and N-NOTICE primitives.Specific details of how TCAP processes the N-NOTICE indication are given in the following sections.PSIST ETS 300 134:1996
Page 8ETS 300 134: December 1992It is also assumed that the N-UNITDATA indication primitive shall contain the SCCP "Return Option" and"Sequence Control" parameters in addition to those parameters defined in the CCITT RecommendationQ.711 [6].3.3TC based on a connection-oriented networkTC based on a connection-oriented network service is outside the scope of this ETS.3.4Support of real-time/less real-time sensitive dataAll data transfer by TC shall be considered as real-time sensitive.3.5Management of address information by the Transaction sub-layerThe procedures relating to address information (e.g. CCITT Recommendation Q.774 [4], subclause 3.3)are undefined in CCITT Recommendations Q.771 to Q.775 [1] to [5].
Although TC does not conveyaddress information in any of its messages, the Transaction sub-layer must provide any necessaryaddress information to the SCCP in every N-UNITDATA request primitive (e.g. global title and sub-systemnumber with a "Global Title routing required" indication).The procedures are intended to be analogous with those relating to Transaction IDs:i)The calling address information received in the first N-UNITDATA indication primitive ineach direction of a transaction, shall be used as called address in all subsequentmessages to the peer within that transaction.ii)Each SCCP user is responsible for providing its own address in the calling addressinformation of every N-UNITDATA request primitive.
This shall not change during thelife of the transaction and shall be in a form which can be used by the SCCP to returnmessages, e.g. from the distant node.iii)Once the transaction is established, the address information shall remain constant forthe life of the transaction.
TCAP shall use the address information for that transactionrather than that received in subsequent N-UNITDATA indication primitives for thattransaction.NOTE 1:In particular the above rules allow the B-SCCP-User to provide its own address ascalling address information instead of the received called address information in thefirst N-UNITDATA indication primitive.NOTE 2:The encoding of calling and called party address parameter in a SCCP message mustfollow the rules defined in CCITT Recommendation Q.713 (1992) (see also ETS 300009).4Specific exceptions and clarifications to CCITT Recommendation Q.771NOTE:The following notation is used in the tables included in this Clause:Mindicates a mandatory parameter;Oindicates an optional parameter;(=)indicates that the parameter must have the same value in a requestprimitive and in the corresponding indication primitive.PSIST ETS 300 134:1996
Page 9ETS 300 134: December 19924.1Primitives for dialogue handling - Q.771, subclause 3.1.1, table 1/Q.771In addition to the dialogue handling primitives identified in table 1/Q.771, the Component sub-layer shallsupport the TC-NOTICE indication primitive.NOTE:TC-NOTICE informs the TC-user that the service provider has been unable to providethe requested service.4.2Primitives for component handling - Q.771, subclause 3.1.1, table 2/Q.771The TC-R-REJECT in table 2/Q.771 shall be used to inform the local TC-user that a component wasrejected by the remote component sub-layer.4.3Overview of the Component sub-layer primitives - Q.771, subclause 3.1.1The abstract syntax of parameters included in primitives must contain sufficient information to enable theconcrete syntax to be encoded from the parameters supplied e.g. whether an operation/error code is localor global.4.4Definition of parameters within dialogue handling primitives - Q.771, subclause 3.1.2.1The following exceptions and clarifications are made to the parameters within the Component sub-layerdialogue handling primitives.4.4.1Address parametersIn addition to the CCITT definition of address parameters, it shall also indicate the address type, forexample a global title and sub-system number.4.4.2"Components Present" parameterThe reference to Q.771, subclause 3.1.3.8 should read as Q.771, subclause 3.1.3.7.The "Components Present" parameter indicates whether or not components are present.
If componentsare present they are delivered by TC to the TC-user in the order received from the originating TC-user.4.4.3"Parameters" parameterThe "Parameters" parameter is not used in any dialogue handling primitive.4.4.4"Quality of Service" parameterThe Quality of Service parameter
shall indicate the SCCP sequence control and return option, for theSCCP connectionless network layer service as defined in CCITT Recommendation Q.711 [6].4.4.5"Report Cause" parameterThe "Report Cause" parameter contains information indicating the reason for the exception report, forexample that the message was returned by the SCCP with the reason as specified in CCITTRecommendation Q.711 [6].
This parameter is in addition to those defined in Q.771, subclause 3.1.2.1,and is required for the TC-NOTICE indication primitive.PSIST ETS 300 134:1996
Page 10ETS 300 134: December 19924.5Dialogue facilities - Q.771, subclause 3.1.2.24.5.1TC-NOTICEIn addition to the dialogue facilities mentioned in Q.771, subclause 3.1.2.2, the ability for TC-users to benotified of non-delivery of user data shall be provided by the TC-NOTICE indication primitive.A TC-NOTICE indication primitive is only passed to the TC-user if the service requested cannot beprovided (i.e. the network layer cannot deliver the message to the remote node) and the TC-userrequested the return option in the "Quality of Service" parameter.Table 1: TC-NOTICE primitiveÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
³ Primitive : TC-NOTICE ³³
Parameter
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³
³
Indication
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Dialogue ID
³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Report Cause
³
M
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ4.5.2Quality of ServiceThe "Quality of Service" parameter shall be optionally provided in all TC dialogue request primitives and notjust the TC-BEGIN primitive as stated in Q.771.In addition to the parameters defined by CCITT for the TC dialogue primitives (see Q.771 tables 4/Q.771,5/Q.771, 6/Q.771, 7/Q.771 and 14/Q.771) the "Quality of Service" parameter shall be provided asindicated below, in table 2.Table 2: "Quality of Service" requirements for TC-primitivesÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
Quality of Service
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-primitive ³
Table
³ Request ³ Indication ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-BEGIN
³ 4/Q.771 ³ O (NOTE)³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-CONTINUE
³ 5/Q.771 ³ O (NOTE)³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-END
³ 6/Q.771 ³ O (NOTE)³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-U-ABORT
³ 7/Q.771 ³ O (NOTE)³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-P-ABORT
³14/Q.771 ³
³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´³ TC-NOTICE
³
³
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÙNOTE:When the "Quality of Service" parameter is not present in a dialogue request primitive,the Component sub-layer shall not request a quality of service to the Transaction sub-layer.
The Transaction sub-layer shall request SCCP Class 0 and no return option tothe SCCP.PSIST ETS 300 134:1996
Page 11ETS 300 134: December 19924.6Unstructured dialogue - Q.771, subclause 3.1.2.2.1, table 3/Q.771The "Components Present" parameter should not be present in the TC-UNI request primitive.
Table 3shows the parameters that are required in the TC-UNI request and indication primitive.Table 3: TC-UNI primitivesÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
³
Primitive : TC-UNI
³³
Parameter
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³
³
Request
³
Indication
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Quality of Service
³
O (NOTE)³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Destination Address
³
M
³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Originating Address
³
M
³
M (=)
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Dialogue ID
³
M
³
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Components Present
³
³
M
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNOTE:When the "Quality of Service" parameter is not present in a dialogue request primitive,the Component sub-layer shall not request a quality of service to the Transaction sub-layer.
The Transaction sub-layer shall request SCCP class 0 and no return option tothe SCCP.4.7End of a dialogue - Q.771, subclause 3.1.2.2.2.3.bComponents are delivered to the Component sub-layer and not directly to the Transaction sub-layer asstated in the first bullet item of Q.771, subclause 3.1.2.2.2.3.b.
The text should therefore read:"The basic scenario uses the TC-END primitives for two purposes:-delivery of any component(s) for which transmission is pending;-indication that no more components will be exchanged for this dialogue in eitherdirection."PSIST ETS 300 134:1996
Page 12ETS 300 134: December 19924.8Report of success primitives - Q.771, subclause 3.1.3.3, table 9/Q.771The operation code in the Return Result (Last/Not Last) components shall be included in both the requestand indication primitives as shown in table 4.Table 4: Report of success primitivesÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
³
Primitive
³³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³
Parameter
³ TC-RESULT-L
³ TC-RESULT-L
³³
³ TC-RESULT-NL ³ TC-RESULT-NL ³³
³
Request
³
Indication
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Dialogue ID
³
M
³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Invoke ID
³
M
³
M (=)
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Operation
³
O (NOTE)³
O (=)
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Parameters
³
O
³
O (=)
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Last Component
³
³
M
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙNOTE:Mandatory when the primitive contains the "Parameters" parameter.4.9Cancel of an operation - Q.771, subclause 3.1.3.6 & figure 8/Q.771The invocation timer is run for all classes as a local matter, but the reporting for class 4 operations is animplementation dependent matter.4.10Reject of a component by the Component sub-layer - Q.771, subclause 3.1.4.1When an invalid or corrupt component is received in an END message, it is not possible to return aREJECT component and so the remote TC-user is not informed.4.11Primitives for transaction handling - Q.771, subclause 3.2.1, table 15/Q.771In addition to the transaction handling primitives identified in table 15/Q.771, the Transaction sub-layer shallsupport the TR-NOTICE indication primitive:NOTE:TR-NOTICE informs the TR-user that the service provider has been unable to providethe requested service.4.12Definition of parameters within Transaction sub-layer primitives - Q.771, subclause 3.2.1The following exceptions and clarifications are made to the parameters within the Transaction sub-layerprimitives.4.12.1"Quality of Service" parameterThe "Quality of Service" parameter shall indicate the SCCP sequence control and return option, for theSCCP connectionless network layer service, as defined in CCITT Recommendation Q.711 [6].4.12.2"Reason" parameterThe "Reason" parameter is not used in any transaction primitives.PSIST ETS 300 134:1996
Page 13ETS 300 134: December 19924.12.3"Report Cause" parameterThe "Report Cause" parameter contains information indicating the reason for the exception report, i.e. thatthe message was returned by the SCCP with the reason as specified in CCITT Recommendation Q.711[6].
This parameter is in addition to those defined in Q.771, subclause 3.2.1, and is required for the TR-NOTICE indication primitive.4.13Transaction facilities - Q.771, subclauses 3.2.3 - 3.2.54.13.1TR-NOTICEIn addition to the transaction facilities mentioned in Q.771, subclause 3.2, the ability for TR-users to benotified of non-delivery of user data shall be provided by the TR-NOTICE indication primitive.
TR-NOTICEindication is given only if the transaction exists, derived from the originating Transaction ID of the returnedmessage.A TR-NOTICE indication primitive is only passed to the TR-user if the service requested cannot beprovided (i.e. the network layer cannot deliver the message to the remote node) and the TR-userrequested the return option in the quality of service parameter.Table 5: TR-NOTICE primitiveÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
³ Primitive : TR-NOTICE ³³
Parameter
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³
³
Indication
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Transaction ID
³
M
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Report Cause
³
M
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ4.13.2"Quality of Service"The "Quality of Service" parameter shall be optionally provided in all TR transaction request primitives andnot just the TR-BEGIN primitive as stated in Q.771.
When the "Quality of Service" parameter is absent,the Transaction sub-layer shall request SCCP Class 0 and no return option to the SCCP.In addition to the parameters defined by CCITT for the TR transaction primitives (see tables 17/Q.771,18/Q.771, 19/Q.771, 20/Q.771 and 21/Q.771) the "Quality of Service" parameter shall be provided asindicated in table 6.PSIST ETS 300 134:1996
Page 14ETS 300 134: December 1992Table 6: "Quality of Service" requirements for TR-primitivesÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
Quality of Service
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄ´³ TR-PRIMITIVE ³
Table
³ Request
³Indication ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-UNI
³ 16/Q.771 ³O (NOTE 1)³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-BEGIN
³ 17/Q.771 ³O (NOTE 1)³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-CONTINUE
³ 18/Q.771 ³O (NOTE 1)³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-END
³ 19/Q.771 ³O (NOTE 1)³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-U-ABORT
³ 20/Q.771 ³O (NOTE 1)³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-P-ABORT
³ 21/Q.771 ³
³ M (NOTE 2)³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄ´³ TR-NOTICE
³
³
³
³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÙNOTE 1:When the "Quality of Service" parameter is not present in a transaction requestprimitive, the Transaction sub-layer shall request SCCP class 0 and no return option tothe SCCP.NOTE 2:When this information is made available by the underlying sub-layer, then it must alsobe passed up to the service user.4.14Transaction Abort by the TR-user - Q.771, subclause 3.2.5.3When the transaction is in the "Initiation Sent" state, i.e. a Begin message has been sent but no backwardmessage for this transaction has been received, the result of the TR-U-ABORT request primitive is purelylocal.
Any message subsequently received that is related to this transaction, shall be handled according tothe actions indicated in table 6, of CCITT Recommendation Q.774 [4].PSIST ETS 300 134:1996
Page 15ETS 300 134: December 19925Specific exceptions and clarifications to CCITT Recommendation Q.7725.1Example reasons for generating P-ABORT causes - Q.772, subclause 2.3Table 7: Example mapping of P-ABORT scenarios to P-ABORT cause valuesÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³
Transaction sub-layer
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³
P-ABORT cause
³
Example reason
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ Unrecognised message type ³The combination of class, form
³³
(Syntax error)
³and tag code does not correspond ³³
³to a known tag i.e. message type ³³
³is not Begin, Continue, End or
³³
³Abort or Unidirectional.
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³Unrecognised transaction ID³Destination transaction ID
³³
³unassigned.
³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.