ITU-T Q 84 1-1993 Stage 2 Description for Multiparty Supplementary Services Clause 1 - Conference Calling (CONF) - General Recommendations on Telephone Switching and Signalling Funthe .pdf

《ITU-T Q 84 1-1993 Stage 2 Description for Multiparty Supplementary Services Clause 1 - Conference Calling (CONF) - General Recommendations on Telephone Switching and Signalling Funthe .pdf》由会员分享，可在线阅读，更多相关《ITU-T Q 84 1-1993 Stage 2 Description for Multiparty Supplementary Services Clause 1 - Conference Calling (CONF) - General Recommendations on Telephone Switching and Signalling Funthe .pdf（47页珍藏版）》请在麦多课文档分享上搜索。

1、INTERNATIONAL TELECOMMUNICATION UNION)45G134 1 TELECOMMUNICATION (03/93)STANDARDIZATION SECTOROF ITU%.%2!,G0G02%#/-%.$!4)/.3G0G0/.G0G04%,%0(/.%37)4#().G0G0!.$G0G03).!,).it does however specify which functional entities may be allocated to a private ISDN.This Recommendation does not specify the addit

2、ional requirements where the service is provided to the user via atelecommunications network that is not an ISDN.The Conference calling supplementary service provides a user with the ability to have a multi-connection call, i.e. asimultaneous communication between more than two parties.The Conferenc

3、e calling supplementary service is defined for all telecommunication services carrying speech.This Recommendation is applicable to the stage 3 Recommendations for the Integrated Services Digital NetworkConference calling supplementary service. The term stage 3 is also defined in Recommendation I.130

4、. Where the textindicates the status of a requirement, i.e. as strict command or prohibition, as authorization leaving freedom, as acapability or possibility, this shall be reflected in the text of the relevant stage 2 and 3 Recommendations.Furthermore, conformance to this Recommendation is met by c

5、onforming to the stage 3 Recommendation with the fieldof application appropriate to the equipment being implemented. Therefore, no method of testing is provided for thisRecommendation.1.2 ReferencesThese references are cited at the appropriate places in the text and the publications are listed herea

6、fter. For datedreferences subsequent amendments to, or revisions of, any of these publications apply to this Recommendation onlywhen incorporated in it by amendment or revision. For undated references, the latest edition of the publication referredto applies.1 CCITT Recommendation I.130 Method for t

7、he characterization of telecommunication services supported by anISDN and network capabilities of an ISDN, 1988.2 CCITT Recommendation Q.65 Stage 2 of the method for the characterization of services supported byand ISDN, 1988.2 Recommendation Q.84 (03/93)3 CCITT Recommendation I.112 Vocabulary of te

8、rms for ISDNs, 1988.4 CCITT Recommendation Q.71 ISDN 64 kbit/s circuit mode switched bearer service, 1992.5 CCITT Recommendation I.254.1 Integrated Services Digital Network (ISDN); Conference calling (CONF)supplementary service; service description.6 CCITT Recommendation Z.100 SDL Specification Desc

9、ription Language, 1988.1.3 DefinitionsFor the purpose of this Recommendation, the following definitions apply:conference controller: The served user controlling the conference.conferee: A conference participant not being the conference controller.multi connection call control: A CC entity with the a

10、bility to control one connection directly and several others viaOCCC entities.one connection call control: A CC entity with the ability to control a single connection for a MCCC entity.party: Either a conferee or the conference controller.forward connection: The connection between a CC located with

11、the Service Providing Entity and a conferees CCA.backward connection: The connection between the served users CCA and a CC located with the Service ProvidingEntity.1.4 Symbols and abbreviationsCId Conference IdentifierCONF Conference callingFEA Functional Entity ActionISDN Integrated Services Digita

12、l NetworkLE Local ExchangeMCCC Multi Connection Call ControlOCCC One Connection Call ControlPId Party IdentifierPNX Private Network ExchangeSDL Specification and Description LanguageTE Terminal Equipment1.5 DescriptionConference calling supplementary service can be invoked either from the idle state

13、 or as a network option from anexisting active call.When conference calling supplementary service is invoked, conference resources (e.g. a “bridge”) are allocated to theserved user. In the case of invocation from an active call, this will be automatically connected by the network to theconference re

14、sources.Once a conference is active, parties may be added, dropped, isolated (i.e. prevented from communicating with theconference), reattached or split (i.e. removed from the conference but remain connected to the conference controller).Recommendation Q.84 (03/93) 31.6 Derivation of a functional mo

15、del1.6.1 Functional model descriptionThe model has been based on the concept that the served user maintains by means of FE1 a single relation to the centreof the conference FE2. FE2 has the ability to have simultaneous relations with all the conferees.This concept has been depicted in Figure 1-1.T11

