CN105915521B

CN105915521B - Multi-party call management method, device and terminal

Info

Publication number: CN105915521B
Application number: CN201610243929.6A
Authority: CN
Inventors: 高毅; 王洪强; 龙海
Original assignee: Beijing Xiaomi Mobile Software Co Ltd
Current assignee: Beijing Xiaomi Mobile Software Co Ltd
Priority date: 2016-04-18
Filing date: 2016-04-18
Publication date: 2020-05-19
Anticipated expiration: 2036-04-18
Also published as: CN105915521A

Abstract

The disclosure relates to a method, a device and a terminal for managing multi-party call. The method comprises the following steps: responding to call requests sent by at least two pieces of application software, and establishing different call connections according to the types of call requesters; and respectively receiving the call information sent by the contacts in different call connections, and sending the call information to the contacts in different call connections. By applying the scheme of the embodiment of the disclosure, the multi-party call established according to different call requests can be managed.

Description

Multi-party call management method, device and terminal

Technical Field

The present disclosure relates to the field of mobile communications technologies, and in particular, to a method, an apparatus, and a terminal for managing a multi-party call.

Background

At present, after a user uses a mobile terminal to make a call, if the user wants to request video chat through third-party social software such as WeChat, the user generally needs to hang up the phone to perform the video chat; or, when the user uses the third-party social software to perform voice or video, there is telephone access to friends, and at this time, the voice or video is generally required to be interrupted to answer the call.

Therefore, the communication method brings inconvenience to the communication use of the user.

Disclosure of Invention

The present disclosure provides a method, an apparatus, and a terminal for multi-party call management, which enable management of a multi-party call established according to different call requests.

According to a first aspect of the embodiments of the present disclosure, a method for multi-party call management is provided, including:

responding to call requests sent by at least two pieces of application software, and establishing different call connections according to the types of call requesters;

and respectively receiving the call information sent by the contacts in different call connections, and sending the call information to the contacts in different call connections.

Optionally, the responding to the call requests sent by the at least two application software, and establishing different call connections according to the types of call requesters includes:

receiving a call request initiated by a local system or third-party software;

under the condition that the call request is judged to be initiated by the local system, a first link of a call party with the local system is established by using an operator voice network, and under the condition that the call request is judged to be initiated by third-party software, a second link of the call party with the third-party software is established by using a wireless network, wherein the first link and the second link are independent.

Optionally, the method further includes:

when the call request initiated by a local system or third-party software is received or the first link or the second link is established, displaying at least one of the following information related to the contact in a call management interface: phone number, name, social account number, third party software name.

Optionally, the call request initiated by the third-party software is initiated when the third-party software reads that a call currently exists in the local system through an interface open to the third-party software.

Optionally, the call information includes voice call information or video call information.

Optionally, the receiving the call information sent by the contacts in different call connections respectively, and sending the call information to the contacts in different call connections respectively includes:

receiving the call voice sent by the local system calling party through a modem on the first link, and receiving the call voice sent by the third-party software calling party through third-party software on the second link;

and acquiring microphone voice monitored by a monitoring mechanism of a local system or third-party software, sending the microphone voice to a local system calling party through the first link, and sending the microphone voice to the third-party software calling party through the second link.

Optionally, the call request initiated by the local system includes contact information of a local system call party, and is established according to the contact information of the local system call party when the first link is established;

the call request initiated by the third-party software comprises contact information of a third-party software calling party, and the call request is established according to the contact information of the third-party software calling party when the second link is established.

According to a second aspect of the embodiments of the present disclosure, there is provided an apparatus for multiparty call management, including:

the first processing module is used for responding to the call requests sent by at least two pieces of application software and establishing different call connections according to the types of call requesters;

and the second processing module is used for respectively receiving the call information sent by the contacts with different call connections established by the first processing module and sending the call information to the contacts with different call connections.

Optionally, the first processing module includes:

the request receiving submodule is used for receiving a call request initiated by a local system or third-party software;

and the link establishing submodule is used for establishing a first link with a local system calling party by using an operator voice network under the condition that the call request received by the request receiving submodule is judged to be initiated by a local system, and establishing a second link with a third-party software calling party by using a wireless network under the condition that the call request received by the request receiving submodule is judged to be initiated by third-party software, wherein the first link and the second link are independent.

Optionally, the first processing module further includes:

the interface display sub-module is used for displaying at least one of the following information related to the contact in a call management interface when the request receiving sub-module receives a call request initiated by a local system or third-party software or when the link establishing sub-module establishes the first link or the second link: phone number, name, social account number, third party software name.

Optionally, the first processing module further includes:

the interface setting submodule is used for setting an interface which is opened towards the third-party software;

the call request initiated by the third-party software received by the request receiving submodule is initiated when the third-party software reads that a call currently exists in a local system through an interface which is arranged by the interface setting submodule and is open to the third-party software.

Optionally, the second processing module includes:

the receiving submodule is used for receiving the call voice sent by the local system calling party through a modem in the first link and receiving the call voice sent by the third-party software calling party through third-party software in the second link;

and the sending submodule is used for acquiring microphone voice which is monitored by a monitoring mechanism of a local system or third-party software, sending the microphone voice to a local system calling party through the first link, and sending the microphone voice to the third-party software calling party through the second link.

According to a third aspect of the embodiments of the present disclosure, there is provided a call terminal including:

a processor and a memory for storing processor-executable instructions;

wherein the processor is configured to:

The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects: the method and the device establish different call connections for the call requests sent by at least two application software according to the types of call requesters, respectively receive call information sent by contacts in different call connections, and send the call information to the contacts in different call connections, thereby realizing management of multi-party calls, enabling a plurality of calls to exist simultaneously if another call request is available in one of the call processes, for example, a WeChat video call request is available in the call process, the call does not need to be hung up and then the WeChat video call is carried out, and greatly facilitating call use of users.

The method and the device can be suitable for call requests sent by different application software, for example, the call requests of a local system can be used, the call requests of third-party software can also be used, under the condition that the call requests are initiated by the local system, a first link of a call party with the local system is established by using an operator voice network, and under the condition that the call requests are initiated by the third-party software, a second link of the call party with the third-party software is established by using a wireless network.

According to the method and the device, an interface which is open to third-party software can be set, wherein a call request initiated by the third-party software can be initiated when the third-party software reads that a call currently exists in a local system through the interface which is open to the third-party software.

The present disclosure may be applicable to different calls, for example, the call information may be voice call information or video call information.

The method and the device can display at least one item of the following information related to the contact in the call management interface for the user to refer to for the convenience of user selection: phone number, name, social account number, third party software name.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a flow chart illustrating a method of multi-party call management according to an exemplary embodiment of the present disclosure.

FIG. 2 is a flow chart illustrating another method of multi-party call management according to an exemplary embodiment of the present disclosure.

FIG. 3 is a block diagram illustrating an apparatus for multi-party call management according to an example embodiment of the present disclosure.

FIG. 4 is a block diagram illustrating another apparatus for multiparty call management according to an example embodiment of the present disclosure.

Fig. 5 is a block diagram illustrating a telephony terminal according to an example embodiment of the present disclosure.

Fig. 6 is another block diagram of a terminal shown in accordance with an exemplary embodiment of the present disclosure.

FIG. 7 is a call management interface diagram of a three-way call shown in accordance with an exemplary embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It is to be understood that although the terms first, second, third, etc. may be used herein to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.

The present disclosure provides a method of multi-party call management, which enables management of multi-party calls established according to different call requests.

The method can be applied to a terminal, and as shown in fig. 1, the method can include the following steps:

in step 101, in response to call requests sent by at least two application software, different call connections are established according to the types of call requesters.

Wherein, this step can include:

receiving a call request initiated by a local system or third-party software;

and under the condition that the call request is judged to be initiated by the local system, establishing a first link with a call party of the local system by using the operator voice network, and under the condition that the call request is judged to be initiated by third-party software, establishing a second link with the call party of the third-party software by using the wireless network, wherein the first link and the second link are independent.

When a call request initiated by a local system or third-party software is received or a first link or a second link is established, at least one of the following information related to a contact person can be displayed in a call management interface: phone number, name, social account number, third party software name, etc.

The call request initiated by the third-party software may be initiated when the third-party software reads that a call currently exists in the local system through an interface open to the third-party software.

In step 102, the call information sent by the contacts with different call connections is received, and the call information is sent to the contacts with different call connections.

The call information may be voice call information or video call information.

Wherein, this step can include:

receiving the call voice sent by a local system calling party through a modem on a first link, and receiving the call voice sent by a third party software calling party through third party software on a second link;

and acquiring microphone voice monitored by a monitoring mechanism of the local system or third-party software, sending the microphone voice to a local system calling party through a first link, and sending the microphone voice to a third-party software calling party through a second link.

The step can receive the call information of the local system call party through the first link and the call information of the third-party software call party through the second link in sequence or simultaneously, and can also send the call information to the local system call party through the first link and send the call information to the third-party software call party through the second link in sequence or simultaneously.

It can be seen from this embodiment that, in the present disclosure, different call connections are established for call requests sent by at least two application software according to the types of call requesters, call information sent by contacts in different call connections is received respectively, and the call information is sent to the contacts in different call connections at the same time, so that management of multi-party calls is achieved, and if there is another call request in one of the call processes, there is no need to hang up the call, and there can be multiple calls at the same time, for example, there is a WeChat video call request in the call process, there is no need to hang up the call and then make a WeChat video call, thereby greatly facilitating call use of users.

The method can be applied to a terminal, and the embodiment describes the technical scheme of the disclosure in more detail with respect to fig. 1.

The multi-party call established in the present disclosure, not referring to a conference call, the parties of the conference call can hear each other's voice, the multi-party call in the present disclosure refers to, for example, users a and B have a phone call and a social call with C, a can hear B, C voice sequentially or simultaneously, B, C can hear a voice sequentially or simultaneously, but B and C cannot hear each other.

The method and the device for calling the application software are applicable to calling requests sent by different application software, for example, the calling requests can be calling requests of a local system, or calling requests of third-party software (for example, third-party social software), and the like. A local system generally refers to a system in which the terminal itself can make a call. Generally, if the third-party software needs to make a voice call, a video call and the like, the third-party software is provided with a call management interface. In order to better realize multi-party call, a multi-party call management device is arranged in the terminal to uniformly manage the call and manage a call management interface of the terminal. The terminal can open an interface to the third-party software, namely, an interface which is open to the third-party software is set, so that the third-party software can establish a call through a multi-party call management device set by the terminal.

The technical solution is described in detail below with reference to fig. 2. As shown in fig. 2, the method may include the steps of:

in step 201, a call request initiated by a local system is received, and a first link with a calling party of the local system is established by using a voice network of an operator.

The call request may be a voice call request or a video call request. The call request may include contact information of the call request, which may include: phone numbers, social account numbers or names, etc. The contact information can be carried in the call request, or can be obtained after being searched in the system according to the call request. Upon receiving the call request, the contact information of the call request may be displayed in a call management interface.

In the step, the terminal acquires a telephone number input by a user on a dial pad of the local system, and further acquires a voice call request after the user clicks voice dialing, wherein the voice call request is sent to a multi-party call management device arranged in the terminal. The multi-party call management device firstly judges the type of a call request initiator, recognizes that a voice call request comes from a local system, reads the telephone number, the name and the like of a contact person in the voice call request, calls a dialing interface of the local system, and carries out a normal dialing process, namely establishes a voice call link through a voice network of an operator. It should be noted that, when the call request does not include information such as names of contacts, the multi-party call management apparatus may read the names of contacts corresponding to the telephone number in the address book according to the telephone number in the voice call request.

