Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0029—Provisions for intelligent networking
  • H04Q3/005—Personal communication services, e.g. provisions for portability of subscriber numbers
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/02—Details
  • H04L12/16—Arrangements for providing special services to substations
  • H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
  • H04L12/1813—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast for computer conferences, e.g. chat rooms
  • H04L12/1818—Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M3/00—Automatic or semi-automatic exchanges
  • H04M3/42—Systems providing special services or facilities to subscribers
  • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q3/00—Selecting arrangements
  • H04Q3/0016—Arrangements providing connection between exchanges
  • H04Q3/0029—Provisions for intelligent networking
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W76/00—Connection management
  • H04W76/40—Connection management for selective distribution or broadcast
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M2203/00—Aspects of automatic or semi-automatic exchanges
  • H04M2203/50—Aspects of automatic or semi-automatic exchanges related to audio conference
  • H04M2203/5063—Centrally initiated conference, i.e. Conference server dials participants
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M2203/00—Aspects of automatic or semi-automatic exchanges
  • H04M2203/65—Aspects of automatic or semi-automatic exchanges related to applications where calls are combined with other types of communication
  • H04M2203/652—Call initiation triggered by text message
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M3/00—Automatic or semi-automatic exchanges
  • H04M3/42—Systems providing special services or facilities to subscribers
  • H04M3/42382—Text-based messaging services in telephone networks such as PSTN/ISDN, e.g. User-to-User Signalling or Short Message Service for fixed networks
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M3/00—Automatic or semi-automatic exchanges
  • H04M3/42—Systems providing special services or facilities to subscribers
  • H04M3/56—Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities
  • H04M3/563—User guidance or feature selection
  • H04M3/565—User guidance or feature selection relating to time schedule aspects
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04M—TELEPHONIC COMMUNICATION
  • H04M7/00—Arrangements for interconnection between switching centres
  • H04M7/0024—Services and arrangements where telephone services are combined with data services
  • H04M7/0042—Services and arrangements where telephone services are combined with data services where the data service is a text-based messaging service
  • H04M7/0048—Services and arrangements where telephone services are combined with data services where the data service is a text-based messaging service where the text-based messaging service is a Short Message Service
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13098—Mobile subscriber
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/1324—Conference call
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04Q—SELECTING
  • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
  • H04Q2213/13336—Store & forward, messaging systems
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
  • H04W4/12—Messaging; Mailboxes; Announcements
  • H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W8/00—Network data management
  • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

