Local exchange subscriber line conferencing method

LOCAL EXCHANGE SUBSCRIBER LINE CONFERENCING

METHOD

BACKGROUND OF THE INVENTION

00041. Field of the Invention. The present invention pertains to call conferencing and, in particular, to reservation-less instant conferencing as it relates to business and residential local exchange telecommunication service subscribers.

00052. Statement of the Problem. A need exists for Regional Bell Operating Companies (RBOCs), wireless carriers, and other Local Exchange Carriers (LECs) to provide simple conferencing services to residential and small office telephone service subscribers. Practicality of the conferencing service for local exchange subscriber line users is dependent upon extreme ease of use through simple, easy to remember access methods that utilize conferencing automation to the maximum practical extent.

0006U.S. Patent 6,181 ,786 B1 , owned by the assignee of the present invention, sets forth a method and apparatus for on-demand teleconferencing. This represents a prior call conferencing approach eliminating prior scheduling and operator interaction in setting up a conference call. This prior art approach uses, for example, the

0007Signaling System No. 7 (SS7) out-of-band signaling to dynamically route incoming conference calls to bridges in a conferencing system having available resources. In operation, a subscriber to the conferencing service is given a telephone number for connecting to the conferencing system along with a system pass code and a maximum conference size at the time he or she signs up for the service. In order to have a conference, the subscriber distributes his or her access telephone number to the conference participants along with an access code and optional conference security (or PIN) code of the subscriber's choosing. The processing of the conference call, billing, etc. is handled at the conferencing system. This mechanism is considered overly complex for application to local exchange subscriber line users because of the need to remember these access telephone numbers, access codes, and PIN codes. Current conferencing service available to local exchange subscriber line users includes three-way conferencing that is typically accessed through a hook-flash mechanism that provides the user with a second dial tone for use in connecting a third party to an existing two-party telephone call. A need exists to extend the capabilities of this type of service through significant simplification of access mechanism as well as through availability of greater than the three conventional call legs simultaneously involved in a conference call event.

SUMMARY OF INVENTION

0009The present invention solves the aforestated problem and meets the needs stated therein. The local exchange subscriber line conferencing of the present invention, from the perspective of the conferencing system, is characterized by reservation-less instant conferencing as it relates to business and residential telecommunication subscribers. From the perspective of the user, the service of the present invention is characterized by a simplified access method for conferencing services that takes advantage of telecommunication network capabilities to eliminate many of the current art complexities involved with accessing such service.

0010A local exchange subscriber line conferencing system and method is set forth herein. A series of input signals from the phone of a subscriber (such as a DTMF sequence of key inputs starting with a star key input) initiate the conference call in the LEC. The conference call is then set up in a bridge and the phone of the subscriber is connected to the bridge. All subsequent callers to the subscriber's phone number at the LEC are routed based on the enabling of a termination attempt trigger and connected to the conference call at the bridge. When the conference call ends, the subscriber's phone is returned to normal service so as to receive all incoming calls made to its phone number.

BRIEF DESCRIPTION OF THE DRAWINGS

0012Figure 1 sets forth one embodiment of the telecommunication network incorporating the conferencing service of the present invention. Figure 2 is the network of Figure 1 setting forth the method whereby a subscriber sets up a local exchange subscriber line conference call.

0013Figure 3 is the network of Figure 1 setting forth the method whereby a subsequent caller joins the subscriber's conference call. Figure 4 is the network of Figure 1 setting forth the method whereby the conference ends.

0014Figure 5 is the network of Figure 1 setting forth the method whereby a subscriber locks and unlocks the conference.

0015Figure 6 is a flow chart illustrating the method of the present invention for a subscriber setting up a conference call and for subsequent callers to join the conference call.

0016Figure 7 is another embodiment of the conferencing service of the present invention with the telecommunication network having a bridge located behind each LEC switch. Figure 8 is another embodiment of the conferencing service of the present invention with the telecommunication network having all the bridges behind a switch.

0017Figure 9 is another embodiment of the conferencing service of the present invention with the telecommunication network without using the SS7 network. DETAILED DESCRIPTION OF THE INVENTION

00181. Overview.

0019The conferencing service of the present invention enables

0020Regional Bell Operating Companies (RBOCs), Wireless Carriers, and other Local Exchange Carriers (LECs) to provide simple conferencing to residential and small office telephone service subscribers. The

0021present invention, in one embodiment, uses the telephone " " (star) key to initiate a conference call and like other star services, conferencing is activated by selecting the " " key followed by a unique set of numbers. These are conventionally referred to as dual- tone multifrequency (DTMF) signals. Other access methods that do not use a " " key code sequence for access represent additional embodiments of this present invention. Any predetermined series of key input signals from the phone of a subscriber can be used when the subscriber requests the conference call.