When the device for managing the multi-party call arranged in the terminal establishes a voice call link through a voice network of an operator, the telephone number and the name can be displayed on a call management interface.

In step 202, a call is transmitted over a first link with a local system party.

In the step, the call information of the local system call party is received through the first link, and the call information is sent to the local system call party through the first link.

In step 203, a call request initiated by the third-party software is received, and a second link with a third-party software calling party is established by using the wireless network.

The second link established in the step is independent from the first link established in the step.

In this step, the third-party software initiates the video call request, for example, but not limited thereto. Assuming that a video call request of a video friend initiated by third-party software is received in the telephone call process, the terminal acquires the video call request and sends the video call request to a multi-party call management device arranged in the terminal. The multi-party call management device judges the type of a call request initiator, recognizes that a video call request comes from third-party software, reads the social account number, name, link (used for establishing a voice link and a video call link) and the like of a friend set in the request by the third-party software in the video call request, and establishes a video call link with the friend by using a wireless network.

In addition, when a video call request is received or a video call link is established, the social contact account number, the name of a friend, the name of third-party software and the like can be displayed in a call management interface.

It can be found that when the device for managing the multi-party call in the terminal is carrying out a call, if a new call request is received at this time, the call connection can be carried out no matter the call is initiated by the local system of the terminal or the third-party software, and similar to the current normal voice multi-party call, the device for managing the multi-party call is only responsible for the call management of the third-party software besides the voice call of the local system. For example, a voice call is being made to the local system, and a video call or a voice call to the third-party software may also be established at the same time.

That is, when the user is making a call (whether a local system call or a third-party software call), if the local system of the terminal receives an incoming call request or the third-party software receives a voice or video chat request, the local system and the third-party software will send the call request to the device for managing the multiparty call in the terminal, and the request may include a phone number, a social account number, a name, etc.

In step 204, the call is transmitted over a second link with a third party software caller.

In the step, the call information of the third-party software calling party is received through the second link, and the call information is sent to the third-party software calling party through the second link.

It should be noted that, in the

above steps

202 and 204, the call may be sequentially or simultaneously sent to the local system caller through the first link and sent to the third-party software caller through the second link, and the call of the local system caller may be sequentially or simultaneously received through the first link and the call of the third-party software caller may be sequentially or simultaneously received through the second link. That is, the users a and B have a phone call and a social call with C, a can hear B, C sound and B, C can hear a sound in sequence or simultaneously, but B and C cannot hear each other.

It should also be noted that the multi-party call set by the present disclosure does not generate audio mixing. The method can acquire the microphone voice monitored by a monitoring mechanism of a local system or third-party software, and send the microphone voice to a local system calling party through a first link and a third-party software calling party through a second link; and receiving the call voice sent by the local system calling party through the modem on the first link, and receiving the call voice sent by the third-party software calling party through the third-party software on the second link. For example, a user A and B have a local system telephone call and a third party social voice call; the voice of the user A at the microphone is respectively monitored and acquired through a monitoring mechanism of a local system or third-party software, and is respectively transmitted to the user B through a first link and transmitted to the user C through a second link; b voice is sent to A from the first link through the modem; the voice sent by the user C through the third-party software is sent to the user A from the second link; a can hear the voices of B and C at the same time, B and C can also hear the voice of A at the same time, but B and C cannot hear each other.

In addition, if the call is a video call, by the method disclosed by the invention, A can see the video pictures of B and C at the same time, B and C can see the video picture of A at the same time, but the video picture of the other party cannot be seen between B and C. Therefore, the multi-party of the present disclosure is that for a, a multi-party call can be performed with B and C, and B and C do not transmit call information to each other.

