Method and device for realizing teleconference, and medium

Abstract

The present application is used for providing a teleconference implementation method, device and medium, the method being applied to a first electronic device, the method comprising: obtaining a call merging operation of a user, the call merging operation being used for merging a first call and a second call into a teleconference; in response to the call merging operation, establishing a teleconference session based on the call merging operation; requesting a conference server to combine the first call and the second call into a telephone conference, and receiving conference information of the telephone conference from the conference server; and determining that the call role of the first electronic device in the first call and the second call is not a conference chairman, updating the second call based on the conference information, binding the teleconference session with the second call, and creating a conference call of the teleconference. According to the method, conference members serving as teleconferences can also combine the conversation, and the cascade function of the teleconferences is achieved.

Description

Technical Field

[0001] The present application relates to the technical field of electronic equipment, and in particular to a method, device and medium for implementing a telephone conference. Background Art

[0002] Telephone conferencing under the Internet Protocol Multimedia Subsystem (IMS) is a basic function commonly used in overseas markets. A user can make or receive a call. After the call is connected, the user makes a second call. After the second call is connected, a conference call can be created by merging the two calls. At this time, the three participants in 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, Figure 1a As shown, only the conference chairperson (ie, electronic device A) is supported to add electronic device D to the conference call, such as Figure 1b As shown, it is not supported for conference members (ie, electronic device B or electronic device C) to add electronic device D to the conference call, which cannot meet the actual usage needs of users. Summary of the invention

[0004] Some implementations of the present application provide a method, device, and medium for implementing a telephone conference. The present application is introduced from multiple aspects below, and the implementations and beneficial effects of the following aspects can be referenced to each other.

[0005] In a first aspect, an embodiment of the present application provides a method for implementing a telephone conference, which is applied to a first electronic device, and the method includes:

[0006] Acquire a call merging operation of the user, where the call merging operation is used to merge a first call and a second call into a conference call; wherein the first call is a suspended call between a 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;

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

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

[0009] It is determined that the call role of the first electronic device in both the first call and the second call is not the conference chairperson, the second call is updated based on the conference information, and the conference call session is bound to the second call to create a conference call of the conference call.

[0010] According to the implementation mode of the present application, after the first electronic device obtains the user's call merging operation, when it is determined that the call role of the first electronic device in both the first call and the second call is not the conference chairperson, 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, thereby realizing the creation of a conference call of the conference call. This conference call implementation method enables conference members of the conference call to also merge calls, realizes the cascading function of the conference call, and improves the user experience. In addition, the first electronic device can realize call merging by making modifications at the application framework layer, and can simultaneously support the conference call cascading function of various chip platforms, and has good applicability.

[0011] In some implementations, establishing a conference call session based on a call merging operation includes:

[0012] Acquire conference attribute information of the telephone conference, and establish a telephone conference session based on the conference attribute information.

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

[0014] In some implementations, determining that the call role of the first electronic device in the first call is not the conference chairperson includes:

[0015] Determine that the call attribute of the first call is a common call; or,

[0016] Determining that the call attribute of the first call is a telephone conference, and determining that the call role of the first electronic device in the first call is a conference member;

[0017] Determining that the call role of the first electronic device in the second call is not the conference chairperson includes:

[0018] Determine that the call attribute of the second call is a common call; or,

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

[0020] According to the implementation mode of the present application, the first electronic device can determine whether the first electronic device is the conference chairperson in the first call and the second call based on the call attributes and the call role of the device in the call. The judgment method is simple and can ensure the accuracy of the judgment result.

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

[0022] When it is determined that the call role of the first electronic device in the first call is not the conference chairperson, the telephone conference session is saved.

[0023] According to an embodiment of the present application, when it is determined that the call role of the first electronic device in the first call is not the conference chairperson, the first electronic device can save the established telephone conference session, thereby realizing the creation of a conference call based on the telephone conference session.

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

[0025] Determine that the call role of the first electronic device in the first call is the conference chairperson, or determine that the call role of the first electronic device in the second call is the conference chairperson, and do not perform the steps of updating the second call based on the conference information, binding the conference call session with the second call, and creating a conference call for the conference call.

[0026] According to an implementation manner of the present application, when it is determined that the calling role of the first electronic device in the first call is the conference chairperson, or when it is determined that the calling role of the first electronic device in the second call is the conference chairperson, the first electronic device can determine that there is no need to create a conference call for the telephone conference, that is, there is no need to bind the created telephone conference session and the second call, thereby avoiding waste of system resources.

[0027] In some implementations, requesting the 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 includes:

[0028] Sending a call merging request to the conference server, where the call merging request is used to request the conference server to merge the first call and the second call into a telephone conference;

[0029] The conference server receives conference information of the telephone conference returned after merging the first call and the second call into a telephone conference.

[0030] According to the implementation mode of the present application, the first electronic device can send a call merge request to the conference server, requesting the conference server to merge the first call and the second call into a conference call and return the conference information, thereby updating the second call based on the conference information, so that the updated second call can provide services for the conference call, which not only improves the efficiency of creating conference calls, but also saves system resource consumption.

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

[0032] Sending a conference subscription request to the conference server, where the conference subscription request is used to obtain participant information of the telephone conference from the conference server, where the participant information includes information of the second electronic device and information of the third electronic device;

[0033] Receive conference subscription results from the conference server;

[0034] If the conference subscription result indicates that the conference subscription is successful, the subscription information from the conference server is received, and the subscription information includes the participant information of the telephone conference;

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

[0036] According to the implementation mode 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 based on the participant information to achieve separate management of different participants.

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

[0038] A conference interface of the telephone conference is displayed, where the conference interface includes information about the second electronic device and information about the third electronic device.

[0039] According to the implementation mode 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 understand that he is currently in a conference call and can perceive the information of the participants of the conference call, thereby ensuring the user's user experience of the conference call.

[0040] In a second aspect, an embodiment of the present application provides an electronic device, comprising: a memory for storing instructions executed by one or more processors of the electronic device; a processor, when the processor executes the instructions in the memory, the electronic device can execute the method for implementing a telephone conference provided by any embodiment of the first aspect of the present application. The beneficial effects that can be achieved in the second aspect can refer to the beneficial effects of any embodiment of the first aspect of the present application, and will not be repeated here.

[0041] In a third aspect, an embodiment of the present application provides a computer-readable storage medium, on which instructions are stored, and when the instructions are executed on a computer, the computer executes the method for implementing a telephone conference provided by any embodiment of the first aspect of the present application. The beneficial effects that can be achieved in the third aspect can refer to the beneficial effects of any embodiment of the first aspect of the present application, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Figure 1a A schematic diagram of a scenario in which a conference chairperson adds a member to a conference provided in some embodiments;

[0043] Figure 1bA schematic diagram of a scenario in which conference members add members to a conference provided in some embodiments;

[0044] Figure 2a and Figure 2b A schematic diagram of a telephone conference scenario provided for an embodiment of the present application;

[0045] Figure 3 A schematic diagram of establishing a new call for conference members provided in some embodiments;

[0046] Figure 4a and Figure 4b A flow chart of the IMS framework logic provided for some embodiments;

