ITU-T Q 2971 CORR 1-1999 Digital Subscriber Signalling System No 2 (DSS2) - User-Network Interface Layer 3 Specification for Point-to-Multipoint Call Connection Control - Corrigendoad.pdf

1、INTERNATIONAL TELECOMMUNICATION UNION ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU Q.2971 Corrigendum I (1 2/99) SERIES Q: SWITCHING AND SIGNALLING Broadband ISDN - B-ISDN application protocols for access signalling Digital subscriber signalling system No. 2 (DSS2) - User-Network Interface

2、Layer 3 specification for point-to-multipoint CalllConnection Control Corrigendum I ITU-T Recommendation Q.2971 - Corrigendum 1 (Previously CCITT Recommendation) INTERNATIONAL TELECOMMUNICATION UNION ITU=T TE LE CO M M U N I CATI ON STANDARDIZATION SECTOR OF ITU Q.2971 Corrigendum 1 (1 2/99) SERIES

3、Q: SWITCHING AND SIGNALLING Broadband ISDN - B-ISDN application protocols for access sign al I i ng Digital subscriber signalling system No. 2 (DSS2) - User-Network Interface Layer 3 specification for point-to-mltipoint Call/Connection Control Corrigendum 1 ITU-T Recommendation Q.2971 - Corrigendum

4、I (Previously CCITT Recommendation) ITU-T Q-SERI ES RECOMMENDATIONS SWITCHING AND SIGNALLING SIGNALLING IN THE INTERNATIONAL MANUAL SERVICE INTERNATIONAL AUTOMATIC AND SEMI-AUTOMATIC WORKING FUNCTIONS AND INFORMATION FLOWS FOR SERVICES IN THE ISDN SPECIFICATIONS OF SIGNALLING SYSTEMS No. 4 AND No. 5

5、 SPECIFICATIONS OF SIGNALLING SYSTEM No. 6 SPECIFICATIONS OF SIGNALLING SYSTEM R1 SPECIFICATIONS OF SIGNALLING SYSTEM R2 DI G ITAL EXCHANGES INTERWORKING OF SIGNALLING SYSTEMS SPECIFICATIONS OF SIGNALLING SYSTEM No. 7 DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 PUBLIC LAND MOBILE NETWORK INTERWORKING

6、 WITH SATELLITE MOBILE SYSTEMS INTELLIGENT NETWORK CLAUSES APPLICABLE TO ITU-T STANDARD SYSTEMS SIGNALLING REQUIREMENTS AND PROTOCOLS FOR IMT-2000 BROADBAND ISDN General aspects Signalling ATM adaptation layer (SAAL) Signalling network protocols Common aspects of B-ISDN application protocols for acc

7、ess signalling and network signalling and interworking B-ISDN application protocols for the network signalling B-ISDN application protocols for access signalling Q.l-Q.3 Q.4-Q.59 Q.60-Q.99 Q. 1 OO-Q. 1 19 Q.120-Q.249 Q.250-Q.309 Q.310-Q.399 Q.400-Q.499 Q.500-Q.599 Q.600-Q.699 Q. 700-Q. 849 Q.850-Q.9

8、99 Q. 1000-Q. 1 O99 Q.1100-Q.1199 Q.1200-Q.1699 Q. 1700-Q.1799 Q.2000-Q.2999 Q.200O-Q.2099 Q.21 OC-Q.2199 Q.2200-Q.2299 Q.2600-Q.2699 Q.2700-Q.2899 4.2900-Q.2999 For further details, please refer to ITU-T List of Recommendations. ITU-T RECOMMENDATION 4.2971 DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 2

9、 (DSS2) - USER-NETWORK INTERFACE LAYER 3 SPECIFICATION FOR POINT-TO-MULTIPOINT CALL/CO“ECTION CONTROL CORRIGENDUM 1 Summary This Corrigendum is issued in order to correct editorial and minor technical errors contained in Recommendation 4.2971 (1995). Source Corrigendum 1 to ITU-T Recommendation 4.29

10、71, was prepared by ITU-T Study Group 11 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on 3 December 1999. Recommendation Q.2971/Cor. 1 (1 2/99) 1 FOREWORD ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications

11、. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent 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 Telecommunic

12、ation Standardization Conference (WTSC), which meets every four years, establishes 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 ITU-T is covered by the procedure laid down in WTSC R

13、esolution No. 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 In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication adminis

14、tration and a recognized operating agency. 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. The ITU takes no position concerning the evidence, validity or a

15、pplicability 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 intellectual property, protected by patents, which may be required

16、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 2000 All rights reserved. No part of this publication may be reproduced or utilized in any form or by an

17、y means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU. 11 Recommendation Q.2971Kor.l (12/99) Recommendation 4.2971 DIGITAL SUBSCRIBER SIGNALLING SYSTEM NO. 2 (DSS2) - USER-NETWORK INTERFACE LAYER 3 SPECIFICATION FOR POINT-TO-MULTIPOINT CA

18、LL/CONNECTION CONTROL CORRIGENDUM 1 (Geneva, 1999) 1) Clause 2 a) Replace reference No. 6 ITU-T Recommendation 4.26 1 O ( 1995) with ITU-T Recommendation 4.26 1 O (1999). b) Replace reference No. 9 ITU-T Recommendation 4.2961 (1995) with ITU-T Recommendation 4.2961.1 (1995) and update all references

19、 in the Recommendation text accordingly. 2) Subclause 5.2 In thefirst paragraph, replace 1.514.293 1 with 1.314.293 1. 3) Subclause 5.3 Replace the fourth paragraph with: Multiple add party requests pending at the same time are allowed (e.g. the root does not need to wait for a response related to o

20、ne add party request before issuing the next one). 4) Subclause 8.1.2.1 Replace Notes 1, 2 and 3 of Table 8-10 with: NOTE 1 - Included in the user-to-network direction when the calling user wants to pass ATM adaptation layer parameters information to the called user. Included in the network-to-user

21、direction if the calling user included an AAL parameters information element in the ADD PARTY message. Must be the same as the one negotiated during the initial call setup, but is not checked by the network. NOTE 2 - Included in the user-to-network direction when the calling user wants to pass broad

22、band high layer information to the called user. Included in the network-to-user direction if the calling user included a Broadband high layer information information element in the ADD PARTY message. Must be the same as the one negotiated during the initial call setup, but is not checked by the netw

23、ork. NOTE 3 - Included in the user-to-network direction when the calling user wants to pass broadband low layer information to the called user. Included in the network-to-user direction if the calling user included a Broadband low layer information information element in the ADD PARTY message. Must

24、be the same as the one negotiated during the initial call setup, but is not checked by the network. Only one Broadband low layer information information element is permitted in the ADD PARTY message. 5) Subclause 8.2.1 Replace thefirst sentence with: The purpose of the Endpoint reference information

25、 element is to idente the individual endpoints of a point-to-multipoint call to which the particular message applies and can be used to indicate that parties other than the first party can not negotiate (see 9.1.1). Recommendation Q.2971Kor.l (12/99) 1 6) Subclause 8.2.1 Replace Figure 8-1 and its a

26、ssociated text by the followingfigure and table: ext. 1 Coding E instruction field Standard Flag I Res. I IE Action Ind. o1 1 Endpoint reference ext. 1 Endpoint reference value Coding JE instruction field Standard Flag I Res. I IE Action Ind. flag Endvoint reference value (continued) Figure 8-UQ.297

27、1- Endpoint reference information element Table 8-16/Q.2971- Endpoint reference information element Octets 1 2 3 4 5 6 6.1 Endpoint reference Qpe (octet 5) Bits 87654321 00000000 Locally defined integer All other values are reserved. Endpoint referenceflag (octet 6) Bit - 8 O 1 The message is sent f

28、rom the side that originated the endpoint reference The message is sent from the side that originated the endpoint reference Endpoint reference value (octet 6, 6.1) The endpoint reference is a 15-bit integer (coded in binary) to uniquely identi an endpoint. 7) Subclause 8.2.2 Replace Figure 8-2 and

29、its associated text by the followingfigure and table: 8 7 6 5 4 3 2 1 Octets I ! 2 I Spare Io O I Endpoint party state I I I Figure 8-2/Q.2971- Endpoint state information element Recommendation Q.297UCor.l (12/99) 5 Table 8-17/Q.2971- Endpoint state information element Endpoint party state (octet 5)

30、 Bits 654321 000000 Null 000001 Add Party Initiated 000100 Party Aierting Delivered 000110 Add Party Received O001 11 Party Alerting Received 001011 Drop Party Initiated O01 100 Drop Party Received 001010 Active All other values are reserved. 8) Subclause 8.2.3 Renumber Table 8-16, Additional multip

31、arv message types as Table 8-18. 9) Subclause 8.2.4 a) Replace the title of this subclause with: 8.2.4 Cause values for the Cause information element b) Delete the table showing the definitions for cause values #32 and #73. c) Replace the first paragraph by: The cause values in 3.2/Q.2610 are applic

32、able. 10) Subclause 9.1.1 Add the following note at the end of the thirdparagraph: NOTE - The term “negotiation“ in the context of this Recommendation relates to Broadband low layer negotiation according to Annex UQ.293 1 and ATM adaption layer parameters negotiation according to hex F/Q.293 1 only.

33、 Other types of negotiation are outside the scope of this Recommendation. 11) Subclause 9.1.2 Replace the last sentence of the first paragraph with: The user shali send an ADD PARTY message only if the link is in the Active link state or in the Call Delivered link state and negotiation with the firs

34、t leaf is not allowed. 12) Subclause 9.1.3 Replace the first sentence of the second paragraph with: Similarly, if the network determines that a requested service is not available, the network shall send an ADD PARTY REJECT message with one of the following causes following the procedures of 9.3.2: 1