It should be noted that, the above is exemplified by receiving the local system call request first and responding, or receiving the third party software call request first and then receiving the local system call request and responding.

It should be noted that, when the call request is received or the link is established, different call connections and/or contact information may be simultaneously displayed in the call management interface.

That is to say, after receiving the call request, the multi-party call management apparatus of the present disclosure may display the phone number, the social account number, the name, and the like in the call management interface for the user to refer to, and the user may select to answer or reject. After answering, the call is successfully established, the user can carry out voice and video chat with the other party, and the related information can be continuously displayed in the call management interface.

If a plurality of calls exist after the calls are successfully established, the contact information of each call can be sequentially displayed from top to bottom in the call management interface. If the call is a video call, the video image of the opposite side can be displayed beside the contact information.

In addition, different control buttons can be displayed in the call management interface according to the type of the call requester.

For example, when a multi-party call is performed, the display area of each contact information may display a corresponding call control button, for example, a mute button, a play-out button, a pause button, and the like may be provided during a normal telephone call. The call control buttons can be distinguished according to call types, and the control buttons of different call types are different. If the local system call is the call by using the operator voice network, the call control button can be consistent with the control button of the current normal call, and the method comprises the following steps: mute, play out, pause, add call, etc. If the third-party software calls, the third-party software calls by using the wireless network, and the call control button can be provided with a putting and receiver button. In addition, an "add call" button may be provided when using the voice video function.

Display of call management interface referring to fig. 7, fig. 7 is a schematic view of a call management interface for a three-party call shown in accordance with an exemplary embodiment of the present disclosure. As shown in fig. 7, the user makes a phone call with the local system calling party named higher one, and makes a social call with the third-party software calling party named zhangsan123 (account name) by using the third-party software. Displaying that a first higher conversation source with a local system conversation party is 'system conversation' in the interface, and displaying a first higher head portrait; the interface displays that the calling source of Zhang III who has called with the third-party software is 'WeChat APP (Application)', and displays the head portrait of Zhang III. And the call management interface also displays function buttons such as mute, hang-up and tentative buttons which are respectively set for the local system call and the social call, and all hang-up buttons which simultaneously control the local system call and the social call. The call management interface in the figure also displays that the local system call is in the middle of speaking, and the social call is open to three. It should be noted that the call management interface of the three-party call of the present disclosure is illustrated in fig. 7 by way of example and not limitation.

Corresponding to the embodiment of the application function implementation method, the disclosure also provides a device and a terminal for managing the multi-party call and a corresponding embodiment.

The apparatus may be provided in a terminal. As shown in fig. 3, the apparatus for managing a multi-party call may include: a first processing module 31 and a second processing module 32.

The first processing module 31 is configured to respond to call requests sent by at least two pieces of application software, and establish different call connections according to types of call requesters.

The call request may be a voice call request or a video call request. The first processing module 31 receives a call request initiated by a local system or third-party software; and under the condition that the call request is judged to be initiated by the local system, establishing a first link with a call party of the local system by using the operator voice network, and under the condition that the call request is judged to be initiated by third-party software, establishing a second link with the call party of the third-party software by using the wireless network, wherein the first link and the second link are independent.

The second processing module 32 is configured to receive call information sent by contacts with different call connections established by the first processing module 31, and send the call information to the contacts with different call connections.

The call information may be voice call information or video call information.

The second processing module 32 may sequentially or simultaneously receive the call information of the local system call party through the first link and receive the call information of the third-party software call party through the second link, and may also sequentially or simultaneously send the call information to the local system call party through the first link and send the call information to the third-party software call party through the second link.

FIG. 4 is another block diagram of an apparatus for multiparty call management illustrated by the present disclosure in accordance with an exemplary embodiment.

The apparatus may be provided in a terminal. As shown in fig. 4, the apparatus for managing a multi-party call may include: a first processing module 31 and a second processing module 32.

The functions of the first processing module 31 and the second processing module 32 can be referred to the description in fig. 3.

