GB2531656A

GB2531656A - Conference calls

Info

Publication number: GB2531656A
Application number: GB1518143.1A
Authority: GB
Inventors: Paul Elwood Dean
Original assignee: VOXYGEN Ltd
Current assignee: VOXYGEN Ltd
Priority date: 2014-10-20
Filing date: 2015-10-14
Publication date: 2016-04-27
Also published as: GB201518143D0; GB201418634D0

Abstract

A method of generating a conference bridge for a conference call accessible by a users number (e.g. PSTN number or mobile phone number), comprising enabling said bridge, and at least some calls to said users number being diverted to said bridge automatically for as long as said bridge is enabled and access thereto is allowed. Another aspect includes a method of generating a conference bridge accessible by a users number, comprising: receiving a request to generate the conference bridge; generating said conference bridge; and automatically redirecting calls to said users number to said conference bridge for as long as said bridge is enabled and access thereto is allowed. Aspects include the request to generate the conference bridge: comprises a predetermined shortcode dialled by the user; comprises a user generated request from a user interface; is generated automatically from an email and/or calendar event. By requiring only the users telephone number to access the conference bridge, the participants do not need any knowledge of the system in use in order to participate in a conference call, and simply act as if they are making a normal one-to-one call.

Description

CONFERENCE CALLS

This invention relates to the establishment of voice conference calls e.g. by generating a conference bridge.

In recent years, the popularity of audio-conferencing services (or conference bridges) has grown immensely, as a tool to allow collaboration and interaction without physical attendance at a single meeting place. A conference bridge allows a group of people to be connected on a single call, whether just as listeners or as active participants. The conference bridge connects a plurality of separate telephone lines, removing the restriction of a one-to-one call. There are many different types of conferencing services, including dedicated bridge appliances, functions integrated into switches or private branch exchanges (PBXs), and cloud based conference hosting services. Some of these conferencing services require pre-registration or booking of resources beforehand, whereas others allow ad-hoc dial-in, allowing an "instant meeting" to be provided for a group of users.

With existing conference bridges, set up can be time consuming, and often requires cumbersome instructions being sent to each participant. This includes, for example, access numbers, conference room numbers and pin codes. This therefore increases the complication of arranging a conference call, dissuading users from using them when they would be beneficial or running the risk of potential participants being absent from a call.

When viewed from a first aspect, the invention provides a method of generating a conference bridge for a conference call accessible by a user's number, comprising enabling said bridge, and at least some calls to said user's number being diverted to said bridge automatically for as long as said bridge is enabled and access thereto is allowed.

This aspect of the invention extends to an apparatus for generating a conference bridge accessible by a user's number, comprising means to enable said bridge, and means for diverting calls to said user's number to said bridge automatically for as long as said bridge is enabled and access thereto is allowed. -2 -

This aspect of the invention further extends to a computer software product for generating a conference bridge accessible by a user's number, comprising instructions for enabling said bridge, and instructions for diverting calls to said user's number to said bridge automatically for as long as said bridge is enabled and access thereto is allowed.

Thus it can be seen that a flexible and accessible conference bridge is provided in which participants can access the call using only the organiser's ordinary phone number. There is no need for a room number or pin number in order to access the conference bridge. Delays to participants joining through lack of familiarity with a conference bridge system can therefore be avoided. By requiring only the user's number to access the conference bridge, the participants do not need any knowledge of the system in use in order to participate in a conference call, and simply act as if they are making a normal one-to-one phone call.

In accordance with the invention a conference bridge may be generated only when needed, allowing easy scheduling of conference calls, and preventing unnecessary interference with the user's personal line. While a conference bridge is active and access is allowed, the user's number is automatically redirected to said bridge, at least for some callers. This allows it to act as an access point to the bridge for those callers, while preventing normal one-to-one phone calls. As the redirection is stopped once the conference bridge is no longer in use, or when access thereto is no longer allowed if that is earlier, the conference bridge is minimally intrusive on the user, automatically returning the phone to normal operation.

When viewed from a second aspect, this invention provides a method of generating a conference bridge accessible by a user's number, comprising: receiving a request to generate the conference bridge; generating said conference bridge; and automatically redirecting calls to said user's number to said conference bridge for as long as said bridge is enabled and access thereto is allowed.

This aspect of the invention extends to an apparatus for generating a conference bridge accessible by a user's number, comprising: -3 -means to receive a request to generate the conference bridge; means to generate said conference bridge; and means to automatically redirect calls to said user's number to said conference bridge for as long as said bridge is enabled and access thereto is allowed.