[0047] Figure 4c A schematic diagram of a merging result of merging calls of conference members provided in some embodiments;

[0048] Figure 5a A schematic diagram of the structure of an electronic device provided by an embodiment of the present application;

[0049] Figure 5b A software structure block diagram of an electronic device provided in one embodiment of the present application;

[0050] Figure 6 A flowchart of a method for implementing a telephone conference provided in one embodiment of the present application;

[0051] Figure 7 A schematic diagram of merging calls among conference members provided in one embodiment of the present application;

[0052] Figure 8 A flowchart of a method for implementing a telephone conference provided for a specific embodiment of the present application;

[0053] Figure 9a and Figure 9b A flowchart for determining to merge hosted calls provided in one embodiment of the present application;

[0054] Fig.9c A flowchart of a conference call for creating a conference call according to an embodiment of the present application;

[0055] Fig.10 A block diagram of an electronic device provided for one embodiment of the present application;

[0056] Fig.11 A block diagram of a system on chip (SOC) provided for one embodiment of the present application. DETAILED DESCRIPTION

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

[0058] In conjunction with the reference manual Figure 2a and Figure 2b , which shows a scene diagram of a telephone conference provided by an embodiment of the present application. In the embodiment of the present application, user A is the conference chair user, and user A will hold a telephone conference with user B and user C. Among them, a telephone conference refers to a user making or receiving a call, and after the call is connected, the user makes a second call, and after the second call is connected, a telephone conference is created by merging the two calls. At this time, the three participants in the telephone conference can hear each other's voices.

[0059] In this scenario, if Figure 2a As shown, Figure 2a The call interface of electronic device A corresponding to user A is shown in FIG. For example, user A's electronic device A has established a call with user B's electronic device B. Figure 2a As shown in (a), electronic device A can display a call interface 201 between electronic device A and electronic device B. Figure 2a The call shown in (a) can be a call made by user A to user B, and user B answers the call to establish the call. Or, Figure 2a The call shown in (a) may be a call established by user A receiving a call from user B and answering the call. The call interface 201 may include the phone number 202 of electronic device B (i.e., 15XXXXXXXX6) and may also include an add call control 203. The add call control 203 may be used to trigger the addition of another call to the current call.

[0060] In response to the user clicking the add call control 203, electronic device A may request to establish a call with a call device other than electronic device B. For example, electronic device A may dial user C's number (i.e., 07XXXXXXXXX1) to establish a call with electronic device C (device of user C). After electronic device A establishes a call with electronic device C, the call between electronic device A and electronic device B is held (or suspended). Electronic device A may display Figure 2a In the call interface 204, the call between electronic device A and electronic device B is held (i.e., in the hold state), and the call between electronic device A and electronic device C is in the call state (i.e., in the active state). The call interface 204 may also include a call merge control 205. After user A clicks the call merge control 205, electronic device A can establish a conference call between electronic device A, electronic device B, and electronic device C, and electronic device A can display the following information: Figure 2aThe call interface 206 shown in (c) can display the information of the participants of the current telephone conference (excluding the conference chairperson), that is, the call interface 206 can include the telephone numbers of the electronic device B and the electronic device C.

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

[0062] In order to clearly describe the embodiment of the present application, the process of implementing a telephone conference on the electronic device side is explained below by taking electronic device A as an example.

[0063] Electronic device A can first establish a first call with electronic device B, and create a telephone session 1 (callsession1), IMS call 1 (framework layer) (imscall1 / imsphoneconnection1(framework)), call connection 1 (telephone service) (telephonyconnection1(teleservice)), and call instance 1 (telecom call1) of the first call. After the first call is established, electronic device A can establish a second call with electronic device C, and create a telephone session 2 (callsession2), IMS call 2 (framework layer) (imscall2 / imsphoneconnection2(framework)), call connection 2 (telephone service) (telephonyconnection2(teleservice)), and call instance 2 (telecom call2) of the second call.

[0064] After the user clicks the call merge control in the call interface displayed by electronic device A, 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 respond to the call merge request, create an IMS conference center X for electronic device A, and pull both electronic device B and 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 electronic device A can report the conference attribute information of the conference call to the upper layer, and the conference attribute information can include but is not limited to information describing the conference identifier, call status, type and format of the telephone number, and information indicating the state of entering the conference call and the call being initiated by the electronic device, etc. For example, dc=id=3, DIALING, toa=129, conf, mo and other information can be reported. After the application framework layer at the upper layer of electronic device A receives the conference attribute information, it 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 a conference call, it can return the call merging result to the electronic device A. The bottom layer of the electronic device A can determine whether the call merging result indicates that the call merging is successful. If it indicates that the call merging is successful, it can report to the upper layer. At this time, the bottom layer can also receive the conference information (including the conference status, etc.) of the conference call from the conference server and report to the upper layer.

[0066] After the application framework layer of electronic device A determines that the call reported by the bottom layer is successfully merged, it can bind imscall2 / imsphoneconnection2 with callsession3, and copy the conference information of the conference call to imscall2 to update imscall2 / imsphoneconnection2. The application framework layer can also copy telephonyconnection2 to call connection 3 (telephonyconnection3) to create an IMS conference (imsconference). The application layer of electronic device A can create a call instance 3 (telecom call3) of the conference call under IMS, thereby completing the creation of the conference call of the merged conference call.

[0067] Electronic device A may also send a conference subscription request to the conference server, and the conference subscription request is used to obtain the participant information of the merged conference call from the conference server, and the participant information includes the information of electronic device B and electronic device C. The conference server may send a conference subscription result to electronic device A in response to the conference subscription request. Electronic device A may 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 may also send subscription information to electronic device A, and the subscription information includes the participant information of the conference call. Electronic device A may also receive subscription information from the conference server. Electronic device A may create a sub-call (call) of the conference call based on the participant information sent by the conference server, and create call instance 4 (telecom call4) and call instance 5 (telecom call5). The call interface of electronic device A may display the conference call and participant information.

[0068] The following example illustrates the problems existing in the above telephone conference scenario.

[0069] In some embodiments, the Figure 3 After creating a conference call for electronic devices A, B, and C, the electronic device that is a member of the conference (for example, electronic device B) can dial user D's number and establish a call with electronic device D. However, due to the framework restrictions in the electronic devices, after electronic device B establishes a call with electronic device D, the call interface displayed by electronic device B does not include a call merge control, so electronic device B cannot add new members to the conference.

[0070] In some embodiments, the framework restrictions in the electronic device can be removed. At this time, for the electronic device that serves as a conference member (taking electronic device B as an example), after establishing a call with electronic device D, the call interface displayed by electronic device B includes a call merge control. However, after user B clicks the call merge control, the merge still fails, and the interface cannot display the "telephone conference" and conference member information normally.

[0071] To explain the reason, the following Figure 4a and Figure 4b First, we briefly introduce the logic of the current IMS framework. 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 merge control to trigger the call merge operation, and accordingly, the electronic device can obtain the user's call merge operation. In step S402, after obtaining the call merge operation, the application framework layer of the electronic device can determine whether the call attributes of the foreground call and the background call are not a conference call (multiparty), or whether the call attribute of the foreground call is a conference call. In step S403, if the judgment result is yes, it can be determined that the foreground call is a merged hosted call. In step S404, if the judgment result is no, it can be determined that the background call is a merged hosted call.