The first processing module 31 may include: request receiving submodule 311 and link establishing submodule 312.

And the request receiving submodule 311 is configured to receive a call request initiated by a local system or third-party software.

The link establishing sub-module 312 is configured to establish a first link with a local system using an operator voice network when it is determined that the call request received by the request receiving sub-module 311 is initiated by the local system, and establish a second link with a third-party software call party using a wireless network when it is determined that the call request received by the request receiving sub-module 311 is initiated by the third-party software, where the first link and the second link are independent of each other.

Wherein, the first processing module may further include: the interface displays sub-module 313.

The interface display sub-module 313 is configured to display, in the call management interface, at least one of the following information related to the contact when the request receiving sub-module 311 receives a call request initiated by the local system or the third-party software, or when the link establishing sub-module 312 establishes the first link or the second link: phone number, name, social account number, third party software name, etc.

Wherein, the first processing module may further include: an interface setting sub-module 314.

And the interface setting submodule 314 is used for setting an interface which is open to third-party software.

The call request initiated by the third-party software received by the request receiving sub-module 311 is initiated when the third-party software reads that a call currently exists in the local system through the interface which is set by the interface setting sub-module 314 and is open to the third-party software.

The second processing module 32 may include: a receiving submodule 321 and a sending submodule 322.

The receiving submodule 321 is configured to receive, in the first link, the call voice sent by the local system caller through the modem, and receive, in the second link, the call voice sent by the third-party software caller through the third-party software.

The sending submodule 322 is configured to obtain microphone voice that is monitored by a monitoring mechanism of the local system or the third-party software, send the microphone voice to the local system calling party through the first link, and send the microphone voice to the third-party software calling party through the second link.

The receiving submodule 321 may receive, sequentially or simultaneously, call information of a local system call party through the first link and call information of a third-party software call party through the second link; the sending sub-module 322 may send the call information to the local system caller over the first link and the third party software caller over the second link in sequence or simultaneously.

In addition, the interface display sub-module 313 may also display different control buttons in the call management interface according to the type of the call requester. If the call is the call of the local system of the terminal, the call is carried out by using the voice network of the operator, and the call control button can be consistent with the control button of the current normal call, comprising the following steps: mute, play out, pause, add call, etc. If the third-party software calls, the third-party software calls by using the wireless network, and the call control button can be provided with a putting and receiver button.

The implementation process of the functions and actions of each unit in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and the parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the disclosed solution. One of ordinary skill in the art can understand and implement it without inventive effort.

Fig. 5 is a block diagram illustrating the present disclosure according to an exemplary embodiment.

As shown in fig. 5, includes: a processor 501 and a memory 502 for storing processor-executable instructions;

wherein the processor 501 is configured to:

It should be further noted that other programs stored in the memory 502 refer to the description in the foregoing method flow, which is not described herein again, and the processor 501 is also configured to execute the other programs stored in the memory 502.

Fig. 6 is a block diagram illustrating an arrangement of a device according to an exemplary embodiment of the present disclosure.

For example, the device 600 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like.

Referring to fig. 6, device 600 may include one or more of the following components: processing component 602, memory 604, power component 606, multimedia component 608, audio component 610, input/output (I/O) interface 612, sensor component 614, and communication component 616.

The processing component 602 generally controls overall operation of the device 600, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 602 may include one or more processors 620 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 602 can include one or more modules that facilitate interaction between the processing component 602 and other components. For example, the processing component 602 can include a multimedia module to facilitate interaction between the multimedia component 608 and the processing component 602.

The memory 604 is configured to store various types of data to support operation at the device 600. Examples of such data include instructions for any application or method operating on device 600, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 604 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

A power supply component 606 provides power to the various components of the device 600. The power components 606 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 600.

