Telephone system and method of operating the same

Abstract

A method (300, 400) of operating a telephony system (100), the system comprising: a client server (170) configured to: access a conference server (140) for establishing conference calls; connect a plurality of terminals (180) to the conference server; and communicate with a UE (160) to receive a call from the UE; the method comprising the following steps, by the client server: detecting initiation of a call between the UE and a given terminal of the plurality of terminals (320, 420); identifying the UE and the given terminal; evaluating whether the detected call is a conference call or a non-conference call; in response to evaluating that the call is a non-conference call: requesting, to the conference server, establishment of a conference call for the identified UE and the given terminal and corresponding to the non-conference call (330-2, 430); receiving, from the conference server, access information for accessing the requested conference call (340, 440); and distributing the access information to individual terminals of the plurality of terminals (360, 460), thereby allowing any of the terminals to access the conference call.

Description

Technical Field

[0001] This invention relates to a telephone system and a method of operating the telephone system. Background Technology

[0002] In a service provider-customer environment, multiple agents within a public service provider organization may need to participate in the same call with a single customer simultaneously; this can be allowed through conference calls.

[0003] However, the caller may omit or be unable to initiate a call as a conference call and may instead initiate a non-conference (or point-to-point) call. For example, a customer may not have the ability to initiate a conference call with multiple agents (e.g., only because they have contact details for just one of the agents) and therefore initiates a non-conference call in which multiple agents cannot participate unless a corresponding conference call is established.

[0004] In addition, meeting calls require participants to be known by the caller and invited by the caller, which can be difficult or laborious to manage for large groups.

[0005] Furthermore, if the operators of the conferencing platform (such as Microsoft, Google, Cisco, Meta, and Zoom) provide features to improve any of the aforementioned issues, these features reside at the operator's location and are far removed from the organization, and therefore may be beyond the organization's proper control and customization.

[0006] The object of this invention is to alleviate at least some of the above-mentioned problems. Summary of the Invention

[0007] According to a first aspect of the invention, a method for operating a telephone system is provided, the system comprising: a client server configured to: access a conference server for establishing a conference call; connect a plurality of terminals to the conference server; and communicate with a UE to receive a call from the UE; the method comprising the steps of the client server: detecting the initiation of a call between the UE and a given terminal among the plurality of terminals; identifying the UE and the given terminal; evaluating whether the detected call is a conference call or a non-conference call; in response to evaluating that the call is a non-conference call: requesting the conference server to establish a conference call for the identified UE and the given terminal and corresponding to the non-conference call; receiving access information from the conference server for accessing the requested conference call; and distributing the access information to each of the plurality of terminals, thereby allowing any terminal among the terminals to access the conference call.

[0008] Preferably, requesting a conference call includes instructing the conference server to pass access information to the identified UE. As used herein, a conference call corresponding to a non-conference call preferably means a conference call involving at least the same calling parties (i.e., the UE and the given terminal). Optionally, the method further includes the step of the client server terminating the non-conference call in response to the establishment of the conference call. Preferably, at least one of the plurality of terminals, other than the given terminal, is a non-participant in both the non-conference call and the requested conference call, but can subsequently participate in the requested conference call by using the access information. Preferably, requesting a conference call includes providing options for the conference call, the options including those relating to: media characteristics, security and privacy, call processing, and / or call management. Optionally, the options are selected based on the identity of the identified terminal and the UE.

[0009] Preferably, in response to assessing that the call is a conference call, the client server: receives access information for the conference call from the conference server; and distributes the access information to each of the plurality of terminals.

[0010] Preferably, the detected call is initiated by the UE. Preferably, the UE is not part of a plurality of terminals. Optionally, the client server is configured to allow the call to continue ringing while requesting the establishment of a conference call. Optionally, the client server is configured to answer the detected call and subsequently request the conference server to bridge the answered call to the requested conference call. Preferably, the client server intercepts the detected call and prevents the establishment of the call with a given terminal.

[0011] Preferably, the detected call is initiated by a given terminal. Preferably, the client server intercepts the detected call, and more preferably, intercepts the call before it is established between the UE and the given terminal, thereby preventing the establishment of the call. In this way, the UE can be notified of the detected call. Preferably, the client server is configured to connect the plurality of terminals to the UE, and wherein, in response to detecting that the call is a non-conference call from a given terminal, the client server prevents the call from being forwarded to the UE.

