1、INTERNATIONAL TELECOMMUNICATION UN ION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.765 (06/2000) SERIES Q: SWITCHING AND SIGNALLING Specifications of Signalling System No. 7 - ISDN user part Signalling System No. 7 - Application transport mechanism ITU-T Recommendation Q.765 (Formerly CC
2、ITT Recommendation) COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicessTD.ITU-T RECMN Q-7b5-ENGL 2000 M 48bZ57L 0689326 T55 ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE FUNCTIONS A
3、ND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No 4 AND No 5 SPECIFICATIONS OF SIGNALLING SYSTEM No 6 SPECIFICATIONS OF SIGNALLING SYSTEM RI SPECIFICATIONS OF SIGNALLING SYSTEM R2 INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 INTERNA
4、TIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS 1 DIGITAL EXCHANGES General Message transfer part (MTP) Signalling connection control part (SCCP) Telephone user part (TUP) ISDN supplementary services Data user part Signalling System No. 7 management Test spec
5、ification 43 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1-Q.3 4.4-4.59 4.60-4.99 Q.100-Q.119 Q.12bQ.249 4.3 1CQ.399 4.400-4.499 Q.50
6、0-Q.599 Q 700-4 799 4.700 Q .2 5 O-Q .3 09 4.600-4.699 4.701-4.709 4.711-4.719 4.720-4.729 Q.73GQ.739 4.740-4.749 4.7564.759 9 4.770-4.779 4.780-4.799 4.800-4.849 Q.850-Q.999 Q. 1 006Q. 1099 Q. 1 100-Q. 1 199 Q. 12064. 1699 Q.1700-4.1799 4.2000-4.2999 For further details, please refer to the list of
7、 ITU-T Recommendations, COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed by Information Handling ServicesSTD-ITU-T RECMN d.765-ENGL 2000 4862591 0689127 991 ITU-T Recommendation 4.765 Signalling System No. 7 - Application transport mechanism Summary This Recommendation
8、 describes the additions to the ISDN User Part (ISUP) for providing a transport mechanism used by applications requiring a bearer in conjunction with the support of the applications signalling information flow. This transport mechanism shall provide the same capabilities as the Transaction Capabilit
9、ies Application Part (TCAP) provides to its users. Source ITU-T Recommendation 4.765 was revised by ITU-T Study Group 11 (1997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. Keywords APM, ISUP. COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed
10、 by Information Handling ServicesFOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, op
11、erating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T study groups which, in tur
12、n, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSC Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE
13、 In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may i
14、nvolve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this R
15、ecommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent databas
16、e. O ITU 2001 All rights reserved. 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 ITU. COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLic
17、ensed by Information Handling Services2 4 6 6.1 6.2 7 7.1 7.2 8 8.1 8.2 8.3 9 9.1 9.2 9.3 10 10.1 10.2 10.3 STD-ITU-T RECMN Q.765-ENGL ZOO0 E 4862573 Ob87327 764 CONTENTS Scope References Definitions Abbreviations . Recommendation structure . Modelling . Network model . Specification model 6.2.1 Int
18、roduction . 6.2.2 General model . 6.2.3 Dynamic primitive flows . . Application Process functions APM Application Process (AP) functions 7.2.1 Introduction . 7.2.2 Primitive interface (AP-SACF) . General . 7.2.3 Procedures . 7.2.4 Pnmitive contents Single Association Control Function (SACF) Introduc
19、tion Information flows related to messages sent by the node Information flows related to messages received by the node . ISDN user part ASE (ISUP ASE) Primitive interface Procedures Primitive contents . Application transport mechanism ASE (APM ASE) . Primitive interface Procedures 10.2.1 Normal proc
20、edures - Sending . 10.2.2 Normal procedures - Receiving 10.2.3 Sending of acknowledgement . 10.2.4 Segmentation . Primitive contents . Page 1 2 2 3 4 11 11 12 12 13 13 14 15 15 15 16 17 17 17 18 18 18 19 19 19 21 21 24 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLicensed b
21、y Information Handling Services STD-ITU-T RECMN Q.765-ENGL 2000 W 4862591 Ob89L30 486 0 11 11.1 11.2 11.3 12 12.1 12.2 12.3 13 13.1 13.2 13.3 13.4 13.5 14 15 Application Transport Mechanism User ASE (APM-user ASE) . Primitive interface Procedures 1 1.2.1 General 1 1.2.2 Signalling congestion 1 1.2.3
22、 Handling of unrecognized signalling information Primitive contents . Network Interface function . Introduction Pnmitive interfaces . 12.2.1 MTP interface 12.2.2 AEI interface . Procedures 12.3.1 Formats and codes . 12.3.2 Distnbution 12.3.3 Primitive mapping . Errors Handling ASE (EH ASE) Introduct
23、ion of unidentified context and addressing errors handling mechanism . handling . handling . Reassembly error handling . 13.1.1 Unidentified context and addressing errors handling - Local error 13.1.2 Unidentified context and addressing errors handling - Remote error Primitive interface Procedures 1
24、3.4.1 Normal procedures - Remote error handling 13.4.2 Normal procedures - Local error handling . 13.4.3 Exceptional procedures - Context identifier error 13.4.4 Exceptional procedures - Unrecognized reason value Primitive contents . Application transport notification information . Timers . Appendix
25、 I . Example sequence diagrams of APM segmentation . Appendix II . Setting of parameter and message instruction indicators . Page 24 24 25 25 25 25 25 26 26 26 26 26 26 26 26 27 27 27 28 28 29 29 29 29 30 31 31 31 31 32 33 34 COPYRIGHT International Telecommunications Union/ITU TelecommunicationsLic
26、ensed by Information Handling ServicesITU-T Recommendation 4.765 Signalling System No. 7 - Application transport mechanism 1 Scope This Recommendation describes the additions to the ISDN User Part (ISUP) for providing a transport mechanism used by applications requiring a bearer in conjunction with
27、the support of the applications signalling information flow. This transport mechanism shall provide the same capabilities as the Transaction Capabilities Application Part (TCAP) provides to its users. The definition of the applications that use this mechanism are documented in their own Recommendati
28、on and are therefore outside the scope of this Recommendation. The Application Transport Mechanism (APM) is capable of creating signalling associations between APM-user application logic located at a Public Initiating Node (PIN) and its peer APM-user application logic located at the Public Addressed
29、 Node (PAN). (The PINRAN concept is described in clause 6.) The ability to create different PINPAN relationships is only limited by the addressing mechanism used. At call setup, the ISUP basic call mechanism is used to route the call through the network towards the PAN in the same manner as it norma
30、lly establishes a call. The APM addressing mechanism is used to determine the node in the call path where the Application Information has to be handled but has no influence on the routing of the call. This transport mechanism provides the APM-user applications (APM “2000“-user applications) with bot
31、h an implicit and an explicit APM addressing capability. The applications originally designed to use the APM “98“ 6 (APM “98“-user applications) can be supported without alterations by the mechanism described in this Recommendation. APM “98“-user and APM “2000“-user applications are differentiated b
32、y their application context identifiers. The coexistence along a call path of nodes with the APM “98“ capability and nodes supporting the APM “2000“ functionality may cause in two very specific configurations, an inappropriate handling of application transport parameters sent by an APM “2000“-user a
33、pplication. 1) The first scenario is the following: a) An APM “2OOO“-user application sends information at call Set-up towards a remote application. b) An intermediate node supporting the previous APM version 6 is encountered in the call path before the node where the application information has to
34、be delivered. c) This intermediate node is addressed by the called party number. In this specific case, the intermediate APM “98“ node will reject the application information associated to the APM “2000“-user application according to the procedures defined in 6. 2) The second scenario is the case wh
35、ere an error notification has to be generated by an APM “98“ node on receipt of application information associated to an APM “2000“-user application. This notification may not be delivered to the initiating application if the explicit addressing mechanism was used by this application. An APM “98“ no
36、de does indeed not support the EH ASE (see clause 13) and cannot therefore use the explicit addressing mechanism for the sending of a notification. Apart from the case explained above (intermediate APM “98“ node addressed by the called party number), such a problem can only possibly occur if applica
37、tion information generated by an application using the explicit addressing mechanism is received by an end node with APM “98“ capability. Because of the above reasons future standardized applications shall not be defined as APM “98“-user applications. COPYRIGHT International Telecommunications Union
38、/ITU TelecommunicationsLicensed by Information Handling ServicesSTD-ITU-T RECMN Q-765-ENGL 2000 4 PIN at transit exchange and PAN at end exchange; PIN at end exchange and PAN at transit exchange; PIN and PAN at transit exchanges. a It means that a PIN located anywhere in the call path has the capabi
39、lity to create a PINPAN relationship with any exchange in the call path having the APM-user capability. The intermediate exchanges having the APM capability but not the APM-user capability will transit the APM information. It is, of course, possible to communicate in both directions once a PINPAN re
40、lationship has been created. It should be noted that only one PINPAN relationship may exist over the same segment of the call path for a given application (Context identity value) which does not use the explicit addressing mechanism. For example, if a PINPAN relationship has been established (PIN) b
41、etween the Originating Local Exchange (OLE) and an intermediate exchange in the call path (PAN), it is not possible to later establish a PINPAN relationship fi-om the destination local exchange to the originating local exchange for the same application since its corresponding PAN would be located at
42、 the OLE and would therefore result in two PINPAN relationships overlapping at the call leg between the OLE and the intermediate exchange. However, it is possible to establish overlapping PINBAN relationships for a given application using the explicit addressing mechanism. 2 References The following
43、 ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recom
44、mendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. i 2 3 4 5 6 ITU-T 4.76 1 (1 999), Signalling System No. 7 - ISDN
45、 User Part functional description. ITU-T 4.762 (1999), Signalling System No. 7 - ISDN User Part general functions of messages and signal. ITU-T 4.763 (1999), Signalling System No. 7 - ISDN User Part formats and codes. ITU-T 4.764 (1999), Signalling System No. 7 - ISDN User Part signallingprocedures.
46、 ITU-T 4.1400 (1993), Architecture framework for the development of signalling and OA this is referred to as the “Application This Recommendation describes only the part of the total Application Process and Protocol functions in the exchange, that relates to NNI enhancements for the support of the A
47、pplication Transport Mec hani sm . The protocol functions relate only to signalling associations with a bearer (ISUP) and describe the additional information and procedures to that defined for ISUP Basic Call 4 and its associated formats and codes 3 required to support the Application Transport Mech
48、anism. The signalling association with a bearer is subdivided into three parts: APM-user Protocol Control (APM-user ASE), Application Transport Mechanism protocol control (APM ASE), and the ISUP Basic Call (ISUP ASE). These are coordinated by the Single Association Control Function (SACF). The Appli
49、cation Entity (AE) can contain more than one APM-user application. It may contain APM “98“-user applications and APM “2OOO“-user applications. It also contains Errors Handling (EH ASE) for taking the appropriate actions in the case when either the addressed node (PAN) does not support the APM-user application or for the handling of APM error cases. The Application Process (AP) contains all Call Control functions; however, this Recommendation will only describe the enhancements required to support the Application Transport Mechanism (APM). The AP relevant to