[0072] like Figure 4b As shown, in step S405, the bottom layer of the electronic device can determine and return that the call merger is successful. In step S406, after the bottom layer of the electronic device returns that the call merger 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 judgment result is yes, the established telephone conference session can be saved. In step S408, if the judgment result is no, the established telephone conference 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 telephone conference (that is, the call role of the electronic device in the merged host call is a conference chairperson or a conference member). In step S410, if the judgment result is yes, the telephone conference session is not bound to the foreground call. In step S411, if the judgment result is no, the telephone conference session is bound to the foreground call to create a conference call for the telephone conference.

[0073] Next, the reason why the call merge fails after user B of electronic device B clicks the call merge control is explained.

[0074] After user B clicks on the call merge control in the call interface displayed by electronic device B, the conference server will create an IMS conference center Y for electronic device B, the underlying modem of electronic device B will report the conference attribute information of the conference call to the upper layer, and the upper application framework layer of electronic device B will establish a conference call session callsession3. According to the normal process, after the lower layer reports the call merge successfully to the upper layer, the upper application framework layer of electronic device B needs to bind callsession3 with the foreground call imscall2 on the IMS framework side, and copy the conference information of the conference call (including conference status, etc.) to imscall2. The upper application layer of electronic device B needs to create telecom call3 for the conference call. After the conference server returns the subscription information, electronic device B can also create sub-calls, telecom call4 and telecom call5 of the conference call based on the reported participant information.

[0075] However, electronic device B is a conference member, and the conference server reports that the call attribute of the call with electronic device A (in this case, bgcall) is a conference call, which means that electronic device B is in a conference call. The conference server reports that the call attribute of the call with electronic device D (in this case, fgcall) is a normal call. Figure 4a and Figure 4b According to the IMS framework logic shown, electronic device B can determine that bgcall is a merged host call. Moreover, when the bottom layer returns that the call merge is successful, since the call attribute of the merged host call bgcall is a conference call (the call role of electronic device B in the merged host call bgcall is a conference member), the established conference call session will not be saved, nor will the conference call session be bound to the foreground call fgcall. Figure 4c As shown, according to the above IMS framework logic, the conference call session will not be saved, and its information will not be copied to fgcall to bind it with the foreground call fgcall. But in fact, the call attribute of conference call does not mean that the current device's call role in the conference call is the conference chairperson. For electronic device B, there is no existing conference call at this time. If the upper layer call cannot get the lower layer conference call information, the upper layer cannot perceive the status and members of the conference call, so the call is not merged successfully.

[0076] In some embodiments, Figures 4a to 4cIn the illustrated embodiment, user B may first click on the exchange control in the call interface displayed by electronic device B before clicking on the call merge control. At this time, electronic device B may 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 on the call merge control in the interface again, and the application framework layer of electronic device B may determine that fgcall is a merged hosted call. Furthermore, when the bottom layer returns that the call merge is successful, since the merged hosted call is fgcall, the application framework layer of electronic device B will save the established conference call session and enter the judgment process of whether the call attribute of the merged hosted call fgcall is a conference call.

[0077] In some embodiments, for Qualcomm (QCOM) chip platforms, since QCOM has set the state of the merged host call fgcall to invalid, the call attributes of the merged host call fgcall can no longer be read, and the subsequent system binding process will be executed at this time, that is, the call merger is successful. For MediaTek (MTK) chip platforms, since the call attribute of the merged host call fgcall can still be read as a conference call, the binding process will not be executed and the call merger is unsuccessful.

[0078] In some embodiments, modifications can also be made in the Vendor / IMS module of the MTK chip manufacturer. 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 as a conference call. However, this method is only applicable to the MTK chip platform and not to the QCOM) chip platform.

[0079] Therefore, a new method for implementing a conference call is needed, so that electronic devices that are conference members can also merge calls. To this end, the embodiments of the present application provide a method, device, and medium for implementing a conference call, so that conference members that are conference members can also merge calls, add people to the conference, and realize the cascading function of the conference call.

[0080] According to an implementation of the present application, after the first electronic device obtains the user's call merging operation, if it is determined that the first electronic device's call role in both the first call and the second call is not the conference chairperson, the created telephone conference session is bound to the second call, and the second call is updated according to the conference information of the telephone conference, thereby realizing the creation of a conference call of the telephone conference. This telephone conference implementation method enables conference members of the telephone conference to merge calls, realizes the cascading function of the telephone conference, and improves the user experience.

[0081] The embodiments of the present application do not limit the form of the electronic device. The electronic device may be a mobile phone, a tablet computer, a laptop computer, a personal computer (PC), a wearable device, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, a vehicle-mounted device (for example, a vehicle computer, a vehicle-mounted navigation system), or other electronic devices that can conduct IMS teleconferencing. The system installed in the electronic device may be an Android, IOS, Hongmeng OpenHarmonyOS, or other systems, which is not limited here.

[0082] The method of the embodiment of the present application is described below in conjunction with the specific structure of the electronic device.

[0083] Figure 5a The structure diagram of an electronic device 500 provided by an embodiment of the present application is shown. The electronic device 500 may 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 speaker 570A, a receiver 570B, a microphone 570C, an earphone interface 570D, a sensor module 580, a button 590, a motor 591, an indicator 592, a camera 593, a display screen 594, and a Subscriber Identification Module (SIM) card interface 595, etc. The sensor module 580 may include a pressure sensor 580A, a gyroscope sensor 580B, an air 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 may include one or more processing units, for example, the processor 510 may include an application processor (AP), a modem processor, a graphics processor (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 integrated into one or more processors. For example, the processor 510 can be used to execute each step of the method for implementing a telephone conference in the embodiment of the present application.

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

[0086] The processor 510 may 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 may store instructions or data that the processor 510 has just used or cyclically used. If the processor 510 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 510, and thus improves the efficiency of the system.

[0087] In some embodiments, after acquiring the user's call merging operation, the processor 510 can bind the created telephone conference session and the foreground call when it is determined that the call role of the electronic device 500 in both the background call and the foreground call is not the conference chairperson, and update the foreground call according to the conference information of the telephone conference to achieve the creation of the conference call of the telephone conference. This telephone conference implementation method enables conference members of the telephone conference to merge calls, realizes the cascading function of the telephone conference, and improves the user experience.

[0088] In some embodiments, the processor 510 may include one or more interfaces. The interface may include an Inter-Integrated Circuit (I2C) interface, an Inter-Integrated Circuit Sound (I2S) interface, a Pulse Code Modulation (PCM) interface, a Universal Asynchronous Receiver / Transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a General-Purpose Input / Output (GPIO) interface, and a 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 may include multiple groups of I2C buses. The processor 510 may be coupled to the touch sensor 580K, the charger, the flash, the camera 593, etc. through different I2C bus interfaces. For example: the processor 510 may be coupled to the touch sensor 580K through the I2C interface, so that the processor 510 communicates with the touch sensor 580K through the I2C bus interface to realize 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 include multiple groups of I2S buses. The processor 510 can be coupled to the audio module 570 via the I2S bus to achieve communication between the processor 510 and the audio module 570. In some embodiments, the audio module 570 can transmit an audio signal to the wireless communication module 560 via the I2S interface to achieve the function of answering a call through a 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 via the PCM bus interface. In some embodiments, the audio module 570 can also transmit audio signals to the wireless communication module 560 via the PCM interface to realize the function of answering calls via a 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 with peripheral devices such as the display screen 594 and the camera 593. The MIPI interface includes a camera serial interface (CSI), a display serial interface (DSI), etc. In some embodiments, the processor 510 and the camera 593 communicate via the CSI interface to realize the shooting function of the electronic device 500. The processor 510 and the display screen 594 communicate via the DSI interface to realize the display function of the electronic device 500.

[0093] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the electronic device 500. In other embodiments of the present application, the electronic device 500 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[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 and the baseband processor.

[0095] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 500 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, antenna 1 can be reused as a diversity antenna for 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 solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the electronic device 500. The mobile communication module 550 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 550 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 550 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 550 can be set in the processor 510. In some embodiments, at least some of the functional modules of the mobile communication module 550 can be set in the same device as at least some of the modules of the processor 510.

[0097] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the 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. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to a speaker 570A, a receiver 570B, etc.), or displays an image or video through a display screen 594. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 510 and be set in the same device as the mobile communication module 550 or other functional modules.

[0098] The wireless communication module 560 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the electronic device 500. The wireless communication module 560 can be one or more devices integrating at least one communication processing module. The wireless communication module 560 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 510. The wireless communication module 560 can also receive the signal to be sent from the processor 510, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0099] In some embodiments, the antenna 1 of the electronic device 500 is coupled to the mobile communication module 550, and the antenna 2 is coupled to the wireless communication module 560, so that the electronic device 500 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may 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. GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the Beidou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS) and / or the Satellite Based Augmentation System (SBAS).

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