[0012] Preferably, the client server is configured to connect a superset of terminals to the conference server, the superset including the plurality of terminals and at least one additional terminal, and the method further includes the steps of: providing at the client server: a first group, the first group including the plurality of terminals and excluding the at least one additional terminal; and a second group, the second group including the at least one additional terminal and excluding the plurality of terminals; and identifying the first group as associated with a detected call, wherein, in response to the identification, the access information is sent to the first group and not sent to the second group. Preferably, identifying the first group as associated with a detected call is performed based on the identity of the UE and / or a given terminal. Optionally, the client server includes an association between the identified UE and (optionally, only) the first group, wherein identifying the first group is performed based on the association. Optionally, the client server includes an association between the identified given terminal and (optionally, only) the first group, wherein identifying the first group is performed based on the association. Preferably, the client server is configured to connect the at least one additional terminal to the conference server and the UE. Optionally, the options for the requested conference call are selected based on a group identified as associated with the detected call.

[0013] Preferably, the method further includes the following steps: providing a monitoring function at the client server for monitoring the status of the conference call; transmitting the access information for the conference call to the monitoring function; having the monitoring function use the access information to query the conference server to obtain status information for the conference call; and having the monitoring function share the obtained status information with the plurality of terminals. Optionally, the monitoring function is not a participant in the conference call. Optionally, in response to the identification of a first group associated with a detected call, the status information is shared with the first group but not with the second group. Optionally, the status information includes: the identity and / or details associated with the caller and / or the called party; the call start time; the communication time; the number of participants; activity indicators, such as an indication of an active and / or held call; the identity of the caller; and / or the identity of the currently active (e.g., speaking or presenting) participants in the call.

[0014] Preferably, the sharing of the acquired state is performed according to predefined rules based on the acquired state information. Optionally, the predefined rules include an evaluation of sufficient privileges by each of the multiple terminals.

[0015] Preferably, the method further includes the step of the client service detecting the UE's participation in the conference call, wherein, in response to the detected participation, the access information is distributed to each of the at least a plurality of terminals other than the given terminal. Optionally, the distribution is performed only in response to the detection of the participation.

[0016] Preferably, identifying the UE and the given terminal includes obtaining their unique call addresses, and wherein requesting to establish the conference call includes transmitting the call address to the conference server. Optionally, the method further includes identifying the UE and / or the given terminal as a caller and / or a called party, and wherein requesting to establish the conference call includes transmitting the identifier to the conference server. Preferably, the call address may include: a telephone number; a network address; a user account profile; a proxy ID; and / or a user ID. Preferably, requesting to establish the conference call includes requesting that the non-conference call be bridged to the requested conference call.

[0017] According to another aspect of the present invention, a computer-readable carrier medium is provided, the computer-readable carrier medium including a computer program that, when executed by a computer, causes the computer to perform the steps of the above-described method.

[0018] According to another aspect of the present invention, a telephone system is provided, the telephone system comprising: a plurality of terminals; and a client server, the client server comprising: a network interface configured to: access a conference server for establishing a conference call; connect the plurality of terminals to the conference server; and communicate with a UE to receive a call from the UE; and a controller configured to: detect the initiation of a call between the UE and a given terminal among the plurality of terminals; identify the UE and the given terminal; evaluate whether the detected call is a conference call or a non-conference call; and in response to evaluating that the call is a non-conference call, request the conference server to establish a conference call for the identified UE and the given terminal and corresponding to the non-conference call; receive access information from the conference server for accessing the requested conference call; and distribute the access information to each of the plurality of terminals, thereby allowing any terminal among the terminals to access the conference call.

[0019] Preferably, the client server, the UE, and the conference server are interconnected via a telecommunications network, which may include: a wireless network, including a wireless local area network; a fixed access or wired network; a public switched telephone network (PSTN); a common old-style telephone service (POTS) network; a satellite network; (at least, any standard-defined generation) a cellular network; HetNet; a network of networks; a broadband network; and / or the Internet. Preferably, the client server is not a component of the conference server, the UE, and / or the telecommunications network, and is located remotely from the conference server, the UE, and / or the telecommunications network.

