hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.2 Description
|
......................................................................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.2.1 Description
|
................................................................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.2.1.1 Indication about multiParty status
|
.......................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.2.2 Applicability to telecommunication services
|
............................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.2.3 Terminology
|
................................................................................................................................................. 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3 Normal procedures with successful outcome
|
..................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.1 Provision
|
...................................................................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.2 Withdrawal
|
................................................................................................................................................... 6
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.5 Activation
|
..................................................................................................................................................... 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.6 Deactivation
|
................................................................................................................................................. 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.7 Invocation
|
..................................................................................................................................................... 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8 Normal operation with successful outcome
|
................................................................................................. 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.1 Beginning the multiParty call
|
................................................................................................................. 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.2 Managing an active multiParty call
|
........................................................................................................ 7
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.3 Managing a held multiParty call
|
............................................................................................................. 8
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.4 Managing a single call and a MPTY
|
...................................................................................................... 8
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.4.1 Single active call
|
............................................................................................................................... 8
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.4.2 Active MPTY and held call
|
.............................................................................................................. 8
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.3.8.5 Remote parties in a Multi-Party Call
|
...................................................................................................... 9
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.4 Exceptional procedures or unsuccessful outcome
|
.............................................................................................. 9
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.5 Alternate procedures
|
.......................................................................................................................................... 9
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6 Interactions with other Supplementary Services
|
................................................................................................ 9
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.81.3 Connected line identification presentation
|
............................................................................................. 9
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.82.1 Call forwarding unconditional
|
.............................................................................................................. 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.82.2 Call forwarding on mobile subscriber Busy
|
......................................................................................... 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.82.3 Call forwarding on no reply
|
.................................................................................................................. 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.82.4 Call Forwarding on mobile subscriber not reachable
|
........................................................................... 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.83.1 Call waiting
|
.......................................................................................................................................... 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.83.2 Call hold
|
............................................................................................................................................... 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.84.1 Multi-party service
|
............................................................................................................................... 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.85.1 Closed user group
|
................................................................................................................................. 10
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.88.1 Barring of all outgoing calls
|
................................................................................................................. 11
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.88.2 Barring of outgoing international calls
|
................................................................................................. 11
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country
|
.................. 11
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.88.6 Barring of incoming calls
|
..................................................................................................................... 11
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
|
........................................ 11
|
64af3f064009d4e29f736a341058c0d4
|
122 084
|
1.7 Interworking considerations
|
............................................................................................................................. 11 Annex A (informative): Change history.......................................................................................................12 History..............................................................................................................................................................13 (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 4 3G TS 22.084 version 3.0.1 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 5 3G TS 22.084 version 3.0.1 0 Scope The present document describes the Supplementary Services belonging to the group MultiParty Supplementary Services. The general aspects, including definitions and recommended provision, of the description of the Supplementary Services are given in TS 22.004. The group of Supplementary Services MultiParty Supplementary Services consists of one Supplementary Service: - MultiParty service (Clause 1). 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004General on Supplementary Services". [3] TS 22.030: Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TS 22.083: Call Waiting (CW) and Call Hold (HOLD) Supplementary Services - Stage 1". [5] TS 22.085 Closed User Group (CUG) Supplementary Services - Stage 1".. [6] TS 21.905: "Vocabulary for 3GPP Specifications" 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TS 21.905. 1 MultiParty Service (MPTY) 1.1 Definition This Supplementary Service provides a mobile subscriber with the ability to have a multi-connection call, i.e. a simultaneous communication with more than one party. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 6 3G TS 22.084 version 3.0.1 1.2 Description 1.2.1 Description A precondition for the multi-party service is that the served mobile subscriber is in control of one active call and one call on hold, both calls having been answered. In this situation the served mobile subscriber can request the network to begin the multiParty service. Once a multiParty call is active, remote parties may be added, disconnected or separated (i.e. removed from the multiParty call but remain connected to the served mobile subscriber). The maximum number of remote parties is 5. 1.2.1.1 Indication about multiParty status Notification shall be sent towards the served mobile subscriber and all the remote parties in a multiParty call at the invocation of this Supplementary Service. In addition, a notification shall always be sent towards all remote parties (i.e. not towards the served mobile subscriber) every time a new party is added to the multiParty call. Notifications shall also be sent to remote parties when they are put on hold and when they are retrieved in accordance with normal Call Hold procedures. In the case where a previously private communication is added again to the multiParty call, a notification shall be sent towards all remote parties. NOTE: During an interim period of time, some networks might not support the sending of the notifications to the remote parties. 1.2.2 Applicability to telecommunication services The applicability of this Supplementary Service is defined in TS 22.004. 1.2.3 Terminology Served Mobile Subscriber During the invocation and active phase, the service is under the control of the served mobile subscriber, i.e. the one who has subscribed to the service. Remote Party Any participant in the multiParty call who is not the served mobile subscriber. 1.3 Normal procedures with successful outcome 1.3.1 Provision This Supplementary Service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not to any subset of these BS. The provision of the Call Hold Supplementary Service is also required. 1.3.2 Withdrawal Withdrawal of the service is made by the service provider upon request by the subscriber or for service provider reasons. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 7 3G TS 22.084 version 3.0.1 1.3.5 Activation The Supplementary Service shall be activated by the service provider as a result of provision. 1.3.6 Deactivation The Supplementary Service shall be deactivated by the service provider as a result of withdrawal. 1.3.7 Invocation Multi-Party service will be invoked by the served mobile subscriber by use of a control procedure, as defined in TS 22.030. 1.3.8 Normal operation with successful outcome Only the served mobile subscriber shall be able to add remote parties to the multiParty call. 1.3.8.1 Beginning the multiParty call When the served mobile subscriber invokes multiParty service from the precondition defined in Section 1.2.1, the network joins the active call and the call on hold together into a multiParty call in which the served mobile subscriber and the remote parties can all communicate with one another. 1.3.8.2 Managing an active multiParty call During an active multiParty call, the served mobile subscriber shall be able to: (i) Add another remote party, to which a private communication has been established using the same procedures as in Section 1.3.8.1, if the number of remote parties does not then exceed the maximum number allowed, which results in an active multiParty call. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties. (ii) Put the connection to multiParty call on hold, i.e. place her connection to the multiParty call on hold (and typically later retrieve it). The served mobile subscriber may make an enquiry call (e.g. to a potential new remote party) or process a Call Waiting request from this state. While the multiParty call is on hold the remaining remote parties in the multiParty call can have communication with each other. As a result of this scenario, the enquiry call or the accepted waiting call can be added to the multiParty call or released. If the call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call. A Hold notification (according to TS 22.083) shall be sent towards all remote parties. (iii) Separate a remote party: Explicitly choose one remote party to have a private communication with. This results in that remote party being removed from the multiParty call which is placed on hold, and the conversation between the served mobile subscriber and the designated remote party being a normal active call (see NOTE 1). The remaining remote parties may have communication with each other in this state. As a result of this scenario the private communication can be added again to the multiParty call or released. If the private call is released by the served mobile subscriber or by the remote party, the served mobile subscriber is in control of a held multiParty call. A Hold notification (according to TS 22.083) shall be sent towards all remote parties, except the designated remote party to which a private communication was established. (iv) Terminate the entire multiParty call. When the served mobile subscriber releases, this is interpreted as a request for termination of the entire multiParty call even if there are calls on hold. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 8 3G TS 22.084 version 3.0.1 No further notification shall be sent. (v) Disconnect a remote party: Explicitly release the remote parties on a one at a time basis (see NOTE 1). In the case when no remote parties remain, the multiParty call is terminated. NOTE 1: If the served mobile subscriber has a private communication with one of the remote parties and this remote party disconnects or is disconnected a notification is sent towards the served mobile subscriber that she has a multiParty call on hold. The notification about the held multiparty call towards the served mobile subscriber is given by the MS, not by the network. 1.3.8.3 Managing a held multiParty call During a held multiParty call the served mobile subscriber shall be able to: 1) Retrieve the held multiParty call, which results in an active multiParty call. 2) Initiate a new call. 3) Process a Call Waiting request. 4) Disconnect the held multiParty call. All calls belonging to the multiParty call shall be released. 5) Disconnect a single remote party. During a held multiParty call the served mobile subscriber shall NOT be able to: Retrieve a single remote party. 1.3.8.4 Managing a single call and a MPTY 1.3.8.4.1 Single active call If the served mobile subscriber is connected to a single active call (regardless whether it is a private communication or a new initiated call) and has a MPTY on hold, she is able to: 1) Disconnect the single active call. 2) Disconnect the held MPTY. 3) Disconnect both. All calls, even if they are on hold, shall be released. 4) Join the single active call and the held MPTY together. This would result in an active MPTY, except if the number of remote parties exceeds the number allowed. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to GSM 02.83) shall be sent towards the previously held remote party. 5) Alternate between both calls. 1.3.8.4.2 Active MPTY and held call If the served mobile subscriber is connected to a active MPTY and has a single call on hold, she is able to: 1) Disconnect the active MPTY. 2) Disconnect the single held call. 3) Disconnect both. All calls, even if they are on hold, shall be released. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 9 3G TS 22.084 version 3.0.1 4) Join the single held call and the active MPTY together. This would result in an active MPTY, except if the number of remote parties exceeds the number allowed. A "MPTY invoke" notification shall be sent towards all remote parties. A Retrieve notification (according to TS 22.083) shall be sent towards all previously held remote parties. 5) Alternate between both calls. If the served mobile subscriber is connected to a active Multi Party call and has a single call on hold, a request for establishing a private communication will be rejected by the network. (Because this would lead to an active call and two calls on hold, which is not supported according to the Call Hold Supplementary Service). An indication will be given to the served mobile subscriber with the reason for failure. 1.3.8.5 Remote parties in a Multi-Party Call Any of the remote parties shall be able to: a) Put her connection to the multiParty call on hold (and typically later retrieve it). The requirements of the Call Hold service then apply; b) Release from the multiParty call. If a remote party releases and no remote party then remains, the requirements of the normal call release procedures then apply. 1.4 Exceptional procedures or unsuccessful outcome If a served mobile subscriber attempts to invoke multiParty service and the network cannot accept that request, the request will be rejected and an indication will be given to the served mobile subscriber with a reason for denial. Some possible reasons for rejection are: - service not subscribed; - resources cannot be allocated; - conflicting situation with other Supplementary Services; - calls are not in appropriate state (e.g. one or more calls are not answered or are in the process of being cleared); - service not supported by the LPLMN. If the service provider cannot satisfy the request to add a further remote party (e.g. if the multiParty call has been cleared or if the maximum number of remote parties allowed has already been reached) the served mobile subscriber shall receive an indication that the request is denied, with the reason for failure. If the radio path of the served mobile subscriber is lost permanently for any reason, the multiParty call shall be released. 1.5 Alternate procedures None identified. 1.6 Interactions with other Supplementary Services 1.6.81.3 Connected line identification presentation Remote parties in an existing multiParty call who have subscribed to connected line number identification presentation will not receive a new remote party's number whenever a served mobile subscriber adds a new remote party to the multiParty call. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 10 3G TS 22.084 version 3.0.1 1.6.82.1 Call forwarding unconditional No interaction, the following text shall give a clarification. Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding unconditional active and operative, the forwarded-to subscriber will be alerted and can be added to the conference. Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections. 1.6.82.2 Call forwarding on mobile subscriber Busy No interaction, the following text shall give a clarification. Calling subscriber: If a calling subscriber attempts to establish a multiParty call to a subscriber with call forwarding on mobile subscriber busy active and operative, and the forwarding condition is met, the forwarded-to subscriber will be alerted and can be added to the conference. Forwarded-to subscriber: A forwarded-to subscriber can establish a multiParty call using an existing forwarded call as one of the multiParty connections. 1.6.82.3 Call forwarding on no reply Same as the interaction between call forwarding on mobile subscriber busy and multiParty call. 1.6.82.4 Call Forwarding on mobile subscriber not reachable Same as the interaction between call forwarding on mobile subscriber busy and multiParty call. 1.6.83.1 Call waiting No interaction. The following text is included for clarification: A user who is active on a multiParty call, either as the served mobile subscriber or as remote party, may receive an indication of a waiting call, provided that the maximum number of calls at the mobile equipment will not be exceeded. After the multiParty call has been put on hold by this user, the waiting call may be accepted by the user. 1.6.83.2 Call hold Any party involved in an active multiParty call (i.e. the served mobile subscriber or a remote party) may place the connection to the multiParty call on hold and later retrieve it. 1.6.84.1 Multi-party service It shall be possible for any remote party in a multiParty call to alternate between two different multiParty calls. Served Mobile Subscriber: The served mobile subscriber cannot control more than one multiParty call at a time. It shall not be possible to invoke multiParty service if either or both of the initial calls are active parts of one or two other multiParty calls. Multi-Party Call controlled by one of the remote parties: The network will not be required to prevent that a leg to one of the other remote parties can be part of another multiParty call controlled by that remote party. 1.6.85.1 Closed user group See TS 22.085. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 11 3G TS 22.084 version 3.0.1 1.6.88.1 Barring of all outgoing calls If barring of all outgoing calls is activated after a multiParty call is invoked, any outgoing calls in progress within that multiParty call will not be barred. Any new outgoing call is barred. 1.6.88.2 Barring of outgoing international calls Same as interworking between barring of all outgoing calls and multiParty service. 1.6.88.4 Barring of outgoing international calls except those directed to the home PLMN country Same as interaction between barring of all outgoing calls and multiParty service. 1.6.88.6 Barring of incoming calls If barring of incoming calls is activated after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred. 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country If barring of incoming calls when roaming outside the home PLMN country is made active and operative after a multiParty call is invoked, any incoming calls in progress within that multiParty call will not be barred. Any new incoming call is barred. Interworking with non-PLMN/ISDN: If a remote party is neither a PLMN nor an ISDN subscriber, it is possible that she is not notified. Mapping of notifications: Direction ISDN to PLMN: 3PTY and CONF shall be mapped onto MPTY. Direction PLMN to ISDN: MPTY shall be mapped onto CONF. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.084 V3.0.1 (1999-10) 12 3G TS 22.084 version 3.0.1 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.84 7.0.0 Transferred to 3GPP SA1 SA#04 22.084 3.0.0 SA#05 22.084 3.0.0 001 R99 3.0.1 Editorial update of references for GSM/3GPP use. (3G TS 22.084 version 3.0.1 Release 1999) ETSI TS 122 084 V3.0.1 (2000-01) ETSI 13 ETSI ETSI TS 122 084 V3.0.1 (2000-01) (3G TS 22.084 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
0.1 References
|
.......................................................................................................................................................... 6
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
0.2 Abbreviations
|
..................................................................................................................................................... 6
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1 Call Waiting (CW)
|
...................................................................................................................................6
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.1 Definition
|
........................................................................................................................................................... 6
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.2 Description
|
......................................................................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.2.1 Description
|
................................................................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.2.2 Applicability to telecommunication services
|
............................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.2.3 Terminology
|
................................................................................................................................................. 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3 Normal procedures with successful outcome
|
..................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.1 Provision
|
...................................................................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.2 Withdrawal
|
................................................................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.5 Activation
|
..................................................................................................................................................... 7
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.6 Deactivation
|
................................................................................................................................................. 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.7 Invocation
|
..................................................................................................................................................... 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.8 Normal operation with successful outcome
|
................................................................................................. 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.8.1 Incoming call from C
|
.............................................................................................................................. 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.8.2 Terminating call by A or B
|
..................................................................................................................... 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.3.11 Interrogation
|
................................................................................................................................................. 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.4 Exceptional procedures or unsuccessful outcome
|
.............................................................................................. 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.4.1 Incoming call from subscriber C ignored by subscriber B
|
........................................................................... 8
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.4.2 Incoming call from subscriber C is indicated as UDUB by subscriber B (or terminal B)
|
............................ 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.4.3 Release by subscriber C within the specified period
|
.................................................................................... 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.4.4 Incoming call from subscriber C is rejected by subscriber B
|
....................................................................... 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.5 Alternate procedures
|
.......................................................................................................................................... 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6 Interactions with other Supplementary Services
|
................................................................................................ 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.82.1 Call forwarding unconditional
|
................................................................................................................ 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.82.2 Call forwarding on mobile subscriber busy
|
............................................................................................ 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.82.3 Call forwarding on no reply
|
.................................................................................................................... 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.83.2 Call hold
|
1.6.83.
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2 Call hold
|
................................................................................................................................................. 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.81.1 Calling line identification presentation
|
................................................................................................... 9
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.84.2 MultiParty
|
............................................................................................................................................. 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.88.6 Barring of all incoming calls
|
................................................................................................................ 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country
|
........................................ 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.7 Interactions with other services
|
....................................................................................................................... 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.7.1 Multicall
|
..................................................................................................................................................... 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
1.8 Interworking considerations
|
............................................................................................................................. 10 2 Call hold.................................................................................................................................................10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.1 Definition
|
......................................................................................................................................................... 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.2 Description
|
....................................................................................................................................................... 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.2.1 Description
|
................................................................................................................................................. 10
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.2.2 Applicability to telecommunication services
|
............................................................................................. 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3 Normal procedures with successful outcome
|
................................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.1 Provision
|
.................................................................................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.2 Withdrawal
|
................................................................................................................................................. 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.5 Activation
|
................................................................................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.6 Deactivation
|
............................................................................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.7 Invocation
|
................................................................................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.3.8 Normal operation with successful outcome
|
............................................................................................... 11
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.4 Exceptional procedures or unsuccessful outcome
|
............................................................................................ 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.4.1 Exceptional operation or unsuccessful outcome
|
........................................................................................ 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.4.6 Invocation
|
................................................................................................................................................... 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.5 Alternate procedures
|
........................................................................................................................................ 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.6 Interactions with other Supplementary Services
|
.............................................................................................. 13 (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 4 3G TS 22.083 version 3.0.1
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.6.83.1 Call waiting
|
.......................................................................................................................................... 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.6.84.2 MultiParty
|
............................................................................................................................................. 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.7 Interactions with other services
|
....................................................................................................................... 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.7.1 Multicall
|
..................................................................................................................................................... 13
|
b2671064415bba1dc2cbd2c8f0018626
|
122 083
|
2.8 Interworking considerations
|
............................................................................................................................. 13 Annex A (informative): Change history.......................................................................................................14 History..............................................................................................................................................................15 (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 5 3G TS 22.083 version 3.0.1 Foreword This Technical Specification has been produced by the 3GPP. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 6 3G TS 22.083 version 3.0.1 0 Scope The present document describes the Supplementary Services belonging to the group Call Completion Supplementary Services. The general aspects, including definitions and recommended provision, of the description of Supplementary Services are given in specification TS 22.004. The group of Call Completion Supplementary Services is divided into the following two Supplementary Services: - Call waiting (clause 1); - Call hold (clause 2). 0.1 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. • For this Release 1999 document, references to GSM documents are for Release 1999 versions (version 8.x.y). [1] GSM 01.04: "Digital cellular telecommunication system (Phase 2+); Abbreviations and acronyms". [2] TS 22.004General on Supplementary Services". [3] TS 22.030: Man-Machine Interface (MMI) of the Mobile Station (MS)". [4] TR 21.905: "Vocabulary for 3GPP Specifications". [5] TS 22.081Line identification Supplementary Services - Stage 1". [6] TS 22.084: "Digital cellular telecommunication system; MultiParty (MPTY) Supplementary Services - Stage 1". [7] TS 22.135: "Multicall Stage 1". 0.2 Abbreviations Abbreviations used in the present document are listed in GSM 01.04 and TR 21.905. 1 Call Waiting (CW) 1.1 Definition The Call Waiting Service permits a mobile subscriber to be notified of an incoming call (as per basic call procedures) whilst the traffic channel is not available for the incoming call and the mobile subscriber is engaged in an active or held call. Subsequently, the subscriber can either accept, reject, or ignore the incoming call. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 7 3G TS 22.083 version 3.0.1 1.2 Description 1.2.1 Description This service operates when the traffic channel at the controlling subscriber B is not available and B is engaged in an active or held call. When a third party (calling subscriber C) attempts to connect to that termination, the controlling subscriber B is given an appropriate indication of the waiting call. A notification that the call is waiting will be sent back towards the calling subscriber C. The maximum number of waiting calls at one time per mobile access is one. This means that no further calls are offered to the subscriber while a call is waiting. NOTE: As a network option this maximum number of waiting calls may be greater than one. This is considered as a possible future enhancement. 1.2.2 Applicability to telecommunication services The applicability of this Supplementary Service to the ongoing call is defined in TS 22.004. The incoming, waiting, call may be of any kind. 1.2.3 Terminology (Controlling) subscriber B This is the subscriber who is provided by the network with the Call Waiting Service and who reacts to the Call Waiting. Subscriber C This is the subscriber who has originated a call to B which causes the Call Waiting Service to be invoked. Subscriber A This represents a subscriber who is engaged in a call with B, being either the calling or the called party. T2; No answer time out The duration of this time out is the time the network will wait for a response from subscriber B, to the offered call from subscriber C. The value of the timer is between 0.5 and 2 minutes at the service providers discretion. 1.3 Normal procedures with successful outcome 1.3.1 Provision This Supplementary Service is provisioned for all Basic Services (BS) subscribed to and to which it is applicable, i.e. not provisioned to any subset of these BS. 1.3.2 Withdrawal Withdrawal will be at the request of the subscriber or for administrative reasons. 1.3.5 Activation This Supplementary Service will be activated either collectively for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in TS 22.030, or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 8 3G TS 22.083 version 3.0.1 1.3.6 Deactivation The service will be deactivated either collectively for all applicable Basic Services or on a Basic Service group basis by the subscriber using a control procedure, as specified in TS 22.030, or by the service provider. The controlling subscriber shall be informed by the network of the success or otherwise of her action. 1.3.7 Invocation This service is invoked by the network on arrival of an incoming call if the service is active and the controlling subscriber B's traffic channel is not available, B is engaged in an active or held call and there is no other call currently waiting. 1.3.8 Normal operation with successful outcome 1.3.8.1 Incoming call from C When an incoming call from subscriber C arrives, the served mobile subscriber is connected to - at least - one call (active or held) and a NDUB (Network Determined User Busy) condition does not exist, then the CW service shall be invoked and the call shall be offered to subscriber B with an appropriate indication, e.g. with a "Call Waiting Tone". If a response to the offered call is received from the mobile termination at B, then the subscriber C shall be given an indication (e.g. ringing tone) that the called subscriber is being informed of the incoming call and, if possible, that call waiting is in operation. 1.3.8.2 Terminating call by A or B If either subscriber A or subscriber B requests that the call is terminated, then this call shall be terminated as for basic call (see TS 22.030 for more information). Subscriber B shall then be given the normal notification that there is a new call to her, as for a normal terminating call. The network shall continue to indicate; e.g. ringing tone towards subscriber C as for a normal call. B can then accept the call from C before the expiry of T2. Subscriber B can also free resources by using the Call Hold Supplementary Service. Subscriber B shall then be able to accept the waiting call from subscriber C before the expiry of T2. Alternatively, subscriber B may specifically request release or hold of the connection to A and accept the waiting call as one action (see TS 22.030). In this case, the network connects subscriber B to subscriber C with no further notifications to either subscriber. This must be done before the expiry of T2. 1.3.11 Interrogation Status check The controlling subscriber may interrogate the network by the use of a control procedure, as specified in TS 22.030. The network shall respond with an appropriate indication telling the subscriber whether the service is supported in this network and, if so, provide a list of all Basic Service groups to which the Call waiting Supplementary Service is active. 1.4 Exceptional procedures or unsuccessful outcome 1.4.1 Incoming call from subscriber C ignored by subscriber B If no response is received by the network from controlling subscriber B before the expiry of T2, then the network shall inform the controlling subscriber B that the call is no longer waiting. Subscriber C shall then be given a no reply indication, unless e.g. Call Forwarding applies. The call waiting service is then made available for a subsequent incoming call. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 9 3G TS 22.083 version 3.0.1 1.4.2 Incoming call from subscriber C is indicated as UDUB by subscriber B (or terminal B) If the waiting call is indicated as UDUB by B before the expiry of T2 the subscriber C shall be given a busy indication, unless e.g. Call Forwarding applies. The call waiting service is then made available for a subsequent incoming call. 1.4.3 Release by subscriber C within the specified period If calling subscriber C terminates the call attempt to subscriber B before the expiry of T2, the call attempt from C shall be terminated, as for basic call, and subscriber B shall be notified. 1.4.4 Incoming call from subscriber C is rejected by subscriber B If the waiting call is explicitly rejected by B before the expiry of T2, the subscriber C shall be given a reject indication. The call waiting service is then made available for a subsequent incoming call. 1.5 Alternate procedures None identified. 1.6 Interactions with other Supplementary Services 1.6.82.1 Call forwarding unconditional If call forwarding unconditional has been activated, it takes precedence over call waiting. Call forwarding unconditional can be activated while a call is waiting without changing the state of the waiting call. 1.6.82.2 Call forwarding on mobile subscriber busy No impact, i.e. neither Supplementary Service shall affect the operation of the other Supplementary Service. The following text clarifies the situation: If user B is NDUB (Network Determined User Busy), Call Forwarding shall take place, and the call is not offered to B. If B is not NDUB, the call shall be offered to B, and if the UDUB (User DUB) condition occurs, then the Call Forwarding shall take place. 1.6.82.3 Call forwarding on no reply If the CFNRy is active and operative for the called subscriber then a waiting call shall still be offered as described in subclause 1.3.8.1 (call waiting indication). If no response is received to this call before the expiry of the No Reply Condition timer, then the call forwarding on no reply service becomes invoked and the call is forwarded as per that call forwarding on no reply service description. 1.6.83.2 Call hold The served user may use the Call Hold service to answer subsequently a waiting call from C. If the served mobile subscriber has an active call and a call one hold the network can still offer an incoming call with the waiting indication i.e. the NDUB condition is not used the normal way (n=2 not 1). NOTE: Although the call is offered to the subscriber, she cannot accept the call as long as she has one active call and one call on hold. If the served mobile subscriber has a call on hold and no active call, an incoming call is offered as a waiting call. 1.6.81.1 Calling line identification presentation See TS 22.081 (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 10 3G TS 22.083 version 3.0.1 1.6.84.2 MultiParty See GSM 22.084 . 1.6.88.6 Barring of all incoming calls Invocation of Barring of Incoming Calls takes precedence over invocation of Call Waiting. Call waiting cannot be activated if barring of incoming calls is activated. The mobile subscriber requesting for call waiting shall be informed of this Supplementary Service incompatibility. The activation of barring of incoming calls does not affect any currently waiting calls. 1.6.88.7 Barring of incoming calls when roaming outside the home PLMN country When active and operative, same as interaction with Barring of All Incoming Calls. 1.7 Interactions with other services 1.7.1 Multicall See TS 22.135 [7]. 1.8 Interworking considerations Calls originating from outside the ISDN/PLMN can undergo call waiting at B. A special in-band indication may be provided to the calling subscriber instead of the normal indication. 2 Call hold 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. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 11 3G TS 22.083 version 3.0.1 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. 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. 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. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 12 3G TS 22.083 version 3.0.1 - 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. 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). (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 13 3G TS 22.083 version 3.0.1 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 2.7 Interactions with other services 2.7.1 Multicall See TS 22.135 [7]. 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. (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 3GPP 3G TS 22.083 V3.0.1 (1999-10) 14 3G TS 22.083 version 3.0.1 Annex A (informative): Change history Change history TSG SA# Spec Versi on CR <Phase> New Version Subject/Comment Jun 1999 GSM 02.83 7.0.0 Transferred to 3GPP SA1 SA#04 22.083 3.0.0 SA#05 22.083 3.0.0 001 002 R99 3.0.1 Editorial update of references for GSM/3GPP use. Multicall (rev787) (3G TS 22.083 version 3.0.1 Release 1999) ETSI TS 122 083 V3.0.1 (2000-01) ETSI 15 ETSI ETSI TS 122 083 V3.0.1 (2000-01) (3G TS 22.083 version 3.0.1 Release 1999) History Document history V3.0.1 January 2000 Publication
|
c59c33a6c4be7d103b9c0a3ad340dec5
|
122 081
|
0 Scope
|
........................................................................................................................................................6
|
c59c33a6c4be7d103b9c0a3ad340dec5
|
122 081
|
0.1 References
|
.......................................................................................................................................................... 7
|
c59c33a6c4be7d103b9c0a3ad340dec5
|
122 081
|
0.2 Abbreviations
|
..................................................................................................................................................... 7
|
c59c33a6c4be7d103b9c0a3ad340dec5
|
122 081
|
1 Calling Line Identification Presentation (CLIP)
|
......................................................................................7
|
c59c33a6c4be7d103b9c0a3ad340dec5
|
122 081
|
1.1 Definition
|
........................................................................................................................................................... 7
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.