CN114449112B

CN114449112B - Prompting method for telephone conference, electronic equipment and storage medium

Info

Publication number: CN114449112B
Application number: CN202210362849.8A
Authority: CN
Inventors: 陈拴锋
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2022-04-08
Filing date: 2022-04-08
Publication date: 2023-06-16
Anticipated expiration: 2042-04-08
Also published as: CN114449112A

Abstract

The embodiment of the application provides a prompting method for a telephone conference, electronic equipment and a storage medium. By adopting the method in the embodiment of the application, the conference chairman equipment establishes a call with a plurality of call equipment, and in the process of inviting the plurality of call equipment to participate in the conference, the telephone number of each participant in the first notification message is determined and displayed according to the stored telephone number of each participant equipment. According to the reminding method of the telephone conference, the conference chairman equipment can accurately display the telephone number corresponding to each conference participant equipment in the telephone conference, and the use experience of using the telephone conference by the conference chairman user is improved.

Description

Prompting method for telephone conference, electronic equipment and storage medium

Technical Field

The present disclosure relates to the field of electronic devices, and in particular, to a method for reminding a conference call, an electronic device, and a storage medium.

Background

With the development of electronic technology, electronic devices (such as mobile phones, tablet computers or smart watches) have more and more functions. The plurality of electronic devices may establish a conference call for the plurality of electronic devices via a session initiation protocol (session initiation protocol, SIP). Taking a mobile phone as an example, a mobile phone a (may be referred to as a conference chairman device) may be in voice communication with a mobile phone B (may be referred to as a conference participant device B) and a mobile phone C (may be referred to as a conference participant device C), respectively, and the mobile phone a may establish a conference call of three mobile phones, that is, the mobile phone a, the mobile phone B, and the mobile phone C, based on SIP. After that, the mobile phone A, the mobile phone B and the mobile phone C can all carry out conference communication with other mobile phones through the telephone conference.

However, when the conference chairman device establishes a conference call, the telephone information of the participant device displayed in the display screen of the conference chairman device is inaccurate, for example, a "private number" is displayed in the display screen of the conference chairman device.

Disclosure of Invention

The embodiment of the application provides an optimized prompting method for a telephone conference, electronic equipment and a storage medium. According to the method, the conference chairman equipment can accurately display the telephone number corresponding to each conference participant equipment in the telephone conference, and the use experience of the conference chairman user in using the telephone conference is improved.

In a first aspect, an embodiment of the present application provides a method for reminding a conference call, which is applied to a conference chairman device, where the conference chairman device establishes a call with a plurality of call devices, and the conference chairman device invites the plurality of call devices to perform the conference call through a conference server, where the number of the call devices is at least 2; the method comprises the following steps: the conference chairman equipment receives a first notification message sent by a conference server, wherein the first notification message comprises the following components: the telephone number and the conference state of the presented conference participant equipment, the anonymous identification and the conference state of an anonymizer, wherein the conference state comprises a conference leaving state and a conference in state, the conference participant equipment is call equipment invited and added into a telephone conference, and the anonymizer is used for hiding the telephone number of the conference participant equipment; judging whether an anonymous person exists in the first notification message; if the anonymizer exists in the first notification message, acquiring the telephone number of the presented participant equipment from the first notification message and acquiring the stored telephone number of each participant equipment from the conference chairman equipment; determining a telephone number corresponding to an anonymizer in a first notification message according to the stored telephone number of each conferee device and the telephone number of the conferee device presented in the first notification message; if the success of the conference of the plurality of conference participant devices is detected, the telephone number corresponding to each conference participant device in the conference state is displayed in a display interface according to the telephone number corresponding to the anonymizer in the first notification message.

In this way, the chairman device establishes a call with a plurality of call devices and invites the plurality of call devices to conduct a teleconference. When the telephone conference is created, the telephone conference and a plurality of calls are bound, so that after the telephone conference is successfully created, the telephone numbers of all the participant devices are displayed to meet the requirement of a user for checking all the participant devices in the telephone conference. The conference chairman device stores telephone numbers of all the conference participant devices, after the conference chairman device receives the first notification message, even if the first notification message contains anonymizer, the conference chairman device can determine the telephone number corresponding to the anonymizer according to the stored telephone number of each conference participant and the telephone number presented (i.e. not anonymized) in the first notification message, so that the conference chairman device can display the telephone number of each conference participant device in a conference state in a display screen, thereby facilitating the conference chairman user to accurately know whether each conference participant is in the conference, and improving the use experience of the conference chairman user in using the conference.

According to a first aspect, a plurality of telephony devices includes: the first communication device and the second communication device; the method further includes, prior to retrieving the stored telephone number of each participant device from the chairman device: storing the telephone number of the first call device and the telephone number of the second call device under the condition that the conference chairman device establishes calls with a plurality of call devices; if the conference chairman equipment is detected to invite the first call equipment through the conference server, determining that the first call equipment is first participant equipment; and if the conference chairman equipment is detected to invite the second session equipment through the conference server, determining that the second session equipment is second participant equipment.

Thus, when the conference chairman device establishes a call, the telephone number of the corresponding call device is stored. And the conference chairman equipment determines each participant equipment added into the telephone conference in real time through the inviting operation, so that the accuracy of the stored telephone numbers of the participant equipment is improved, and the accuracy of the determined telephone numbers of the anonymizers is further improved.

According to a first aspect, the first notification message further comprises a telephone number of the conference chairman device and a conference status; obtaining the telephone number of the presented participant device from the first notification message, including: acquiring a stored telephone number of the conference chairman equipment; the telephone number of the conference chairman device and the anonymous identification of the anonymizer are removed from the first notification message, and the telephone number of the presented conference participant device is obtained.

In this way, the first notification message includes the telephone number and the conference state of the conference chairman device, the telephone number of the conference chairman device is removed from the first notification message, the telephone number of the currently presented conference participant device in the rest conference is removed, the accurate telephone information of the presented conference participant device is obtained, the interference of the telephone number of the conference chairman device in the first notification message on the telephone number of the determined anonymizer is reduced, and the speed of determining the telephone number of the anonymizer is improved.

According to a first aspect, if the first notification message includes a unique anonymizer, determining a phone number corresponding to the anonymizer in the first notification message according to the stored phone number of each participant device and the phone number of the participant device presented in the first notification message, including: and respectively matching the telephone numbers of the presented participant devices with the telephone numbers of each stored participant device, and acquiring the telephone numbers which are not matched from the telephone numbers of the stored participant devices as the telephone numbers corresponding to the anonymizers in the first notification message.

In this way, the conference chairman device stores the telephone numbers of the current various participant devices of the conference, the telephone numbers of the participant devices presented in the first notification message are respectively matched with the stored telephone numbers of each participant, and the telephone numbers which are not matched are the telephone numbers of the anonymizer.

According to a first aspect, the method further comprises: a first correspondence between anonymous identifications of anonymizers and corresponding phone numbers in a first notification message is stored. In this way, if the notification message for updating the meeting participant information is received subsequently, the phone number of the anonymizer can be determined based on the first corresponding relation, so that the situation that the phone number of the same anonymizer is repeatedly determined is avoided.

According to the first aspect, if the conference server detects that the conference participant device leaves the conference call, a second notification message is sent to the conference chairman device, wherein the second notification message comprises the telephone number and the conference state of the presented conference participant device, and the anonymous identification and the conference state of the anonymous participant; the anonymous identifier in the second notification message is the same as the anonymous identifier in the first notification message; the method further comprises the steps of: receiving a second notification message sent by the conference server; determining the telephone number of each participant device in the second notification message according to the first correspondence; determining the telephone number of the meeting participant equipment in the meeting leaving state in the second notification message according to the telephone number of each meeting participant equipment in the second notification message; the telephone number of the participant device in the away-from-meeting state is removed from the display interface.

Thus, when the conference participant equipment leaves the telephone conference, the conference server sends a second notification message to enable the conference chairman equipment to update the telephone numbers of the conference participant equipment in the online state in the display interface in time. Because the first notification message contains the unique anonymous person, and the anonymous identifier in the second notification message is the same as the anonymous identifier in the first notification message, that is, the conference chairman device can determine the telephone number of each participant device according to the first corresponding relationship and the second notification message. And determining the telephone number of the conference caller according to the conference state of each conference participant device in the second notification message. The conference chairman equipment removes the display interface from the conference leave equipment (namely the call equipment in the conference leave state) in time, so that the conference chairman user can see the information of the conference leave equipment in real time, and the use experience of the conference chairman user is improved.

According to a first aspect, before receiving the second notification message sent by the conference server, the method further comprises: responding to the jump operation of the chairman user, jumping to a detailed interface, wherein the detailed interface comprises options corresponding to each participant device, and the options corresponding to the participant device comprise the telephone number of the participant device and a hang-up control; in response to the chairman user clicking a hang-up control in an option corresponding to one or more participant devices, the call with the selected participant device is disconnected.

In this way, when the telephone numbers of the various participant devices and the corresponding hang-up controls are displayed on the conference chairman device, the conference chairman user can flexibly remove one or more (such as 2 or more) participant devices from the conference call.

According to a first aspect, the method further comprises: the conference chairman device responds to the operation of adding the call of the conference chairman user, and establishes a third call with a third call device, wherein the third call device is a call device except the plurality of call devices;