16、24630-90/d01FE1 FE2 FE3xFE3nrarbrbFIGURE 1-1/Q.84FIGURE 1-1/Q.84.D01 = 4,5 CMNOTE FE3x is the functional entity which belongs to that party which is explicitly identified by the conference controller(e.g. DROP party-X). FE3n are the functional entities which belong to the parties not identified by t

17、he conference controller (e.g. allparties except party-X).1.6.2 Description of functional entitiesFE1 Originating service agentFE2 Service providing entityFE3 Destination service agent1.6.3 Relation with a basic serviceThe relationship with a basic service is shown in Figure 1-2.T1124641-91/d02FE2 F

18、E3xFIGURE 1-2/Q.84FE1FE3nCCA CCCCCCCCCCCC CCACCArarbrbr2r2r2r2r3r3r1FIGURE 1-2/Q.84D02 = 6 CM4 Recommendation Q.84 (03/93)1.7 Information flows1.7.1 Information flows diagramsThe following information flow diagrams are identified: Figure 1-3 Requesting a new conference call; Figure 1-4 Change normal

19、 call into a conference call; Figure 1-5 Adding a new conferee; Figure 1-6 Isolating a conferee; Figure 1-7 Reattaching a conferee; Figure 1-8 Dropping a conferee from the conference; Figure 1-9 Splitting a conferee from the conference; Figure 1-10 Call clearing by conferee; Figure 1-11 Disconnect w

20、hen floating is not allowed; Figure 1-12 Disconnect when floating is allowed; Figure 1-13 Terminate conference; Figure 1-14 Disconnect controller.211913 221927922924905224T1128841-91/d03FE2FE3xFIGURE 1-3/Q.84Requesting a new conference callFE1FE3nrarbCONFreq.CONFconf.SETUPSETUPrbreq. indresp. confFI

21、GURE 1-3/Q.84.D03 = 8,5 CM1.7.2 Definition of individual information flows1.7.2.1 Modification to relationship r1associated with raThe CONF supplementary service defines the following modifications to the r1relationship.Recommendation Q.84 (03/93) 592192292392492J92592C93191190A926912T1128851-91/d04

22、FE2 FE3xFIGURE 1-4/Q.84Change normal call into a conference callFE1 FE3nrarbCONFreq.CONFconf.rbCONFreq. indCONFresp. confINFORM 1req. indINFORM 1indFIGURE 1-4/Q.84.D04 = 10,5 CM6 Recommendation Q.84 (03/93)93191490090190292X92Y92J92392592Z90A92C93190792C421411 903915T1128861-91/d05FE2 FE3xFIGURE 1-5

23、/Q.84Adding a new confereeFE1 FE3nrarbADDreq.ADDconf.rbADDreq. indADDresp. confDISCreq. indINFORM 1req. indINFORM 7req. indINFORM 1ind.INFORM 7ind.FIGURE 1-5/Q.84.D05 = 15,5 CMRecommendation Q.84 (03/93) 793191493192C91592992092B92C92AT1128871-91/d06FE2 FE3xFIGURE 1-6/Q.84Isolating a confereeFE1 FE3

24、nrarbISOLATEreq.rbISOLATEreq. indINFORM 4req. indINFORM 4ind.INFORM 8ind.ISOLATEresp. confISOLATEconf.INFORM 8req. indFIGURE 1-6/Q.84.D06 = 12 CM8 Recommendation Q.84 (03/93)93191493192C91592D92092E92C92FT1128881-91/d07FE2 FE3xFIGURE 1-7/Q.84Reattaching a confereeFE1 FE3nrarbREATTACHreq.rbREATTACHre

25、q. indINFORM 5req. indINFORM 5ind.INFORM 9ind.REATTACHresp. confREATTACHconf.INFORM 9req. indFIGURE 1-7/Q.84.D07 = 12 CMRecommendation Q.84 (03/93) 991493192C91592G92092H92J92K90492MT1128891-91/d08221FE2 FE3xFIGURE 1-8/Q.84Dropping a confereeFE1 FE3nrarbDROPreq.rbreq. indINFORM 10ind.DROPconf.INFORM

26、 10req. indDROPreq. indDROPresp. confRELEASEFIGURE 1-8/Q.84.D08 = 13 CM10 Recommendation Q.84 (03/93)93193192C211 22191090890190992N92092H92P90C92J92C92R90992P224912T1128901-91/d09FE2 FE3xFIGURE 1-9/Q.84Splitting a confereeFE1 FE3nrarbSPLITreq.rbINFORM 3ind.SPLITconf.INFORM 3req. indSETUPreq. indSET

