A method, apparatus, and medium for implementing a conference call

Abstract

The application provides a conference call implementation method, device and medium. The method is applied to a first electronic device. The method comprises the following steps: obtaining a call merging operation of a user, wherein the call merging operation is used for merging a first call and a second call into a conference call; in response to the call merging operation, establishing a conference call session based on the call merging operation; requesting a conference server to merge the first call and the second call into a conference call, and receiving conference information of the conference call from the conference server; determining that the first electronic device is neither a conference chairman in the first call nor a conference chairman in the second call, updating the second call based on the conference information, binding the conference call session and the second call, and creating a conference call of the conference call. The method can enable conference members of the conference call to also merge calls, and realize a cascade function of the conference call.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of electronic devices, and in particular, to a conference call implementation method, device and medium. BACKGROUND

[0002] Conference call under Internet Protocol Multimedia Subsystem (IMS) is a basic function commonly used in overseas markets. A user can dial or receive a call, and after the call is connected, the user dials a second call, and after the second call is connected, a conference call can be created by merging the two calls. At this time, the three participants of the conference call can hear each other's voices.

[0003] Currently, when electronic device A establishes a conference call with electronic device B and electronic device C, as shown in FIG. 1, only the conference chairman (i.e., electronic device A) can add electronic device D to the conference call, as shown in FIG. 2, and the conference members (i.e., electronic device B or electronic device C) cannot add electronic device D to the conference call, as shown in FIG. 3, which cannot meet the actual use requirements of users. Figure 1a Figure 1b SUMMARY

[0004] Some embodiments of the present application provide a conference call implementation method, device and medium. The following aspects of the present application are described below, and the embodiments and advantages of the following aspects can be mutually referenced.

[0005] In a first aspect, the embodiments of the present application provide a conference call implementation method applied to a first electronic device. The method includes:

[0006] obtaining a call merging operation of a user, the call merging operation being used to merge a first call and a second call into a conference call; wherein the first call is a call between the first electronic device and at least one second electronic device that is on hold, and the second call is a call between the first electronic device and a third electronic device that is in progress;

[0007] in response to the call merging operation, establishing a conference call session based on the call merging operation;

[0008] requesting a conference server to merge the first call and the second call into the conference call, and receiving conference information of the conference call from the conference server;

[0009] determining that the first electronic device is not a conference chairman in the call roles in the first call and the second call, updating the second call based on the conference information, binding the conference call session with the second call, and creating a conference call. ​​

[0010] According to the embodiment of the present application, after the first electronic device obtains the talk merge operation of the user, in the case that the first electronic device is determined not to be the chairman in the first talk and the second talk, the created conference call session is bound with the second talk, and the second talk is updated according to the conference information of the conference call, so as to realize the creation of the conference call of the conference call. This conference call implementation manner enables the conference member of the conference call to also merge the talk, realizes the cascade function of the conference call, and improves the user experience. Moreover, the first electronic device realizes the talk merge by modifying in the application framework layer, so that the conference call cascade function of various chip platforms can be supported at the same time, and the applicability is good.

[0011] In some embodiments, the conference call session based on the talk merge operation is established, including:

[0012] Conference attribute information of the conference call is obtained, and the conference call session is established based on the conference attribute information.

[0013] According to the embodiment of the present application, the first electronic device can establish the conference call session based on the conference attribute information, so as to process various events related to the conference call creation.

[0014] In some embodiments, the determination that the first electronic device is not the chairman in the first talk includes:

[0015] It is determined that the talk attribute of the first talk is a normal talk; or,

[0016] It is determined that the talk attribute of the first talk is a conference call, and it is determined that the talk role of the first electronic device in the first talk is a conference member.

[0017] The determination that the first electronic device is not the chairman in the second talk includes:

[0018] It is determined that the talk attribute of the second talk is a normal talk; or,

[0019] It is determined that the talk attribute of the second talk is a conference call, and it is determined that the talk role of the first electronic device in the second talk is a conference member.

[0020] According to the embodiment of the present application, the first electronic device can determine whether the first electronic device is the chairman in the first talk and the second talk according to the talk attribute and the talk role of the device in the talk, the determination method is simple, and the accuracy of the determination result can be ensured.

[0021] In some embodiments, the method further includes:

[0022] In a case where it is determined that the call role of the first electronic device in the first call is not the conference chair, the conference call session is saved.

[0023] According to the embodiment of the present application, in a case where it is determined that the call role of the first electronic device in the first call is not the conference chair, the first electronic device can save the established conference call session, so that the conference call is created based on the conference call session.

[0024] In some embodiments, the method further comprises:

[0025] In a case where it is determined that the call role of the first electronic device in the first call is the conference chair, or it is determined that the call role of the first electronic device in the second call is the conference chair, the step of updating the second call based on the conference information is not performed, the conference call session is bound to the second call, and the conference call of the conference call is created.

[0026] According to the embodiment of the present application, in a case where it is determined that the call role of the first electronic device in the first call is the conference chair, or it is determined that the call role of the first electronic device in the second call is the conference chair, the first electronic device can determine that the conference call of the conference call does not need to be created, i.e. the created conference call session does not need to be bound to the second call, thereby avoiding waste of system resources.

[0027] In some embodiments, the conference server is requested to merge the first call and the second call into the conference call, and conference information of the conference call is received from the conference server, including:

[0028] The call merge request is sent to the conference server, and the call merge request is used to request the conference server to merge the first call and the second call into the conference call.

[0029] The conference information of the conference call returned after the conference server merges the first call and the second call into the conference call is received.

[0030] According to the embodiment of the present application, the first electronic device can send the call merge request to the conference server, request the conference server to merge the first call and the second call into the conference call and return the conference information, and update the second call based on the conference information, so that the updated second call can provide services for the conference call, thereby improving the creation efficiency of the conference call and saving system resource consumption.

[0031] In some embodiments, the method further comprises:

[0032] The conference subscription request is sent to the conference server, and the conference subscription request is used to obtain participant information of the conference call from the conference server, the participant information including information of the second electronic device and information of the third electronic device.

[0033] receiving the conference subscription result from the conference server;

[0034] if the conference subscription result indicates that the conference subscription is successful, receiving subscription information from the conference server, the subscription information including participant information of the conference call;

[0035] creating a first sub-call of the conference call according to the information of the second electronic device, and creating a second sub-call of the conference call according to the information of the third electronic device.

[0036] According to the embodiments of the present application, the first electronic device can obtain the participant information of the conference call by sending a conference subscription request to the conference server, and then create two sub-calls of the conference call according to the participant information, thereby realizing the individual management of different participants.

[0037] In some embodiments, the method further includes:

[0038] displaying a conference interface of the conference call, the conference interface including the information of the second electronic device and the information of the third electronic device.

[0039] According to the embodiments of the present application, the first electronic device displays the conference interface of the conference call and displays the participant information in the conference interface, so that the user can know that he is currently in the conference call and can perceive the information of the participants of the conference call, thereby ensuring the user experience of using the conference call.

[0040] In a second aspect, the embodiments of the present application provide an electronic device, including: a memory for storing instructions executed by one or more processors of the electronic device; and the processor, when executing the instructions in the memory, can make the electronic device execute the implementation method of the conference call provided by any of the embodiments of the first aspect of the present application. The beneficial effects achieved by the second aspect can refer to the beneficial effects of any of the embodiments of the first aspect of the present application, which will not be repeated here.

[0041] In a third aspect, the embodiments of the present application provide a computer-readable storage medium, and the computer-readable storage medium stores instructions, which, when executed on a computer, make the computer execute the implementation method of the conference call provided by any of the embodiments of the first aspect of the present application. The beneficial effects achieved by the third aspect can refer to the beneficial effects of any of the embodiments of the first aspect of the present application, which will not be repeated here. BRIEF DESCRIPTION OF DRAWINGS

[0042] Figure 1a a schematic diagram of a scenario in which a conference chairman adds members to join a conference provided for some embodiments;

[0043] Figure 1bA scenario diagram of adding a member into a conference for some embodiments of the conference member;

[0044] Figure 2a And Figure 2b A scenario diagram of a conference call for an embodiment of the application;

[0045] Figure 3 A scenario diagram of establishing a new call for some embodiments of the conference member;

[0046] Figure 4a And Figure 4b A flowchart of the IMS framework logic for some embodiments of the application;

[0047] Figure 4c A scenario diagram of merging a call for some embodiments of the conference member;

[0048] Figure 5a A structural diagram of an electronic device for an embodiment of the application;

[0049] Figure 5b A software structural block diagram of an electronic device for an embodiment of the application;

[0050] Figure 6 A flowchart of an implementation method of a conference call for an embodiment of the application;

[0051] Figure 7 A scenario diagram of merging a call for an embodiment of the conference member;

[0052] Figure 8 A flowchart of an implementation method of a conference call for an embodiment of the application;

[0053] Figure 9a And Figure 9b A flowchart of determining to merge a host call for an embodiment of the application;

[0054] Figure 9c A flowchart of creating a conference call for an embodiment of the conference call;

