3GPP2 S.R0006-506-A Version 1.

0 Version Date: June 2007

Wireless Features Description: Call Transfer

COPYRIGHT
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

Revision History

Revision Rev. 0 Rev. A Initial Publication (Note 1) Note 2

Date December 1999 June 2007

Notes: 1. S.R0006-0 v1.0 was published as a single part. 2. All parts of S.R0006-A v1.0 replace S.R0006-0 v1.0.

S.R0006-506-A v1.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Wireless Features Description: Call Transfer

Contents
List of Tables...................................................................................................................................................ii 1 Call Transfer (CT).............................................................................................................................1 1.1 1.2 1.3 1.4 Normal Procedures with Successful Outcome....................................................................1 Exception Procedures or Unsuccessful Outcome ...............................................................3 Alternative Procedures .......................................................................................................4 Interactions with Other Wireless Services..........................................................................4

506-i

Contents

S.R0006-506-A v1.0
1 2

List of Tables
Table 1: Table 2: Holding 2Way State for Call Transfer .......................................................................2 3-Way State for Call Transfer......................................................................................2

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

List of Tables

506-ii

S.R0006-506-A v1.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Call Transfer (CT)

Call Transfer (CT) enables the subscriber to transfer an in-progress established call to a third party. The call to be transferred may be an incoming or outgoing call. While CT is invoked, CT impacts the subscribers ability to receive calls. After CT is finished or when CT is not invoked, CT does not impact a subscribers ability to originate calls or to receive calls.

Applicability to Telecommunications Services CT is applicable to voice telecommunication services.

1.1

Normal Procedures with Successful Outcome

Authorization CT may be generally available or may be provided after prearrangement with the service provider.

Deauthorization CT may be withdrawn at the subscribers request or for administrative reasons.

Registration CT has no registration.

Deregistration CT has no deregistration.

Activation CT shall be activated upon authorization.

Deactivation CT shall be deactivated upon deauthorization.

Invocation CT may be invoked by an authorized subscriber putting a call on hold, dialing a third party and then disconnecting.

506-1

Call Transfer (CT)

S.R0006-506-A v1.0
1

CT may be invoked by a subscriber with both CT and Three-Way Calling activated by establishing a three-way call and then disconnecting.

2 3 4 5

Normal Operation with Successful Outcome CT allows a controlling subscriber to put a call on hold, dial a third party, and then connect the held party and the third party into a call. The following table defines the system reactions for each call party action that are different than Three-Way Calling (3WC). Refer to Three-Way Calling normal operations with successful outcome for the system reaction tables rather than repeating the information here. Table 1: State Holding 2-way Holding 2Way State for Call Transfer Condition One party is on hold. The controlling subscriber is alerting the other party, or the controlling subscriber is in a two-way conversation with a third party. System Reaction Release the controlling subscriber. Connect the held party and the third party. Optionally apply a warning tone. Go to the Idle state. Ignore any accompanying digits. Release the third party. Connect the held party and the controlling subscriber. Optionally apply a warning tone. Go to the 2-way state.

6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

XID 5E 1 5A 1 5F 1 5S 1 5U 1

Call Party Action The controlling subscriber presses the END key. To avoid transferring the call or to drop the third party, the controlling subscriber without Three-Way Calling active presses the SEND key with or without digits.

24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

CT also allows a controlling subscriber, which also has Three-Way Calling (3WC) active, to set up a three-way call and then drop out of the call leaving the other two parties of the call connected to each other. The following table defines the system reactions for each call party action that are different than Three-Way Calling (3WC). Refer to Three-Way Calling normal operations with successful outcome for the system reaction tables rather than repeating the information here. Table 2: State 3-way 3-Way State for Call Transfer Condition A connection is established between the controlling subscriber, a second party and a third party. System Reaction Release the controlling subscriber. Connect the second party and the third party. Optionally apply a warning tone. Go to the Idle state.

39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54

XID 6E 1

Call Party Action The controlling subscriber presses the END key.

55 56 57 58 59 60

Call Transfer (CT)

506-2

S.R0006-506-A v1.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Call Detail Record The system should record call detail information for the following: a. b. c. d. CT invocation activities and events. CT bridge usage duration. Actual air time usage duration. Transfer-to call leg usage.

See DMH for the specific information to be included for each element.

1.2

Exception Procedures or Unsuccessful Outcome

Registration None identified.

Deregistration None identified.

Activation None identified.

Deactivation None identified.

Invocation The CT request shall be rejected when the invoking subscriber is not authorized. The subscriber may be notified of the rejection cause, and the established end-to-end connection shall remain in the state existing prior to the request. Refer to Three-Way Calling exception procedures or unsuccessful outcome for invocation for the system reaction tables rather than repeating the information here.

Exceptions While Roaming None identified.

Exceptions During Intersystem Handoff None identified.

506-3

Call Transfer (CT)

S.R0006-506-A v1.0
1

1.3

Alternative Procedures
An alternative procedure has been identified for CT. This procedure builds upon the normal CT procedures. Refer to the alternative procedures of Three-Way Calling (see S.R0006-522) for the system reaction tables.

2 3 4 5 6 7 8 9

1.4

Interactions with Other Wireless Services

