Call transfer with automatic return.

<b>Technical Field</b>

This invention relates to telecommunications.

<b>Background of the Invention</b>

As stored program controlled switching systems have evolved, a wide variety of useful features have been developed to extend the communication capabilities such systems provide. One class of features relates to redirecting calls. Consider an example where a customer calls a business and the call is answered by a general customer representative. The representative and the customer talk for a few minutes and the representative determines that the customer should talk to a specialist. The representative then transfers the call to the specialist. If the representative wants to talk with either the specialist or the customer at the end of the call, the representative needs to stay on the line as the customer talks to the specialist. This is wasteful of network resources, e.g., a conference bridge, but even more significantly, it wastes the representative's time.

Recent years have seen an increase in the use of switch adjuncts for providing telecommunication services. Examples of such adjuncts include PBXs, voice mail systems, and service circuit nodes. In many services, the adjunct performs a role similar to that of the customer representative in the above example in that the adjunct transfers the call to a third party. If the service requires the adjunct to resume call control after the customer-specialist conversation is over, the adjunct must stay involved with the call throughout the customer-specialist conversation. In cases where a switch included in the adjunct provides part of the initial connection from a caller to a called party, a subsequent transfer of the call to a third party requires a continued connection through the adjunct switch even though the initial called party may not be associated with the adjunct. In all such services, both network and adjunct resources are wasted. A further problem is that adjuncts that provide telecommunication services over open interfaces, e.g., an ISDN basic rate interface (BRI), often do not have the high reliability or traffic bearing capacity of central switching equipment. These deficiencies are more significant when a talking path is established through the adjunct and such path must be maintained after a call is transferred.

<b>Solution</b>

These problems are solved and a technical advance is achieved in accordance with the principles of the invention in a call processing method where a transferring station can be disconnected from a call after the call is transferred to a third station, but where the call is automatically returned to the transferring station in response to either disconnect signaling or other predefined signaling, e.g., a flash or a dual-tone-multi-frequency (DTMF) tone, advantageously without requiring any station to dial the transferring station. The transferring station is for a subscriber to a new transfer feature referred to as a transfer-with-return. The feature is invoked for the call either in response to a signal from the transferring station requesting invocation of the feature or because the subscriber has only the transfer-with-return feature and no other transfer feature. The call is also returned in response to a busy or no answer condition of the third station. In an arrangement comprising a switching system connected to the transferring station, and an adjunct switch also connected to the switching system, the initial connection may be from the calling station through the switching system, the adjunct switch, and back through the switching system to the transferring station. After the transfer, the connection need not go through the adjunct switch.

A call processing method in accordance with the invention includes connecting a call from a first station to a second station. The call is then transferred from one of the first and second stations to a third station, for communication between the other of the first and second stations and the third station. The one station is for a subscriber to a transfer-with-return feature. The feature is invoked for the call. At some point, the one station is disconnected from the call. The call is automatically returned to the one station in response to a prespecified event and without receiving a dialed number for the one station.

The invention is used in three illustrative services described herein and referred to as Services 1, 2, and 3. In Service 1 (FIGS. 1 and 2), the transferring station is for a human attendant. In Service 2 (FIGS. 13 and 14), the transferring station is a service circuit node (SCN). In Service 3 (FIGS. 15 and 16), the transferring station is an external service module (ESM).

The prespecified event resulting in the automatic return could be receiving disconnect signaling from only one of the other and third stations. The prespecified event could also be receiving predefined signaling, e.g., a flash or DTMF tone, from one of the other and third station. Finally, the prespecified event could be detecting a busy or no answer condition of the third station.

In response to disconnect signaling from both the other and third stations, the one station is notified of the end of the call.

The call transfer is effected in one of three ways: blind transfer, consultation, or conference. With blind transfer, the other station and the third station are connected without having previously connected the one station and the third station for a two-way consulation. With consultation, the one station and the third station are connected for two-way consultation and thereafter the other station and the third station are connected. With conference, the one station, the other station, and the third station are initially connected for a conference and the one station subsequently drops out.