responding to the merging operation of the chairman user, and inviting the third session device to join the teleconference through the conference server by the chairman device; receiving a third notification message sent by the conference server, wherein the third notification message comprises the telephone number of the third communication device and an anonymous identifier in the first notification message; determining the telephone number of each meeting participant device in the current telephone conference according to the first corresponding relation and the third notification message; and displaying the telephone numbers corresponding to the meeting participant devices in the meeting state on a display interface.

In this way, after a plurality of meeting participant devices succeed in meeting, the conference chairman device can invite new call devices to meeting, and the conference server feeds back a third notification message, so that the conference chairman device can update the telephone number of the meeting participant device at present in time. The first corresponding relation is the corresponding relation between the telephone number of the anonymous person and the anonymous identifier in the first notification message, so that the conference chairman equipment can obtain and display the telephone number of each participant in the current telephone conference based on the first corresponding relation and the third notification message, and the telephone number of the anonymous person is prevented from being repeatedly determined.

According to a first aspect, if the first notification message includes a plurality of anonymizers, determining a phone number corresponding to the anonymizer in the first notification message according to the stored phone number of each participant device and the phone number of the participant device presented in the first notification message includes: acquiring a corresponding relation between a telephone number and an anonymous identifier of each anonymous person in a fourth known message, wherein the fourth known message is a notification message fed back by a conference server when calling equipment is invited to join a telephone conference last time, and the number of anonymous persons in the fourth known message is one less than that of anonymous persons in the first notification message;

And determining the telephone number corresponding to each anonymizer in the first notification message according to the corresponding relation between the telephone number of each anonymizer in the fourth notification message and the anonymizing identifier, the stored telephone number of each conferee device and the telephone number of the conferee device presented in the first notification message.

In this way, when the first notification message includes a plurality of anonymity people, the fourth notification message is the last call inviting device, and the notification message fed back by the conference server, that is, the phone number corresponding to each anonymity person in the first notification message is determined based on the last notification message, the stored phone numbers of the conference participant devices and the first notification message, so that even if a plurality of anonymity persons exist in the first notification message, the phone number of each anonymity person can be accurately determined, the conference participant can be accurately invited by the conference chairperson device, or the conference participant can be removed, and the use experience of the conference chairperson device for hosting the conference call is improved.

According to a first aspect, before the conference chairman device receives the first notification message sent by the conference server, the method further comprises: the conference chairman equipment invites the first call equipment to join the telephone conference to the conference server, and the conference server returns a fourth notification message to the conference chairman equipment; if the conference chairman equipment receives the fourth notification message, the conference server invites the second conference equipment to join the conference call, and the conference server returns the first notification message to the conference chairman equipment.

In this way, the conference chairman device only continues to invite the next call device when receiving the notification message returned by the last call device inviting, so that the conference chairman device can determine the anonymity person in the notification message based on the notification message received each time, and the phone number of each anonymity person can be determined accurately.

According to a first aspect, the method further comprises: storing a corresponding relation between the number of each anonymous person and the anonymous identifier in the first notification message; if the conference server detects that the conference participant equipment leaves the telephone conference, a fifth notification message is sent to the conference chairman equipment, wherein the fifth notification message comprises the telephone number and the conference state of each presented conference participant equipment, and the anonymous identification and the conference state of each anonymous person; the method further comprises the steps of: receiving a fifth notification message sent by the conference server; determining the telephone number of each participant device in the fifth notification message according to the corresponding relation between the number corresponding to each anonymizer in the first notification message and the anonymizing identifier; determining the telephone number of the meeting participant equipment in the meeting leaving state in the fifth notification message according to the telephone number of each meeting participant equipment in the fifth notification message; the telephone number of the participant device in the away-from-meeting state is removed from the display interface.

Therefore, as each anonymizer has a corresponding anonymous identifier, when meeting attendee equipment exists, the meeting chairman equipment can accurately determine the telephone number of the meeting attendee equipment, and further remove the telephone number of the meeting attendee equipment from the display screen, so that the telephone number of the meeting attendee equipment is kept accurate in real time.

According to a first aspect, detecting whether a plurality of participant devices are successful in a meeting, includes: receiving a first meeting invitation result returned by the meeting server, wherein the first meeting invitation result indicates that the first meeting participant equipment is successful in meeting; and receiving a second meeting invitation result returned by the meeting server, wherein the second meeting invitation result indicates that the second meeting participants are successful in meeting.

In this way, before the telephone conference is established, the conference chairman device establishes call connection with a plurality of call devices, the conference server invites the plurality of call devices to carry out the telephone conference, each call device in the plurality of call devices successfully carries out the conference, and then the conference success of the plurality of conference participant devices is determined, so that the situation that the number of the conference participant devices is displayed before the conference is successfully established is avoided, and the situation that the conference chairman user checks the telephone number of the conference participant devices is not met is avoided.

In a second aspect, an embodiment of the present application provides an electronic device, including: one or more processors; a memory;

and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the method of alerting teleconferences of the first aspect and any possible implementation of the first aspect.

In a third aspect, the present application provides a computer readable medium for storing a computer program comprising instructions for performing the method of the first aspect or any possible implementation of the first aspect.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a scenario illustrating an exemplary teleconference;

Fig. 2 is a schematic diagram of a structure of an exemplary wireless communication system;

FIG. 3 is a block diagram of a hardware architecture of an exemplary electronic device;

FIG. 4 is a schematic diagram illustrating interactions between devices when a method for reminding a conference call in the present application is performed;

FIG. 5 is a flow chart illustrating an exemplary process for determining a number corresponding to an anonymizer;

FIG. 6 is a schematic diagram of a scenario illustrating a reminder for a teleconference;

FIG. 7 is a schematic diagram illustrating interactions between devices when another exemplary method for reminding a conference call according to the present application is performed;

fig. 8 is a schematic view of a scenario illustrating an exemplary method of alerting the teleconference performed during a teleconference call;

FIG. 9 is a schematic diagram illustrating interactions between devices when another exemplary method for reminding a conference call according to the present application is performed;

FIG. 10 is a schematic diagram illustrating interactions between devices when another exemplary method for alerting a conference call of the present application is performed;

fig. 11 is a schematic diagram of an exemplary scenario in which a participant device actively leaves a teleconference;

fig. 12 is a schematic diagram of an exemplary scenario in which a chairman user removes a participant device from a teleconference.

Detailed Description

The following description of the embodiments of the present application will be made clearly and fully with reference to the accompanying drawings, in which it is evident that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

Fig. 1 is a schematic view of a scenario illustrating a teleconference.

In one embodiment, user A (who acts as a chairman user) wants to conduct a teleconference with user B and user C. Fig. 1 shows a display screen of a device of a user a, a display interface of a call between a mobile phone a (the device of the user a) and a mobile phone B (the device of the user B) is shown as 1a in fig. 1, and a call interface 10 displays phone information 11 of the user B, where the phone information 11 includes a phone number of the user B (i.e., 86 xxxxxxxx 1) and a call duration (e.g., 4 seconds shown in reference numeral 11). Other functionality controls are included in the call interface 10, such as a recording control, a waiting for call control, a call adding control 12, a video call control, a mute control, and a contact list control, etc., as shown in the call interface 10. The recording control is used for triggering recording of call content; the control waiting for the call is used for triggering the change of the current call state to the hold state. The control of the video call is used for triggering and opening a camera of the current equipment and shooting; the mute control is used for triggering the silencing operation on the call; the contact list control is used to trigger an interface to jump to the contact list. The add call control 12 is used to trigger the addition of other calls in the current call. In this example, as shown in fig. 1a, the user a may click on the call adding control 12, and trigger to jump to the dial interface after clicking on the call adding control 12, so that the mobile phone a establishes a call with a call device other than the mobile phone B; the dial-up interface may include, among other things, a contact list and/or a dial-up keypad (the dial-up interface is not shown in fig. 1). Handset a dials the number of user C (i.e., 86XXXXXXX 2) and establishes a call with handset C (the device of user C), as shown in fig. 1B, in call interface 13, the call between handset a and handset B is maintained (i.e., in hold state), and the call between handset a and handset C is in active state. The call interface 13 in 1B further includes a call combining control 14, and after the user clicks the call combining control 14, the mobile phone a may establish a conference call between the mobile phone a, the mobile phone B and the mobile phone C based on SIP, as shown in fig. 1C. The conference call interface in 1c displays the conference call information (e.g., private number; 86 xxxxxxxx 1), the number of participants (e.g., 2), and the call duration (e.g., 24 seconds). The teleconference interface also includes a detail control 15, and user a clicks the detail control 15 to jump to the detail interface of the meeting information, as shown in fig. 1 d. In this 1d, the detailed interface of the conference information is displayed with a private number and "86xxxxx 1".

In the teleconference, the telephone number of the conferee device displayed in the display screen of the conference chairman device is completely dependent on the information of the conferees in the network notification (namely, a Notify message), the information of the conferees in the notification message is provided with anonymity, if the information of the conferees in the network notification is completely displayed according to the information of the conferees in the network notification, when the network is abnormal and the notification message is provided with anonymity, the display screen of the conference chairman device is provided with anonymity. In this example, when the meeting participant information carried in the Notify message contains anonymous information, the Notify message is shaped as:

<user entity="sip:+86XXXXXXX0@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>connected</status>

<user entity="sip:+86XXXXXXX1@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>connected</status>

<user entity="sip:anonymousA@anonymous.invalid" state="full"><status>connected</status>

in the notification message, the first number is "86XXXXXXX0", the state in the teleconference is a conference state (i.e., connected state), the second number is "86XXXXXXX1", and the state in the teleconference is a conference state (i.e., connected state). The third number is hidden (i.e., anonymized) to identify the third number as "anonymousA". When the mobile phone a receives the notification message, if "anonymousA" is detected, the "private number" is displayed in the display. The manner that the mobile phone A displays the phone information of the participants in the Notify message completely reduces the conference use experience of the user.

The method for reminding the telephone conference is executed by the electronic equipment, so that the electronic equipment can accurately display the number corresponding to each participant equipment, and the experience of using the telephone conference by the chairman user is improved.

First, a wireless communication system in which the embodiments of the present application can be applied will be described with reference to fig. 2. Fig. 2 is a schematic diagram of a wireless communication system in which embodiments of the present application may be applied. The wireless communication system may be LTE, a 5G wireless communication system, or a new communication system that is developed in future wireless communication. The wireless communication system may apply the embodiments of the present application as long as the wireless communication system employs IMS as a voice implementation.

As shown in fig. 2, the wireless communication system includes a UE201a, a UE201b, a UE201c, an access network device 202 providing the UE201a with an LTE network, an access network device 203 providing the UE201b, the UE201c with a 5G network, a core network device 204, and an Internet-protocol multimedia subsystem (Internet-protocol Multimedia Subsystem, IMS) 205. Wherein UE201a may be a calling UE, UE201b and UE201c may be a called UE. In some examples, the access network device 202, the access network device 203, the core network device 204, and the IMS205 may also be collectively referred to as a Network (NW).

The IMS205 may include Proxy-Call Session Control Function, P-CSCF, entities, query-Call Session Call Session Control Function, I-CSCF, serving-Call Session Control Function, S-CSCF, and Home subscriber Server (Home Subscriber Server, HSS).

The P-CSCF entity is the first attachment point of the access network to the IMS, and all session messages originating from and terminating at IMS-enabled UEs are forwarded by the P-CSCF entity. The P-CSCF entity may be used to forward IMS registration requests from the UE to the S-CSCF entity and to forward registration response information to the UE.

The I-CSCF entity may connect the S-CSCF entity and the P-CSCF entity for providing access to the home network for the UE. In the IMS registration process, the P-CSCF entity may forward an IMS registration request from the UE to the I-CSCF entity, which may query the HSS in the IMS, selecting one S-CSCF entity for the UE. In the calling process, the calling message to the IMS network is firstly routed to the I-CSCF, the I-CSCF entity can inquire the address information of the S-CSCF entity registered by the user for the UE through the HSS in the IMS, and then the message is routed to the S-CSCF.

The S-CSCF entity is a control core of the IMS and provides session control, registration and other functions for the UE. The S-CSCF entity is used for receiving the IMS registration request forwarded by the P-CSCF entity and authenticating the UE by matching with the HSS. After determining that authentication is passed, S-CSCF obtains subscription information of UE from HSS. The S-CSCF entity is also used for connecting with each application server based on the ISC interface, and the S-CSCF entity is also used for triggering the application server to execute operation and routing the request of the UE to the corresponding application server.

The HSS is used to store all subscriber and service related data such as subscriber identity, subscription information, access information, etc.

It should be appreciated that while the wireless communication system shown in fig. 2 includes only 3 UEs, one access network device 202, and one access network device 203, the wireless communication system may include fewer and/or more UEs, and/or more access network devices. The wireless communication system may further comprise an access network device providing a 4G/5G network for the UE201 a. The wireless communication system may also include access network devices that provide LTE networks for UE201 b and UE201 c.

In the embodiment of the present application, the UE201 may be any terminal capable of communicating with another terminal through a wireless communication network (e.g., a 5G network and an IMS). The UE201 may be a cell phone, a tablet computer, a computer with wireless transceiver function, a virtual reality device, an augmented reality device, a wireless device in industrial control, a wireless device in unmanned, a wireless device in telemedicine, a wireless device in smart grid, a wireless device in transportation security, a wireless device in smart city, a wireless device in smart home, a smart wearable device (e.g., smart watch), etc.