Asynchronous Data Service (ADS) CT does not support ADS.

10 11 12 13 14 15 16 17

Call Delivery (CD) None identified.

18 19 20 21 22

Call ForwardingBusy (CFB) None identified.

23 24 25 26 27

Call ForwardingDefault (CFD) None identified.

28 29 30 31 32 33

Call ForwardingNo Answer (CFNA) None identified.

34 35 36 37 38

Call ForwardingUnconditional (CFU) None identified.

39 40 41 42 43

Call Transfer (CT) Not applicable.

44 45 46 47 48

Call Waiting (CW) CT and CW are mutually exclusive. A call incoming to a controlling subscriber setting up or engaged in a CT shall be given busy treatment, even if the called subscriber has CW active. A flash request (i.e., pressing the SEND key) from a subscriber authorized for CT while CW alerting is being applied, shall be used to respond to the CW call. If the controlling subscriber still desires to transfer the call, it must first dispose of the CW call before requesting a transfer.

49 50 51 52 53 54 55 56 57 58 59 60

Call Transfer (CT)

506-4

S.R0006-506-A v1.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Calling Name Presentation (CNAP) None identified.

Calling Name Restriction (CNAR) If the CT controlling subscriber is authorized for a Variable Per-Call CNAR Mode and activates CNAR during the setup of a CT leg, the CNAR activation applies only to that call leg. If the CT controlling subscriber is authorized for a Variable Per-Call CNAR Mode and deactivates CNAR during the setup of a CT leg, the CNAR deactivation applies only to that call leg.

Calling Number Identification Presentation (CNIP) None identified.

Calling Number Identification Restriction (CNIR) If the CT controlling subscriber activates the Temporary CNIR Mode during the setup of a CT leg, then the Temporary CNIR activation applies only to that call leg. If the CT controlling subscriber deactivates the Temporary CNIR Mode during the setup of a CT leg, then the Temporary CNIR deactivation applies only to that call leg.

Conference Calling (CC) Once CT is invoked, CT takes precedence over CC. That is, the controlling subscriber cannot add more parties to a CT (in effect trying to convert the CT call into a CC). Once CC is invoked, CC takes precedence over CT. That is, the conference controller cannot transfer a conference in progress or relinquish control of the conference to one of the conferees.

Data Privacy (DP) CT does not support DP.

Do Not Disturb (DND) None identified.

Emergency Services (9-1-1) If a subscriber with CT invokes 9-1-1 during a call or with a call on hold (thereby seemingly invoking CT), transfer shall not take place if the controlling subscriber disconnects. Also, a flash (an activation of the SEND key) while communicating with

506-5

Call Transfer (CT)

S.R0006-506-A v1.0
1

a PSAP is used to bridge the held party into the conversation rather than to disconnect the PSAP. If 9-1-1 is invoked while idle, flash requests and attempts to a third number are ignored. Flexible Alerting (FA) None identified.

2 3 4 5 6 7 8 9 10 11 12

Group 3 Facsimile (G3 Fax) CT does not support G3 Fax.

13 14 15 16 17

Message Waiting Notification (MWN) MWN pip tone should only be applied for the first leg of the call.

18 19 20 21 22

Mobile Access Hunting (MAH) None identified.

23 24 25 26 27

Network Directed System Selection (NDSS) None identified.

28 29 30 31 32

Non-Public Service Mode (NP) This interaction is beyond the scope of this standard.

33 34 35 36 37

Over-the-Air Service Provisioning (OTASP) When OTASP is active, it takes precedence over all other calls and features.

38 39 40 41 42 43

Password Call Acceptance (PCA) None identified.

44 45 46 47 48

Preferred Language (PL) None identified.

49 50 51 52 53

Priority Access and Channel Assignment (PACA) None identified.

54 55 56 57 58 59 60

Call Transfer (CT)

506-6

S.R0006-506-A v1.0
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Remote Feature Control (RFC) None identified.

Selective Call Acceptance (SCA) None identified.

Service Negotiation (SN) None identified. Subscriber PIN Access (SPINA) CT should not be activated while SPINA is active.

Subscriber PIN Intercept (SPINI) The service provider may require the CT invoking subscriber (with SPINI active) to enter the SPINI PIN when initiating a CT. That is, the subscriber shall be requested to enter the SPINI PIN on any call leg, if the call leg meets the call type criteria for SPINI.

Three-Way Calling (3WC) CT takes precedence over 3WC. When the controlling subscriber disconnects on an active three-way call, and also has CT active, then the disconnect shall be used to transfer the call and the two non-controlling parties remain connected. To avoid a call transfer, the controlling subscriber may force a three-way call to disconnect by sending a flash request to drop the last party added and then disconnecting the remaining party. 3WC takes precedence over CT for the interpretation of flash requests. If the controlling subscriber presses SEND in the Holding 2-way state (and both CT and 3WC are active), the result is a conference request rather than a CT drop party request. If the controlling subscriber presses SEND while in the 3-way state, the last party is requested to be dropped.

User Group (UG) None identified. Voice Message Retrieval (VMR) None identified.

506-7

Call Transfer (CT)

S.R0006-506-A v1.0
1

Voice Privacy (VP) None identified.

1

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60

Call Transfer (CT)

506-8