[0101] The display screen 594 is used to display images, videos, etc. 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 or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 500 may include 1 or N display screens 594, where N is a positive integer greater than 1.

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

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

[0104] The internal memory 521 can be used to store computer executable program codes, and the executable program codes include instructions. The internal memory 521 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 500 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 521 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash memory (Universal Flash Storage, UFS), etc. The processor 510 executes various functional 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 provided in the processor.

[0105] In some embodiments, the internal memory 521 may store instructions for implementing a conference call. The processor 510 runs the instructions for implementing the conference call so that after obtaining the user's call merging operation, the processor 510 can bind the created conference call session with the foreground call when it is determined that the call role of the electronic device 500 in both the background call and the foreground call is not the conference chairperson, and update the foreground call according to the conference information of the conference call to create a conference call of the conference call. This conference call implementation method enables conference members of the conference call to merge calls, realizes the cascading function of the conference call, and improves the user experience.

[0106] The electronic device 500 can implement audio functions such as music playing and recording through the audio module 570, the speaker 570A, the receiver 570B, the microphone 570C, the headphone jack 570D, and the application processor.

[0107] The audio module 570 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. 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 some functional modules of the audio module 570 can be arranged in the processor 510.

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

[0109] The receiver 570B, also called a "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device 500 receives a call or voice message, the voice can be received by placing the receiver 570B close to the human ear.

[0110] Microphone 570C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 570C 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, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the electronic device 500 can also be provided with three, four or more microphones 570C to collect sound signals, reduce noise, identify the sound source, realize directional recording function, etc.

[0111] The pressure sensor 580A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 580A can be set on the display screen 594. There are many types of pressure sensors 580A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 580A, the capacitance between the electrodes changes. The electronic device 500 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 594, the electronic device 500 detects the touch operation intensity according to the pressure sensor 580A. The electronic device 500 can also calculate the touch position according to the detection signal of the pressure sensor 580A. In some embodiments, touch operations acting on 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 the first pressure threshold acts on the short message application icon, an instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, an instruction to create a new short message is executed.

[0112] The touch sensor 580K is also called a "touch control device". The touch sensor 580K can be set on the display screen 594, and the touch sensor 580K and the display screen 594 form a touch screen, also called a "touch control screen". The touch sensor 580K is used to detect touch operations acting on or near it. The touch sensor can pass 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 set on the surface of the electronic device 500, which is different from the position of the display screen 594.

[0113] The key 590 includes a power key, a volume key, etc. The key 590 may be a mechanical key or a touch key. The electronic device 500 may 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 used to connect a SIM card. The SIM card can be connected to and separated from the electronic device 500 by inserting it into the SIM card interface 595 or pulling it out from the SIM card interface 595. The electronic device 500 can support 1 or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 595 can support Nano SIM cards, Micro SIM cards, SIM cards, and 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 also be compatible with different types of SIM cards. The SIM card interface 595 can also be compatible with external memory cards. The electronic device 500 interacts with the network through the SIM card to implement functions such as calls and data communications. 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 micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the layered architecture as an example to illustrate the software structure of the electronic device 500. Among them, the present application does not limit the type of operating system of the electronic device. For example, it can be an Android system, a Linux system, a Windows system, an iOS system, a Harmony Operating System (Harmony OS), etc.

[0116] Figure 5b The software structure block diagram of an electronic device 500 provided by an embodiment of the present application is shown. The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. Figure 5b As shown, the electronic device 500 may 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] Among them, the application layer may include dialer, telephony, telecommunication (Telecom) and call user interface (InCall UI). Dialer can provide users with services such as dialing, answering calls, and hanging up calls. Telephony can be used to manage phone calls, such as caller ID, answering calls, and hanging up calls. Telecom can provide API support for phone calls, which can cooperate with hardware devices to provide voice, SMS, data link, SIM card management, phone book and other functions. InCall UI can provide users with interfaces during incoming calls, outgoing calls or calls, such as dialing interface, incoming call interface, call interface, etc. The contact application can manage (add, delete, change or synchronize) contact information. Telephony, Telecom and InCall UI jointly provide users with call functions. For example, when Telephony receives an incoming call, it can first notify Telecom, and then Telecom notifies InCallUI of the incoming call and displays the incoming call interface.

[0118] The application framework layer can provide 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 phone functions. These APIs can be used to obtain network information, monitor phone status changes, send text messages, etc. The Telecom framework provides a unified interface to manage phone calls, including making calls, answering calls, and call control (such as holding, hanging up, switching speakers). The working principle of the Telecom framework is to act as an intermediary between the Telephony framework and other call services. When there is an incoming or outgoing call, the Telephony framework notifies the Telecom framework, and then the Telecom framework handles the call according to the default dialer application and call settings configured by the user. The NET / IMS framework mainly includes the IMS manager (ImsManager) that provides the IMS service API, and the call (ImsCall) created by the ImsManager that is responsible for handling IMS voice and video call connections.

[0120] HAL provides a unified and simple hardware operation interface for upper-layer applications, with the purpose of abstracting the hardware and reducing the coupling between the operating system and the hardware of electronic devices. HAL and the Telephony framework can reliably transmit data, send commands, and parse responses through the Radio Interface Layer (RIL). RIL is the bridge between the modem and the wireless access point in electronic devices.

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

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

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