[0020] As used herein, a telephone call or call preferably includes real-time voice, video, and / or teletactile communication. As used herein, the term "conference call" preferably means a single call capable of simultaneously including at least three parties (i.e., where the called party and / or the caller includes at least two members). As used herein, the term "non-conference call" preferably refers to a point-to-point call including only one called party and one caller. Preferably, the client server is an Internet Protocol (IP) telephone call processing server, device, or system. Preferably, the respective terminals are IP Protocol (IP) telephone terminals.

[0021] The above overview is not intended to describe every illustrated embodiment or implementation of the subject matter herein. The invention includes any novel aspects described and / or illustrated herein. The invention also extends to methods and / or apparatuses substantially as described herein and / or illustrated with reference to the accompanying drawings. The invention is also provided as computer programs and / or computer program products for performing any methods described herein and / or for implementing any apparatus features described herein, and as computer-readable media having stored thereon programs for performing any methods described herein and / or for implementing any apparatus features described herein. Features described as hardware implementations may alternatively be software implementations, and vice versa.

[0022] It should be understood that the various operations used in the methods of the present invention can be performed in any order and / or simultaneously, as long as the teachings remain operational. Furthermore, it should be understood that the apparatus and methods of the present invention may include any number or all of the described embodiments, provided the teachings remain operational.

[0023] Any device feature can also be provided as a corresponding step of the method, and vice versa. As used herein, device plus functional features can alternatively be represented according to their respective structures, for example, as a suitably programmed processor.

[0024] Any feature in one aspect of the invention may be applied to other aspects of the invention in any suitable combination. Any, some, and / or all features in one aspect may be applied to any, some, and / or all features in any other aspect in any suitable combination. Specific combinations of the various features described and defined in any aspect of the invention may be implemented and / or provided and / or used independently.

[0025] As used throughout the text, unless otherwise specified, the word "or" may be interpreted in an exclusive and / or inclusive sense.

[0026] The present invention extends to telephone systems as described herein and / or substantially as shown with reference to the accompanying drawings and methods of operating such telephone systems. The invention will now be described by way of example only, with reference to the accompanying schematic diagrams, in which: Figure 1 A schematic diagram of a telecommunications system is shown; Figure 2 Details of the telecommunications system were shown; and Figure 3 The method of operating a telecommunications system is shown.

[0027] While various embodiments are suitable for various modifications and alternatives, their details have been shown by example in the accompanying drawings and will be described in detail. However, it should be understood that the purpose is not to limit the claimed invention to the specific embodiments described. Rather, the invention is intended to cover all modifications, equivalents, and substitutions falling within the spirit and scope of the subject matter defined by at least the claims. Detailed Implementation

[0028] Figure 1 A schematic diagram of a telecommunications system 100 is shown.

[0029] Telecommunication system 100 includes: client domain (CD) 110, service provider (SP) 120, wide area telecommunications network (TN) 130, and conferencing server (CS) 140.

[0030] CD 110 includes multiple users 150 that typically operate independently, and each user is associated with a corresponding user equipment (UE) 160. Each UE is configured to communicate with TN 130 to participate in real-time video and / or audio telematics (hereinafter referred to as "calls"), including conference calls and non-conference calls. UEs are telecommunications devices in the following forms: telephones (including cellular, smart, delivery line, and / or satellite phones), tablets, laptops, and / or PCs. Each UE (and, through an agent, the corresponding user) is associated with a unique client identifier used to identify and establish calls to it. For example, client identifiers include telephone numbers, network addresses, user account profiles, and / or user IDs.

[0031] SP 120 includes: a telephone system (TS) 170, multiple terminals 180, and multiple agents 190.

[0032] SP 120 is a conceptual single entity that operates to provide services to user 150 via multiple agents 190 using corresponding terminals 180. For example, SP is a call center used for: customer support and / or inquiries, transactions, brokerage services and / or order processing, research, and / or marketing.