0022The subscriber informs the other parties (participants) to simply call the subscriber's phone number at the time of the conference. Subsequent parties to the conference call join either by dialing the published phone number of the subscriber or by dial-out from the conference. The LEC for the subscriber then routes all subsequent callers of the subscriber's phone number to the conference at a bridge where all such subsequent callers who are participants are connected to the conference.

0023At the end of the conference, the LEC returns the subscriber's phone to normal service so that any party then calling the subscriber's phone number is rung through to the subscriber's phone. 2. Operation. a. System

0024In Figure 1 , the overview of the telecommunication network incorporating the conferencing service system 10 of the present invention is set forth. A subscriber 20 setting up the conference call is shown in communication with a central office (CO) or Mobile Switching Office (MSO) switch 30a. Likewise, subsequent callers 40a, 40b, 40c, and 40d to the conference call are shown at another CO or MSO switch 30b. In Figure 1 , the subsequent callers 40a-40d are illustrated having access to the same CO or MSO switch 30b. It is to be expressly understood that each subsequent caller 40 (such as 40a, 40b, 40c, 40d...) could be accessing a different CO (or MSO) switch in the same LEC or in different parts of the country (or world) with different LECs, RBOCs, etc. It is also to be expressly understood that while the subscriber 20 is accessing the CO switch 30a through a calling phone set 22, that the present invention 10 is not limited to such an arrangement and the subscriber 20 could be accessing a mobile switching center through a wireless carrier by using a cell phone or the like. The CO switches 30 (such as 30a, 30b, 30c, ...) are part of

0025Local Access and Transport Areas 50 (LATAs) as defined based on the AT&T Bell System break up into 161 local telephone serving areas in the United States. LEC 100 has exclusive rights to operate within a LATA 50 subject to the state Public Utility Commission (PUC) regulations. In Figure 1 , LEC 100 and conference system 110 are in the LATA 50.

0026LATA 50 shown in Figure 1 has two separate communication paths. The first path 52 is through the SS7 60 which communicates with a Conference Allocation and Control System (CACS) 70 in the conferencing system 110. An example of a commercially available

0027CACS 70 is the READIVOICE system from Voyant Technologies, Inc. LATA 50 also communicates over path 54 with the switch 30c to further communicate with the conferencing bridges 80. The conferencing bridges 80 are connected to a Switched 10/100 Base T data network 90 which is also connected over path 56 to CACS 70. An example of a commercially available conferencing bridge 80 is the INNOVOX media server also from Voyant Technologies, Inc. The

0028CACS 70 in turn is administered over a local area network 140 by an operator/administrator 120.

0029CACS 70 acts as the conferencing resource manager and contains information about subscribers and/or subscriber profiles and available bridge conferencing resources. In another embodiment the

0030CACS 70 is within the LEC's network 100 and is installed behind a switch or multiple switches 30. As shown in Figure 1 , 'dynamic' routing, using the SS7 network 60, of a conference to a bridge 80 occurs and represents one embodiment. The present invention also uses alternative embodiments such as carrier-supplied signaling methods other than the SS7 network 60 (for example TCP/IP communication mechanisms that serve the same purpose), and signaling mechanisms where the communication is with the conferencing bridge 80 rather than the CACS 70 (for example Integrated Services Digital Network Primary Rate Interface (ISDN

0031PRI). The conferencing methods set forth herein can be adapted to operate in a number of different telecommunication environments as discussed more completely in the related application filed contemporaneously herewith.

0032b. Subscriber

0033The subscriber 20 has the retail relationship with the LEC 100. The subscriber 20 receives local service from the LEC 100 and has selected to receive the conferencing service 10 of the present invention as an additional service such as conventional "call forwarding" from the LEC. The subscriber 20 interfaces, in one embodiment, with the application through a Plain Old Telephone Service (POTS) local loop phone 22. The conference is initiated by the subscriber 20 lifting the handset of the phone 22 and then entering for example '*' (i.e., pushing the "star" key) followed by a predetermined set of digits, for example "90." Any predetermined series of signals from the phone 22 such as a series of key inputs can be used. At that time, the subscriber 20 will be put into "conference mode." Conference mode means that the subscriber 20 is transferred into the conferencing system 110 and any subsequent calls to the subscriber's telephone number will be routed to the subscriber's conference on a bridge 80 assigned to the conference call where the subscriber's conference is located.