27、UPresp. confINFORM 2req. indINFORM 2ind.FIGURE 1-9/Q.84.D09 = 14 CM90B92U92H92J92V91692C931421T1128911-91d10FE2 FE3xFIGURE 1-10/Q.84Call clearing by confereeFE1 FE3nrarbrbINFORM 10ind.INFORM 6req. indINFORM 6ind.INFORM 10req. indRELEASEreq. indFIGURE 1-10/Q.84.D10 = 9 CMRecommendation Q.84 (03/93) 1

28、132192W92L92W321T1128921-91/d11FE2 FE3xFIGURE 1-11/Q.84Disconnect when floating is not allowedFE1 FE3nrarbrbDISCreq. indRELEASEreq. indFIGURE 1-11/Q.84.D11 = 7,5 CM32132192W92L92Q92C92J931T1128931-91/d12FE2 FE3xFIGURE 1-12/Q.84Disconnect when floating is allowedFE1 FE3nrarbrbDISCreq. indINFORM 11req

29、. indINFORM 11ind.FIGURE 1-12/Q.84.D12 = 8,5 CM12 Recommendation Q.84 (03/93)91492S321421411T1128941-91/d13FE2 FE3xFIGURE 1-13/Q.84Terminate conferenceFE1 FE3nrarbrbRELEASEreq. indTERMINATECONFERENCEreq.TERMINATECONFERENCEDISCreq. indreq. indFIGURE 1-13/Q.84.D13 = 8,5 CM914931421411 90391592T92L92Q9

30、2C92JT1128951-91/d14FE2 FE3xFIGURE 1-14/Q.84Disconnect controllerFE1 FE3nrarbrbreq.DISCONNECTCONTROLLERreq. indDISCONNECTCONTROLLERDISCONNECTCONTROLLERresp. confDISCreq. indINFORM 11req. indINFORM 11ind.conf.FIGURE 1-14/Q.84.D14 = 12,5 CMRecommendation Q.84 (03/93) 131.7.2.1.1 Contents of SETUPThe a

31、dditional contents of SETUP are shown in Table 1-1.TABLE 1-1/Q.841.7.2.2 Relationship ra1.7.2.2.1 Contents of CONFThe contents of CONF are shown in Table 1-2.This confirmed information flow is used to request the Conference calling service from an existing call.TABLE 1-2/Q.841.7.2.2.2 Contents of CO

32、NF REJECTThe contents of CONF REJECT are shown in Table 1-3.TABLE 1-3/Q.84SETUP Allowed values req.ind resp.confConference indicator (Note 1) OptionalSplit indicator (Note 2) OptionalConference size (Note 3) Integer OptionalConference identity (Note 1) Integer OptionalConference identity (Note 2) In

33、teger OptionalParty identity (Note 2) Integer OptionalNOTES1 This information element is mandatory when a conference call is requested.2 This information element is mandatory when a two party call to a conference is requested.3 This information element shall only be used if a conference call is requ

34、ested.CONF Allowed values req.ind resp.confConference size Integer OptionalParty identity Integer MandatoryCONF REJET Allowed values req.indCause No bridge Mandatory14 Recommendation Q.84 (03/93)1.7.2.2.3 Contents of ADDThe contents of ADD are shown in Table 1-4.This confirmed information flow appea

35、rs from FE1 to FE2 and is used to request to add a call to the indicatedconference.TABLE 1-4/Q.841.7.2.2.4 Contents of ADD REJECTThe contents of ADD REJECT are shown in Table 1-5.TABLE 1-5/Q.841.7.2.2.5 Contents of ISOLATEThe contents of ISOLATE are shown in Table 1-6.This confirmed information flow

36、 appears between FE1 and FE2 and is used to request the indicated conferee to beisolated from the conference.TABLE 1-6/Q.841.7.2.2.6 Contents of ISOLATE REJECTThe contents of ISOLATE REJECT are shown in Table 1-7.ADD Allowed values req.ind resp.confConference identity Integer MandatoryParty identity

37、 Integer MandatoryADD REJET Allowed values req.indCause No more parties allowed, invalid CId MandatoryISOLATE Allowed values req.ind resp.confParty identity Integer MandatoryRecommendation Q.84 (03/93) 15TABLE 1-7/Q.841.7.2.2.7 Contents of REATTACHThe contents of REATTACH are shown in Table 1-8.This

38、 confirmed information flow appears between FE1 and FE2 and is used to request the indicated conferee to bereattached to the conference bridge.TABLE 1-8/Q.841.7.2.2.8 Contents of REATTACH REJECTThe contents of REATTACH REJECT are shown in Table 1-9.TABLE 1-9/Q.841.7.2.2.9 Contents of DROPThe content