The one station is provided with call history information, e.g., call identification information defining the call as a return call, and defining the reason for the return, for use at the one station in answering or subsequently controlling the return call.

The one station may be connected back in with the other and third stations for conference as part of the automatic return. Alternatively, the one station may be connected with the other station and the third station may be connected with the other station.

If the one station is part of a group of stations, e.g, a multi-line hunt group or automatic call distributor group, that are accessible via one or more common directory numbers, the call is returned to the one station rather than any other station of the group.

In an arrangement comprising a host switching system and an adjunct switch connected to the host system, the illustrative method may be performed by either the host system or the adjunct switch.

A further call processing method in accordance with the invention includes connecting a call from a first station to a second station. The call is then transferred from one of the first and second stations to a third station, for communication between the other of the first and second stations and the third station. At some point, the one station is disconnected from the call. In response to disconnect signaling from both the other and the third stations, the previously disconnected one station is notified of the end of the call.

<b>Drawing Description</b>

<ul id="ul0001" list-style="none"><li>FIG. 1 is a hardware diagram for an arrangement where Service 1 described herein is implemented;</li><li>FIG. 2 is a call flow diagram for Service 1;</li><li>FIGS. 3-11 are action-event diagrams for a number of states used to implement the call flow for Service 1;</li><li>FIGS. 12 is a state diagram summarizing transitions between the states of FIGS. 3-11;</li><li>FIG. 13 is a hardware diagram for an arrangement where Service 2 described herein is implemented;</li><li>FIG. 14 is a call flow diagram for Service 2;</li><li>FIG. 15 is a hardware diagram for an arrangement where Service 3 described herein is implemented; and</li><li>FIG. 16 is a call flow diagram for Service 3.</li></ul>

<b>Detailed Description</b>

<b>Terminology</b>

The terms, 1stStation, 2ndStation, and 3rdStation are used herein to refer to stations of a calling party, called (and transferring) party, and transferred-to party, respectively. The 1stStation originates a call to a 2ndStation, which in turn transfers the call to a 3rdStation, establishing a talking path between the 1stStation and the 3rdStation. The services described herein also apply to cases where a 1stStation originates a call to a 2ndStation, the 1stStation transfers the call to a 3rdStation, establishing a talking path between the 2ndStation and the 3rdStation. The transferring station is also referred to as one of the first and second stations while the non-transferring station is referred to as the other of the first and second stations.

The terms 1stStation, 2ndStation, and 3rdStation should be read broadly as referring to customer and network equipment, telephones, computers, PBXs, and network and third-party switch adjuncts.

<b>Services</b>

The following description relates to three new telephone services: <ul id="ul0002" list-style="none"><li><u>Service 1: Attendant Service with</u><u>Transfer-with-Return</u> In this service description, transfer-with-return and call-history features are illustrated in the context of a service center, in which customers (1stStations) call an attendant (2ndStations), who in turn can transfer the call to service specialists (3rdStations). Upon some designated signal (e.g., a flash, DTMF, or disconnect from the 1stStation or 3rdStation) the 1stStation and/or 3rdStation are reconnected to the 2ndStation.</li><li><u>Service 2: SCN use of</u><u>Transfer-with-Return feature so that SCN can be information gateway</u> In this service description, the notion of an attendant (2ndStation) is generalized to include switching adjuncts, in this case, a Service Circuit Node (SCN) that can invoke the transfer-with-return and call-history features on a host switch. In such a case, the SCN is able to establish independent call legs from or to a 1stStation and a 3rdStation (the SCN acts as the 2ndStation), to apply a variety of service circuits (e.g., announcements, facsimile, and conference facilities), and to transfer the two call legs back to the host switch, so that the SCN is no longer part of the talking path between the 1stStation and 2ndStation. Upon some designated signal (e.g., a flash, DTMF, or disconnect from the 1stStation or 3rdStation) the 1stStation and/or 3rdStation are reconnected to the 2ndStation as a conference of 1st, 2nd, and 3rdStations or two call paths--a communication path between the 1st and 2ndStations and an independent communication path between the 2nd and 3rdStations.</li><li><u>Service 3: ESM use of</u><u>Transfer-with-Return feature so that ESM can be information &amp; service circuit gateway</u> In this service, a service circuit node (SCN) is generalized to less powerful service adjuncts or CPE, e.g., automated telecommunications systems referred to herein as external service modules (ESMs).</li></ul>