[0055] Figure 10 A block diagram of an electronic device for an embodiment of the application;

[0056] Figure 11 A block diagram of a System on Chip (SOC) for an embodiment of the application. DETAILED DESCRIPTION

[0057] The technical solutions in the embodiments of the application will be described clearly and completely below with reference to the accompanying drawings in the embodiments of the application.

[0058] With reference to the accompanying drawings Figure 2a and Figure 2b which shows a schematic diagram of a conference call scenario provided by an embodiment of the present application. In the embodiment of the present application, a user A is a conference chair user, and the user A will have a conference call with a user B and a user C. The conference call refers to a case where a user dials or receives a call, and after the call is connected, the user dials a second call, and after the second call is connected, a conference call is created by merging the two calls. At this time, the three participants of the conference call can hear each other.

[0059] In this scenario, as shown in Figure 2a , the call interface shown in Figure 2a is a call interface of an electronic device A corresponding to the user A. Taking a case where the electronic device A of the user A has established a call with an electronic device B of the user B as an example, as shown in (a) of Figure 2a , the electronic device A can display a call interface 201 between the electronic device A and the electronic device B. The call shown in (a) of Figure 2a may be a call established by the user A dialing a call to the user B and the user B answering the call. Alternatively, Figure 2a , the call shown in (a) of may be a call established by the user A answering a call from the user B. The call interface 201 can include a phone number 202 of the electronic device B (i.e., 15XXXXXXXX6), and can also include an add call control 203. The add call control 203 can be used to trigger adding another call to the current call.

[0060] In response to a click operation of the user on the add call control 203, the electronic device A can request to establish a call with a call device other than the electronic device B. For example, the electronic device A can dial a number (i.e., 07XXXXXXXXX1) of the user C, and establish a call with an electronic device C (a device of the user C). After the electronic device A establishes the call with the electronic device C, the call between the electronic device A and the electronic device B is maintained (or is on hold). The electronic device A can display a call interface 204 as shown in (b) of Figure 2a . In the call interface 204, the call between the electronic device A and the electronic device B is maintained (i.e., is in a hold state), and the call between the electronic device A and the electronic device C is in a call state (i.e., is in an active state). The call interface 204 can also include a call merge control 205. After the user A clicks the call merge control 205, the electronic device A can establish a conference call among the electronic device A, the electronic device B, and the electronic device C, and the electronic device A can display a conference call interface 206 as shown in (c) of Figure 2aThe call interface 206 shown in (c) can display the information of the participants (excluding the conference chair) of the current conference call, i.e., the call interface 206 can include the phone numbers of the electronic device B and the electronic device C.

[0061] In this scenario, the electronic device A establishes a call with the electronic device B and the electronic device C, and after the user A clicks the call merge control 205, the conference server creates an IMS conference center X for the electronic device A and pulls the electronic device B and the electronic device C into the conference, thus completing the creation of the conference call. At this time, the call role of the electronic device A is the conference chair of the conference call, and the call roles of the electronic device B and the electronic device C are the conference members of the conference call. Figure 2b

[0062] To clearly describe the embodiments of the present application, the process of implementing the conference call on the electronic device side is first described below by taking the electronic device A as an example.

[0063] The electronic device A can first establish a first call with the electronic device B, create a phone session 1 (callsession1), an IMS call 1 (framework layer) (imscall1 / imsphoneconnection1(framework)), a call connection 1 (telephony connection 1 (teleservice)), and a call instance 1 (telecom call1). After the establishment of the first call, the electronic device A can establish a second call with the electronic device C, create a phone session 2 (callsession2), an IMS call 2 (framework layer) (imscall2 / imsphoneconnection2(framework)), a call connection 2 (telephony connection 2 (teleservice)), and a call instance 2 (telecom call2).

[0064] ​After the user clicks the call merge control in the call interface displayed by the electronic device A, the electronic device A can send a call merge request to the conference server, and the call merge request is used to request the conference server to merge the first call and the second call into a conference call. The conference server can create an IMS conference center X for the electronic device A in response to the call merge request, and pull the electronic device B and the electronic device C into the conference to complete the creation of the conference call. At this time, the modem (Modem) at the bottom layer of the electronic device A can report the conference attribute information of the conference call to the upper layer. The conference attribute information can include but is not limited to information describing the conference identifier, the call state, the type and format of the telephone number, and information indicating the entry into the conference call state and the call initiated by the electronic device, etc. For example, the information such as dc=id=3, DIALING, toa=129, conf, mo, etc. can be reported. The application framework layer at the upper layer of the electronic device A receives the conference attribute information, and can establish a conference call session (callsession3) based on the conference attribute information.

[0065] After the conference server merges the first call and the second call into the conference call, the conference server can return a call merge result to the electronic device A. The bottom layer of the electronic device A can determine whether the call merge result indicates that the call merge is successful, and if so, the call merge result can be reported to the upper layer. At this time, the bottom layer can also receive the conference information (including the conference state, etc.) of the conference call from the conference server, and report the conference information to the upper layer.

[0066] After the application framework layer at the upper layer of the electronic device A determines that the bottom layer reports that the call merge is successful, the imscall2 / imsphoneconnection2 can be bound with the callsession3, and the conference information of the conference call can be copied to the imscall2 to update the imscall2 / imsphoneconnection2. The application framework layer can also copy the telephonyconnection2 to a call connection 3 (telephonyconnection3) to create an IMS conference (imsconference). The application layer at the upper layer of the electronic device A can create a call instance 3 (telecom call3) of the conference call under the IMS, thereby completing the creation of the conference call after the merging.

[0067] The electronic device A can further send a conference subscription request to the conference server, the conference subscription request being used to acquire the participant information of the merged teleconference from the conference server, the participant information including the information of the electronic device B and the information of the electronic device C. The conference server can send a conference subscription result to the electronic device A in response to the conference subscription request. The electronic device A can receive the conference subscription result sent by the conference server. If the conference subscription result indicates that the conference subscription is successful, the conference server can further send subscription information to the electronic device A, the subscription information including the participant information of the teleconference. The electronic device A can further receive the subscription information from the conference server. The electronic device A can create sub-calls of the teleconference according to the participant information sent by the conference server, and create a telecom call 4 and a telecom call 5. The call interface of the electronic device A can display the teleconference and the participant information.

[0068] The following illustrates the problems in the above teleconference scenario.

[0069] In some embodiments, the reference is made in combination with the description of the accompanying drawings Figure 3 After the teleconference for the calls of the electronic device A, the electronic device B and the electronic device C is created, for the electronic device (e.g., the electronic device B) as a conference member, the number of the user D can be dialed again to establish a call with the electronic device D. However, due to the framework limitation in the electronic device, after the call between the electronic device B and the electronic device D is established, the call merge control is not included in the call interface displayed by the electronic device B, and thus the electronic device B cannot add a new member into the conference.

[0070] In some embodiments, the framework limitation in the electronic device can be removed, and thus for the electronic device (e.g., the electronic device B) as a conference member, after the call with the electronic device D is established, the call merge control is included in the call interface displayed by the electronic device B. However, after the call merge control is clicked by the user B, the call merge is still unsuccessful, and the interface cannot normally display the teleconference and the conference member information.

[0071] To illustrate the reason, the following describes the Figure 4a and Figure 4b First, the logic of the current IMS framework is briefly introduced. As shown in FIG. 1, the IMS framework includes a P-CSCF (Proxy-Call Session Control Function), an S-CSCF (Serving-Call Session Control Function), an I-CSCF (Interrogating-Call Session Control Function), an HSS (Home Subscriber Server), a P-AS (Proxy-Application Server), an S-AS (Serving-Application Server), a P-CSCF (Proxy-Call Session Control Function), a P-AS (Proxy-Application Server), an S-AS (Serving-Application Server), and a P-CSCF (Proxy-Call Session Control Function). Figure 4aAs shown, in step S401, after the electronic device establishes two calls—a background call (bgcall, in hold state) and a foreground call (fgcall, in active state)—the user can click the call merging control to trigger a call merging operation. Correspondingly, the electronic device can obtain the user's call merging operation. In step S402, after obtaining the call merging operation, the application framework layer of the electronic device can determine whether the call attributes of the foreground and background calls are not multiparty calls, or whether the call attribute of the foreground call is a multiparty call. In step S403, if the determination result is yes, it can be determined that the foreground call is a merged host call. In step S404, if the determination result is no, it can be determined that the background call is a merged host call.

[0072] like Figure 4b As shown, in step S405, the underlying layer of the electronic device can confirm and return that the call merging is successful. In step S406, after the underlying layer of the electronic device returns that the call merging is successful, the application framework layer of the electronic device can determine whether the foreground call is a merged host call. In step S407, if the determination result is yes, the established conference call session can be saved. In step S408, if the determination result is no, the established conference call session is not saved. In step S409, the application framework layer of the electronic device can determine whether the call attribute of the merged host call is a conference call (i.e., the call role of the electronic device in the merged host call is conference chair or conference member). In step S410, if the determination result is yes, the conference call session is not bound to the foreground call. In step S411, if the determination result is no, the conference call session is bound to the foreground call, and a conference call for the conference call is created.