35、3) Subclause 9.2 Replace the title of this subclause with: Subsequent party establishment at the destination side Recommendation Q.2971Kor.l (12/99) 3 14) Subclause 9.2 In the secondparagraph, replace the second sentence with: The SETUP message shall contain the Endpoint reference information elemen

36、t and the Broadband bearer capability information element shall indicate ”point-to-multipoint” in the user plane connection configuration field. 15) Subclause 9.2 Replace the last two paragraphs of this subclause with: At the terminating interface, the ADD PARTY, ADD PARTY ACKNOWLEDGE, ADD PARTY REJ

37、ECT, PARTY ALERTING, DROP PARTY, and DROP PARTY ACKNOWLEDGE messages shall not be used. At the terminating interface, the receipt of an ADD PARTY, ADD PARTY ACKNOWLEDGE, ADD PARTY REJECT, PARTY ALERTING, DROP PARTY, or DROP PARTY ACKNOWLEDGE message shall be treated as an unrecognized or unexpected

38、message. 16) Subclause 9.3.3.1 Replace the text of this subclause with: In order to drop itself, the leaf shall send a RELEASE or RELEASE COMPLETE message according to the procedures of 5.4.2/Q.293 1 and 5.4.3/Q.293 1 and shall enter the Null party state. 17) Subclause 9.3.3.2 In thefirst paragraph,

39、 delete the reference to subclause 9.3.2. 18) Subclause 9.3.3.2 In the fourth paragraph, replace the text of the 2nd bullet item Mth: a when all other parties associated with the call are in the Drop Party Initiated, or Drop Party Received party state, the network shall initiate procedures for dropp

40、ing the party along the path to the remote user, send a RELEASE message to the user with cause #3 1, “normal, unspeczj?ed” and enter the Null party state. 19) Subclause 9.3.3.2 In the fourth paragraph, 2nd bullet item, 5th paragraph, 6th paragraph 2nd bullet item and 7th paragraph, delete “Null, It

41、from the sequence of party states at all occurrences so that only the Drop Party Initiated and Drop Party Received party state remain. 20) Subclause 9.3.3.2 In the last paragraph, replace the text of the first bullet item Mth: 0 for any party in the Drop Party Initiated or Drop Party Received party

42、state all party timers shall be stopped and the Null party state shall be entered; and 21) Subclause 9.3.3.2 Delete Note 2 in the last paragraph. 22) Subclause 9.3.4.2 Replace the first paragraph with: Apart fiom the exception conditions identified in 9.3.2 and 9.5, the network shall initiate droppi

43、ng a party at the root interface by sending a DROP PARTY or RELEASE message with the cause value received Tom the network or remote user. 4 Recommendation Q.2971/Cor.l (12/99) 23) Subclause 9.3.4.2 In the fourth paragraph, Ist bullet item, 5th paragraph, 6th paragraph 2nd bullet item and 7th paragra

44、ph, delete “Null, I from the sequence of party states at all occurrences so that only the Drop Party Initiated and Drop Party Received party state remain. 24) Subclause 9.3.4.2 In the fourth paragraph replace the text of the Ist bullet item with: 0 when all other parties associated with the call are

45、 in the Drop Party Initiated or Drop Party Received party state, the user shall send a RELEASE message with cause #31, “normal, unspecified“ and enter the Null party state; or 25) Subclause 9.3.4.2 Replace the last sentence of the last paragraph with: When the user receives a RELEASE message, for al

46、l parties (for this call) party timers shall be stopped and the Null party state shall be entered. 26) Subclause 9.3.5 In the second paragraph, delete “Null, If from the sequence of party states so that only the Drop Party Initiated and Drop Party Received party state remain. 27) Subclause 9.3.5 Rep

47、lace the 2nd paragraph with: Similarly, upon receiving a DROP PARTY or ADD PARTY REJECT message while in the Drop Party Initiated party state, and while all parties associated with the call are in the Drop Party Initiated or Drop Party Received party state, the recipient shall stop timer T398, disco

48、nnect the bearer virtual channel, and send a RELEASE message with cause #3 1 “normal, unspeczped“. 28) Subclause 9.3.6 Replace the jrst sentence of the first paragraph with: All parties of a call can be dropped by the root by sending a RELEASE message with an appropriate cause value according to 4.2

49、610 to the network. 29) Subclause 9.3.6 Replace the first sentence of the 2nd paragraph with: In order to initiate the dropping of all parties, while in the Active or Call Delivered link state, the network shall first send an ADD PARTY REJECT message with the cause value received from the network for each party in the Add Party Received party state and then shall send a RELEASE message with cause #3 1 “normal, unspecified“. 30) Subclause 9.5.3.2.1 In item d), replace 5.6.7.214.293 1 with 5.6.7. UQ.2931. 31) Subclause 9.5.3.2.3 Replace the text of item a) with the