<b>Service 1: Attendant Service with Transfer-with-Return</b>

These features are used by a group of 2ndStations (e.g., a group of service attendants) to transfer calls to service agents who specialize in a particular area, and to then have the call transferred back to them for service follow-ups, quality audits, etc. Four sets of features are identified: <ul id="ul0003" list-style="dash"><li>transfer-with-return feature</li><li>return transfer triggers, in particular a call-termination trigger</li><li>call-history feature</li><li>call-termination notification</li></ul>

<b>Feature Descriptions:</b>

<b>A) transfer with return</b>

This feature allows a subscribing attendant (a 2ndStation) to transfer a call (from a 1stStation) to a 3rdStation, allowing a talking path between the 1st and 3rd Stations and allowing the 2ndStation to disconnect from the call. However, following the disconnection by the 2ndStation, the 1stStation and 3rdStation are reconnected to the 2ndStation, if the 1st or 3rdStation signals appropriately; or the 1stStation or 3rdStation are reconnected to the 2ndStation, if the 3rdStation or 1stStation disconnects.

The feature works as a line-subscribed feature, that can be invoked on a per-call basis or automatically invoked on all calls. If subscribed to on a per-call basis, the attendant (2ndStation) may signal transfer with no return, transfer with return, or other subscribed to attendant features, e.g., conference, hold, etc. If the attendant is part of a multi-line hunt or ACD group, the return-transfer is made to the attendant that initially handled the call. If the attendant is busy, the call is forwarded to an appropriate co-worker.

<b>B) return transfer triggers</b>

Reconnection to the 2ndStation is triggered in several ways: disconnection by the 1st or 3rd Station, and signaling (e.g., flash or DTMF) by the 1st or 3rdStation. If the feature allows the 1stStations or 3rdStations to signal (e.g., flash or DTMF) reconnection to the attendant, then the transfer-with-return feature works in conjunction with 3-way calling. The 2ndStation could drop out of the conference and then be asked to come back into the conference. In some cases, a 3rdStation may be an automated service module, e.g., a mail system. To permit the 1stStation to signal a return to the 2ndStation while disconnecting the 3rdStation, a call-termination trigger is needed.

<b>C) call-history feature on returned transfer</b>

So that the 2ndStation (the service attendant) knows that the call is a previously handled call, and so that the 2ndStation is able to quickly identify which call is being returned, the transfer-with-return feature provides call-history and call-identification information in the call-setup message. It also provides a reason message that specifies the reason for the return, e.g., 3rdStation disconnected, 1stStation request, etc.

<b>D) call-termination notification</b>

In some call scenarios, both the 1st and 3rd Stations might disconnect before either is reconnected to the 2ndStation. In such cases, the 2ndStation (the service attendant) might still be interested in the call history between the 1st and 3rd Stations. Thus, the feature permits the attendant to specify (perhaps during service subscription) whether or not they should be notified if the caller and the called party both drop the call.

Note that in the call flow of FIG. 2, the 2ndStation(the attendant) places the 1stStation (the caller) on hold; originates a call to a 3rdStation (e.g., a service agent); conferences together the three stations; and finally disconnects the 2ndStation, leaving a talking path between the 1st and 3rd Stations. The service concept also applies to other call flows. In particular, the 2ndStation could disconnect as soon as the call to the 3rdStation is set up but not answered, thus leaving the 1st and 3rdStations in a ringing state. Further, the 2ndStation could connect to the 3rdStation for two-way consultation prior to connecting the 1stStation and 3rdStation.

FIG. 1 is a diagram of an exemplary network configuration. The 1stStation, 2ndStation and 3rdStation are connected to switches 10, 20, and 30, respectively. Switches 10 and 20 and switches 20 and 30 are interconnected by trunks 15 and 25, respectively, which may include intermediate switches. Billing center 40 and billing subsystems 41, 42, and 43 are discussed later herein with respect to Service 5.

FIGS. 3-11 provide a state chart of how the call-with-return and call-history features operate within switching system 20 for Service 1. FIG. 12 provides a summary of the state transitions.

To improve readability, the following descriptions are partitioned by state. The notation for each state title should be read as: service concept number-state number, state name, e.g., 1-1. state Initial, indicates that Initial is the name of the first state in the state model describing service 1.

<b>1-1. state Initial (FIG. 3)</b>

The call flow begins in the state Initial, with the initial event, Incoming_call. This initial event initiates call processing.

The first action taken in this state is to translate the digits dialed by the 1stStation (i.e., the caller) into a specific directory number, and to then initiate a call-setup to the 2ndStation represented by the dialed directory number.

If the call to the 2ndStation is answered (i.e., an event answered is received from the 2ndStation), then connect 1st and 2nd Stations and transition the state model to another state, 2way.

If the event disconnect is received from either station, then the call ends.

<b>1-2. state 2way (FIG. 4)</b>

If the event disconnect is received from either station, then the call ends.

If the 2ndStation sends an appropriate signal (e.g., a flash or DTMF), and the 2ndStation is a subscriber to the transfer-with-return feature, then place the 1stStation on hold, and transition the state model to another state, 2way_2ndStationActive.

<b>1-3. state 2way 2ndStationActive (FIG. 5)</b>

The 1stStation (caller) is on hold.

Several events are possible in this state:

-

event Initial Event

The state begins by processing the internally generated event, Initial_Event. Processing this event results in a tone!collect_digits action that delivers a stuttered tone to the 2ndStation. The stuttered tone prompts the 2ndStation for a feature code, one of which is transfer-with-return, another is transfer-without-return (i.e., call-transfer as it is currently done).

-

event collected digits

The digits signaled by the 2ndStation are received as the event collected_digits. If the collected digits indicate a request for transfer-with-return, a Return_active indicator is set to true. If the transfer-with-return or -without-return feature is requested, then a second tone!collect_digits action delivers dial tone to the 2ndStation. The dial tone prompts the 2ndStation for a directory number. If a valid directory number is received from the 2ndStation, a call-setup procedure is invoked and the state model then transitions to a new state, 3way_2ndStationActive_3rdStationSetUp

-

event signal

If the appropriate signal (e.g., a flash) is received by the switch from the 2ndStation, the call is returned to the previous 2-way talking path between the 1stStation and 2ndStation, and state model transitions back to the state 2way.

NOTE: the feature may be implemented so that indicating a request for starting transfer procedures is implied by the 2ndStations's (i.e., the subscriber's) initial feature request (flash or DTMF). In this case, call flow would proceed directly from points (1) to (2) in FIG. 5.

<b>1-4. state 3way 2ndStationActive 3rdStationSetUp (FIG. 6)</b>

The 1stStation is on hold, and the 2ndStation has initiated transfer procedures. Several events are possible in this state:

-

event call failed

The call could not be connected to the designated directory number, perhaps because the 3rdStation was busy or did not answer. In this event, busy or ringing (as appropriate) is delivered to the 2ndStation. The state model then transitions to state 2way_2ndStationActive.

-

event call answered

The 3rdStation answers the call. In this case, the switch establishes a 2-way path between the 2nd and 3rd stations. The state model then transitions to an new state, 3way_2ndStationActive_3rdStationActive.

-

event disconnect received from 2ndStation

The 2ndStation disconnects. In this event, the switch establishes a 2-way connection between the 1stStation and the 3rdStation. Since the 3rdStation has not yet answered, the 1stStation receives audible ringing. The state model then transitions to an new state, 2way_1stStationActive_3rdStationActive.

-

event signal received from 2ndStation

The 2ndStation (the subscriber) signals (typically, but not necessarily, by flashing) a request to return to the 2-way call with the 1stStation. In this event, a talking path is established between the 1st and 2nd stations, and the state model transitions back to the state 2way.

In the next two states, the 2ndStation has a two-way conversation with either the 1stStation or the 3rdStation. The 2ndStation's signal (flash or DTMF) acts a toggle between these two states. If the 2ndStation signals a conference request, procedures for a 3-way conversation are initiated.

<b>1-5. state 3way 2ndStationActive 3rdStationActive (FIG. 7)</b>

In this state the 1stStation is on hold, while the 2nd and 3rd Stations are connected in a talking path. Two events are significant in this state:

-

event signal for toggle

received from 2ndStation

If the 2ndStation signals a single flash (or some DTMF equivalent) then the switch opens the path between the 2nd and 3rd Stations, and connects a path between the 1st and 2nd Stations. The state model then transitions to a new state 3way_1stStationActive_2ndStationActive.

-

event signal for conference

received from 2ndStation

If the 2ndStation signals a double-flash (or some DTMF equivalent) then the switch creates a 3-way call between the 1st, 2nd, and 3rd Stations. The state model then transitions to a new state 3way.

<b>1-6. state 3way 1stStationActive 2ndStationActive (FIG. 8)</b>

In this state the 3rdStation is on hold, while the 1st and 2nd Stations are connected in a talking path. Two events are significant in this state:

-

event signal for toggle

received from 2ndStation

If the 2ndStation signals a single flash (or some DTMF equivalent) then the switch opens the path between the 1st and 2nd Stations, and connects a path between the 2nd and 3rd Stations. The state model then transitions back to the state 3way_2ndStationActive_3rdStationActive.

-

event signal for conference received

from 2ndStation

If the 2ndStation signals a double-flash (or some DTMF equivalent) then the switch creates a 3-way call between the 1st, 2nd, and 3rd Stations. The state model then transitions to a new state 3way.

<b>1-7. state 3way (FIG. 9)</b>

In the 3way state, all three stations are connected together in a 3-way conference.

If the 2ndStation disconnects, a 2-way call is created between the 1stStation and the 3rdStation and the state model transitions to state 2way_1stStationActive_3rdStationActive.

If the 1stStation or 3rdStation disconnects, a 2 way call is created between the two remaining stations (between the 2ndStation and 3rdStation, or between the 1stStation and 2ndStation, respectively). If 3rdStation disconnects, the state model transitions back to state 2way. If the 1stStation disconnects, the state model transitions to the state 2way, but consider the 3rdStation as if it were the 1stStation (the original 1stStation is no longer part of the call), except of course, the 2ndStation is now the call originator.

Not shown are procedures that allow the 2ndStation (the subscriber who established the 3-way conference) to request the switch to create a 2-way call between the 2ndStation and 1stStation (or between the 2ndStation and 3rd Station), while placing the 3rdStation (or 1stStation) on hold.

<b>1-8. state 2way 1stStationActive 3rdStationActive (FIG. 10)</b>

In this state, the 2ndStation is not part of the call.

Initially, the connection between the 1st and 3rd station is either in a ringing state or in a talking state (depending upon whether or not the 2ndStation disconnected before or after the 3rdStation answered; or in terms of the state model, depending on whether the previous state was 3way_2ndStationActive_3rdStationSetUp or 3way).

Five events are significant:

-

event no answer received from 3rdStation

If the 3rdStation does not answer, the 1stStation continues to hear ringing until the 1stStation signals a request to return the call to the 2ndStation, or the 1stStation disconnects. No state transition is required.

-

event answer received from 3rdStation

If the 3rdStation answers, then the switch establishes a talking path between the 1stStation and 3rdStation. No state transition is required.

-

event signal for return to 2ndStation

received from 1stStation

The 3rdStation is released (disconnected) from call. If the transfer-with-return feature is active, then the state model transitions to the Return_Call state; if the feature is not active, then the call is terminated and the 1st station is disconnected.

-

event signal for return to 2ndStation

received from 3rdStation

If the transfer-with-return feature is active, then the state model transitions to the Return_Call state; if the feature is not active, then the call is terminated and the 3rd station is disconnected.

-

event disconnect received from

1stStation or 3rdStation

If the transfer-with-return feature is active, then the state model transitions to the Return_Call state; if the feature is not active, then the call is terminated and the remaining stations are disconnected.

<b>1-9. state Return Call (FIG. 11)</b>

Prior to this state, the 1st or 3rd Station disconnected or signalled a request to reconnect a talking path to the 2ndStation (the service attendant and subscriber in Service 1). In this state, the 2ndStation is sent an information message detailing call history information. This information allows the 2ndStation to separate new calls from return calls, to construct service bills if appropriate, or to send billing information back to the host switch.

If the 1st or 3rd Station has disconnected and the 2ndStation answers, the state model transitions back to the state 2way and a two-way talking path is established between the 2ndStation and the remaining station.

If neither the 1st or 3rd Station has disconnected and the 2ndStation answers, the call to the 2ndStation results in a 3-way call involving the 1st, 2nd, and 3rd Stations and a state model transition to the state 3way.

Please note, the 1stStation can force a disconnect of the 3rdStation by sending the appropriate signal, e.g., a designated DTMF sequence.

<b>Service 2: SCN use of Transfer-with-Return feature so that SCN can be information gateway (FIG. 13)</b>

The features detailed in Service 2 are the same as those specified for Service 1: <ul id="ul0004" list-style="dash"><li>transfer-with-return feature</li><li>return transfer triggers, in particular a call-termination trigger</li><li>call-history feature</li><li>call-termination notification</li></ul> In Service 1, these features were demonstrated with a human at each station. In contrast, in Service 2, the human attendant at the 2ndStation is replaced with a Service Circuit Node (SCN).

An arrangement comprising an ISDN switching system 300, a service circuit node 400, and a database 500 is shown in FIG. 39. ISDN switching system 300 is of the type disclosed in U. S. Patent 4,592,048 issued to M. W. Beckner et al. on May 27, 1986. Service node 400 is of the type disclosed in the AT&amp;T A-I-Net™ Service Circuit Node (SCN) System Description and the AT&amp;T A-I-Net™ Service Circuit Node (SCN) Product Technical Specifications Release 1, both of April 15, 1992. System 300 comprises a control arrangement 310, a switching network 320, and line units 330 and is connected to analog station sets 211, 212, and 213 as well as other station sets not shown. System 300 is also connected to service node 400 by a number of ISDN basic rate interface (BRI) lines. Service node 400 comprises a control computer 440, a switch fabric 420, and service circuits 430. Service circuits 430 provide the following capabilities: 1) digit collection, 2) tone detection/generation, 3) FAX receipt, storage, and transmittal, 4) voice recording, storage, and playback, 5) text-to-speech (TTS) announcements, 6) call setup through the switch fabric 420, 7) conference bridging, 8) transferring a call to a second party, and 9) returning call control to system 300. Database 500 provides a reverse white pages directory which returns a calling party name when a calling party number is provided. Although not shown in FIG. 39, service node 200 may be connected to a plurality of ISDN switching systems in addition to system 100. System 300 with the transfer-with-return and call history features added, together with SCN 400 are used as switch 20 and the 2ndStation in FIG. 13.

The features illustrated in the call flow of FIG. 14 can be used by the SCN (the 2ndStation in these examples) to transfer calls back to a host switch (thus increasing service reliability and decreasing traffic capacity), and then regain call control when the 1stStation or 2ndStation disconnects (or appropriately signals). These features also allow the SCN to act as information gateway to a variety of external service modules which are independent and which have no knowledge of the SCN.

This permits several extensions to the basic call flow described earlier: <ul id="ul0005" list-style="none"><li>1. The call could be an in-band or out-of-band data call. This allows the concept to support both voice and data applications.</li><li>2. Because many automated systems can operate on multiple concurrent calls, the call flow described previously can be broadened so that the caller (the 1stStation) need not be placed on hold during the conversation between the 2ndStation (in this case, a SCN) and the 3rdStation (i.e., service agent or ESM). Instead the SCN could maintain parallel conversations with the 1stStation and the 3rdStation before establishing a talking path between the 1st and 3rd Stations. When the 1st or 3rdStation requests reconnection to the 2ndStation (i.e. the SCN) the reconnection could either be a conference including all three parties or two separate calls (1stStation to SCN, and SCN to 3rdStation). This option for reconnection may be provisioned at subscription time. In the case of the SCN, the service is provisioned to support reconnection as separate calls, because the SCN could apply its own conference circuits if necessary.</li><li>3. Because a SCN is used as the automated attendant, the interactions between caller and SCN could allow services in which the SCN: <ul id="ul0006" list-style="dash"><li>plays voice or text-to-speech announcements (e.g., service options);</li><li>collects information that influences service behavior. For example, information might be collected via, <ul id="ul0007" list-style="dash"><li>dtmf digit reception,</li><li>speech recognition,</li><li>speaker verification,</li><li>out-of-band signals from another switching center.</li></ul></li><li>collects information for storage and subsequent analysis, conversion, or retrieval (i.e., playback), e.g., <ul id="ul0008" list-style="dash"><li>voice recording/playback</li><li>ascii-to-fax conversion</li><li>facsimile recording/playback</li><li>text-to-speech conversion</li></ul></li><li>create conferences.</li></ul></li></ul>

The number of different services supported by an SCN is very large. For example, the SCN may provide an information gateway service in which user choices are communicated. As each choice is recognized, the transfer-with-return procedures executes allowing the user access to the chosen service and to return to the SCN after completing the service transaction.

<b>Feature Descriptions:</b>

<b>A) transfer with return</b>

This feature allows the SCN (acting as a 2ndStation, in the current terminology) to call a 1stStation or answer a call from a 1stStation. The SCN may apply a multitude of service circuits to the call (as required by a particular service flow), and eventually may transfer the call to a 3rdStation (possibly an external service module (ESM)). As part of the transfer procedure, the SCN signals that the call should be returned to the SCN under a variety of conditions.

In addition, if the SCN and the 3rdStations need to communicate call-related data, the data could be transmitted to the 3rdStations either as part of the call-setup or could be sent over a RS232 link, a X.25 network, or through the D-channel on ISDN. An alternative would be to transmit the data via a voice channel prior to transferring the 1stStation call to the 3rdStation.

<b>B) return transfer triggers</b>

Reconnection to the 2ndStation ci be triggered in several ways: disconnection by the 1st or 3rd Station, signaling (e.g., flash or DTMF) by the 1st or 3rdStation. If the feature allows the 1stStations or 3rdStations to signal (e.g., flash or DTMF) reconnection to the 2ndStation, then the transfer-with-return feature can work in conjunction with 3-way calling. The 2ndStation may drop out of the conference and then be asked to come back into the conference. In some cases, a 3rdStation may be an ESM, e.g., a mail system. Some of these ESMs may not provide a method by which a caller can request the ESM to initiate a disconnect. Therefore, to permit the 1stStation to signal a return to the 2ndStation (the SCN) and disconnect the 3rdStation (the ESM) from the call, a call-termination trigger is needed.

<b>C) call-history on returned transfer</b>

As part of the return transfer procedure, the switch alerts the 2ndStation (the SCN) with a call set-up message containing the caller's DN and a transaction_id (possibly the account code). A reason message is provided that specifies the reason for the return, e.g., 3rdStation disconnected, caller-initiated return, etc. The 2ndStation (the SCN) can then process the call using the appropriate customer logic, and determine the call history and billing records from internally stored data. (Note the call-history capability referred to in Service 1 could be provided through an SCN, if all call-transfers return to the SCN, or all call-history records are sent to the SCN).

<b>D) call-termination notification</b>

If the caller disconnects, then a message is sent to the 2ndStation (the SCN), so that the 2ndStation (the SCN) can track service measurements and 3rdStation usage (if this important for the service).

<b>Service 3: ESM use of Transfer-with-Return feature so that ESM can be information &amp; service circuit gateway (FIG. 15)</b>

The features detailed in this service are the same as those specified for Service 1: <ul id="ul0009" list-style="dash"><li>transfer-with-return feature</li><li>return transfer triggers, in particular a call-termination trigger - call-history feature</li><li>call-termination notification</li></ul> In Service 2, the 2ndStation was operated by a Service Circuit Node. In contrast, Service 3 uses a simple external service module (gateway-ESM) as the 2ndStation. The gateway-ESM is capable of concurrently answering multiple calls (by sending the appropriate control message) and transferring them to various locations. There is no need for the gateway-ESM to provide announcement circuits or a switch network. The 3rdStations that receive the transferred calls can be operated by service agents or service-circuit ESMs that provide announcements, record/send voice or facsimile, etc. The call flow is shown in FIG. 16.

<b>Feature Description</b>

<b>A) transfer with return</b>

This feature allows the gateway-ESM (acting as a 2ndStation, in the current terminology) to call a 1stStation or answer a call from a 1stStation. The ESM can only answer and transfer calls to a 3rdStation (possibly a service-circuit or external service module (ESM)). As part of the transfer procedure, the gateway-ESM signals that the call should be returned to the gateway-ESM under a variety of conditions.

In addition, if the gateway-ESM and the 3rdStations need to communicate call-related data, the data could be transmitted to the 3rdStation either as part of the call-setup or could be sent over a RS232 link, a X.25 network, or through the D-channel on ISDN. An alternative would be to transmit the data via a voice channel prior to transferring the 1stStation to the 3rdStation.

<b>B) return transfer triggers</b>

Reconnection to the 2ndStation can be triggered in several ways: disconnection by the 1st or 3rd Station, signaling (e.g., flash or DTMF) by the 1st or 3rdStation. If the feature allows the 1stStations or 3rdStations to signal (e.g., flash or DTMF) reconnection to the 2ndStation, then the transfer-with-return feature can work in conjunction with 3-way calling. The 2ndStation may drop out of the conference and then be asked to come back into the conference. In some cases, a 3rdStation may be an ESM, e.g., a mail system. Some of these ESMs may not provide a method by which a caller can request the ESM to initiate a disconnect. Therefore, to permit the 1stStation to signal a return to the 2ndStation and disconnect the 3rdStation (e.g., a voice mail ESM) from the call, a call-termination trigger is needed.

<b>C) call-history on returned transfer</b>

As part of the return transfer procedure, the switch alerts the 2ndStation (the gateway-ESM) with a call set-up message containing the caller's DN and a transaction_id (possibly the account code). A reason message is provided that specifies the reason for the return, e.g., 3rdStation disconnected, caller-initiated return, etc. The 2ndStation (the gateway-ESM) can then process the call using the appropriate customer logic, and determine the call history and billing records from internally stored data. (Note the call-history capability referred to in Service 1 could be provided through a gateway ESM, if all call-transfers return to the gateway-ESM, or all call-history records are sent to the gateway-ESM).

<b>D) call-termination notification</b>

If the 1stStation disconnects, then a message is sent to the 2ndStation (gateway-ESM), so that the 2ndStation. (the gateway-ESM) can track service measurements and 3rdStation usage (if this important for the service).

Please note, in this scenario, the human attendant is replaced with an automated system. This permits several extensions to the basic call flow described earlier: <ul id="ul0010" list-style="none"><li>1. The call could be an in-band or out-of-band data call. This allows the concept to support both voice and data applications.</li><li>2. Because many automated systems can operate on multiple concurrent calls, the call flow described previously can be broadened so that the caller need not be placed on hold during the conversation between the automated attendant (in this case, a ESM) and the third-party (i.e., service agent or another ESM). Instead the automated attendant could maintain parallel connections with the caller and the third party before establishing a talking path between the caller and third party.</li></ul>