[0073] The following explains why user B of electronic device B still cannot merge calls after clicking the call merging control.

[0074] Although after user B clicks the call merge control in the call interface displayed by electronic device B, the conference server creates IMS conference center Y for electronic device B, the Modem underlying electronic device B reports the conference attribute information of the teleconference to the upper layer, and the application framework layer of the upper layer of electronic device B establishes the teleconference session callsession3. According to the normal process, after the underlying layer reports the successful call merge to the upper layer, the application framework layer of the upper layer of electronic device B needs to bind callsession3 and the foreground call imscall2 on the IMS framework side, and copy the conference information (including the conference state) of the teleconference to imscall2. The application layer of the upper layer of electronic device B needs to create the telecom call3 of the teleconference. After the conference server returns the subscription information, electronic device B can also create the sub-calls of the teleconference, telecom call4 and telecom call5, according to the reported participant information.

[0075] However, as a conference member, the call attribute of the call between electronic device B and electronic device A (which is bgcall at this time) reported to electronic device B by the conference server is a teleconference, that is, electronic device B is in a teleconference. The call attribute of the call between electronic device B and electronic device D (which is fgcall at this time) reported to electronic device B by the conference server is a normal call. According to the IMS framework logic shown in Figure 4a and Figure 4b electronic device B can determine that bgcall is a merge host call. And after the underlying layer returns that the call merge is successful, since the call attribute of the merge host call bgcall is a teleconference (at this time, the call role of electronic device B in the merge host call bgcall is a conference member), the established teleconference session will not be saved, and the teleconference session will not be bound with the foreground call fgcall. As shown in Figure 4c According to the above IMS framework logic, it will cause that the teleconference session of the teleconference is not saved, and finally its information is not copied to fgcall to be bound with the foreground call fgcall. But actually, the call attribute of a teleconference cannot represent that the call role of the current device in the teleconference is a conference chairman. For electronic device B, there is no existing teleconference at this time, and if the upper layer call cannot get the teleconference information from the underlying layer, the upper layer cannot perceive the state and members of the teleconference, so the call is not successfully merged.

[0076] In some embodiments, in Figures 4a to 4cIn the illustrated embodiment, before clicking the call merge control, user B can click the exchange control in the call interface displayed by electronic device B. At this time, electronic device B can determine that the call with electronic device A is fgcall, and the call with electronic device D is bgcall. At this time, user B clicks the call merge control in the interface again, and the application framework layer of electronic device B can determine that fgcall is the merge host call. Moreover, when the underlying layer returns that the call merging is successful, since the merge host call is fgcall, the application framework layer of electronic device B saves the established conference call session and enters the judgment flow of whether the call attribute of the merge host call fgcall is a conference call.

[0077] In some embodiments, for a high pass (Qualcomm, QCOM) chip platform, since QCOM has set the state of the merge host call fgcall to be invalid, the call attribute of the merge host call fgcall cannot be read, and at this time, the subsequent system binding process, i.e., call merging success, is performed. For a MediaTek (MTK) chip platform, since the call attribute of the merge host call fgcall can still be read to be a conference call, the binding process is not performed, and the call merging is not successful.

[0078] In some embodiments, the Vendor / IMS module of the MTK chip manufacturer can also be modified, and when the call role of electronic device B in fgcall or bgcall is a conference member, the conference attribute of fgcall or bgcall is not reported to be a conference call. However, this method is only applicable to the MTK chip platform and is not applicable to the QCOM chip platform.

[0079] Therefore, a new conference call implementation method is needed, so that the electronic device as a conference member can also merge the call. To this end, the embodiments of the present application provide a conference call implementation method, device and medium, so that the electronic device as a conference member of the conference call can also merge the call, pull people into the conference, and realize the cascading function of the conference call.

[0080] According to an embodiment of the present application, after the first electronic device obtains the call merging operation of the user, in the case where the call role of the first electronic device in the first call and the second call is neither a conference chairman, the created conference call session and the second call are bound, and the second call is updated according to the conference information of the conference call, so as to realize the creation of the conference call of the conference call. This conference call implementation method enables the electronic device as a conference member of the conference call to also merge the call, realizes the cascading function of the conference call, and improves the user experience.

[0081] The form of the electronic device is not limited in the embodiments of the present application. The electronic device can be a mobile phone, a tablet computer, a notebook computer, a personal computer (PC), a wearable device, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) \ virtual reality (VR) device, a vehicle-mounted device (for example, an in-vehicle infotainment (IVI), a vehicle-mounted navigation device), and the like, which can perform an IMS conference call. The system installed in the electronic device can be an Android, an IOS, a HarmonyOS, and the like, and is not limited herein.

[0082] The method of the embodiments of the present application will be described below in combination with the specific structure of the electronic device.

[0083] Figure 5a A structural schematic diagram of an electronic device 500 provided by an embodiment of the present application is shown. The electronic device 500 can include a processor 510, an external memory interface 520, an internal memory 521, a universal serial bus (USB) interface 530, a charging management module 540, a power management module 541, a battery 542, an antenna 1, an antenna 2, a mobile communication module 550, a wireless communication module 560, an audio module 570, a loudspeaker 570A, a receiver 570B, a microphone 570C, a headset interface 570D, a sensor module 580, a key 590, a motor 591, an indicator 592, a camera 593, a display screen 594, and a subscriber identification module (SIM) card interface 595, and the like. The sensor module 580 can include a pressure sensor 580A, a gyroscope sensor 580B, a barometric pressure sensor 580C, a magnetic sensor 580D, an acceleration sensor 580E, a distance sensor 580F, a proximity light sensor 580G, a fingerprint sensor 580H, a temperature sensor 580J, a touch sensor 580K, an ambient light sensor 580L, a bone conduction sensor 580M, and the like.

[0084] The processor 510 can include one or more processing units, for example: the processor 510 can include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processor (NPU), etc. Among them, different processing units can be independent devices, or can be integrated in one or more processors. For example, the processor 510 can be used to execute the steps of the implementation method of the conference call in the embodiments of the present application.

[0085] The processor 510 can generate operation control signals according to instruction operation codes and timing signals to complete the control of fetching and executing instructions.

[0086] The processor 510 can also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 510 is a cache memory. The memory can save instructions or data that the processor 510 has just used or repeatedly uses. If the processor 510 needs to use the instructions or data again, it can be directly called from the memory. This avoids repeated access and reduces the waiting time of the processor 510, thereby improving the efficiency of the system.

[0087] In some embodiments, after obtaining the talk merge operation of the user, in the case where the processor 510 determines that the talk roles of the electronic device 500 in the background talk and the foreground talk are neither the conference chair, the processor 510 binds the created conference call session and the foreground talk, and updates the foreground talk according to the conference information of the conference call, to realize the creation of the conference call of the conference call. This conference call implementation method enables conference members of the conference call to also merge the talk, realizes the cascading function of the conference call, and improves the user experience.

[0088] In some embodiments, the processor 510 can include one or more interfaces. The interfaces can include Inter-Integrated Circuit (I2C) interface, Inter-Integrated Circuit Sound (I2S) interface, Pulse Code Modulation (PCM) interface, Universal Asynchronous Receiver / Transmitter (UART) interface, Mobile Industry Processor Interface (MIPI), General-Purpose Input / Output (GPIO) interface, Subscriber Identity Module (SIM) interface.

[0089] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 510 can contain multiple sets of I2C bus. The processor 510 can be coupled to the touch sensor 580K, the charger, the flash, the camera 593, etc. through different I2C bus interfaces respectively. For example, the processor 510 can be coupled to the touch sensor 580K through the I2C interface, so that the processor 510 and the touch sensor 580K communicate through the I2C bus interface, realizing the touch function of the electronic device 500.

[0090] The I2S interface can be used for audio communication. In some embodiments, the processor 510 can contain multiple sets of I2S bus. The processor 510 can be coupled to the audio module 570 through the I2S bus, realizing the communication between the processor 510 and the audio module 570. In some embodiments, the audio module 570 can deliver audio signals to the wireless communication module 560 through the I2S interface, realizing the function of answering the phone through the Bluetooth headset.

[0091] The PCM interface can also be used for audio communication, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 570 and the wireless communication module 560 can be coupled through the PCM bus interface. In some embodiments, the audio module 570 can also deliver audio signals to the wireless communication module 560 through the PCM interface, realizing the function of answering the phone through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0092] The MIPI interface can be used to connect the processor 510 and the display screen 594, the camera 593 and other peripheral devices. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), and the like. In some embodiments, the processor 510 and the camera 593 communicate through the CSI interface to implement the photographing function of the electronic device 500. The processor 510 and the display screen 594 communicate through the DSI interface to implement the display function of the electronic device 500.

[0093] It can be understood that the interface connection relationship between the modules shown in the embodiments of the present application is only illustrative and does not constitute a structural limitation on the electronic device 500. In some other embodiments of the present application, the electronic device 500 can also use different interface connection modes or a combination of multiple interface connection modes in the above embodiments.