• the present invention relates generally to extended call setup and control, and particularly to a system and method for effecting the establishment of enhanced call connections using a short message service (SMS) message.
• SMS short message service
• the increased mobility has meant that it is less and less likely that a group of persons will be co-located at a central location and able to participate in meetings.
• Such conference calls have been organized so that participants gather at pre-defined wireline locations at a single date and time, in order to participate in a conference call set up between such locations. While workable, such wireline conference calls are sub-optimal in that they limit the mobility of participants, who must agree and arrange to attend at one of the pre-defined wireline locations in order to participate in the conference call. This requirement tends to negate the freedom from being tethered to a wireline telephone provided to the participants through the use of cellular telephones.
• a further disadvantage of the wireline conference call is its relative inflexibility. Meetings, whether face-to-face or by conference call, are generally dynamic. It frequently arises that unexpected issues are raised and discussed, and other persons not participating in the meeting may have to be consulted. In the context of a face-to-face meeting, such developments may be relatively easily accommodated.
• the conference call must often be terminated and rescheduled at a later time or date in order to permit the participation of these other persons.
• SMS short message service
• users can set up, initiate and participate in conference calls using a cellular telephone and SMS messages.
• the SMS messaging feature also permits a user to control the configuration of the conference call while the call is in progress, without the need for additional equipment, such as a second telephone device.
• a conference call is set up by an initiating party using the SMS messaging feature.
• the initiating party transmits a message or series of ⁇ messages that identify each participant by telephone number and specifies a date and time for the conference call. The date and time may be in the future, or may take effect immediately.
• the system forwards an invitation to each of the participants to permit them to accept the conference call using the SMS messaging feature.
• the invitation identifies the date and time of the conference call and specifies a conference bridge number (CBN) to be transmitted in order to accept participation in the conference call .
• the CBN uniquely identifies the conference call to which the participant is to be joined.
• the system attempts to connect each participant who accepted the conference call invitation. If the system is able to establish a connection with the participant, it adds the participant to the conference call using a conference bridge in a manner well known in the art.
• the SMS messaging feature need not be available on the cellular telephone device itself. Rather, text messaging available on a separate device such as a personal digital assistant may also be used. Indeed, a wireline telephone may also be used for the call after call setup is accomplished using an SSM or text messaging equipped device .
• Participants who may wish to participate in a conference call but do not have SMS capability may interact with the system using other suitable electronic text messaging means, such as e-mail or by voice using a dial-up IVR unit. Alternatively, they may accept the call at the time, prompted by an IVR unit.
• one of the existing participants may transmit an SMS message to the desired participant containing the designated CBN and other information identifying the telephone call.
• an existing participant may transmit ' an SMS message to request that the system invite the intended participant, whereupon the system transmits instructions to permit the desired participant to join the conference call.
• the intended participant may join the conference call by merely transmitting the requested information by SMS message.
• the method and system in accordance with the embodiments of the present invention therefore provide a simple, convenient and powerful mechanism for setting up, controlling and participating in extended calls such as conference calls between cellular telephones.
• FIG. 1 is a schematic diagram illustrating principal components of a system shown in an exemplary deployment for providing SMS message-initiated call setup and control operations in accordance with an embodiment of the invention
• FIG. 2 is a flow chart illustrating principal steps performed by a conference scheduler database application in accordance with an embodiment of the invention when a conference request;
• FIG. 3 is a flow chart illustrating principal steps performed by a call controller in accordance with an embodiment of the invention when a call request ' generated by the conference scheduler database application is retrieved from the call controller database;
• FIG. 4 is a call flow diagram illustrating principal steps in a successful attempt to arrange a conference call on a scheduled basis
• FIG. 5 is a call flow diagram illustrating principal steps in a successful attempt to establish a previously scheduled conference call
• FIG. 6 is a call flow diagram illustrating principal steps in a successful attempt to arrange a conference call involving a participant using a wireline telephone and without SMS capability;
• FIG. 7 is a call flow diagram illustrating principal steps in two successful attempts by a participant to join an ongoing conference call at the invitation of an existing 'participant.
• FIG. 8 is a call flow diagram illustrating principal steps in a successful attempt by a participant to forward an ongoing conference call from one telephone number to another.
• the present invention provides a system and method for establishing conference call connections using SMS messages sent from any device adapted to communicate using a text messaging protocol such as SMS .
• the call may be set up to connect a group of telephone devices accessible through the public switched telephone (PSTN) wireline or the wireless telephone networks.
• PSTN public switched telephone
• the participants in the conference call have the ability to communicate using the short message service (SMS) protocol, whether directly through the participant's associated wireless telephone or through an alternative text messaging device, such as a personal digital assistant (PDA) .
• SMS short message service
• PDA personal digital assistant
• the method also enables users to join the call using an SMS message, if they possess requisite information.
• a party to a call may also transfer or bridge the call using SMS messaging.
• Requesting or scheduling initiation of the extended call may alternatively be made through an Internet portal or web page of the service provider, to expedite entry of the request .
• SMS messages may therefore alternatively be used only to enable calling parties to join, and possibly to invite other SMS users to join the extended call.
• FIG. 1 illustrates an exemplary deployment of a system for providing telephone conference call services to customers who initiate conference call requests using the SMS protocol.
• a Public Switched Telephone Network (PSTN) 24 comprises a network of switched trunks for carrying voice and data traffic between terminal units, such as conventional telephone terminals 2. Usage of the trunks in the PSTN 24 are controlled by a Common Channel Signaling (CCS) network 22, such as Signaling System Number 7 (SS7) .
• CCS Common Channel Signaling
• SS7 Signaling System Number 7
• the CCS network 22 includes a plurality of switches interconnected by signaling and trunk lines.
• the architecture of the CCS network 22 is also well known in this art. As discussed above, use and deployment of cellular telephones 16 is rapidly increasing. As is well known in this art, the SS7 system uses the Mobile
• MAP Application Part
• TCAP Mobile Switching Centers
• MSC Mobile Switching Centers
• HLR Visitor Location Registers
• VLR Visitor Location Registers
• the HLR 19 is a database used for permanent storage and management of subscriptions and service profiles for subscribers at the point of subscription.
• the MSC 20 is a switch that controls voice circuits. It communicates wirelessly with cellular telephones within its associated cellular region through one or more associated base station subsystem(s) (BSS) 18.
• the MSC 20 also makes circuit connections into the PSTN 24 to establish an outgoing call from the cellular telephone 16 or accepts a connection from the PSTN 24 to establish an incoming call to a cellular subscriber.
• the BSS 18 includes a base station controller (BSC) that controls one or more base transceiver systems (BTS) . Each BTS defines a cell of a cellular network and communicates wirelessly with the cellular telephone 16.
• the BSC manages resource assignment when a subscriber moves from one sector of one BTS to another.
• the VLR 21 stores information for cellular subscribers that are roaming within cells managed by the associated MSC 20.
• the MAP protocol also supports SMS wireless service. SMS enables the transmission of alphanumeric messages between mobile subscribers and external systems, such as electronic mail, paging and voice-mail systems.
• the maximum length of an SMS message is typically 160 characters .
• SMS service A hallmark of the SMS service is that message delivery is guaranteed by the network. If the destination unit is unavailable, the message is stored until the destination unit becomes available. Further, so long as the destination unit is active, it may generally receive or send an SMS message, independent of whether a voice or data call is in progress. Where an SMS message is to be transmitted between mobile users, the message is transmitted wirelessly from the transmitting unit, say 16a to the BSS 18a associated with the MSC 20a governing the transmitting unit's present location. The SMS message is thereafter routed along the CCS network 22 elements to the recipient's governing MSC 20b, for example, through the associated BSS 18b and
• Certain wireless devices other than cellular telephones 16 may have SMS functionality.
• Such devices may include Personal Digital Assistants (PDA) 14 having wireless capability, such as Research in Motion's Blackberry " and 3Com Corporation's Palm VII devices, which can communicate using the SMS feature of the BSS 18 and the associated MSC 20, but do not make use of the voice/data cellular network.
• WAP telephones 12 may also support SMS messaging.
• SMS service One of the benefits of SMS service is its ability to exchange messages with non-mobile units, such as voice-mail systems, web-based messaging systems enabled by the SMS web gateway 23 from the Internet 26, e-mail and other external Short Messaging Entities (SME) .
• SMSC SMS Centers
• the SMSC 25 relays, stores and forwards short messages from an SME to a mobile device.
• SMSC 25 and the SME take the place of the MSC 20.
• SMS message received from the Internet 26 by the SMS web gateway 23 will be communicated to the SMSC 25 and transmitted through the CCS network 22, to the MSC 20 serving the recipient, through the associated BSS 18 and wirelessly out to the recipient unit 16.
• the system for providing telephone conference call services in accordance with the present invention includes a conference scheduler gateway (CSG) 30, a centrally located conference call server 28 and at least one service center 4.
• CSG conference scheduler gateway
• centrally located conference call server 28 and at least one service center 4.
• the conference scheduler gateway 30 receives SMS messages addressed to it and converts the message content into a text message for transmission, together with a header indicating who sent the message, over a secure connection, such as TCP/IP, through the Internet 26 to the server 28.
• a conference gateway 32 may be connected directly to a call controller 8 by an Ethernet link 31, for example.
• the conference gateway receives SMS messages directly over a wireless link from a wireless base station, base station 18a, for example. This has advantages in that, since the SMS network guarantees SMS message delivery, the delay and potential loss of data packets that can occur in the Internet is avoided.
• the conference gateway 32 preferably includes all of the functionality of the server 28, including the respective databases, which may be accessed through the Internet by customers who wish to add or change records in their personal profiles, etc.
• the conference gateway is adapted to wirelessly receive SMS messages and to process the messages in the same way that the server 28 does.
• the conference gateway may pass the SMS messages directly to the call controller 8, without conversion, in with case the call controller 8 includes the conference scheduler database application 29, and the databases 27a-27d.
• the server 28 is accessed by customers through the Internet 26, typically using SMS messages sent by a customer using a cellular telephone 16 via the conference scheduler gateway 30.
• a web server 33 may provide a worldwide web gateway that permits customers to schedule conference calls using a web interface.
• the server • 28 includes or has access to a conference scheduler database application 29 and a plurality of databases 27a-27d. Internal or external connections permit the conference scheduler database application 29 to access and update the various databases 27.
• the conference scheduler database application 29 receives the content of SMS messages and processes them in order to schedule, initiate and reconfigure requested conference call services.
• the databases include a profile database 27a, a billing database 27b and a conference database 27c.
• the profile database 27a maintains customer profiles, including pre-defined conference call configurations, user preferences and permissions.
• the billing database 27b maintains financial records including prepaid services.
• the conference database 27c maintains a list of scheduled conference calls.
• a call queue 27d accessed by call controllers (CC) 8 using a secure connection to pull for conference calls that are to be initiated, or reconfigured.
• Each service center 4 includes for example, a point-of-presence (POP) switch 6, the CC 8 and an intelligent peripheral such as an Interactive Voice Response (IVR) unit 10.
• POP point-of-presence
• IVR Interactive Voice Response
• Service center 4 are located whenever traffic volume warrants, for example, in each major city in the service area.
• the POP 6 is a telecommunications switch and is integrated into the PSTN 24. Alternatively, it may be an existing toll switch within the PSTN 24. In any event, the ability to bridge calls is central to its functionality.
• the CC 8 - is an application that periodically polls its assigned call queue 27d through a secure connection to obtain requests for calls to be set up or reconfigured by the service center 4. ,It also accesses and updates the databases 27 through a secure connection. It sends instructions to the POP 6, as required, to effect to the call requests.
• the IVR 10 is an intelligent peripheral that permits voice interaction with a system user in order to obtain information for customer validation and call setup or reconfiguration.
• the server 28 and the service center 4 cooperate to provide conference call services to customers in accordance with an embodiment of the present invention.
• the system for providing conference call services is a subset of a group of services provided by a telephone service provider (TSP) .
• TSP telephone service provider
• any wireline or wireless device may send an SMS text message to the conference scheduler database application 29 to request a conference call setup.
• the conference scheduler database application 29 receives an- SMS text message requesting a conference call, the message is parsed and validated. If valid, the conference scheduler database application 29 schedules the conference call by sending SMS text messages to the proposed participants, who may accept or decline the conference call invitation.
• the conference scheduler database application 29 updates the call queue 27d to request that connections be made to establish the conference call.
• the CC 8 systematically polls the call queue 27d and retrieves call requests for completion by the POP 6.
• an intelligent peripheral such as IVR 10, may be used under certain circumstances to obtain conference call related information.
• SMS message format itself imposes a few constraints on the format of the electronic text message. SMS messages have a maximum length of 160 characters, but may be concatenated to form larger messages. Nevertheless, because the transmission of each message incurs a service charge, messages should comprise a collection of generally highly-coded and brief command sequences.
• an exemplary text message format for a request to schedule a conference call is as follows:
• the command listed above in bold text is mandatory and must be provided for every call request .
• the command specifies the type of call that is to be established by the system.
• exemplary commands are: “cc”; “sec”, “cc#” and “scc#”.
• the "cc” command is used to establish a conference call between three or more parties on an immediate basis, as discussed below.
• the "sec” command is used to establish a scheduled conference call at a later date.
• the "cc#” and “scc#” commands are used to originate predefined sets of originating number / destination number groups that are stored in a customer profile for either immediate or scheduled conference calls respectively.
• the optional abort time field may be specified to avoid calls at an inconvenient time. Since not all forms of electronic text messaging, including SMS, can be relied upon to deliver messages within a predicted time, the "abort time" limits the window in which an attempt will be made to schedule a conference call.
• the abort time is preferably specified in the format "dd:mo :hh:mm, Time Zone"; a 24-hour format, followed by a time zone indicator. If an abort date is not specified, the date on which the message was sent, as indicated in the message header, is assumed. If the abort time has passed when the message is received, the message is discarded and a call aborted message is returned to the requester.
• an originating number is designated as a default.
• the optional origination no. information permits a requester to specify an originating number which is not stored in the customer profile.
• the specification of an originating number that is not stored in the customer profile initiates a special authentication procedure to determine the entitlement of the caller to place a call, as described in Applicant's co-pending United States Patent Application No. 09/813,845, referenced above.
• the mandatory, destination info(s) information is used to specify the contact information for two or more conference call participants.
• the contact information consists of a primary destination number, an optional backup destination number, and a text messaging address.
• the destination number (s) may conform to any number plan format and must appear first. Multiple contact information groups are separated by semicolons.
• SMS messages may be addressed to the participant by sending them to the destination telephone number.
• the SMS-capability is indicated by the letter "s” following the slash character instead of an explicit text messaging address.
• this may be indicated by the letter "v” following the slash character in place of any explicit text messaging address.
• the originating text message address is not provided. It is unnecessary because it is inferred from the message header of the text message containing the command sequence .
• the originating text message address is identified using the originating telephone number, which is stored in the "from" field of the SMS message. This telephone number must be among the originating numbers stored in the customer profile database 27a.
• the date/time information is used for scheduled calls, that is, calls that are not to be initiated immediately.
• the date/time field will only be valid with the following commands: "sec” and "scc#" .
• the omission of the date/time field for these commands will result in a syntax error.
• the date/time information is preferably specified in the format "dd:yy:mo :hh:mm, TimeZone" .
• the time is preferably specified in 24 -hour format, followed by a time zone indicator. If a date is not specified, the current date is assumed.
• the optional POP (point of presence) information is used to indicate a particular POP from which the conference call is to be set up.
• the billing code is an optional field used to associate charges for the call with a particular billing code, as is well known in this art.
• Scheduling Request message format there are a number of other SMS messages that may be exchanged between users and the system, namely the invitation, Accept, Decline, Join and Forward messages.
• the invitation message is sent by the conference scheduler database application 29 to each participant in the conference call as identified in the Scheduling Request message.
• the abort time and date/time fields have the same significance as in the Scheduling Request message.
• the CBN field contains a conference bridge number assigned by the server 28 to uniquely identify the conference call .
• An exemplary text message format is as follows :
• the Accept and Decline messages are sent by each recipient of an invitation message to indicate whether the recipient wishes to participate in the proposed conference call identified by the CBN field.
• Exemplary text message formats are as follows:
• Decline message format d; abort time; CBN
• the Join message may be sent by a proposed participant to the system to request admission into an ongoing conference call.
• the proposed participant must have been previously provided with the CBN, which both identifies the conference call and serves to validate the proposed participant.
• the Join message may be sent by a present participant in the conference call to the system, to request that an invitation be sent to the proposed participant.
• the destination info field is required to identify the proposed participant to the system. The destination info field is not required when the proposed participant sends the Join message, because this can be inferred from the message header of the text message containing the message.
• An exemplary text message format is as follows:
• the Forward message may be sent by a present participant in an ongoing conference call to forward the participant's telephone number (origination no.) to a new telephone number (destination no.) . Because no SMS message need be sent, the text messaging address is not required.
• An exemplary text message format is as follows:
• Forward message format f; abort time; CBN; origination no. ; destination no.
• FIG. 2 is a flow diagram showing principal steps performed by the conference scheduler database application 29, to manage the exchange of the above- identified messages with users and to access and update the databases 27 in conjunction therewith.
• a text message is retrieved by the conference scheduler database application 29 from the Internet 26, or directly by the CC 8 from the conference gateway 32 (step 200) .
• the conference scheduler database application 29 examines the delimited information in the message (step 202) to determine whether the message can be parsed. If the information is incorrectly specified or critical information is missing, the conference scheduler database application 29 formulates an appropriate error message (step 204) and transmits it to the originator identity extracted from the message header (step 206) , at which point it waits for the receipt of another message.
• the conference scheduler database application 29 determines if an abort time was specified in the message
• the abort time is used to ensure that a call is not completed at an inconvenient time. If an abort time has not been specified, a default abort time is computed (step 210) using the time specified in the message header that indicates when the message was sent, plus a pre-determined default interval, say 5 minutes. In either case, the abort time is compared to the system time to determine whether it has expired (step 212) . If the abort time has expired, an abort message is formulated (step 214) and the conference scheduler database application 29 transmits it to the originator identity extracted from the message header (step 216) , at which point it waits for the receipt of another message.
• the conference scheduler database application 29 determines if the message is a Scheduling Request message (step 218) . If not, it proceeds to step 252, described below.
• the originator identity is extracted from the message header and used as a key to search the profiles database 27a to determine if the originator is entitled to request a conference call (step 220) : If a customer profile cannot be located (step 222) , the conference scheduler database application 29 formulates an appropriate error message (step 204) and transmits it to the originator identity extracted from the message header (step 206) , at which point it waits for the receipt of another message.
• the customer profile record is retrieved (step 224) . Credit is checked with the corresponding entry in the billing database 27b
• step 226) If the subscriber lacks credit to initiate the call, the conference scheduler database application 29 formulates an appropriate error message (step 204) and transmits it to the originator identity extracted from the message header (step 206) , at which point it waits for the receipt of another message. If the credit is acceptable, the message is examined to determine whether the originating number was explicitly specified (step 228) . If no originating number was specified in the text message, the originating number is extracted from the subscriber profile
• the originating number is checked to ensure that it conforms to a known number plan (step 232) . If not, the conference scheduler database application 29 formulates an appropriate error message (step 204) and transmits it to the originator identity extracted from the message header (step 206) , at which point it waits for the receipt of another message.
• the conference scheduler database application 29 assigns a CBN to the requested conference call (step 238) and creates a new call entry in the conference database 27c (step 240) .
• the conference scheduler database application 29 adds the originating information (both the telephone number and the text message address) into the new call entry (step 242) .
• the conference scheduler database application 29 also extracts all of the destination information specified in the received text message and adds each set into the new call entry (steps 244 and 246) .
• the conference scheduler database application 29 thereupon formulates an invitation message containing the CBN, and if a scheduled call, the date/time (step 248) and transmits it to the originating and destination text message addresses (step 250) , at which point it waits for the receipt of another message.
• the originator who specified this in the Scheduling Request message, is aware of this fact, and will communicate directly with the proposed participants.
• the conference scheduler database application 29 may be provided with access to an IVR 10, whereupon a recorded voice message may be sent to the telephone number of each such proposed participant, conveying the details and requesting a response.
• the proposed participant will be requested to access either the web server 33 or to communicate by e-mail or other text means and transmit a response, whether using an Accept or Decline message as appropriate.
• the IVR 10 may also be used to solicit a response directly from the proposed participant at the end of the recorded voice message.
• a further possibility, which is adapted here, is that such proposed participants are marked as requiring confirmation by the service center 4 at the time that the conference call is initiated. For the purposes of the conference scheduler database application 29, they are presumed to have accepted the invitation. Thus, the service center 4 will attempt to set up the call and will request confirmation using the IVR 10 before bridging such calls into the conference call.
• the conference scheduler database application 29 determines if the message is an Accept message (step 252 FIG. 2b) . If not, it determines if it is a Decline message (step 254) .
• the conference database 27c is queried to determine if an acknowledgement is required for the particular participant (step 256) .
• An acknowledgement will be required only for those participants who are invited to join a conference call already in progress, or who have not otherwise been invited by the originator of the Scheduling Request message.
• the acknowledgment consists of a report to the originator of the Scheduling Request message indicating that the particular participant intends to join or is- joining the conference call.
• the conference scheduler database application 29 formulates an appropriate report message (step 258) and transmits it to the originator of the Scheduling Request message (step 260) .
• the conference scheduler database application 29 updates the call entry in the conference database 27c corresponding to the specified CBN to reflect the response from the particular participant (step 262) .
• step 264 the conference scheduler database application 29 waits for the receipt of another message.
• a timeout period may be established beyond which the conference scheduler database application 29 no longer waits for responses.
• the conference scheduler database application 29 formulates a status report (step 266) and transmits it to the originator of the Scheduling Request message (step 268) .
• step 272 If the requested conference call was to take place immediately, or when the scheduled time has arrived (step 272) , the conference scheduler database application 29 writes call requests to the call queue 27d corresponding to the appropriate service center 4 and waits for the receipt of another message (step 274) .
• step 272 during which the conference scheduler database application 29 waits for the scheduled time to arrive, does not mean that the conference scheduler database application 29 is unable to process other messages related to other conference calls in the interim.
• Step 272 merely serves to indicate that the call request is not written to the call queue 27d until the scheduled time has arrived.
• the conference scheduler database application 29 determines if the message is a Forward message (step 276) . If not, the message must be a Join message.
• the conference scheduler database application 29 updates the call entry in the conference database 27c corresponding to the specified CBN to reflect that a specified conference number is being replaced by a new conference number (step 278) . If the conference call is already underway (step 280) , the conference scheduler database application 29 writes a call request to the call queue 27d corresponding to the appropriate service center 4 (step 282) . Thereafter, the conference schedule -database application 29 waits- for -the receipt of another message. Optionally, the conference scheduler database application 29 may also formulate an appropriate report message and transmit it to the originator of the Forward message (not shown) .
• the message must be a Join message.
• the conference scheduler database application 29 determines if destination information has been specified in the message (step 284 FIG. 2c) . If so, the message is presumed to have been sent from a current participant in the conference call in respect of a proposed participant.
• the conference scheduler database application 29 therefore updates the call entry in the conference database 27c corresponding to the specified CBN to add the specified destination information (step 286) , sets the acknowledgement flag for this entry (step 288)-, formulates an invitation message containing the CBN and optionally the date/time (step 290) and transmits it to the specified destination text message address (step 292) , at which point it waits for the receipt of another message.
• step 264 the server will determine that the decision "All responses received?" (step 264) will be true. As well, the conference call is already underway. Therefore, a call request is written to the call queue (step 274) to join the new participant to the conference call.
• the conference database need merely be updated.
• the recipient of the Join invitation will be connected to the call together with all other participants, when the call is initiated.
• the message is presumed to have been sent by a proposed participant who has been given the CBN by an existing participant.
• the CBN could have been communicated by the transmission of an SMS message from the existing participant to the proposed participant.
• the conference scheduler database application 29 updates the call entry in the conference database 27c corresponding to the specified CBN to add the call termination information extracted from the message (step 294) .
• the conference scheduler database application 29 If the conference call is already underway (step 296) , the conference scheduler database application 29 writes a call request to the call queue 27d of the appropriate service center 4 (step 298) . Thereafter, the conference scheduler database application 29 awaits the -receipt of another message. Optionally, the conference scheduler database application 29 may also formulate an appropriate report message and transmit it to the originator of the Join message (not shown in the flow chart) .
• conference scheduler database application processing is related to a specific network configuration and implementation and text messages may be processed in many other ways to achieve the same result without departing from the spirit and scope of the invention.
• FIG. 3 is a flow diagram showing principal steps performed by a call controller 8, when a call request is written in steps 274, 282 or 298 of FIG. 2.
• the call controller 8 retrieves a call request from the call queue 27d
• step 300 The call controller 8 determines if the call request is for a conference call (step 302) . If not, it proceeds to step 350 described below.
• the call controller 8 instructs the POP 6 to dial the originating number specified in the call request (step 304) .
• the call controller 8 polls the POP 6 to determine when the call has been set up (step 306) . After a predetermined time, the call controller 8 determines whether the call has been answered (step 308) . If the call has not been answered, an error message is formulated (step 310) and returned to the requester (step 312) , after which the call controller 8 retrieves another call request .
• the call controller 8 instructs the POP 6 to dial one of the remaining destination numbers specified in the call request (step 314) .
• the call controller 8 polls the POP 6 to determine when the call has been set up (step 316) . After a predetermined time, the call controller 8 determines whether the call has been answered (step 318) . If the call has not been answered, an error message is formulated (step 318) and returned to the requester (step 319) , after which the call controller 8 proceeds to step 340, to process other destination numbers that may have been specified.
• the call controller 8 determines whether the dialed destination number is one for which acceptance of the conference call must be solicited (step 320) . As discussed previously, this would be the case if the proposed participant has no text message address and was unable to accept or decline the conference call previously.
• an instruction message is sent by the call controller 8 to the IVR 10 instructing the IVR 10 to play a predetermined recorded voice message and solicit a response as to whether the proposed participant wishes to accept or decline the conference call (step 322) .
• the response may be a voice response or a digit input using the tel-ephone dial pad.
• the call controller 8 thereafter awaits a response from the IVR 10 (step 324) .
• the call controller 8 determines if the conference call was accepted or declined (step 326) .
• the call controller 8 releases the call to the IVR 6 (step 328) and instructs the POP 6 to bridge the destination telephone call with the ongoing conference call (step 330) , which includes the originating telephone call and any previous destination calls bridged therewith. If the conference call is declined, the call controller 8 releases the call to the destination telephone (step 332) , releases the call to the IVR 6 (step 334) , formulates an error message
• step 336 which it returns to the requester (step 338) .
• the call controller 8 determines if any more destination telephone calls remain to be made (step 340) . If so, the call controller 8 proceeds to step 314 discussed above. If not, the call controller 8 passes call information to the billing database 27b (step 342) .
• the call controller 8 polls the POP 6 for call progress (step 344) . If the call controller 8 determines that the conference call has not been terminated (step 346) , it polls the POP 6 again after a predetermined time lapse.
• the call controller 8 passes call information, including the termination time to the billing database 27b (step 348) , after which the call- controller— -retrieves- another call request .
• step 346 which indicates that the call controller continuously polls the POP 6 until it is determined that the conference call has been terminated, 5. does not mean that it is unable to process other received call requests relating to other calls in the interim. Rather, it merely serves to indicate that the call information is not passed to the billing database 27b until the call has been terminated.
• the call controller 8 determines if the call request is a call forward request (step 350) . If not, the call request 5 must be a call join request and the call controller 8 proceeds to step 362 discussed below.
• the call controller 8 instructs the POP 6 to dial the destination number specified in the call request 0 (step 352) .
• the call controller 8 polls the POP 6 to determine when the call has been set up (step 354) . After a predetermined time, the call controller 8 determines whether the call has been answered (step 356) . If the call has not been answered, an error message is 5 formulated (step 310) and returned to the requester (step 312) , after which the call controller 8 retrieves another call request.
• the call controller 8 instructs the POP 6 to bridge the destination telephone ' call with the ongoing conference call (step 358) , which comprises the originating telephone call and any previous destination calls bridged therewith.
• the call controller 8 thereafter releases the call to the originating number specified in the call request, which had been previously bridged into the ongoing conference call (step 360) , after which the call controller 8 retrieves another call request.
• the call request must be a call join request.
• the call controller 8 instructs the POP 6 to dial the destination number specified in the call request (step 362) .
• the call controller 8 polls the POP 6 to determine when the call has been set up (step 364) . After a predetermined time, the call controller 8 determines whether the call has been answered (step 366) . If the call has not been answered, an error message is formulated (step 310) and returned to the requester (step 312) , after which the call controller 8 retrieves another call request.
• the call controller 8 instructs the POP 6 to bridge the destination telephone call with the ongoing conference call (step 368) , which comprises the originating telephone call and any previous destination calls bridged therewith, after which the call controller 8 retrieves another call request.
• the foregoing overview of call controller processing is related to a specific network configuration and implementation and call requests may be processed in many other ways to achieve the same result without departing from the spirit and scope of the invention.
• FIGS. 4-7 are call flow diagrams that illustrate principal steps in exemplary calls established using the methods and system in accordance with the present invention.
• FIG. 4 shows the call flow for a successful attempt to arrange a conference call on a scheduled basis.
• cellular telephone 16b is the originator of the conference call request, and wishes to join in WAP telephone 12 and cellular telephone 16a.
• the customer at cellular telephone 16b sends a Scheduling Request message containing the requisite details by SMS to MSC 20b (step 400)
• the message is in turn forwarded to conference scheduler database application gateway 30 and eventually to the conference scheduler database application 29 (steps 401-402) .
• the conference scheduler database application 29 determines if it is parsible (step 403. If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b through the SMS gateway 23, MSC 20b and the cellular telephone 16b (steps 404-406) .
• the conference scheduler database application 29 determines if the abort time has expired, as described above with reference to FIG. 2 (step 407) . If so, the conference scheduler database application 29 returns an abort message to the customer at cellular telephone 16b along the same path. If the abort time has not expired, the conference scheduler database application 29 accesses the customer's profile from the profile database 27a, as described above with reference to FIG. 2 (step 411) and determines if the conference call may be arranged (step 412) . If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b along the same path as described above with reference to steps 404-406 (steps 413-415) .
• the conference scheduler database application 29 confirms that the originating number conforms to a known number plan (step 416) . If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b along the same path. If the originating number is accurate, the conference scheduler database application 29 assigns a conference bridge number (CBN) and creates a new entry in the conference database 27c, as described above with reference to FIG. 2 (step 420) .
• CBN conference bridge number
• the conference scheduler database application 29 thereafter formulates an invitation message that it forwards to the SMS gateway 23 (step 421) for transmission to the WAP telephone 12 and cellular telephone 16a.
• the SMS gateway 23 forwards the invitation message to MSC 20a (step 422) , which forwards it to cellular telephone 16a (step 423) .
• the SMS gateway 23 also forwards the invitation message to MSC 20b (step 424) , which forwards it to WAP telephone 12 (step 425) .
• the WAP telephone 12 transmits an Accept or Decline message that it forwards through MSC 20b, conference scheduler gateway 30 and the conference scheduler database application 29 (steps 426-428) .
• the conference scheduler database application 29 determines if the message is a Decline message (step 429) . If so, it transmits a report message to this effect to the customer at cellular telephone 16b along the same path as steps 404-406 (steps 430-432) . In either event, the conference scheduler database application 29 updates the conference database 27c (step 433) .
• Cellular telephone 16a also transmits an Accept or Decline message that it forwards through MSC 20a, conference scheduler gateway 30 and the conference scheduler database application 29 (steps 434-436) .
• the conference scheduler database application 29 determines if the message is a Decline message (step 437) . If so, it transmits a report message to this effect to the customer at cellular telephone 16b along the same path as steps 404-406 (steps 438-440) . In either event, the conference scheduler database application 29 updates the conference database 27c (step 441) . Once the conference scheduler database application 29 determines that all invitees have responded with either an Accept or Decline message
• step 442 it transmits a report message listing the participants to the customer at cellular telephone 16b along the same path as steps 404-406 (steps 443-445) .
• the conference scheduler database application waits until the scheduled time before proceeding to request that the conference call be established, as described below in FIG. 5
• FIG. 5 shows the call flow for a successful attempt to establish a previously scheduled conference call.
• cellular telephone 16b is the originator of the conference call request, and wishes to join in WAP telephone 12 and cellular telephone 16a.
• the conference scheduler database application 29 writes a call request record to the call queue 27d (step 501) .
• the call controller 8 polls the call queue 27d on a regular basis (step 502) and retrieves call requests written to the call queue (step 503) .
• call controller 8 sends an instruction to the POP 6 to set up a call connection to the specified originating number (step 504) .
• the POP 6 thereupon formulates a call setup message (an Integrated Services
• IAM IAM
• PSTN 24 forwards the call setup message into the PSTN 24 (step 505) which forwards the message through the PSTN 24 to the MSC 20b (step 506) .
• the IAM message will be forwarded through the PSTN 24 along the CCS network 22 that directs connections through the PSTN 24, however this has been omitted from FIGs . 5-8 for simplicity.
• the MSC 20b On receipt of the IAM, the MSC 20b applies ringing to the cellular telephone 16b (step 507) and returns an Address Complete (ACM) message through the PSTN 24 to the POP 6 (steps 508-509) . Subsequently, the cellular telephone 16b is answered (step 510) , which causes the MSC 20b to return an Answer (ANM) message through the PSTN 24 to the POP 6 (steps 511-512) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 513) and retrieves the call status when it is available (step 514) . The information retrieved informs the call controller 8 that the first call to the originating number has been completed. The call controller thereupon sends an instruction to the POP 6 to set up a call connection to the first specified destination number, corresponding to WAP telephone 12
• step 515) The POP 6 thereupon formulates a call setup message and forwards the call setup message into the
• PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the PSTN 24 (step 516) which forwards the message to the
• the MSC 20b (step 517) .
• the MSC 20b applies ringing to the WAP telephone 12 (step 518) and returns an Address Complete (ACM) message through the PSTN 24 to the POP 6 (steps 519-520) .
• ACM Address Complete
• the WAP telephone . 12 is answered (step 521), which causes the MSC 20b to return an Answer (ANM) message through the PSTN 24 to the ' POP 6 (steps 522-523) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 524) and retrieves the call status when it is available (step 525) .
• the information retrieved informs the call controller 8 that the second call to the first destination number has been completed.
• the call controller 8 thereupon instructs the POP 6 to bridge the calls together (step 526) .
• the call controller then sends an instruction to the POP 6 to set up a call connection to the second specified destination number, corresponding to cellular telephone 16a (step 530) .
• the POP 6 thereupon formulates a call setup message and forwards the call setup message into the PSTN 24 (step 531) which forwards the message through the PSTN 24 to the MSC 20a (step 532) .
• the MSC 20a On receipt of the IAM, the MSC 20a applies ringing to cellular telephone 16a (step 533) and returns an Address Complete (ACM) message through the PSTN 24 to the POP 6 (steps 534-535) .
• ACM Address Complete
• cellular telephone 16a is answered (step 536) , ' which causes the MSC 20a to return an Answer (ANM) message through the PSTN 24 to the POP 6 (steps 537-538) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 539) and retrieves the call status when it becomes available (step 540) .
• the information retrieved informs the call controller 8 that the third call to the second destination number has been answered.
• the call controller 8 then instructs the POP 6 to bridge the calls together (step 541) .
• the call controller 8 therefore sends an information record to the billing database 27b instructing that a billing transaction be created for the call (step 545) .
• a Release message is generated, in this case by MSC 20b (step 547) , which is forwarded through the PSTN 24 to the POP 6 (step 548) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 549) and retrieves the call status when it is available (step 550) .
• the information retrieved informs the call controller 8 that WAP telephone 12 has gone on hook. Meanwhile, the POP 6 acknowledges this with a Release Complete (RLC) message sent back to the PSTN (step 551) .
• RLC Release Complete
• a Release message is generated, in this case by MSC 20b (step 553), which is forwarded through the PSTN 24 to the POP 6 (step 554) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 555) and retrieves the call status when it is available (step 556) .
• the information retrieved informs the call controller 8 that cellular telephone 16b has gone on hook. Meanwhile the POP 6 acknowledges the Release message with a Release Complete
• the call controller 8 therefore sends an information record to the billing database 27b instructing that a billing transaction be created for the call (step 558) .
• the call flow for a conference call on an immediate basis will consist of the call flows shown in FIG.4 followed immediately by the call flows shown in FIG. 5. That is to say, the wait step (step 446) is omitted.
• FIG. 6 shows the call flow for a successful attempt to arrange a conference call involving ,a participant using a wireline telephone and without text message capability.
• cellular telephone 16b is the originator of the conference call request, and wishes to join in wireline telephone 2 and cellular telephone 16a.
• steps 515 through 526 are omitted and are replaced with steps 615-636, described below.
• the call controller sends an instruction to the POP 6 to set up a call connection to the first specified destination number, in this case corresponding to wireline telephone 2 (step 615) .
• the POP 6 thereupon formulates a call setup message and forwards the call setup message into the PSTN 24 (step 616) which forwards the message through the PSTN 24 to the switch, for example an SSP, that controls wireline telephone 2a (step 617) .
• the switch On receipt of the IAM, the switch applies ringing to the wireline telephone 2 (step 618) and returns an Address Complete (ACM) message through the PSTN 24 to the POP 6 (steps 619-620) .
• ACM Address Complete
• the wireline telephone 2a is answered (step 621) , which causes the SSP to return an Answer (ANM) message through the PSTN 24 to the POP 6 (steps 622-623) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 624) and retrieves the call status when it is available (step 625) .
• the information retrieved informs the call controller 8 that the second call to the first destination number has been completed.
• the call controller 8 in this case notes that confirmation that the conference call is accepted needs to be obtained, as explained above with reference to FIG. 3. It instructs the POP 6 to activate the IVR 10 (step 626) .
• the POP 6 is connected to the IVR 10 by a Small Message Desk Interface (SMDI) or an ISDN Private Rate Interface (PRI) and sends an ISDN setup message to the IVR 10 (step 627) .
• SMSI Small Message Desk Interface
• PRI ISDN Private Rate Interface
• the IVR 10 responds with an Acknowledge message (step 628) and an Answer message (step 629) .
• the call controller 8 periodically polls the POP 6 to determine call status (step 630) and retrieves the call status when it is available (step 631) .
• the information retrieved informs the call controller 8 that the third call to the second destination number has been answered.
• the call controller 8_ _then sends a message, for example through a TCP/IP connection to the IVR 10 instructing the IVR 10 to query the customer to determine whether they wish to accept the conference call connection being established (step 632) .
• the IVR 10 plays an appropriate recorded voice message, which is heard by the proposed participant at the wireline telephone 2 (step 633) .
• the proposed participant delivers a response, say by inputting digits using the telephone dial pad (step 634) .
• the proposed participant could be prompted to deliver a voice response which is recorded and analyzed.
• the response is captured by the IVR 10 and returned to the call controller 8 along the TCP/IP connection (step 635) . In this example, it is assumed that the response is to accept the conference call .
• the call controller 8 thereupon instructs the POP to bridge the calls together (step 636) .
• Processing from this point forward generally follows the sequence set out in FIG. 5 at step 530 onward .
• FIG. 7 shows the call flow for two successful attempts by a participant to join an ongoing conference call at the invitation of an existing participant.
• cellular telephone 16b is a current participant of the ongoing conference call and wishes that cellular telephone 16a join in the conference call.
• cellular telephone 16b transmits, by SMS message to cellular telephone 16a, the CBN corresponding to the ongoing conference call and cellular telephone 16a transmits a Join request to the conference scheduler database application 29.
• the customer at cellular telephone 16b sends a message containing the CBN by SMS to MSC 20b (step 700) .
• the message is forwarded in turn to MSC 20a and eventually to cellular telephone 16a (step 701-702) .
• the customer at cellular telephone 16a sends a Join message by SMS to MSC 20a (step 703) .
• the message is in turn forwarded to conference scheduler gateway 30 and eventually to the conference scheduler database application 29 (steps 704, 707) .
• the conference scheduler database application 29 determines if it is parsible (step 708) . If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b along the same path as shown in steps 404-406 of FIG. 4 (step 709 shown but remaining are not illustrated) .
• the conference scheduler database application 29 determines if the abort time has expired, as described above with reference to
• step 710 the conference scheduler database application 29 returns an abort message to the customer at cellular telephone 16b along the same path as steps 404-406 (step 711 shown but remaining steps are not illustrated) . If the abort time has not expired, the conference scheduler database application 29 updates the entry in the conference database 27c to reflect the Join request, as described above with reference to FIG. 2 (step 712) . The conference scheduler database application 29 thereafter determines if the conference call is already underway (step 722) . Having determined that it is, the conference scheduler database application 29 writes a call request record to the call queue 27d (step 723) .
• the processing which follows is common to both the first attempt (flows shown above the first dotted line) and the second attempt (flows shown between the first and second dotted line) .
• the flows for the common processing are shown below the second dotted line.
• the call controller 8 polls the call queue 27d on a regular basis (step 725) and retrieves call requests written to the call queue (step 726) .
• call controller 8 When a Join request is retrieved, call controller 8 sends an instruction to the POP 6 to set up a call connection to the specified destination number, corresponding to cellular telephone 16a (step 727) .
• POP 6 thereupon formulates a call setup message and forwards the call setup message into the PSTN 24
• step 728 which forwards the message through the PSTN 24 to the MSC 20a (step 729) .
• the MSC 20a On receipt of the IAM, the MSC 20a applies ringing to cellular telephone 16a
• step 730 and returns an Address Complete (ACM) message through the PSTN 24 to the POP 6 (steps 731-732) .
• ACM Address Complete
• step 733 which causes the MSC 20a to return an Answer (ANM) message through the PSTN 24 to the POP 6
• the call controller 8 periodically polls the POP 6 to determine -call status (step 736) and retrieves the call status when it is available
• step 737 The information retrieved informs the call controller ' 8 that the third call to the second destination number has been completed.
• the call controller 8 thereupon instructs the POP to bridge the calls together (step 738) . Processing from this point forward generally follows the sequence set out in FIG. 5 at step 545 onward.
• cellular telephone 16b transmits a Join request to the conference scheduler database application 29.
• the processing for this attempt is identical to the processing for the first attempt, with the exception that steps 700-704 are replaced by steps 705-706 and steps 713-721, described below are introduced after step 712 and before step 722.
• Cellular telephone 16b sends a Join message by SMS to MSC 20b (step 705) .
• the message is forwarded to conference scheduler gateway 30 (step 706) and eventually to the conference scheduler database application 29 (step 707) .
• the conference scheduler database application 29 determines if it is parsible (step 708) . If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b backwards along the same path as shown in steps 404-406 of FIG. 4 (step 709 shown but remaining flows omitted) . If the message is parsible, the conference scheduler database application- 29 determines if the abort time has expired, as described above with reference to FIG. 2 (step 710) .
• the conference scheduler database application 29 returns an abort message to the customer at cellular telephone 16b along the same path as steps 404-406 (step 711 shown but remaining flows omitted) . If the abort time has not expired, the conference scheduler database application 29 updates the entry in the conference database 27c to reflect the Join request, as described above with reference to FIG. 2 (step 712) .
• the conference scheduler database application 29 thereafter formulates an invitation message that it forwards to the SMS gateway 23 (step 713) for transmission to cellular telephone 16a.
• the SMS gateway 23 forwards the invitation message to MSC 18a
• step 714 which forwards it to cellular telephone 16a (step 715) .
• the cellular telephone 16a transmits an
• the conference scheduler database application 29 determines if the message is a Decline message (step 19) . If so, it transmits a report message to this effect to the customer at cellular telephone 16b along the same path as steps 404-406 (step 720 shown but remaining flows omitted) . In either event, the conference scheduler database application 29 updates the conference database 27c (step 721) . Processing from this point forward generally follows the sequence set out in FIG. 7 at step 722 onward, as discussed above . . . _ Forwarding an Ongoing Conference Call
• FIG. 8 shows the call flow for a successful attempt by a participant to forward an ongoing conference call from one telephone number to another.
• cellular telephone 16b is a present participant of the ongoing conference call and wishes to continue its participation in the conference call using wireline telephone 2.
• the customer at cellular telephone 16b sends a Forward message by SMS to MSC 20b (step 801) .
• the message is in turn forwarded to conference scheduler gateway 30 and to the conference scheduler database application 29 (steps 802-803) .
• the conference scheduler database application 29 determines if it is parsible (step 804) . If not, the conference scheduler database application 29 returns an error message to the customer at cellular telephone 16b backwards along, the same path as shown in steps 404-406 of FIG. 4 (step 805 shown but remaining flows omitted) . If the message is parsible, the conference scheduler database application 29 determines if the abort time has expired, as described above with reference to FIG. 2 (step 806) .
• the conference scheduler database application 29 returns an abort message to the customer at cellular telephone 16b along the same path as steps 404-406 (step 807 shown but remaining flows omitted) . If the abort time has not expired, the conference scheduler database application 29 updates the entry in the conference database 27c to reflect the forward request, as described above with reference to FIG. 2. (step 808).
• the conference scheduler database application 29 writes a call request record to the call queue 27d (step 809) .
• the call controller 8 polls the call queue 27d on a regular basis (step 810) and retrieves call requests written to the call queue (step 811) .
• the call controller When a Join request is retrieved, the call controller sends an instruction to the POP 6 to set up a call connection to the specified destination number, in this case corresponding to wireline telephone 2a (step 812) .
• the POP 6 thereupon formulates a call setup message and forwards the call setup message into the PSTN 24 (step 813) which forwards the message through the PSTN 24 to the switch, for example an SSP that controls wireline telephone 2 (step 814) .
• the switch On receipt of the IAM, the switch applies ringing to the wireline telephone 2 (step 815) and returns an Address
• step 816-817) the wireline telephone 2 is answered (step 818) , which causes the SSP to return an
• the call controller 8 periodically polls the POP 6 to determine call status (step 821) and retrieves the call status when it is available
• step 822 The information retrieved informs the call controller 8 that the call to the destination number has been completed.
• the call controller 8 thereupon instructs the POP to bridge the call to the ongoing conference call (step 823) .
• the call controller 8 also instructs the POP 6 to release the call to the original number used by the customer, in this case, to cellular telephone 16b
• step 824 The POP 6 thereupon formulates a Release message and forwards the Release message into the PSTN 24 (step 825) , which returns a Release complete message (step 826) forwards a Release the message through the PSTN 24 to MSC 20b (step 827) .
• MSC 20b On receipt of the Release message, MSC 20b plays a dial tone to cellular telephone 16b, which causes the customer to put the cellular telephone on hook (step 828) and returns a Release Complete (RLC) message through the PSTN 24 to the POP 6 (step 829) .
• RLC Release Complete
• the conference scheduler database application 29 is preferably provisioned to send a SMS message to each participant with a SMS enabled device that cannot be joined to the conference call, or is dropped from the call.
• the SMS message includes the CBN for the conference call and an invitation to join, or rejoin, the conference call.
• the conference scheduler application 29 After the participant receives the SMS message, he replies to the SMS message with a SMS message that includes the CBNV
• the conference scheduler application 29 checks the recipients telephone number against all primary and backup telephone numbers scheduled to participate in the call. If the participant's telephone number is among the telephone numbers of participants in the call, the ⁇ onference call scheduler database application 29 passes the telephone number to the CC 8, with instructions to bridge to the answered call to the conference call identified by the CBN. The CC 8 then calls the participant using the telephone number and bridges the participant to the conference call . This mechanism therefore provides a simple and convenient way to join participants who have missed or forgotten a conference call, or have been dropped from the call for any reason.
• the present invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in any combination thereof.
• Apparatus of the invention can be implemented in a computer program product tangibly embodied in a machine- readable storage device for execution by a programmable processor; and methods actions can be performed by a programmable processor executing a program of instructions to perform functions of the invention by operating on input data and generating output.
• the invention can be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one input device, and at least one output device.
• Each computer program can be implemented in a high-level procedural or object oriented programming language, or in assembly or machine language if desired; and in any case, the language can be a compiled or interpreted language.
• Suitable processors include, by way of example, both general and specific microprocessors. Generally, a processor will receive instructions and data from a readonly memory and/or a random access memory. Generally, a computer will include one or more mass storage devices for storing data files; such devices include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD disks. Any of the foregoing can be supplemented by, or incorporated in ASICs (application-specific integrated circuits) .
• ASICs application-specific integrated circuits
• Examples of such types of computers are programmable processing systems contained in the conference scheduler database application 29 and the call controller 8 shown in FIG. 1 suitable for implementing or performing the apparatus or methods of the invention.
• the system may comprise a processor, a random access memory, a hard drive controller and an input/output controller coupled by a processor bus.
• the conference scheduler gateway 30, conference scheduler database application 29 and service center 4 need not be located in physically disparate locations as shown in FIG. 1. Rather, it is possible for the conference scheduler gateway 30, which is in wireless communication with SMS users, to be directly connected to the call controller 8.
• the call controller 8 may either contain all the functionality of the conference scheduler database application 29, or be directly connected with it.
• the databases 27 may be directly accessed by the call controller 8, or remain accessible by Ethernet communication as is shown in FIG. 1. In this fashion, there is no need to connect through the Internet in order to receive requests from users. Nevertheless, the well -developed hierarchy for sending SMS messages to wireless customers through the Internet 26 and an SMS gateway 23 is well understood and may continue to be appropriated .

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Multimedia (AREA)
• General Engineering & Computer Science (AREA)
• Telephonic Communication Services (AREA)
• Mobile Radio Communication Systems (AREA)
• Pharmaceuticals Containing Other Organic And Inorganic Compounds (AREA)
• Saccharide Compounds (AREA)
• Low-Molecular Organic Synthesis Reactions Using Catalysts (AREA)

Applications Claiming Priority (3)

Publications (2)

Family

ID=23291160

Family Applications (1)

Country Status (6)

Cited By (2)

Families Citing this family (137)

Family Cites Families (9)

• 2002
  • 2002-10-30 EP EP02769806A patent/EP1442625B1/fr not_active Expired - Lifetime
  • 2002-10-30 WO PCT/CA2002/001630 patent/WO2003039181A1/fr not_active Application Discontinuation
  • 2002-10-30 US US10/496,830 patent/US20050078612A1/en not_active Abandoned
  • 2002-10-30 AT AT02769806T patent/ATE485688T1/de not_active IP Right Cessation
  • 2002-10-30 DE DE60238073T patent/DE60238073D1/de not_active Expired - Lifetime
• 2005
  • 2005-02-04 HK HK05100991.4A patent/HK1071266A1/xx not_active IP Right Cessation
• 2008
  • 2008-06-26 US US12/146,783 patent/US20090093240A1/en not_active Abandoned

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events