This aspect of the invention further extends to a computer software product for generating a conference bridge accessible by a user's number, comprising: instructions for receiving a request to generate the conference bridge; instructions for generating said conference bridge; and instructions for automatically redirecting calls to said user's number to said conference bridge for as long as said bridge is enabled.

Thus it can be seen that a server, for example in a remote server, may be used to produce the conference bridges as necessary. Each conference bridge can be generated within the server in response to a request, e.g. from a user. Conference bridges only exist when in use, preventing unnecessary memory use or scheduling issues, as can occur when conference calls must be fitted into a predetermined set of bridges.

It will be appreciated that there a number of ways in which a user may request the establishment of a conference call. In a set of embodiments, the request to generate the conference bridge comprises a predetermined shortcode being dialled by the user. This shortcode is recognised by the network and can immediately establish a conference call to which the user may be connected to await further participants.

Additionally or alternatively, the conference call may be established using a web interface or a mobile app, and thus in a set of embodiments the request to generate the conference bridge comprises a user-generated request from a user interface.

In a set of embodiments, the request to generate the conference bridge is generated automatically from an email and/or calendar event. This may be achieved by parsing emails and/or calendar events for details regarding a future conference call, translating the relevant email address(es) of the user to the user's -4 -number e.g. using a database of known email-to-number relationships, and scheduling the conference call for the appropriate time.

In a set of embodiments, all calls to the user's number are redirected to the conference bridge while the conference bridge is enabled and access is allowed.

However, in a set of embodiments, only certain calls are redirected to the conference bridge. This may allow the user more control over the participants of the conference call, and may help to ensure that only the correct participants are present. In a set of embodiments, Calling Line Identity (CLI) may be used to identify participants. Other methods of identification may however be used instead.

Controlling the participants may be particularly useful when confidentiality is a concern, for example during business calls.

Alternatively, control over participants may be used to ensure that certain callers are not redirected to the conference bridge, for example ensuring that an emergency contact is put straight through to the user without disabling the conference bridge.

In a set of embodiments, the conference bridge is generated at a predetermined time scheduled in a request ahead of time. Alternatively it may be when the request for a conference bridge is received.

Access to the conference bridge may be allowed for all of the time while the bridge is enabled. In a set of embodiments however access to the bridge is only allowed for a shorter time. The access time may be a fixed period or defined by the user.

The feature allows participants to join at the beginning of the call put prevents someone calling the user at a later point while the conference call is still going on inadvertently being added to the conference. This is most likely to be useful where access to the bridge is not restricted to specifically-identified participants.

The conference bridge may be disabled automatically at a predetermined time, which may be specified by the user when said bridge is enabled, either as a specific time or by specifying a call duration. However, it may alternatively be automatically disabled when the final participant leaves the call, or it may be manually disabled by the user. -5 -