The multimedia component 608 includes a screen that provides an output interface between the device 600 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 608 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the device 600 is in an operating mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 610 is configured to output and/or input audio signals. For example, the audio component 610 includes a Microphone (MIC) configured to receive external audio signals when the device 600 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 604 or transmitted via the communication component 616. In some embodiments, audio component 610 further includes a speaker for outputting audio signals.

The I/O interface 612 provides an interface between the processing component 602 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor component 614 includes one or more sensors for providing status assessment of various aspects of the device 600. For example, the sensor component 614 may detect an open/closed state of the device 600, the relative positioning of components, such as a display and keypad of the device 600, the sensor component 614 may also detect a change in position of the device 600 or a component of the device 600, the presence or absence of user contact with the device 600, orientation or acceleration/deceleration of the device 600, and a change in temperature of the device 600. The sensor assembly 614 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 614 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 614 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 616 is configured to facilitate communications between the device 600 and other devices in a wired or wireless manner. The device 600 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 616 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 616 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the device 600 may be implemented by one or more Application Specific Integrated Circuits (ASICs)

(ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), controller, microcontroller, microprocessor or other electronic component, for performing the above method.

In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 604 comprising instructions, executable by the processor 620 of the device 600 to perform the above-described method is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

A non-transitory computer readable storage medium having instructions therein, which when executed by a processor of a terminal device, enable the terminal to perform a method of multiparty call management, the method comprising:

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A multi-party call management method is applied to a call terminal, and is characterized by comprising the following steps:

the call terminal responds to call requests sent by at least two pieces of application software and establishes different call connections according to the types of call requesters;

respectively receiving call information sent by the contacts in different call connections, and sending the call information to the contacts in different call connections;

the responding to the call requests sent by at least two application software and establishing different call connections according to the types of call requesters comprises the following steps:

receiving a call request initiated by a local system or third-party software, wherein the call request initiated by the third-party software is initiated by the third-party software when reading that a call currently exists in the local system through an interface opened to the third-party software;

under the condition that the call request is judged to be initiated by a local system, a first link of a call party with the local system is established by using an operator voice network, and under the condition that the call request is judged to be initiated by third-party software, a second link of the call party with the third-party software is established by using a wireless network, wherein the first link and the second link are independent;

the receiving the call information sent by the contacts with different call connections respectively and sending the call information to the contacts with different call connections respectively includes:

2. The method of claim 1, further comprising:

3. The method of claim 1, wherein the call information comprises voice call information or video call information.

4. A method according to any one of claims 2 to 3, characterized in that:

the call request initiated by the local system comprises contact information of a local system call party, and is established according to the contact information of the local system call party when the first link is established;

5. A multi-party call management device is applied to a call terminal and is characterized by comprising:

the second processing module is used for respectively receiving call information sent by the contacts with different call connections established by the first processing module and sending the call information to the contacts with different call connections;

the first processing module comprises:

the request receiving submodule is used for receiving a call request initiated by a local system or third-party software, wherein the call request initiated by the third-party software is initiated by the third-party software when reading that a call currently exists in the local system through an interface opened to the third-party software;

the link establishing submodule is used for establishing a first link with a local system calling party by using an operator voice network under the condition that the call request received by the request receiving submodule is judged to be initiated by a local system, and establishing a second link with a third-party software calling party by using a wireless network under the condition that the call request received by the request receiving submodule is judged to be initiated by third-party software, wherein the first link and the second link are independent;

the second processing module comprises:

6. The apparatus of claim 5, wherein the first processing module further comprises:

7. The apparatus of claim 5, wherein the first processing module further comprises:

and the interface setting submodule is used for setting an interface which is open for the third-party software.

8. A telephony terminal, comprising:

a processor and a memory for storing processor-executable instructions;

wherein the processor is configured to:

receiving a call request initiated by a local system or third-party software, wherein the call request initiated by the third-party software and received by the request receiving submodule is initiated when the third-party software reads that a call currently exists in the local system through an interface which is arranged by the interface setting submodule and is open to the third-party software;