1、STD*ITU-T RECMN Qa932-ENGL 1998 M 4862591 Ob55579 T78 INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STAN DARD IZATION SECT0 R OF ITU Q.932 (05198) SERIES Q: SWITCHING AND SIGNALLING Digital subscriber Signalling System No. I - Network layer Digital Subscriber Signalling System No. I
2、- Generic procedures for the control of ISDN s u p p lernen ta ry services ITU-T Recommendation Q.932 (Previously CCITT Recommendation) STD-ITU-T RECMN Q.932-ENGL 1778 48b2571 Ob55575 904 m ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNA
3、TIONAL AUTOMATIC AND SEM I-AUTOMATI C WORKING FUNCTIONS AND 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 DIGITAL EXCHANGES INTERW
4、ORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS General Data link layer Q.1-Q.3 Q.4-Q. 59 Q .60-Q. 99 Q.100-Q.119 Q. 120-Q.249 Q .250-Q. 309 Q.310-Q.399 Q.400-Q.499 Q. 500-Q. 599 Q.600-Q ,6
5、99 Q. 700-Q. 849 Q.850-Q.999 Q.850-Q.919 Q. 920-Q. 929 Network layer Q.930-Q.939 User-network management Stage 3 description for supplementary services using DSS I PUBLIC LAND MOBILE NETWORK INTERWORKING WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN Q. 940-Q. 949 Q.950-(2.999 Q. 1
6、000-Q. I O99 Q. 1 1 OO-Q. I1 99 Q.1200-Q.1999 Q.2000-Q.2999 For further details, please refer to ITU-T List of Recommendations STD-ITU-T RECMN 8.932-ENGL 1998 48b259L 065557b 840 W ITU-T RECOMMENDATION Q.932 DIGITAL SUBSCFUBER SIGNALLING SYSTEM NO. 1 - GENERIC PROCEDURES FOR THE CONTROL OF ISDN SUPP
7、LEMENTARY SERVICES Summary This Recommendation defines the generic procedures applicable for the control of supplementary services at the user-network interface. These procedures may be used for the invocation and operation of supplementary services in association with existing calls or outside any
8、existing calls. A significant new area addressed by this Recommendation is the support of Virtual Private Networks by means of new optional extensions. Source ITU-T Recommendation 4.932 was revised by ITU-T Study Group Il (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the
9、15“ of May 1998. Recommendation Q.932 (05/98) I STD-ITU-T RECMN Q.932-ENGL 1998 48b2591 Ob55577 787 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanen
10、t organ of the ITU. The ITU-T is responsible for studying technical, operating 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, e
11、stablishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. The approval of Recommendations by the Members of the IT-T is covered by the procedure laid down in WTSC Resolution No. 1. In someareas of information technology which fall within
12、 ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation the term recognized operating agency (ROA) includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms
13、Administration, ROA and public correspondence are defined in the Constitution of the ITU (Geneva, 1992). INTELLECTUAL PROPERTY RIGHTS The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. Th
14、e 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 Recommendation, the ITU had not received notice of intel
15、lectual 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 database. O ITU 1999 All rights reserved. No part of this
16、publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. Recommendation Q.932 (05/98) Il Page General . 1 2 Overview of the generic protocols and of their scope 2.1 Three generic
17、 protocols 2.1.1 Stimulus protocols . 2.1.2 Functional protocol . 3 Coexistence of protocols supported by a network 4 Keypad protocol . 4.1 General . 4.2 4.3 4.4 Elements of procedure 4.4.1 General Messages used in the Keypad protocol . Coding of the Keypad facility information element . 4.5 Procedu
18、res at the invocation interface 4.5.1 User procedures . 4.5.2 Network procedures Procedures at the remote interface 4.6 5 Feature key management protocol 5.1 Messages . 5.2 Procedures 5.2.1 Assumptions and restrictions Invocation of supplementary services . 5.2.3 Network responses 5.2.2 5.2.4 Genera
19、l aspects 5.2.5 Error conditions . 6 Functional protocol . 6.1 General . 6.1.1 Introduction . 6.1.2 Scope ofthe procedures 6.1.3 Categories of procedures . 6.1.4 Supplementary service functions 6.2 Separate messages category Hold and Retrieve functions 6.2.2 Hold procedures 6.2.3 Retrieve procedures
20、 . 6.2.1 Recommendation Q.932 (05/98) 1 4 4 4 5 9 9 10 10 10 10 11 12 12 13 13 13 13 13 13 14 14 16 17 . 111 STDmITU-T RECMN Qm932-ENGL 1998 48b2541 0655577 55T 6.2.4 Collision of messages 6.2.5 Parameter values (Timers) . 6.2.6 Clearing of a held call . Common information element category . 6.3.1 C
21、all related supplementary service procedures . 6.3.2 Bearer connection independent supplementary service procedures 6.3.3 Responses to multiple supplementary service invocations . 6.3.4 Coding of the call reference 6.3.5 Formal definition of data types . 6.3.6 Error procedures Network side channel r
22、eservation function 6.4.1 Implicit reservation . 6.4.2 Explicit reservation . 6.4.3 Effect of reservation on channel selection for a new call 6.3 6.4 7 7.1 Message hctional definition and content . Messages for supplementary service control 7.1.1 FACILITY . 7.1.2 HOLD 7.1.3 HOLD ACKNOWLEDGE 7.1.4 HO
23、LD EJECT . 7.1.5 REGISTER 7.1.6 RETRIEVE 7.1.7 RETRIEVE ACKNOWLEDGE . 7.1.8 RETRIEVE REJECT 7.2 Messages for Call Independent. Connection-Oriented Signalling . 7.2.1 CALL PROCEEDING 7.2.2 CONNECT 7.2.3 CONNECT ACKNOWLEDGE 7.2.4 FACILITY . 7.2.5 RELEASE . 7.2.6 RELEASE COMPLETE . 7.2.7 SETUP . 7.2.8
24、STATUS 7.2.9 STATUS ENQUIRY . 8 General message format and information element coding . 8.1 Message type Page 19 19 19 19 20 20 22 22 22 22 24 24 26 29 30 30 31 32 32 32 33 33 34 34 35 35 35 36 36 36 37 37 38 38 38 39 iv Recommendation Q.932 (05/98) a . 2 9 9.1 9.2 9.3 9.4 10 10.1 10.2 Other informa
25、tion elements 8.2.1 8.2.2 8.2.3 8.2.4 8.2.5 8.2.6 8.2.7 8.2.8 8.2.9 8.2.10 8.2.1 1 Call state Endpoint identifier., . Facility . Extended facility information element Feature activation Feature indication Information request . Service profile identification . Bearer capability . Channel identificati
26、on . Notification indicator Generic notification procedures General . 9.1.1 Introduction . 9.1.2 Scope ofthe procedures 9.1.3 Categories of procedures . Call related notifications . 9.2.1 Introduction . 9.2.2 Procedures . Call independent notifications 9.3.1 Introduction . 9.3.2 Procedures . Extensi
27、on of the Notification indicator information element . Call Independent Signalling Control Procedures . Point-to-point Networked connection-oriented call independent component transport mechanism . 1 O . 1.1 Connection establishment at the originating interface 1 O . 1.2 Connection establishment at
28、the destination interface 1 O . 1.3 Connection clearing . 1 O . 1.4 Interaction with restart procedure 1 O . 1.5 Interaction with call rearrangements . 1 O . 1.6 Handling of error conditions . 1 O . 1.7 Protocol timer values . Broadcast Networked connection-oriented call independent component transp
29、ort mechanism Page 39 39 39 41 47 48 49 50 51 53 53 54 56 56 56 56 56 57 57 57 57 57 57 58 58 58 58 60 62 63 63 63 64 64 Recommendation Q.932 (05/98) V Annex A . User service profiles and terminal identification A . 1 Introduction A.2 User service profiles . A.3 Terminal identification . A.4 Initial
30、ization A.4.1 Terminal requested initialization . A.4.2 Network solicited initialization . A.4.3 Collision A.5 Identification procedures Annex B - SDL diagrams for Hold/Retrieve functions . B . 1 Introduction Annex C - Definition of address types Annex D - Enhancements for Virtual Private Networks .
31、 D . 1 D.2 D.3 D.4 D.5 Introduction D.l.l Acronyms used in this Annex . Additional messages and content . D.2.1 SETUP message Additional information elements and coding . D.3.1 Called party number D.3.2 Calling party number . D.3.3 Connected number . D.3.4 Transit counter . D.3.5 VPN indicator D.3.6
32、 Facility . Additional procedures for the control of supplementary services using the common information element approach D.4.1 General D.4.2 Procedures applicable in a public network context . D.4.3 Procedures applicable in a VPN context . Generic notification procedures D.5.1 Categories of notific
33、ations D.5.2 Non-standardized notifications . D.5.3 Protocol control requirements . D.5.4 GFT-Control requirements Page 64 64 66 66 66 67 67 67 67 68 68 77 79 79 80 80 80 80 80 80 80 80 80 81 83 83 84 84 87 87 87 87 88 vi Recommendation Q.932 (05/98) STD-ITU-T RECMN Q.932-ENGL 1998 = 48b2591r Ob5556
34、2 044 - D.6 Flow control and related notifications D.6.1 Flow control capabilities . Indications related to flow control D.6.2 Appendix I . Illustration of the application of the three protocol types Example use ofthe Keypad protocol Examples o use of the Functional protocol . I . 1 Introduction 1.2
35、 1.3 1.4 Example of use ofthe Feature key management protocol 1.4.1 1.4.2 Call related supplementary service procedures . Call independent supplementary service procedures Appendix II . Functional reference model for the operation of supplementary services Appendix III . General description of compo
36、nent encoding rules III . 1 General component structure 111.2 Tag 111.2.1 Tag class 111.2.2 Fom of the data element . 111.2.3 Tag code 111.3 Length of the contents 111.4 Contents Appendix IV . Definition of operations. errors and data types . IV.2 Components IV.2.1 Length of each component or of the
37、ir data elements IV.2.2 Component type tag IV.2.3 Component identifier tags . IV.3 Operation value tag . IV.4 Error value tag IV.5 Problem tag . IV.6 Parameters Appendix V . List of object identifiers defined in Recommendation 4.932 Acronyms used in this Recommendation . V.l V.2 References Page 88 8
38、8 88 90 90 90 92 97 97 98 100 102 102 103 103 104 104 105 106 106 106 107 109 109 110 110 110 113 114 114 114 Recommendation Q.932 (05198) vii STD-ITU-T RECMN Q.932-ENGL L998 Recommendation Q.932 DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 1 - GENERIC PROCEDURES FOR THE CONTROL OF ISDN SUPPLEMENTARY SE
39、RVICES (revised in 1998) 1 General This Recommendation defines the generic procedures applicable for the control of supplementary services at theuser-network interface. These procedures may be used for the invocation and operation of supplementary services in association with existing calls or outsi
40、de any existing calls. The detailed procedures applicable to individual supplementary services are provided in Q.95-series Recommendations. However, typical examples of the application of these generic procedures to some supplementary services are provided in Appendix I for explanatory and illustrat
41、ive purposes only. 2 Three generic protocols are defined for the control of supplementary services at ISDN user-network interfaces. These protocols operate at layer 3 of the control plane at the S/T reference points, and assume that the use of layers 1 and 2 conforms to Recommendations 1.430 i, 1.43
42、1 2 and 4.921 3. In addition, the three generic protocols assume the existence of an established data link and use the acknowledged information transfer service available at the layer 2 to layer 3 interface. Overview of the generic protocols and of their scope 2.1 Three generic protocols Three gener
43、ic protocols are defined for the control of supplementary services, two of which are stimulus, the third being functional; these protocols are: - the Keypad protocol; - the Feature key management protocol; - the Functional protocol. 2.1.1 Stimulus protocols 2.1.1.1 Keypad protocol The Keypad protoco
44、l is based on the use of the Keypad facility and Display information elements. The Keypad facility information element may be included in the SETUP and INFORMATION messages. The Display information element may be included in any message sent by the network to the user according to Recommendation 4.9
45、3 1 4. This protocol applies to supplementary service invocation in the user-to-network direction, and the keypad facility codes used for the invocation of individual supplementary services are network- dependent. The protocol is stimulus in the sense that it does not require any knowledge about the
46、 invoked supplementary service by the user equipment. It may be used in any state of a call and in association with a call for supplementary service invocation and is applicable to both the basic and primary rate access structures. Clause 4 contains a detailed specification of this generic protocol.
47、 Recommendation Q.932 (05/98) 1 STDOITU-T RECMN Q.932-ENGL 3998 48b2593 Ob55584 917 2.1.1.2 Feature key management protocol The Feature key management protocol is based on the use of two information elements that are specified in clause 8: the Feature activation and Feature indication information el
48、ements. The Feature activation information element may be included in the SETUP and in the INFORMATION messages in the user-to-network direction. The Feature indication information element may be included in basic call control messages in the network-to-user direction. This protocol typically applie
49、s to supplementary service operation during calls but also allows for non-call related supplementary service control. Non-call related supplementary service control is accomplished by sending an INFORMATION message with the dummy call reference value and which contains a Feature activation information element. The user may send a Feature activation request at any time, and the network may send a Feature indication information element at any time. The supplementary service associated with the Feature identifier is service provider dependent and must be coordinated betw