0034Optionally, prior to being routed to the conferencing bridge 80, participants 40 that call the subscriber's telephone number receive an Interactive Voice Response (IVR) message stating, for example: "The person that you have called is presently in a conference, please press

00351 to join the conference or press any other number to be directed to default busy treatment." In one embodiment, if the subscriber presses any number other than "1", the caller will be forwarded to default call treatment, which may include voicemail (if the subscriber has a voicemail account with the LEC 100), call forwarding, or a busy signal.

0036It is to be expressly understood that in the aforesaid, local loop phone 22 can be any suitable phone device, such as a telephone, a cell or wireless phone, or any other suitable communication device used to provide subscriber line communications service. Furthermore, while the "star" key is the preferred key of use due to its conventionality in the telephone industry and understanding by the public, it is to be understood that any other suitable function key signal, voice command, code input, or other stimulation mechanism could be utilized under the teachings of the present invention. As another embodiment, a special key on a wireless telephone or icon on a wireless phone or wireless computing device is activated to generate the signal series. In a further embodiment, the signal series to place the subscriber line 24 in conference mode could be stimulated through interaction with an Internet web page or other user interface in communication with the CACS 70 via the Internet. Routing of the calls to the conferencing bridge 80 is controlled by switch 30a and CACS 70. When the subscriber 20 enters the "star" key input followed by the predetermined set of digits to put his/her telephone number in conference mode in one embodiment of the invention, the switch 30a is set to direct the subscriber via a Dialed Number Trigger (DNT) to bridge 80. Subsequent callers 80a-d to the subscriber line 24 telephone number are, in one embodiment, forwarded via a Termination Attempt Trigger (TAT) to the same conference bridge 80.

0037The rights and functionality available to the subscriber 20 are configurable. The LEC 100 provides particular features to certain groups of customers. For example, the LEC 100 might want to provide "mute all" to business subscribers but not residential subscribers. Many such conference control features are specific features developed for this application of the present invention include, but are not limited to:

0038(a) Single Line Auto Termination with Keep-Alive Prompt -

0039After a configurable timer expires in switch 30a, single line conferences would play a message to the line offering the chance to stay in conference through a DTMF key response from phone 22. A response would reset the timer. No response would cause the call to be disconnected and the conference to end. This feature would handle the case of a subscriber 20 who leaves his/her phone off hook in conference. (b) Boot Last-In Participant -

0040This is a DTMF sequence (or other suitable command sequence) that would allow the subscriber 20 to key-in and remove undesired participants 40 from the conference.

0041(c) Pre-Route Lock -

0042In conventional conferencing systems, a conference lock occurs after a subsequent caller 40 has been routed to the selected bridge 80. This is discussed in greater detail later with respect to Figure 5. A message is played informing the caller 40 that the conference he/she is attempting to join is locked, followed by a disconnect. In the present invention, the call is redirected to the switch 30a to subscriber- line provisioned "busy" behavior or an IVR system 32 that would play the subsequent caller 40 a message such as: "The person that you have called is in a conference, please press two to leave them a voicemail or try back later."

0043(d) Conference Security Code -

0044In conventional conferencing systems, a Conference

0045Security Code (CSC) applies after the subscriber 20 has enabled his/her subscriber line for conferencing by entering the ' ' code. A DTMF sequence (or other suitable command sequence) would allow the subscriber 20 to provide a Conference Security Code consisting of a sequence of digits. In the service of the present invention, when a subsequent caller 40 has been routed to the selected bridge 80, a message will be played requesting that the CSC be entered. Only if the subsequent caller 40 enters the correct CSC, will the caller be placed into the conference. This feature would prevent the entrance of unwanted callers to the conference calling the subscriber's phone number, (e) Channel Mute

0046This is a DTMF (or other suitable command input) sequence that allows the subscriber 20 or any participant 40 to mute their conference input in order to prevent introduction of undesired noise into the conference. A similar DTMF sequence returns the line to an un-muted state. (f) Conference Count

0047This is a DTMF (or other suitable command input) sequence that allows the subscriber 20 or any participant 40 to receive a voice message count of the number of conference participants. (g) Subscriber Dial Out

0048This is a DTMF (or other suitable command input) sequence that allows the subscriber 20 to access a dial out line from the selected bridge 80 to call a participant 40 and add him/her to the conference. (h) Operator Request

0049This is a DTMF (or other suitable command input) sequence that would allow the subscriber 20 or any participant 40 to request an attendant or operator 120 to join and assist the conference. The above features are controlled via the conference control mechanisms found in traditional conferencing systems, such as detailed in aforementioned 786 patent.

0050c. Routing flow

