DESCRIPTION
TECHNICAL FIELD
The invention generally relates to conference calling through cellular phones. More
particularly, the invention relates to improving conference calling by way of providing a
conference calling application in the cellular phones.
BACKGROUND
One of existing solutions for conference calling is to use any of operator-deployed
platforms, commonly known as bridge. However, there are certain problems in such use of
such operator-deployed platforms. Firstly, a subscriber needs to take bridge details from the
operator. Further, the subscriber needs to manually request each participant to join the bridge.
After that, each participant dials the conference number and enters a passcode to join the
conference call. For small duration conference or less number of participants, these activities
are quite time consuming. Moreover, all the participants need to remember the conference
number and the passcode in order to join the conference call.
Another existing solution is to bridge the multiple calls into the conference call
through the cellular phone. However, this may be a tedious task for a user, as the user has to
put an ongoing call on hold, and then answer or dial the second call. After that, all such calls
are manually bridged into the conference call. This process clearly affects the flow of the
conversation. Sometimes, the user may experience call drop due to so many activities that the
user needs to do during the call.
Another existing solution is to provide an application in the cellular phone, which is
dedicated to conference calling. However, such applications are generally operator specific,
which merely provide a mobile interface for sharing conference number and the passcode.
In present scenario, users continue to use these inefficient and tedious solutions for
conference calling. Due to this inefficiency and tediousness, the users may not opt of
conference calling sometimes and hence operators miss out additional revenue. To this end,
there is a scope of lot of improvements in this area of technology.
3
SUMMARY OF THE INVENTION
In accordance with the purposes of the invention, the present invention as embodied
and broadly described herein, provides improved conference calling through a conference
calling application in a cellular phone. This conference calling application is configured to
receive certain input details from a user. Further, the conference calling application allows
adding participants manually or through the phonebook of the cellular phone. Once the
conference call is booked, the conference calling application automatically sends a
notification to each participant. The notification may be in the form of a SMS, email, and/or
instant message. Participant’s response to the notification is also reflected in the user
interface of the conference calling application. At the time of conference call, participants are
required to establish a call with the contact number of the user only, than an unfamiliar bridge
number used in conventional bridge solutions. Further, calls established with intended
participants are automatically merged into the conference call without requiring any passcode
from the intended participants. Furthermore, non-intended participants could also join the
conference call by providing the passcode, otherwise indication relevant announcement may
be played and/or a predefined message is sent. At the end of the conference call, a report with
a summary of the conference call may be published. The conference calling application also
provides the features of recording the conference call and storing it locally on the cellular
phone or on a shared location at a cloud sever. The conference calling application is not
required as such on the participant’s end. However, if it is there, the participants can get
enriched user experience.
The advantages of the invention include, but are not limited to increased security, ease
of use, self-setup of conference call, no dependency on external conference providers or
operators, reduced load at operators, conference calling at normal rates of calling,
uninterrupted call flow, inbuilt notification to participants, passcode being made optional,
automatic calling to start the conference, and increase in revenue.
These and other aspects as well as advantages will be more clearly understood from
the following detailed description taken in conjunction with the accompanying drawings and
claims.
4
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS:
To further clarify advantages and aspects of the invention, a more particular
description of the invention will be rendered by reference to specific embodiments thereof,
which is illustrated in the appended drawings. It is appreciated that these drawings depict
only typical embodiments of the invention and are therefore not to be considered limiting of
its scope. The invention will be described and explained with additional specificity and detail
with the accompanying drawings, which are listed below for quick reference.
Figure 1 illustrates an exemplary method for facilitating a multi-party conference call
in a cellular phone through a conference calling application, in accordance with an
embodiment of present invention.
Figure 2 illustrates an exemplary method for setting up the multi-party conference call
beforehand, in accordance with an embodiment of present invention.
Figure 3a illustrates an exemplary cellular phone that facilitates a multi-party
conference call, in accordance with an embodiment of present invention.
Figure 3b illustrates an exemplary network environment that facilitates a multi-party
conference call, in accordance with an embodiment of present invention.
Figure 4 illustrates an exemplary use case for conference calling without passcode, in
accordance with an embodiment of present invention.
Figure 5 illustrates an exemplary use case for conference calling with passcode, in
accordance with an embodiment of present invention.
Figure 6 illustrates an exemplary screen for registration, in accordance with an
embodiment of present invention.
Figure 7 illustrates an exemplary screen for authentication, in accordance with an
embodiment of present invention.
Figure 8 illustrates an exemplary home screen of the conference calling application, in
accordance with an embodiment of present invention
5
Figure 9 illustrates an exemplary screen for managing busy messages, in accordance
with an embodiment of present invention
Figure 10 illustrates an exemplary screen for managing groups, in accordance with an
embodiment of present invention.
Figure 11 illustrates an exemplary screen for conference setup, in accordance with an
embodiment of present invention.
It may be noted that to the extent possible, like reference numerals have been used to
represent like elements in the drawings. Further, those of ordinary skill in the art will
appreciate that elements in the drawings are illustrated for simplicity and may not have been
necessarily drawn to scale. For example, the dimensions of some of the elements in the
drawings may be exaggerated relative to other elements to help to improve understanding of
aspects of the invention. Furthermore, the one or more elements may have been represented
in the drawings by conventional symbols, and the drawings may show only those specific
details that are pertinent to understanding the embodiments of the invention so as not to
obscure the drawings with details that will be readily apparent to those of ordinary skill in the
art having benefit of the description herein.
DETAILED DESCRIPTION
It should be understood at the outset that although illustrative implementations of the
embodiments of the present disclosure are illustrated below, the present invention may be
implemented using any number of techniques, whether currently known or in existence. The
present disclosure should in no way be limited to the illustrative implementations, drawings,
and techniques illustrated below, including the exemplary design and implementation
illustrated and described herein, but may be modified within the scope of the appended
claims along with their full scope of equivalents.
The term “some” as used herein is defined as “none, or one, or more than one, or all.”
Accordingly, the terms “none,” “one,” “more than one,” “more than one, but not all” or “all”
would all fall under the definition of “some.” The term “some embodiments” may refer to no
embodiments or to one embodiment or to several embodiments or to all embodiments.
6
Accordingly, the term “some embodiments” is defined as meaning “no embodiment, or one
embodiment, or more than one embodiment, or all embodiments.”
The terminology and structure employed herein is for describing, teaching and
illuminating some embodiments and their specific features and elements and does not limit,
restrict or reduce the spirit and scope of the claims or their equivalents.
More specifically, any terms used herein such as but not limited to “includes,”
“comprises,” “has,” “consists,” and grammatical variants thereof do NOT specify an exact
limitation or restriction and certainly do NOT exclude the possible addition of one or more
features or elements, unless otherwise stated, and furthermore must NOT be taken to exclude
the possible removal of one or more of the listed features and elements, unless otherwise
stated with the limiting language “MUST comprise” or “NEEDS TO include.”
Whether or not a certain feature or element was limited to being used only once,
either way it may still be referred to as “one or more features” or “one or more elements” or
“at least one feature” or “at least one element.” Furthermore, the use of the terms “one or
more” or “at least one” feature or element do NOT preclude there being none of that feature
or element, unless otherwise specified by limiting language such as “there NEEDS to be one
or more . . . ” or “one or more element is REQUIRED.”
Unless otherwise defined, all terms, and especially any technical and/or scientific
terms, used herein may be taken to have the same meaning as commonly understood by one
having an ordinary skill in the art.
Reference is made herein to some “embodiments.” It should be understood that an
embodiment is an example of a possible implementation of any features and/or elements
presented in the attached claims. Some embodiments have been described for the purpose of
illuminating one or more of the potential ways in which the specific features and/or elements
of the attached claims fulfil the requirements of uniqueness, utility and non-obviousness.
Use of the phrases and/or terms such as but not limited to “a first embodiment,” “a
further embodiment,” “an alternate embodiment,” “one embodiment,” “an embodiment,”
“multiple embodiments,” “some embodiments,” “other embodiments,” “further
embodiment”, “furthermore embodiment”, “additional embodiment” or variants thereof do
NOT necessarily refer to the same embodiments. Unless otherwise specified, one or more
7
particular features and/or elements described in connection with one or more embodiments
may be found in one embodiment, or may be found in more than one embodiment, or may be
found in all embodiments, or may be found in no embodiments. Although one or more
features and/or elements may be described herein in the context of only a single embodiment,
or alternatively in the context of more than one embodiment, or further alternatively in the
context of all embodiments, the features and/or elements may instead be provided separately
or in any appropriate combination or not at all. Conversely, any features and/or elements
described in the context of separate embodiments may alternatively be realized as existing
together in the context of a single embodiment.
Any particular and all details set forth herein are used in the context of some
embodiments and therefore should NOT be necessarily taken as limiting factors to the
attached claims. The attached claims and their legal equivalents can be realized in the context
of embodiments other than the ones used as illustrative examples in the description below.
Figure 1 illustrates an exemplary method (100) for facilitating a multi-party
conference call in a cellular phone through a conference calling application, in accordance
with an embodiment of present invention. In said embodiment, the method (100) comprises:
establishing (101) a call with a first contact number, wherein the first contact number is an
invitee to the multi-party conference call; monitoring (102) in a background state an
incoming call from a second contact number; and automatically merging the incoming call
with the already established call to create the multi-party conference call if the second contact
number pertaining to the incoming call is in an invitee list to the multi-party conference call,
or a designated passcode is received during the incoming call (steps 103 a-d).
In a further embodiment, the method (100) comprises playing (104) a relevant
announcement to the second contact number if the passcode is incorrect for a predefined
number of times or not received. Additionally, a predefined message, such as “user is busy in
a conference call” may be sent to the second contact number.
In a further embodiment, the method (100) comprises recording (105) the conference
call; and storing (106) the recorded conference call in a memory storage of the cellular phone
or at a shared location on a cloud.
In a further embodiment, the method (100) comprises setting up (107) the multi-party
conference call beforehand.
8
Figure 2 illustrates an exemplary method for setting up (107) the multi-party
conference call beforehand, in accordance with an embodiment of present invention. In said
embodiment, the setting up (107) comprises: receiving (201) input details pertaining to the
multi-party conference call; booking (202) the multi-party conference call based on the
received input details; and automatically sending (203) a notification in respect of the multiparty
conference call to each invitee.
In a further embodiment, the details of the multi-party conference call comprise one
or more of start time of the multi-party conference call, end time of the multi-party
conference call, duration of the multi-party conference call, subject of the multi-party
conference call, the passcode, contact number or email address for each invitee, and name of
each invitee. Any of these details may be used as content in the notification.
In a further embodiment, the conference calling application provides a user interface
to select the contact number and the name corresponding to the contact number from a
phonebook of the cellular phone.
In a further embodiment, the user interface provides an option to edit the contact
number and the name corresponding to the contact number before sending the notification.
In a further embodiment, the user interface provides an option to manually enter the
contact number and the name corresponding to the contact number.
In a further embodiment, the user interface provides an option to create a group of
intended participants for frequent use.
In a further embodiment, the notification is in form of a SMS, Email, or instant
message.
In a further embodiment, the setting up (107) comprises receiving (204) a response to
the notification. The response may be to accept, reject, or tentatively accept the invitation of
the conference call. All such responses to the notification are also reflected in the user
interface of the conference calling application, which maintains a list of participants and their
responses.
In a further embodiment, the setting up (107) comprises sending (205) at least one
reminder before the conference call.
In a further embodiment, the setting up (107) comprises marking (206), based on a
user selection, at least one invitee as optional for the conference call.
9
In a further embodiment, the setting up (107) comprises automatically calling (207)
the invited contact numbers at the start time of conference call.
Figure 3a illustrates an exemplary cellular phone (300) that facilitates a multi-party
conference call, which can implement the methods described with reference to preceding
figures.
In one embodiment, the cellular phone (300) comprises: a processor (301); a display
(302) coupled with the processor (301); and a memory (303) coupled with the processor
(301), the memory (303) having a conference calling application (304) that facilitates the
conference call, wherein the conference calling application (304) is configured to: establish a
call with a first contact number, wherein the first contact number is an invitee to the multiparty
conference call; monitor in a background state an incoming call from a second contact
number; and automatically merge the incoming call with the already established call to create
the multi-party conference call if the second contact number pertaining to the incoming call is
in an invitee list to the multi-party conference call, or a designated passcode is received
during the incoming call. Here, establishing the call includes receiving an incoming call and
or making an outgoing call to start the conversation.
In a further embodiment, the conference calling application (304) is configured to
play a relevant announcement to the second contact number if the passcode is incorrect for a
predefined number of times or not received. Additionally, a predefined message, such as
“user is busy in a conference call” may be sent to the second contact number.
In a further embodiment, the conference calling application (304) is configured to
record the conference call and store the recorded conference call in the memory (303) of the
cellular phone or at a shared location on a cloud.
In a further embodiment, the conference calling application (304) is configured to set
up the multi-party conference call beforehand.
In a further embodiment, the conference calling application (304) is configured to:
receive input details pertaining to the multi-party conference call; book the multi-party
conference call based on the received input details; and automatically send a notification in
respect of the multi-party conference call to each invitee.
In a further embodiment, the details of the multi-party conference call comprise one
or more of start time of the multi-party conference call, end time of the multi-party
10
conference call, duration of the multi-party conference call, subject of the multi-party
conference call, the passcode, contact number or email address for each invitee, and name of
each invitee. Any of these details may be used as content in the notification.
In a further embodiment, the conference calling application (304) provides a user
interface to select the contact number and the name corresponding to the contact number
from a phonebook (305) of the cellular phone (300).
In a further embodiment, the user interface provides an option to edit the contact
number and the name corresponding to the contact number before sending the notification.
In a further embodiment, the user interface provides an option to manually enter the
contact number and the name corresponding to the contact number.
In a further embodiment, the user interface provides an option to create a group of
intended participants for frequent use.
In a further embodiment, the notification is in form of a SMS, Email, or instant
message.
In a further embodiment, the conference calling application (304) is configured to
receive a response to the notification. The response may be to accept, reject, or tentatively
accept the invitation of the conference call. All such responses to the notification are also
reflected in the user interface of the conference calling application, which maintains a list of
participants and their responses.
In a further embodiment, the conference calling application (304) is configured to
send at least one reminder before the conference call.
In a further embodiment, the conference calling application (304) is configured to
mark, based on a user selection, at least one invitee as optional for the conference call.
In a further embodiment, the conference calling application (304) is configured to
automatically call the invited contact numbers at the start time of conference call.
Figure 3b illustrates an exemplary network environment that facilitates a multi-party
conference call. A convener of the conference call needs to first download the conference
calling application (204) from an app server (306) on his/her phone (300a). One or more
participants could also download the conference calling application (304) at their phones
(300b) to get better user experience. Conference calling is performed through the
telecommunication network (307) using voice channel, data connection is not required as
such for regular working of the conference calling application (304). However, in one
implementation, the conference calling may be performed through data channel of the
11
telecommunication network (307). Once conference call is completed, a recording of the
conference call may be stored at a shared location on a cloud server (308) from where the
convener and the participants through their phones (300a, 300b) can retrieve the recording
later on.
Figure 4 illustrates an exemplary use case (400) for conference calling without
requiring any passcode, in accordance with an embodiment of present invention. At step 401,
the conference calling application (304) is downloaded and installed in the memory (303) of
the cellular phone (300); this is the only time where a data connection necessarily required.
Once application is installed in the cellular phone, the data connection is not required at least
for regular working of the conference calling application (304).
This conference calling application (304) can be used by a user to quickly set up a
conference call without any dependency on external conference providers or operators.
In fact, conference call can be set up on the fly using this conference calling application
(304). For this purpose, the user enters details, such as time, duration, subject, etc. of the
conference call. The conference call can be set as a one-time conference call or as a recurring
conference call.
The user may manually provide contact number and name of each intended
participant. Alternatively, the user can select the participants from the phonebook (305) of the
cellular phone (300), more specifically the contact numbers and name of the intended
participants. In one implementation, the conference calling application (304) provides option
of editing the contact number and name of the intended participant at the time of adding the
participants for the conference call. In one implementation, the user can mark certain
participants as optional for the conference call. These participants are notified about the same
so that they can join the conference call accordingly. In one implementation, the conference
calling application (304) provides creation of a group of participants where participants could
be added and deleted as per requirements. This group feature can be used for ease of use for
frequent conference calling with the group of participants.
When all such details are received, the user is prompted to book the conference call.
Upon booking of the conference call, a SMS is sent to each of intended participants
automatically at steps 402 and 403. The SMS may include time, duration, subject, etc. of the
conference call. If the cellular phone has an active data connection, an email/instant message
12
may be sent in addition to the SMS or as an alternative to the SMS depending upon user
preference stored in the settings of the conference calling application (304). Participants can
respond to the SMS/email/instant message notification by accepting, rejecting, or tentatively
accepting the invitation for the conference call. The response can also be in the form of a
SMS/email/instant message just like the notification. Further, any participant having the
conference calling application in his/her phone can also respond through the conference
calling application directly. On the other hand, the conference calling application at the user’s
end can display a list of such responses as in who has accepted, rejected, or tentatively
accepted the invitation for the conference call. Furthermore, the conference calling
application at the user’s end can be configured to send periodic reminders in form of
SMS/email/instant message or application-to-application communication before the
conference call.
As the user has booked the conference call and added the intended participant
himself/herself, these intended participants can call on the contact number of the user to join
the conference call without requiring any passcode. At step 404, a first caller dials the user
number, i.e., the contact number of the cellular phone (300). At step 405, the user answers the
call to start the conversation. At step 406, a subsequent caller dials the user number. At step
407, the conference calling application (304) checks if any conference call is setup for that
duration and if the subsequent caller is an intended participant to that conference call. If yes,
then the conference calling application (304) automatically adds this subsequent call into the
conference call without requiring any action from the user. In this way, the flow of the
conversation is not broken and user does not have to manually add the participant into the
conference call. From participant’s perspective, the participant neither has to call on an
unfamiliar bridge number nor has to provide any passcode. In other words, if a subsequent
caller is a participant intended by the user at the time of setting up the conference call, the
conference calling application (304) automatically bridges the call into the conference call
without prompting for passcode and without bothering the user, at step 408. However, if the
subsequent caller is a non-intended participant, then a call waiting signal is sent to the
subsequent caller or a relevant announcement may be played. Additionally, a predefined
message, such as “the person you have called is busy in a conference call or another call”
may be sent to the subsequent caller. In this way, an additional layer of security is
implemented as compared to known solutions as only intended participant can join the
13
conference call that too without requiring any passcode, while all other users are asked to
wait. In other words, indent participants can join the call only from the number specified by
user at the time of creating the conference call, but not from any other number. On the other
hand, in known solutions, anybody having the details of bridge details/passcode can join the
conference call from any contact number.
Figure 5 illustrates an exemplary use case (500) for conference calling with passcode,
in accordance with an embodiment of present invention. At step 501, the conference calling
application (304) is downloaded and installed in the memory (303) of the cellular phone
(300), the conference calling application (304) can be used to set up a conference call. For
this purpose, the user enters details, such as time, duration, subject, passcode, etc. of the
conference call. The user also selects the intended participants from the phonebook (305).
Alternatively, the user manually provides contact number of each intended participant. In this
embodiment, non-intended participants can also join the conference call if they have the
passcode. This may be particularly useful when an intended participant having the passcode
may want to join the conference call from some other number due to some reasons, such as
low battery, low network coverage, etc. This may also be useful in cases where an intended
participant would also like to a non-intended participant to represent or accompany him/her
in the conference call. Accordingly, the intended participant may share in advance the
conference details including the passcode with any non-intended participant.
When all the required details are received, the user is prompted to book the
conference call. Upon booking of the conference call, a SMS is sent to each of intended
participants automatically at steps 502 and 503. The SMS may include time, duration,
subject, passcode, etc. of the conference call. If the cellular phone has an active data
connection, an email/instant message may be sent in addition to the SMS or as an alternative
to the SMS depending upon user preference stored in the settings of the conference calling
application (304). As user has booked the conference call and added the participant, all the
intended participants can call on the contact number of the user to join the conference call
without any passcode, whereas non-intended participants can also call on the contact number
of user and join the conference call, but only after providing the passcode.
At step 504, a first caller dials the user number. At step 505, the user answers the call
to start the conversation. At step 506, a subsequent caller dials the user number. At step 507,
14
the conference calling application (304) checks if any conference call is setup for that
duration and if the subsequent caller is an intended participant to that conference call. If yes,
then the conference calling application (304) automatically adds this subsequent call into the
conference call without requiring any action from the user. In this way, the flow of the
conversation is not broken and user does not have to manually add the participant into the
conference call. From participant’s perspective, the participant neither has to call on an
unfamiliar bridge number nor has to provide passcode. In other words, if a subsequent caller
is a participant intended by the user at the time of setting up the conference call, the
conference calling application (304) automatically bridges the call into the conference call
without prompting for the passcode, at step 508. However, if the subsequent caller is
determined as a non-intended participant by the conference calling application (304), then the
conference calling application (304) prompts for the passcode. If passcode is entered and is
correct, then the conference calling application (304) automatically bridges this subsequent
call into the conference call, otherwise a relevant announcement is played and/or a predefined
message (optional) is sent to the subsequent caller. In one implementation, the passcode can
be made mandatory even for intended participants for the purpose of an additional layer of
security.
Figure 6 illustrates an exemplary screen (600) for one time registration, in accordance
with an embodiment of present invention. This screen (600) comprises a first textbox (601)
for receiving name of user of the application, a second textbox (602) for receiving mobile
number of the user, and a submit button (603) for storing the received information and
registering the user.
Figure 7 illustrates an exemplary screen (700) for authentication of user at the time of
registration, in accordance with an embodiment of present invention. This screen (700)
comprises a textbox (701) for receiving a One Time Password (OTP) and a submit button
(702) for verifying the received OTP. This OTP feature allows to authenticate the user and
his phone number to prevent any misuse.
Figure 8 illustrates an exemplary home screen (800) of the conference calling
application, in accordance with an embodiment of present invention. This screen (800)
comprises a plurality of hyperlinks to various other screens of the conference calling
application. For instance, a first hyperlink (801) to a screen for managing busy messages, a
15
second hyperlink (802) to a screen for managing groups, and a third hyperlink (803) to a
screen for conference setup may be provided. These other screens are explained in detail in
subsequent figures and paragraphs.
Figure 9 illustrates an exemplary screen (900) for managing busy messages, in
accordance with an embodiment of present invention. This screen (900) displays a list (901)
of existing busy messages, such as Message 1 and Message 2. Any of these existing busy
messages can be edited or deleted through a respective user interface (901a, 901b). Said
screen (900) also provides an option (902) to provide a customized busy message. The
customized busy message can be received through a textbox (902a) and an enter button
(902b) from the user of the conference calling application.
Figure 10 illustrates an exemplary screen (1000) for managing groups, in accordance
with an embodiment of present invention. This screen (1000) displays an option (1001) to
edit or delete existing groups through a dropdown user interface (1001a) and/or a radio button
user interface (1001b). Said screen (1000) also displays an option (1002) to create a new
group, wherein the name of the new group is received in a textbox (1000a) from the user.
Said screen (1000) also displays an option (1003) to add mandatory participants for
the conference call. For this purpose, a plurality of textboxes (1003a, 1003b) are provided to
receive the details of mandatory participants from the user. These textboxes (1003a, 1003b)
are supplemented with corresponding search buttons (1003c, 1003d) to facilitate search for
participants in the phonebook. If required, more such textboxes and corresponding search
buttons could be added through a hyperlink (1003e) for adding more mandatory participants.
Similarly, said screen (1000) also displays an option (1004) to add optional
participants for the conference call. For this purpose, another plurality of textboxes (1004a,
1004b) are provided to receive the details of optional participants from the user. These
textboxes (1004a, 1004b) are also supplemented with corresponding search buttons (1004c,
1004d) to facilitate search for participants in the phonebook. If required, more such textboxes
and corresponding search buttons could be added through a hyperlink (1004e) for adding
more optional participants. At the bottom of said screen (1000), an enter button (1005) is
provided which the user can click to save a new group or changes in existing groups.
16
Figure 11 illustrates an exemplary screen (1100) for conference setup, in accordance
with an embodiment of present invention. Said screen (1100) provides a first textbox (1101)
for receiving the subject line of a conference call to be booked, and a second textbox (1102)
for receiving the agenda of the conference call. The user could choose an existing group of
participants through a dropdown user interface (1103) for the same. Otherwise, the user could
add mandatory participants (1104) for the conference call through a plurality of textboxes
(1104a, 1104b) and/or corresponding search buttons (1104c, 1104d) facilitating search for
participants in the phonebook. If required, more such textboxes and corresponding search
buttons could be added through a hyperlink (1104e) for adding more mandatory participants.
Similarly, the user could add optional participants (1105) for the conference call through
another plurality of textboxes (1105a, 1105b) and/or corresponding search buttons (1105c,
1105d) facilitating search for participants in the phonebook. If required, more such textboxes
and corresponding search buttons could be added through a hyperlink (1105e) for adding
more optional participants.
In relation to timing of the conference call, said screen (1100) provides another
textbox (1106) or any other relevant user interface to receive the start time/date of the
conference call. Similarly, said screen (1100) also provides another textbox (1107) or any
other relevant user interface to receive the end time/date of the conference call.
Apart from these features, said screen (1100) comprises another text box (1108) for
receiving an optional passcode. In a preferred embodiment, intended participants are not
asked for this passcode to join the conference call, while non-intended participants could join
the conference call only by providing the passcode. On the other hand, non-intended
participants not providing the passcode or providing incorrect passcode for a predefined
number of times get to listen a relevant announcement. Additionally, a predefined message,
such as “user is busy in a conference call” may be sent. Said screen (1100) further comprises
a dropdown menu (1109) for choosing a busy message which is sent to non-participants who
call the user during the conference call. One example of the busy message is “I am in
conference call. I will call you back later”. Another example is “Please call me later”. Said
screen (1100) further comprises a checkbox (1110) for enabling or disabling auto-recording
feature. If this feature is on, the conference calling application will automatically record the
conference call and store it at a shared location in the cloud server (308). Said screen (1100)
further comprises a checkbox (1111) for enabling or disabling an auto-dial feature. If this
17
feature is on, the conference calling application will automatically dial to the participants at
the start time of conference call. At the bottom of said screen (1100), an enter button (1112)
is provided which the user can click to book the conference call based on information
provided by him/her.
The conference calling application is not required as such on the participant’s end.
However, if it is there, the participants can get enriched user experience. For example, a
participant can see a list of other participants. Further, the participants can get notification
through the conference calling application than regular notifications in form of SMS, email,
and/or instant message. Further, the participants can accept, reject, or tentatively accept the
invitation to the conference call from the user interface of the conference calling application.
The conference calling application can also provide periodic reminders before the conference
call. The conference calling application can automatically dial into the conference call at start
time of the conference call, if such an auto-dial option is switched on by a participant in the
settings of the conference calling application. Furthermore, the conference calling application
at the participant’s end can independently record and store the audio of conference call,
otherwise the participant is dependent on the convener of the conference call to provide a link
to the shared location on the cloud server where the audio is stored by the convener’s
conference calling application. In one implementation, the participant’s application and the
convener’s application communicate with each other in background to share the schedule of
participant with the convener so that convener can book the conference call for a time slot
where all parties are free.
While certain present preferred embodiments of the invention have been illustrated
and described herein, it is to be understood that the invention is not limited thereto. Clearly,
the invention may be otherwise variously embodied, and practiced within the scope of the
following claims.
18
We Claim:
1. A method for facilitating a multi-party conference call in a cellular phone through a
conference calling application, the method comprising:
establishing a call with a first contact number, wherein the first contact
number is an invitee to the multi-party conference call;
monitoring in a background state an incoming call from a second contact
number; and
automatically merging the incoming call with the already established call to
create the multi-party conference call if the second contact number pertaining to the
incoming call is in an invitee list to the multi-party conference call, or a designated
passcode is received during the incoming call.
2. The method as claimed in claim 1, further comprising:
playing an announcement to the second contact number if the passcode is
incorrect for a predefined number of times or not received.
3. The method as claimed in claim 1, further comprising:
recording the conference call; and
storing the recorded conference call in a memory storage of the cellular phone
or at a shared location on a cloud.
4. The method as claimed in claim 1, further comprising:
setting up the multi-party conference call beforehand.
5. The method as claimed in claim 4, wherein the setting up comprising:
receiving input details pertaining to the multi-party conference call;
booking the multi-party conference call based on the received input
details; and
automatically sending a notification in respect of the multi-party
conference call to each invitee.
6. The method as claimed in claim 5, wherein the details of the multi-party conference
call comprise one or more of start time of the multi-party conference call, end time of
the multi-party conference call, duration of the multi-party conference call, subject of
19
the multi-party conference call, the passcode, contact number or email address for
each invitee, and name of each invitee.
7. The method as claimed in claim 6, wherein the conference calling application
provides a user interface to select the contact number and the name corresponding to
the contact number from a phonebook of the cellular phone.
8. The method as claimed in claim 7, wherein the user interface provides an option to
edit the contact number and the name corresponding to the contact number before
sending the notification.
9. The method as claimed in claim 7, wherein the user interface provides an option to
manually enter the contact number and the name corresponding to the contact
number.
10. The method as claimed in claim 7, wherein the user interface provides an option to
create a group of intended participants for frequent use.
11. The method as claimed in claim 5, wherein the notification is in form of a SMS,
Email, or instant message.
12. The method as claimed in claim 5, further comprising:
receiving a response to the notification.
13. The method as claimed in claim 5, further comprising:
sending at least one reminder before the conference call.
14. The method as claimed in claim 5, further comprising:
marking, based on a user selection, at least one invitee as optional for
the conference call.
15. The method as claimed in claim 5, further comprising:
automatically calling the invited contact numbers at the start time of
conference call.
16. A cellular phone that facilitates a multi-party conference call, the cellular phone
comprising:
a processor;
a display coupled with the processor; and
a memory coupled with the processor, the memory having a conference calling
application that facilitates the conference call, wherein the conference calling
application is configured to:
20
establish a call with a first contact number, wherein the first contact
number is an invitee to the multi-party conference call;
monitor in a background state an incoming call from a second contact
number; and
automatically merge the incoming call with the already established call
to create the multi-party conference call if the second contact number
pertaining to the incoming call is in an invitee list to the multi-party
conference call, or a designated passcode is received during the incoming call.
17. The cellular phone as claimed in claim 16, wherein the conference calling application
is further configured to play an announcement to the second contact number if the
passcode is incorrect for a predefined number of times or not received.
18. The cellular phone as claimed in claim 16, wherein the conference calling application
is further configured to record the conference call and store the recorded conference
call in the memory of the cellular phone or at a shared location on a cloud.
19. The cellular phone as claimed in claim 16, wherein the conference calling application
is further configured to set up the multi-party conference call beforehand.
20. The cellular phone as claimed in claim 19, wherein the conference calling application
is further configured to
receive input details pertaining to the multi-party conference call;
book the multi-party conference call based on the received input
details; and
automatically send a notification in respect of the multi-party
conference call to each invitee.
21. The cellular phone as claimed in claim 20, wherein the details of the multi-party
conference call comprise one or more of start time of the multi-party conference call,
end time of the multi-party conference call, duration of the multi-party conference
call, subject of the multi-party conference call, the passcode, contact number or email
address for each invitee, and name of each invitee.
22. The cellular phone as claimed in claim 21, wherein the conference calling application
provides a user interface to select the contact number and the name corresponding to
the contact number from a phonebook of the cellular phone.
21
23. The cellular phone as claimed in claim 22, wherein the user interface provides an
option to edit the contact number and the name corresponding to the contact number
before sending the notification.
24. The cellular phone as claimed in claim 22, wherein the user interface provides an
option to manually enter the contact number and the name corresponding to the
contact number.
25. The cellular phone as claimed in claim 22, wherein the user interface provides an
option to create a group of intended participants for frequent use.
26. The cellular phone as claimed in claim 20, wherein the notification is in form of a
SMS, Email, or instant message.
27. The cellular phone as claimed in claim 20, wherein the conference calling application
is further configured to receive a response to the notification.
28. The cellular phone as claimed in claim 20, wherein the conference calling application
is further configured to send at least one reminder before the conference call.
29. The cellular phone as claimed in claim 20, wherein the conference calling application
is further configured to mark, based on a user selection, at least one invitee as optional
for the conference call.
30. The cellular phone as claimed in claim 21, wherein the conference calling application
is further configured to automatically call the invited contact numbers at the start time
of conference call.