[0094] The wireless communication function of the electronic device 500 can be implemented through the antenna 1, the antenna 2, the mobile communication module 550, the wireless communication module 560, the modem processor, the baseband processor, and the like.

[0095] The antenna 1 and the antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the electronic device 500 can be used to cover a single or multiple communication frequency bands. Different antennas can also be multiplexed to improve the utilization rate of the antennas. For example, the antenna 1 can be multiplexed as a diversity antenna of a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0096] The mobile communication module 550 can provide a solution including 2G / 3G / 4G / 5G wireless communication applied to the electronic device 500. The mobile communication module 550 can include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), and the like. The mobile communication module 550 can receive electromagnetic waves from the antenna 1 and perform filtering, amplification, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 550 can also amplify the signals modulated by the modem processor and convert them into electromagnetic waves radiated through the antenna 1. In some embodiments, at least part of the functional modules of the mobile communication module 550 can be arranged in the processor 510. In some embodiments, at least part of the functional modules of the mobile communication module 550 and at least part of the modules of the processor 510 can be arranged in the same device.

[0097] The modem processor can include a modulator and a demodulator. The modulator is configured to modulate a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is configured to demodulate a received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low-frequency baseband signal processed by the baseband processor is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 570A, a microphone 570B, etc.), or displays an image or a video through the display screen 594. In some embodiments, the modem processor can be a separate device. In other embodiments, the modem processor can be independent of the processor 510, and can be disposed in the same device as the mobile communication module 550 or other functional modules.

[0098] The wireless communication module 560 can provide a wireless communication solution including a wireless local area network (WLAN) (such as a wireless fidelity (Wi-Fi) network), Bluetooth (BT), a global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared technology (IR), and the like, which can be applied to the electronic device 500. The wireless communication module 560 can be one or more devices that integrate at least one communication processing module. The wireless communication module 560 receives an electromagnetic wave via an antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signal, and transmits the processed signal to the processor 510. The wireless communication module 560 can also receive a signal to be transmitted from the processor 510, perform frequency modulation and amplification on the signal, and radiate the signal as an electromagnetic wave via the antenna 2.

[0099] In some embodiments, antenna 1 and mobile communication module 550 of electronic device 500 are coupled, and antenna 2 and wireless communication module 560 are coupled, so that electronic device 500 can communicate with a network and other devices through wireless communication technology. The wireless communication technology can include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. The GNSS can include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), Beidou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0100] Electronic device 500 implements a display function through a GPU, display screen 594, and an application processor, etc. The GPU is a microprocessor for image processing, connected to display screen 594 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 510 can include one or more GPUs that execute program instructions to generate or change display information.

[0101] The display screen 594 is configured to display images, videos, and the like. The display screen 594 includes a display panel. The display panel can be a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), an Active-Matrix Organic Light Emitting Diode (AMOLED), a Flex Light-Emitting Diode (FLED), a Miniled, a Micro Led, a Micro-oLed, a Quantum Dot Light Emitting Diodes (QLED), or the like. In some embodiments, the electronic device 500 can include one or N display screens 594, where N is a positive integer greater than 1.

[0102] In some embodiments, the display screen 594 can be configured to display an interface of the electronic device. For example, the display screen 594 can be configured to display an interface of a teleconference.

[0103] The electronic device 500 can implement a photographing function through an ISP, the camera 593, a video codec, a GPU, the display screen 594, and an application processor, and the like. In some embodiments, the electronic device 500 can include one or N cameras 593, where N is a positive integer greater than 1.

[0104] The internal memory 521 can be configured to store computer-executable program codes including instructions. The internal memory 521 can include a program storage area and a data storage area. The program storage area can store an operating system, at least one application program required by a function (such as a sound playing function, an image playing function, and the like), and the like. The data storage area can store data (such as audio data, a phone book, and the like) created during use of the electronic device 500, and the like. In addition, the internal memory 521 can include a high-speed random access memory, and can further include a non-volatile memory such as at least one of a magnetic disk storage device, a flash memory device, a Universal Flash Storage (UFS), and the like. The processor 510 executes various function applications and data processing of the electronic device 500 by running instructions stored in the internal memory 521 and / or instructions stored in a memory disposed in the processor.

[0105] In some embodiments, the internal memory 521 can store instructions of a conference call implementation method. The processor 510 runs the conference call implementation method instructions, so that after obtaining the talk merge operation of the user, the processor 510 can bind the created conference call session and the foreground call in the case where the processor 510 determines that the talk roles of the electronic device 500 in the background call and the foreground call are neither the conference chair, and update the foreground call according to the conference information of the conference call, to realize the creation of the conference call of the conference call.

[0106] The electronic device 500 can realize audio functions through the audio module 570, the speaker 570A, the receiver 570B, the microphone 570C, the earphone interface 570D, and the application processor, etc. For example, music playing, recording, etc.

[0107] The audio module 570 is used to convert digital audio information into analog audio signals, and is also used to convert analog audio input into digital audio signals. The audio module 570 can also be used to encode and decode audio signals. In some embodiments, the audio module 570 can be arranged in the processor 510, or part of the functions of the audio module 570 can be arranged in the processor 510.

[0108] The speaker 570A, also known as a "loudspeaker", is used to convert audio electrical signals into sound signals. The electronic device 500 can listen to music or listen to a hands-free call through the speaker 570A.

[0109] The receiver 570B, also known as a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 500 answers a call or a voice message, the receiver 570B can be held close to the ear to listen to the voice.

[0110] The microphone 570C, also known as a "microphone", "sound collector", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak into the microphone 570C through the mouth to input the sound signal into the microphone 570C. The electronic device 500 can be provided with at least one microphone 570C. In other embodiments, the electronic device 500 can be provided with two microphones 570C, in addition to collecting sound signals, it can also realize the noise reduction function. In other embodiments, the electronic device 500 can also be provided with three, four or more microphones 570C, to realize the collection of sound signals, noise reduction, and also to identify the sound source, to realize the directional recording function, etc.

[0111] The pressure sensor 580A is configured to sense a pressure signal and convert the pressure signal to an electrical signal. In some embodiments, the pressure sensor 580A can be disposed on the display screen 594. The pressure sensor 580A can be of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, etc. The capacitive pressure sensor can include at least two parallel plates of conductive material. When a force is applied to the pressure sensor 580A, the capacitance between the electrodes changes. The electronic device 500 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 594, the electronic device 500 detects the intensity of the touch operation based on the pressure sensor 580A. The electronic device 500 can also calculate the position of the touch based on the detection signal of the pressure sensor 580A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than a first pressure threshold is applied to the short message application icon, the instruction to view short messages is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the short message application icon, the instruction to create a new short message is executed.

[0112] The touch sensor 580K, also referred to as a "touch device". The touch sensor 580K can be disposed on the display screen 594, and the touch sensor 580K and the display screen 594 together form a touch screen, also referred to as a "touch panel". The touch sensor 580K is configured to detect a touch operation applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 594. In other embodiments, the touch sensor 580K can also be disposed on the surface of the electronic device 500, which is different from the position where the display screen 594 is located.

[0113] The keys 590 include a power key, a volume key, etc. The keys 590 can be mechanical keys. They can also be touch keys. The electronic device 500 can receive key input and generate key signal input related to user settings and function control of the electronic device 500.

[0114] The SIM card interface 595 is configured to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 595 to realize contact and separation with the electronic device 500. The electronic device 500 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 595 can support a Nano SIM card, a Micro SIM card, a SIM card, or the like. Multiple cards can be inserted into the same SIM card interface 595 at the same time. The types of the multiple cards can be the same or different. The SIM card interface 595 can be compatible with different types of SIM cards. The SIM card interface 595 can also be compatible with external storage cards. The electronic device 500 interacts with a network through the SIM card to realize functions such as call and data communication. In some embodiments, the electronic device 500 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 500 and cannot be separated from the electronic device 500.

[0115] The software system of the electronic device 500 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Embodiments of this application exemplarily illustrate the software structure of the electronic device 500 by taking the layered architecture as an example. In this application, the type of the operating system of the electronic device is not limited. For example, it can be an Android system, a Linux system, a Windows system, an iOS system, a Harmony Operating System (Harmony OS), or the like.

[0116] Figure 5b A software structure block diagram of the electronic device 500 provided by an embodiment of this application is shown. The layered architecture divides the software into several layers, each of which has a clear role and division of labor. Layers communicate with each other through software interfaces. As shown in the figure, Figure 5b The electronic device 500 can include an application layer, an application framework layer, a hardware abstraction layer (Hardware Abstraction Layer, HAL), and a Vendor / IMS module, and a device connection layer.