0051In Figure 2, operation of the conferencing system 110 of the present invention for one embodiment in setting up a conference call is set forth. (a) Subscriber *90 Dialing

0052The following "numbers" identify the sequence flow of one embodiment which is illustrated by the numbered arrows in Figure 2. This is one method of the present invention by which a subscriber 20 initiates a conference call:

00531. The subscriber 20 picks up the handset of the phone 22.

00542. The subscriber 20 dials (for example) *90, which triggers a dialed number trigger (DNT) in the local switch 30a.

00553. The CO switch 30a responds to the dialed number trigger (DNT) by sending a Transactional Capabilities

0056Application Part (TCAP) query message to the CACS 70 via the SS7 Network 60 from LATA 50. The following information is contained in the TCAP message: i. Message Type = Conversation With Permission ii. Component Type = Invoke iii. Operation = Connectivity Control iv. Parameters = Called Number (i.e., number dialed by the subscriber, in this example, *90), Calling Number (i.e., subscriber 20 phone number)

0057This TCAP message communicates to the CACS 70 that subscriber 20 of the conferencing service 10 wishes to enable the line for conferencing. The subscriber's phone number is included in the "Calling Number" parameter. The number that the subscriber dialed ("*90" in this example) is contained in the "Called Number" parameter. In another embodiment a Private Hidden Forwarding Number (PHFN) is used which terminates in a selected bridge 80 such as bridge 80a.

00584. In one embodiment, the CACS 70 uses the Calling Number contained in the TCAP message to validate the subscriber and determine the profile of the conference (which may include enabled conferencing features and maximum conference size). In another embodiment, the CACS 70 uses the Calling Number to validate the subscriber and the Called Number to determine the conference profile. In yet another embodiment, the switch 30a may perform all subscription validation and the Called Number and/or Calling Number may be used by the CACS 70 to determine conference profile. The subscriber profile information is stored in memory in

0059CACS 70. In all embodiments, based on the stored conference profile, the CACS 70 will conventionally determine which bridge 80 (if there are multiple bridges such as, for example, bridges 80a and 80b) shall host the conference based on resource availability.

00605. Assuming that the caller 20 is a valid subscriber, the CACS 70 sends a TCAP message through the SS7 network 60 to the switch 30a in LATA 50 instructing it to toggle the subscriber's Termination Attempt Trigger (TAT) to "enabled". TAT is conventional, but the present invention is making a new use of it for conferencing under the steps of the present invention.

00616. Switch 30a signals through the SS7 network 60 to the CACS 70 via TCAP queries to request call handling instructions for calls destined to the subscriber's phone

006222. The following information is contained in this TCAP message: i. Message Type = Conversation With Permission ii. Component Type = Invoke iii. Operation = Update Request iv. Parameters = User ID or Number, Bearer

0063Capability, Trigger Criteria Flag, where User

0064Number is the subscriber line 24 phone number, Bearer Capability is "voice" and the

0065Trigger Criteria Flag is "enabled".

0066The switch 30a also responds through the SS7 network 60 to the above TCAP query with another TCAP message to the

0067CACS 70 that provides a successful acknowledgement. The following information is contained in this TCAP message:

0068Message Type = Response i. Component Type = Return Result ii. Operation = None v. Parameters = None

00697. The CACS 70 sends a TCAP message through the SS7 network 60 to the switch 30a including the network address of the selected bridge 80a that will host the conference. The following information is contained in this TCAP message:

0070Message Type = Response

0071Component Type = Invoke

0072Operation = Call Forward iv. Parameters = Outpulse Number (Mandatory),

0073Trunk Group Number (Optional), where the

0074Outpulse Number identifies the incoming line with the conference running on the bridge 80, and the Trunk Group Number identifies the network address of the bridge 80 servicing the conference call.

00758. The CACS 70 notifies the selected bridge 80a over the data network 90 that will be hosting the conference that a conference is about to commence, and instructs the selected bridge 80a to allocate the ports required to host the conference based on the conference profile of the subscriber 20. The order of steps 7 and 8 is immaterial.

00769. Upon receipt of the TCAP message sent in step 7, the switch 30a routes the call of the subscriber 20 to the selected conferencing bridge 80a.

007710. The selected bridge 80a notifies the CACS 70 that the conference is underway.

0078Following completion of all of the above steps, the call is completed to a conferencing system as described in U.S. Patent 6,181 ,786 B1 , or by other conventional means of conference control. In addition, the subscriber line 24 is now in "conference mode". Subsequent calls to the subscriber line 24 telephone number while in "conference mode" will be forwarded to the conferencing system as described in the following section.

