SIST ETS 300 184:1999

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.VWRULWHYIRUPDFLMVNLSUHWRNLIntegrated Services Digital Network (ISDN); Conference call, add-on (CONF) supplementary service; Functional capabilities and information flows33.080Digitalno omrežje z integriranimi storitvami (ISDN)Integrated Services Digital Network (ISDN)ICS:Ta slovenski standard je istoveten z:ETS 300 184 Edition 1SIST ETS 300 184:1999en01-julij-1999SIST ETS 300 184:1999SLOVENSKI
STANDARD



SIST ETS 300 184:1999



EUROPEANETS 300 184TELECOMMUNICATIONApril 1993STANDARDSource: ETSI TC-SPSReference: T/S 22-12ICS:33.080Key words:ISDN, supplementary service.Integrated Services Digital Network (ISDN);Conference call, add-on (CONF) supplementary serviceFunctional capabilities and information flowsETSIEuropean Telecommunications Standards InstituteETSI SecretariatPostal address: F-06921 Sophia Antipolis CEDEX - FRANCEOffice address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCEX.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.frTel.: +33 92 94 42 00 - Fax: +33 93 65 47 16Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and theforegoing restriction extend to reproduction in all media.© European Telecommunications Standards Institute 1993. All rights reserved.SIST ETS 300 184:1999New presentation - see History box



Page 2ETS 300 184: April 1993Whilst every care has been taken in the preparation and publication of this document, errors in content,typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to"ETSI Editing and Committee Support Dept." at the address shown on the title page.SIST ETS 300 184:1999



Page 3ETS 300 184: April 1993ContentsForeword.51Scope.72Normative references.73Definitions.84Symbols and abbreviations.85Description.96Derivation of a functional model.96.1Functional model description.96.2Description of functional entities.96.3Relation with a basic service.107Information flows.107.1Information flow diagrams.107.2Definition of individual information flows.157.2.1Modification to relationship r1 associated with ra.157.2.1.1Contents of SETUP.157.2.2Relationship ra.157.2.2.1Contents of CONF.157.2.2.2Contents of CONF REJECT.167.2.2.3Contents of ADD.167.2.2.4Contents of ADD REJECT.167.2.2.5Contents of ISOLATE.167.2.2.6Contents of ISOLATE REJECT.167.2.2.7Contents of REATTACH.177.2.2.8Contents of REATTACH REJECT.177.2.2.9Contents of DROP.177.2.2.10Contents of DROP REJECT.177.2.2.11Contents of INFORM6.177.2.3Relationship rb.188SDL diagrams for functional entities.188.1SDL diagrams for FE1.198.2SDL diagrams for FE2.268.3SDL diagrams for FE3.389Functional Entity Actions (FEAs).399.1FEAs of FE1.399.2FEAs of FE2.399.3FEAs of FE3.4110Allocation of functional entities to physical locations.41History.42SIST ETS 300 184:1999



Page 4ETS 300 184: April 1993Blank pageSIST ETS 300 184:1999



Page 5ETS 300 184: April 1993ForewordThis European Telecommunication Standard (ETS) has been produced by the Signalling Protocols &Switching (SPS) Technical Committee of the European Telecommunications Standards Institute (ETSI).In accordance with CCITT Recommendation I.130 [1], the following three level structure is used todescribe the supplementary telecommunications services as provided by European publictelecommunications operators under the pan-European Integrated Services Digital Network (ISDN):-Stage 1: is an overall service description, from the user's standpoint;-Stage 2: identifies the functional capabilities and information flows needed to support the servicedescribed in stage 1; and-Stage 3: defines the signalling system protocols and switching functions needed to implement theservice described in stage 1.This ETS details the stage 3 aspects (signalling system protocols and switching functions) to support theConference call, add-on (CONF) supplementary service. The stage 1 and stage 3 aspects are detailed inETS 300 183 (1992) and ETS 300 185 (1993), respectively.SIST ETS 300 184:1999



