ITU-T Q 932 AMD 1-2000 Digital Subscriber Signalling System No 1 - Generic Procedures for the Control of ISDN Supplementary Services Amendment 1 Series Q Switching and Signalling Dtwo.pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.932 Amendment 1 (06/2000) SERIES Q: SWITCHING AND SIGNALLING Digital subscriber Signalling System No. 1 - Network layer Digital Subscriber Signalling System No. 1 - Generic procedures for the control of ISD

2、N supplementary services Amendment 1 ITU-T Recommendation Q.932 - Amendment 1 (Formerly CCITT Recommendation) ITU-T Q-SERIES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING S

3、YSTEMS No. 4 AND No. 5 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DIGITAL EXCHANGES INTERWORIUNG OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 Q3 INTERFACE DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 INTERN

4、ATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS General Q.lLQ.3 Q.4-Q.59 Q.60.99 Q. 100.119 Q. 120.249 Q.250.309 Q.310.399 Q.400.499 Q.500.599 Q.600.699 Q.700.799 Q.800.849 Q.850.999 Q.850.919 Data link layer Q.920.929 User-network management Q.940.949 Stage

5、 3 description for supplementary services using DSS1 PUBLIC LAND MOBILE NETWORK INTERWORIUNG WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK BROADBAND ISDN SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 Q.950.999 Q. 1000. 1099 Q. 1 100.1199 Q. 1200.1699 Q.1700.1799 Q.2000.2999 For further deta

6、ils, please re$er to the list of ITD-T Recommendations. ITU-T Recommendation 4.932 Digital Subscriber Signalling System No. 1 - Generic procedures for the control of ISDN supplementary services AMENDMENT 1 Summary This Amendment 1 to ITU-T 4.932 (1998) is provided in order to support the Generic Add

7、ressing and Transport protocol as defined in ITU-T 4.860 (2000). Additionally, various ASN.l module definitions according to ITU-T X.680/X.880 are also added and necessary updates and corrections for existing ASN. 1 modules are provided. Source Amendment 1 to ITU-T Recommendation 4.932 was prepared

8、by ITU-T Study Group 11 (1 997-2000) and approved under the WTSC Resolution 1 procedure on 15 June 2000. ITU-T Q.932/Amd.l (06/2000) 1 FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecommunication Stand

9、ardization Sector (ITU-T) is a permanent organ of ITU. 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),

10、which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, 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 withi

11、n ITU-Ts purview, the necessary standards are prepared on a collaborative basis with IS0 and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. INTELLECTUAL PROPERTY RIGHTS I

12、TU draws attention to the possibility that the practice or implementation of this Recommendation may involve 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 mem

13、bers or others outside of the 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 are cautioned that this may n

14、ot represent the latest information and are therefore strongly urged to consult the TSB patent database. 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 perm

15、ission in writing fi-om ITU. 11 ITU-T Q.932/Amd.l (06/2000) Recommendation 4.932 Digital Subscriber Signalling System No. 1 - Generic procedures for the control of ISDN supplementary services AMENDMENT 1 Text and tables to ITU-T 4.932 are amended as follows: 1) Clause 1 Change the heading of the exi

16、sting clause 1 to “Scope“. 2) Subclause 1.1 A new subclause “1.1 Definitions“ should be added as follows: For the purpose of the GAT protocol, the following definitions apply: 1.1.1 data units between adjacent application entities. 1.1.2 units between application entities that need not be adjacent.

17、3) Subclause 6.1.1 Introduction Insert a 3rdparagraph as follows: The support of the GAT protocol as defined in ITU-T 4.860 is a network and user option and its use is based on bilateral agreement between the network and user. The extensions of the generic functional protocol required for the suppor

18、t of the GAT protocol are described in ITU-T 4.860 (generic part) and in this Recommendation (transport mechanisms and coding of the facility information element). 4) The following new Table 6-1 bis is the ASN.1 module according to ITU-TX680/X880 and sould be added after Table 6-1 as follows: local

19、signalling: a signalling procedure restricted to the exchange of application protocol general signalling: a signalling procedure for the exchange of application protocol data Subclause 6.4.3 Effect of reservation on channel selection for a new call ITU-T Q.932/Amd.l (06/2000) 1 Table 6-1 bislQ.932 -

20、 Explicit network controlled channel reservation (ASN.l module according to ITU-T X.680/X.880) Explicit-Network-Controlled-C hannel-Reservation itu-t recommendation q 932 explicit-network-controlled-channel-reservation(4) DEFINITIONS := BEGIN EXPORTS explicitReservationCreationContro1, explicitReser

