1、k UNI CATION STANDARD ETS 300 134 December 1992 Source: ETSI TC-SPS Reference: TIS 43-05 UDC: 621.395 Key words: ISDN, CCITT SS No.7, TCAP Integrated Services Digital Network (ISDN); CCIm Signalling System No.7 Transaction Capabilities Application Part (TCAP) ETSI European Telecommunications Standar
2、ds Institute ETSI Secretariat Postal address: 06921 Sophia Antipolis Cedex - FRANCE Office address: Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE Tel.: + 33 92 94 42 O0 - Fax: + 33 93 65 47 16 - Tlx: 470 040 F European Telecommunications Standards Institute 1 992. All rights reserved. No
3、 part may be reproduced except as authorised by written permission. The copyright and the foregoing restriction on reproduction extend to all media in which the information may be embodied. Page 2 ETS 300 134: 1992 Whilst every care has been taken in the preparation and publication of this document,
4、 errors in content, typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to “ETSI Standards Management Dept.“ at the address shown on the title page. Page 3 ETS 300 134:1992 Contents Foreword . 5 1 Scope . 7 2 Normative references 7 3 General exceptions a
5、nd clarifications to CCITT Recommendations Q.771 to Q.775 7 3.1 3.2 3.3 3.4 3.5 Support of TC by terminal equipment 7 Services assumed from a connectionless network layer . 7 TC based on a connection-oriented network . 8 Support of real-time/less real-time sensitive data . 8 Management of address in
6、formation by the Transaction sub-layer . 8 4 Specific exceptions and clarifications to CCIlT Recommendation 0.771 . 8 4.1 4.2 4.3 4.4 4.5 4.6 4.7 4.9 4.1 O 4.1 1 4.1 2 4.8 4.13 4.14 5 Specific 5.1 5.2 5.3 5.4 Primitives for dialogue handling . Q.771, subclause 3.1 .1. table 1/Q.771 . 9 Primitives fo
7、r component handling . 0.771, subclause 3.1.1, table 2/Q.771 . 9 Overview of the Component sub-layer primitives . Q.771, subclause 3.1.1 9 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
8、.3 “Parameters“ parameter . 9 4.4.4 “Quality of Service“ parameter 9 4.4.5 “Report Cause“ parameter 9 Dialogue facilities . 0.771, subclause 3.1.2.2 9 4.5.2 Quality of Service 10 Unstructured dialogue . 0.771, subclause 3.1.2.2.1, table 3/Q.771 10 End of a dialogue . Q.771, subclause 3.1.2.2.2.3.b 1
9、1 Report of success primitives . 0.771, subclause 3.1.3.3, table 9/Q.771 11 Cancel of an operation . 12.771, subclause 3.1.3.6 Functional description of transaction capabilities“. CCITT Recommendation 0.772 (i 988): “Specifications of Signalling System No.7; Transaction capabilities information elem
10、ent definitions“. CCITT Recommendation 0.773 (1 988): “Specifications of Signalling System No.7; Transaction capabilities formats and encoding“. CCITT Recommendation Q.774 (1 988): “Specifications of Signalling System No.7; Transaction capabilities procedures“. CCITT Recommendation 0.775 (1 988): “S
11、pecifications of Signalling System No.7; Guidelines for using transaction capabilities“. CCITT Recommendation 0.71 1 (1 988): “Specifications of Signalling System No.7; Functional description of the signalling connection control part“. CCITT Recommendation X.229 (1 988): “Open Systems Interconnectio
12、n (OSI); Remote operations: Protocol specification“. CCITT Recommendation X.208 (1 988): “Open Systems Interconnection (Ost); Model and Notation: Service definition: Specification of Abstract Syntax Notation One (ASN.1 I“. General exceptions and clarifications to CCITT Recommendations Q.77 1 to Q.77
13、5 -I 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
14、) or Signalling Connection Control Part (SCCP). Previous page is blank I Page8 ETS 300 134:1992 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. It is also a
15、ssumed 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 i61. 3.3 TC based on a connectionsriented network TC based on a connection-oriented network service is ou
16、tside the scope of this ETC. 3.4 Support of real-timefless 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 i
17、41, subclause 3.3) are undefined in CCITT Recommendations Q.771 to 0.775 I11 to 151. 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 a
18、nd sub-system number with a “Global Title routing required“ indication). The procedures are intended to be analogous with those relating to Transaction IDS: il The calling address information received in the first N-UNITDATA indication primitive in each direction of a transaction, shall be used as c
19、alled address in all subsequent messages to the peer within that transaction. ii) iii) 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
20、 which can be used by the SCCP to return messages, e.g. from the distant node. 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-UNI
21、TDATA 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
22、 called party address parameter in a SCCP message must follow the rules defined in CCIlT Recommendation 0.71 3 (1 992) (see also ETS 300 0091. 4 Specific exceptions and clarifications to CCITT Recommendation Q.771 NOTE: The following notation is used in the tables included in this Clause: M indicate
23、s a mandatory parameter; O indicates an optional parameter; (=I indicates that the parameter must have the same value in a request primitive and in the corresponding indication primitive. Page 9 ETS 300 134:1992 4.1 Primitives for dialogue handling - Q.771, subclause 3.1 .l, table 1 /a771 In additio
24、n to the dialogue handling primitives identified in table 110.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
25、subclause 3.1 .l , table 2lQ.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 primi
26、tives 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 - 0.771, subdause 3.1.2.1 The following exceptions and clarific
27、ations 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“ pa
28、rameter The reference to Q.771, subclause 3.1.3.8 should read as 0.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 “
29、Parameters“ parameter The “Parameters“ parameter is not used in any dialogue handling primitive. 4.4.4 “Quai 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 Recomm
30、endation Q.711 61. 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 61. This parameter is in addition to th
31、ose defined in Q.771, subclause 3.1 -2.1, and is required for the TC-NOTICE indication primitive. 4.5 Dialogue facilities - Q.771 subclause 3.1.2.2 4.5.1 TC-NOTICE In addition to the dialogue facilities mentioned in (2.771 , subclause 3.1.2.2, the ability for TC-users to be notified of non-delivery
32、of user data shall be provided by the TC-NOTICE indication primitive. Page 10 ETS 300 134:1992 Report Caus e A TC-NOTICE indication primitive is only passed to the TC-user if the service requested cannot be provided (.e. the network layer cannot deliver the message to the remote node) and the TC-use
33、r requested the return option in the “Quality of Service“ parameter. M Table 1 : TC-NOTICE primitive Parameter Indication Dialogue ID 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
34、stated in 0.771. In addition to the parameters defined by CCITT for the TC dialogue primitives (see Q.771 tables 4/Q.771, 5/0.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-prim
35、itives 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 O and no return option to the SCCP. 4.6 Unstructured di
36、alogue - 0.771, subclause 3.1.2.2.1, table 3K.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. II 34834583 0055577 TL5 Parme ter Quality of Service Destination
37、Address Originating Address Dialogue ID Components Present Page 11 ETS 300 134:1992 Primitive : TC-UNI Request Indication O (NOTE) M M M M M (=I M M Table 3: TC-UNI primitives NOTE: When the “Quality of Service“ parameter is not present in a dialogue request primitive, the Component sub-layer shall
38、not request a quality of service to the Transaction sub-layer. The Transaction sub-layer shall request SCCP class O and no return option to the SCCP. 4.7 End of a dialogue - 0.771, subclause 3.1.2.2.2.3.b Components are delivered to the Component sub-layer and not directly to the Transaction sub-lay
39、er 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
40、dialogue in either direction.“ 4.8 Report of success primitives - 0.771, subclause 3.1.3.3, table 9/0.771 The operation code in the Return Result (LastNot Last) components shall be included in both the request and indication primitives as shown in table 4. 3404583 0055578 95L Dialogue ID Invoke ID O
41、peration Parameters Last Component Page 12 ETS 300 134:1992 M M M M (=I O (NOTE) 0 (=I O o (=I M Table 4: Report of success primitives Parme t e r Primitive I Request Indication TC-RESULT-L TC-RESULT-L TC-RESULT-NL TC-RESULT-NL NOTE: Mandatory when the primitive contains the “Parameters“ parameter.
42、4.9 Cancel of an operation - 0.771, subclause 3.1.3.6 ion sub-layer Example reason The combination of class, form and tag code does not correspond to a known tag i.e. message type is not Begin, Continue, End or Abort or Unidirectional. Destination transaction ID unassigned. D 3404583 0055583 44b Pag
43、e 15 ETS 300 134:1992 Table 7: Example mapping of P-ABORT scenarios to P-ABORT cause values (concluded) Transaction sub-layer P-ABORT cause Badly formatted Transactioc Port ion Incorrect Transaction Portion Resource limitation Example reason Length indicator value less than 128 octets, but coded lon
44、g form. Length indicator value does not correspond to length of message. Combination of originating and destination transaction ID does not conform to message type. Component Portion Tag present, but no components. Message does not contain all the mandatory information elements defined in CCITT Reco
45、mmendation 4.773 31 for the message type. The order of the received information elements within the message does not conform to CCITT Recommendation Q.773 131 for the message type. Unrecognised tag other than message type. Congestion No Transaction ID can be allocated to the new transaction establis
46、hment request. Table 7 identifies and gives a P-ABORT classification for those abnormal occurrences which would cause the P-ABORT message to be transmitted. The table is not exhaustive, but seeks to ensure that different administrations have a common understanding on the mapping between a P-ABORT ca
47、use and the abnormal occurrence which generates it. The left hand side of the table shows the P-ABORT cause value as defined in Q.772, subclause 2.3. The right hand side shows examples of the type of abnormal occurrence which would generate such a message. 5.2 Operation code - 0.772, subclause 3.4 T
48、he operation code shall also be present in Return Result (Last/Not Last) components, if the result contains parameters. 3q04583 0055582 382 Page 16 ETS 300 134:1992 5.3 Example reasons for generating General Problem reject components - 0.772. subclause 3.8.1 Table 8: Example mapping of General Probl
49、em reject scenarios to General Problem reject types Component sub-layer General problem Unrecognised component 1 Mistyped component Badly structured component Example reason Component Type Tag not recognised as Invoke, Return Result Not Last Return Error, Reject or Return Result Last. Missing Invoke ID element. Operation code element expected but not present. Return Error Component received with no Error Code element. The order of the received information elements within the component does not conform to CCITT Recommendation 4.773 for that Component type. Length in