[0033] Each terminal 180 is configured to participate in calls, including conference calls and non-conference calls, and is operated by a corresponding agent 190. For example, multiple terminals are in the form of IP or Voice over Internet Protocol (VoIP) telecommunications equipment (e.g., appropriately configured telephones, tablets, laptops, and / or PCs). Each terminal communicates with TS 170 (e.g., via a local area network, including Ethernet and / or wireless LAN).

[0034] Each terminal 180 (and, via an agent, a corresponding agent 190) is associated with a unique terminal identifier used to identify and establish calls to it. For example, the terminal identifier may include a telephone number, network address, agent account profile, and / or agent ID.

[0035] The TS 170 is a call processing device that centrally controls the call processing of each terminal 180. For example, the TS can be in the form of a server on which appropriate call processing software runs.

[0036] Figure 2 The TS 170 is shown in more detail, including: an external input / output interface (EI / OI) 210, an internal input / output interface (II / OI) 220, a controller 230, a database 240, and a monitoring function (MF) 250.

[0037] The controller 230 is configured to communicate with each of the EI / OI 210, II / OI 220, database 240 and MF 250, and is further configured to perform data processing and communication.

[0038] Controller 230 is configured to communicate with TN 130 and with each of the terminals 180 via EI / OI 210 and II / OI 220, respectively, specifically to intercept outbound and inbound calls from and to the terminals. As used herein, an "outbound call" refers to a call from at least one of the terminals 180 from SP 120 to an external entity of SP (including any of the UEs 160), while an "inbound call" refers to a reverse call (e.g., a call from UE 160 to SP 120).

[0039] Furthermore, controller 230 is configured to communicate with CS 140 (e.g., via an appropriate application programming interface API) at least to request the establishment of a conference call and subsequently receive conference call information from the CS. The conference call information includes access information and status information.

[0040] Access information is information that notifies, identifies, and permits access to conference calls used by UE 160 and terminal 180. For example, access information includes: notifications, invitations, and / or warnings of incoming calls; and conference identifiers and access details, such as conference ID (or “thread ID”), telephone number, and / or network address (e.g., URL). Where the conference call is private or securely protected so that access is restricted only to authenticated devices and / or users, access information also includes access credentials (e.g., PIN, passcode, and / or password), encryption keys, and / or access certificates or tokens. Access information is typically generated by CS 140.

[0041] The status information indicates the status of the conference call, wherein the status includes: start and / or end time, and / or duration; participant identifiers (using, for example, client and / or terminal identifiers), including past, present and / or potential participants, the caller (i.e., the initiator of the call), the called party (i.e., the recipient of the call), and / or currently active (e.g., speaking or presenting) participants and / or the host; the capabilities and / or limitations of the conference call (e.g., audio, video, whiteboard, mute, capacity limits, etc.); and / or activity information, such as indications of active and / or held calls. Upon receiving the status information by controller 230, the information is transmitted to MF 250.

[0042] Database 240 includes a memory for storing packet information related to at least terminal 180. The packet information includes at least one group, wherein each group is associated with at least two terminal identifiers defined as members of the group and any number (including zero) of client identifiers.

[0043] A group comprises terminals 180 associated with at least two terminal identifiers, wherein assignment to a group indicates that a terminal (and its corresponding agent) is associated based on: team, location, license level or privilege, hierarchy, workflow, function, department, and / or role. Accordingly, when a group is associated with at least one client identifier, the UE associated with it is assigned to the corresponding terminal within that group. In this way, agents are effectively assigned to specific clients, and said assignments are stored in database 240.

[0044] Where appropriate, these groups may have any characteristics, including but not limited to: hierarchical or non-hierarchical structure, overlapping or non-overlapping structure, uniqueness, nesting, inheritability or non-inheritability, and / or defining group members inclusively or exclusively.

[0045] TN 130 is configured to facilitate calls (including circuit-switched and packet-switched calls) between at least SP 120 and CD 110, and to allow SP and CD access to CS 140.

[0046] TN 130 can therefore be used to include or exist in the form of: wireless networks, including wireless LANs; fixed access or wired networks; public switched telephone networks (PSTN); ordinary old-style telephone service (POTS) networks; satellite networks; (at least, any standard-defined generation) cellular networks; HetNet; networks of networks; broadband networks; and / or the Internet.

