2 Call hold
22.0833GPPCall Waiting (CW) and Call Holding (HOLD)Stage 1Supplementary ServicesTS
2.1 Definition
The call hold service allows a served mobile subscriber, who is provisioned with this Supplementary Service, to interrupt communication on an existing active call and then subsequently, if desired, re-establish communication. The traffic channel remains assigned to the mobile subscriber after the communication is interrupted to allow the origination or possible termination of other calls.
2.2 Description
2.2.1 Description
When the call hold service is invoked, communication is interrupted on the traffic channel and the traffic channel is released from the existing call. The traffic channel is reserved for the served mobile subscriber invoking the call hold service. The served mobile subscriber can only have one call on hold at a time.
One traffic channel should be reserved for the served mobile subscriber as long as the subscriber has one call on hold and is currently not connected to any other call, i.e. the network should not reserve more than one traffic channel for a mobile station.
If the served mobile subscriber has a call on hold and is not connected to an active call, she can:
1) Retrieve the held call.
2) Set up another call.
3) Disconnect the held call.
If the served mobile subscriber has a call on hold and is not connected to an active call she can not receive a call, except when using the Call Waiting Supplementary Service. For additional information, see subclause 2.6.83.1 (Interaction with Call Waiting Supplementary Service).
If the served mobile subscriber is connected to an active call and has another call on hold, she can:
1) Alternate from one call to the other.
2) Disconnect the active call.
3) Disconnect the held call.
4) Disconnect both calls.
If the served mobile subscriber is connected to an active call and has another call on hold, she can not receive a call. For additional information, see subclause 2.6.83.1 (Interaction with Call Waiting Supplementary Service).
2.2.2 Applicability to telecommunication services
The applicability of this Supplementary Service is defined in TS 22.004 [2].
NOTE: If the served mobile subscriber has a call on hold she may set up another call using a different telecommunications service.
2.3 Normal procedures with successful outcome
2.3.1 Provision
This Supplementary Service is provisioned for all basic services subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BS.
2.3.2 Withdrawal
The service will be withdrawn at the subscriber’s request or for administrative reasons.
2.3.5 Activation
The Supplementary Service will be activated by the service provider as a result of provision.
2.3.6 Deactivation
The Supplementary Service will be deactivated by the service provider as a result of withdrawal.
2.3.7 Invocation
Call hold will be invoked by the served mobile subscriber by use of a control procedure as described in TS 22.030 [3].
2.3.8 Normal operation with successful outcome
Hold request
The served mobile subscriber indicates to the network that communication on the interface is to be interrupted. A call may be placed on hold:
– on the served calling subscriber’s interface by her at any time after the call has been answered and before call clearing has begun.
– on the served called subscriber’s interface by her at any time after the call has been answered and before call clearing has begun.
The communication on the connection is then interrupted An acknowledgement shall be given to the served mobile subscriber, and the traffic channel is now available for other uses. A notification shall be sent towards the held party indicating that the call has been placed on hold.
Disconnect
If at any time a call is in the held state, either party may disconnect from that call.
Unidirectionality
Assume that subscriber A and B are connected to a call and both have subscribed to the call hold services. The call hold service is unidirectional, so it is possible for:
1) only party A to have party B on hold;
For party A the call is on hold, for the held party B the call is active.
2) only party B to have party A on hold;
For party B the call is on hold, for the held party A the call is active; or
3) each party to have the other on hold.
For party A and party B the call is on hold.
Handling of call hold service within a call
The served mobile subscriber may control the call hold service by use of the control procedures as described in TS 22.030 [3].
If the served mobile subscriber has a call on hold and is not connected to an active call, she can:
1) Retrieve the held call.
A notification shall be send towards the previously held party that the call has been retrieved.
2) Set up another call.
Results in the served mobile subscriber being engaged in that new call and still holding the other call.
3) Disconnect the held call (as for basic call).
If the served mobile subscriber is connected to an active call and has another call on hold, she can:
1) Alternate from one call to the other.
Results in the previously active call being held and the previously held call becoming active. Privacy is provided between the two calls. A notification shall be sent towards the previously held party that the call has been retrieved and another notification shall be sent towards the party being put on hold.
2) Disconnect the active call.
Results in the traffic channel being available for the served mobile subscriber and the other call being still on hold. The served mobile subscriber shall be notified that she has a call on hold. The disconnected party shall be notified as for a basic call.
NOTE: The notification about the held call towards the served mobile subscriber is given by the MS, not by the network.
3) Disconnect the held call.
The disconnected party shall be notified as for a basic call.
4) Disconnect both calls (as for basic call).
If the served mobile subscriber is connected to an active call and has another call on hold, and the active call is disconnected by the other party; then the served mobile subscriber shall be notified that she has a call on hold.
NOTE: The notification about the held call towards the served mobile subscriber is given by the MS, not by the network.
2.4 Exceptional procedures or unsuccessful outcome
2.4.1 Exceptional operation or unsuccessful outcome
If the network cannot retrieve a previously held call, the mobile subscriber will be informed of the reason of the failure. (For example, the call may be in the process of being cleared). The call state is not affected.
If the network cannot alternate between two calls, the mobile subscriber will be informed of the reason for the failure. The call states are not affected.
2.4.6 Invocation
Hold
If a mobile subscriber tries to invoke the hold service while not subscribed to the service or for some other reason, the service provider cannot provide the hold service, an indication will be provided to the mobile subscriber with the reason of failure. The call state is not affected.
2.5 Alternate procedures
None identified.
2.6 Interactions with other Supplementary Services
2.6.83.1 Call waiting
See subclause 1.6.83.2.
2.6.84.2 MultiParty
See TS 22.084 [5]
2.7 Interactions with other services
2.7.1 Multicall
See TS 22.135 [6].
2.8 Interworking considerations
The operation of this Supplementary Service is not affected by the nature of the far end of the connection.
NOTE: In some networks the indication to the distant user about the held or retrieve state of the call may not be supported.
Annex A (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
WI |
|
Jun 1999 |
GSM 02.83 |
Transferred to 3GPP SA1 |
7.0.0 |
||||||||
|
SA#04 |
22.083 |
R99 |
Transferred to 3GPP SA1 |
3.0.0 |
|||||||
|
SP-05 |
SP-99479 |
S1-99630 |
22.083 |
001 |
R99 |
D |
Editorial changes for alignment |
3.0.0 |
3.0.1 |
Editorial changes |
|
|
SP-05 |
SP-99449 |
S1-99854 |
22.083 |
002 |
R99 |
B |
Multicall |
3.0.0 |
3.1.0 |
Multicall |
|
|
SP-11 |
SP-010065 |
S1-010258 |
22.083 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.1.0 |
4.0.0 |
||||
|
SP-15 |
SP-020045 |
S1-020457 |
22.083 |
003 |
– |
Rel-4 |
F |
Editorial CR to correct terms and references |
4.0.0 |
4.1.0 |
CORRECT |
|
SP-16 |
SP-020267 |
S1-021043 |
22.083 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.1.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.083 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-36 |
22.083 |
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 |
|