[0117] The application layer can include a dialer, telephony, telecom, and incall user interface (InCall UI). The dialer provides users with services such as dialing, answering, and hanging up calls. Telephony manages phone calls, including caller ID, answering, and hanging up. Telecom provides API support for phone calls, working with hardware devices to offer voice, SMS, data connectivity, SIM card management, and phonebook functionality. The InCall UI provides users with an interface for incoming and outgoing calls, or during a call, such as a dialer, incoming call screen, and call screen. The contacts application manages (adds, deletes, modifies, or synchronizes) contact information. Telephony, Telecom, and InCall UI work together to provide call functionality. For example, when Telephony receives an incoming call, it first notifies Telecom, which then notifies InCall UI to display the incoming call screen.

[0118] The application framework layer provides the application layer with an application programming interface (API) and a programming framework. The application framework layer includes some predefined functions.

[0119] like Figure 5b As shown, the application framework layer can include the Telephony framework, the Telecom framework, and the Network (NET) / IMS framework. The Telephony framework provides APIs for accessing telephone functionality. These APIs can be used to obtain network information, monitor phone status changes, send SMS messages, etc. The Telecom framework provides a unified interface for managing telephone calls, including making calls, answering calls, and call control (such as holding, hanging up, and speakerphone switching). The Telecom framework acts as an intermediary between the Telephony framework and other call services. When a call comes in or goes out, the Telephony framework notifies the Telecom framework, which then handles the call based on the user-configured default dialer application and call settings. The NET / IMS framework mainly includes the IMS Manager, which provides IMS service APIs, and the calls (ImsCall) created by the ImsManager that handle IMS voice and video call connections.

[0120] The HAL provides a unified and simple hardware operation interface for the upper layer application, and aims to abstract the hardware and reduce the coupling between the electronic device operating system and the hardware. The HAL and the Telephony framework can perform reliable data transmission, command sending and response analysis through a Radio Interface Layer (RIL). The RIL is a bridge for communication between the Modem and the wireless access point on the electronic device.

[0121] The Vendor / IMS module mainly includes implementation classes of IMS services, and is responsible for dealing with the Modem and the Media, and providing IMS related services.

[0122] The device connection layer includes the Modem and the Media. The Modem can be used to implement signal conversion between different devices, for example, can convert the digital signal transmitted in the device into an analog signal transmitted by the telephone system, and convert the analog signal into a digital signal. The Media can be used to process media files such as audio and video in the electronic device.

[0123] In addition, the device connection layer can also include a bottom layer module and a basic module (not shown in the figure) for implementing various basic capabilities of the electronic device 500. The bottom layer module can include various hardware and its corresponding driver programs. For example, the bottom layer module can include a microphone and a microphone driver, a camera and a camera driver, a sensor and a sensor driver, and hardware and its driver for implementing a call function.

[0124] It can be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the electronic device 500. In other embodiments of the present application, the electronic device 500 can include more or fewer components than illustrated, or combine certain components, or split certain components, or different component arrangements. The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0125] It should be noted that the specific structures of the first electronic device, the second electronic device and the third electronic device mentioned in the embodiments of the present application can be the same or different, and the embodiments of the present application do not make specific limitations thereon.

[0126] The following will introduce in detail the specific flow of the implementation method of the conference call provided by the embodiments of the present application.

[0127] The implementation method of the conference call provided by the embodiments of the present application can be applied to an electronic device with a hardware structure as shown in Figure 5a and a software structure as shown in Figure 5bThe electronic device shown in the software structure. Or more or less than the components shown, or combine certain components, or split certain components, or different component arrangements, and the like hardware structure and software structure of the electronic device.

[0128] The following example of a mobile phone, the implementation method of the conference call provided by an embodiment of the present application is described in detail. Reference Figure 6 As shown, Figure 6 The flow chart of the implementation method of the conference call provided by an embodiment of the present application is shown, which can be executed by the mobile phone B (as an example of the first electronic device), which can include steps S601-S606.

[0129] S601: mobile phone B acquires the user's call merge operation, which is used to merge the background call (as an example of the first call) and the foreground call (as an example of the second call) into a conference call.

[0130] Wherein, the background call can be a suspended call between the mobile phone B and the mobile phone A, mobile phone C (as an example of at least one second electronic device), that is, the call between the mobile phone B and the mobile phone A, mobile phone C is in the call hold state (i.e. in the hold state). The foreground call can be an ongoing call between the mobile phone B and the mobile phone D (as an example of the third electronic device), that is, the call between the mobile phone B and the mobile phone D is in the call state (i.e. in the active state).

[0131] In the embodiment of the present application, the background call can be a normal call or a conference call. In the case of a conference call, the conference call can be established by other mobile phones (such as mobile phone A), that is, the mobile phone B is a conference member of the conference call. The conference call can also be established by the mobile phone B, that is, the mobile phone B is the chairman of the conference call. In the case of a normal call, it can be a call between other mobile phones (such as mobile phone A) and mobile phone B, or a call between mobile phone B and other mobile phones (such as mobile phone A), and the mobile phone B is a call member of the normal call.

[0132] In the embodiment of the present application, the foreground call can be a normal call or a conference call. The specific content of the foreground call is similar to that of the background call, and the related content of the background call can be referred to, which will not be described here in the embodiment of the present application.

[0133] It should be noted that the background call is a conference call in which the other mobile phone (for example, mobile phone A) is the conference chairman, and the foreground call is a normal call in the embodiments of the present application, but the present application is not limited thereto. In some embodiments, the background call can be a normal call, the foreground call can also be a conference call, or the background call and the foreground call can both be a conference call or a normal call, and the embodiments of the present application do not make a specific limitation thereto.

[0134] In the embodiments of the present application, mobile phone B can first establish a conference call with mobile phone A and mobile phone C. The conference call can be a conference call established by mobile phone A among mobile phone A, mobile phone B and mobile phone C, or a conference call established by mobile phone B among mobile phone A, mobile phone B and mobile phone C, and the embodiments of the present application do not make a specific limitation thereto. Thereafter, mobile phone B can establish a call with mobile phone D by dialing the number of user D. After mobile phone B establishes a call with mobile phone D, the call between mobile phone B and mobile phone D is in an active state, which is the foreground call; and the call between mobile phone B and mobile phone A and mobile phone C is in a hold state, which is the background call.

[0135] In the embodiments of the present application, after mobile phone B establishes a call with mobile phone D, mobile phone B can display a call interface for the call with mobile phone D. In the call interface, the call between mobile phone B and mobile phone A and mobile phone C is maintained, and the call between mobile phone B and mobile phone D is in a call state. The call interface can also include a call merging control. Mobile phone B can detect a click operation of a user on the call merging control. When it is detected that the user performs the click operation on the call merging control, it is determined that a call merging operation of the user is acquired. The call merging operation can be used to merge the background call and the foreground call into a conference call. The click operation on the call merging control can include, but is not limited to, a pressing action of a finger of the user on the area where the call merging control is located, and the present application does not make a specific limitation thereto.

[0136] In some embodiments, the user can also trigger the call merging through other operation modes such as long pressing the call merging control and double-clicking the call merging control. The specific implementation mode is similar to the implementation mode of clicking the call merging control, and the related content of the implementation mode of clicking the call merging control can be referred to, and the embodiments of the present application do not make a specific limitation thereto.

[0137] It should be noted that the operation mode for triggering the call merging is only an example, and in actual application, the user can also trigger the call merging through other operation modes such as dragging one call to the area where the other call is located, and the present application does not make a specific limitation to the specific implementation mode of the call merging operation.

[0138] S602: Mobile phone B establishes a conference call session based on the call merging operation in response to the call merging operation.

[0139] In this embodiment, after mobile phone B receives the user's call merging operation, it can establish a conference call session corresponding to the call conference obtained by merging the background call and the foreground call based on the call merging operation. Specifically, mobile phone B can respond to the call merging operation, obtain the conference attribute information of the conference call, and establish a conference call session based on the obtained conference attribute information.

[0140] In practical applications, the modem at the bottom layer of mobile phone B can send conference attribute information for the teleconference to the IMS application. This attribute information may include, but is not limited to, information describing the conference identifier, call status, type and format of the phone number, and information indicating that the call has entered a conference call state and that the call was initiated by an electronic device. For example, it can send information such as dc=id=3, DIALING, toa=129, conf, and mo. After receiving the conference attribute information, the IMS application can send it to the application framework layer above mobile phone B. Upon receiving the conference attribute information, the application framework layer can establish a corresponding teleconference session based on the conference attribute information. The specific establishment method will not be elaborated further in this embodiment.

[0141] It is understandable that mobile phone B can establish a teleconference session based on conference attribute information to handle various events related to the creation of the conference call.

[0142] S603: Mobile phone B requests the conference server to merge the background call and the foreground call into a conference call.

[0143] In this embodiment, mobile phone B first establishes a conference call with mobile phones A and C, then establishes a call with mobile phone D. After obtaining the user's call merging operation, it can request the conference server to merge the background call and the foreground call into a conference call. (Refer to the appendix of the specification.) Figure 7 The conference server can create an IMS conference center Y for mobile phone B based on the request from mobile phone B, and connect IMS conference center X and mobile phone D to the conference, completing the creation of the merged teleconference. In this way, users of mobile phones A, B, C, and D can all hear each other. Specifically, IMS conference center X is the IMS conference center created by the conference server for mobile phone A when establishing a teleconference between mobile phones A, B, and C based on a request from mobile phone A.