21、vationManagement, explicitReservationCance1, maximumNumberOfReservationsReached, noExplicitReservationExistsOrInvalidReservationIndicator, UnwantedReservationCreated, implicitReservationUsed, Reservationhdicator; IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects joint-iso-itu-t rem

22、ote-operations(4) informationObjects(5) versionl(0); notAvailable, notsubscribed FROM General-Errors itu-t recommendation q 950 general-errors-list(l); explicitReservationCreationContro1 OPERATION : := ARGUMENT controlOption ENUMERATED noReservationRequired (O), reservationRequiredWithReservationInd

23、icator (i), reservationRequiredWithoutReservationIndicator (2) RESULT ReservationIndicator - optional ERRORS maximumNumberOfReservationsReachedl notAvailable1 notsubscribedl unwantedReservationCreated CODE locak2O 1 explicitReservationManagement OPERATION := ARGUMENT ReservationIndicator - optional

24、RESULT ERRORS noExplicitReservationExistsOrInvalidReservationIndicator I notAvailable1 notsubscribedl implicitReservationUsed CODE locak2l 1 explicitReservationCance1 OPERATION : := ARGUMENT ReservationIndicator - optional RESULT ERRORS noExplicitReservationExistsOrInvalidReservationIndicator I notA

25、vailable1 notsubscribed CODE locak22 1 maximumNumberOfReservationsReached ERROR := CODE local:33 noExplicitReservationExistsOrInvalidReservationIndicator ERROR := CODE local:34 UnwantedReservationCreated ERROR := CODE local:35 implicitReservationUsed ERROR := CODE local:36 ReservationIndicator : :=

26、INTEGER (-128127) END - of Explicit-Network-Controlled-Channel-Reservation ITU-T Q.932/Amd.l (06/2000) 5) 8.2.3 Facility a) This subclause defines in addition the structure and the coding of the Facility information element, required for the support of the GAT protocol, as described in ITU-T 4.860.

27、Specific procedures describing applications of the GAT protocol are outside the scope of this Recommendation. b) Insert the following text after the 4th paragraph: A new Figure 8-2 bis specipes the layout of the Facility information element for the GAT protocol and should be inserted after Figure 8-

28、2 as follows: Facility information element identifier o1 O O O 1 1 1 O Length of Facility information element O O Protocol profile ext. 1 2 3 I I GATPDU (Note) NOTE- When the protocol profile field in Octet 3 contains the value “GAT Protocol“, a single GATPDU component (as defined in ITU-T 4.860) sh

29、all be included in octet group 4. Figure 8-2 bislQ.932 - Facility information element 4, etc. c) Replace Table 8-5 with the following: Table 8-5/Q.932 - Facility information element Protocol ProJile Bits 54321 1 O O O 1 1 O O 1 O 1 O O 1 1 1 O 1 1 O 1 1 1 1 1 All other values are reserved and their

30、usage is the subject of other Recommendations. NOTE 1 - When this codepoint is used, the NFE, NPP, and the Interpretation components shall be excluded. In addition, ITU-T defined local values apply for the components. NOTE 2 - When this codepoint is used, the NFE, NPP, and the Interpretation compone

31、nts shall be excluded. See ITU-T Q.941 for the CMIP protocol. NOTE 3 - When this codepoint is used, the NFE, NPP, and the Interpretation components shall be excluded. See ITU-T X.217 and X.227 for the ACSE protocol. NOTE 4 - When this codepoint is used, the NFE, NPP, and the Interpretation component

32、s as defined in ISO/IEC 11582 can be included. In this case, only ISO/IEC defined local values apply for the components. For consistency with ISO/IEC 11582, a Facility information element with the protocol profile value “networking extensions“ shall not be included in the SETUP ACKNOWLEDGE, CALL PRO

33、CEEDING, and CONNECT ACKNOWLEDGE messages as these messages are of local significance. NOTE 5 - When this codepoint is used, a single GATPDU component as defined in ITU-T Q.GFT shall be included in octet group 4 of the Facility information element. Remote Operations Protocol (Note 1) CMIP Protocol (

34、see ITU-T Q.941 1 i) (Note 2) ACSE Protocol (see ITU-T X.217 and X.227 12) (Note 3) GAT Protocol (Note 5) Networking extensions (Note 4) ITU-T Q.932/Amd.l (06/2000) 3 6) 4 Subclause 8.2.3.1.1 Components (octets 4, etc.) Replace the definition of the return result component in Table 8-7 with the foll

35、owing: ReturnResultComponent := SEQUENCE Invokeid invokeIdentifierType, SEQUENCE Operationvalue OPERATION, Result ANY DEFINED BY Operationvalue OPTIONAL b) A new Table 8- 7 bis provides the coding of the Facility information element according to ITU-TX 680/X880 and should be added after Table 8-7 as