[0047] CS 140 is configured to establish and host conference calls for participation by either terminal 180 or UE 160 via TN 130. In this example, CS is external (or remote) to both CD 110 and SP 120 and is operated by a third party. For example, CS 140 is configured to provide conference calling functionality provided by: Microsoft Teams from Microsoft Corporation; Zoom from Zoom Video Communications, Inc.; Google Meet from Google Inc.; Slack from Slack Technologies LLC; WhatsApp Messenger from MetaPlatforms; and / or Webex from Cisco Systems, Inc.

[0048] Figure 3 and Figure 4 Each demonstrates the processing of operating SP 120 to provide greater local control over conference call functionality.

[0049] More specifically, Figure 3 The process 300 for operating SP 120 for outbound calls is shown.

[0050] In the first step 310, one of the agents 190 initiates a call to the UE 160 ("Calling Party") using the corresponding terminal 180 ("Called Party"), and the initiated call is intercepted by TS 170 and received by controller 230 via II / O-I220. The initiated call includes the identities of the calling party and the called party (collectively referred to as "Calling Parties") as corresponding terminal identifiers and client identifiers, which the controller obtains and stores in association with the initiated call.

[0051] In the next step 320, controller 230 determines whether the initiated call is a conference call or a non-conference call. For example, in response to a conference call request identifying address CS 140, the controller identifies the initiated call as a conference call. The conference call request includes: instructing CS 140 to establish a conference call for the caller; a called party identifier (a client identifier in this process 300) for receiving the conference call; and options for the conference call.

[0052] The component options for a conference call request include, for example: Media characteristics, such as: licensed media used for the call (e.g., audio, video, screen sharing, whiteboard, polling, chat, captioning or transcription, spatial video, file sharing, remote desktop control and / or telekinesis, etc.); communication protocols and parameters; and media quality; Security and privacy features, such as: call encryption, participant authentication, participant list, geo-locking, participant blacklist, waiting room, meeting lock, and / or media recording; Call processing, such as call holding, forwarding, transfer, termination and / or merging; and / or Call management, such as: host selection and authentication; participant authorization and / or removal, cancellation of privileges, automatic host delivery, host and participant capabilities, and / or modification of privileges and permissions for any of the above options.

[0053] It should be understood that the specific options selected for conference calls depend at least on the compatibility capabilities of the CS, which the TS is configured to determine (e.g., via API).

[0054] If, in step 320, controller 230 determines that the initiated call is a conference call, then process 300 proceeds to step 330-1, whereby the controller allows the conference call request of the initiated outbound conference call to proceed to CS 140.

[0055] In the subsequent step 340, upon receiving a conference call request, CS 140 establishes a conference call based on the received (client and terminal) identifiers and the specified options, and generates access information for the conference call.

[0056] After establishment, CS 140 transmits the generated access information to TS 170 via TN 130. The access information received by TS is then forwarded by TS to the caller (terminal) recorded by the controller (in step 320) as associated with the initiated call, and the terminal uses the access information to connect to the established conference call.

[0057] Access information is also received by the called party (UE), and an incoming call is alerted and access to the incoming call is allowed, wherein the incoming call is a conference call itself (e.g., where the UE has a known ability to directly participate in conference calls, such as a UE running a conference application compatible with CS 140), or a point-to-point call with the CS (e.g., using PSTN, VoLTE, or VoWiFi), which the CS then bridges to the conference call (e.g., where the UE does not have the ability to directly participate in conference calls (such as POTS terrestrial lines)).

[0058] In the next step 350, controller 230 queries database 240 to identify all groups associated with the calling parties. After identifying the groups, the database returns all terminal identifiers associated with the identified groups, except for the terminal identifier of the calling party; these members are referred to herein as “associated members”.

[0059] In the next step 360, using the corresponding terminal identifier, the controller 230 then distributes access information to the identified associated members. Upon receiving the access information at each associated member's terminal, the terminal displays an indication of the established conference call (e.g., on the terminal's display or indicator) and a corresponding option to connect to the call (e.g., a "Join" button) to the appropriate agent. In this way, regardless of whether any caller includes associated members in the initiated call, all associated members are notified of the conference call, and subsequently, all associated members are able, but not forced, to participate in the conference call using shared access information.