In accordance with any aspect of the invention the user will typically request the conference bridge in respect of their own number. However this is not essential and it is envisaged that another party such as a personal assistant could request the bridge for a different number. Such requests (or those for the user's own number) may be made via a different -e.g. web -interface.

The user may not participate in the conference call. However, in a set of embodiments the user is also a participant of the call. In order to join the conference bridge, the user may call their own number, or alternatively the user may call a number allocated by the conference bridge. However, in a set of embodiments, the user may be called by the conference bridge at a predetermined time in order to join the conference call. This predetermined time may be the time at which the conference call is scheduled, but in a set of embodiments it is when the first participant calls the conference bridge.

In a set of embodiments, a plurality of conference bridges may be enabled on said user's number at one time. This may be the case when back-to-back conference calls are required, as it allows for the first call to overrun into the period defined for the second call. In a set of such embodiments, the user is able to switch between the plurality of conference calls without disabling said conference bridges. Conveniently the periods for which access is allowed to the respective bridges do not overlap.

In a set of embodiments, a record of required conference bridges is stored in a database. This may allow a user access to a list of their planned conference bridges, assisting scheduling of further conference calls.

The user's number may be a standard public switched telephone network (PSTN) number, but in a set of embodiments it is a mobile phone number. This may allow the user increased flexibility in arranging conference calls, as they are not tied to a specific location.

The user may enable the call using an application on the phone associated with their number. This application may include a record of planned conference calls, -6 -and/or a record of past conference calls. Different versions of the application may be available, giving the user different levels of functionality. For example, one version may provide duration-limited calls, whereas an alternative premium version may allow unlimited calling.

The application may allow the user to view information regarding the status of the conference bridge, for example the number (and identity) of current participants, the duration of the conference call, the amount of time left for the call if a fixed duration has been assigned, or information regarding any participants who have not yet joined the call or who have already left the call.

In addition or alternatively, the user may be able to forcibly remove a participant from a conference bridge. They may also prevent the removed participant from reentering the conference bridge. This may be through adding the user to a list of banned participants from that particular call. However, in a set of embodiments the user is able to lock the conference bridge, preventing any more participants joining the conference call.

In a set of embodiments, the user may be able to mute and unmute their microphone and/or speaker while the conference bridge is enabled. This may be useful when switching between multiple conference bridges, as it would prevent operator noise (e.g. button presses) being carried into the conference call. Background noise and disturbances can affect the quality of a conference call, so reducing these would be desirable.

The Applicant has appreciated that it is advantageous for the user to be able to switch back and forth between multiple conference bridges. In a set of embodiments, the user may be able to transfer participants from one conference bridge to another. In an overlapping set of embodiments, the user may be able to merge a first conference bridge with a second conference bridge, such that all participants connected to the first conference bridge are transferred to the second conference bridge or vice versa, and subsequently only one of the conference bridges continues to exist. -7 -

In a set of embodiments, the user may be able to record at least a part of a conference call. This recording may be carried out on demand, or alternatively may be predefined, for example if the user is recording an entire conference call.

In a set of embodiments where only certain calls (e.g. from particular people or after access is no longer allowed) are redirected to the conference bridge, any other calls may be redirected to an alternative service. This may, for example, comprise a voicemail service in which they can leave a message for the user, or a pre-recorded message from the user, for example stating an alternative means of contact.

The conference bridge may be set up to allow certain participants to take part in two-way communication and the remaining users only being able to listen, but in a set of embodiments all participants are able to take part in two-way communication. The former may be used when a group of people need instructing, so the user only has to repeat the instructions once, whereas the latter may be more useful for discussions.

An embodiment of the present invention will now be described, by way of example only, with reference to the accompanying drawings in which: Fig. 1 shows a flow chart of the process that takes place whenever there is incoming call activity for a particular user.

Fig. 2 shows a flow chart of the process that takes place whenever there is outgoing call activity for a particular user.

Fig. 3 shows a flow chart of exemplary conference room logic for an exemplary conference bridge; and Fig. 4 shows a flow chart of an interaction with a user when joining the conference bridge of Fig. 3.

Fig. 1 shows a flow chart of the process that takes place whenever there is incoming call activity for a particular user. When an incoming call 100 is active for a particular user, the core network of the mobile provider performs a lookup in the Home Location Register (HLR) at step 102. During this lookup, the core network checks at step 104 for a specific flag that represents whether said user is currently subscribed to a conferencing service. -8 -

If at step 104 it is determined that the specific user is not subscribed to the conferencing service, the call continues as a normal call 106 unhindered. However, if at step 104 the specific flag is set, it is determined that the user is subscribed to the conferencing service and the call is diverted from the core network to a server that implements a conferencing server at step 108.

Within the conferencing server, a decision is made at step 110 as to whether or not to answer the call. If the call is not answered, a further decision is made at step 112 regarding whether to loop back the call (commonly called a trombone), in which case the call is diverted back to the core network at step 116 and resumes as a normal call 106. If the call is not to be looped back, further signalling can take place and the call can be deflected or transferred, such that management of the call is transferred back to the core network at step 114. If, however, at step 110 the call is answered, the call is connected to the conference room logic at step 118. Further details of what happens to it then are given below with reference to Fig. 3.

Fig. 2 shows a flow chart of the process that takes place whenever there is outgoing call activity for a particular user. When an outgoing call 200 is active for a particular user, the core network of the mobile provider performs a lookup in the Home Location Register (HLR) at step 202. During this lookup, the core network checks at step 204 for a specific flag that represents whether said user is currently subscribed to a conferencing service.

If at step 204 it is determined that the specific user is not subscribed to the conferencing service, the call continues as a normal call 208 unhindered. However, if at step 204 the specific flag is set, it is checked whether the user has dialled their own number or a short code to access the user's own conference at step 206. If it is determined that the user is attempting to access their own conference, the call is diverted from the core network to a server that implements a conferencing server at step 210.

Within the conferencing server, a decision is made at step 214 as to whether or not to answer the call. If the call is not answered, a further decision is made at step 218 regarding whether to loop back the call (commonly called a trombone), in which case the call is diverted back to the core network at step 212 and resumes as a -9 -normal call 208. If the call is not to be looped back, further signalling can take place and the call can be deflected or transferred, such that management of the call is transferred back to the core network at step 220. If, however, at step 214 the call is answered, the call is connected to the conference room logic at step 216. Further details of what happens to it then are given below with reference to Fig. 3.

Fig. 3 shows a flow chart of exemplary conference room logic for an exemplary conference bridge. At step 2, a check is made to determine if a conference call is currently scheduled. If there is no conference call scheduled, the call resumes as a normal call 4. If there is a conference call scheduled, a check 6 is made to determine if the calling party belongs to a pre-authorised list of callers, which may be generated by the user specifically for that call or may be a general list of possible participants. If the calling party does belong to the pre-authorised list, a further check 8 is carrier out to determine if the conference is currently locked. If the conference is not locked, the call is bridged to the conference 10.

If, however, the caller does not belong to the pre-authorised list, or the conference is locked at the time of calling, a recorded message 12 notifies the caller that the person they have dialled is on a conference call and prompted to press "1" on their keypad if they were invited to the conference call or be transferred to voicemail. If the caller does not press "1" within 5 seconds, the caller is transferred to voicemail 18. If the caller pressed a key other than "1", a check 14 is made to determine if it is a valid admin code. The admin code may be a general code for that user, or it may change depending on the conference bridge being reached. If the caller has entered a valid admin code, the call is bridged to the conference 16. If the caller's input was not a valid admin code 14, a further check 15 is carried out to determine if the caller has made more than two attempts. If so the systems transfer the caller to voicemail 18, else it repeats the recorded message 12 and allows a further attempt.

If, however, following the recorded message 12 the caller presses "1" within 5 seconds, a check 22 is carried out to determine if the conference room is locked. If the conference is locked, a recorded message 24 notifies the caller that they are being placed on hold while their attendance status is confirmed before transferring the caller into a waiting room 26. Every 15 seconds, a recorded message asks the caller to continue to hold, and if more than 45 seconds pass, a further recorded message notifies the caller that their status for the conference could not be determined before removing the caller from the waiting list and transferring them to voicemail 18.

If, however, at stage 22 the conference is not locked, a further check 30 determines if the caller is the first participant to join the conference. If the conference already has other participants, the call is bridged to the conference 32. If, however, the caller is the first participant, a record message 34 informs the caller that they are currently the only person in the conference and that the conference organiser is being dialled. The conference server then makes an outbound call 36 to the conference organiser and periodically plays a recorded message 38 to the caller to ask them to continue to hold. If the conference organiser answers, the call is bridged to the conference 40. If more than 45 seconds pass without the conference organiser answering the call from the conference server, a recorded message 42 informs the caller that the conference organiser could not be contacted and that a message has been sent to the conference organiser asking them to call the caller.

Fig. 4 shows a flow chart of an interaction with a user when joining the conference bridge of Fig. 3. When a call has been bridged to the conference, a check 44 is first made to determine if the conference server already has an audio greeting saved for the caller's ID. If an audio greeting already exists, a recorded message 56 welcomes the user to the conference. If an audio greeting for the caller's ID cannot be located, a recorded message 48 requests that the caller records their name after a tone. The conference server then checks 50 that it has captured at least 1 second of useable audio. If the server has been unable to capture at least 1 second of useable audio, a recorded message 52 asks the caller to try again. If, however, at least 1 second of useable audio was captured, said audio then undergoes post processing and caching 54 before a recorded message 56 welcomes the caller to the conference.

The post processing and caching 54 is used to create a pleasing and consistent cadence and level for participants that hear the audio greeting or composite messages that include the audio greeting. The recorded greeting is truncated front and back to remove background noise and faded in and out in order to minimise noise. A small and consistent amount of silence is added to make pleasing gaps in the composite messages. Finally, any composite message (e.g. "Fred has joined the conference") is maximized in volume and compressed, so that (a) quiet recordings are boosted to an audible volume and (b) the composite message and recorded greeting are of a consistent volume.

Thus it will be appreciated that a method of generating a conference bridge for a conference call accessible by a user's number has been described herein. Although particular embodiments have been described in detail, it will be appreciated by those skilled in the art that many variations and modifications are possible using the principles of the invention set out herein.

Claims

Claims 1. A method of generating a conference bridge for a conference call accessible by a user's number, comprising enabling said bridge, and at least some calls to said user's number being diverted to said bridge automatically for as long as said bridge is enabled and access thereto is allowed.
2. A method of generating a conference bridge accessible by a user's number, comprising: i) receiving a request to generate the conference bridge; ii) generating said conference bridge; and iii) automatically redirecting calls to said user's number to said conference bridge for as long as said bridge is enabled and access thereto is allowed.
3. The method as claimed in claim 2, wherein the request to generate the conference bridge comprises a predetermined shortcode dialled by the user.
4. The method as claimed in claim 2, wherein the request to generate the conference bridge comprises a user-generated request from a user interface.
5. The method as claimed in claim 2, wherein the request to generate the conference bridge is generated automatically from an email and/or calendar event.
6. The method as claimed in any preceding claim, wherein all calls to the user's number are redirected to the conference bridge while the conference bridge is enabled and access is allowed.
7. The method as claimed in any of claims 1 to 5, wherein only certain calls are redirected to the conference bridge.
8. The method as claimed in any preceding claim, comprising using Calling Line Identity (CLI) to identify participants.
9. The method as claimed in any preceding claim, comprising generating or enabling the conference bridge at a predetermined time specified in a or the request.
10. The method as claimed in any of claims 1 to 8, comprising generating or enabling the conference bridge when a or the request for a conference bridge is received.
11. The method as claimed in any preceding claim, wherein access to the conference bridge is available for a fixed period.
12. The method as claimed in any preceding claim, comprising disabling the conference bridge automatically when a final participant disconnects therefrom.
13. The method as claimed in any preceding claim, wherein the conference bridge is manually disabled by the user.
14. The method as claimed in any preceding claim, comprising the conference bridge calling the user in order to join the conference call.
15. The method as claimed in claim 14, comprising the conference bridge calling the user at a predetermined time at which the conference call is scheduled.
16. The method as claimed in claim 14, comprising the conference bridge calling the user when a first participant calls the conference bridge.
17. The method as claimed in any preceding claim, wherein a plurality of conference bridges may be enabled on the user's number at one time.
18. The method as claimed in claim 17, wherein the user is able to switch between the plurality of conference calls without disabling the plurality of conference bridges.
19. The method as claimed in claim 17 or 18, wherein the user is able to transfer participants from one conference bridge to another.
20. The method as claimed in any of claims 17 to 19, wherein the user is able to merge a first conference bridge with a second conference bridge, such that all participants connected to the first conference bridge are transferred to the second conference bridge or vice versa, and subsequently only one of the conference bridges continues to exist.
21. The method as claimed in any preceding claim, wherein the user may enable the conference bridge using an application on the phone associated with the user's number.
22. The method as claimed in claim 21, wherein the application includes a record of planned conference calls.
23. The method as claimed in claim 21 or 22, wherein the application includes a record of past conference calls.
24. The method as claimed in any of claims 21 to 23, wherein the application allows the user to view information regarding the status of the conference bridge.
25. The method as claimed in any preceding claim, wherein the user is able to forcibly remove a participant from the conference bridge.
26. The method as claimed in any preceding claim, wherein the user is able to lock the conference bridge.
27. The method as claimed in any preceding claim, wherein the user is able to record at least a part of a conference call.
28. The method as claimed in any preceding claim, the method further comprising redirecting any calls not diverted or redirected to the conference bridge to an alternative service.
29. The method as claimed in any preceding claim, wherein only certain participants in the conference bridge are able to take part in two-way communication and remaining participants are only able to listen.
30. An apparatus for generating a conference bridge accessible by a user's number, comprising means to enable said bridge, and means for diverting calls to said user's number to said bridge automatically for as long as said bridge is enabled and access thereto is allowed.
31. The apparatus as claimed in claim 30 arranged to carry out a method as claimed in any of claims 3 to 29.
32. A computer software product for generating a conference bridge accessible by a user's number, comprising instructions for enabling said bridge, and instructions for diverting calls to said user's number to said bridge automatically for as long as said bridge is enabled and access thereto is allowed.
33. The computer software product as claimed in claim 32 further comprising instructions to carry out a method as claimed in any of claims 3 to 29.
34. An apparatus for generating a conference bridge accessible by a user's number, comprising: i) means to receive a request to generate the conference bridge; ii) means to generate said conference bridge; and iii) means to automatically redirect calls to said user's number to said conference bridge for as long as said bridge is enabled and access thereto is allowed.
35. The apparatus as claimed in claim 34 arranged to carry out a method as claimed in any of claims 3 to 29.
36. A computer software product for generating a conference bridge accessible by a user's number, comprising: i) instructions for receiving a request to generate the conference bridge; ii) instructions for generating said conference bridge; and iii) instructions for automatically redirecting calls to said user's number to said conference bridge for as long as said bridge is enabled.
37. The computer software product as claimed in claim 36 further comprising instructions to carry out a method as claimed in any of claims 3 to 29.