tech-invite   World Map
3GPP     Specs     Glossaries     UICC       IETF     RFCs     Groups     SIP     ABNFs       T+       Search     Home
Top        in Index        Prev        Next

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

|   ToC   |   3GPP‑Page   |   ETSI‑search   |   Help   |

(P) V14.0.0    2017/03    21 p.
(P) V13.0.0    2015/12    21 p.
(P) V12.0.0    2014/10    21 p.
(P) V11.0.0    2012/09    21 p.
(P) V10.0.0    2011/04    21 p.
(P) V9.0.0    2009/12    21 p.
(P) V8.0.0    2009/01    21 p.
(P) V7.0.0    2007/06    21 p.
(P) V6.0.0    2004/12    21 p.
(P) V5.0.0    2002/07    21 p.
(P) V4.2.0    2002/12    21 p.
(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 Scope    2 References    3 Definitions, symbols and abbreviations    3.1 Definitions    4 Description    4.1 Description of multicall    4.2 Applicability to telecommunication services    5 Functional requirements    5.1 Provision    5.2 Withdrawal    5.3 Registration    5.4 Erasure    5.5 Activation    5.6 Deactivation    5.7 Invocation    5.8 Interrogation    5.9 Call related procedures    5.10 Charging requirements    6 Exceptional procedures or unsuccessful outcome    6.1 Exceptional operation or unsuccessful outcome    6.2 Registration    6.3 Erasure    6.4 Activation    6.5 Deactivation    6.6 Invocation    6.7 Interrogation    6.8 Roaming in non-supporting networks    7 Interaction with other services    7.1 Line Identification    7.2 Call Forwarding    7.3 Call Completion    7.4 Multi Party (MPTY)    7.5 Closed User Group (CUG)    7.6 Advice of Charge (AoC)    7.7 Call Barring    7.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 services    8.1 CAMEL    8.2 IST    8.3 ODB    8.4 Emergency Calls    A [N] Busy definition    B Cross Phase Compatibility    B.1 Compatibility With Existing Standards    B.2 Compatibility With Future Releases    C Change history   

 

1   Scope   PDF-p. 6
2   References
3   Definitions, symbols and abbreviations
4   Description   PDF-p. 7
5   Functional requirements
6   Exceptional procedures or unsuccessful outcome      Up
7   Interaction with other services
8   Interaction with other network features and services
A  (Normative)   Busy definition   PDF-p. 15
B   Cross Phase Compatibility   PDF-p. 16
C   Change history   PDF-p. 18

Up        Top