Tech-invite3GPPspecsGlossariesIETFRFCsGroupsSIPABNFsWorld Map
Top   in Index   Prev   Next

TS 22.135 (SA1)
Multicall – Service description – Stage 1

ToC   3GPP‑Page   ETSI‑search   Help    
V15.0.0 (PDF)2018/06  20 p.
V14.0.0  2017/03  21 p.
V13.0.0  2015/12  21 p.
V12.0.0  2014/10  21 p.
V11.0.0  2012/09  21 p.
V10.0.0  2011/04  21 p.
V9.0.0  2009/12  21 p.
V8.0.0  2009/01  21 p.
V7.0.0  2007/06  21 p.
V6.0.0  2004/12  21 p.
V5.0.0  2002/07  21 p.
V4.2.0  2002/12  21 p.
V3.4.0  2000/10  19 p.


Rapporteur:  Miss Miettinen, Natalia
See also:  Multicall-related TS/TR

The Multicall supplementary service enables a mobile subscriber to have several simultaneous CS calls, each call using its own dedicated bearer. Only one CS bearer can used for speech at a given time.

A speech call is one of TS11 (Telephony), TS12 (Emergency Calls), and TS61 (Alternate speech/fax). If the bearer capability information is not available, e.g. the call is originated/transited by a PSTN, the basic service cannot be deduced and the network shall, for multicall purposes, handle the call as telephony.

A held call shall be regarded as using the bearer used while the call was active.

Note:  The 3GPP protocol architecture allows several parallel CS calls, the limitation being that there is only one traffic channel in GERAN, which the different CS calls share. This is facilitated by e.g. the Call Waiting, Call Hold, Call Transfer and Multiparty Supplementary Services. Call configurations related to supplementary services are not considered as Multicall. See clause 7 for interaction.

It shall be possible for each CS call to use a dedicated bearer of independent traffic and performance characteristics. It shall be possible to release each active CS call independently of any other CS call.


 

Here   Top

 

1 Scope2 References3 Definitions, symbols and abbreviations3.1 Definitions4 Description4.1 Description of multicall4.2 Applicability to telecommunication services5 Functional requirements5.1 Provision5.2 Withdrawal5.3 Registration5.4 Erasure5.5 Activation5.6 Deactivation5.7 Invocation5.8 Interrogation5.9 Call related procedures5.10 Charging requirements6 Exceptional procedures or unsuccessful outcome6.1 Exceptional operation or unsuccessful outcome6.2 Registration6.3 Erasure6.4 Activation6.5 Deactivation6.6 Invocation6.7 Interrogation6.8 Roaming in non-supporting networks7 Interaction with other services7.1 Line Identification7.2 Call Forwarding7.3 Call Completion7.4 Multi Party (MPTY)7.5 Closed User Group (CUG)7.6 Advice of Charge (AoC)7.7 Call Barring7.8 Explicit Call Transfer (ECT)7.9 Completion of Call to Busy Subscriber (CCBS)7.10 Multiple Subscriber Profile (MSP)7.11 Calling Name Presentation (CNAP)7.12 User-to-User Signalling (UUS)7.13 enhanced Multi-Level Precedence and Pre-emption service (eMLPP)7.14 Call Deflection (CD)8 Interaction with other network features and services8.1 CAMEL8.2 IST8.3 ODB8.4 Emergency CallsA [N] Busy definitionB Cross Phase CompatibilityB.1 Compatibility With Existing StandardsB.2 Compatibility With Future ReleasesC Change history

 

1  ScopePDF-p. 6
2  References
3  Definitions, symbols and abbreviations
4  DescriptionPDF-p. 7
5  Functional requirements
6  Exceptional procedures or unsuccessful outcomeUp
7  Interaction with other services
8  Interaction with other network features and services
A (Normative)  Busy definitionPDF-p. 15
B  Cross Phase CompatibilityPDF-p. 16
C  Change historyPDF-p. 18

Up   Top