Page 6ETS 300 184: April 1993Blank pageSIST ETS 300 184:1999



Page 7ETS 300 184: April 19931ScopeThis standard defines stage two of the Conference call, add-on (CONF) supplementary service for thepan-European Integrated Services Digital Network (ISDN) as provided by European publictelecommunications operators. Stage two identifies the functional capabilities and the information flowsneeded to support the service as described in stage one. The stage two description also identifies useroperations not directly associated with a call (see CCITT Recommendation I.130 [1]).This standard is specified according to the methodology specified in CCITT Recommendation Q.65 [2].This standard does not formally describe the relationship between this supplementary service and theBasic Call but where possible this information is included for guidance.In addition this standard does not specify the requirements where the service is provided to the user via aprivate ISDN. This standard does not specify the requirements for the allocation of defined functionalentities within a private ISDN; it does, however, specify which functional entities may be allocated to aprivate ISDN.This standard does not specify the additional requirements where the service is provided to the user via atelecommunications network that is not an ISDN.The CONF supplementary service provides a user with the ability to have a multi-connection call, i.e. asimultaneous communication between more than two parties.The CONF supplementary service is defined for all telecommunication services carrying speech.This standard is applicable to the stage three standards for the ISDN Conference call, add-on
(CONF)supplementary service. The term stage three is also defined in CCITT Recommendation I.130 [1]. Wherethe text indicates the status of a requirement, i.e. as strict command or prohibition, as authorisation leavingfreedom, as a capability or possibility, this shall be reflected in the text of the relevant stage threestandards.Furthermore, conformance to this standard is met by conforming to the stage three standards with the fieldof application appropriate to the equipment being implemented. Therefore, no method of testing is providedfor this standard.2Normative referencesThis standard incorporates by dated or undated reference, provisions from other publications. Thesenormative references are cited at the appropriate places in the text and the publications are listedhereafter. For dated references subsequent amendments to, or revisions of any of these publications applyto this standard only when incorporated in it by amendment or revision. For undated references the latestedition of the publication referred to applies.[1]CCITT Recommendation I.130 (1988): "Method for the characterisation oftelecommunication services supported by an ISDN and network capabilities of anISDN".[2]CCITT Recommendation Q.65 (1988): "Stage 2 of the method for thecharacterisation of services supported by an ISDN".[3]CCITT Recommendation I.112 (1988): "Vocabulary of terms for ISDNs".[4]CCITT Recommendation Q.71 (1988): "ISDN 64 kbit/s circuit mode switchedbearer services".[5]ETS 300 183 (1992): "Integrated Services Digital Network (ISDN); Conferencecall, add-on (CONF) supplementary service; Service description".SIST ETS 300 184:1999



Page 8ETS 300 184: April 1993[6]CCITT Recommendation Z.100 (1988): "Functional Specification and DescriptionLanguage (SDL)".[7]CCITT Recommendation I.210 (1988): "Principles of telecommunication servicessupported by an ISDN and the means used to describe them".3DefinitionsFor the purposes of this standard, the following definitions apply:Backward connection: that part of a normal call that connects a served user's CCA with a CC locatedwith the Service Providing Entity (SPE).Conferee: a conference participant not being the conference controller.Conference controller: the served user controlling the conference.Forward connection: the connection between a Call Control (CC) located with the SPE and a conferee'sCall Control Agent (CCA).Integrated Services Digital Network (ISDN): see CCITT Recommendation I.112 [3], § 2.3, definition308.Multi Connection Call Control (MCCC): a call control entity with the ability to control one connectiondirectly and several others via One Connection Call Control (OCCC) entities.One Connection Call Control (OCCC): a call control entity with the ability to control a single connectionfor a MCCC entity.Party: either a conferee or the conference controller.Service; telecommunications service: see CCITT Recommendation I.112 [3], § 2.2, definition 201.Supplementary service: see CCITT Recommendation I.210 [7], § 2.4.4Symbols and abbreviationsCCCall ControlCCACall Control AgentCONFConference call, add-onFEAFunctional Entity ActionISDNIntegrated Services Digital NetworkLELocal ExchangeMCCCMulti Connection Call ControlOCCCOne Connection Call ControlPTNXPrivate Telecommunications Network eXchangeSDLSpecification and Description LanguageSPEService Providing EntityTETerminal EquipmentSIST ETS 300 184:1999



Page 9ETS 300 184: April 19935DescriptionThe CONF supplementary service can be invoked from the idle state. As a network option, the CONFsupplementary service can be invoked from an existing active call.When the CONF supplementary service is invoked, conference resources (e.g. a "bridge") are allocated tothe served user. In the case of invocation from an active call, this shall be automatically connected by thenetwork to the conference resources.Once a conference is active, parties may be added, dropped, isolated (i.e. prevented from communicatingwith the conference), reattached or split (i.e. removed from the conference but remain connected to theconference controller).6Derivation of a functional model6.1Functional model descriptionThe model has been based on the concept that the served user maintains by means of FE1 a singlerelation to the centre of the conference FE2. FE2 has the ability to have simultaneous relations with all theconferees.This concept has been depicted in figure 1.ÚÄÄÄÄÄ¿
ÚÄÄÄÄÄ¿
rb
ÚÄÄÄÄÄ¿³
³ ra ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³³ FE1 ÃÄÄÄÄ´ FE2 ÃÄÄÄÄÄÄÄÄÄ¿
³FE3x ³ÀÄÄÄÄÄÙ
ÀÄÄÄÄÄÙ
³
ÀÄÄÄÄÄÙ
³
³
³
ÚÄÄÄÄÄ¿
ÀÄÄÄÄÄÄÄÄ´
³
rb
³FE3n ³
ÀÄÄÄÄÄÙFigure 16.2Description of functional entitiesFE1:Originating service agentFE2:Service providing entityFE3:Destination service agentSIST ETS 300 184:1999



Page 10ETS 300 184: April 19936.3Relation with a basic serviceThe relationship with a basic service is shown in figure 2. The model for basic call handling is defined inCCITT Recommendation Q.71 [4].ÚÄÄÄÄÄ¿
ÚÄÄÄÄÄ¿
rb
ÚÄÄÄÄÄ¿³
³ ra ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³³ FE1 ÃÄÄÄÄ´ FE2 ÃÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ FE3x³ÃÄÄÄÄÄ´ r1 ÃÄÄÄÄÄ´ r2 ÚÄÄÄÄÄ¿
³
r2
ÚÄÄÄÄÄ¿ r3 ÃÄÄÄÄÄ´³ CCA ÃÄÄÄÄ´ CC
ÃÄÄÄÄ´ CC
ÃÄÄÅÄÄÄÄÄÄÄ´ CC
ÃÄÄÄÄ´ CCA ³ÀÄÄÄÄÄÙ
ÃÄÄÄÄÄ´ r2 ÀÄÄÄÄÄÙ
³
ÀÄÄÄÄÄÙ
ÀÄÄÄÄÄÙ
³ CC
ÃÄÄ¿
³
rb
ÚÄÄÄÄÄ¿
ÀÄÄÄÄÄÙ
³
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³
³
³ FE3n³
³ ÚÄÄÄÄÄ¿
r2
ÚÄÄÄÄÄ¿ r3 ÃÄÄÄÄÄ´
ÀÄ´ CC
ÃÄÄÄÄÄÄÄÄÄÄ´ CC
ÃÄÄÄÄ´ CCA ³
ÀÄÄÄÄÄÙ
ÀÄÄÄÄÄÙ
ÀÄÄÄÄÄÙFigure 27Information flows7.1Information flow diagramsThe following information flow diagrams are identified:-Figure 3:Requesting a new conference call;-Figure 4:Change normal call into conference call;-Figure 5:Adding a new conferee;-Figure 6:Isolating a conferee;-Figure 7:Reattaching a conferee;-Figure 8:Dropping a conferee from the conference;-Figure 9:Splitting a conferee from the conference;-Figure 10:Call clearing by conferee;-Figure 11:Ending the conference.NOTE:FE3x is the functional entity which belongs to that party which is explicitly identified bythe conference controller (e.g. DROP party-X). FE3n are the functional entities whichbelong to the parties not identified by the conference controller (e.g. all parties exceptparty-X).SIST ETS 300 184:1999