0079The above method steps and message contents represent only an embodiment of the present invention and, it is to be understood, that method steps order and message contents can vary based upon individual telecommunication architects without departing from the spirit of the present invention.

0080(b) Subsequent caller routing

0081In Figure 3, operation of the conferencing method 10 of the present invention whereby a subsequent caller joins the conference call is set forth for the SS7 60 embodiment. The numbered arrows shown in Figure 3 corresponds to the method of accomplishing this.

00821. A subsequent caller 40 picks up the handset on phone 42 and dials the subscriber's phone number for phone 22.

00832. Through conventional means, the subsequent caller's call is connected via the subsequent caller's local CO switch 30b and via the LATA 50 to the switch 30a that services the subscriber line 24. It is to be understood that the switch 30b can be the same as subscriber's switch 30a, located in the same LATA 50 as switch 30a, in a remote LATA location, or elsewhere.

00843. The CO Switch 30a determines that the subscriber's Termination Attempt Trigger (TAT) is activated (via step 5 in the aforementioned subscriber flow), which causes a TCAP message to be sent to the CACS 70 via SS7 60 to determine where to forward the call. The following information is contained in the TCAP message: i. Message Type = Conversation With

0085Permission ii. Component Type = Invoke iii. Operation = Connectivity Control Termination Attempt iv. Parameters = Called Number (number dialed by the subsequent caller, which would be the subscriber line 24 phone number), Calling

0086Number (phone number of the subsequent caller 40) In the PHFN embodiment (not shown), switch 30a forwards the subsequent caller to the subscriber's PHFN on the selected bridge 80a, the same bridge as the subscriber's conference call.

00874. Upon receipt of the TCAP message, the CACS 70 responds to the switch 30a with a TCAP message requesting that the switch 30a play an announcement to the calling party requesting the calling party (i.e., the subsequent caller 40) to input a code (i.e., called entered digits (CED)) having at least one DTMF input signal such as, for example, "press 1 to enter the conference" and to collect the digits entered by the calling party 40. The following information is contained in the TCAP message: i. Message Type = Conversation with

0088Permission ii. Component Type = Invoke iii. Operation = Caller Interaction Send to Resource iv. Parameters = Play Announcement and Collect Digits Tag and Announcement Tag

00895. The switch 30a plays a message to the subsequent caller 40 requesting that the caller "press '1' (or any other CED) to enter the conference or any other number to be directed to voicemail or other default busy treatment". Any other suitable message that conveys these instructions can be used here.

00906. The subsequent caller 40 presses "1" (or any other CED) to join the conference, or any other digit to be disconnected or sent to default busy treatment (e.g. voicemail, busy signal) and this information is transmitted via conventional means back to switch 30a.

00917. Upon collecting the digit or digits from the caller, the switch 30a responds to the TCAP message of the aforestated step 4 by sending a TCAP message through the SS7 network 60 to the

0092CACS 70 containing the Caller Entered Digit(s) (CED) (which would be, for example, "1" in the instance that the calling party 40 wishes to join the conference and any other digit for alternative behavior). The following information is contained in the TCAP message: i. Message Type = Conversation with

0093Permission ii. Component Type = Invoke iii. Operation = Caller Interaction Resource Clear iv. Parameters = Collected Digits (1 or other, or none) 8. The CACS 70, in one embodiment, validates the Caller Entered Digits (CED). The CACS 70 responds to the switch 30a with a TCAP message including call termination instructions. If the CED is "1", the instructions include information about on which bridge 80 to place this call (e.g., bridge 80a). The following information is contained in the TCAP message:

