B.2 Compatibility With Future Releases
22.1353GPPMulticallRelease 17Service descriptionStage 1TS
It is envisaged that 3GPP standards will evolve in future releleases, for example with the addition of new service requirements. The standards which define the technical implementation should be developed in such a way that it is practical to add the requirements in this section in a backward compatible manner.
Following chapters include requirements that are foreseen for future release.
B.2.1 Multicall configuration
When having one active CS call and one held call on the same bearer. It shall be possible to create a new CS bearer and to move one of the calls to the new bearer, resulting both calls being active within the limits set by the operator/user and within the capability of the terminal. See figure 2: Split of bearer.
When having two calls (multicall) on the separate bearers. It shall be possible to join both calls to one of the two bearers, put the one of the calls to hold and to release unused CS bearer. It shall be possible to select which call to put on hold. See figure 2: Combination of bearers. (Note: there is no clear end-user service requirement for this feature at time being).
NOTE: Due to that only speech calls can be put on hold, so one of the two active Cs calls has to be a speech call.
Figure 2: Illustration for split of bearer and combination of bearers
B.2.2 Several simultaneous speech calls / bearers
A Key requirements for multicall is to allow several simultaneous CS calls with dedicated bearers. The most important usage scenario is to allow several CS data bearers to be bind at application level resulting to higher than 64kbits/s data rates. Another important feature is to allow simultaneous speech and data calls.
It’s been proposed that the multicall feature could be introduced in a phased manner; meaning that in the first phase, i.e. 3GPP release 99 does only support one active speech call at a time. However, Call control should not prohibit a complete set of multiple speech bearer services in future releases and UTRAN shall be designed in a flexible way to support multiple speech bearers. The specific NDUB definition for speech call shall be removed when multiple speech call is supported. At this release , Supplementary Services Call Waiting, Multiparty and Call Hold are used to offer simultaneous speech calls to user.
Ncs may be extended in further releases.
If multiple simultaneous speech calls are supported in the future then the Call Hold service may be used to reconfigure the number of bearers supporting speech calls if required during handover. e.g. in the case of handover to GERAN where only one speech call can be active at a time. This requirement is dependent on the user subscribing to Call Hold.
B.2.3 CCBS
At this release CCBS no enhancements for CCBS is required.
In the future releases the definition of IDLE state of subscriber A and destination B should be modified in away that the IDLE state is reach even if there are active CS calls but the maximum limit of CS calls is not reached.
Annex C (informative):
Change history
|
Date |
Version |
Comment |
|
19 Mar. 1999 |
0.0.1 |
First draft by the editor (Tommi Kokkola / Nokia) |
|
30 Mar. 1999 |
0.1.0 |
Output from S1 Multicall ad hoc |
|
6 Apr. 1999 |
0.1.0 |
Minor modifications by the editor. Proposed version 1.0.0 |
|
19 Apr. 1999 |
1.0.0 |
For information to 3GPP TSG SA#3 |
|
10. Jun. 1999 |
1.1.0 |
Draft from editor for the email meeting. |
|
18. Jun. 1999 |
1.1.1 |
Draft during the email meeting. |
|
24. Jun .1999 |
1.2.0 |
Result of email discussions. For some issues status still unstable. |
|
1. Jul .1999 |
1.2.1 |
Comments from TSGN & TSGS Multimedia and Multicall joint meeting included. (Revisions included from version 1.1.0) |
|
8. Jul. 1999 |
1.3.0 |
Results from S1 Plenary. Drafting continues at S1_Multicall mailing lists. Contributions expected on: |
|
28. Sep. 1999 |
1.4.0 |
Output from S1 Multicall ad hoc, Germany. |
|
1.Oct. 1999 |
1.6.0 |
Proposed version 2.0.0 |
|
10. Oct 1999 |
2.0.0 |
Version 2.0.0 |
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
Work Item |
|
SP-05 |
SP99-433 |
22.135 |
Version 3.0.0 approved |
3.0.0 |
|||||||
|
SP-06 |
SP-99523 |
S1-991020 |
22.135 |
001 |
R99 |
D |
Transfer of Handover chapter to 22.129 |
3.0.0 |
3.1.0 |
||
|
SP-06 |
SP-99523 |
S1-991065 |
22.135 |
002 |
R99 |
D |
Clarification on handling of multiple bearers |
3.0.0 |
3.1.0 |
||
|
SP-06 |
SP-99554 |
S1-99963 |
22.135 |
003 |
R99 |
C |
Registration, Interrogation and Restriction of Packet Domain |
3.0.0 |
3.1.0 |
||
|
SP-07 |
SP-000068 |
S1-000168 |
22.135 |
004 |
R99 |
F |
Clarification of requirement for Multicall |
3.1.0 |
3.2.0 |
||
|
SP-08 |
SP-000205 |
S1-000349 |
22.129 |
012 |
R99 |
F |
Alignment of handover requirements for Multicall |
3.2.0 |
3.3.0 |
||
|
SP-09 |
SP-000375 |
S1-000585 |
22.135 |
006 |
R99 |
F |
Interaction with MSP |
3.3.0 |
3.4.0 |
||
|
SP-09 |
SP-000406 |
S1-000656 |
22.135 |
007 |
R99 |
F |
Removal of the Requirement on Network to Tear Down Calls to Accept EC in Multicall |
3.3.0 |
3.4.0 |
||
|
SP-09 |
SP-000406 |
S1-000657 |
22.135 |
008 |
R99 |
F |
Addition of Ncs_MT limitation to number of MPTY members |
3.3.0 |
3.4.0 |
||
|
SP-11 |
SP-010065 |
S1-010258 |
22.135 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.4.0 |
4.0.0 |
||||
|
SP-15 |
SP-020045 |
S1-020457 |
22.135 |
009 |
– |
Rel-4 |
F |
Editorial CR to correct terms and references |
4.0.0 |
4.1.0 |
CORRECT |
|
SP-16 |
SP-020267 |
S1-021043 |
22.135 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.1.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.135 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-36 |
22.135 |
Rel-7 |
Updated from Rel-6 to Rel-7 |
6.0.0 |
7.0.0 |
||||||
|
SP-42 |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|