1、STD.ITU-T RECMN 8.759-ENGL 1993 m YBb2571 Obb3207 739 m GENERAL SECRETARIAT INTERNATIONAL TELECOMMUNICATION UNION Subject: INFORMATION NOTE Geneva. June 1999 Recommendation ITU-T 4.954 (03/93) TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU ITU-T Recommendation 4.954 (03/93) Stage 3 description for
2、multiparty supplementary services using DSS 1 Clause 1 - Conference calling Clause 2 - Three-party service This covering note is to warn readers that the version of ITU-T 4.954.2 (03/93) contained in the volume ITU-T 4.954 (03/93) is “obsolete“, superseded by ITU-T 4.954.2 (10/95). Only ITU-T 4.954.
3、1 (03/93) remains in force. ITU-T 4.954.2 (03/93) was originally published with ITU-T Q.954.1 (03/93) in the same volume named ITU-T 4.954 (03/93). ITU-T Q.954.2 (10/95) was subsequently published separately. To correct this situation, the electronic version of ITU-T 4.954 (03/93) was split into two
4、, with ITU-T 4.954.1 (03/93) remaining “in-force and ITU-T 4.954.2 (03/93) labelled as “obsolete“. Union internationale des tlcommunications Place des Nations 1211 GENVE 20 Suisse - Switzerland - Suiza ITU-T RECMN+Q.54 93 M 4862593 0590203 Lb2 INTERNATIONAL TELECOMMUNICATION UNION l ITU-T TELECOMMUN
5、ICATION STANDARDIZATION SECTOR OF ITU Q.954 (03/93) DIGITAL SUBSCRIBER SIGNALLING SYSTEM No. 1 STAGE 3 DESCRIPTION FOR SUPPLEMENTARY SERVICES USING DSS 1 STAGE 3 DESCRIPTION FOR MULTIPARTY SUPPLEMENTARY SERVICES USING DSS 1 CLAUSE 1 - CONFERENCE CALLING CLAUSE 2 - .THREE-PARTY SERVICE ITU-T Recommen
6、dation Q.954 (Previously “CCIlT Recommendation”) FOREWORD The IT Telecommunication Standardization Sector (ITU-T) is a permanent organ of the International Telecom- munication Union. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them w
7、ith a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Conference (WTSC), which meets every four years, established the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics. IT-T Recommendat
8、ion 4.954, clauses 1 and 2, was prepared by, the ITU-T Study Group XI (1988-1993) and was approved by the WTSC (Helsinki, March 1-12, 1993). NOTES 1 As a consequence of a reform process within the International Telecommunication Union (ITU), the CCITT ceased to exist as of 28 February 1993. In its p
9、lace, the Telecommunication Standardization Sector (ITU-T) was created as of 1 March 1993. Similarly, in this reform process, the CCIR and the IFRB have been replaced by the Radiocommunication Sector. In order not to delay publication of this Recommendation, no change has been made in the text to re
10、ferences containing the acronyms “CCITT, CCIR or IFRB” or their associated entities such as Plenary Assembly, Secretariat, etc. Future editions of this Recommendation will contain the proper terminology related to the new IT structure. 2 telecommunication administration and a recognized operating ag
11、ency. In this Recommendation, the expression “Administration” is used for conciseness to indicate both a O ITU 1994 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
12、ission in writing from the ITU. 4862591 0590205 CONTENTS T35 1 Conference calling . 1.1 Definition 1.2 Description 1.3 Operational requirements 1.4 Coding requirements . 1.5 Signalling requirements 1.6 Interactions with other supplementary services 1.7 Interactions with other networks . 1.8 Signalli
13、ng flows 1.9 Parameter values . 1.10 Dynamic description (SDLs) 2 Three-Party Service 2.1 Definition 2.2 Description 2.3 Operational requirements 2.4 Coding requirements . 2.5 Signalling requirements 2.6 Interactions with other supplementary services 2.7 Interactions with other networks . 2.8 Signal
14、ling flows 2.9 Parameter values . 2.10 Dynamic description . Appendix I (referred to in clause 2) - Diagrammatic description of coding requirements . I . 1 1.2 Return result components . 1.3 Return error components Invoke components . Page 1 1 1 2 2 6 12 15 16 25 25 44 44 44 45 45 45 48 50 51 56 56
15、60 61 61 62 References . 62 Recommendation Q.954 (03/93) i Recommendation 4.954 STAGE 3 DESCRIPTION FOR MULTIPARTY SUPPLEMENTARY SERVICES USING DSS 1 (Helsinki, 1993) 1 Conference calling 1.1 Definition This supplementary service provides a user with the ability to have a multi-connection call, i.e.
16、 a simultaneous communication between more than two parties. 1.2 Description 1.2.1 General description When conference calling is invoked, conference resources (e.g. a “bridge”) are allocated to the served user and any calls indicated by the service request are added to the conference. Once a confer
17、ence is active, parties may be added, dropped, isolated (i.e. prevented from communicating with the conference), reattached or split (Le. removed from the conference but remain connected to the conference controller). The controller can place hisher connection to the conference on hold, retrieve the
18、 conference, end the conference, or disconnect himselfherself from the conference. 1.2.2 Specific terminology 1.2.2.1 User The DSS 1 protocol entity at the user side of the user-network interface. 1.2.2.2 Network The DSSl protocol entity at the network side of the user-network interface. 1.2.2.3 Ser
19、ved user The DSSl protocol entity at the user side of the user-network interface used to request and control the CONF supplementary service. 1.2.2.4 Remote user The DSSl protocol entity at the user side of the user-network interface which is involved in a instance of the CONF supplementary service b
20、ut which has no control of it. I 1.2.2.5 Isolate An action that restricts communications with a participant of the conference. 1.2.2.6 Reattach An action that re-establishes the communication with a participant of the conference. 1.2.2.7 Split An action that creates a normal call between the served
21、user and a remote user. 1.2.2.8 Drop An action that clears the connection to a remote user. Recommendation Q.954 (03/93) 1 1.2.2.9 Floating The situation in which an instance of the CONF supplementary service exists without the served user. 1.2.2.10 Conference ID An identifier that identifies an ins
22、tance of the CONF supplementary service. 1.2.2.11 Party ID An identifier that identifies a participant within an instance of the COW supplementary service. 1.2.2.12 Invoke component See 8.2.5.1.VQ.932 i. 1.2.2.13 Return result component See 8.2.5.1.1lQ.932 11. 1.2.2.14 Return error component See 8.2
23、.5.1.1Q.932 i. 1.2.3 This service is only applicable to telephony teleservices. The applicability of the 7 kHz audio bearer capability is for further study. Qualification on the applicability to telecommunication services 1.2.4 State definitions The call states associated with basic call control acc
24、ording to Recommendation 4.931 2 shall apply. No other states are used to describe the CONF supplementary service. 1.3 Operational requirements 1.3.1 Provision and withdrawal Not applicable. 1.3.2 Not applicable. Requirements on the originating network side 1.3.3 Not applicable. Requirements on the
25、destination network side 1.4 Coding requirements Table 1-1 shows the definition of the operations and errors required for the CONF supplementary service using ASN.1 as specified in Recommendation X.208 4 and using the OPERATION and ERROR macro as defined in Figure 4K.219 5. All components (invoke, r
26、eturn result, return error and reject) shall be included within a Facility information element. This Facility information element may be included in any appropriate message unless a more restricting specification is given. Table 1-2 contains the additional codepoints for the CONF supplementary servi
27、ce which shall be employed in octet 3 of the Notification indicator information element (to be conveyed in the NOTFY message). Table 1-3 shows the definition of the extended notification required for the CONF supplementary service using ASN.1 as specified in Recommendation X.208 41 and using the NOT
28、IFICATION macro as specified in Recommen- dation 4.932 i. 2 Recommendation Q.954 (03/93) TABLE 1 - 1 /Q.954 Definition of operations and errors SonferenceAdd-On-Operations ccitt recommendation q 954 conference-add-on-operations- and-errors (1 ) ) 3EFINITIONS := 3EGIN EXPORTS IMPORTS BeginCONF, AddCO
29、NF, SplitCONF, DropCONF, IsolateCONF, ReattachCONF, PartyDISC, FloatCONF, EndCONF, IllConferenceld, IIIPartyld, NumberOf PartiesExceeded, NotActive, NotAllowed, Partyld, Conference1 d, Conf Size; OPERATION, ERROR FROM Remote-Operation-Notation joint-iso-ccitt remote-operations(4) notation(0) ) UserN
30、otSubscribed, notAvailable, resourceUnavailable, invalidCallState, supplementaryServiceInteractionNotAllowed FROM General-Error-List ccitt recommendation q 950 general-error-list (1) ; BeginCONF:= OPERATION ARGUMENT ConfSize - optional Conferenceld, Partyld OPTIONAL ) RESULT SEQUENCE ERRORS userNotS
31、ubscnbed, notAvailable, resourceUnavailable, invalidCallState ) AddCONF := OPERATION ARGUMENT Conferenceld RESULT Partyld ERRORS IIIConferenceld, NumberOf PartiesExceeded, NotAllowed, supplementary ServiceInteractionNotAllowed, invalidCallState SplitCONF:= OPERATION ARGUMENT RESULT ERRORS DropCONF :
32、= OPERATION ARGUMENT RESULT ERRORS IsolateCONF := OPERATION ARGUMENT RESULT ERRORS ReattachCONF := OPERATION ARGUMENT RESULT ERRORS SEQUENCE Conferenceld, Partyld IllConferenceld, IIIPartyld Partyld IIIPartyld, NotActive ) Partyld IIIPartyld, NotActive Partyld IIIPartyld, NotActive Recommendation Q.
33、954 (0-3) 3 TABLE 1-UQ.954 (continued) Definition of operations and errors PartyDISC := OPERATION ARGUMENT RESULT ERRORS ERRORS ERRORS Identifyconferee := OPERATION ARGUMENT IllConferenceld := ERROR IIIPariyld := ERROR NumberOfPartiesExceeded := ERROR NotActive := ERROR NotAllowed := ERROR Partyld :
34、= := INTEGER (0127) Conferenceld := INTEGER (0127) ConfSize := INTEGER (0127) FioatCONF := OPERATION EndCONF := OPERATION , beginCONF BeginCONF := 40 addCONF AddCONF := 41 SplitCONF SplitCONF := 42 dropCONF DropCONF := 43 isolateCoNF IsolateCONF := 44 reattachCONF ReattachCONF := 45 partyDISC PartyD
35、ISC := 46 floatCONF FloatCONF := 47 endCONF EndCONF := 48 identifyconferee Identifyconferee := 49 illconferenceld iilconferenceld := 28 illPartyld IIIPartyld := 29 numberOfPaities Exceeded NumberOfParties Exceeded := 30 notActive NotActive := 31 notAllowed NotAllowed := 32 END - of Confefence-Addn-e
36、perations Partyld IIIPartyld, NotActive ) NotActive, NotAllowed NotActive Partyld 4 Recommendation Q.954 (03/93) ITU-T RECMN*Q-754 73 4862571 0570230 3T2 TABLE 1-UQ.954 Additional codepoints in the Notifcation indicator information element Bits 87654321 11000010 11000011 11000100 11000101 110001 10
37、11 O00 11 1 11001000 11001001 11001010 11001011 Meaning Conference established, i.e. the user takes part in a multiparty call Conference disconnected, i.e. the user takes part in a, normal, two party call Other party added Isolated Reattached Other party isolated Other party reattached Other party s
38、plit Other party disconnected Conference floating TABLE 1-3/Q.954 Definition of extended notification Conference-Add-on-Notifications ccitt recommendation q 954 conference-add-on (1) extended-notifications (2) DEFINITIONS - BEGIN EXPORTS PartyldNotfflcat ion; IMPORTS NOTIFICATION - FROM ccitt recomm
39、endation q 932 notificationdata-structure (5) Partyld FROM Conference-Add-On-Operations ccitt recommendation q 954 conference-add-on (1) operations-and-types (1) ; ARGUMENT Partyld PartyldNotification := NOTIFICATION paryldNotiflcation, PartyldNotification := 1 END - of ConferenceAdd-On-Nofification
40、s 5 ITU-T RECMN*Q.954 93 m YB62591 0590211 239 m 1.5 Signailing requirements Where the text in the following sections refers to an “xxxx” invoke component, an invoke component is meant with its operation value set to the value of operation “xxxx”. 1.5.1 Activation, deactivation and registration Not
41、applicable, Le. no signalling procedures are required for the activation, deactivation or registration of this supplementary service. 1.5.2 Invocation and operation 1.5.2.1 Beginning the conference from the idle state 1.5.2.1.1 Normal operation To request a conference (i.e. without an initial confer
42、ee), the served user shall send a SETUP message to the network including a Facility information element and a Bearer capability information element. The Facility information element shall contain a BeginCONF-Invoke component. This component may contain a ConfSize parameter indicating the maximum num
43、ber of conferees. If this parameter is not provided, then the network shall set the conference size to a network dependent value. The Bearer capability information element shall indicate an appropriate bearer capability with regard to the applicability of the conference call add-on service. The Call
44、ed party number and the Called party subaddress information element shall be omitted by the user. Further the normal basic call procedures apply according to 5.11Q.931 2. When the network responds with a CONNECT message it shall include a BeginCONF-Retum-Result component in a Facility information el
45、ement. This component contains a ConferenceId parameter. The ConferenceId shall be used in some operations to identify the conference explicitly. When the user receives a correctly encoded BeginCONF-Return-Result component the user shall accept the provided information, save the included ConferenceI
46、d and shall not respond to the network. The procedures used to request a conference are completely independent from other calls. 1.5.2.1.2 Exceptional procedures If the user is not subscribed to the CONF supplementary service, the network shall start the basic call clearing procedures as defined in
47、5.3/4.931 2. One of the messages sent by the network to the served user shall contain a Facility information element with a BeginCONF-Retum-Error component indicating the error “notSubscribed”. Furthermore this message shall contain a Cause information element indicating cause No. 3 1 “Normal, unspe
48、cified” and a location of “public network serving the local user”. If the user is not subscribed to the basic service as requested in the SETUP message, the network shall start the basic call clearing procedures as defined in 5.3/Q.931 2. If the user indicates an inappropriate bearer capability, the
49、 network shall start the basic call clearing procedures as defined in 5.3/Q.931 2. One of the messages sent by the network to the served user shall contain a Facility information element with a BeginCONF-Return-Error component indicating the error “notAvailable”. Furthermore this message shall contain a Cause information element indicating cause No. 31 “Normal, unspecified” and a location of “public network serving the local user”. If the network cannot accept t