[0060] The controller also transmits access information to the MF 250.

[0061] In subsequent step 370, the MF requests the status information of the established conference call from the CS 140 (via the operation of the controller 230 and through the output from the EI / OI 210). Responsively, the CS 140 then registers the MF 250 as a subscriber to this status information, and the CS pushes the status information to the TS 170, which is routed to the MF for storage and subsequently delivered by the controller to at least the associated members of the displayed conference call. In this way, associated members can observe the status of the call without necessarily attending, providing more details to help them determine whether to join the conference call (e.g., based on the elapsed duration and / or participants).

[0062] Returning to step 320, if it is determined otherwise that the initiated call is not a conference call, process 300 proceeds to step 330-2, where controller 230 prevents the initiated call from being forwarded. Instead, TS 130 requests that a conference call be established for the calling parties. To do this, TS 130 generates a conference call request using the terminal identifier and client identifier associated with the initiated call. Subsequently, TS forwards the conference call request to CS via TN and establishes the conference call in the same manner as described above with reference to step 340. TS is configured to allow the inbound initiated call to continue ringing while awaiting the establishment of the conference call, or is configured to answer the call and request that the answered call be bridged to the requested conference call.

[0063] In this way, TS effectively replaces non-conference calls with the corresponding conference calls, and thus ensures that outbound calls (subject to overriding) are always conference calls. After step 330-2, and starting from the subsequent step 340, the process continues using the replaced conference calls.

[0064] Figure 4 It is used for processing SPs used for inbound calls.

[0065] In the first step 410, one of the users 150 initiates a non-conference call from the corresponding UE 160 (now the “caller” for this processing 400) to the SP via TN 130, and the call is received by TS 170.