Page 11ETS 300 184: April 1993
ÚÄÄÄÄÄ¿
ra
ÚÄÄÄÄÄ¿
rb
ÚÄÄÄÄÄ¿
³ FE1 Ã Ä Ä Ä Ä Ä Ä Ä´ FE2 Ã Ä Ä Ä Ä Ä Ä Ä´ FE3x³
ÀÂÄÄÄÂÙ
ÀÂÄÄÄÂÙ
ÀÂÄÄÄÂÙ
³
³
³
³
³
³CONF
³
³
³
³
³
³ÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³req.
³913³211 SETUP
221³
³
³
³
³
³>>>>|----->|>>>>ÃÄÄÄ´
³
³
³
³
req.ind
³927³
³
³
³
³
³922³
³
³
³
³
³924³
³
³
³
³
³925³
³
³
³
³
³905³
³
³
³
³
SETUP
224ÃÄÄÄ´
³
³
³
³<<<<|<-----|<<<<³
³
³
³
³
³
resp.conf
³
³
³
³CONF
³912³
³
³
³
³<ÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³conf.
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 3: Requesting a new conference call from idle call state
ÚÄ - - - - - - - - rb - - - - - - - - -
Ä¿
ÚÄÄÄÄÄ¿
ra
ÚÄÄÁÄÄ¿
rb
ÚÄÄÄÄÄ¿
ÚÄÄÁÄÄ¿
³ FE1 Ã Ä Ä Ä Ä Ä Ä Ä´ FE2 Ã Ä Ä Ä Ä Ä Ä Ä´ FE3x³
³ FE3n³
ÀÂÄÄÄÂÙ
ÀÂÄÄÄÂÙ
ÀÂÄÄÄÂÙ
ÀÂÄÄÄÂÙ
³
³
³
³
³
³
³
³CONF
³
³
³
³
³
³
³
³ÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³req.
³911³ CONF
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³ req.ind
³921³
³
³
³
³
³
³
³922³
³
³
³
³
³
³
³923³
³
³
³
³
³
³
³924³
³
³
³
³
³
³
³92J³
³
³
³
³
³
³
³925³
³
³
³
³
³
³
³92C³ INFORM1
³
³
³
³
³
³
ÃÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ>ÃÄÄÄ´
³
³
³
³
³
³ req.ind
³931³ INFORM1
³
³
³
³
³90A³
ÃÄÄÄÅÄÄÄÄÄÄÄÄ>
³
³
³
³ CONF
³926³
³
³ ind.
³
³
ÃÄÄÄ´<ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³CONF
³912³ resp.conf
³
³
³
³
³
³<ÄÄÄÄÄÄÄÅÄÄÄ´
³
³
³
³
³
³conf.
³
³
³
³
³
³
³
³
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙ
ÀÄÄÄÙFigure 4: Change normal call into conference callSIST ETS 300 184:1999



Page 12ETS 300 184: April 1993
ÚÄ - - - - - - - - rb - - - - - - - - -
Ä¿
ÚÄÄÄÄÄ¿
ra
ÚÄÄÁÄÄ¿
rb
ÚÄÄÄÄÄ¿
ÚÄÄÁÄÄ¿
³ FE1 Ã Ä Ä Ä Ä Ä Ä Ä´ FE2 Ã Ä Ä Ä Ä Ä Ä Ä´ FE3x³
³ FE3n³
ÀÂÄÄÄÂÙ
ÀÂÄÄ
...