[0124] It is to be understood that the structure illustrated in the embodiment 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 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may 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 may be the same or different, and the embodiments of the present application do not specifically limit this.

[0126] The specific process of the method for implementing a telephone conference provided in the embodiment of the present application is described in detail below.

[0127] The method for implementing a telephone conference provided in the embodiment of the present application can be applied to Figure 5a The hardware structure shown in Figure 5bIn an electronic device with the software structure shown in the figure, or with more or fewer components than shown in the figure, or with some components combined, or some components separated, or with different component arrangements, etc., and with similar hardware structures and software structures.

[0128] The following uses a mobile phone as an example to describe in detail a method for implementing a conference call provided by an embodiment of the present application. Figure 6 As shown, Figure 6 A flowchart of a method for implementing a conference call provided by an embodiment of the present application is shown. The method can be executed by mobile phone B (as an example of a first electronic device), and the method can include steps S601-S606.

[0129] S601: Mobile phone B obtains a call merging operation of the user, where the call merging operation is 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 conference call.

[0130] The background call may be a hung call between mobile phone B and mobile phone A and mobile phone C (as an example of at least one second electronic device), that is, the call between mobile phone B and mobile phone A and mobile phone C is in a call holding state (i.e., in a hold state). The foreground call may be an ongoing call between mobile phone B and mobile phone D (as an example of a third electronic device), that is, the call between mobile phone B and mobile phone D is in a call state (i.e., in an 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 where the background call is a conference call, the conference call can be a conference call established by other mobile phones (such as mobile phone A), that is, mobile phone B is a conference member of the conference call. The conference call can also be a conference call established by mobile phone B, that is, mobile phone B is the conference chair of the conference call. In the case where the background call is a normal call, it can be a call between other mobile phones (such as mobile phone A) and mobile phone B, or it can be a call between mobile phone B and other mobile phones (such as mobile phone A), in which case 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 relevant content of the background call can be referred to, and the embodiment of the present application will not be repeated here.

[0133] It should be noted that in the embodiment of the present application, the background call is a telephone conference with other mobile phones (such as mobile phone A) as the conference chairperson, and the foreground call is an ordinary call. However, it is not limited to this. In some embodiments, the background call can be an ordinary call, the foreground call can also be a telephone conference, or both the background call and the foreground call can be a telephone conference or an ordinary call, and the embodiment of the present application does not specifically limit this.

[0134] In the embodiment 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 between mobile phone A, mobile phone B and mobile phone C established by mobile phone A, or a conference call between mobile phone A, mobile phone B and mobile phone C established by mobile phone B. The embodiment of the present application does not impose specific restrictions on this. Thereafter, mobile phone B can establish a call with mobile phone D by dialing the number of user D. After mobile phone B and mobile phone D establish a call, the call between mobile phone B and mobile phone D is in the active state, which is a foreground call; the call between mobile phone B and mobile phone A and mobile phone C is in the hold state, which is a background call.

[0135] In the embodiment 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 calls between mobile phone B and mobile phone A and mobile phone C are held, and the call between mobile phone B and mobile phone D is in a call state. The call interface can also include a call merge control. Mobile phone B can detect a user's click operation on the call merge control. When the user's click operation on the call merge control is detected, it is determined that the user's call merge operation is obtained. The call merge operation can be used to merge the background call and the foreground call into a conference call. Among them, the click operation on the call merge control may include but is not limited to the user's finger pressing the area where the call merge control is located, which is not limited here.

[0136] In some embodiments, the user can also trigger call merging by long pressing the call merge control, double-clicking the call merge control, and other operations. The specific implementation method is similar to the implementation method of clicking the call merge control mentioned above. Please refer to the relevant content of the implementation method of clicking the call merge control. The embodiments of this application will not be repeated here.

[0137] It should be noted that the above-mentioned operation method for triggering call merging is only an example. In actual application, the user can also trigger call merging by other operations such as dragging one call to the area where another call is located. The embodiment of the present application does not specifically limit the specific implementation method of the call merging operation.

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

[0139] In the embodiment of the present application, after mobile phone B obtains the user's call merging operation, it can establish a telephone conference session corresponding to the telephone 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 telephone conference, and establish the telephone conference session based on the obtained conference attribute information.

[0140] In actual applications, the modem at the bottom layer of mobile phone B can send conference attribute information of the conference call to the IMS application. The attribute information may include but is not limited to information describing the conference ID, call status, type and format of the telephone number, as well as information indicating the entry into the conference call status, information that the call is initiated by an electronic device, etc. For example, dc=id=3, DIALING, toa=129, conf, mo and other information can be sent. After receiving the conference attribute information, the IMS application can send the conference attribute information to the application framework layer on the upper layer of mobile phone B. After receiving the conference attribute information, the application framework layer can establish a conference call session corresponding to the conference call according to the conference attribute information. The specific establishment method will not be repeated in this embodiment of the present application.

[0141] It can be understood that mobile phone B can establish a telephone conference session based on the 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 the embodiment of the present application, mobile phone B first establishes a conference call with mobile phone A and mobile phone C, and then establishes a call with mobile phone D. After obtaining the user's call merge operation, it can request the conference server to merge the background call and the foreground call into a conference call. Figure 7 , the conference server can establish IMS conference center Y for mobile phone B according to the request of mobile phone B, and connect IMS conference center X and mobile phone D to the conference to complete the creation of the merged conference call. In this way, users of mobile phone A, mobile phone B, mobile phone C and mobile phone D can hear each other's voice. Among them, IMS conference center X can be the IMS conference center established by the conference server for mobile phone A when establishing a conference call between mobile phone A, mobile phone B and mobile phone C based on the request of mobile phone A.

[0144] S604: Mobile phone B receives conference information of the telephone conference from the conference server.

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

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

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

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

[0149] In an embodiment of the present application, after mobile phone B obtains the user's call merge operation, it can also obtain call attribute information of the background call and the foreground call, as well as the call role information of mobile phone B in the background call and the foreground call from the conference server, thereby determining whether the call role of mobile phone B in the background call and the foreground call is the conference chairman.

[0150] Among them, when it is determined that the call attribute information of the background call / foreground call indicates that the call is a normal call, it can be directly determined that the call role of mobile phone B in the background call / foreground call is not the conference chairperson. When it is determined that the call attribute information of the background call / foreground call indicates that the call is a telephone conference, if the call role information of mobile phone B in the background call / foreground call indicates that the call role of mobile phone B is a conference member, it can be determined that the call role of mobile phone B in the background call / foreground call is not the conference chairperson. If the call role information of mobile phone B in the background call / foreground call indicates that the call role of mobile phone B is the conference chairperson, it can be determined that the call role of mobile phone B in the background call / foreground call is the conference chairperson.

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

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

[0153] In the embodiment of the present application, mobile phone B can update the foreground call based on the acquired conference information, and directly bind the established telephone conference session to the foreground call, thereby completing the creation of the conference call of the telephone conference.

[0154] In actual applications, when the application framework layer of mobile phone B determines that the call merger is successful and the call role of mobile phone B in both the background call and the foreground call is not the conference chairperson, the imscall2 / imsphoneconnection2 of the foreground call can be bound to the established conference call session callsession3, and the conference information of the conference call can be copied to imscall2 to update imscall2 / imsphoneconnection2. The telephonyconnection2 of the foreground call can also be copied to the telephonyconnection3 of the conference call to create an IMS conference (imsconference). The application layer of mobile phone B can also create telecom call3 of the conference call under IMS, thereby completing the creation of the conference call of the merged conference call.

[0155] In some embodiments, if it is determined that the call role of mobile phone B in the background call is not the conference chairperson, the telephone conference session can be saved, and then the subsequent steps are performed. If it is determined that the call role of mobile phone B in the background call is the conference chairperson, the telephone conference session may not be saved, and then the subsequent steps are not performed.

[0156] It can be understood that when it is determined that the call role of mobile phone B in the background call is not the conference chairperson, mobile phone B can save the established telephone conference session, thereby achieving the creation of a conference call based on the telephone conference session.

[0157] In some embodiments, if it is determined that the call role of mobile phone B in the background call is the conference chairperson, or if it is determined that the call role of mobile phone B in the foreground call is the conference chairperson, step S606 is not performed. That is, in the case where it is determined that the call role of mobile phone B in the background call is the conference chairperson, regardless of whether the call role of mobile phone B in the foreground call is the conference chairperson, there is no need to save the telephone conference session or create a conference call for the telephone conference. In the case where it is determined that the call role of mobile phone B in the background call is not the conference chairperson, and it is determined that the call role of mobile phone B in the foreground call is the conference chairperson, although the telephone conference session is saved, there is still no need to create a conference call for the telephone conference.

[0158] It can be understood that when it is determined that the calling role of mobile phone B in the background call is the conference chairperson, or when it is determined that the calling role of mobile phone B in the foreground call is the conference chairperson, mobile phone B can determine that there is no need to create a conference call for the telephone conference, that is, there is no need to bind the created telephone conference session and the foreground call, thereby avoiding waste of system resources.

[0159] In summary, after the mobile phone obtains the user's call merging operation, when it is determined that the mobile phone's call role in both the background call and the foreground call is not the conference chairperson, the created conference call session and the foreground call are bound, and the foreground call is updated according to the conference information of the conference call, thereby realizing the creation of the conference call of the conference call. This conference call implementation method enables conference members of the conference call to merge calls, realizes the cascading function of the conference call, and improves the user experience. In addition, the mobile phone can realize call merging by making modifications at the application framework layer, and can simultaneously support the conference call cascading function of various chip platforms, and has good applicability.

[0160] The following is a further description of the method for implementing a telephone conference provided by the embodiment of the present application through a specific embodiment. Figure 8 As shown, Figure 8 A flowchart showing a method for implementing a telephone conference provided by a specific embodiment of the present application is shown. Figure 6 To further illustrate the illustrated embodiment, the method may include steps S801 - S808 .

[0161] S801: Mobile phone B (as an example of a first electronic device) obtains a call merging operation of the user, where the call merging operation is 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 conference call.

[0162] S802: Mobile phone B responds to the call merging operation and establishes a telephone conference session based on the call merging operation.

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

[0164] In the embodiment of the present application, after mobile phone B obtains the call merging operation, it 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.

[0165] In actual applications, mobile phone B may send a call merging request to the modem through the hardware abstraction layer HAL interface of the IMS application. The modem may receive the call merging request and send the call merging request to the conference server.

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

[0167] In the embodiment of the present application, after receiving the call merge request sent by mobile phone B, the conference server can respond to the call merge request, merge the background call and the foreground call, and complete the creation of the merged telephone conference. Thereafter, the conference server can return the call merge result to mobile phone B, and the call merge result can be used to indicate whether the call merge is successful.

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

[0169] In the embodiment of the present application, when the call merger is successful (i.e., the telephone conference is successfully created), the conference server may also send the conference information of the merged telephone conference to mobile phone B. The conference information may include but is not limited to information such as the conference status. When the call merger fails, the conference server will not send the conference information of the telephone conference to mobile phone B.

[0170] Accordingly, 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. If the call merging is successful, the conference information of the telephone conference returned by the conference server can also be received.

[0171] It can be understood that mobile phone B can send a call merge request to the conference server, requesting the conference server to merge the background call and the foreground call into a conference call and return the conference information, thereby updating 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 efficiency of creating conference calls, but also saves system resource consumption.

[0172] S806: Mobile phone B determines to merge the background call and the foreground call into a hosted call.

[0173] In the embodiment of the present application, after mobile phone B obtains the call merging operation, it can determine the merged host call from the two calls to be merged. Specifically, only when the call role of mobile phone B in the background call is the conference chairperson, the background call will be set as the merged host call.

[0174] The process of determining the merged hosted calls is described below with reference to the accompanying drawings.

[0175] In conjunction with the reference manual Figure 9aIn step S901, the user can click the call merge control in the call interface to trigger the call merge operation. Accordingly, mobile phone B can obtain the user's call merge operation. In step S902, after obtaining the call merge operation, mobile phone B can obtain the call attribute information of the background call and the call role information of mobile phone B in the background call from the conference server, so as to determine whether the call role of mobile phone B in the background call is the conference chairperson. In step S903, when it is determined that the call role of mobile phone B in the background call is the conference chairperson, the background call can be determined to be a merged hosted call. In step S904, when it is determined that the call role of mobile phone B in the background call is not the conference chairperson, the foreground call can be determined to be a merged hosted call.

[0176] In some embodiments, the Figure 9b In step S905, the user can click the call merge control in the call interface to trigger the call merge operation, and accordingly, mobile phone B can obtain the user's call merge operation. In step S906, after obtaining the call merge operation, mobile phone B can obtain the call attribute information of the background call and the foreground call, as well as the call role information of mobile phone B in the background call from the conference server. Mobile phone B can determine whether the background call and the foreground call are not a conference call based on the call attribute information of the background call and the foreground call. When the judgment result is no, it is determined whether the call role of mobile phone B in the background call is not the conference chairperson based on the call role information of mobile phone B in the background call. In step S907, if it is determined that the background call and the foreground call are not a conference call, or it is determined that the call role of mobile phone B in the background call is not the conference chairperson, the foreground call can be determined to be a merged host call. In step S908, if it is determined that the call role of mobile phone B in the background call is the conference chairperson, the background call can be determined to be a merged host call.

[0177] It should be noted that in the embodiment of the present application, step S802, step S803 to step S805, and step S806 can be executed sequentially or simultaneously. The present application does not specifically limit the execution order of step S802, step S803 to step S805, and step S806.

[0178] Next return Figure 8 , describing the method for implementing a telephone conference in an embodiment of the present application.

[0179] S807: Mobile phone B determines that the call role of mobile phone B in the combined hosted call is not the conference chairperson.

[0180] In the embodiment of the present application, when mobile phone B determines that the call merger is successful, it is not necessary to bind the merged hosted call to the telephone conference session only if the call role of mobile phone B in the merged hosted call is indeed the conference chairperson. If the call role of mobile phone B in the merged hosted call is not the conference chairperson, it is necessary to bind the merged hosted call to the telephone conference session.

[0181] In the embodiment of the present application, when it is determined that the foreground call is a combined host call, mobile phone B can also obtain the call attribute information of the foreground call and the call role information of mobile phone B in the foreground call from the conference server, so as to determine whether the call role of mobile phone B in the foreground call is the conference chairperson. When it is determined that the call role of mobile phone B in the foreground call is the conference chairperson, it is determined that the call role of mobile phone B in the combined host call is the conference chairperson, and the subsequent step S808 does not need to be executed at this time; otherwise, it can be determined that the call role of mobile phone B in the combined host call is not the conference chairperson, and the subsequent step S808 can be executed at this time.

[0182] In the embodiment of the present application, when it is determined that the background call is a merged hosted call, the call role of mobile phone B in the merged hosted call must be the conference chairperson, and there is no need to perform the subsequent step S808.

[0183] S808: Mobile phone B updates the foreground call based on the conference information, and binds the telephone conference session with the foreground call to create a conference call of the telephone conference.

[0184] In the embodiment of the present application, mobile phone B can update the foreground call based on the acquired conference information, and directly bind the established telephone conference session to the foreground call, thereby completing the creation of the conference call of the telephone conference.

[0185] The process of establishing a conference call for a telephone conference is described below with reference to the accompanying drawings.

[0186] In a specific embodiment, in conjunction with the reference specification Fig.9cIn step S909, mobile phone B can determine that the call merger is successful according to the call merger result returned by the conference server. In step S910, when mobile phone B determines that the call merger is successful, it can first determine whether the foreground call is a merged host call. In step S911, when the foreground call is a merged host call, the telephone conference session can be saved. In step S912, when mobile phone B determines that the foreground call is not a merged host call (that is, the background call is a merged host call), the telephone conference session may not be saved. In step S913, mobile phone B can determine whether the call role of mobile phone B in the merged host call is the conference chairperson. In step S914, if the judgment result is yes, there is no need to execute step S808, that is, the telephone conference session is not bound to the foreground call, and there is no need to create a conference call of the telephone conference. In step S915, if the judgment result is no, step S808 can be executed, that is, the telephone conference session is bound to the foreground call to create a conference call of the telephone conference.

[0187] Exemplarily, when the foreground call is a combined host call, if mobile phone B determines that the call role of mobile phone B in the foreground call is not the conference chairperson, step S808 can be executed to create a conference call for the conference call. If mobile phone B determines that the call role of mobile phone B in the foreground call is the conference chairperson, step S808 does not need to be executed, that is, there is no need to create a conference call for the conference call. When the background call is a combined host call, the call role of mobile phone B in the background call must be the conference chairperson, and step S808 does not need to be executed at this time.

[0188] In some embodiments, the method may further include the following steps: 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 telephone conference from the conference server, and the participant information includes the information of the telephone conference conducted with mobile phone A and mobile phone C (as an example of at least one second electronic device) and the information of mobile phone D (as an example of a third electronic device). After mobile phone B sends the conference subscription request to the conference server, the conference server returns the conference subscription result to mobile phone B. 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 unsuccessful, the conference server will not send the subscription information to mobile phone B; if the conference subscription result indicates that the conference subscription is successful, the conference server will send the subscription information to mobile phone B. Mobile phone B can receive the subscription information from the conference server, and the subscription information includes the participant information of the telephone conference, that is, the information of the telephone conference conducted with mobile phone A and mobile phone C and the information of mobile phone D. Mobile phone B can also create a first sub-conversation of the telephone conference based on the information of the telephone conference conducted with mobile phone A and mobile phone C, and create a second sub-conversation of the telephone conference based on the information of mobile phone D. The method for creating a sub-conversation is not described in detail in the embodiment of the present application.

[0190] In actual applications, mobile phone B can send a 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 it to the conference server. The modem of 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 also send the subscription information to the IMS application of mobile phone B. After receiving the subscription information, the IMS application can send the subscription information to the upper application framework layer of mobile phone B, thereby creating two sub-calls of the conference call.

[0191] It can be understood that mobile phone B 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 to achieve separate management of different participants.

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

[0193] In the embodiment of the present application, after creating two sub-calls, mobile phone B can display a conference interface of the telephone conference on the display screen, and the conference interface can display the participant information of the telephone conference. The method of displaying the conference interface in the embodiment of the present application is not repeated here.

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

[0195] It should be noted that other contents in step S801 to step S808 in the embodiment of the present application can be referred to Figure 6 to Figure 7 The relevant contents in the illustrated embodiments will not be repeated in the embodiments of the present application.

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

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

[0198] The processor, when the processor executes the instructions in the memory, can make the electronic device execute the above embodiment Figures 6 to 9c The method for implementing a telephone conference is shown.

[0199] The present application also provides a computer-readable storage medium, on which instructions are stored. When the instructions are executed by a processor, the processor executes the above-mentioned embodiment. Figures 6 to 9c The method for implementing a telephone conference is shown.

[0200] The present application also provides a computer program product comprising instructions, which, when executed on an electronic device, enables a processor to execute the above-mentioned embodiments. Figures 6 to 9c The method for implementing a telephone conference is shown.

[0201] Reference now Fig.10 , shown is a block diagram of an electronic device 1000 according to one embodiment of the present application. The electronic device 1000 may 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 1001 via a multi-drop bus such as a front side bus (FSB), a point-to-point interface such as a Quick Path Interconnect (QPI), or a similar connection 1006. The processor 1001 executes instructions that control general types of data processing operations. In one embodiment, the controller hub 1003 includes, but is not limited to, a graphics memory controller hub (Graphics Memory Controller Hub, GMCH) (not shown) and an input / output hub (Input Output Hub, IOH) (which may be on a separate chip) (not shown), wherein the GMCH includes a memory and a graphics controller and is coupled to the IOH.

[0202] The electronic device 1000 may 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 may be integrated within the processor (as described in the present application), with the memory 1004 and the coprocessor 1002 being directly coupled to the processor 1001 and the controller hub 1003, with the controller hub 1003 being in a single chip with the IOH.

[0203] The memory 1004 may be, for example, a dynamic random access memory (DRAM), a phase change memory (PCM), or a combination of the two. The memory 1004, as a computer-readable storage medium, may include one or more tangible, non-temporary computer-readable media for storing data and / or instructions. For example, the memory 1004 may include any suitable non-volatile memory such as a flash memory and / or any suitable non-volatile storage device, such as one or more hard disk drives (HDD(s)), one or more compact disc (CD) drives, and / or one or more digital versatile disc (DVD) drives.

[0204] According to some embodiments of the present application, the memory 1004 as a computer-readable storage medium stores instructions, and when the instructions are executed on the computer, the system 1000 executes the method for implementing the telephone conference according to the above embodiment. Figures 6 to 9c The implementation method of the telephone conference shown is not repeated here.

[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, a compression engine, a graphics processor, a general purpose graphics processor (GPGPU), or an embedded processor. The optional nature of the coprocessor 1002 is indicated by a dashed line in Fig.10 middle.

[0206] In one embodiment, the electronic device 1000 may further include a network interface (Network Interface Controller, NIC) 1006. The network interface 1006 may include a transceiver for providing a radio interface for the electronic device 1000, thereby communicating with any other suitable device (such as a front-end module, an antenna, etc.). In various embodiments, the network interface 1006 may be integrated with other components of the electronic device 1000. The network interface 1006 may implement the functions of the communication unit in the above-mentioned embodiments.

[0207] The electronic device 1000 may further include an input / output (I / O) device 1005. The I / O 1005 may 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 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] It is worth noting that Fig.10 This is for illustrative purposes only. Fig.10 It is shown that the electronic device 1000 includes multiple devices such as a processor 1001, a controller hub 1003, and a memory 1004. However, in actual applications, the devices using the methods of the present application may only include a part of the devices of the electronic device 1000, for example, it may only include the processor 1001 and the network interface 1006. Fig.10 The properties of optional devices are shown with dotted lines.

[0209] Reference now Fig.11 , which is a block diagram of a SoC (System on Chip) 1100 according to an embodiment of the present application. Fig.11 In the FIG, similar components have the same reference numerals. In addition, the dashed boxes are optional features of more advanced SoCs. Fig.11 In the embodiment, SoC 1100 includes: an interconnect unit 1150, which is coupled to a processor 1110; a system agent unit 1170; a bus controller unit 1180; an integrated memory controller unit 1140; a group or one or more coprocessors 1120, which may 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 coprocessor 1120 includes a special-purpose processor, such as, for example, a network or communication processor, a compression engine, a GPGPU, a high-throughput MIC processor, or an embedded processor.

[0210] The static random access memory (SRAM) unit 1130 may include one or more tangible, non-transitory computer-readable storage media for storing data and / or instructions. The computer-readable storage medium may store instructions, specifically, temporary and permanent copies of the instructions. The instructions may include: when executed by at least one unit in the processor, causing the Soc 1100 to execute the implementation method of the telephone conference according to the above embodiment, which may be specifically referred to in the above embodiment. Figures 6 to 9cThe implementation method of the telephone conference shown is not repeated here.

[0211] The various embodiments of the mechanism disclosed in the present application can be implemented in hardware, software, firmware or a combination of these implementation methods. The embodiments of the present application can be implemented as a computer program or program code executed on a programmable system, which includes 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 in this application and generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

[0213] Program code can be implemented with high-level programming language or object-oriented programming language to communicate with the processing system. When necessary, program code can also be implemented with assembly language or machine language. In fact, the mechanism described in this application is not limited to the scope of any specific programming language. In either case, the language can be a compiled language or an interpreted language.

[0214] In some cases, the disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried or stored on one or more temporary or non-temporary machine-readable (e.g., computer-readable) storage media, which may be read and executed by one or more processors. For example, instructions may be distributed over a network or by other computer-readable media. Therefore, machine-readable media may include any mechanism for storing or transmitting information in a machine (e.g., computer) readable form, including, but not limited to, floppy disks, optical disks, optical disks, compact disc read-only memories (Compact Disc Read Only Memory, CD-ROMs), magneto-optical disks, read-only memories (Read Only Memory, ROM), random access memories (RAM), erasable programmable read-only memories (Erasable Programmable Read Only Memory, EPROM), electrically erasable programmable read-only memories (Electrically Erasable Programmable Read Only Memory, EEPROM), magnetic cards or optical cards, flash memory, or a tangible machine-readable memory for transmitting information (e.g., carrier waves, infrared signal digital signals, etc.) using the Internet in electrical, optical, acoustic, or other forms of propagation signals. Accordingly, machine-readable media include any type of machine-readable media suitable for storing or transmitting electronic instructions or information in a form readable by a machine (eg, a computer).

[0215] In the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be required. Instead, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the accompanying drawings of the specification. In addition, the inclusion of structural or method features in a particular figure does not mean that such features are required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0216] It should be noted that the units / modules mentioned in the various device embodiments of the present application are all logical units / modules. Physically, a logical unit / module can be a physical unit / module, or a part of a physical unit / module, or can be implemented as a combination of multiple physical units / modules. The physical implementation method of these logical units / modules themselves is not the most important. The combination of functions implemented by these logical units / modules is the key to solving the technical problems proposed by 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 units / modules that are not closely related to solving the technical problems proposed by the present application, which does not mean that there are no other units / modules in the above-mentioned device embodiments.