Fig. 3 is a schematic diagram of a hardware structure of a UE201 (i.e., an electronic device 201) according to an embodiment of the present application. As shown in fig. 3, the electronic device 201 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (universal serial bus, USB) interface 130, a charge management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, keys 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identity module (subscriber identification module, SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyro sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

The processor 110 may include one or more processing units, such as: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

In this embodiment, the processor 110 may determine, according to the stored phone numbers and phone information of each of the meeting device in the notification message, a phone number corresponding to an anonymizer in the notification message, where the anonymizer may be the anonymized phone information.

The wireless communication function of the electronic device 201 can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, a modem processor, a baseband processor, and the like.

The mobile communication module 150 may provide a solution for wireless communication including 2G/3G/4G/5G, etc. applied on the electronic device 201. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be provided in the same device as at least some of the modules of the processor 110.

The SIM card interface 195 is used to connect a SIM card. The SIM card may be brought into and out of contact with the electronic device 201 by inserting the SIM card interface 195, or by extracting it from the SIM card interface 195. The electronic device 201 may support 1 or N SIM card interfaces, N being a positive integer greater than 1. The electronic device 201 interacts with the network through the SIM card to realize functions such as communication and data communication.

In this embodiment, the electronic device 201 may establish a call with other call devices and conduct a conference call through the SIM card and the mobile communication module 150.

Fig. 4 is a schematic diagram illustrating interactions between devices when a method for reminding a teleconference in the present application is performed. Fig. 5 is a schematic diagram exemplarily showing a determination of a number corresponding to an anonymizer, and fig. 6 is a scene schematic diagram exemplarily showing a reminder of the teleconference. In this example, the calling user (user a) device is taken as UEA, the called device is taken as UEB and UEC as examples, that is, the UEA is taken as a chairman device, and the UEB and the UEC may be taken as participant devices. Alternatively, in this example, the participant device may be a telephony device joining the conference and not be a chairman device. The following describes the reminding method of the teleconference specifically with reference to fig. 4, 5 and 6:

step 401: ue a establishes a call with ue b.

Illustratively, a user a (a chairman user) may perform a dialing operation through a dialing interface of a mobile phone a (UEA), and the chairman device establishes a call through a conference server (i.e., IMS) and a participant device B (i.e., UEB) in response to the dialing operation of the chairman user. As shown in fig. 6a, the call interface 601 displays phone information 603 of the mobile phone B (i.e., UEB), where the phone information 603 includes the phone number of the mobile phone B and the call duration.

Step 402: the UEA establishes a call with the UEC.

Illustratively, a call between a chairman device (i.e., UEA) and a participant device C (i.e., UEC) may be established in response to a user a adding user C. The operation of adding the user C may be an operation of clicking the add call control 602 as shown in fig. 6 a.

After the ue a establishes a call with the UEC, the call between the ue a and the ue b is in a hold state, as shown in fig. 6b, in which the call in option 606 is in a hold state, and in which the call in option 605 is in a conference state.

Step 403: the UEA creates a conference.

Illustratively, the meeting chairman user clicks the merge control, and the meeting chairman device creates the meeting in response to the operation of the meeting chairman user clicking the merge control (e.g., control 607 in 6b of FIG. 6). Specifically, the chairman device may initiate a conference setup request to a conference server (i.e., IMS) through an INVITE message. After the conference is established successfully, the conference chairman device can continue to subscribe to the conference state with the conference server to alter and invite the conference participant device to join the conference.

It should be noted that, for a description of a method for creating a conference between a chairman device and a conference server, reference may be made to a method for creating a conference between an electronic device and a conference server in a conventional technology, which is not described herein.

Step 404: UEA subscribes to conference status.

For example, after a chairman device establishes a connection with a conference server, creating a conference, the chairman device may subscribe to the conference server for conference status. I.e. the chairman device initiates a subscription request to the conference server, which may return a 200 OK message in response to the subscription request, after successful subscription to the conference server.

Step 405: the conference server sends a notification message (notify_1) to the UEA.

Illustratively, the conference server sends a Notify message to the conference chairman device (i.e., UEA) that is used to inform the conference chairman device to update the current state of the participant device. The notification message includes at least: the phone number of the chairman device and the connection status (e.g., connected status), which may also be referred to as a conference status.

For example, the notify_1 shape is as follows:

<user entity="sip:+86XXXXXXX0@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>connected</status>；

the conference chairman device can know from notify_1, and the current teleconference only comprises the conference chairman device.

Step 406: the chairman device UEA invites UEB to a conference.

Illustratively, the chairman device sends a message to the conference server inviting the UEB to participate in the conference, e.g. a Refer message.

Step 407: the conference server transmits a conference invite request message to the UEB.

Illustratively, the conference server sends a conference INVITE request message, which may be an INVITE message, to the UEB in response to a message sent by the chairman device inviting the UEB to conference.

Step 408: the UEB returns a response message to the conference server.

Illustratively, the UEB returns a response message, such as a 200 OK message, to the conference server.

Step 409: the conference server transmits a notification message (notify_2) to the UEA for notifying the conference invitation result.

Illustratively, the conference server may send a notification message to the chairman device upon receiving the 200 OK message returned by the UEB. The notification message (notify_2) is used to Notify the chairman device of the meeting invitation result. If the conference server receives the 200 OK message returned by the UEB, the notification message returned by the conference server indicates that the conference invitation was successful.

In this example, different labels (e.g., notify_1, notify_2, etc.) of notification messages are used to distinguish between the respective notification messages and are not used to limit the type of notification message.

After the meeting invitation is successful, the meeting server may send a notification message (notify_4) indicating the meeting participant information to the chairman device. The chairman device may continue to invite other devices to the conference server for conference before receiving the notification message (Notify _ 4). And the conference server sequentially sends notification messages for updating the participant information to the conference chairman equipment according to the time sequence of the invitations. For example, the chairman device (UEA) sends a message inviting UEB to conference to the conference server at time t1, sends a message inviting UEC to conference to the conference server at time t2, wherein time t1 is earlier than time t2, the conference server returns a notification message (notify_4) for updating the participant information UEB to the UEA at time t3, and the conference server returns a notification message (notify_5) for updating the participant information UEC to the UEA at time t 4.

It should be noted that, before IR92 13.0, the protocol does not explicitly specify that the UEA must receive the notification message (notify_4) before it can continue to invite the next participant. After IR 92.13.0, section 2.3.3 of the conference in the protocol specifies that the UEA must receive a notification message (notify_4) before it can continue to invite the next participant. If the protocol of IR 92.13.0 is adopted, the UEA, after receiving the notification message (notify_4), invites the conference server to join the conference.

In this example, taking the example of the UEA inviting the conference server to a UEC for a conference before receiving a notification message that the conference server returns for updating the conference participant information.

Step 410: the UEA invites the conference server to the UEC for the conference.

For example, when the chairman device determines that the conference invitation to UEB is successful, a message may be sent to the conference server inviting UEC to participate. The conferred message may be a Refer message.

Step 411: the conference server sends a conference invite request message to the UEC.

Illustratively, the conference server sends a conference INVITE request message, which may be an INVITE message, to the UEC in response to a message sent by the chairman device inviting the UEC to conference.

Step 412: the UEC returns a response message to the conference server.

Illustratively, upon receiving the INVITE message, the UEC may return a response message, such as a return 200 OK message, to the conference server.

Step 413: the conference server transmits a notification message (notify_3) to the UEA for notifying the conference invitation result.

Illustratively, similar to step 409, the conference server may send a notification message (notify_3) to the chairman device after receiving the response message returned by the UEC, the notification message (notify_3) indicating that the conference invitation was successful.

Step 414: the conference server sends a notification message (notify_4) to the UEA to update the meeting participant information.

Illustratively, after returning the conference invitation result to the UEA, the conference server may send a notification message (notify_4) to the UEA, the notification message (notify_4) carrying information of each participant, the information of the participant including: telephone numbers corresponding to the participant devices. Note that, since the notification message (notify_4) corresponds to successful participation of the inviting UEB, at this time, the UEA has not initiated the conference invitation to the UEC to the conference server, and the notification message (notify_4) does not include the information of the UEC. The UEA may obtain information of the current participant from the notification message.

Step 415: the IMS sends a notification message (notify_5) to the UEA to update the conference participant information.

Illustratively, after the conference server returns the conference invitation result for inviting the UEC to conference to the UEA, similar to step 414, if the conference server determines that the conference invitation result indicates that the conference invitation is successful, a new notification message (notify_5) may be sent to the UEA for the UEA to update new participant information.

In this example, since the ue a invites UEB earlier than UEC, the notification message (notify_5) will contain information about each participant, i.e. the notification message (notify_5) contains the telephone numbers of UEB, UEC and UEA.

Step 416: the UEA determines the number corresponding to the anonymizer and displays the number of each participant.

Illustratively, the Notify message may contain anonymous number information, also in random numbers. Alternatively, in this example, a number corresponding to one participant is randomly hidden.

The process of determining the number corresponding to the anonymizer is described in detail below in conjunction with fig. 5:

step 4161: the UEA determines whether an anonymous is present in the notification message. If the UEA determines that the anonymous exists in the notification message, then step 4162 is performed; if the UEA determines that no anonymizer exists in the notification message, step 4163 is directly performed.

Illustratively, the UEA may determine whether an anonymous is present in the notification message by an anonymous identifier, which may be "anonymous", for example. If the UEA queries that no anonymous identifier exists in the notification message, it determines that no anonymous person exists in the notification message, step 4163 may be performed.

For example, the UEA receives the notification message (i.e., notify_4) at time t3, and the UEA determines that there is participant information in the notify_4. The UEA continues to determine if an anonymous identification ("anonymous") exists in the notify_4. Notify4 forms such as:

the ue a queries that "anonymous" does not exist in the Notify4 message, i.e., the ue a determines that no anonymizer exists in the notify_4 message, step 4163 is performed.

The UEA receives the notification message (i.e. notify_5) at time t 4. The UEA continues to determine if an anonymous identification ("anonymous") exists in the notify_5. Notify_5 is shaped as:

the ue a queries that "anonymous" exists in the notify_5 message, i.e., the ue a determines that an anonymity exists in the notify_5 message, step 4162 is performed.

Step 4162: the UEA determines the number corresponding to the anonymizer according to the stored number of the conferee.

Illustratively, the UEA may store a telephone number corresponding to the participant device when establishing a call with the participant device. For example, after a UEA establishes a call with a UEB, the telephone number of the UEB may be stored. Similarly, the UEA establishes a call with the UEC, and may store the telephone number of the UEC. Optionally, the UEA may also update the phone number corresponding to the participant device locally when the participant device is invited to participate in or removed from the participant device.

The UEA may determine the number corresponding to the anonymizer according to the number corresponding to each participant in the notification message and the stored number of the participant. Specifically, the UEA may obtain numbers of participants from the notification message, compare the obtained numbers with each of the stored participant numbers, and obtain non-matched phone numbers from the stored participant numbers. The UEA takes the obtained unmatched telephone number as the number corresponding to the anonymizer.

For example, the UEA stores the telephone numbers of the respective participants when establishing a call with the participants. In this example, the UEA stores the telephone number of the UEA as "86XXXXXXX0", the telephone number of the UEB as "86XXXXXXX1", and the telephone number of the UEC as "86XXXXXXX2", respectively.

The UEA receives the notification message (i.e., notify_5) at time t4, and the UEA determines that there is participant information in this notify_5. The UEA continues to determine if an anonymous identification ("anonymous") exists in the notify_5. Notify_5 is shaped as:

the UEA queries that "anonymous" exists in the notify_5 message, i.e., the UEA determines that an anonymizer exists in the notify_5 message. The UEA may determine, according to the conference invitation result, that the phone number of each participant is: 86XXXXXXX0, 86XXXXXXX1, and 86XXXXXXX2. The telephone numbers acquired by the UEA from the notify_5 are respectively: 86XXXXXXX0, 86XXXXXXX1, and anonymousA. The ue a compares the acquired phone numbers with the stored phone numbers, respectively, and if the 86 xxxxxxxx 2 stored in the ue a is not matched, the ue a determines that the number corresponding to the anonymizer is 86 xxxxxxxx 2.

Step 4163: the UEA displays the number of each participant.

Illustratively, the UEA determines the number corresponding to the anonymizer and the number corresponding to the conference chairman device, i.e. according to the conference status of each telephone number, the telephone number of each conference participant in the conference status is displayed in the display. For example, as shown in 6c of fig. 6, telephone information 609 is displayed in the teleconference interface 608, and the telephone information 609 includes a telephone number of each participant (e.g., 86 xxxxxxxx 1, 86XXXXXXX 2), the number of participants (e.g., 2), and a conference duration (e.g., 24 seconds). The teleconference interface 608 also includes a detail control 610, which user a clicks on, jumping to the detail interface 611 of the meeting information, as shown in fig. 6 d. In the 6d, the telephone number of each participant is displayed in the detailed interface 611 of the conference information, which is 86 xxxxxxxx 1;86XXXXXXX2.

In this example, the conference chairman device stores the phone numbers of each participant, after the conference chairman device receives the notification message, even if the notification message contains an anonymizer, the conference chairman device can determine the number corresponding to the anonymizer according to the stored phone number of each participant and the phone number which is not anonymized in the notification message, so that the conference chairman device can display the number of each participant in the display screen, thereby facilitating the conference chairman user to accurately know whether each participant is in the conference, and improving the use experience of the conference chairman user in using the teleconference.

Fig. 7 is a schematic diagram illustrating interactions between devices when a reminding method of a teleconference of the present application is performed. Fig. 8 is a schematic view of a scenario in which the present example performs a reminding method of a teleconference during a teleconference call, which is exemplarily shown. In this example, with the calling user (user a) device as the UEA, the UEA establishes a call with the UEB and the UEC, respectively, and the UEA, the UEB, and the UEC establish a teleconference, during which the UEA may also invite a new UE to join the teleconference, a procedure of a prompting method of the teleconference is described below with reference to fig. 7 and 8:

step 701: ue a establishes a call with ue b.

Step 702: the UEA establishes a call with the UEC.

Step 703: the UEA creates a conference.

Step 704: the UEA subscribes to the conference state with the conference server.

Step 705: the conference server returns a notification message (notify_6) to the UEA.

Step 706: the UEA invites the conference server to the UEB for the conference.

Step 707: the conference server transmits a conference invite request message to the UEB.

Step 708: the UEB returns a response message to the conference server.

Step 709: the conference server transmits a notification message (notify_7) to the UEA for notifying the conference invitation result.

Step 710: the UEA invites the conference server to the UEC for the conference.

Step 711: the conference server sends a conference invite request message to the UEC.

Step 712: the UEC returns a response message to the conference server.

Step 713: the conference server transmits a notification message (notify_8) to the UEA to Notify the conference invitation result.

Step 714: the conference server sends a notification message (notify_9) to the UEA to update the meeting participant information.

Step 715: the conference server transmits a notification message (notify_10) to the UEA to update the meeting participant information.

Step 716: the UEA determines the number corresponding to the anonymizer and displays the number of each participant.

In this example, the process types of steps 701-716 and steps 401-416 may refer to the descriptions of steps 401-416 in the relevant descriptions of steps 701-716, and will not be described herein. The UEA displays the number of each participant and as shown in 8a of fig. 8, the teleconference interface 801 displays telephone information 802 (including telephone numbers 86 xxxxxxxx 1 and 86 xxxxxxxx 2).

Step 717: the UEA establishes a call with the UEN.

Illustratively, the chairman device may add a new participant device (e.g., a UEN) during the talk period of the teleconference. Alternatively, as shown in 8a of fig. 8, the chairman user may click on the "add call" control 803 on the UEA's teleconference interface 801. The UEA responds to the call adding operation of the user, jumps to a dialing interface or a contact list interface, and the user A can input the telephone number of the equipment to be added through the dialing interface or can input the telephone number of the equipment to be added through clicking the contact. The UEA responds to the operation of dialing the UEN by the user A, and establishes the conversation between the UEA and the UEN.

It should be noted that, for a description of a method for establishing a call between a chairman device and a participant device, reference may be made to a method for performing voice communication between an electronic device and another electronic device in a conventional technology, which is not described herein.

Step 718: the UEA merges the conferences, inviting the UEN to the conference.

Illustratively, after the chairman device establishes a call with the ue n, as shown in 8b of fig. 8, the call between the ue a and the ue n in the display interface 804 is in a meeting state (i.e., active state), as shown in option 805. The call between UEA and UEC is maintained (i.e., hold state) as shown in option 806. The call between UEA and UEB will be maintained (i.e., hold state) as shown in option 807. The display interface 804 also displays a merge control 808 for merging calls. The chairman user clicks the merge control 808 and in response thereto the chairman device merges the call with the UEN (as indicated at 805) into a conference call, alternatively the UEA may send a Refer message inviting the UEN to a conference.

Step 719: the conference server sends a conference invite request message to the UEN.

This step is similar to step 407, and the description of the step 407 may be referred to, and will not be repeated here.

Step 720: the UEN returns a response message to the conference server.

This step is similar to step 408, and the description will be referred to in step 408, and will not be repeated here.

Step 721: the conference server transmits a notification message (notify_11) to the UEA to Notify the conference invitation result.

Illustratively, upon receiving a response message returned by the UEN, the conference server may send a notification message (notify_11) to the UEA, where the notification message (notify_11) is used to Notify the conference invitation result, e.g., the conference invitation result indicates that the UEN is invited to a successful conference.

Step 722: the conference server sends a notification message (notify_12) to the UEA to update the meeting participant information.

Illustratively, the conference server may send a notification message (notify_12) to the UEA, which carries information for each participant, and upon receipt of which notification message (notify_12) the UEA may update the participant information, wherein the participant may be used to instruct the participant device.

Step 723: the UEA determines the number corresponding to the anonymizer and displays the number of each participant.

Illustratively, the UEA may determine the anonymizer's information based on the stored phone number and the received notification message (notify_12). The UEA determines that the anonymizer corresponds to a number similar to step 416.

For example, the UEA stores the telephone numbers of the respective participants when establishing a call with the participants. In this example, the UEA stores the telephone number of the UEA as "86XXXXXXX0", the telephone number of the UEB as "86XXXXXXX1", and the telephone number of the UEC as "86XXXXXXX2", respectively. The conference server sends a Notify message to the UEA, which receives the notification message (i.e., notify_10) at time t6, and determines that there is participant information in this notify_10. The UEA continues to determine if an anonymous identification ("anonymous") exists in the notify_10. Notify_10 is shaped as:

<user entity="sip:+86XXXXXXX2@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>connected</status>

the UEA inquires that "anonymous" does not exist in the notify_10 message, and the UEA directly displays the telephone number of each participant.

UEA establishes a call with UEN during a teleconference call. The UEA may store the telephone number of the UEN (e.g., 86 XXXXXXXN) during the establishment of the call. After the UEA establishes a call with the UEN, the UEA merges the conference and invites the UEN to participate in the conference.

After the ue n and the session, the session server notifies the ue a of the notify_12 message, and the ue a receives the notify_12 message at time t 7. The UEA determines that participant information exists in the notify_12. The UEA continues to determine if an anonymous identification ("anonymous") exists in the notify_12. Notify_12 message is shaped as:

<user entity="sip:+86XXXXXXX2@ims.mncXXX.mccXXX.3gppnetwork.org " state="full"><status>connected</status>

The UEA determines that an anonymity exists in the notify_12 message. The UEA may determine, according to the conference invitation result, that the phone number of each participant is: 86XXXXXXX1, 86XXXXXXX2, and 86 XXXXXXXXXN. The telephone numbers acquired by the UEA from the notify_12 are respectively: 86XXXXXXX0, 86XXXXXXX1, 86XXXXXXX2, and anonymousA. The ue a compares the acquired phone numbers with stored phone numbers, respectively, where the stored phone includes a phone of a chairman device and a phone of each participant, and the ue a may determine that the stored 86 xxxxxxxxn is not matched, and determine that the number corresponding to the anonymizer is 86 xxxxxxxxn.

The UEA may display the telephone numbers of the individual participants in a display screen, as shown in 8c of fig. 8, with telephone information 811 in a teleconference interface 809, i.e. "86XXXXXXX1, +86 XXXXXXX2 and 86XXXXXXXN". The chairman user clicks the detailed control 810 and jumps to the display interface 812 where the numbers of the individual participants and the hang-up control corresponding to each number are displayed, and the chairman user can remove the corresponding participant device by clicking the hang-up control.

It should be noted that, during the teleconference, if the participant device changes in the teleconference (for example, there is a newly added participant device in the teleconference), the conference chairman device displays the phone number of each participant currently in the conference according to the newly received notification message.

In this example, during the teleconference call, the conference chairman device may add a new participant device, and according to the notification message and the stored phone number, the conference chairman device may still accurately determine the number corresponding to the anonymous person, so that the conference chairman device may accurately display the number of the current participant whenever, so that the user of the conference chairman device may learn the information of each participant.

In some embodiments, the UEA may also determine the phone number corresponding to the anonymizer if there are participants actively away from the conference.

For example, the meeting participants leave the meeting, and the UEA receives a Notify message in the form of:

<user entity="sip:+86XXXXXXX1@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>disconnected</status>

the UEA determines that an anonymous person is present in the Notify message. The UEA may determine, according to the conference invitation result, that the phone number of each participant is: 86XXXXXXX1, 86XXXXXXX2, and 86 XXXXXXXXXN. The telephone numbers acquired by the UEA from the Notify are respectively: 86XXXXXXX0, 86XXXXXXX1, 86XXXXXXX2, and anonymousA. The ue a compares the acquired phone numbers with stored phone numbers, respectively, where the stored phone includes a phone of a chairman device and a phone of each participant, and the ue a may determine that the stored 86 xxxxxxxxn is not matched, and determine that the number corresponding to the anonymizer is 86 xxxxxxxxn. The ue a may also determine that the number corresponding to the conference leaving device is 86 xxxxxxxx 1 from the Notify, and the ue a may display the phone numbers of the conference participants currently in each conference in the display screen, that is, "86 xxxxxxxx 2 and 86XXXXXXXN".

In this example, whether there are meeting participants leaving the meeting or not, the conference chairman device can accurately determine the number corresponding to the anonymizer, and the experience of the conference chairman device in use is improved.

In one embodiment, if a plurality of anonymizers exist in the notification message, a method for reminding a teleconference as shown in fig. 9 may be adopted, and the specific procedure of the method for reminding a teleconference is as follows:

step 901: ue a establishes a call with ue b.

Step 902: the UEA establishes a call with the UEC.

Step 903: the UEA creates a conference.

Step 904: the UEA subscribes to the conference state with the conference server.

Step 905: the conference server sends a notification message (notify_13) to the UEA.

Step 906: the UEA invites the conference server to the UEB for the conference.

Step 907: the conference server transmits a conference invite request message to the UEB.

Step 908: the UEB returns a response message to the conference server.

Step 909: the conference server transmits a notification message (notify_14) to the UEA to Notify the conference invitation result.

In this example, the descriptions of steps 901 to 909 are similar to steps 401 to 409, and reference may be made to the descriptions of steps 401 to 409, and will not be repeated here.

Step 910: the conference server sends a notification message (notify_15) to the UEA to update the meeting participant information.

Illustratively, IR92 13.0 and subsequent agreements indicate that the conference chairman device has subscribed to the conference state, the UE must wait for a relevant SIP notification confirming the conference state of the last invited conference participant before inviting a new conference participant. In this example, the conference server transmits a notification message (notify_14) to the UEA to Notify the conference invitation result, and then the conference server transmits a notification message (notify_15) to the UEA. The notification message (notify_14) indicates that the invitation to the UEB was successful, and the notification message (notify_15) carries the participant information for the UEA to update the participant information.

After receiving the notification message (notify_15), the UEA determines whether or not an anonymous exists in the notification message (notify_15); if the UEA determines that the anonymity exists in the notification message, then the number corresponding to the anonymity is determined according to the stored number of the conferee, i.e. step 911 is performed. If the UEA determines that no anonymizer is present in the notification message, step 912 is performed.

Step 911: the UEA determines the number corresponding to the anonymizer.

Illustratively, the UEA may obtain numbers of the participants from the notification message, compare the obtained numbers with each of the stored participant numbers, and obtain non-matched telephone numbers from the stored participant numbers. The UEA takes the obtained unmatched telephone number as the number corresponding to the anonymizer.

For example, the UEA stores the telephone numbers of the respective participants when establishing a call with the participants. In this example of the present invention,

when a UEA (e.g., having a telephone number of "86xxxxxx 0") establishes a call with a UEB (e.g., having a telephone number of "86XXXXXXX 1"), the telephone number of the UEB is stored. When the UEA invites the UEB to participate in the conference, it may be confirmed that the participant includes the telephone number of the UEB, that is, after the UEA successfully invites the UEB to the IMS, the UEA determines that the UEB is a participant, and a correspondence between the UEB and the participant may be established (i.e., the UEA determines that the UEB is a participant device).

When the UEA receives a notification message (e.g., notify_15) for updating the meeting participant information, and determines that the notification message (notify_15) contains an anonymizer, the notify_15 is shaped as:

the UEA obtains the number of the participant and the telephone number of the chairman device from the notify_15 message. Since the UEA stores its own telephone number (i.e., 86XXXXXXX 0) and stores the correspondence between UEB and participants, the UEA can determine the number corresponding to anonymousA as UEB, i.e., the UEA can determine that the number corresponding to anonymousA is "86XXXXXXX1". The UEA stores the correspondence between "anonymousA" and "86XXXXXXX1".

It should be noted that, in this example, the UEA establishes a call with the UEB and the UEC before creating the conference, so when the UEA detects that both the UEB and the UEC are successful in conference, it is determined that the current conference call is established successfully. If the UEA does not detect that both UEB and UEC are participating, the UEA determines that the conference has not been successfully established, at which time the UEA does not display the telephone number of the participant in real time, as in step 911, the UEA performs the step of determining the number of the anonymous party, but does not perform the step of displaying the telephone number of the participant.

Step 912: the UEA invites the conference server to the UEC for the conference.

Illustratively, the UEA invites the UEC to participate after receiving a notification message updating the participant information. The procedure for inviting the UEC to participate is similar to step 410 and will not be described in detail here.

Step 913: the conference server sends a conference invite request message to the UEC.

This step is similar to step 411, and the relevant description may refer to the content of step 411, and will not be described here again.

Step 914: the UEC returns a response message to the conference server.

This step is similar to step 412, and the description of this step may refer to the description of step 412, and will not be repeated here.

Step 915: the conference server transmits a notification message (notify_16) to the UEA to Notify the conference invitation result.

Illustratively, the conference server may feed back an invitation result for inviting the UEC to participate to the UEA through the notification message (notify_16). This step is similar to step 409, and the description of the relevant step 409 may be referred to, and will not be repeated here.

Step 916: the conference server sends a notification message (notify_17) to the UEA to update the meeting participant information.

Illustratively, upon receiving the notification message (notify_17), the UEA determines whether an anonymous is present in the notification message (notify_17). If the UEA determines that the anonymity exists in the notification message, step 917 is performed by determining, according to the stored number of the conferee, the number corresponding to the anonymity. If the UEA determines that the anonymizer does not exist in the notification message, the telephone number of each conferee is directly displayed.

Step 917: the UEA determines the number corresponding to the anonymizer and displays the number of each participant.

Illustratively, there are a plurality of (e.g., 2) anonymizers in the notification message (notify_17) sent by the conference server, and the UEA may determine the number corresponding to the anonymizer not determined in the notification message (notify_17) according to the stored phone number of the conferee and the number corresponding to the anonymizer determined in step 911. Specifically, the UEA may obtain the phone numbers of all participants, and obtain the correspondence between the anonymizer and the phone numbers stored in step 911; the corresponding telephone number of the anonymous person that is not determined in the notification message (notify_17) can be determined.

For example, when a UEA (e.g., having a telephone number of "86 xxxxxxxx 0") establishes a call with a UEB (e.g., having a telephone number of "86 xxxxxxxx 1"), the telephone number of the UEB is stored. When the UEA establishes a call with the UEC, the telephone number of the UEC (e.g., the telephone number of the UEC is "86XXXXXXX 2") is stored. In addition, when the UEA invites the UEB, it may be confirmed that the participant includes the telephone number of the UEB, that is, after the UEA successfully invites the UEB to the conference server, the UEA determines that the UEB is the participant, and may establish a correspondence between the UEB and the participant.

When the UEA receives a notification message (such as notify_15) for updating the participant information at time t8, it is determined that the notification message (notify_15) contains an anonymizer. The UEA determines the number corresponding to the anonymizer in the notify_15, and stores the correspondence between "anonymousA" and "86XXXXXXX 1".

After receiving notify_15 at time t8, UEA invites IMS to invite UEC to conferencing. The UEA may confirm that the conferee includes the phone number "86XXXXXXX2" after receiving the conference invitation result for notifying the UEC of the conference, that is, after the UEA successfully invites the UEC to the conference server, the UEA determines that the UEC is the conferee, and may establish a correspondence between the UEC and the conferee.

When the UEA receives a notification message (such as notify_17) for updating the participant information at time t9, and determines that the notification message (notify_17) contains an anonymizer, time t8 is earlier than time t 9. Notify_17 is shaped as:

<user entity="sip:+86XXXXXXXX0@ims.mncXXX.mccXXX.3gppnetwork.org" state="full"><status>connected</status>

<user entity="sip:anonymousA@anonymous.invalid " state="full"><status>connected</status>

<user entity="sip:anonymousB@anonymous.invalid" state="full"><status>connected</status>

the UEA determines that the notify_17 includes two anonymizers, and the UEA queries the correspondence between the "anonymousA" and the "86XXXXXXX 1". And the UEA inquires that the stored telephone numbers of the participants include "86XXXXXXX1, 86XXXXXXX2", the UEA also stores its own telephone number "86XXXXXXX0". The UEA can determine the correspondence between anonymousB and 86XXXXXXX 2.

The UEA may display the phone number of each anonymizer in a display screen of the UEA after determining the phone number corresponding to each anonymizer.

Optionally, 3 or more anonymizers may be included in the notification message. In one embodiment, if the UEA is during a teleconference (e.g., 10 minutes during a teleconference call), the UEA jumps to the dial interface in response to a chairman user clicking on a control to add the call. The UEA establishes a call with the UEN in response to an operation by the chairman to dial the UEN. The UEA may store the telephone number of the UEN. The UEA merges the telephone conference and the call with the UEN (i.e., the call between the UEA and the UEN) in response to the conference chairman clicking on the merge control. The UEA invites the conference server to the UEN for the conference. After the conference server feeds back the successful conference invitation result to the UEA, the UEA determines that the telephone number of the conference participant also includes "86XXXXXXXN". For example, the storage attendees include "86XXXXXXX1, 86XXXXXXX2, and 86XXXXXXXN", and also store the correspondence of "86XXXXXXX1" to "anonymousA", and the correspondence of "86XXXXXXX2" to "anonymousB". The UEA receives the notify_18 at time t10 and determines that the notification message (notify_18) contains an anonymous person. Notify_18 is as follows:

<user entity="sip:anonymousC@anonymous.invalid" state="full"><status>connected</status>

The ue a determines that three anonymizers are included in the notify_18, and the ue a queries the correspondence between the "anonymousA" and the "86XXXXXXX1" and the correspondence between the "86XXXXXXX2" and the "anonymousB". And the telephone numbers of the participants stored in the UEA include "86XXXXXXX1, 86XXXXXXX2, 86XXXXXXXN", and the telephone number of the ue itself "86XXXXXXX0". The UEA can determine the correspondence between anonymousC and 86 XXXXXXXN.

Note that, in the communication protocol, the Notify message is indicated to distinguish each anonymous person through anonymousX, which may be different english letters.

In this example, the chairman device, after receiving the participant information fed back by the last participant invitation, invites the next participant device to the conference server. After receiving the notification message for updating the meeting participant information each time, the conference chairman device can determine the telephone number corresponding to each anonymizer in the notification message according to the stored telephone numbers, so that even if a plurality of anonymizers exist in the notification message, the telephone number of each anonymizer can be accurately determined, the conference chairman device can accurately invite the meeting participant or remove the meeting participant, and the use experience of the conference chairman device for hosting the telephone conference is improved.

In one embodiment, during a conference call, the IMS detects that a participant is leaving the conference call, and may send a notification message to the chairman device to notify the UEA that the participant is leaving, the particular flow being shown in fig. 10.

Step 1001: ue a establishes a call with ue b.

Step 1002: the UEA establishes a call with the UEC.

Step 1003: the UEA creates a conference.

Step 1004: the UEA subscribes to the conference state with the conference server.

Step 1005: the conference server sends a notification message to the UEA.

Step 1006: UEA invites UEB to participate in the session.

Step 1007: the conference server transmits a conference invite request message to the UEB.

Step 1008: the UEB returns a response message to the conference server.

Step 1009: the conference server transmits a notification message (notify_20) to the UEA to Notify the conference invitation result.

Step 1010: the conference server transmits a notification message (notify_21) to the UEA to update the meeting participant information.

Step 1011: the UEA determines the number corresponding to the anonymizer.

Step 1012: the UEA invites the UEC to participate in the session.

Step 1013: the conference server sends a conference invite request message to the UEC.

Step 1014: the UEC returns a response message to the conference server.

Step 1015: the conference server transmits a notification message (notify_22) to the UEA to Notify the conference invitation result.

Step 1016: the conference server sends a notification message (notify_23) to the UEA to update the meeting participant information.

Step 1017: the UEA determines the number corresponding to the anonymizer and displays the number of each participant.

In this example, steps 1001 to 1017 are similar to steps 901 to 917, and reference is made to steps 901 to 917 for description, and detailed description thereof will be omitted.

Step 1018: the conference server sends a notification message (notify_24) to the UEA to inform the conferees that they are away from the conference.

Illustratively, during a call of a teleconference, the participant device leaves the current teleconference. The conference server detects that the conference participants leave the conference call and sends a notification message to the UEA informing the conference chairman device of the information of the conference participants leaving. The chairman device can judge whether a participant leaves or not through the current connection state of the device.

For example, the notification message (notify_24) is shaped as:

<user entity="sip:anonymousA@anonymous.invalid " state="full"><status>disconnected</status>

in the notification message, the device with the telephone number of "86XXXXXXX0" is in a meeting state (connected), and the device with the anonymous number (also called anonymous identifier) of "anonymousA" is in a meeting leaving state (unconnected); the devices with anonymous numbers "anonymousB" and "anonymousC" are in a meeting state (connected).

Step 1019: the UEA determines the number corresponding to the conference participant and displays the number of each conference participant.

Illustratively, the UEA determines the number corresponding to the conference leaving device according to the status of each device in the notification message and the stored number corresponding to each device, and displays the number of each conference participant.

For example, when a UEA (e.g., having a telephone number of "86 xxxxxxxx 0") establishes a call with a UEB (e.g., having a telephone number of "86 xxxxxxxx 1"), the telephone number of the UEB is stored. When the UEA establishes a call with the UEC, the telephone number of the UEC (e.g., the telephone number of the UEC is "86XXXXXXX 2") is stored. In addition, when the UEA invites the UEB to the IMS to participate in the conference, it may be confirmed that the participant includes the telephone number of the UEB, that is, after the UEA invites the UEB to the conference server to succeed in participating in the conference, the UEA determines that the UEB is a participant, and may establish a correspondence between the UEB and the participant.

When the UEA receives a notification message (e.g., notify_21) for updating the participant information at time t11, it is determined that the notification message (notify_21) contains an anonymizer. After step 1011, the UEA stores the correspondence between "anonymousA" and "86XXXXXXX 1".

After receiving notify_21 at time t11, the UEA invites the conference server to join the conference with the UEC. The UEA may confirm that the conferee includes the telephone number "86XXXXXXX2" after receiving the conference invitation result for notifying the UEC of the conference, that is, after the UEA successfully invites the UEC to the IMS, the UEA determines that the UEC is the conferee, and may establish a correspondence between the UEC and the conferee.

When the UEA receives a notification message (such as notify_23) for updating the participant information at time t12, it is determined that the notification message (notify_23) contains an anonymizer. After step 1017, the UEA stores the correspondence between "anonymousB" and "86XXXXXXX2".

If the UEB device leaves the conference, the conference server detects that the UEB leaves the current teleconference, and sends a notification message (notify_24) to the UEA, where the notify_24 is as follows:

the UEA detects that the state of anonymousA in the notify_24 is "disconnect", and can determine that "anonymousA" is in the conference leaving state. And the UEA, which determines the number of the conference participant from the conference as "86 xxxxxxxxx 1", stores the correspondence between "anonymousA" and "86 xxxxxxxxx 1". The UEA displays the number corresponding to the meeting participant currently in the display interface, i.e., displays "86xxxxxx 2".

In this example, when the meeting participant device actively leaves the meeting, the meeting server sends a notification message to the UEA to notify the UEA of the information of the meeting participant. The UEA determines the number of the participant according to the notification message, and can display the current participant in the conference on the display interface, so that the number of the participant on the display interface is accurately updated, and the conference chairman equipment can accurately know the number of each participant.

Fig. 11 is a schematic diagram of an exemplary scenario in which participants actively leave a teleconference.

The UEA (UEA is a chairman device), the UEB (a device for user B), the UEC (a device for user C), and the UEN (a device for user N) are in the same teleconference, as shown in 11a of fig. 11, the teleconference interface 1101 displays telephone information 1102, which includes the telephone number of each participant (i.e., 86 xxxxxxxxxx 1, 86XXXXXXX2, and 86 XXXXXXXN), the number of participants in the meeting (e.g., 3), and the call duration (e.g., 50 minutes 24 seconds as shown in 11 a). The user N carries out hanging-up operation on the current call of the UEN, the conference server detects that the UEN leaves the conference and sends a notification message to the UEA, and the notification is as follows:

<user entity="sip:anonymousA@anonymous.invalid " state="full"><status>connected </status>

<user entity="sip:anonymousC@anonymous.invalid" state="full"><status>disconnected </status>

the UEA stores: the correspondence of "anonymousA" to "86XXXXXXX1", the correspondence of "anonymousB" to "86XXXXXXX2", and the correspondence of "anonymousC" to "86 xxxxxxxxn". The UEA determines that the number of the conference participant leaving the conference is "86XXXXXXXN" according to the stored correspondence. The UEA displays new telephone information 1104 on the teleconference interface 1101, the telephone information 1104 including the telephone number of each participant (i.e., 86 xxxxxxxx 1 and 86 xxxxxxxx 2), the number of participants in the meeting (2 people), and the call duration (50 minutes 30 seconds as shown in fig. 11 b). The teleconference interface 1101 further includes a detailed control 1103, and the chairman user clicks the detailed control 1103 to jump to the detailed interface 1105 of the meeting information, as shown in fig. 11 c. In this 11c, the telephone numbers of each participant at the meeting are displayed in the detailed interface 1105 of the meeting information as 86 xxxxxxxx 1 and 86 xxxxxxxx 2, respectively.

Fig. 12 is a schematic diagram of an exemplary scenario in which a conference chairman removes a participant from a teleconference.

The UEA (UEA is a chairman device, the telephone number of the UEA is 86 xxxxxxxx 0), the UEB (a device of the user B), the UEC (a device of the user C) and the ue N (a device of the user N) are in the same conference call, as shown in 12a of fig. 12, the conference call interface 1201 displays telephone information 1202, and the telephone information 1202 includes the telephone number of each participant (i.e., 86 xxxxxxxx 1, 86 xxxxxxxx 2 and 86 xxxxxxxxn), the number of participants in the conference (e.g., 3 persons) and the call duration (e.g., 50 minutes and 30 seconds as shown in 12 a). The teleconference interface 1201 also includes a detail control 1203, and the chairman user clicks the detail control 1203 to jump to the detail interface 1204 of the meeting information, as shown in fig. 12 b. The detailed interface 1204 contains three options, the chairman user clicking on the hang-up control in option 1205, the UEA disconnecting the call to the device corresponding to "86XXXXXXXN" in response to the hang-up operation by the chairman user. The conference server detects that the device corresponding to 86XXXXXXXN leaves the telephone conference, and sends a notification message to the UEA, wherein the notification is as follows:

the UEA stores: the correspondence of "anonymousA" to "86XXXXXXX1", the correspondence of "anonymousB" to "86XXXXXXX2", and the correspondence of "anonymousC" to "86 xxxxxxxxn". The UEA determines that the number of the conference participant leaving the conference is "86XXXXXXXN" according to the stored correspondence. The UEA displays new telephone information 1207 on the teleconference interface 1206, the telephone information 1207 including the telephone number of each participant (i.e., 86 xxxxxxxx 1 and 86 xxxxxxxx 2), the number of participants at the meeting (2 people), and the talk time (50 minutes and 32 seconds as shown in 12 c). The device corresponding to that number (i.e., "86 xxxxxxxxxn") will be removed from the teleconference. The chairman user may learn from telephone information 1207 the number of the current meeting participant device.

In another embodiment, in the case that only one anonymizer exists in the Notify message (i.e. the protocol of the previous version of IR 92.0 is adopted), the process of removing the conferee or the conferee leaving the teleconference by itself by the chairman user is similar to that of fig. 10-12, and will not be described again here.

It will be appreciated that the electronic device, in order to achieve the above-described functions, includes corresponding hardware and/or software modules that perform the respective functions. The steps of an algorithm for each example described in connection with the embodiments disclosed herein may be embodied in hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation is not to be considered as outside the scope of this application.

The present embodiment also provides a computer storage medium having stored therein computer instructions which, when executed on an electronic device, cause the electronic device to perform the above-described related method steps to implement the method for starting an application in the above-described embodiments. The storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The present embodiment also provides a computer program product which, when run on a computer, causes the computer to perform the above-mentioned related steps to implement the method of launching an application in the above-mentioned embodiments.

The electronic device, the computer storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects thereof can be referred to the beneficial effects in the corresponding methods provided above, and will not be described herein.

Any of the various embodiments of the application, as well as any of the same embodiments, may be freely combined. Any combination of the above is within the scope of the present application.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone.

The terms first and second and the like in the description and in the claims of embodiments of the present application are used for distinguishing between different objects and not necessarily for describing a particular sequential order of objects. For example, the first target object and the second target object, etc., are used to distinguish between different target objects, and are not used to describe a particular order of target objects.

In the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as examples, illustrations, or descriptions. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

In the description of the embodiments of the present application, unless otherwise indicated, the meaning of "a plurality" means two or more. For example, the plurality of processing units refers to two or more processing units; the plurality of systems means two or more systems.

The embodiments of the present application have been described above with reference to the accompanying drawings, but the present application is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those of ordinary skill in the art without departing from the spirit of the present application and the scope of the claims, which are also within the protection of the present application.

Claims

1. The reminding method of the telephone conference is characterized by being applied to conference chairman equipment, wherein the conference chairman equipment establishes a call with a plurality of call equipment, the conference chairman equipment invites the plurality of call equipment to carry out the telephone conference through a conference server, and the number of the plurality of call equipment is at least 2; the method comprises the following steps:

The conference chairman device receives a first notification message sent by the conference server, wherein the first notification message comprises: the telephone number and the conference state of the presented conference participant equipment, the anonymous identification of the anonymizer and the conference state, wherein the conference state comprises a conference leaving state and a conference in state, the conference participant equipment is call equipment invited and joins the telephone conference, and the anonymizer is used for hiding the telephone number of the conference participant equipment;

judging whether an anonymous person exists in the first notification message;

if the anonymizer exists in the first notification message, acquiring the telephone number of the presented conferee device from the first notification message and acquiring the stored telephone number of each conferee device from the conference chairman device;

determining a telephone number corresponding to an anonymizer in the first notification message according to the stored telephone number of each participant device and the telephone number of the participant device presented in the first notification message;

if the meeting success of the plurality of meeting participant devices is detected, displaying the telephone number corresponding to each meeting participant device in a meeting state in a display interface according to the telephone number corresponding to the anonymous person in the first notification message;

If the first notification message includes a unique anonymizer, determining, according to the stored phone numbers of each participant device and the phone numbers of the participant devices presented in the first notification message, a phone number corresponding to the anonymizer in the first notification message includes:

and respectively matching the telephone numbers of the presented conferee devices with the telephone numbers of each of the stored conferee devices, and acquiring the telephone numbers which are not matched from the telephone numbers of the stored conferee devices as the telephone numbers corresponding to the anonymizers in the first notification message.

2. The method of claim 1, wherein the plurality of telephony devices comprises: the first communication device and the second communication device;

before retrieving the stored phone number for each participant device from the chairman device, the method further comprises:

storing the telephone number of the first call device and the telephone number of the second call device under the condition that the conference chairman device establishes calls with the plurality of call devices;

if the conference chairman equipment is detected to invite the first call equipment through the conference server, determining that the first call equipment is first participant equipment;

And if the conference chairman equipment is detected to invite the second session equipment through the conference server, determining that the second session equipment is second participant equipment.

3. The method of claim 1, wherein the first notification message further comprises a telephone number and a meeting status of the chairman device; obtaining the telephone number of the presented participant device from the first notification message, including:

acquiring a stored telephone number of the conference chairman equipment;

and removing the telephone number of the conference chairman device and the anonymous identification of the anonymizer from the first notification message, and obtaining the telephone number of the presented conferee device.

4. The method according to claim 1, wherein the method further comprises:

and storing a first corresponding relation between the anonymous identifier of the anonymous person and the corresponding telephone number in the first notification message.

5. The method of claim 4, wherein if the conference server detects that a participant device is present to leave the conference call, sending a second notification message to the chairman device, the second notification message including a telephone number and a conference status of the presented participant device, an anonymous identification of an anonymous person, and a conference status; the anonymous identifier in the second notification message is the same as the anonymous identifier in the first notification message; the method further comprises the steps of:

Receiving a second notification message sent by the conference server;

determining the telephone number of each participant device in the second notification message according to the first corresponding relation;

determining the telephone number of the meeting participant equipment in the second notification message in a meeting leaving state according to the telephone number of each meeting participant equipment in the second notification message;

and removing the telephone number of the meeting participant equipment in the meeting leaving state from the display interface.

6. The method of claim 5, wherein prior to the receiving the second notification message sent by the conference server, the method further comprises:

responding to a jump operation of a chairman user, jumping to a detailed interface, wherein the detailed interface comprises options corresponding to each participant device, and the options corresponding to the participant device comprise telephone numbers and hang-up controls of the participant devices;

and in response to the chairman user clicking a hang-up control in options corresponding to one or more participant devices, disconnecting the call with the selected participant device.

7. The method according to claim 4, wherein the method further comprises:

The conference chairman device responds to the call adding operation of the conference chairman user and establishes a third call with a third call device, wherein the third call device is a call device except the plurality of call devices;

responding to the merging operation of the chairman user, and inviting the third session device to join the telephone conference through the conference server by the chairman device;

receiving a third notification message sent by the conference server, wherein the third notification message comprises a telephone number of the third communication device and an anonymous identifier in the first notification message;

determining the telephone number of each meeting participant device in the current conference call according to the first corresponding relation and the third notification message;

and displaying the telephone numbers corresponding to the meeting participant devices in the meeting state on the display interface.

8. The method of claim 2, wherein if the first notification message includes a plurality of anonymizers, the determining the phone number corresponding to the anonymizer in the first notification message based on the stored phone number of each participant device and the phone number of the participant device presented in the first notification message includes:

Obtaining a corresponding relation between a telephone number and an anonymous identifier of each anonymous person in a fourth known message, wherein the fourth known message is a notification message fed back by the conference server when calling equipment is invited to join the telephone conference last time, and the number of anonymous persons in the fourth known message is one less than that of anonymous persons in the first notification message;

and determining the telephone number corresponding to each anonymizer in the first notification message according to the corresponding relation between the telephone number of each anonymizer in the fourth notification message and the anonymizer, the stored telephone number of each conferee device and the telephone number of the conferee device presented in the first notification message.

9. The method of claim 8, wherein prior to the chairman device receiving the first notification message sent by the conference server, the method further comprises:

the conference chairman equipment invites the first call equipment to join the telephone conference to the conference server, and the conference server returns a fourth known message to the conference chairman equipment;

and if the conference chairman equipment receives the fourth notification message, inviting the second conference equipment to join the conference call to the conference server, and returning the first notification message to the conference chairman equipment by the conference server.

10. The method of claim 8, wherein the method further comprises:

storing the corresponding relation between the number of each anonymizer and the anonymity identifier in the first notification message;

if the conference server detects that the conference participant equipment leaves the telephone conference, a fifth notification message is sent to the conference chairman equipment, wherein the fifth notification message comprises a telephone number and a conference state of each presented conference participant equipment, and an anonymous identifier and a conference state of each anonymous participant; the method further comprises the steps of:

receiving a fifth notification message sent by the conference server;

determining the telephone number of each participant device in the fifth notification message according to the corresponding relation between the number corresponding to each anonymizer in the first notification message and the anonymizing identifier;

determining the telephone number of the meeting participant equipment in a meeting leaving state in a fifth notification message according to the telephone number of each meeting participant equipment in the fifth notification message;

11. The method of claim 2, wherein detecting whether the plurality of participant devices successfully conferred comprises:

Receiving a first meeting invitation result returned by the meeting server, wherein the first meeting invitation result indicates that the first participant equipment is successful in meeting;

and receiving a second meeting invitation result returned by the meeting server, wherein the second meeting invitation result indicates that the second meeting participants are successful in meeting.

12. An electronic device, comprising:

one or more processors;

a memory;

and one or more computer programs, wherein the one or more computer programs are stored on the memory, which when executed by the one or more processors, cause the electronic device to perform the method of alerting of a conference call as claimed in any one of claims 1-11.

13. A computer readable storage medium comprising a computer program, characterized in that the computer program, when run on an electronic device, causes the electronic device to perform the method of reminding a conference call according to any one of claims 1-11.