0094Message Type = Response Component Type = Invoke iii. Operation = Call Forward iv. Parameters = Routing Number of bridge or voicemail or other service (Mandatory), Trunk Group Number if routing number is for a bridge 80 (Optional) If the CED is not "1", the message instructs the switch 30a to proceed normally (as if the subscriber's line were busy), which may include routing the caller to voicemail or other service. The following information is contained in the TCAP message: i. Message Type = Response ii. Component Type = Invoke iii. Operation = Connection Control Authorize

0095Termination iv. Parameters = None

00969. The switch 30a then routes the calling party 40 to the appropriate bridge 80 (e.g., 80a) or to alternative class service, or to busy line handling as determined from the caller 40 input in the aforestated step 8.

009710. The bridge 80a sends a message over network 90 to the CACS 70 notifying it that the subsequent caller 40 is connecting to the conference. The call is completed to a conferencing system 110 as described in U.S. Patent 6,181 ,786 B1 or by other conventional means of conference control. The above method steps and message contents represent only an embodiment of the present invention and, it is to be understood, that method steps order and message contents can vary based upon individual telecommunication architects without departing from the spirit of the present invention.

0098(c) End of Conference Call

0099In Figure 4, operation of the conferencing method 10 of the present invention whereby the conference ends and the subscriber line 24 is re-set to directly receive incoming telephone calls is set forth for the SS7 60 embodiment. The following numbered arrows shown in Figure 4 correspond to the method of accomplishing this.

01001. The conference call ends when the subscriber phone 22 is placed on hook and the subscriber line 24 conveys a disconnect signal to the switch 30a. 2. The CO Switch 30a detects conventionally that the subscriber line 24 has been disconnected and delivers a disconnect signal to the conferencing bridge 80a.

01013. The bridge 80a informs the CACS 70 that the conference subscriber 20 has disconnected. In one embodiment, any remaining participants (e.g., subsequent callers 40) to the conference are disconnected at this point by sending a message indicating that participants should be disconnected from the CACS 70 to the bridge 80a. In an alternative embodiment, the remaining parties 40 are allowed to remain connected to the conference until they disconnect.

01024. The CACS 70 sends a TCAP message through the SS7 network 60 to the switch 30a instructing it to toggle the subscriber's Termination Attempt Trigger (that was set in step 5 of the subscriber routing) to "disabled". This is the instruction that sets the subscriber line back to normal operating condition where calls to the subscriber line 24 phone number will ring the subscriber's phone 22, rather than forward to the conferencing service. The following information is contained in the TCAP message:

0103Message Type = Conversation With Permission Component Type = Invoke Operation = Update Request iv. Parameters = User ID or Number, Bearer Capability (i.e. voice), Trigger Criteria, where User Number is the subscriber line 24 phone number, Bearer Capability is "voice" and Trigger Criteria

0104Flag is "disable".

01055. The switch 30a then responds to this TCAP message with another TCAP message through the SS7 network 60 to the

0106CACS 70 indicating successful acknowledgement when the operation is complete. The following information is contained within this TCAP message:

0107Message Type = Response Component Type = Return Result iii. Operation = None iv. Parameters = None

0108Upon completion of the last event, the subscriber line 24 is returned to normal operation, whereas subsequent calls to the subscriber line 24 phone number will not generate TCAP queries from the switch 30 to the CACS 70, thus preventing subsequent calls from being routed to the conferencing system 110.

0109The above method steps and message contents represent only an embodiment of the present invention and, it is to be understood, that method steps order and message contents can vary based upon individual telecommunication architects without departing from the spirit of the present invention. (d) Pre-Route Locking and Unlocking

0110In Figure 5, operation of the subscriber locking and unlocking the conference to prevent or allow subsequent callers from joining the conference call is set forth as one embodiment. 1. The subscriber 20 determines that the conference should be

0111"locked" to prevent further subsequent callers 40 from being permitted to enter the conference. The mechanism by which the subscriber 20 controls the conferencing system 110 to indicate his/her desire to lock the conference is outside the scope of this present invention and is conventional such as a specific DTMF keystroke sequence received by switch 30a.

01122. The command to lock the conference is delivered via conventional means to bridge 80a.

01133. The bridge 80a notifies the CACS 70 that the conference should be locked, and no further subsequent callers should be permitted to enter the conference.

01144. The CACS 70 sends a TCAP message through the SS7 network 60 to the switch 30a to set the Termination Attempt Trigger (TAT) to "disabled". This will set the subscriber's line 24 back to normal operating mode, where subsequent calls will no longer generate TCAP queries from the switch 30 to the CACS 70 to request call handling instructions. The following information is contained in the TCAP message: i. Message Type = Conversation With Permission ii. Component Type = Invoke iii. Operation = Update Request iv. Parameters = User ID or Number, Bearer

0115Capability (i.e. voice), Trigger Criteria Flag, where

0116User Number is the subscriber phone number, Bearer Capability is "voice" and Trigger Criteria

0117Flag is "disable". 5. The switch 30a then responds to this TCAP message with another TCAP message indicating successful acknowledgement when the operation is complete. The following information is contained within this TCAP message: Message Type = Response Component Type = Return Result Operation = None iv. Parameters = None Upon completion of the last event, although the subscriber 20 is still in the conference, the subscriber line 24, from the perspective of switch

011830, is returned to normal operation, whereas subsequent calls to the subscriber line 24 phone number will not generate TCAP queries to the conferencing system 110. Subsequent calls to the subscriber line will encounter the default busy treatment (busy signal, voicemail, or other service) for that subscriber.

0119Once locked, in order to unlock the conference, Figure 5 depicts the same flow of activities with the following changes:

01201. The subscriber 20 determines that the conference should be

0121"unlocked" to allow further subsequent callers to be permitted to enter the conference. The mechanism by which the subscriber 20 controls the conferencing system 110 to indicate his/her desire to unlock the conference is also conventional and uses a DTMF key stroke sequence received by the switch

012230a. 2. The command to unlock the conference is delivered to and received by via conventional means by the bridge 80a.

01233. The bridge 80a notifies the CACS 70 that the conference should be unlocked, and further subsequent callers should be permitted entry to the conference. 4. The CACS 70 sends a TCAP message through the SS7 network 60 to the switch 30a instructing it to toggle the subscriber's Termination Attempt Trigger (TAT) to "enabled". As subsequent callers dial the subscriber's phone number, this TAT will cause the switch 30a to send a TCAP message through the SS7 network 60 to the CACS 70 to request call handling instructions when calls are placed to the subscriber's phone number. The following information is contained in this TCAP message to enable the Termination Attempt Trigger: Message Type = Conversation With Permission Component Type = Invoke Operation = Update Request iv. Parameters = User ID or Number, Bearer

0124Capability, Trigger Criteria Flag, where User Number is the subscriber phone number, Bearer Capability is "voice" and the Trigger Criteria Flag is "enable". 5. The switch 30a responds to the above TCAP query with another TCAP message through the SS7 network 60 to the CACS 70 that provides a successful acknowledgement. The following information is contained in this TCAP message: i. Message Type = Response ii. Component Type = Return Result iii. Operation = None iv. Parameters = None Once completed, subsequent callers will be permitted to enter the conference as defined in section (b) (Subsequent Caller Routing). The above method steps and message contents represent only an embodiment of the present invention and, it is to be understood, that method steps order and message contents can vary based upon individual telecommunication architects without departing from the spirit of the present invention. In another embodiment, once the conference is locked, a message is played to any subsequent caller who calls the subscriber's phone number. This message informs the subsequent caller that the subscriber is in a closed conference and to leave a message by pressing a DTMF key (i.e., or press 7) or call back later. In another embodiment, the subsequent caller to the locked conference is given an announcement as above followed by a busy signal. It is to the understood that many variations can be provided under the teachings of the present invention.

01254. Methods.

0126In Figure 6, the setting up and participating in a conference call of the present invention is set forth. In step 600, the subscriber 20 contacts the other participants 40 in the conference call. For example, the subscriber 20 may call, e-mail, fax, use the Internet, etc. all other desired participants 40 in the conference call and inform them of a time for the call and to call his/her phone number for his/her phone 22 at that time. The performance of step 600 can be at any suitable time in advance of conference calls of the present invention.

0127In step 610, the subscriber 20 using phone 22 dials a

0128predetermined series of inputs such as " 90" to initiate the conference. In stage 620, the LEC 100 and the conferencing system 110, as fully described above for Figure 2, sets up the conference call for the subscriber 20.

0129At this time, the subscriber 20 is on line and has a conference call set up ready for other participants (i.e., subsequent callers 40 to the subscriber's phone number) based upon the subscriber's profile. At, about, or just after the time of the conference call, one or more additional participants 40 in stage 630 calls the subscriber's phone number for phone 22. LEC 100 and conferencing system 110 forwards each subsequent caller 40 to the selected bridge 80 (e.g., 80a).

0130Optionally, as shown by dotted lines in stage 640, the subsequent caller 40 enters the additional signal (or signals) CED such as pressing the number "1." When valid, stage 650 is entered and the subsequent caller 40 is added as a participant to the conference call. If not valid, a message is played in stage 645 to the subsequent caller 40. The subsequent caller 40 may be given one or more retries 647 and, if the subsequent caller does not enter the proper signal in stage 640, the process ends 660 with respect to that subsequent caller.

0131The same steps 640, 645, and 660 are optionally used by the CASC 70 to verify the input of the Conference Security Code (CSC) by the subsequent caller discussed earlier.

0132In stage 650, subsequent callers 40 are added to the conference call.

0133The conferencing system 110 monitors in step 670 whether the conference call is over and, if not, in stage 680 continues to monitor and adjust the conference call based upon the subscriber 20 profile features as keyed in by the subscriber 20. Any operator 120a, administrator 120b, profile (including conference control) features can be performed during the conference call. Once the conference call is over, stage 690 is entered. The conference ends, in one embodiment, when the subscriber 20 disconnects. In another embodiment, a timer times out. Any remaining participants 40 would be played a voice message and disconnected from the conferencing bridge. Upon disconnection, the switch immediately resets the subscriber line to "normal" mode (e.g., deactivating the subscriber's termination attempt trigger) allowing the subscriber to be able to receive normal point-to-point calls.

01345. Alternate Operational Embodiments. a. Pre-set "Conference Mode"

0135With this option, the subscriber 20 enters the 90 DTMF sequence (or any other sequence) into his/her phone 22 at dial tone and then is played a message (such as a switch-based IVR 32 resource) that his/her phone service is now in "conference mode". The subscriber 20 then hangs up or presses 1 to join the conference. While in "conference mode," all subsequent callers 40 to the subscriber's phone number would be played a message which informs them that the person they have called is in a conference call. Subsequent callers 40 who press 1 would be routed to a conference bridge and placed into the conference call.

0136The conference would end in stage 690 under either one of the following conditions: 1 ) the subscriber 20 joins the conference and it then disconnects, or 2) the subscriber 20 enters 90 at dial tone again

0137(or any suitable conference end signal or sequence input by the subscriber). In either case, conference participants would be played a voice message and disconnected.

0138b. Regular Phone Call Becomes Conference

0139^•k

0140Under this embodiment, the subscriber keys in 90 (or any other sequence or suitable signal) during a regular POTS phone call, which results in both parties to the call setting up a conference call and being transferred to a conference bridge 80. Subsequent callers 40 to the subscriber's phone number are directed to the conference after a confirmation IVR message. The signaling is a matter of design choice and does not limit the scope of the invention.

0141c. Pre-set Conference Mode, Ring Back On First Participant This embodiment is similar to a. above, except that the subscriber 20 would be called, if he/she is not already in conference, when the first participant 40 is sent to the conference. The subscriber

014220 is prompted with an appropriate message and given the opportunity to join the conference. d. Attended Entry With Participant Recorded Name

0143As an extension to the capability described in a. above, conference participants 40 are prompted, once they are connected to the conference bridge, to record their name for conference entry screening. The subscriber 20 is played a message informing him/her that a subsequent caller 40 is requesting to join their conference, with the subsequent caller identified by the recorded name. The subscriber 20 is given the opportunity to input a signal that either authorize that person in or to disconnect. Optionally, the subscriber 20 is allowed to speak privately (outside the conference) with the caller 40 prior to placing him/her in conference or disconnecting him/her.

0144e. Attended Entry Using Existing LEC Call-waiting Mechanism This embodiment is similar to that proposed in d. above, except that participant 40 entry is attended through the existing LEC call- waiting mechanism. The subscriber 20 is informed of new incoming callers 40 with voice path call-waiting tones. The subscriber 20 then performs a hook flash to speak with the incoming caller 40. In the switch 30, a second hook flash would place the caller 40 in conference.

0145f. Subscription Management in Network 100 instead of CACS 70

0146This embodiment involves an assumption in the CACS 70 that all subscriber 20 calls that reach the conferencing system 110 represent calls from valid subscribers 20. In this embodiment, the CACS 70 need not have a pre-existing account profile established for the subscriber; rather the CACS 70 will use a predetermined profile of conference configuration settings that will apply to all conferences on the system 110. 6. Alternate Architectural Embodiments.

0147Several architectural alternatives exist under the teachings of the present invention:

0148a. Bridges 80 Located with Individual LEC Switches 30 This configuration shown in Figure 7 distributes conference trunking capacity to individual switches 30 in the LEC network 100. All conferences would be handled by the bridge 80 or bridges (and servers 70 and 90) located physically behind the switch 30a that services the subscriber's phone line 20a.

0149b. Bridges 80 Centrally Located Within the LEC

0150Network 100

0151This configuration shown in Figure 8 places all of the conference bridges 80 behind a single switch 30 in the LEC network

0152100, which concentrates the trunking capacity to a particular switch 30 and switch site. This configuration would allow for more efficient capacity management and bridge port resource management, because all of the bridges are controlled by one central conferencing call router.

0153c. Fixed Access (Without SS7 Network 60) This configuration shown in Figure 9 removes the conferencing system 10 connections to the SS7 network 60. In this embodiment, conference calls involving a particular subscriber 20 will always terminate on the same conference bridge 80. Control of subscriber line 24 behavior necessary to direct incoming callers to the conference when appropriate takes place either within the switch 30 or otherwise within the telephone network 100.

0154It is to be understood that the teachings of the present invention can be implemented in a number of telecommunication architectures, not limited to the above. The above disclosure sets forth a number of embodiments of the present invention. Those skilled in this art will however appreciate that other arrangements or embodiments, not precisely set forth, could be practiced under the teachings of the present invention and that the scope of this invention should only be limited by the scope of the following claims.