[0217] It should be noted that, in the examples and description of the present application, relational terms such as first and second, etc. 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 these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or equipment including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or equipment. In the absence of further restrictions, the elements defined by the statement "comprise one" do not exclude the presence of other identical elements in the process, method, article or equipment including the elements.

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

Claims

1. A method for implementing a telephone conference, applied to a first electronic device, characterized in that: The method comprises: Acquire a call merging operation of the user, where the call merging operation is used to merge a first call and a second call into a conference call; wherein the first call is a hung 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, establishing a telephone conference session based on the call merging operation; Requesting a conference server to merge the first call and the second call into a telephone conference, and receiving conference information of the telephone conference from the conference server; Determine that the call role of the first electronic device in both the first call and the second call is not a conference chairperson, update the second call based on the conference information, bind the telephone conference session with the second call, and create a conference call of the telephone conference.

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

3. The method according to claim 1, characterized in that The determining that the call role of the first electronic device in the first call is not a conference chairperson includes: Determine that the call attribute of the first call is a common call; or, Determining that the call attribute of the first call is a telephone conference, and determining that the call role of the first electronic device in the first call is a conference member; The determining that the call role of the first electronic device in the second call is not a conference chairperson includes: Determine that the call attribute of the second call is a common call; or, It is determined that the call attribute of the second call is a telephone conference, and it is determined that the call role of the first electronic device in the second call is a conference member.