[0144] S604: Mobile phone B receives conference information from the conference server for a teleconference.

[0145] In the embodiment of the present application, the conference server can also return the call merging result to the mobile phone B, and the call merging result is used to indicate the result of merging the background call and the foreground call into the conference call. When the conference call is successfully created, the conference server can return the call merging success result to the mobile phone B, otherwise, the conference server can return the call merging failure result to the mobile phone B. When the conference call is successfully created, the conference server can also send the conference information of the created conference call to the mobile phone B, and the conference information can include but is not limited to the conference state and other information, which are not limited in the embodiment of the present application.

[0146] Correspondingly, the mobile phone B can receive the conference information of the conference call sent by the conference server.

[0147] In actual application, the modem of the mobile phone B can receive the call merging result returned by the conference server and the conference information of the conference call. The modem can also send the call merging success result and the received conference information to the IMS application of the mobile phone B. After receiving the call merging success result and the conference information, the IMS application can send the call merging success result and the conference information to the application framework layer of the upper layer of the mobile phone B.

[0148] S605: The mobile phone B determines that the call role of the mobile phone B in the background call and the foreground call is not the conference chairman.

[0149] In the embodiment of the present application, after the mobile phone B obtains the call merging operation of the user, the mobile phone B can also obtain the call attribute information of the background call and the foreground call and the call role information of the mobile phone B in the background call and the foreground call from the conference server, so as to determine whether the call role of the mobile phone B in the background call and the foreground call is the conference chairman.

[0150] In the embodiment of the present application, after the mobile phone B obtains the call merging operation of the user, the mobile phone B can also obtain the call attribute information of the background call and the foreground call and the call role information of the mobile phone B in the background call and the foreground call from the conference server, so as to determine whether the call role of the mobile phone B in the background call and the foreground call is the conference chairman.

[0151] It can be understood that the mobile phone B can determine whether the mobile phone B is the conference chairman in the background call and the foreground call according to the call attribute and the call role of the device in the call, and the determination method is simple and can ensure the accuracy of the determination result.

[0152] S606: The phone B updates the foreground call based on the conference information, and binds the teleconference session with the foreground call to create the conference call of the teleconference.

[0153] In the embodiments of the present application, the phone B can update the foreground call based on the acquired conference information, and directly bind the established teleconference session with the foreground call, so as to complete the creation of the conference call of the teleconference.

[0154] In actual application, when the application framework layer of the phone B determines that the call merging is successful, and the phone B is neither the chairman in the foreground call nor the chairman in the background call, the phone B can bind the imscall2 / imsphoneconnection2 of the foreground call with the established teleconference session callsession3, and copy the conference information of the teleconference to the imscall2 to update the imscall2 / imsphoneconnection2. The phone B can also copy the telephonyconnection2 of the foreground call to the telephonyconnection3 of the teleconference to create the IMS conference (imsconference). The application layer of the phone B can also create the telecom call3 of the teleconference under the IMS, so as to complete the creation of the conference call of the merged teleconference.

[0155] In some embodiments, when it is determined that the phone B is not the chairman in the background call, the phone B can save the teleconference session, and then execute the subsequent steps. When it is determined that the phone B is the chairman in the background call, the phone B can not save the teleconference session, and then does not execute the subsequent steps.

[0156] It can be understood that when it is determined that the phone B is not the chairman in the background call, the phone B can save the established teleconference session, so as to create the conference call based on the teleconference session.

[0157] In some embodiments, if it is determined that the phone B is the chairman in the background call, or it is determined that the phone B is the chairman in the foreground call, the step S606 is not executed. That is, when it is determined that the phone B is the chairman in the background call, whether the phone B is the chairman in the foreground call or not, the phone B does not need to save the teleconference session, and does not need to create the conference call of the teleconference. When it is determined that the phone B is not the chairman in the background call, and it is determined that the phone B is the chairman in the foreground call, although the phone B saves the teleconference session, the phone B still does not need to create the conference call of the teleconference.

[0158] It can be understood that, in a case that the phone B is determined to be the chairman in the background call or the phone B is determined to be the chairman in the foreground call, the phone B can determine that the conference call of the teleconference does not need to be created, that is, the created teleconference session and the foreground call do not need to be bound, thereby avoiding waste of system resources.

[0159] In summary, after the phone obtains the call merging operation of the user, in a case that the phone is determined not to be the chairman in the background call and the foreground call, the phone binds the created teleconference session and the foreground call, and updates the foreground call according to the conference information of the teleconference, thereby realizing creation of the conference call of the teleconference. This teleconference implementation manner enables the conference member of the teleconference to also merge the call, realizes the cascading function of the teleconference, and improves the use experience of the user. Moreover, the phone realizes the call merging by modifying the application framework layer, and can support the teleconference cascading function of various chip platforms at the same time, thereby being good in applicability.

[0160] The implementation method of the teleconference provided in the embodiments of the present application is further described below through a specific embodiment. Referring to Figure 8 , a flowchart of the implementation method of the teleconference provided in an embodiment of the present application is shown, which is a further description of the embodiment shown in Figure 8 , the method can include steps S801-S808. Figure 6

[0161] S801: The phone B (as an example of a first electronic device) obtains a call merging operation of a user, the call merging operation being used to merge a background call (as an example of a first call) and a foreground call (as an example of a second call) into a teleconference.

[0162] S802: The phone B establishes a teleconference session based on the call merging operation in response to the call merging operation.

[0163] S803: The phone B sends a call merging request to a conference server, the call merging request being used to request the conference server to merge the background call and the foreground call into the teleconference.

[0164] In the embodiments of the present application, after the phone B obtains the call merging operation, the phone B can send the call merging request to the conference server to request the conference server to merge the background call and the foreground call into the teleconference.

[0165] In actual application, the phone B can send the call merging request to a modem through a hardware abstraction layer (HAL) interface of an IMS application, and the modem can receive the call merging request and send the call merging request to the conference server. ​

[0166] S804: The conference server merges the background call and the foreground call into a conference call in response to the call merging request.

[0167] In the embodiments of the present application, after the conference server receives the call merging request sent by the mobile phone B, the conference server can merge the background call and the foreground call in response to the call merging request, and complete the creation of the conference call after merging. Thereafter, the conference server can return the call merging result to the mobile phone B, and the call merging result can be used to indicate whether the call merging is successful.

[0168] S805: If the call merging is successful, the conference server returns the conference information of the conference call to the mobile phone B.

[0169] In the embodiments of the present application, when the call merging is successful (i.e., the conference call is successfully created), the conference server can also send the conference information of the merged conference call to the mobile phone B, and the conference information can include but is not limited to conference status information and the like. When the call merging fails, the conference server will not send the conference information of the conference call to the mobile phone B.

[0170] Correspondingly, the mobile phone B can receive the call merging result returned by the conference server, and determine whether the call merging is successful according to the call merging result. In the case of determining that the call merging is successful, the mobile phone B can also receive the conference information of the conference call returned by the conference server.

[0171] It can be understood that the mobile phone B can send a call merging request to the conference server to request the conference server to merge the background call and the foreground call into a conference call and return the conference information, so as to update the foreground call based on the conference information, so that the updated foreground call can provide services for the conference call, which not only improves the creation efficiency of the conference call, but also saves the system resource consumption.

[0172] S806: The mobile phone B determines the merging host call from the background call and the foreground call.

[0173] In the embodiments of the present application, after the mobile phone B obtains the call merging operation, the mobile phone B can determine the merging host call from the two calls to be merged. Specifically, only in the case that the call role of the mobile phone B in the background call is a conference chairman, the background call is set as the merging host call.

[0174] The process of determining the merging host call will be described below with reference to the accompanying drawings.

[0175] The process of determining the merging host call will be described below with reference to the accompanying drawings. Figure 9aIn step S901, the user can click the call merging control in the call interface to trigger the call merging operation, and accordingly, the mobile phone B can acquire the call merging operation of the user. In step S902, after acquiring the call merging operation, the mobile phone B can acquire the call attribute information of the background call and the call role information of the mobile phone B in the background call from the conference server, so as to determine whether the call role of the mobile phone B in the background call is the conference chairman. In step S903, when it is determined that the call role of the mobile phone B in the background call is the conference chairman, it can be determined that the background call is the merged host call. In step S904, when it is determined that the call role of the mobile phone B in the background call is not the conference chairman, it can be determined that the foreground call is the merged host call.

