1、INTERNATIONAL TELECOMMUNICATION UNIONITU-T Q.860TELECOMMUNICATIONSTANDARDIZATION SECTOROF ITU(06/2000)SERIES Q: SWITCHING AND SIGNALLINGDigital subscriber Signalling System No. 1 GeneralIntegrated services digital network (ISDN)and broadband integrated services digitalnetwork (B-ISDN) generic addres
2、sing andtransport (GAT) protocolITU-T Recommendation Q.860(Formerly CCITT Recommendation)ITU-T Q-SERIES RECOMMENDATIONSSWITCHING AND SIGNALLINGSIGNALLING IN THE INTERNATIONAL MANUAL SERVICE Q.1Q.3INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING Q.4Q.59FUNCTIONS AND INFORMATION FLOWS FOR SERVICES I
3、N THE ISDN Q.60Q.99CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS Q.100Q.119SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5 Q.120Q.249SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 Q.250Q.309SPECIFICATIONS OF SIGNALLING SYSTEM R1 Q.310Q.399SPECIFICATIONS OF SIGNALLING SYSTEM R2 Q.400Q.499DIGITAL EXCHA
4、NGES Q.500Q.599INTERWORKING OF SIGNALLING SYSTEMS Q.600Q.699SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q.700Q.799Q3 INTERFACE Q.800Q.849DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 Q.850Q.999General Q.850Q.919Data link layer Q.920Q.929Network layer Q.930Q.939User-network management Q.940Q.949Stage 3 de
5、scription for supplementary services using DSS1 Q.950Q.999PUBLIC LAND MOBILE NETWORK Q.1000Q.1099INTERWORKING WITH SATELLITE MOBILE SYSTEMS Q.1100Q.1199INTELLIGENT NETWORK Q.1200Q.1699SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.1700Q.1799BROADBAND ISDN Q.2000Q.2999For further details, pleas
6、e refer to the list of ITU-T Recommendations.ITU-T Q.860 (06/2000) iITU-T Recommendation Q.860Integrated services digital network (ISDN) and broadband integratedservices digital network (B-ISDN) generic addressingand transport (GAT) protocolSummaryThis Recommendation provides the protocol for Generi
7、c Addressing and Transport (GAT). GAT is aprotocol for exchanging Application Protocol Data Units (APDUs) between service provision pointsthat may be located within the same network, between networks, or between a terminal and anetwork.The protocol is applicable to the signalling network, and may be
8、 used in conjunction with the DigitalSubscriber Signalling System No. 1 (DSS1) protocol, Digital Subscriber Signalling System No. 2(DSS2) protocol, Signalling System No. 7 (SS No. 7), and is applicable at interfaces where thoseprotocols are applicable.SourceITU-T Recommendation Q.860 was prepared by
9、 ITU-T Study Group 11 (1997-2000) and approvedunder the WTSC Resolution 1 procedure on 15 June 2000.ii ITU-T Q.860 (06/2000)FOREWORDThe International Telecommunication Union (ITU) is the United Nations specialized agency in the field oftelecommunications. The ITU Telecommunication Standardization Se
10、ctor (ITU-T) is a permanent organ ofITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendationson them with a view to standardizing telecommunications on a worldwide basis.The World Telecommunication Standardization Conference (WTSC), which meets ever
11、y four years,establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on thesetopics.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, th
12、e necessary standards areprepared on a collaborative basis with ISO and IEC.NOTEIn this Recommendation, the expression “Administration“ is used for conciseness to indicate both atelecommunication administration and a recognized operating agency.INTELLECTUAL PROPERTY RIGHTSITU draws attention to the
13、possibility that the practice or implementation of this Recommendation mayinvolve 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 othersoutside of the
14、 Recommendation development process.As of the date of approval of this Recommendation, ITU had not received notice of intellectual property,protected by patents, which may be required to implement this Recommendation. However, implementors arecautioned that this may not represent the latest informat
15、ion and are therefore strongly urged to consult theTSB patent database. ITU 2001All 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.ITU-T Q.86
16、0 (06/2000) iiiCONTENTSPage1 Scope 12 References 13 Definitions 24 Abbreviations . 45 Description . 55.1 Overview 55.1.1 Introduction . 55.1.2 Provision of addresses. 65.2 Protocol architecture. 95.3 Transport mechanisms 95.4 Services provided by individual protocol entities 105.4.1 Services provide
17、d by ROSE 105.4.2 Services provided by GAT-control . 105.4.3 Services provided by the transport mechanisms . 106 Operational requirements . 116.1 Provision and withdrawal . 116.2 Requirements on the originating network side. 116.3 Requirements on the destination network side. 117 Primitive definitio
18、ns and state definitions 117.1 Primitive definitions . 117.2 State definitions 118 Coding requirements 128.1 Message functional definitions and content . 128.2 General message format and information element coding . 129 Signalling procedures . 149.1 Sending GAT-Control 149.1.1 Introduction . 149.1.2
19、 Sending a service user APDU as the initial APDU of a transaction . 149.1.3 Responding to a service user APDU that has been received. 179.2 Receiving GAT-Control . 179.2.1 Introduction . 179.2.2 Receiving GAT-Control located at a terminal 179.2.3 Receiving GAT-Control located at a transit exchange,
20、incoming localexchange, incoming gateway PINX, incoming gateway exchange,outgoing local exchange or outgoing gateway exchange 18iv ITU-T Q.860 (06/2000)Page9.3 Transit GAT-Control 199.4 End GAT-Control. 199.5 Interpretation 199.5.1 Inclusion of an InterpretationAPDU parameter at a Source entity . 19
21、9.5.2 Handling of APDUs at a Destination entity 2010 Interactions with other networks 2010.1 Interworking with private ISDNs . 2010.2 Interworking with non-ISDNs 2010.3 Interworking with frame-relay 2010.4 Interworking with PSPDNs 2110.5 Interworking with H.323 environments . 2111 Parameter values.
22、21Annex A Redirection function 21Appendix I Examples of GAT protocol architectures 22I.1 Introduction 22I.2 Examples for use in narrow-band ISDN. 23I.3 Examples for use in broadband ISDN 24I.4 Key to figures within this appendix 25I.5 Bibliography for figures within this appendix 25Appendix II Gener
23、al information for the definition of GAT user applications 26II.1 Introduction 26II.2 ROSE 26II.3 Service indicator. 26II.4 Addressing mechanisms . 27II.4.1 Transport mechanism addresses 27II.4.2 GAT addresses 27II.4.3 Application addresses 27II.5 Other application data issues 27Appendix III Assignm
24、ent of object identifiers. 27ITU-T Q.860 (06/2000) 1ITU-T Recommendation Q.860Integrated services digital network (ISDN) and broadband integratedservices digital network (B-ISDN) generic addressingand transport (GAT) protocol1ScopeThis Recommendation provides the protocol for Generic Addressing and
25、Transport (GAT). GAT is aprotocol for exchanging Application Protocol Data Units (APDUs) between service provision pointsthat may be located within the same network, between networks, or between a terminal and anetwork. This Recommendation also provides a common framework for the use of ROSE or for
26、thesupport of other application dependent content (e.g. in the IN environment) and interpretationcapabilities in conjunction with the GAT protocol.The protocol is applicable to the signalling network, and may be used in conjunction with the DigitalSubscriber Signalling System No. 1 (DSS1) protocol,
27、Digital Subscriber Signalling System No. 2(DSS2) protocol, Signalling System No. 7 (SS No. 7), and is applicable at interfaces where thoseprotocols are applicable.The details of addressing and routing at the level of the transport mechanism are outside the scope ofthis specification.2 ReferencesThe
28、following ITU-T Recommendations and other references contain provisions which, throughreference in this text, constitute provisions of this Recommendation. At the time of publication, theeditions indicated were valid. All Recommendations and other references are subject to revision; allusers of this
29、 Recommendation are therefore encouraged to investigate the possibility of applying themost recent edition of the Recommendations and other references listed below. A list of the currentlyvalid ITU-T Recommendations is regularly published.1 ITU-T I.411 (1993), ISDN user-network interfaces Reference
30、configurations.2 ITU-T Q.932 (1998), Digital subscriber signalling system No. 1 Generic procedures forthe control of ISDN supplementary services.3 ITU-T X.219 (1988), Remote operations: Model, notation and service definition.4 ITU-T X.880 (1994), Information technology Remote Operations: Concepts, m
31、odel andnotation.5 ITU-T X.229 (1988), Remote Operations: Protocol specification.6 ITU-T X.208 (1988), Specification of Abstract Syntax Notation One (ASN.1).7 ITU-T X.209 (1988), Specification of Basic Encoding Rules for Abstract Syntax NotationOne (ASN.1).8 ITU-T X.680 (1994), Information technolog
32、y Abstract Syntax Notation One (ASN.1):Specification of basic notation.9 ITU-T X.690 (1994), Information technology ASN.1 encoding rules; Specification of BasicEncoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules(DER).10 ITU-T I.413 (1993), B-ISDN user-network interf
33、ace.11 ITU-T I.112 (1993), Vocabulary of terms for ISDNs.2 ITU-T Q.860 (06/2000)3 DefinitionsThis Recommendation defines the following terms:3.1 anynode: a value for the sourceEntity and destinationEntity of the GAT network facilityextension, such that (two cases exist): when specified without an ad
34、dress, the requested service functionality is to be provided atthe next service provision point along the path of the transport mechanism that supports theservice within the same or any subsequent service provider. For this value, an end node actsto provide end GAT-Control functionality; or when spe
35、cified with an associated address, the requested service functionality is to beprovided at the next service provision point along the path of the transport mechanismwithin the same, or any subsequent, service provider that has the given address. Where thefirst service provision point that has the gi
36、ven address does not wish to provide the service,it can alter the address to that of another service provision point either within the sameservice provider or within a different service provider. For this value, an end node that is notaddressed discards the information.3.2 Broadband Integrated Servi
37、ces Digital Network (B-ISDN): an ISDN that supports ratesgreater than primary rate.3.3 coincident S and T reference point: see ITU-T I.411 1. Unless otherwise stated, thisshould also be understood to include the coincident SBand TB reference point, as defined inITU-T I.413 10.3.4 end GAT-Control: th
38、is entity is located at the entity providing the destination serviceprovision point. It provides information to the application concerning the source of the service userAPDUs (ApduPortion parameter), taken from the GAT-PDU, and passes the service user APDU tothe application.3.5 end node: the node th
39、at is at either the end point of the transport mechanism, or at the localexchange, whichever comes first along the path of the transport mechanism.3.6 endNode: a value for the sourceEntity and destinationEntity of the GAT network facilityextension, such that the requested service functionality is to
40、 be provided at the last service provisionpoint along the path of the transport mechanism before a terminal is reached. This may be within thecurrent service provider or in any subsequent service provider. For this value, an end node acts toprovide end GAT-Control functionality.3.7 endTerminal: a va
41、lue for the sourceEntity and destinationEntity of the GAT networkfacility extension, such that the requested service functionality is to be provided at the terminal alongthe path of the transport mechanism. This terminal can be attached to the current service provider orto any subsequent service pro
42、vider.3.8 GAT control: the protocol entity supporting the GAT protocol. It provides services to theGAT users, both directly and through ROSE, and uses the services of various underlying protocols(e.g. DSS1, ISUP) in order to provide the transport of those GAT user protocol data units.3.9 GAT user: a
43、 protocol entity that uses the services of the GAT protocol to transfer the GATuser protocol data units between the peer GAT user entities.3.10 general signalling: a signalling procedure for the exchange of GAT user protocol data unitsbetween application entities that need not be adjacent.3.11 incom
44、ing gateway exchange: a public network exchange for which an incoming transportmechanism (bearer-related or bearer-independent) is received from a private network exchange in aprivate network, or from a public network exchange in another public network.ITU-T Q.860 (06/2000) 33.12 incoming gateway PI
45、NX: a private network exchange for which an incoming transportmechanism (bearer-related or bearer-independent) is received from a public network exchange in apublic network.3.13 incoming local exchange: a public network exchange for which an incoming transportmechanism (bearer-related or bearer-inde
46、pendent) is received from a terminal.3.14 Integrated Services Digital Network (ISDN): see ITU-T I.112 9, definition 308.3.15 local signalling: a signalling procedure restricted to the exchange of application protocoldata units between adjacent application entities.3.16 no value at all: (i.e. a value
47、 for both the sourceEntity and destinationEntity of the GATnetwork facility extension assumed when the GAT network facility extension is absent) therequested service functionality is to be provided along the path of the transport mechanism at theimmediate next entity (terminal or node) that provides
48、 GAT at a GAT-Control entity.3.17 outgoing gateway exchange: a public network exchange for which an outgoing transportmechanism (bearer-related or bearer-independent) is generated to a private network exchange in aprivate network, or to a public network exchange in another public network.3.18 outgoi
49、ng gateway PINX: a private network exchange for which an outgoing transportmechanism (bearer-related or bearer-independent) is generated to a public network exchange in apublic network.3.19 outgoing local exchange: a public network exchange for which an outgoing transportmechanism (bearer-related or bearer-independent) is generated to a terminal.3.20 owner domain: an owner domain is a domain under the control of a single operator, and canrange from a single terminal, to a public network, and to other forms of service pr