4. The method according to claim 3, characterized in that The method further comprises: In a case where it is determined that the call role of the first electronic device in the first call is not a conference chairperson, the telephone conference session is saved.

5. The method according to claim 3, characterized in that: The method further comprises: Determine that the calling role of the first electronic device in the first call is the conference chairperson, or determine that the calling role of the first electronic device in the second call is the conference chairperson, and do not perform the steps of updating the second call based on the conference information, binding the telephone conference session with the second call, and creating a conference call for the telephone conference.

6. The method according to claim 1, characterized in that The requesting the conference server to merge the first call and the second call into a telephone conference, and receiving conference information of the telephone conference from the conference server, includes: Sending a call merging request to the conference server, wherein the call merging request is used to request the conference server to merge the first call and the second call into a telephone conference; The conference server receives conference information of the telephone conference returned after merging the first call and the second call into a telephone conference.

7. The method according to any one of claims 1 to 6, characterized in that: The method further comprises: Sending a conference subscription request to the conference server, wherein the conference subscription request is used to obtain participant information of the telephone conference from the conference server, wherein the participant information includes information of the second electronic device and information of the third electronic device; Receiving a conference subscription result from the conference server; 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 telephone conference; A first sub-call of the conference call is created according to the information of the second electronic device, and a second sub-call of the conference call is created according to the information of the third electronic device.

8. The method according to claim 7, characterized in that The method further comprises: A conference interface of the telephone conference is displayed, wherein 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; The processor, when executing the instructions in the memory, can enable the electronic device to execute the method for implementing a telephone conference as described in any one of claims 1 to 8.

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

Images