39、s of DROP are shown in Table 1-10.This confirmed information flow appears between FE1 and FE2 and is used to request the call to the indicated confereeto be released.TABLE 1-10/Q.841.7.2.2.10 Contents of DROP REJECTThe contents of DROP REJECT are shown in Table 1-11.ISOLATE REJECT Allowed values req

40、.indCause Invalid PId MandatoryREATTACH Allowed values req.ind resp.confParty identity Integer MandatoryREATTACH REJECT Allowed values req.indCause Invalid PId MandatoryDROP Allowed values req.ind resp.confParty identity Integer Mandatory16 Recommendation Q.84 (03/93)TABLE 1-11/Q.841.7.2.2.11 Conten

41、ts of INFORM 6The contents of INFORM 6 are shown in Table 1-12.The unconfirmed information flow appears between FE2 and FE1 and is used to indicate that a party has terminated hisconnection.TABLE 1-12/Q.841.7.2.2.12 Contents of DISCONNECT CONTROLLERThe contents of DISCONNECT CONTROLLER are shown in

42、Table 1-13.This confirmed information flow appears between FE1 and FE2 and is used to request the conference controller to bedisconnected.TABLE 1-13/Q.841.7.2.2.13 Contents of DISCONNECT CONTROLLER REJECTThe contents of DISCONNECT CONTROLLER REJECT are shown in Table 1-14.TABLE 1-14/Q.84DROP REJECT

43、Allowed values req.indCause Invalid PId MandatoryINFORM 6 Allowed values req.indParty identity Integer MandatoryDISCONNECT CONTROLLER Allowed values req.ind resp.confDISCONNECT CONTROLLER REJECT Allowed values req.indCause Floating not allowed MandatoryRecommendation Q.84 (03/93) 171.7.2.2.14 Conten

44、ts of TERMINATE CONFERENCEThe contents of TERMINATE CONFERENCE are shown in Table 1-15.This confirmed information flow appears between FE1 and FE2 and is used to request termination of the CONFsupplementary service.TABLE 1-15/Q.841.7.2.3 Relationship rbThere are no parameters included in INFORM 1 “A

45、DDED TO CONFERENCE”, INFORM 2 “PRIVATECOMMUNICATION”, INFORM 3 “OTHER PARTY IN PRIVATE COMMUNICATION”, INFORM 4 “ISOLATED”,INFORM 5 “REATTACHED”, INFORM 7 “OTHER PARTY ADDED TO CONFERENCE”, INFORM 8 “OTHERPARTY ISOLATED” and INFORM 9 “OTHER PARTY REATTACHED”, INFORM 10 “OTHER PARTYDROPPED” and INFOR

46、M 11 “CONFERENCE FLOATING”.1.8 SDL diagrams for functional entitiesAll SDL diagrams for functional entities are described according to Recommendation Z.100 6.1.8.1 SDL diagrams for FE1T1128960-91/d15CCA_CONFCCA_ADD_SPLITFIGURE 1-15/Q.84Block diagram for FE1FIGURE 1-15/Q.84.D15 = 6,5 CMTERMINATE CONF

47、ERENCE Allowed values req.ind18 Recommendation Q.84 (03/93)CNF8T1128970-91/d160idle3active910912916From FE2916SPLITreq.GeneratesetparametersINFORM 6req. indINFORM 6ind.3activeNOTES1 CNF8 breaks basic call at connector S1/2, see Recommendation Q.71 4.2 Before establishing the new call the user may pl

48、ace another call on hold to obtain a B-channel.FIGURE 1-16/Q.84FE1 process CCA_ADD_SPLITFIGURE 1-16/Q.84.D16 = 11,5 CMRecommendation Q.84 (03/93) 19T1128980-91/d17FIGURE 1-17/Q.84FE1 process CCA_ADD_SPLIT3activeADDreq.914ADDreq. ind(cid)914To FE23activeADDresp. conf(pid)915From FE2ADDconf.9153active

49、ADD REJECTreq. ind(cause)915From FE2ADD REJECTind.9153activeFIGURE 1-17/Q.84.D17 = 17 CM20 Recommendation Q.84 (03/93)T1128990-91/d18CNF9FIGURE 1-18/Q.84 (sheet 1 of 6)FE1 process CCA_CONF3activeCONFreq.911CONFreq. ind911To FE23activeCONFresp. conf(pid, cid)912From FE2CONFconf.9123activeCONF REJECTreq. ind(cause)912From FE2CONF REJECTind.9123active0idleCONFreq.913Generatesetupparameters913NOTE CNF9 breaks basic call at connector S1/2, see Recommendation Q.71 4.FIGURE 1-18/Q.84