[0176] In some embodiments, in combination with the description of the accompanying drawings Figure 9b In step S905, the user can click the call merging control in the call interface to trigger the call merging operation, and accordingly, the mobile phone B can acquire the call merging operation of the user. In step S906, after acquiring the call merging operation, the mobile phone B can acquire the call attribute information of the background call and the foreground call and the call role information of the mobile phone B in the background call from the conference server. The mobile phone B can determine whether the background call and the foreground call are not teleconference according to the call attribute information of the background call and the foreground call. When the determination result is no, it is determined whether the call role of the mobile phone B in the background call is not the conference chairman according to the call role information of the mobile phone B in the background call. In step S907, if it is determined that the background call and the foreground call are not teleconference, or it is determined that the call role of the mobile phone B in the background call is not the conference chairman, it can be determined that the foreground call is the merged host call. In step S908, if it is determined that the call role of the mobile phone B in the background call is the conference chairman, it can be determined that the background call is the merged host call.

[0177] It should be noted that the step S802, the steps S803 to S805, and the step S806 in the embodiments of the present application can be executed in sequence or simultaneously, and the execution order of the step S802, the steps S803 to S805, and the step S806 is not limited in the present application.

[0178] Next, the implementation method of the teleconference of the embodiments of the present application is described. Figure 8

[0179] S807: The mobile phone B determines that the call role of the mobile phone B in the merged host call is not the conference chairman.

[0180] ​In the embodiment of the present application, when the phone B determines that the call merging is successful, only in the case that the call role of the phone B in the merging host call is indeed the conference chairman, the merging host call does not need to be bound with the teleconference session. In the case that the call role of the phone B in the merging host call is not the conference chairman, the merging host call needs to be bound with the teleconference session.

[0181] In the embodiment of the present application, when the front call is determined to be the merging host call, the phone B can also acquire the call attribute information of the front call and the call role information of the phone B in the front call from the conference server, so as to determine whether the call role of the phone B in the front call is the conference chairman. When the call role of the phone B in the front call is determined to be the conference chairman, the call role of the phone B in the merging host call is determined to be the conference chairman, and in this case, the subsequent step S808 does not need to be executed; otherwise, the call role of the phone B in the merging host call can be determined to be not the conference chairman, and in this case, the subsequent step S808 can be executed.

[0182] In the embodiment of the present application, when the back call is determined to be the merging host call, the call role of the phone B in the merging host call is necessarily the conference chairman, and in this case, the subsequent step S808 does not need to be executed.

[0183] S808: The phone B updates the front call based on the conference information, and binds the teleconference session with the front call to create the conference call of the teleconference.

[0184] In the embodiment of the present application, the phone B can update the front call based on the acquired conference information, and directly bind the established teleconference session with the front call, so as to complete the creation of the conference call of the teleconference.

[0185] The process of creating the conference call of the teleconference will be described below in combination with the accompanying drawings.

[0186] In one specific embodiment, the process of creating the conference call of the teleconference will be described in combination with the accompanying drawings. Figure 9cIn step S909, the mobile phone B can determine that the call merging is successful according to the call merging result returned by the conference server. In step S910, when the mobile phone B determines that the call merging is successful, the mobile phone B can first determine whether the foreground call is the call of the merging host. In step S911, when the foreground call is the call of the merging host, the mobile phone B can save the conference session. In step S912, when the mobile phone B determines that the foreground call is not the call of the merging host (i.e., the background call is the call of the merging host), the mobile phone B can not save the conference session. In step S913, the mobile phone B can determine whether the mobile phone B is the chairman in the call of the merging host. In step S914, if the determination result is yes, the mobile phone B does not need to perform step S808, i.e., the conference session is not bound to the foreground call, and the conference call of the conference session does not need to be created. In step S915, if the determination result is no, the mobile phone B can perform step S808, i.e., the conference session is bound to the foreground call, and the conference call of the conference session is created.

[0187] For example, when the foreground call is the call of the merging host, if the mobile phone B determines that the mobile phone B is not the chairman in the foreground call, the mobile phone B can perform step S808, and create the conference call of the conference session. If the mobile phone B determines that the mobile phone B is the chairman in the foreground call, the mobile phone B does not need to perform step S808, i.e., the conference call of the conference session does not need to be created. When the background call is the call of the merging host, the mobile phone B is necessarily the chairman in the background call, and thus the mobile phone B does not need to perform step S808.

[0188] In some embodiments, the method can further include the following steps: the mobile phone B sends a conference subscription request to the conference server, the conference subscription request is used to obtain the participant information of the conference session from the conference server, and the participant information includes the information of the conference session between the mobile phone A and the mobile phone C (as an example of the at least one second electronic device) and the information of the mobile phone D (as an example of the third electronic device). After the mobile phone B sends the conference subscription request to the conference server, the conference server returns a conference subscription result to the mobile phone B. The mobile phone B can receive the conference subscription result from the conference server, and the conference subscription result is used to indicate whether the conference subscription is successful.

[0189] If the conference subscription result indicates that the conference subscription is not successful, the conference server does not send the subscription information to the mobile phone B; if the conference subscription result indicates that the conference subscription is successful, the conference server sends the subscription information to the mobile phone B. The mobile phone B can receive the subscription information from the conference server, and the subscription information includes the participant information of the teleconference, i.e., the information of the teleconference with the mobile phone A and the mobile phone C and the information of the mobile phone D. The mobile phone B can further create a first sub-call of the teleconference according to the information of the teleconference with the mobile phone A and the mobile phone C, and create a second sub-call of the teleconference according to the information of the mobile phone D. The method for creating the sub-call is not described herein again.

[0190] In actual application, the mobile phone B can send the conference subscription request to the modem through the hardware abstraction layer (HAL) interface of the IMS application, the modem can receive the conference subscription request and send the conference subscription request to the conference server. The modem of the mobile phone B can receive the conference subscription result returned by the conference server and the subscription information returned after the conference subscription is successful. The modem can further send the subscription information to the IMS application of the mobile phone B. After receiving the subscription information, the IMS application can send the subscription information to the application framework layer of the upper layer of the mobile phone B, thereby creating two sub-calls of the teleconference.

[0191] It can be understood that the mobile phone B can obtain the participant information of the teleconference by sending the conference subscription request to the conference server, and further create two sub-calls of the teleconference according to the participant information, thereby realizing the separate management of different participants.

[0192] In some embodiments, the method can further include the following steps: the mobile phone B displays a conference interface of the teleconference, and the conference interface includes the information of the teleconference with the mobile phone A and the mobile phone C and the information of the mobile phone D.

[0193] In the embodiments of the present application, after creating the two sub-calls, the mobile phone B can display the conference interface of the teleconference in the display screen, and the conference interface can display the participant information of the teleconference. The method for displaying the conference interface is not described herein again.

[0194] It can be understood that the mobile phone B displays the conference interface of the teleconference and displays the participant information in the conference interface, so that the user can know that he is currently in the teleconference, and can perceive the information of the participants of the teleconference, thereby ensuring the user experience of using the teleconference.

[0195] It should be noted that other contents in steps S801 to S808 in the embodiments of the present application can refer to the related contents in the embodiments shown in Figures 6 to 7 The embodiments of the present application are not described herein again.

[0196] The application also provides an electronic device, comprising:

[0197] a memory for storing instructions executed by one or more processors of the electronic device, and

[0198] the processor, when executing the instructions in the memory, can enable the electronic device to perform the implementation method of the conference call as shown in the above embodiments. Figures 6 to 9c

[0199] The application also provides a computer readable storage medium, which has instructions stored thereon, the instructions, when executed by a processor, enable the processor to perform the implementation method of the conference call as shown in the above embodiments. Figures 6 to 9c

[0200] The application also provides a computer program product comprising instructions, which, when executed on an electronic device, enable the processor to perform the implementation method of the conference call as shown in the above embodiments. Figures 6 to 9c

[0201] Reference is now made to Figure 10 , which is a block diagram of an electronic device 1000 according to one embodiment of the application. The electronic device 1000 can include one or more processors 1001 coupled to a controller hub 1003. For at least one embodiment, the controller hub 1003 communicates with the processor(s) 1001 via a multi -branch bus, such as a Front Side Bus (FSB), a point-to-point interface such as Quick Path Interconnect (QPI), or similar connection 1006. The processor(s) 1001 execute instructions to perform a general type of processing operation. In one embodiment, the controller hub 1003 includes, but is not limited to, a Graphics Memory Controller Hub (GMCH) (not shown) which includes a memory and graphics controller and is coupled to the IOH (which can be on a separate chip) (not shown) and the processor(s) 1001.

[0202] The electronic device 1000 can also include a coprocessor 1002 and a memory 1004 coupled to the controller hub 1003. Alternatively, one or both of the memory and the GMCH can be integrated within the processor (as described in this application), the memory 1004 and the coprocessor 1002 are coupled directly to the processor 1001 and the controller hub 1003, which is in a single chip with the IOH.

[0203] ​​​The memory 1004 can be, for example, a Dynamic Random Access Memory (DRAM), a Phase Change Memory (PCM), or a combination of both. The memory 1004, as an example of computer-readable storage media, can include one or more tangible, non-transitory computer-readable media used to store data and / or instructions, for example. For example, the memory 1004 can include any suitable non-volatile memory, such as flash memory, and / or any suitable non-volatile storage device(s), such as one or more Hard-Disk Drive(s) (HDD(s)), one or more Compact Disc (CD) drive(s), and / or one or more Digital Versatile Disc (DVD) drive(s).