36、 follows: Table 8-7 bislQ.932 - Facility information element component coding Facility-Information-Element-Components DEFINITIONS IMPLICIT TAGS := BEGIN - exports eve ything IMPORTS OPERATION, ERROR FROM Remote-Operations-Information-Objects fioint-iso-itu-t remote-operations(4) informationObjects(5

37、) versionl(0); itu-t recommendation q 932 facility-information-element-component(3) ROS InvokeId:InvokeIdSet, OPERATION:Invokable, 0PERATION:Returnable) := CHOICE invoke il Invoke InvokeIdSet, Invokable, returnResult 2 ReturnResult Returnable, returnError 3 ReturnError Errors Returnable, reject 41 R

38、eject 1 (CONSTRAINED BY - must conform to the above dejnition - ! Rejectproblem : general-UnrecognizedPDU) Invoke InvokeId:InvokeIdSet, 0PERATION:Operations) := SEQUENCE invokeId InvokeId (InvokeIdSet) (CONSTRAINED BY - must be unambiguous - ! Rejectproblem : invoke-duplicatehvocation), linkedId CHO

39、ICE present O IMPLICIT present InvokeId, absent i IMPLICIT NULL 1 (CONSTRAINED BY - must identzfi an outstanding operation - ! Rejectproblem : invoke-UnrecognizedLinkedId) (CONSTRAINED BY - which has one or more linked operations- ! Rejectproblem : invoke-linkedResponseUnexpected) OPTIONAL, opcode O

40、PERATION. NOTIFICATION := CLASS I I - for the support of general addressing, the protocol profile shall be set to the value “GAT Protocol“. d) For local signalling, indicate any address required for the multiple subscriber number or subaddressing supplementary service, if applicable. e) For general

41、signalling, indicate any address and identification information required for addressing and identification within the transport mechanism. If the GFT-Control entity is unable to provide the transfer of generic functional data, it shall indicate this to the ROSE entity or any other appropriate ASE. t

42、he point-to-point bearer-related transport mechanism defined in 6.3.1 ; the broadcast bearer-related transport mechanism defined in 6.3.1 ; the point-to-point transport mechanism (connection-oriented) defined in 6.3.2.1 ; the broadcast transport mechanism (connection-oriented) defined in 6.3.2.2; th

43、e broadcast transport mechanism (connectionless) defined in 6.3.2.3. the point-to-point bearer-related transport mechanism defined in 6.3.1 ; the broadcast bearer-related transport mechanism defined in 6.3.1 ; the point-to-point transport mechanism (connection-oriented) defined in 10.1. b) c) 11.1.2

44、 Receipt of generic functional data When a transport mechanism receives a Facility information element, this is indicated to the GFT-Control entity. The GFT-Control entity shall check the protocol profile, and if it is valid it shall indicate this data to the appropriate ASE. In particular, if the p

45、rotocol profile is set to “ROSE“, this shall be indicated to the ROSE entity. If the protocol profile is set to a reserved value, or to a value of protocol profile that is not supported, the generic functional data shall be discarded, and the procedures for unrecognized information element content h

46、andling as specified in 5.8.7.1 or 5.8.7.2/Q.93 1, as appropriate, shall be followed on the appropriate transport mechanism. The error handling rules in 5.8.7.1 and 5.8.7.2/Q.931 shall apply only for errors in the octets 1 through 3 of the Facility information element. Errors in subsequent octets sh

47、all be handled according to the appropriate ROSE protocol procedures. 11.2 GAT-Control When general addressing is supported, the GAT-Control entity shall be provided, and the procedures for the GAT protocol specified in ITU-T 4.860 shall apply. ITU-T Q.932/Amd.l (06/2000) 9 10) AnnexC 4 Replace the

48、definition of the PartyNumber in Table C-1 with the following: PartyNumber NsapEncodedNumber := CHOICE UnknownPartyNumber O IMPLICIT NumberDigits, - the numberingplan is the default numbering plan of the - network. It is recommended that this value is used. publicPartyNumber i IMPLICIT PublicPartyNu

49、mber, - the numberingplan is according to - ITU-T Recommendation E.164. nsapEncodedNumber 2 IMPLICIT NsapEncodedNumber, - ATM endsystem address encoded as an NSAP address. dataPartyNumber 3 IMPLICIT NumberDigits, - not used, value resewed. telexPartyNumber 4 IMPLICIT NumberDigits, - not used, value resewed. privatePartyNumber 5 IMPLICIT PrivatePartyNumber, nationalStandardPartyNumber 8 IMPLICIT NumberDigits - not used, value resewed. := OCTET ST