13 Handover
23.1353GPPMulticall supplementary serviceRelease 17Stage 2TS
In the case that the network supports Multicall, it shall be possible to handover multiple bearers (See TS 23.009).
Annex A (informative):
Examples
The following table shows some examples:
1 Mobile Originating Call (MO call).
As an example: Nbr=2.
Current Status |
Additional MO call |
||||
---|---|---|---|---|---|
No |
Status |
Number of bearers |
Number of calls |
Speech |
Data |
1 |
None |
0 |
0 |
Acceptable |
Acceptable |
2 |
1 Speech call(active) |
1 |
1 |
Rejected |
Acceptable |
3 |
1 Speech call(on hold) |
1 |
1 |
Acceptable (with same SI) Rejected (with another SI) |
Acceptable |
4 |
1 Data call(active) |
1 |
1 |
Acceptable |
Acceptable |
5 |
1 Speech call(on hold) 1 Speech call(active) |
1 |
2 |
Rejected |
Acceptable |
6 |
1 Speech call(on hold) 1 Data call(active) |
1 |
2 |
Rejected |
Acceptable |
7 |
Multiparty (2-5 remote parties: active) |
1 |
2 – 5 |
Rejected |
Acceptable |
8 |
Multiparty (2-5 remote parties: on hold) |
1 |
2 – 5 |
Acceptable (with same SI) Rejected (with another SI) |
Acceptable |
9 |
1 Speech call(active) 1 Data call(active) |
2 |
2 |
Rejected |
Rejected |
10 |
1 Speech call(on hold) 1 Data call(active) |
2 |
2 |
Acceptable (with same SI as speech call) Rejected (with another SI) |
Acceptable (with same SI as speech call) Rejected (with another SI) |
11 |
1 Speech call(on hold) 1 Speech call(active) 1 Data call(active) |
2 |
3 |
Rejected |
Rejected |
12 |
2 Data call(active) |
2 |
2 |
Rejected |
Rejected |
13 |
1 Speech call(on hold) 2 Data call(active) |
2 |
3 |
Rejected |
Rejected |
14 |
Multiparty (2-5 remote parties: active) 1 Data call(active) |
2 |
3 – 6 |
Rejected |
Rejected |
15 |
Multiparty (2-5 remote parties: on hold) 1 Data call(active) |
2 |
3 – 6 |
Acceptable (with same SI as speech call) Rejected (with another SI) |
Acceptable (with same SI as speech call) Rejected (with another SI) |
2 Mobile Terminated Call (MT call).
As an example: Nbr=2 (CW is not active).
Current Status |
Additional MT call |
||||
---|---|---|---|---|---|
No |
Status |
Number of bearers |
Number of calls |
Speech |
Data |
1 |
None |
0 |
0 |
Offered |
Offered |
2 |
1 Speech call(active) |
1 |
1 |
Busy |
Offered |
3 |
1 Speech call(on hold) |
1 |
1 |
Busy |
Offered |
4 |
1 Data call(active) |
1 |
1 |
Offered |
Offered |
5 |
1 Speech call(on hold) 1 Speech call(active) |
1 |
2 |
Busy |
Offered |
6 |
1 Speech call(on hold) 1 Data call(active) |
1 |
2 |
Busy |
Offered |
7 |
Multiparty (2-5 remote parties: active) |
1 |
2 – 5 |
Busy |
Offered |
8 |
Multiparty (2-5 remote parties: on hold) |
1 |
2 – 5 |
Busy |
Offered |
9 |
1 Speech call(active) 1 Data call(active) |
2 |
2 |
Busy |
Busy |
10 |
1 Speech call(on hold) 1 Data call(active) |
2 |
2 |
Busy |
Busy |
11 |
1 Speech call(on hold) 1 Speech call(active) 1 Data call(active) |
2 |
3 |
Busy |
Busy |
12 |
2 Data call(active) |
2 |
2 |
Busy |
Busy |
13 |
1 Speech call(on hold) 2 Data call(active) |
2 |
3 |
Busy |
Busy |
14 |
Multiparty (2-5 remote parties: active) 1 Data call(active) |
2 |
3 – 6 |
Busy |
Busy |
15 |
Multiparty (2-5 remote parties: on hold) 1 Data call(active) |
2 |
3 – 6 |
Busy |
Busy |
3 Call Waiting (CW).
As an example: Nbr=2 (CW is provisioned).
Current Status |
Additional MT call |
||||
---|---|---|---|---|---|
No |
Status |
CW status for speech |
CW status for data |
Speech |
Data |
1 |
None |
– |
– |
– |
– |
2 |
1 Speech call(active) |
active |
– |
CW offered |
MT offered |
Not active |
– |
busy |
MT offered |
||
3 |
1 Speech call(on hold) |
active |
– |
CW offered |
MT offered |
Not active |
busy |
MT offered |
|||
4 |
1 Data call(active) |
– |
active |
MT offered |
MT offered |
Not active |
MT offered |
MT offered |
|||
5 |
1 Speech call(on hold) via bearer A 1 Speech call(active) via bearer A |
active |
active |
CW offered |
MT offered |
active |
Not active |
CW offered |
MT offered |
||
Not active |
active |
busy |
MT offered |
||
Not active |
Not active |
busy |
MT offered |
||
6 |
1 Speech call(on hold) via bearer A 1 Data call(active) via bearer A |
active |
active |
CW offered |
MT offered |
active |
Not active |
busy |
MT offered |
||
Not active |
active |
CW offered |
MT offered |
||
Not active |
Not active |
busy |
MT offered |
||
7 |
Multiparty via bearer A (2-5 remote parties: active) |
active |
– |
CW offered |
MT offered |
Not active |
– |
Busy |
MT offered |
||
8 |
Multiparty via bearer A (2-5 remote parties: on hold) |
active |
– |
CW offered |
MT offered |
Not active |
– |
busy |
MT offered |
||
9 |
1 Speech call(active) via bearer A 1 Data call(active) via bearer B |
active |
active |
CW offered |
CW offered |
active |
Not active |
CW offered |
CW offered |
||
Not active |
active |
busy |
CW offered |
||
Not active |
Not active |
busy |
busy |
||
10 |
1 Speech call(on hold) via bearer A 1 Data call(active) via bearer B |
active |
active |
CW offered |
CW offered |
active |
Not active |
CW offered |
CW offered |
||
Not active |
active |
busy |
CW offered |
||
Not active |
Not active |
busy |
busy |
||
11 |
1 Speech call(on hold) via bearer A 1 Speech call(active) via bearer A 1 Data call(active) via bearer B |
active |
active |
CW offered |
CW offered |
active |
Not active |
CW offered |
CW offered |
||
Not active |
active |
busy |
CW offered |
||
Not active |
Not active |
busy |
busy |
||
12 |
2 Data call(active) |
– |
active |
CW offered |
CW offered |
– |
Not active |
busy |
busy |
||
13 |
1 Speech call(on hold) via bearer A 2 Data call(active) via bearer A and B |
– |
active |
CW offered |
CW offered |
– |
Not active |
Busy |
Busy |
||
14 |
Multiparty via bearer A (2-5 remote parties: active) 1 Data call(active) via bearer B |
active |
active |
CW offered |
CW offered |
active |
Not active |
CW offered |
CW offered |
||
Not active |
active |
busy |
CW offered |
||
Not active |
Not active |
busy |
busy |
||
15 |
Multiparty via bearer A (2-5 remote parties: on hold) 1 Data call(active) via bearer B |
active |
active |
CW offered |
CW offered |
active |
Not active |
CW offered |
CW offered |
||
Not active |
active |
busy |
CW offered |
||
Not active |
Not active |
busy |
busy |
Annex B (informative):
Change history
Change history |
|||||||
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
CN#07 |
Approved at TSGN#07 |
3.0.0 |
|||||
CN#08 |
001 |
1 |
Clean-up and corrections for Multicall Stage 2 |
3.1.0 |
|||
CN#09 |
002 |
4 |
Requirement on Network to Tear Down Calls to Accept EC in Multicall |
3.2.0 |
|||
CN#09 |
004 |
2 |
Correction to MT_Multicall SDL |
3.2.0 |
|||
CN#09 |
003 |
2 |
Inclusion of call hold in basic call handling |
4.0.0 |
|||
CN#16 |
Release 5 after CN#16 |
5.0.0 |
|||||
CN#26 |
Release 6 after CN#26 |
6.0.0 |
|||||
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
CT#46 |
Update to Rel-9 version (MCC) |
9.0.0 |
|||||
2011-03 |
Update to Rel-10 version (MCC) |
10.0.0 |
|||||
2012-09 |
Update to Rel-11 version (MCC) |
11.0.0 |
|||||
2014-09 |
Update to Rel-12 version (MCC) |
12.0.0 |
|||||
2015-12 |
Update to Rel-13 version (MCC) |
13.0.0 |
|||||
2017-03 |
Update to Rel-14 version (MCC) |
14.0.0 |
|||||
2018-06 |
Update to Rel-15 version (MCC) |
15.0.0 |
|||||
2020-07 |
Update to Rel-16 version (MCC) |
16.0.0 |
|||||
2022-03 |
CT#95 |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |