MXPA97002833A - Method and apparatus for providing an advanced system for improved delivery delivery in a telecommunication system - Google Patents

Abstract

The present invention relates to a method of sending a call in a communication system in which a plurality of stations of the subscriber are interconnected through a switch for communication with one another, the method comprises the steps of: receiving in the switch a call of a first station of plurality of stations of the subscriber, the call is initially directed to a second station of the plurality of stations of the abandoned, establish a connection between the first station and the second station, put a warning on the second station, provide a call tone to the first station, disconnect the connection between the first station and the second station, carry out a call sending establishment to a third station of the plurality of subscriber stations, determine a result of the call sending establishment and send the call in accordance with the result of the shipment establishment of ll beloved, wherein the sending step further comprises the step of re-establishing the connection between the first station and the second station in response to a determination that the result of the call sending establishment was unsatisfactory

Description

"METHOD AND APPARATUS FOR PROVIDING AN ADVANCED FEATURE FOR SENDING IMPROVED CALL, IN A TELECOMMUNICATION SYSTEM" BACKGROUND OF THE INVENTION TECHNICAL FIELD OF THE INVENTION This invention relates to the processing of calls in a telecommunication system and, more particularly, to the processing of an improved Call Forward feature does not answer.

DESCRIPTION OF THE RELATED TECHNIQUE The developments and improvements in communication switching systems have allowed operators of the telecommunication system to offer a number of new and useful services to the subscribers of the system. An example of this type of service is the call forwarding feature that is ently provided by telephone companies. Call forwarding allows subscribers to automatically redirect calls made to the subscriber's number (base address) to another number (distant address) in the system.

Telephone systems ently provide the feature of call forwarding in distant forms. Examples include Variable Call Forwarding (CFV), where the subscriber is allowed to directly activate and deactivate the send and specify the remote address to which calls should be sent during each activation. While CFV is active, calls to the subscriber's line are directed to the remote address, and if the remote address is busy, a reminder call is provided to the base address. A second example of call forwarding features is Call to Busy Line (CFBL). In the CFBL, calls to the base address are sent to a remote address only when the base address is occupied. A third example of a call submission is Call Forwarding Do Not Answer (CFBL). In CFBL, calls that end in the base address call the base address during a specified interval. A CFD synchronizer is used to synchronize the interval. If the call is not answered, it is sent to a distant address. Because the base address calls in CFD, the ent CFD implementations suffer from an inconvenience that oc when calls can not be sent successfully. When the call is not sent successfully after the called base address has not answered, a caller (home address) will hear the tone of the call and then a busy or congestion tone. Hearing the busy or congestion tone after having heard a tone of the call can be confusing for the caller and is not desirable in a telephone system. A typical solution involves checking the status of the line, of the shipping line before the call is sent. If the state of the line is another one that is not unoccupied, the call is not sent. This solution is disadvantageous since the remote address may be busy but may have a characteristic, such as the call forwarding (CFV), Call Waiting (CW) or Busy to Complete Series (SCB) variable, which would allow the The call will be completed, but it would not be invoked because the call is not sent when the line is found other than the unoccupied one. A second problem also oc when, even when the state of the line is unoccupied, a call can not be successfully sent due to a congestion. In this situation, the caller at the address of origin will hear the confusion sequence of a ring tone followed by a congestion tone. The telephone industry standard for Call Sub-Features, the Bellcore document TR-TSY-000586, Expedition 1, July 1989, is incorporated herein by reference. The standard requires that the problem be sent unsatisfactorily towards a second characteristic or a distant occupied address is taken into account in systems that conform to it's norm. The BellCore standard indicates the general requirement that if the remote address is busy, but it has a sending feature that can be invoked, then the sending from the distant address must be carried out. The standard also requires that if the remote address is busy, and has no sending characteristics, then the call should be considered as a non-sent call, and the call handling not sent be applied to the call. The call handling is not sent and the rule is to continue calling the base address and continue sending a ring tone to the home address. If the normal requirement is met, an originating subscriber will not hear a ringing tone followed by a busy tone if the remote address is occupied. Also, a second shipment will be made if the CFD is to a distant address that is assigned a shipping characteristic. The Bellcore standard does not deal with the problems that can occur in CFD when shipments are involved in sequence. For example, a source address may call a base address, which in turn has a CFD implemented to send to a first remote address that has a CFV implemented to send to a second remote address. In this situation, if the base address does not answer, and the second distant address is busy, the caller at the source address will hear a ringing tone when the base address calls and then hear a busy tone after the call was sent from the first remote address to the second distant address. In addition, a second problem occurs in this solution when a call can not be sent from the base address successfully due to a congestion, even when the remote address is idle, or if it is busy or has a feature that can not be invoked. In this situation, even when the remote address is idle or busy and has a feature that can be invoked, the caller at the source address will hear the confusion sequence of a ringing tone followed by a congestion tone.

COMPENDIUM OF THE INVENTION The present invention provides a method and apparatus that provides Call Forwarding Do not Count with an Advance feature. The Advanced feature prevents the sequence of a ringing tone followed by a busy tone or congestion from being heard at the source address when a call has not been successfully sent. In one aspect, the present invention provides a method and apparatus in a communication system for receiving a call directed from a first subscriber station to a second subscriber station, creating a through connection between the first and second stations of the subscriber, giving notice to the second station, providing a ring tone to the first station, interrupting the connection between the first and second stations, carrying out a call set-up to a third subscriber station, and, determining the results of the Call Set-up. In another aspect, the present invention provides a method and apparatus for continuing to give notice to the third station and terminating the warning of the second station if the result of the Call Establishment is satisfactory. In another aspect, the present invention provides a method and apparatus for reconnecting the second station with the first station if the result of the Call Establishment is unsatisfactory.

In yet another aspect, the present invention provides a method and apparatus for calling a feature if the result of the Call Set-up was a designated feature, carrying out a second Call Set-up to a fourth station of the subscriber and determining the results of the call set-up. Second Call Establishment.

BRIEF DESCRIPTION OF THE DRAWINGS For a more detailed understanding of the present invention, for further objects and advantages thereof, reference may now be made to the following description taken in conjunction with the accompanying drawings, in which: Figure 1 is a functional diagram of high level of an appropriate telephone system switching arrangement to implement the preferred embodiment of the present invention; Figure 2 is an illustrative functional diagram of the No Answer Answer Send software and an AXE hardware organization of Figure 1; Figure 3 is a table to categorize the Call Set-up System events that occur during the implementation of the Callback Advanced Not Reply feature; Figure 4 illustrates a call scenario for a successful call set-up result; Figure 5 illustrates a call scenario for an unsatisfactory call set-up result; Figure 6 illustrates a call scenario for a characteristic designated call set-up result; Figure 7 illustrates a call scenario for a characteristic call set-up result when there is more than one subscriber in the Callback call does not Answer; Figure 8 illustrates a call scenario for a characteristic call set-up result when a characteristic other than another send feature is signaled; Figure 9 is a flow chart illustrating the functions carried out by the software Advanced Call Send Do not Answer, when the processing of the call is initiated in accordance with the teachings of the present invention; Figure 10A is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 as the Advance to CFD software is invoked; Figure 10B is a signal flow diagram illustrating the exchange of the signals between the functional blocks of Figure 2 during CFD Advance Call installation; Figure 10C is a signal flow diagram illustrating signal exchange during call set-up between the functional blocks of Figure 2, when the remote subscriber is idle without termination feature: Figure 10D is a flow chart of signals illustrating the exchange of signals during the establishment of the call between the functional blocks of Figure 2, when the remote subscriber is busy or congested; Figure 10E is a signal flow diagram illustrating the exchange of the signals during call set-up between the functional blocks of Figure 2 when the remote address has an active termination characteristic; Figure 10F is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the result of the Call Set-up is successful.

Figure 10G is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the result of the Call Establishment is unsatisfactory. Figure 10H is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the result of the Call Set-up is a designated characteristic, and, the signaling characteristic is a feature of the Set-up type. Call. Figure 101 is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the result of the Call Set-up is a designated feature, and, the signaling characteristic is a Call Set type feature.; Figure 10J is a signal flow diagram illustrating the exchange of signals within the functional blocks of Figure 2, when the Call Establishment by the designated feature is towards a termination subscriber that is idle without active termination feature; Figure 10K is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2, when the Call Establishment by the designated feature is towards a busy or congested subscriber without active termination feature; Figure 10L is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2, when the Establishment of Calling by the indicated particularity is towards a second indicated characteristic; Figure 10M is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2, when the Establishment of Calling by the indicated characteristic has a satisfactory result; Figure ION is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2, when the Establishment of Calling through the indicated feature is unsatisfactory; and Figure 10O is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2, when the result of the Establishment of Call through the particularity indicated is a second particularity indicated.

DETAILED DESCRIPTION OF THE INVENTION Figure 1 shows a telephone switching system in which the present invention can be implemented. The system of Figure 1 includes a telecommunication switch 100 controlled by stored program which may be for example an Ericsson AXE. The system also includes the subscriber apparatuses of the station 102, 104, 106, 108 and 110, and the basic subscriber access lines 112, 114, 116, 118 and 120. The AXE 100 contains a software subsystem of the subscriber system. operation and hardware referred to as the 122 APZ subsystem, and a software subsystem referred to as the 124 APT subsystem. Access lines 112-120, for example, can be basic rate lines of type Q.931. The APZ 122 contains the hardware and processors for the application software operation that is contained within APT 124. The APT 124 also contains the switching equipment to direct the call traffic, as well as the characteristic software that implements the features. of the call service. Figure 2 is an illustrative functional diagram of the Advanced Send Not Answer software and related hardware and software works in the APT Section of the AX in Figure 1. APT software and hardware functional blocks include the Traffic Manager ( TrafficMgr) 202, Connection Manager (ConnectionMgr), Feature Manager (FeatureMgr) 206, Interaction Manager (InteractionMgr) 208, Callback Do Not Answer (FeatureCFD) 210, other related features (FeatureOther) 212, and, a Characteristic Database (FeatureDB) 214. The TrafficMgr 202 contains software and hardware that manages the new call facilities. During the new call setup, the TrafficMgr 202 uses the data received from FeatureCFD 210 or FeatureOther 212 via FeatureMgr to establish the call. The TrafficMgr 202 also contains analysis tables that are used to determine where an address is placed and also if an address has any of the termination characteristics. The trafficMgr 202 is able to ask a subscriber line of the address to determine if the line is unoccupied, busy or congested. In addition, the TrafficMgr 202 starts the CFD synchronizer for base addresses with active CFD. The ConnectionMgr 204 handles the physical connection between the subscribers. The ConectionMgr 204 can create a connection between the subscribers or interrupt an already established connection. FeatureMgr 206 handles instructions received from FeatureCFD 210, FeatureOther 212, or InteractionMgr 208, requesting action from ConnectionMgr 204, TrafficMgr 202, or InteractionMgr 208. InteractionMgr 208 performs the function of resolving conflicts between two features that are leading to out actions on the same call. The InteractionMgr 208 ensures that only one feature at a time has control over a call. The FeatureCFD 210 contains the logic necessary to control the CFD Advanced function. The FeatureOther 212 block is a generic representation of other features that interact with FeatureCFD 210. FeatureOther 212 can be one of two types: (1) A Call Set type feature where invoking the feature will result in a call which must be established with the Call Set results determined by feature CFD 210, or, (2) a non-call type Set feature where the feature will not need a call set. The FeatureDB 214 contains the database containing information, v.gr, a remote address for sending, about a subscriber connected with a feature that is provided by the FeatureCFD 210 or FeatureOther 212 blocks.

The present invention provides a method and system in which the subscriber calling a CFD subscriber will not hear a ringing tone followed by a congested or confused busy tone, in problem situations discussed above. When the CFD subscriber stops answering the call within the specified time, the expiration of the CFD time occurs and the CFD feature uses an Advanced mechanism to determine if the call can be successfully sent. The Advance mechanism consists in interrupting the connection between the source and base addresses, establishing a call to the remote address and waiting for the results of the call establishment before terminating the call tone in the origin address. The system continues to supply the call tone to the source address and calls the base address after the connection has been interrupted. Three types of Call Establishment results can be received: Satisfactory, unsatisfactory or the indicated characteristic. Figure 3 is a table that categorizes the Call Set-up System events that occur during the implementation of the Callback Advance feature. Do not answer. If the result of the Call Set-up is satisfactory, the origin and distant addresses are connected (the call is sent), and the base address is released. The call at the base address will be terminated and the source address will be supplied with a ring tone from the new connection. If the result is unsatisfactory, the source and base addresses will reconnect after being disconnected during the Call Set-up (no call sending processing is applied). If the result is of indicated characteristic, the indicated characteristic is retained to continue the establishment of call. The CFD feature will remain on the call to inspect the call establishment. The CFD characteristic receives the results of the subsequent call establishment (s) and acts on the results in the same way as it reacted for the results of the initial call setup. The Advanced mechanism continues and the characteristic CFD will remain on the call until it receives either a satisfactory or unsatisfactory call set-up result. In all these situations the CFD Advance features provide the caller with a constant ring tone. Figures 4-8 illustrate possible scenarios in which the CFD Advance feature will provide the source address with a constant ring tone. Figure 4 illustrates a call scenario for a successful call setup result. The origin address 400 calls the base address 402. The base address has the Call Reply Not Reply (CFD) feature to the remote 404 address. When the base address 402 stops responding within the specified amount of time, the CFD timeout occurs and a call set-up is attempted to the remote 404 address. The connection system event is received indicating the connection of the source address to the remote 404 address has occurred. This is a successful result of the call set-up so that the remote address 404 starts ringing or calling, indicating that the connection between the source address 400 and the remote 404 address has been completed. Base address 402 then disconnects and stops calling. Figure 5 illustrates a call scenario for an unsatisfactory call set-up result.

The home address 500 calls the base address 502. The base address 502 has the characteristic CFD at the remote address 504. Then the base address 502 stops responding within the specified amount of time, a CFD time extension occurs and a call set-up is attempted to the remote address 504. The busy subscriber system event is received which is a result of unsatisfactory call setup, so that the base address 502 continues calling until they answer or until the origin address 500 is disconnected. Figure 6 illustrates a call scenario in which the first result received from the call set-up attempted to the first remote address 604 is a designated feature that is a call setup type feature. The second result received from the call set-up that has been attempted towards the second remote address 606 is satisfactory. Address 600 of origin calls address 602 of base. The base address 602 has the characteristic CFD at the first remote address 604. The first remote address 604 has the Call Variable Send (CFV) feature to the second remote address 606. The base address 602 stops responding within the specified amount of time, the CFD timeout occurs and a call set-up is attempted to the first remote address 604. The signal feature system event is received indicating the CFV characteristic. The CFV feature is invoked which carries out a call setup to the second remote address 606. The connection system event is received indicating that the connection from the source address to the second remote address 604 occurred. This is a successful call set-up result so that the second remote address 606 begins to call or ring, indicating that the connection between the source address 600 and the second remote address 606 has been completed. The base address 602 is then disconnected and stops calling. Figure 7 illustrates a call scenario that shows how the Advanced mechanism works when there is more than one CFD subscriber in the call. The home address 700 calls the base address 702. The base address 702 has a CFD to the first remote address 704. When the base address 702 stops responding within a specified amount of time, the CFD timeout occurs and a call set-up is attempted to the first remote address 704. The connection system event is received indicating that the connection of the source address 700 to the first remote address 704 occurred. This is a successful call set-up result so that the remote address 704 begins to call, indicating the connection between the source address 700 and the first remote address 704. Base address 702 then disconnects and stops calling. The Advanced mechanism for the first base address 702 has concluded. When the first remote address 704 stops responding within the specified amount of time, a CFD timeout occurs and a call set-up is attempted to the second remote address 706. The busy subscriber system event is received which is an unsatisfactory call set-up result so that the first remote address 704 continues to call until there is an answer or until the source address 700 is disconnected. From this example it will be seen that the advance is carried out every time the CFD timeout occurs. When the characteristics of type of non-call establishment are indicated, it is known, due to its nature, that the result of any additional call set-up will be satisfactory or unsatisfactory (the end of any sending string is reached in sequence). In these cases, the particularity of CFD does not need to remain in the call. Instead of this, depending on the indicated characteristic, the base address is disconnected (the call is sent) or the base address continues to call until they answer or until the source address is disconnected (a non-sending treatment is applied call) . As an example, if we point out the particularity of Intercept Service (IS), it is known that the result of the call establishment will be unsatisfactory. Therefore, the call is not sent and the base address continues to call. On the contrary, if the particularity of the Meeting Conference (MMC) is pointed out, it is known that the result of the call establishment will be satisfactory. Therefore, the base address is disconnected and the particularity of MMC is invoked (the peculiarity of CFD does not remain in the call). In these cases, the advance movement is not in effect until the result of the establishment of the satisfactory or unsatisfactory call is actually received. But it is inevitable until it is known that the result of the call establishment is satisfactory or unsatisfactory. Figure 8 illustrates a call scenario where a non-call establishment type particularity is pointed out. The 800 home address calls the base 802 address. The base address 802 has a CFD to the remote station 804. The remote 804 address is busy and has an active call waiting characteristic (CAW). The base address 802 ceases to count within the specified amount of time, a CFD time extension occurs and a call set-up is attempted to the remote 804 address. An event of the signaling feature system is received which indicates that the CAW feature is active in the remote address. The CFD characteristic releases the remote address and falls from the call since CAW is a non-call establishment type feature. The CAW feature is retained. The CAW feature provides the call waiting tone to the remote 804 address and provides the ring tone to the originating address 800 and takes the call. PICTURES A and B are tables illustrating the signals exchanged between the functional blocks of Figure 2 when taking actions using the Advanced Send Not Answer software, in the preferred embodiment of the invention.

TABLE A SIGNAL ORIGIN AND DESTINY Expires the TrafficMgr- Synchronizer »FeatureMgr CFD Retain FeatureMgr? FeatureCFD Feature InteractionMgr- "> FeatureOther FeatureCFD FeatureMgr Retained FeatureOther-UnteraactionMgr Read the FeatureCFD? -FeatureDB Feature of the FeatureOthert Feature Feature FeatureDB? Feature FeatureCFD of FeatureOther Feature Release FeatureCFD FeatureMgr Feature FeatureOther-linteractionMgr Feature FeatureMgr- »FeatureCFD Released InteractionMgr-» FeatureOther Write the FeatureCFD? FeatureMgr Data FeatureOther- »InteractionMgr Established FeatureMgr -» - TrafficMgr InteractionMgr-FeatureMgr Create Calls FeatureCFD- > FeatureMgr FeatureOthert Set FeatureMgr- »TrafficMgr New Call Connect Traf ficMgr- > Connect ionMgr Connected ConnectionMgr- > TraficMgr Connection TrafficMgr- > FeatureMgr FeatureMgr FeatureCFD Call FeatureOther Feature (Satisfactory) Subsystem Occupied / TraficMgr ~ »Congested FeatureMgr Establishment FeatureMgr- > Call FeatureCFD (fail) FeatureOther Feature TraficMgr ~ FeatureMgr Designated BOX B SIGNAL ORIGIN AND DESTINY Divided FeatureCFD- »FeatureMgr Interrupt FeatureMgr- > Connect ionMgr Connection Connection ConnectionMgr-FeatureMgr Interrupted Divided R FeatureMgr? FeatureCFD Free FeatureCFD-FeatureMgr Released FeatureMgr? FeatureCFD Release FeatureMgr-ConnectionMgr Released ConnectionMgr- FeatureMgr Join FeatureCFD? FeatureMgr United FeatureMgr? FeatureCFD Delivery FeatureCFD - '«- • FeatureMgr (feature, simultaneous FeatureOther) Delivery FeatureCFD- »FeatureMgr (Feature, FeatureOtherT chained) Retain Logic FeatureMgr-UnteractionMgr Interaction Retained Logic InteractionMgr- > FeatureMgr Referring first to CHART A, the CFDTimerExpires signal is sent by TrafficMgr 202 to inform FeatureMgr 306 that the call limit of the CFD base address has been reached and that CFD should be invoked. The Retain Feature signal is sent via FeatureMgr 206 or InteractionMgr 208 to give commands to FeatureCFD 210 or FeatureOther 212 to handle a call. The Withheld Feature signal is sent to FeatureMgr 206 via FeatureCFD 210 or Feature 212 to announce that the feature has been retained. The signal to read the data feature is sent via FeatureCFD 210 or FeatureOther 212 to FeatureDB 214 in order to read the data connected with a feature of the subscriber. The data characteristic signal is sent in response to the signal to read the data characteristic and contains the subscriber data. The Feature Release signal is sent via FeatureCFD 210 or FeatureOther 212 to FeatureMgr 308 to indicate that they no longer need to handle a call. The Released Feature signal is sent from FeatureMgr 206 to Feature CFD 210 or FeatureOther 212 to announce that the feature has been released. The Set the Set Data signal is sent via Feature 208 or FeatureOther 210 to FeatureMgr 206, or FeatureOther to InteractionMgr 208 to write the Call Set-up data to TrafficMgr 202. FeatureMgr 206 or InteractionMgr 208 transmits the data to TrafficMgr 202 with the Write the established data. A Create Call signal is sent from featureCFD 210 or FeatureOther 212 to FeatureMgr 306 in order for a call to be established between the two addresses. The Set New Call signal is sent from FeatureMgr 306 to TrafficMgr 202 in order to establish a call ordered by a feature. The connect signal is used by TrafficMgr 302 to order ConnectionMgr 204 to connect two addresses specified in the Set New Call signal, if the address to which it has been called is not busy, it does not have a Set type characteristics. Call, or a congestion does not prevent the connection. The Connected signal is sent from ConnectionMgr 302 to TrafficMgr 304 to make it known that the connection has been made. After making a connection, the calling party hears the ringing tone and the address to which it has been called is ringing or calling. If the called address is disconnected after the connection, a conversation connection is made. The connection is sent from TrafficMgr 302 to FeatureMgr 306 to announce that the signal has been activated Establish New Call The Set Call signal (satisfactory) is sent from FectureMgr 306 to FeatureCFD 210 or FeatureOther 212 to Indicate that the Create Call signal has been successfully triggered. The Occupied / Congested Subsystem signal is sent by the TrafficMgr 202 to indicate to FeatureMgr 206 that the attempt to establish the call is towards a busy subscriber, or, that the line is congested. The Call Set-up (failure) signal is sent via FeatureMgr 206 to FeatureCFD or FeatureOther 214 after receiving a Busy / Congested Subsystem signal to indicate a successful Call Set-up. The Signal Characterized signal is sent via TraficMgr 202 to FeatureM? Rr 206 to indicate that the Call Set attempt is toward an address with an active characteristic. The Signal Characteristic signal indicates whether the indicated feature is a type of Call Set-up or a characteristic or type of Call Set-up. Referring now to TABLE B, the Division signal is sent from the CFD Feature to order that the connection between the two subscribers be interrupted. After the connection between the two subscribers is interrupted, each subscriber will continue to hear any of the tones that the system was providing to them during the connection (eg, a calling party will continue to hear the call and address to whom it's called will continue to be called). If the called party's address is picked up after the connection is interrupted, a disk tone is provided to that address. The Interrupt Connection signal is sent to ConnectionMgr 204 via FeatureMgr 206 to implement the Division signal. The Interrupted Connection is sent from ConnectionMgr 204 to FeatureMgr 206 to announce that a connection has been interrupted. The R Division is sent from FeatureCFD 206 to FeatureCFD to announce that the Division signal has been acted upon. The Free signal is sent from FeatureCFD 210 to FeatureMgr 206 in order to release the base address when it has its conversation path disconnected as a result of a split signal and is still calling. A Released signal is sent via FeatureMgr 206 to FeatureCFD to make it known that the Free signal has been triggered. The Release signal is sent from FeatureMgr 206 to ConnectionMgr 204 in order to implement a Free signal. The released signal is sent via ConnectionMgr to announce that the release signal has been acted upon. The Join signal is sent through FeatureCFD 210 to instruct FeatureMgr 206 to reconnect the two addresses that have been disconnected by the Division signal. The Unite signal is sent via FeatureMgr 206 to FeatureCFD 210 to report that the Join signal has been triggered. The Delivery signal (characteristic, simultaneous) is used by FeatureCFD 210 or FeatureOther 212 to instruct FeatureMgr 206 to deliver a call to another feature. In a simultaneous delivery, the feature that orders the delivery in the call remains and receives the subsequent results of the Call Set-up. The delivery signal (chained feature) is used by FeatureCFD 210 or FeatureOther 212 to instruct FeatureMgr 206 to deliver a call to another feature. In a delivery chained to the characteristic that orders the delivery, it falls from the call. The Retain Logical Interaction signal is sent by FeatureMgr 206 to order InteractionMgr 208 to handle a simultaneous delivery. The retained Logic signal is sent by InteractionMgr 208 to make it known that the signal Retain the Interaction Logic has been triggered. Figure 9 is a flow chart illustrating the steps followed by the CFD Advance Software when a call addressed to a base address with the CFD activated is received in the system. In step 1000, the call is received in the system, a connection is made from the source address to the base address and the CFD synchronizer is started. In step 1002, the CFD synchronizer expires and the CFD software is invoked. Referring temporarily to Figure 10A, a signal flow diagram illustrating the exchange of the signals between the functional blocks of Figure 2 is displayed as the CFD Advance software is invoked. The TrafficMgr 202 sends an Expiration signal from the CFD Synchronizer to featureMgr 206 to indicate the expiration of the CFD synchronizer. The FeatureMgr 206 then invokes the CFD Advance Feature by sending a Hold Feature signal to the FeatureCFD 210. FeatureCFD 210 returns to the Featured Feature signal back to FeatureMgr 206 to make the retention known. Referring again to Figure 9, from Step 1002, the software of the CFD feature moves to Step 1004 and establishes a call to the remote address for CFD. This Call Set-up is illustrated in greater detail in Figure 10B which is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 during the Early Call Establishment of the CFD Feature of Step 1004 To establish a call, FeatureCFD 210 sends a ReadFeatData to FeatureDB 214 to remove the Feature from the Data in the CFD subscriber. The data characteristic is then sent to FeatureCFD 210 in response in a Data Feature message. The FeatureCFD 210 then divides the base address and source address by sending a split signal to FeatureMgr 206. FeatureMgr 206 sends a Stop Interrupt signal to ConnectionMgr 204 to instruct ConnectionMgr 204 to disconnect the connection between the address base and the address of origin. When the connection is broken, the ConnectionMgr 204 returns to an Interrupted Connection message to FeatureMgr 206. The featureMgr 206 then informs FeatureCFD 210 that the division has been completed by sending a SplitR to FeatureCFD 210. Once the base address has been split and the address of origin, or base address continues ringing or calling until the call is terminated. The termination of the call and the reconnection will be described further. If the base address is disconnected after the division is completed and before reconnection or termination of the call, a disk tone is provided to the base address. The base address can originate a call during this time. The FeatureCFD 210 now writes the feature of the data in FeatureMgr 206 with a Write the Established Data signal. The Set Data Write signal is transmitted by FeatureMgr 206 to TraficMgr 202 and FeatureMgr 206 sends a written data recognition to FeatureCFD 210. The FeatureCFD 210 now sends a Call to FeatureMgr 206 signal, and FeatureMgr 206 establishes the call by sending a Set New Call signal to TrafficMgr 202. The Call Establishment will result in one of the three messages being returned to FeatureCFD 210. In the first scenario for Call Set-up, the remote subscriber is idle without a feature of completion. Figure 10C is a signal flow diagram illustrating the exchange of the signals between the functional blocks of Figure 2 when the remote subscriber is idle without a termination feature. Upon determining that the remote subscriber is idle, the TrafficMgr 202 sends a ConnectionMgr 204 Connection signal to create a connection between the base address and the remote address. The ConnectionMgr 204 recognizes the connection by returning a signal Connected to the TrafficMgr 202. The TrafficMgr 202 then sends a Connect to FeatureMgr 206 signal which in turn informs FeatureCFD of the establishment result with a Call Set-up Signal (Satisfactory). In the second scenario for the Call Establishment, the remote subscriber is busy or congested and has no active termination feature. Figure 10D is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the remote subscriber is busy or congested. Upon determining that the remote subscriber is busy or congested with no active feature, the TrafficMgr 202 sends a signal from the Busy / Congested Subsystem to FeatureMgr 206. The FeatureMgr 206 then sends a Call Set-up (fail) signal to FeatureCFD 210 to indicate a unsatisfactory call establishment. In the third possible scenario for a Call Establishment, the remote address has a particularity of active termination. Figure 10E is a signal flow diagram illustrating the exchange of the signals between the functional blocks of Figure 2 when the remote address has an active termination feature. If the remote address has an active termination feature, the TrafficMgr 202 informs FeatureMgr 206 by sending a FeatureMgr 206 signal to FeatureMgr 206. FeatureMgr 206 then returns the results of the Call Establishment to FeatureCFD 210 with a Call Set-up signal (Feature) . Referring again to Figure 9, after Call Establishment to the remote address, the software of the CFD feature is moved to Step 1006 where the result of the Call Set-up is determined and an appropriate action is initiated. If FeatureCFD 210 has received a Call Set (Satisfactory) signal, the CFD software moves from Step 1006 to Step 1008. In Step 1008 the software continues calling the remote address initiated during the Call Set-up. From Step 1008 the software moves to Step 1010 and terminates the call of the base address. The process then ends in Step 1012. Referring temporarily to Figure 10F, a signal flow diagram illustrating the signals between the functional blocks of Figure 2 is shown when the result of the Call Set is satisfactory. Upon receipt of the Call Set-up signal (satisfactory) the FeatureCFD 210 sends a free signal to FeatureMgr 206 instructing it to release the base address. The call from the remote address will start automatically when the connection to the remote address is made. The FeatureMgr 206 sends a Release Signal to ConnectionMgr 202 to release the base address. The base is released and the call ends. The ConnectionMgr 202 returns a released signal to FeatureMgr 206 to inform FeatureMgr 206 of the release. The FeatureMgr 206, in turn, informs FeatureCFD 210 that the base address has been released by sending a Released Signal to FeatureCFD 210. The FeatureCFD 210 then sends a Release Feature signal to FeatureMgr 206 requesting release. FeatureMgr 206 recognizes the release of the CFD characteristic by sending a Feature Released signal to FeatureCFD 210. The process is now terminated. Referring again to Figure 9, if CFCD 210 has received a Call Establishment (Fail) signal in Step 1006, the CFD software moves from Step 1006 to Step 1014. In Step 1014 the software connects new the source and base address while still calling the base address. If the base address is dropped when a new connection is attempted, a voice announcement is provided to the source address saying that the call can not be completed. The process then terminates at Step 1016. Figure 10G is a signal flow diagram illustrating the signal exchange between the functional blocks of Figure 2 when the result of the Call Set is unsatisfactory. Upon receipt of the Call Set-up signal (failure) the FeatureCFD 210 sends a Join signal to FeatureMgr 206. FeatureMgr 206 then reconnects the source and base address by sending a Connection signal to ConnectionMgr 202. The re-connection is recognized by ConnectionMgr 202 by sending a signal connected to FeatureMgr 206 and the FeatureMgr 206, in turn, by sending a signal attached to FeatureCFD 210. FeatureCFD 210 then sends a signal of Release Feature to FeatureMgr 206 requesting release. FeatureMgr recognizes the release of the CFCD feature by sending a Released Feature Signal to CFCD 210. The process is now terminated. Referring again to Figure 9, if CFCD 210 has received a Call Set-up signal (Feature), the CFCD software moves from Step 1006 to Step 1018 to determine whether a feature of Call Settlement or Call Set-up type was noted. If it is determined, in Step 1018, that the indicated feature is a No Call Establishment type feature, the software moves to Step 1020. In Step 1020 the CFD software disconnects the base address. From step 1020, the software moves to step 1022. In 1022, the software invokes the designated characteristic that falls from the call. The software then moves to Step 1028. In step 1028, the CFD Advanced process ends as the signaling feature continues the call. Figure 10H is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the result of the establishment is a designated feature, and, the signaling feature is a non-call establishment type feature. . The FeatureCFD 210 sends a Free signal to FeatureMgr 206 to initiate the release of the base address. The FeatureMgr 206 then sends a Release signal to ConnectionMgr 202. The CoonectionMgr 202 releases the base address and the base address stops calling. ConnectionMgr 302 then recognizes the release of the base address to FeatureMgr 206 by returning a released signal to FeatureMgr 206. FeatureMgr 206, in turn, informs FeatureCFD of the release by sending a released signal to FeatureCFD 210. The FeatureCFD now delivers the call to the designated characteristic of the type of No Call Establishment by sending a Delivery signal (feature, chained) to FeatureMgr 206. After delivery, FeatureCFD requests to be released by sending a Release Feature signal to FeatureMgr 206. FeatureMgr 206 releases FeatureCFD and sends a Free Feature signal in acknowledgment. The FeatureMgr then sends a Hold Feature signal to FeatureOther 212. The FeatureOther 212 will be retained and will take over the call as the CFCD process ends. Referring again to Figure 9, if the designated feature is a Call Set type feature, the software moves to Step 1024. In 1024 the software invokes a feature that has been signaled. The invoked feature then continues to the Call Set-up at 1026. Figure 101 is a signal flow diagram illustrating the signal exchange between the functional blocks of Figure 2 when the result of the Call Set-up is a designated feature and characteristic. indicated is a Call Set type feature. After receiving the Call Set-up signal (Feature) the FeatureCFD 210 instructs the FeatureMgr 206 with a Delivery signal (Feature, simultaneous), to deliver the call setup to the FeatureOther 212. The FeatureMgr 206 then retains the logic of Interaction by sending a signal to Retain the Interaction Logic to InteractionMgr 208. InteractionMgr 208 sends an acknowledgment that the logic has been retained by sending a Retentive Logic signal to FeatureMgr 206. The InteractionMgr 208 then retains the other signaled characteristic by sending a Feature signal Retained to FeatureOther 212. FeatureOther 212 responds with a Hold Feature signal to recognize hold. The FeatureOther 212 retrieves the necessary data by sending a signal to read the Data Feature to FeatureDB 214. The FeatureDB 214 sends the Data Feature response. Feature 212 then writes the Settlement data in InteractionMgr 208 with a message to Enter the Set Data. The established data is sent from InteractionMgr 208 to FeatureMgr 206 with a message of Enter the Established Data and then TrafficMgr 202 is transmitted from FeatureMgr 206 with a Write Set Data message. FeatureMgr 206 recognizes that the Established Data is written by sending a Written Data signal to the InteractionMgr 208 and InteractionMgr 208 transmits the Written Data signal to the FeatureOther 212. The FeatureOther 212 then sends a signal to Create a Call to the InteractionMgr 210 to initiate the Establishment of Call. The InteractionMgr 210 transmits the Create Call to FeatureMgr 206 signal. When receiving the Create a Call signal, FeatureMgr 206 establishes the call to the terminating subscriber by sending a Set New Call signal to the TrafficMgr 202. During the Call Establishment of the Pass 1026 (Figure 9), the TrafficMgr 202 will return one of the three messages to the FeatureMgr 206, depending on the results of the establishment of the new call by another designated feature. Figure 10J is a signal flow diagram illustrating the flow of the signals between the functional blocks of Figure 2 when the establishment by the indicated feature is for a termination subscriber that is idle without active feature. The TrafficMgr 202 will send a Connection Signal to ConnectionMgr 204. The ConnectionMgr 204 recognizes the connection by sending an acknowledgment signal from Connected to the TrafficMgr 202 in response. The termination subscriber is now connected to the originating subscriber and is calling. The trafficMgr 202 sends a Connect to FeatureMgr 206 signal to indicate that a connection was made. The FeatureMgr 206 sends a Call Set (Satisfactory) signal to the InteractionMgr 208. The Call Set (Satisfactory) signal is sent through the InteractionMgr 208 to the FeatureOhter 212. Upon receiving the Call Set-up (Satisfactory) message, the FeatureOther 212 sends a Feature Release request to the InteractionMgr 208. The InteractionMgr 208 releases the feature and sends a Feature Release signal to the FeatureOther 212. The InteractionMgr 208 then sends a Call Set-up (Satisfactory) message to the FeatureCFD 210 for indicate a satisfactory call establishment. InteractionMgr 208 also requests the release of the Interaction Logic by sending an Interaction Logic Release signal to FeatureMgr 206. FeatureMgr 206 then informs InteractionMgr 208 of the release of interaction logic by sending a Logic signal released to InteractionMgr. 208 Figure 10K is a signal flow diagram illustrating the flow of the signals between the functional blocks of Figure 2 when the establishment by the indicated feature is towards a busy or congested subscriber with no particular active termination. The TrafficMgr 202 will send a Busy / Congested Subsystem signal to the FeatureMgr 206. The FeatureMgr 206 then sends a Call Set-up (Fail) signal to the InteractionMgr 208. In turn, the InteractionMgr 208 sends a Call Set-up signal (Fault). ) to FeatureOther 212. Upon receipt of the Call Set-up (Fail) signal, the FeatureOther 212 sends a Send Tone signal to the InteractionMgr 208. The FeatureOther 212 then requests to be released by sending a Release Feature signal to the InteractionMgr 208. InteractionMgr 208 recognizes the release of another feature by sending a Feature Released signal to the FeatureOther 212. The InteractionMgr 208 then returns the Call Set results by sending a Call Set-up (Fail) signal to the FeatureCFD 210 to indicate a call set-up. unsatisfactory. The InteractionMgr 208 also sends an Interaction Logic Release signal to the FeatureMgr 206 to request the release of the interaction logic. The FeatureMgr 206 then informs InteractionMMgr 208 of the release of the interaction logic by sending a Freed Logic Signal to the InteractionMgr 208. Figure 10L is a signal flow diagram illustrating the flow of the signals between the functional blocks of the Figure 2 when the result of the Call Establishment by the indicated characteristic is a second indicated characteristic. The TrafficMgr 202 sends a Feature Signal signal to the FeatureMgr 206. The FeatureMgr 206 then informs the InteractionMgr 208 of the result with a Call Set-up signal (characteristic). The InteractionMgr 208 returns to the Call Set-up (feature) to the FeatureOther 212 and the FeatureOther 212 delivers the call to the designated feature. Referring again to Figure 9, since Step 1026, the Software returns to Step 1006. At 1006 the Call Establishment results are determined. If the FeatureCFD has received a Call Set-up message (satisfactory) indicating a successful call set-up result using the feature set forth in Step 1026, the CFD software moves to Step 1008. In Step 1008, the Software continues to call to the termination address initiated during the Call Set-up. From Step 1008 the software moves to Step 1010 and then terminates the base address call. The process then ends in Step 1012. Figure 10M shows the exchange of signals between the blocks of Figure 2 when the Call Establishment by the indicated feature has a satisfactory result. The call from the remote address will have started automatically when the connection to the remote address was made. After the interaction logic is released, the FeatureCFD 210 sends a Free call to FeatureMgr 206 to initiate the termination of the call in the base address. The FeatureMgr 206 instructs the ConnectionMgr 204 to disconnect the base address by sending a Release signal to the ConnectionMgr 204. When the base address has been disconnected, the ConnectionMgr 204 returns a Released signal to the FeatureMgr 206. The base address now stops to call. FeatureMgr 206 recognizes that the base address has been released by sending a Released signal to FeatureCFD 212. FeatureCFD 210 then requests to be released by sending a signal to deliberate the feature to FeatureMgr 206. FeatureMgr 206 recognizes the release by returning a Feature signal Released to the FeatureCFD 210.

Referring again to Figure 9, if FeatureCFD 210 has received a Call Set-up (Fail) signal, indicating an unsatisfactory call set-up result using the feature set forth in Step 1026, the CFD software moves from the step 1006 to Step 1014. In step 1014, the software continues to call the base station and reconnects the base and origin address. The software then moves to Step 1016, where the process ends. Figure ION shows the exchange of signals between the blocks of Figure 2 when the Call Establishment by the indicated feature has an unsatisfactory result. After the interaction logic is released, the FeatureCFD 210 initiates the re-connection of the source and base addresses by sending a Join signal to the FeatureMgr 106. The FeatureMgr 206 instructs the ConnectionMgr 202 to reconnect the source addresses of the base by sending a Connection signal to the ConnectionMgr 202. The CoonectionMgr 202 recognizes the connection to a connected signal sent back to the FeatureMgr 206. The FeatureMgr 206 then sends a signal attached to the FeatureCFD 210 to inform the FeatureCFD 210 that the connection between The source and base addresses have been established. The FeatureCFD 210 requests to be released by sending a FeatureCreated FeatureMgr 206 signal. The FeatureMgr 206 releases the feature and sends a released Feature signal back to FeatureCFD 210. The process has now finished. Referring again to Figure 9, if the FeatureOther 212 has received a Call Set-up signal (Feature), indicating a second feature designated as the result of the Call Set-up in Step 1026 by the first feature noted, the software will be will move from Step 1006 to Step 1018. In step 1024, the second signaling characteristic is invoked as the first indicated feature delivers the call to the second characteristic. The invoked feature continues the call in Step 1026 and returns to Step 1006 as the first feature. The CFD is not aware of this delivery and is still waiting for the result of the call establishment to see if it is satisfactory or unsatisfactory. The process continues as before, until a result of the Call Set-up at Step 1006 or Step 1018 is reached leading to the end of the process. Figure 10O is a signal flow diagram illustrating the exchange of signals between the functional blocks of Figure 2 when the Call Establishment by the designated feature is a second signalized characteristic that is a call establishment type feature. Feature 216 sends a Delivery (characteristic, chained) signal to InteractionMgr 208. FeatureOther 216 then requests to be released by sending a feature release signal to InteractionMgr 208. Upon release of the feature, InteractionMgr 208 sends a Release Characteristic signal to the FeatureOther 216 in recognition. The InteractionMgr then sends a Feature Hold signal to the FeatureOther 216. The FeatureOther 216 is now the second feature noted. The FeatureOther 216 responds to the InteractionMgr 208 with a Feature Hold signal to recognize feature retention. The process then continues as the FeatureOther 212 establishes a call. It is believed that the operation and construction of the present invention will be apparent from the foregoing description and even when the method and apparatus shown and described herein have been characterized as being preferred, obvious changes and modifications can be made therein without deviating of the spirit and scope of the invention as defined in the following claims.

Claims (32)

R E I V I N D I C A C I O N E S:

1. A method of sending a call in a communication system in which a plurality of subscriber stations are interconnected through a switch for communication with each other, the method comprises the steps of: receiving a call from a first one on the switch; plurality station of subscriber stations, the call is initially directed to a second station of the plurality of subscriber stations; establish a connection between the first station and the second station; put a warning on the second station; provide a ring tone to the first station; disconnect the connection between the first station and the second station; carry out a call sending facility to a third station of the plurality of subscriber stations; determine a result of the call sending establishment; and sending the call in accordance with the result of the call sending facility, wherein the sending step further comprises the step of re-establishing the connection between the first station and the second station in response to a determination that the result of the Call sending establishment was unsatisfactory.

The method according to claim 1, wherein the sending step includes the step of terminating the overwarning provided to the second station in response to a determination that the call sending establishment was unsatisfactory.

3. The method according to claim 1, wherein a successful call setup result includes an indication that the third station is idle.

4. The method according to claim 1, wherein the result of the unsatisfactory call setup establishes an indication that the third station is busy.

The method according to claim 1, wherein an unsatisfactory call set-up result includes an indication that the third station is not able to be reached due to congested lines.

6. The method according to claim 1, wherein the sending step includes the step of establishing a connection between the first station and the third station in response to a determination that the call sending establishment was successful.

The method according to claim 6, wherein the step of establishing a connection between the first station and the third station includes the step of overdrafting the third station.

The method according to claim 1, wherein a subscriber's service feature is associated with the third station and the sending step includes the step of invoking the subscriber's service feature in response to a determination that the result of the call sending establishment signals the service characteristic of the subscriber of the third station.

The method - according to claim 8, wherein the step of invoking the service feature of the subscriber includes the steps of: carrying out a second call sending facility to a fourth station; determine a result of the second call sending facility; and send the call in accordance with the second call delivery establishment result.

The method according to claim 9, wherein the step of sending the call in accordance with the second result of the call sending establishment includes the step of terminating the overdraft of the second station in response to a determination of that the second call sending facility was satisfactory.

The method according to claim 9, wherein the step of sending the call in accordance with the second call set-up result includes the step of re-establishing the connection between the first station and the second station in response to a determination that the second call sending facility was unsatisfactory.

12. The method according to claim 9, wherein a successful result of the second call sending facility includes an indication that the fourth station is idle.

The method according to claim 9, wherein an unsatisfactory result of the second call sending facility includes an indication that the fourth station is busy.

The method according to claim 9, wherein an unsatisfactory result of the second call sending facility includes an indication that the fourth station can not be reached due to congested lines.

The method according to claim 9, wherein the step of sending the call in accordance with the second result of establishing the call includes the step of establishing a connection between the first station and the fourth station.

The method according to claim 15, wherein the step of establishing a connection between the first station and the fourth station includes the step of overdrafting the fourth station.

17. An apparatus for sending a call in a communication system wherein the plurality of stations of the subscriber are interconnected through a switch to communicate with each other, the apparatus comprising: means for receiving a call from a switch on the switch; first station of the plurality of subscriber stations, the call being initially directed to the second station of the plurality of subscriber stations; a means to establish a connection between the first station and the second station; a means for placing a warning on the second station; means for providing a ring tone to the first station; means for disconnecting the connection between the first station and the second station; means for carrying out a call sending establishment to a third station of the plurality of subscriber stations; means for determining a result of the call sending facility; and means for sending the call in accordance with the result of the call sending facility, wherein the means for sending further comprises means for re-establishing the connection between the first station and the second station in response to a determination that the result of the call delivery establishment was unsatisfactory.

The apparatus according to claim 17, wherein the means for sending includes means for terminating the overwarning provided to the second station in response to the determination that the result of the call sending establishment was satisfactory.

19. The apparatus according to claim 17, wherein a successful result of the call sending establishment includes an indication that the third station is idle.

The apparatus according to claim 17, wherein an unsatisfactory result of the call sending establishment includes an indication that the third station is busy.

The apparatus according to claim 17, wherein an unsatisfactory result of the call sending facility includes an indication that the third station is not able to be reached due to congested lines.

22. The apparatus according to claim 17, wherein the means for sending includes means for establishing a connection between the first station and the third station in response to a determination that the call set-up was successful.

23. The apparatus according to claim 22, wherein the means for establishing a connection between the first station and the third station includes a means for overdraying the third station.

24. The apparatus according to claim 17, wherein a particularity of the subscriber's service is associated with the third station and the means for sending includes a means for invoking the subscriber's particularity of service in response to a determination that the The result of establishing the call sending signals the particularity of service of the subscriber of the third station.

25. The apparatus according to claim 24, wherein the means for invoking the service feature of the subscriber includes: means for carrying out a second call sending facility to a fourth station, a means for determining a result of the second call sending facility; and a means for sending the call in accordance with the second result of the establishment of the call delivery.

26. The apparatus according to claim 25, wherein the means for sending the call in accordance with the second call set-up result includes a means for terminating the overdraft setting provided to the second station in response to a determination that the second call sending facility was satisfactory.

27. The apparatus according to claim 25, wherein the means for sending the call in accordance with the second call delivery establishment result includes a means for re-establishing the connection between the first station and the second station, in response to a determination that the second call sending facility was unsatisfactory.

28. The apparatus according to claim 25, wherein a successful result of the call sending establishment includes an indication that the fourth station is idle.

29. The apparatus according to claim 25, wherein a second unsatisfactory result of the call sending includes an indication that the fourth station is busy.

30. The apparatus according to claim 25, wherein a second unsatisfactory call sending result includes an indication that the fourth station is not able to be reached due to congested lines.

The apparatus according to claim 25, wherein the means for sending the call in accordance with the second call delivery establishment result includes a means for establishing a connection between the first station and the fourth station.

32. The apparatus according to claim 31, wherein the means for establishing a connection between the first station and the fourth station includes a means for warning the fourth station.