[0204] According to some embodiments of the present application, the memory 1004, as computer-readable storage media, stores instructions thereon that, when executed by a computer, cause the system 1000 to perform the implementation method of a conference call according to the above embodiments. For details, refer to the implementation method of a conference call shown in the above embodiments, which will not be repeated here. Figures 6 to 9c

[0205] In one embodiment, the coprocessor 1002 is a special-purpose processor, such as, for example, a high-throughput many-Integrated Core (MIC) processor, a network or communication processor, compression engine, graphics processor, a General Purpose Computing on GPU (GPGPU), embedded processor, etc. The optional nature of the coprocessor 1002 is denoted in Figure 10 FIG. 10 by dashed lines.

[0206] In one embodiment, the electronic device 1000 can further include a Network Interface Controller (NIC) 1006. The network interface 1006 can include a transceiver to provide a radio interface for the electronic device 1000 to communicate to any other suitable device (e.g., a front end module, an antenna, etc.). In various embodiments, the network interface 1006 can be integrated with other components of the electronic device 1000. The network interface 1006 can implement the functionality of the communication unit in the above embodiments.

[0207] ​The electronic device 1000 can further include an input / output (I / O) device 1005. The I / O 1005 can include a user interface designed to enable a user to interact with the electronic device 1000, a peripheral component interface designed to enable peripheral components to also interact with the electronic device 1000, and / or a sensor designed to determine environmental conditions and / or location information related to the electronic device 1000.

[0208] Notably, Figure 10 are merely exemplary. That is, although Figure 10 In the embodiment shown in FIG. 1, the electronic device 1000 includes a processor 1001, a controller hub 1003, a memory 1004, and the like, but in actual applications, a device using the methods of the present application can include only a portion of the components of the electronic device 1000, for example, can include only the processor 1001 and the network interface 1006. Figure 10 The nature of optional components in FIG. 1 is shown in dashed lines.

[0209] Reference is now made to Figure 11 , which shows a block diagram of a SoC (System on Chip) 1100 according to one embodiment of the present application. In Figure 11 , like components have like reference numbers. In addition, dashed lined boxes indicate optional features of the more advanced SoC's. In Figure 11 , the SoC 1100 includes an interconnect unit 1150 coupled to a processor 1110, a system agent unit 1170, a bus controller unit 1180, an integrated memory controller unit 1140, a set or one or more coprocessors 1120A-N, which can include integrated graphics logic, an image processor, an audio processor, and a video processor, a static random access memory (SRAM) unit 1130, and a direct memory access (DMA) unit 1160. In one embodiment, the coprocessors 1120A-N are dedicated processors, such as, for example, network or communication processors, compression engines, GPGPU, a high-throughput MIC processor, embedded processors, etc.

[0210] The static random access memory (SRAM) unit 1130 can include one or more tangible, non-transitory computer-readable storage media that store data and / or instructions for storage and / or retrieval. The computer-readable storage media can store instructions, specifically, a temporary and permanent copy of the instructions. The instructions can include instructions that, when executed by at least one of the processors, cause the SoC 1100 to perform the implementation method of the conference call according to the embodiments described above, specifically, the implementation method of the conference call according to the embodiments described above can be performed by the SoC 1100. Figures 6 to 9cThe implementation method of the illustrated conference call is not described here again.

[0211] Embodiments of the mechanisms disclosed herein can be implemented in hardware, software, firmware, or a combination of these implementation approaches. Embodiments of the application can be implemented as computer programs or program code executing on programmable systems such as computer programs or program code that are executable on a programmable system including at least one processor, a storage system (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device.

[0212] Program code can be applied to input instructions to perform the functions described herein and generate output information. The output information can be applied to one or more output devices, in known fashion. For purposes of this application, a processing system includes any system that has a processor, such as for example a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0213] The program code can be implemented in a high level procedural or object oriented programming language to communicate with a processing system. The program code can be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited in scope to any particular programming language. In any case, the language can be a compiled or interpreted language.

[0214] In some cases, the disclosed embodiments can be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments can also be implemented as instructions carried by or stored on one or more transitory or non-transitory machine- readable (e.g., computer-readable) media, which can be read and executed by one or more processors. For example, the instructions can be distributed over the network or by other computer readable media. Thus, a machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer), including without limitation, a floppy disk, an optical disc (e.g., a CD or DVD), a magnetic disk, a read only memory (ROM), a random access memory (RAM), an erasable programmable read only memory (EPROM), an electrically erasable programmable read only memory (EEPROM), a magnetic or optical card, a flash memory, or a tangible, machine-readable storage used in the transmission of information over the Internet via electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Accordingly, a machine-readable medium includes any type of medium for storing or transmitting information that is readable by a machine (e.g., a computer).

[0215] In the drawings, some of the structural or methodological features can be shown in particular arrangements and / or orders. However, it should be understood that such particular arrangements and / or orders can not be required. Instead, in some embodiments, the features can be arranged differently from that shown in the figures. Furthermore, inclusion of a structural or methodological feature in a particular figure is not meant to imply that such feature is required in all embodiments, and in some embodiments, the features can not be included or can be combined with other features.

[0216] It should be noted that each unit / module mentioned in each device embodiment of the present application is a logical unit / module, and in physical, one logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented by a combination of multiple physical unit / modules, and the physical implementation of the logical unit / module is not the most important. The combination of the functions implemented by these logical units / modules is the key to solving the technical problems proposed in the present application. In addition, in order to highlight the innovative part of the present application, the above-mentioned device embodiments of the present application do not introduce the units / modules that are not closely related to solving the technical problems proposed in the present application, which does not mean that the above-mentioned device embodiments do not have other units / modules.

[0217] It should be noted that in the examples and descriptions of the present application, the relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including one" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0218] Although the present application has been illustrated and described with reference to certain preferred embodiments thereof, it should be understood by those skilled in the art that various changes in form and details can be made therein without departing from the spirit and scope of the present application.

Claims

1. A method for implementing a teleconference, applied to a first electronic device, characterized in that, The method includes: The user's call merging operation is obtained, which is used to merge a first call and a second call into a conference call; wherein the first call is a suspended call between the first electronic device and at least one second electronic device, and the second call is an ongoing call between the first electronic device and a third electronic device; In response to the call merging operation, a teleconference session based on the call merging operation is established; The request is made to the conference server to merge the first call and the second call into a conference call, and to receive conference information of the conference call from the conference server. If it is determined that the first electronic device is not the conference chair in either the first call or the second call, the second call is updated based on the conference information, and the teleconference session is bound to the second call to create a conference call for the teleconference; Determining that the first electronic device's role in the second call is not that of a conference chair includes: The call attribute of the second call is determined to be a conference call, and the call role of the first electronic device in the second call is determined to be a conference member.

2. The method according to claim 1, characterized in that, The establishment of a teleconference session based on the call merging operation includes: Obtain the conference attribute information of the teleconference, and establish the teleconference session based on the conference attribute information.

3. The method according to claim 1, characterized in that, Determining that the first electronic device's role in the first call is not that of a conference chair includes: Determine that the call attribute of the first call is a normal call; or, The call attribute of the first call is determined to be a conference call, and the call role of the first electronic device in the first call is determined to be a conference member.

4. The method according to claim 3, characterized in that, The method further includes: If it is determined that the first electronic device is not the conference chair in the first call, the teleconference session is saved.

5. The method according to claim 3, characterized in that, The method further includes: If the call role of the first electronic device in the first call is determined to be that of the conference chair, or if the call role of the first electronic device in the second call is determined to be that of the conference chair, the steps of updating the second call based on the conference information and binding the teleconference session to the second call to create a conference call for the teleconference are not performed.

6. The method according to claim 1, characterized in that, The requesting conference server merges the first call and the second call into a conference call, and receives conference information from the conference server regarding the conference call, including: Send a call merging request to the conference server, the call merging request being used to request the conference server to merge the first call and the second call into a telephone conference; The conference information returned by the conference server after merging the first call and the second call into a conference call is received.

7. The method according to any one of claims 1-6, characterized in that, The method further includes: A conference subscription request is sent to the conference server. The conference subscription request is used to obtain the participant information of the telephone conference from the conference server. The participant information includes the information of the second electronic device and the information of the third electronic device. Receive meeting subscription results from the meeting server; If the meeting subscription result indicates that the meeting subscription was successful, the subscription information is received from the meeting server, and the subscription information includes the participant information of the telephone conference; The first sub-call of the teleconference is created based on information from the second electronic device, and the second sub-call of the teleconference is created based on information from the third electronic device.

8. The method according to claim 7, characterized in that, The method further includes: The conference interface of the teleconference is displayed, and the conference interface includes information about the second electronic device and information about the third electronic device.

9. An electronic device, characterized in that, include: A memory for storing instructions executed by one or more processors of the electronic device; A processor, when executing the instructions in the memory, causes the electronic device to perform the teleconference implementation method according to any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method for implementing a telephone conference as described in any one of claims 1 to 8.

Images