[0066] The caller may directly call a specific terminal 180, or generally call SP 120, in which case, by means of appropriate call processing performed by TS, a specific terminal 180 (e.g., based on a group mapping between the caller's client identifier and available terminals in database 240) is selected to receive the call; the specific terminal is for the called party in processing 400.

[0067] In the next step 420, the initiated call is received by TS 170, and specifically by controller 230 via EI / OI 210. Controller 230 identifies the initiated call as an inbound non-conference call and identifies the calling parties by obtaining the associated client identifier and terminal identifier.

[0068] In the next step 430, to prevent the establishment of a point-to-point call, TS 170 prevents the initiated call from being forwarded and connected to the called party (e.g., from the caller's perspective, the initiated call remains in a ringing state or is answered by the TS). Instead, controller 230 uses the client identifier and terminal identifier to generate a conference call request for establishing a conference call. Controller 230 then forwards the conference call request to CS 140.

[0069] In the next step 440, upon receiving a conference call request, CS 140 establishes a conference call for all parties and transmits access information for the established conference call to all parties via TN 130 using client identifiers and terminal identifiers (in a manner corresponding to step 340 of processing 300).

[0070] The CS transmits access information to the calling party (UE) in a manner corresponding to that described with respect to step 340. Upon receiving this access information and accepting the conference call (either manually by the associated user or automatically by appropriate software running on the UE), the UE is connected to the established conference call. Thereafter, the original inbound call is effectively terminated.

[0071] In the next step 450, when the TS receives the access information, the controller 230 transmits the access information to the called party (terminal). When accepting a conference call, the terminal is also connected to the established conference call.

[0072] In this way, the parties to the call connect via a conference call rather than the original non-conference call; this allows for subsequent participation by associated members.

[0073] Processing 400 proceeds to step 460, and then to step 470. These two steps correspond to steps 360 and 370 of processing 300, respectively.

[0074] Alternative options and modified options

[0075] It should be understood that steps 370 and 470 can be performed at any time after TS 170 receives access information for the established conference call, and therefore, at least simultaneously with steps 350 and 450.

[0076] Where steps 370 and / or 470 overlap with steps 350 and 450, steps 360 and 460 are performed only in response to TS170 determining the participation of the called party and / or the calling party through the operation of MF 250. In this way, the alert to associated members regarding the conference call is only executed when the called party accepts and joins the conference call, thereby preventing agent 190 from being notified of attempted but failed calls.

[0077] In one embodiment, the system and / or its components or subsystems may include computing devices, microprocessors, modules, and other computers or computing devices, which may be any programmable means that accepts digital data as input, is configured to process the input according to instructions or algorithms, and provides results as output. In one embodiment, the computing and other such devices discussed herein may include, contain, or be coupled to instructions configured to execute computer programs, a central processing unit (CPU). Thus, the computing and other such devices discussed herein are configured to perform basic arithmetic, logic, and input / output operations.

[0078] The computing and other devices discussed herein may include memory. Memory may include volatile or non-volatile memory required by the coupled computing device or processor to provide not only space for executing instructions or algorithms, but also space for storing the instructions themselves. For example, in one embodiment, volatile memory may include random access memory (RAM), dynamic random access memory (DRAM), or static random access memory (SRAM). In one embodiment, non-volatile memory may include, for example, read-only memory, flash memory, ferroelectric RAM, hard disk, floppy disk, magnetic tape, or optical disk storage. The foregoing list does not limit the types of memory that can be used, as these embodiments are given by way of example only and are not intended to limit the scope of the invention.

[0079] In one implementation, the system or its components may include or comprise various modules or engines, each of which is constructed, programmed, configured, or otherwise adapted to autonomously perform a function or a set of functions. As used herein, the term "engine" is defined as a real-world device, component, or arrangement of components implemented using hardware, such as by an application-specific integrated circuit (ASIC) or a field-programmable gate array (FPGA), or by a combination of hardware and software, such as a microprocessor system and a set of program instructions that adapt the engine to perform a specific function, which (when executed) transforms the microprocessor system into a dedicated device. An engine may also be implemented as a combination of both, where some functions are facilitated by separate hardware, while other functions are facilitated by a combination of hardware and software. In some implementations, at least a portion of the engine may be executed on the processors of one or more computing platforms consisting of hardware that executes operating systems, system programs, and applications (e.g., one or more processors, data storage devices such as memory or drive storage, input / output devices such as network interface devices, video devices, keyboards, mice, or touchscreen devices, etc.), and may also be implemented using multitasking, multithreading, distributed (e.g., cluster, peer-to-peer, cloud, etc.) processing, or other such techniques, where appropriate. Therefore, each engine can be implemented in a variety of physically feasible configurations and should generally not be limited to any particular implementation illustrated herein unless such limitation is explicitly stated. Furthermore, an engine itself may consist of more than one sub-engine, each of which can be considered its own engine. Moreover, in the implementations described herein, each engine in the various engines corresponds to a defined autonomous function; however, it should be understood that in other contemplated implementations, each function may be assigned to more than one engine. Similarly, in other contemplated implementations, multiple defined functions may be implemented by a single engine that executes those multiple functions, possibly alongside other functions, or distributed differently within a set of engines, rather than specifically shown in the examples herein.

[0080] Various embodiments of the systems, apparatus, and methods have been described herein. These embodiments are given by way of example only and are not intended to limit the scope of the claimed invention. Furthermore, it should be understood that the various features of the described embodiments can be combined in various ways to produce many additional embodiments. In addition, although various materials, sizes, shapes, constructions, and locations, etc., for the disclosed embodiments have been described, other materials besides those disclosed may be used without departing from the scope of the claimed invention.

[0081] Those skilled in the art will recognize that embodiments may include fewer features than those shown in any single embodiment described above. The embodiments described herein are not intended to be an exhaustive representation of how various features can be combined. Therefore, these embodiments are not mutually exclusive combinations of features; rather, as will be understood by those skilled in the art, embodiments may include combinations of different individual features selected from different individual embodiments. Furthermore, elements described with respect to one embodiment may be implemented in other embodiments, even if not described in such embodiments, unless otherwise stated. While dependent claims may refer in the claims to specific combinations with one or more other claims, other embodiments may also include combinations of dependent claims with the subject matter of each other dependent claim, or combinations of one or more features with other dependent or independent claims. Such combinations are presented herein unless it is indicated that a particular combination is not desired. Furthermore, even if a claim is not directly dependent on an independent claim, it is intended to include features of that claim in any other independent claim.

[0082] Furthermore, references to "one embodiment," "implementation," or "some embodiments" in the specification mean that a specific feature, structure, or characteristic described in connection with that embodiment is included in at least one embodiment of the teachings. The appearance of the phrase "in one embodiment" in different places in the specification does not necessarily refer to the same embodiment.

[0083] Any reference to the foregoing documents is limited by reference such that no subject matter is incorporated herein, contrary to the express disclosure herein. Any reference to the foregoing documents is further limited by reference such that none of the claims included in those documents are incorporated herein by reference. Any reference to the foregoing documents is further limited by reference such that any definitions provided in the documents are not incorporated herein by reference unless expressly included herein.

[0084] Each feature disclosed herein and (where appropriate) is provided independently or in any suitable combination as part of the claims and drawings.

[0085] Any reference numerals appearing in the claims are for illustrative purposes only and should not limit the scope of the claims.

Claims

1. A method for operating a telephone system, the system comprising: The client server is configured as follows: Connect to the conference server used to establish conference calls; Connect multiple terminals to the conference server; as well as Communicate with the UE to receive calls from the UE; The method includes the following steps, performed by the client server: Detecting the initiation of a call between the UE and a given terminal among the plurality of terminals; Identify the UE and the given terminal; Assess whether the detected call is a conference call or a non-conference call; In response to the assessment that the call was a non-conference call: Request the conference server to establish a conference call for the identified UE and the given terminal, and corresponding to the non-conference call; Receive access information from the conference server for accessing the requested conference call; as well as The access information is distributed to each of the plurality of terminals, thereby allowing any terminal among the terminals to access the conference call.

2. The method according to claim 1, wherein, In response to the assessment that the call is a conference call, the client server: receives access information for the conference call from the conference server; and distributes the access information to each of the plurality of terminals.

3. The method according to claim 1 or 2, wherein, The detected call was initiated by the UE.

4. The method according to claim 1 or 2, wherein, The detected call was initiated by the given terminal.

5. The method according to any one of the preceding claims, wherein, The client server is configured to connect a superset of terminals to the conference server, the superset including the plurality of terminals and at least one additional terminal, and the method further includes the following steps: At the client server, the following is provided: A first group, comprising the plurality of terminals but excluding the at least one additional terminal; and The second group, which includes the at least one additional terminal but does not include the plurality of terminals; and The first group is identified as associated with the detected call, wherein, in response to the identification, the access information is sent to the first group and not to the second group.

6. The method according to any one of the preceding claims, further comprising the step of: The client server provides monitoring functionality for monitoring the status of the conference call; The access information for the conference call is transmitted to the monitoring function; The monitoring function uses the access information to query the conference server to obtain status information for the conference call; as well as The monitoring function shares the obtained status information with the multiple terminals.

7. The method according to claim 6, wherein, The sharing of the acquired state is performed in accordance with predefined rules based on the acquired state information.

8. The method according to any one of the preceding claims, the method further comprising the step of the client service detecting the participation of the UE in the conference call, and wherein, In response to the detected participation, the access information is distributed to each of the at least plurality of terminals other than the given terminal.

9. The method according to any one of the preceding claims, wherein, Identifying the UE and the given terminal includes obtaining their unique call addresses, and wherein requesting to establish the conference call includes passing the call address to the conference server.

10. The method according to any one of the preceding claims, wherein, Requesting to establish the conference call includes requesting to bridge the non-conference call to the requested conference call.

11. A computer-readable carrier medium comprising a computer program that, when executed by a computer, causes the computer to perform the steps according to any one of the preceding claims.

12. A telephone system, the telephone system comprising: Multiple terminals; as well as Client server, the client server includes: Network interface, the network interface being configured to: Connect to the conference server used to establish conference calls; Connect the plurality of terminals to the conference server; and Communicating with the UE to receive calls from the UE; and The controller is configured to: Detecting the initiation of a call between the UE and a given terminal among the plurality of terminals; Identify the UE and the given terminal; Assess whether the detected call is a conference call or a non-conference call; In response to the assessment that the call is a non-conference call, a request is made to the conference server to establish a conference call for the identified UE and the given terminal and corresponding to the non-conference call; Receive access information from the conference server for accessing the requested conference call; and The access information is distributed to each of the plurality of terminals, thereby allowing any terminal among the terminals to access the conference call.

Images