CN109923880B

CN109923880B - Conference flow control method and related equipment

Info

Publication number: CN109923880B
Application number: CN201780069190.4A
Authority: CN
Inventors: 樊宇伟; 张振忠
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-03-31
Filing date: 2017-07-21
Publication date: 2021-02-23
Anticipated expiration: 2037-07-21
Also published as: CN109923880A; WO2018176697A1

Abstract

The application provides a conference flow control method, which is used for normally updating a conference state, and is applied to a first terminal, wherein the first terminal and one or more second terminals establish an SIP conference, and the method comprises the following steps: receiving a participation event notification of the participation second terminal, wherein the participation event notification carries the network identifier of the participation second terminal; receiving a conference event notification of the conference leaving second terminal, wherein the conference event notification carries a network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal comprises a terminal identifier of the conference leaving second terminal; when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference; and when the network identification of the conference leaving second terminal is successfully matched with the network identification of the conference participating second terminal, prompting the conference participating second terminal to leave the SIP conference. The application also provides a corresponding terminal, a storage medium and a computer program product.

Description

Conference flow control method and related equipment

The present application claims priority of chinese patent application having application number 201710208980.8 entitled "a conference flow control method" filed by chinese patent office on 31/3/2017, the entire contents of which are incorporated herein by reference.

Technical Field

The invention belongs to the technical field of communication, and particularly relates to a conference flow control method and a terminal.

Background

With the maturity of internet telephony, a user terminal may establish a multiparty conference session using a Session Initiation Protocol (SIP) using a voice transmission technology based on an Internet Protocol (IP). For example, voice over long term evolution (VoLTE) or wireless fidelity (wifi) are voice over IP transmission technologies. The voice transmission technology of the IP can realize the common transmission of data and voice services in the same network. The user terminal may establish a multiparty conference session using either the SIP-based VoLTE technology or the volwifi technology.

In the prior art, after establishing a multiparty conference call based on SIP, a user terminal can communicate with other user terminals through a conference center. The conference center is responsible for managing the states of all the participating user terminals. The user terminal can receive the conference event notification sent by the conference center to acquire the change condition of the conference state of other user terminals. However, in the prior art, when a user terminal receives a notification of a conference leaving event of another user terminal, it is impossible to know which user terminal leaves the conference and correctly update the local conference state of the user terminal.

Disclosure of Invention

The embodiment of the application provides a conference flow control method, which is used for solving the technical problem that the local conference state of a user terminal cannot be updated correctly in the prior art. The embodiment of the application also provides a corresponding terminal, a storage medium and a computer program product.

A first aspect of the present application provides a conference flow control method, where the method may be applied to a first terminal, and the first terminal may establish a SIP conference with one or more second terminals, where the method may include: receiving a participation event notification of a participation second terminal, wherein the participation event notification carries a network identifier of the participation second terminal; receiving a conference leaving event notification of a conference leaving second terminal, wherein the conference leaving event notification carries a network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal comprises a terminal identifier of the conference leaving second terminal; when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference; and when the network identification of the conference leaving second terminal is successfully matched with the network identification of the conference participating second terminal, prompting the conference participating second terminal to leave the SIP conference. As can be seen from the above first aspect, in the conference flow control method provided in the first aspect of the present application, when the terminal identifier of the conference leaving second terminal is different from the telephone number of the conference participating second terminal, the network identifier of the conference leaving second terminal may be matched with the network identifier of the conference participating second terminal, so as to correctly prompt the conference participating second terminal to leave the SIP conference.

With reference to the first aspect, in a first possible implementation manner, the method further includes: when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, determining whether the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference have an inclusion relationship; and when the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference do not have the inclusion relationship, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference. As can be seen from the first possible implementation manner of the first aspect, when the terminal identifier of the departing second terminal and the phone number of the participating second terminal do not have a containment relationship, the step of matching the network identifier of the departing second terminal and the network identifier of the participating second terminal is performed, so that the process of matching the network identifier of the departing second terminal and the network identifier of the participating second terminal can be reduced.

With reference to the first possible implementation manner of the first aspect, in a second possible implementation manner, the method further includes: and when the terminal identification of the conference leaving second terminal and the telephone number of the conference participating second terminal have a containing relationship, prompting the conference participating second terminal to leave the SIP conference. As can be seen from the second possible implementation manner of the first aspect, when the terminal identifier of the conference leaving second terminal and the telephone number of the conference participating second terminal have a inclusion relationship, the conference participating second terminal can be correctly prompted to leave the SIP conference.

With reference to the first aspect, in a third possible implementation manner, the matching the network identifier of the departing second terminal and the network identifier of the participating second terminal includes: determining whether the network identification of the second terminal in the conference is the same as the network identification of the second terminal in the conference; and when the network identifier of the second terminal in the conference is the same as the network identifier of the second terminal in the conference, determining that the network identifier of the second terminal in the conference is successfully matched with the network identifier of the second terminal in the conference. As can be seen from the third possible implementation manner of the first aspect, whether the network identifier of the conference leaving second terminal and the network identifier of the conference participating second terminal are successfully matched can be quickly determined by determining whether the network identifier of the conference leaving second terminal is the same as the network identifier of the conference participating second terminal, so that the conference participating second terminal is correctly prompted to leave the SIP conference when the matching is successful.

With reference to the first aspect, or the first possible implementation manner of the first aspect, or the second possible implementation manner of the first aspect, or the third possible implementation manner of the first aspect, in a fourth possible implementation manner, the network identifier of the participating second terminal includes a terminal identifier of the participating second terminal, and the method further includes: and when the terminal identification of the second terminal participating in the conference is determined to be different from the telephone number of the second terminal participating in the conference, and the terminal identification of the second terminal participating in the conference and the telephone number of the second terminal participating in the conference do not have an inclusion relationship, storing the network identification of the second terminal participating in the conference. As can be seen from the fourth possible implementation manner of the first aspect, when the terminal identifier of the second participant terminal and the phone number of the second participant terminal do not have an inclusion relationship, the network identifier of the second participant terminal may be stored, so that when the terminal identifier of the second participant terminal and the phone number of the second participant terminal do not have an inclusion relationship, the second participant terminal leaving the conference may be determined by the stored network identifier of the second participant terminal.

A second aspect of the present application provides a terminal, where the terminal may be a first terminal, and the first terminal establishes a SIP conference with one or more second terminals, and the terminal may include:

the first receiving unit is used for receiving a participation event notification of a participation second terminal, and the participation event notification carries a network identifier of the participation second terminal;

a second receiving unit, configured to receive a conference leaving event notification of a conference leaving second terminal, where the conference leaving event notification carries a network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal includes a terminal identifier of the conference leaving second terminal;

the matching unit is used for matching the network identifier of the second terminal of the conference with the network identifier of the second terminal of the conference when the terminal identifier of the second terminal of the conference is different from the telephone number of the second terminal of the conference;

and the prompting unit is used for prompting the participating second terminal to leave the SIP conference when the network identifier of the leaving second terminal is successfully matched with the network identifier of the participating second terminal.

With reference to the second aspect, in a first possible implementation manner, the terminal may further include:

the determining unit is used for determining whether the terminal identification of the conference separating second terminal and the telephone number of the conference participating second terminal have an inclusion relationship or not when the terminal identification of the conference separating second terminal is different from the telephone number of the conference participating second terminal;

the matching unit is further configured to match the network identifier of the conference-departing second terminal with the network identifier of the conference-participating second terminal when the terminal identifier of the conference-departing second terminal does not have a containment relationship with the telephone number of the conference-participating second terminal.

With reference to the first possible implementation manner of the second aspect, in a second possible implementation manner, the prompting unit may further be configured to:

and when the terminal identification of the conference leaving second terminal and the telephone number of the conference participating second terminal have a containing relationship, prompting the conference participating second terminal to leave the SIP conference.

With reference to the second aspect, in a third possible implementation manner, the matching unit may include:

the first determining subunit is used for determining whether the network identifier of the second terminal in the conference is the same as the network identifier of the second terminal in the conference;

and the second determining subunit is configured to determine that the network identifier of the second terminal in the conference is successfully matched with the network identifier of the second terminal in the conference when the network identifier of the second terminal in the conference is the same as the network identifier of the second terminal in the conference.

With reference to the second aspect, or the first possible implementation manner of the second aspect, or the second possible implementation manner of the second aspect, or the third possible implementation manner of the second aspect, in a fourth possible implementation manner, the network identifier of the participating second terminal includes a terminal identifier of the participating second terminal, and the terminal may further include:

and the storage unit is used for storing the network identifier of the second conference participating terminal when the terminal identifier of the second conference participating terminal is determined to be different from the telephone number of the second conference participating terminal and the terminal identifier of the second conference participating terminal does not have a containing relation with the telephone number of the second conference participating terminal.

The beneficial effects of the parts in the second aspect can refer to the description in the first aspect, and are not described herein.

Yet another aspect of the present application provides a terminal, including: a processor and a memory; the memory stores computer instructions, and when the computer instructions in the memory are executed, the processor executes the conference flow control method according to the first aspect or any one of the optional implementations of the first aspect.

A further aspect of the present application provides a computer-readable storage medium, which includes instructions, when executed on a first terminal, to cause the first terminal to perform the conference flow control method according to the first aspect or any one of the optional implementations of the first aspect, where the first terminal establishes an SIP conference with one or more second terminals.

A further aspect of the present application provides a computer program product comprising instructions, which when run on a first terminal, cause the first terminal to perform the conference flow control method of the first aspect or any one of the optional implementations of the first aspect, where the first terminal establishes a SIP conference with one or more second terminals.

According to the embodiment of the application, when the first terminal receives the participation event notification of the participation second terminal, the network identification of the participation second terminal carried by the participation event notification can be obtained. When receiving the conference leaving event notification of the conference leaving second terminal, the network identifier of the conference leaving second terminal carried by the conference leaving event notification may be obtained, where the network identifier of the conference leaving second terminal includes the terminal identifier of the conference leaving second terminal. When the network identifier of the conference leaving second terminal is different from the telephone number of the conference participating second terminal, the conference leaving second terminal can be correctly determined by matching the network identifier of the conference leaving second terminal with the network identifier of the conference participating second terminal, so that the conference state can be correctly updated to prompt the conference participating second terminal to leave the conference.

Drawings

Fig. 1 is a schematic diagram of a conference call setup process in an embodiment of the present application;

FIG. 2 is a schematic diagram of a process of leaving a teleconference by a participant terminal in the embodiment of the present application;

FIG. 3 is a schematic diagram of an application scenario in an embodiment of the present application;

fig. 4 is a flowchart of an embodiment of a conference flow control method provided in an embodiment of the present application;

fig. 5 is a flowchart of another embodiment of a conference flow control method provided in an embodiment of the present application;

FIG. 6 is a diagram illustrating a participant list in an embodiment of the present application;

fig. 7 is a flowchart of another embodiment of a conference flow control method provided in an embodiment of the present application;

FIG. 8 is a schematic illustration of another participant list in an embodiment of the subject application;

fig. 9 is a schematic diagram of an embodiment of a terminal in an embodiment of the present application;

fig. 10 is a schematic diagram of another embodiment of the terminal in the embodiment of the present application.

Detailed Description

First, a procedure of establishing a multiparty conference call based on SIP and a procedure of leaving a conference by a participant terminal will be described separately.

Referring to fig. 1, a schematic diagram of a SIP teleconference setup process in the embodiment of the present application is shown. In this example, user terminal a may be a terminal that initiates a conference call, i.e., user terminal a is a chairman of the conference, and user terminals B and C are terminals that participate in the conference call.

User Equipment (UE) a may store telephone numbers of user terminal B and user terminal C. User terminal a may establish a network-based voice connection with user terminal B by calling the phone number of user terminal B. User terminal a may establish a network-based voice connection with user terminal C by calling the telephone number of user terminal C. I.e. the voice session connection of user terminal a with user terminal B and the voice session connection of user terminal a with user terminal C are maintained simultaneously.

The user terminal a then creates a conference, with which the user terminal a communicates via a Uniform Resource Identifier (URI) of a conference center (conference factor). The URI of the conference center corresponds to the telephone number of the conference center.

The process of the user terminal A for establishing the telephone conference comprises the following steps: 1. the user terminal a sends invitation information (INVITE) of the conference to the conference center. 2. The conference centre sends the conference parameters (message 183 in the SIP protocol, hereinafter referred to as message 183) to the user terminal a. 3. The user terminal a sends an acknowledgement message (PRACK) of the reception of the conference parameters to the conference center. 4. The conference center sends response information (message 200 in the SIP protocol, hereinafter referred to as message 200) of the confirmation information to the user terminal a. 5. The user terminal a transmits communication resource UPDATE information (UPDATE) to the conference center. 6. The conference center sends response information of the update information to the user terminal a (message 200). 7. The conference center sends the conference establishment success information (OK) to the user terminal A, and the establishment of the conference communication channel between the user terminal A and the conference center is completed. 8. And the user terminal A sends confirmation information (ACK) of the conference establishment success information to the conference center to complete the process of establishing the teleconference by the user terminal A, and at the moment, the user terminal A is added into the teleconference.

The user terminal a may subscribe to the conference event from the conference center, and the process of subscribing to the conference event by the user terminal a includes: 9. the user terminal a sends subscription conference event information (SUBSCRIBE) to the conference center. 10. The conference center sends response information subscribing to the conference event information to user terminal a (message 200). After subscribing the conference event, the user terminal a may receive a conference event notification sent by the conference center.

After user terminal a joins the conference, the conference center may send a conference event notification to user terminal a. The process of sending the conference event notification to the user terminal a by the conference center includes: 11. the conference centre sends a notification of a meeting event (NOTIFY) to the user terminal a. At this time, the participant event notification carries the network identifier, and the network identifier is the network identifier of the user terminal a, so that the participant of the current conference is prompted to be the user terminal a. 12. User terminal a sends a response message to the conference center for the event notification of the participation (message 200). The user terminal a can know the current conference state through the conference event notification.

The user terminal a can pull the user terminal B into the established teleconference, and the process of joining the teleconference by the user terminal B includes: 13. user terminal a sends participant adding information (Refer UE B) to the conference center, where the participant adding information carries the phone number of user terminal B saved by user terminal a. 14. The conference center sends response information (message 202 in the SIP protocol, hereinafter referred to as message 202) of the participant addition information to the user terminal a. 15. The conference center sends INVITE information (INVITE) of the conference to the user terminal B. 16. The user terminal B sends response information (message 100 in the SIP protocol, hereinafter referred to as message 100) of the invitation information to the conference center. 17. The conference center sends a notification message (NOTIFY) to the user terminal a, notifying the user terminal a that the user terminal B has been invited to enter the teleconference. 18. The user terminal a transmits response information of the notification information to the conference center (message 200). 19. The conference centre and the user terminal B perform a procedure similar to the above-described 2-6 conference centre communicating with the user terminal a, i.e. the conference centre sends the conference parameters to the user terminal B (message 183). The user terminal B sends an acknowledgement message (PRACK) of the reception of the conference parameters to the conference center. The conference center sends a response message (message 200) confirming the information to the user terminal B. The user terminal B transmits communication resource UPDATE information (UPDATE) to the conference center. The conference center sends response information of the update information to the user terminal B (message 200). The figure only schematically shows that the conference centre sends the response information (message 200) of the update information to the user terminal B, and other steps are omitted in the figure. 20. The conference center sends notification information (NOTIFY) to the user terminal a, notifying the user terminal a that the user terminal B has successfully invited to enter the teleconference. 21. The user terminal a transmits response information of the notification information to the conference center (message 200). And finishing the process of joining the teleconference by the user terminal B.

After user terminal B joins the conference call, the conference centre may send a conference event notification to user terminal a. The process of sending the conference event notification to the user terminal a by the conference center includes: 22. the conference centre sends a notification of a meeting event (NOTIFY) to the user terminal a. At this time, the network identifier carried by the conference event notification is the network identifier of the user terminal B, the user terminal B newly joining the teleconference is prompted, and the participants of the current conference are the user terminal a and the user terminal B. 23. User terminal a sends a response message to the conference center for the event notification of the participation (message 200). The user terminal a can know the current conference state through the conference event notification.

After user terminal B joins the conference call, user terminal a needs to remove the voice connection with user terminal B. The procedure of removing the voice connection with the user terminal B includes: 24. the user terminal a sends the end call information (BYE) to the user terminal B. 25. The user terminal B transmits response information for ending the call information to the user terminal a (message 200). So that user terminal a removes the voice connection with user terminal B.

Similar to the process of user terminal B joining the conference call, user terminal a may pull user terminal C into the established conference call. The process of joining the teleconference by the user terminal C includes: 26. user terminal a sends participant adding information (Refer UE C) to the conference center, where the participant adding information carries the phone number of user terminal C saved by user terminal a. 27. The conference center sends response information of the participant addition information to the user terminal a (message 202). 28. The conference center sends invitation information (INVITE) of the conference to the user terminal C. 29. The user terminal C sends the response information of the invitation information to the conference center (message 100). 30. The conference center sends a notification message (NOTIFY) to the user terminal a, notifying the user terminal a that the user terminal C has been invited to enter the teleconference. 31. The user terminal a transmits response information of the notification information to the conference center (message 200). 32. The conference centre and the user terminal C perform a procedure similar to the above-described 2-6 conference centre communicating with the user terminal a, i.e. the conference centre sends the conference parameters to the user terminal C (message 183). The user terminal C sends an acknowledgement message (PRACK) of the reception of the conference parameters to the conference center. The conference center sends a response message (message 200) confirming the information to the user terminal C. The user terminal C sends communication resource UPDATE information (UPDATE) to the conference center. The conference center sends response information of the update information to the user terminal C (message 200). The figure only schematically shows that the conference center sends the response information (message 200) of the update information to the user terminal C, and other steps are omitted in the figure. 33. The conference center sends notification information (NOTIFY) to the user terminal a, notifying the user terminal a that the user terminal C has successfully invited to enter the teleconference. 34. The user terminal a transmits response information of the notification information to the conference center (message 200). And finishing the process of joining the user terminal C into the teleconference.

After user terminal C joins the conference call, the conference centre may send a conference event notification to user terminal a. The process of sending the conference event notification to the user terminal a by the conference center includes: 35. the conference centre sends a notification of a meeting event (NOTIFY) to the user terminal a. At this time, the network identifier carried by the conference event notification is the network identifier of the user terminal C, and the user terminal C which is newly added to the teleconference is prompted, so that the participants of the current conference are the user terminal a, the user terminal B and the user terminal C. 36. User terminal a sends a response message to the conference center for the event notification of the participation (message 200). The user terminal a can know the current conference state through the conference event notification.

After user terminal C joins the conference call, user terminal a needs to remove the voice connection with user terminal C. The procedure of removing the voice connection with the user terminal C includes: 37. the user terminal a transmits the call end information (BYE) to the user terminal C. 38. The user terminal C transmits response information for ending the call information to the user terminal a (message 200). So that user terminal a removes the voice connection with user terminal C.

At this time, the user terminal a, the user terminal B, and the user terminal C all enter the teleconference, and the teleconference can be started.

Meanwhile, the participating user terminals can actively leave the teleconference. Referring to fig. 2, a flow of a conference call leaving of a user terminal participating in the embodiment of the present application is shown. In this example, user terminal a, user terminal B, and user terminal C are in a teleconference, and user terminal B actively leaves the teleconference. The flow that the user terminal B leaves the teleconference and the conference center can send the conference event notification to the user terminal a includes: 39. the user terminal B transmits the conference ending information (BYE) to the conference center. 40. The conference center sends response information of the conference end information to the user terminal B (message 200). 41. The conference center sends a notification of a departure event (NOTIFY) to the user terminal a. At this time, the conference exit event notification carries a network identifier, which may be the network identifier of the user terminal B to prompt the user terminal B to leave the teleconference. 42. User terminal a sends the response information of the departure event notification to the conference center (message 200). The user terminal a can know the current conference state through the conference event notification.

Referring to fig. 3, a schematic diagram of an application scenario in the embodiment of the present application is shown. In the embodiment of the present application, when a multi-party teleconference is performed, a user terminal only communicates with a conference center (conference factor), and does not perform end-to-end communication with other user terminals. Therefore, the conference center is responsible for managing the states of all the participating user terminals, and the conference center can send a conference event notification to the terminals and update the conference state to the user terminals subscribed with the conference event. That is, the user terminal may subscribe to the conference event from the conference center, for example, step 9 in fig. 1, and the conference center may transmit a conference event notification to the user terminal when the conference state changes, for example, step 11, step 22, step 35 in fig. 1, and step 41 in fig. 2. In practical applications, a concentrator (FOCUS) in a conference center may send a conference event notification to a user terminal through the SIP protocol and obtain feedback of the user terminal. The MIXER (MIXER) in the conference center can implement voice communication of the teleconference through real-time transport protocol (RTP).

The conference center may carry a network identifier of the user terminal in the delivered conference event notification, where the network identifier may be described by using an SIP URI. The format of the SIP URI may be x @ y, where x represents a terminal identifier of the user terminal, the terminal identifier may be a phone number or may be changed to another character string, y represents a service host, and the service host may be a domain name or an IP address. Com, where the part +13512345678 before @ is the terminal identity of the user terminal, which is the phone number, and the part after @ is the domain name.

The following description will take an example in which the conference event notification (NOTIFY message) carries the conference event. Wherein, the extensible markup language (XML) describes that the current conference state has three participants < user-count > 3>, and updates the state < status > of one of the participants < user entry > sip: +61419373414@ connect.

10:12:52.772UE----<----NOTIFY-------------------NW(9NOTIF)Call-Id:

……

<conference-state>

<user-count>3</user-count>

</conference-state>

<users>

<endpoint

entity＝"sip:[email protected]:5160；transport＝tcp"state＝"full">

</endpoint>

</user>

</users>

</conference-info>

In an example, the membership event notification carries a network identification of the user terminal of +61419373414@ connect.

The terminal initiating the conference call holds the telephone numbers of the participating conference call terminals. When the terminal initiating the teleconference pulls the terminal participating in the teleconference into the established teleconference, the terminal initiating the teleconference sends the stored telephone number of the terminal participating in the teleconference to the conference center so as to pull the terminal participating in the teleconference into the established teleconference. Such as step 13 and step 26 in fig. 1. However, because the processing flow of the conference center is complex, the terminal identifier in the network identifier carried in the conference event notification returned by the conference center may change, which is different from the telephone number of the terminal participating in the teleconference. See table below for:

scene	Locally stored telephone number	Network identification carried by conference event notification	Whether it is matched
				1	+13512345678	sip:[email protected]	Is that
2	10086	sip:[email protected]	Whether or not
				3	13812345678	sip:[email protected]	Whether or not

For example, in scenario 1, the phone number of the participant teleconference terminal stored in the terminal initiating the teleconference is +13512345678, and the network identifier of the participant teleconference terminal carried in the delivered conference event notification by the conference center is +13512345678@ cmcc.

In scenario 2, the telephone number of the terminal participating in the teleconference, which is stored in the terminal initiating the teleconference, is 10086, and the network identifier of the terminal participating in the teleconference, which is carried in the delivered conference event notification by the conference center, is 01010086@ cmcc.

In scene 3, the telephone number of the terminal participating in the teleconference, which is stored by the terminal initiating the teleconference, is 13812345678, and the network identifier of the terminal participating in the teleconference, which is carried in the delivered conference event notification by the conference center, is anonymous01@ anonymous.

Since the terminal initiating the teleconference can store the telephone numbers of the terminals participating in the teleconference, the terminal initiating the teleconference can add the telephone numbers of the terminals participating in the teleconference to the displayed participant list, and the participant list cannot be displayed wrongly in the process that the participant terminals enter the teleconference.

However, in the prior art, when a participant terminal leaves a teleconference, and a conference center sends a conference leaving event notification to a terminal initiating the teleconference, when a terminal identifier in a network identifier carried in the conference leaving event notification cannot be matched with a stored telephone number, for example, the above scenario 2 and scenario 3 occur, the terminal initiating the teleconference cannot acquire the telephone number of the conference leaving terminal, that is, cannot determine a participant terminal leaving the conference, and further cannot delete the telephone number of the participant terminal leaving the conference from a displayed participant list, and a situation that a local conference state of the terminal initiating the teleconference cannot be correctly updated may occur.

Therefore, the embodiment of the present application provides a conference flow control method, which can be applied to a first terminal. The first terminal establishes a SIP conference with one or more second terminals. The first terminal may be understood as a terminal initiating a conference call. The second terminal may be understood as a terminal participating in the conference call, i.e. a participant terminal. And the first terminal receives the participation event notification of the participation second terminal, and the participation event notification carries the network identification of the participation second terminal. The first terminal may further receive a conference leaving event notification of the conference leaving second terminal, where the conference leaving event notification carries a network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal includes a terminal identifier of the conference leaving second terminal. And matching the network identifier of the conference leaving second terminal with the network identifiers of the conference participating second terminals, so that the conference state can be correctly updated to prompt the conference participating second terminals to leave the conference. The embodiment of the application also provides a corresponding terminal, a storage medium and a computer program product.

The first terminal or the second terminal in the embodiments of the present application may be a smart phone, a tablet computer, a laptop portable computer, a desktop computer, or the like.

First, an implementation manner of the first terminal storing the network identifier of the participating second terminal and/or the phone number of the participating second terminal in this embodiment is described.

In a first implementation manner, the first terminal may store the phone number of the second terminal and the network identifier of the participating second terminal carried in the participating event notification, where the network identifier of the participating second terminal may be described using the SIP URI.

For example, in step 22 and step 35 in fig. 1, when receiving the conference participating event notification of the second terminal, the first terminal may store the network identifier of the second terminal, which is carried in the conference participating notification.

The first terminal can store the telephone number of the second terminal participating in the conference, and the first terminal carries the telephone number of the second terminal participating in the conference when sending the participant adding information to the conference center, so that the first terminal knows that the second terminal participating in the conference is currently entering the conference. When receiving the conference participating event notification of the second terminal participating in the conference, the network identifier of the second terminal participating in the conference, which is carried by the conference participating event notification, may be stored in correspondence with the phone number of the second terminal participating in the conference currently entering the conference.

For example, in step 13 in fig. 1, the participant addition information carries the phone number of the user terminal B saved by the user terminal a, and the user terminal a knows that the user terminal a is currently entering the conference as the user terminal B. The network identification carried by the conference event notification may be saved together with the telephone number of the user terminal B in step 22 if the network identification carried by the conference event notification corresponds to the network identification of the user terminal B.

In a second implementation manner, the network identifier of the participating second terminal includes the terminal identifier of the participating second terminal, and when it is determined that the terminal identifier of the participating second terminal is different from the telephone number of the participating second terminal and the terminal identifier of the participating second terminal does not have a containment relationship with the telephone number of the participating second terminal, the network identifier of the participating second terminal is stored.

That is, when the first terminal receives the participation event notification, for example, in step 22 and step 35 in fig. 1, it is first determined whether the terminal identifier in the network identifier of the participation second terminal is the same as the phone number of the locally stored participation second terminal.

If the terminal identifier in the network identifier of the second terminal participating in the conference is the same as the locally stored telephone number of the second terminal participating in the conference, the network identifier of the second terminal participating in the conference is not stored, and only the telephone number of the second terminal participating in the conference is stored.

And if the terminal identifier in the network identifier of the second terminal participating in the conference is different from the locally stored telephone number of the second terminal participating in the conference, continuously judging whether the terminal identifier in the network identifier of the second terminal participating in the conference has a containing relation with the locally stored telephone number of the second terminal participating in the conference. For example, the terminal id 01010086 in the network id in scenario 2 has a containing relationship with the locally stored phone number 10086, that is, the string 10086 belongs to a part of the string 01010086, and both have a containing relationship.

If the terminal identifier in the network identifier of the participating second terminal has a containing relationship with the locally stored telephone number of the participating second terminal, the network identifier of the participating second terminal may not be stored, and only the telephone number of the participating second terminal may be stored.

And if the terminal identification in the network identification of the second terminal participating in the conference does not have the inclusion relationship with the locally stored telephone number of the second terminal participating in the conference, storing the network identification of the second terminal participating in the conference.

In practical application, the network identifier of the participating second terminal in the participating event notification may be stored in correspondence with the telephone number of the participating second terminal that has recently joined the conference. For example, in step 13 in fig. 1, the user terminal a sends participant addition information to the conference center, where the participant addition information carries the phone number of the user terminal B saved by the user terminal a. Then, in step 22, when the conference center sends a conference event notification to the user terminal a, the network identifier carried in the conference event notification may be stored in correspondence with the telephone number of the user terminal B.

Since the telephone number of the participating second terminal is stored in the embodiment of the application, and the network identifier of the participating second terminal can also be received and/or stored, when the meeting exit event notification is received, and when it cannot be determined which participating second terminal leaves the meeting, the network identifier of the meeting exit second terminal can be matched with the network identifier of the participating second terminal, so that the meeting state can be correctly updated to prompt the participating second terminal to leave the meeting.

Referring to fig. 4, a flowchart of an embodiment of a conference flow control method provided in this embodiment of the present application is shown, where this embodiment may be applied to a first terminal, and the first terminal may establish an SIP conference with one or more second terminals. The first terminal may be understood as a terminal initiating a conference call. The present embodiment may include the following steps:

step 401: and receiving a participation event notification of the participation second terminal, wherein the participation event notification carries the network identifier of the participation second terminal.

A participating second terminal may be understood as a second terminal participating in a conference call. After the participating second terminal enters the conference, the first terminal may receive a conference event notification of the participating second terminal from the conference center. The participation event notification may carry a network identity of the participating second terminal, which may be described by a SIP URI.

Step 402: and receiving a conference leaving event notification of the conference leaving second terminal, wherein the conference leaving event notification carries the network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal comprises the terminal identifier of the conference leaving second terminal.

A conference-away second terminal may be understood as a second terminal that leaves the conference, and there may be one or more conference-away second terminals. The first terminal may receive a departure event notification sent by the conference center, for example, step 41 in fig. 2. The network identifier of the second terminal in the conference may be carried in the conference event notification, and the network identifier may be described using a SIP URI. The network identifier of the second terminal may include the terminal identifier of the second terminal.

Step 403: and when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference.

When the terminal identification of the conference leaving second terminal is the same as the telephone number of the conference participating second terminal, the conference state of the conference participating second terminal can be correctly updated.

And when the terminal identifier of the conference-departing second terminal is different from the telephone number of the conference-participating second terminal, in an implementation manner, the network identifier of the conference-departing second terminal can be directly matched with the network identifier of the conference-participating second terminal.

When the terminal identifier of the conference-departing second terminal is different from the telephone number of the conference-participating second terminal, in another implementation manner, whether the terminal identifier of the conference-departing second terminal and the telephone number of the conference-participating second terminal have a containing relationship or not can be determined; and when the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference do not have the inclusion relationship, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference.

And when the terminal identification of the conference leaving second terminal and the telephone number of the conference participating second terminal have the inclusion relationship, prompting the conference participating second terminal to leave the SIP conference.

In some possible implementation manners of the present application, an implementation manner of matching the network identifier of the conference-departing second terminal with the network identifier of the conference-participating second terminal may be:

determining whether the network identification of the second terminal away from the meeting is the same as the network identification of the second terminal participating in the meeting; and when the network identification of the second terminal in the conference is the same as the network identification of the second terminal in the conference, determining that the network identification of the second terminal in the conference is successfully matched with the network identification of the second terminal in the conference.

In a first implementation manner, if the terminal identifier of the departing second terminal is different from the phone number of the participating second terminal, it may be further determined whether the network identifier of the departing second terminal is the same as the network identifier of a certain participating second terminal.

If the network identifier of the second terminal is the same as the network identifiers of the participating second terminals, the network identifier of the second terminal can be successfully matched with the network identifiers of the participating second terminals. Therefore, the conference state can be correctly updated to prompt the second terminal which is successfully matched with the network identifier to leave the conference.

In a second implementation manner, if the terminal identifier of the departing second terminal is not the same as the phone number of the participating second terminal, it is determined whether the terminal identifier of the departing second terminal has an inclusion relationship with the phone number of a certain participating second terminal. For example, in scenario 2, the terminal identifier 01010086 in the network identifier of the second terminal in the conference has an inclusion relationship with the locally stored telephone number 10086 of the second terminal in the conference, that is, the character string 10086 belongs to a part of the character string 01010086, and thus has an inclusion relationship with the terminal identifier 8986.

If the terminal identification of the conference leaving second terminal has a containing relation with the telephone numbers of the conference participating second terminals, the conference state can be correctly updated to prompt the conference participating second terminals to leave the conference.

And if the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference do not have the inclusion relationship, continuously judging whether the network identification of the second terminal in the conference is the same as the network identification of a certain second terminal in the conference.

If the network identifier of the second terminal leaving the meeting is the same as the network identifier of the second terminal participating in the meeting, the network identifier of the second terminal leaving the meeting can be successfully matched with the network identifier of the second terminal participating in the meeting, so that the meeting state can be correctly updated to prompt the second terminal participating in the meeting, which is successfully matched with the network identifier, to leave the meeting.

For example, the phone number of the second participating terminal stored in the first terminal is 13812345678, the network identifier of the second participating terminal carried in the conference event notification issued by the conference center is anonymous01@ anonymous. invalid, and the terminal identifier anonymous01 in the network identifier of the second participating terminal is different from the phone number 13812345678 of the second participating terminal, so that the network identifier of the second participating terminal and the phone number 13812345678 of the second participating terminal may be correspondingly stored. When the network identifier of the second terminal in the conference is anonymous01@ anonymous.invalidity carried in the notification of the conference event, if the terminal identifiers anonymous01 in the network identifiers of the second terminal in the conference are different from the telephone numbers of the second terminals in the conference, the second terminal in the conference with the telephone number 13812345678 can be determined to be the second terminal in the conference by determining that the network identifiers anonymous01@ anonymous.invalidity are the same as the network identifiers anonymous01@ anonymous.invalidity of the second terminal in the conference, so as to prompt the second terminal in the conference to leave the SIP conference, and thus the list of the participants can be updated correctly.

Step 404: and when the network identification of the conference leaving second terminal is successfully matched with the network identification of the conference participating second terminal, prompting the conference participating second terminal to leave the SIP conference.

When the network identifier of the second terminal leaving the meeting is successfully matched with the network identifiers of the second terminals participating in the meeting, the meeting state can be correctly updated to prompt the second terminals participating in the meeting, which are successfully matched with the network identifiers, to leave the meeting.

And if the network identifier of the departing second terminal is different from the network identifier of the departing second terminal, namely the network identifier of the departing second terminal is not matched with the network identifiers of the participating second terminals, the notification of the departing event is error, and the notification of the departing event can be discarded.

The following describes an embodiment of a conference flow control method provided in the embodiment of the present application, taking an actual application scenario as an example. Referring to fig. 5, a flowchart of another embodiment of a conference flow control method provided in the embodiment of the present application is shown. In this embodiment, the user terminal a serves as a first terminal, and the user terminals B and C serve as second terminals. After the user terminal a creates the teleconference, the user terminal B joins the teleconference, and this embodiment is described with a flow when the user terminal C joins the teleconference, and this embodiment may include:

step 501: and the user terminal A receives the participation event notification, and the participation event notification carries the network identification of the participation user terminal. The network identity may be the network identity of the user terminal C.

Step 502: the user terminal a determines whether the network identifier carried by the participation event notification is the same as or has a containing relationship with the stored telephone number of the user terminal C, if so, the process goes to step 504, and if not, the process goes to step 503.

Step 503: the user terminal a stores the network identifier carried by the participation event notification and the telephone number of the user terminal C correspondingly, and then the process goes to step 504.

Step 504: and the user terminal A updates the conference state, namely, the telephone number of the user terminal C is updated to the participant list displayed by the user terminal A so as to prompt the user terminal C to join the conference.

Referring to fig. 6, a schematic diagram of a participant list after the user terminal C joins the teleconference in the embodiment of the present application is shown.

Referring to fig. 7, a flowchart of another embodiment of a conference flow control method provided in the embodiment of the present application is shown. In this embodiment, the user terminal a serves as a first terminal, and the user terminals B and C serve as second terminals. After the user terminal A, the user terminal B and the user terminal C all join the teleconference, the participating user terminal B leaves the teleconference. In this embodiment, a flow when the user terminal B leaves the teleconference is described, and this embodiment may include:

step 701: the user terminal A receives the event notice of the conference, and the event notice of the conference carries the network identification of the user terminal of the conference.

Step 702: the user terminal a determines whether the network identifier carried by the conference exit event notification matches the stored telephone number or network identifier of a certain conference-participating user terminal, if yes, step 703 is performed, and if not, step 704 is performed.

The user terminal a may determine whether the terminal identifier in the network identifier carried in the conference exit event notification is the same as or has a containment relationship with the stored telephone number of a certain conference participating user terminal. If yes, the network identification carried by the conference exit event notification is matched with the stored telephone number of a certain conference user terminal. If not, continuing to judge whether the network identifier carried by the conference exit event notification is the same as the stored network identifier of a certain conference participating user terminal. If yes, the network identification carried by the conference event notification is matched with the stored network identification of a certain conference participating user terminal. And if not, the network identification carried by the conference event notification is not matched with the stored telephone number or network identification of the participant user terminal.

Step 703: the user terminal a updates the conference state. Namely, the user terminal B corresponding to the network identifier carried by the conference leaving event notification is determined as the conference leaving user terminal, and the telephone number of the user terminal B is removed from the participant list to prompt the user terminal B to leave the conference.

Step 704: the user terminal a discards the breakout event notification.

Referring to fig. 8, a schematic diagram of a participant list after the user terminal B leaves the teleconference in the embodiment of the present application is shown.

That is, in the embodiment of the present application, the conference state can be correctly updated by updating the participant list to prompt the departure terminal to leave the conference.

Referring to fig. 9, an embodiment of a terminal 90 provided in the embodiment of the present application is shown, where the terminal may be a first terminal, and the first terminal may establish a SIP conference with one or more second terminals, and the terminal may include:

a first receiving unit 901, configured to receive a participation event notification of the participating second terminal, where the participation event notification carries a network identifier of the participating second terminal.

A second receiving unit 902, configured to receive a conference exit event notification of the conference exit second terminal, where the conference exit event notification carries a network identifier of the conference exit second terminal, and the network identifier of the conference exit second terminal includes a terminal identifier of the conference exit second terminal.

A matching unit 903, configured to match the network identifier of the conference-departing second terminal with the network identifier of the conference-participating second terminal when the terminal identifier of the conference-departing second terminal is different from the telephone number of the conference-participating second terminal.

And a prompting unit 904, configured to prompt the participating second terminal to leave the SIP conference when the network identifier of the departing second terminal is successfully matched with the network identifiers of the participating second terminals.

Optionally, the terminal may further include:

the determining unit is used for determining whether the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference have an inclusion relationship or not when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference;

and the matching unit is also used for matching the network identifier of the conference leaving second terminal with the network identifier of the conference participating second terminal when the terminal identifier of the conference leaving second terminal does not have the inclusion relationship with the telephone number of the conference participating second terminal.

Optionally, the prompting unit may be further configured to:

Optionally, the matching unit may include:

and the second determining subunit is used for determining that the network identifier of the second terminal in the conference is successfully matched with the network identifier of the second terminal in the conference when the network identifier of the second terminal in the conference is the same as the network identifier of the second terminal in the conference.

Optionally, the network identifier of the participating second terminal may include a terminal identifier of the participating second terminal, and the terminal may further include:

and the storage unit is used for storing the network identifier of the second participating terminal when the terminal identifier of the second participating terminal is determined to be different from the telephone number of the second participating terminal and the terminal identifier of the second participating terminal does not have an inclusion relationship with the telephone number of the second participating terminal.

In the embodiment of the application, when the first terminal telephone number receives the conference participating event notification of the second terminal, the network identifier of the second terminal participating in the conference, which is carried by the conference participating event notification, can be acquired. When receiving the conference leaving event notification of the conference leaving second terminal, the network identifier of the conference leaving second terminal carried by the conference leaving event notification may be obtained, where the network identifier of the conference leaving second terminal includes the terminal identifier of the conference leaving second terminal. When the network identification of the conference leaving second terminal is different from the telephone number of the conference participating second terminal, the conference leaving second terminal can be correctly determined to leave the conference by matching the network identification of the conference leaving second terminal with the network identification of the conference participating second terminal, and the conference leaving event notification notifies the conference leaving event notification so that the conference state can be correctly updated to prompt the conference leaving second terminal to leave the conference.

Fig. 10 is a block diagram showing a partial structure of a mobile terminal 90 according to an embodiment of the present invention. Referring to fig. 10, the mobile terminal includes: radio Frequency (RF) circuitry 810, memory 820, input unit 830, display unit 840, sensor 850, audio circuitry 860, WiFi module 870, processor 880, and power supply 890. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 10 is not intended to be limiting of mobile terminals and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

The following describes each component of the mobile terminal in detail with reference to fig. 10:

RF circuitry 810 may be used to transmit or receive data;

the memory 820 may be used to store software programs and modules, and the processor 880 executes various functional applications and data processing of the mobile terminal by operating the software programs and modules stored in the memory 820. The memory 820 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the mobile terminal, and the like. Further, the memory 820 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 830 may be used to receive an operation instruction of a user and generate a key signal input related to user setting and function control of the mobile terminal 80. Specifically, the input unit 830 may include a touch panel 831 and other input devices 832. The touch panel 831, also referred to as a touch screen, can collect touch operations of a user (e.g., operations of the user on the touch panel 831 or near the touch panel 831 using any suitable object or accessory such as a finger or a stylus pen) thereon or nearby, and drive a corresponding connected mobile terminal according to a preset program. Alternatively, the touch panel 831 may include two portions of a touch detection mobile terminal and a touch controller. The touch detection mobile terminal detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing mobile terminal, converts it into touch point coordinates, and then sends the touch point coordinates to the processor 880, and can receive and execute commands sent from the processor 880. In addition, the touch panel 831 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 830 may include other input devices 832 in addition to the touch panel 831. In particular, other input devices 832 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

The display unit 840 may be used to display an interface. The Display unit 840 may include an indicator Light 841, and the indicator Light 841 may be optionally configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, touch panel 831 can cover indicator 841, and when touch panel 831 detects a touch operation thereon or nearby, it can transmit to processor 880 to determine the type of touch event, and then processor 880 can provide a corresponding visual output on indicator 841 according to the type of touch event. Although the touch panel 831 and the indicator light 841 are implemented as two separate components in fig. 9 to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 831 and the indicator light 841 may be integrated to implement the input and output functions of the mobile terminal.

The mobile terminal 80 may also include at least one sensor 850.

Audio circuitry 860, speaker 861, microphone 862 may provide an audio interface between the user and the mobile terminal. The audio circuit 860 can transmit the electrical signal converted from the received audio data to the speaker 861, and the electrical signal is converted into a sound signal by the speaker 861 and output; on the other hand, the microphone 862 converts the collected sound signal into an electrical signal, which is received by the audio circuit 860 and converted into audio data, and then the audio data is processed by the audio data output processor 880 and transmitted to, for example, another mobile terminal via the camera 810, or the audio data is output to the memory 820 for further processing.

WiFi module 870 may be used for communication.

The processor 880 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 820 and calling data stored in the memory 820, thereby integrally monitoring the mobile terminal. Optionally, processor 880 may include one or more processing units; preferably, the processor 880 may integrate an application processor, which mainly handles operating systems, user interfaces, applications, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into processor 880.

The mobile terminal 80 also includes a power supply 890 (e.g., a battery) for supplying power to the various components, which may be logically connected to the processor 880 via a power management system that may be used to manage charging, discharging, and power consumption.

Although not shown, the mobile terminal 80 may further include a camera, a bluetooth module, etc., which will not be described herein.

In this embodiment of the present invention, the processor 880 included in the mobile terminal further has the following functions:

receiving a participation event notification of a participation second terminal, wherein the participation event notification carries a network identifier of the participation second terminal;

receiving a conference leaving event notification of a conference leaving second terminal, wherein the conference leaving event notification carries a network identifier of the conference leaving second terminal, and the network identifier of the conference leaving second terminal comprises a terminal identifier of the conference leaving second terminal;

when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference;

and when the network identification of the conference leaving second terminal is successfully matched with the network identification of the conference participating second terminal, prompting the conference participating second terminal to leave the SIP conference.

Optionally, the method may further include:

when the terminal identification of the second terminal in the conference is different from the telephone number of the second terminal in the conference, determining whether the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference have an inclusion relationship;

and when the terminal identification of the second terminal in the conference and the telephone number of the second terminal in the conference do not have the inclusion relationship, matching the network identification of the second terminal in the conference with the network identification of the second terminal in the conference.

Optionally, the method may further include:

Optionally, the matching the network identifier of the departing second terminal and the network identifier of the participating second terminal may include:

determining whether the network identification of the second terminal in the conference is the same as the network identification of the second terminal in the conference;

and when the network identifier of the second terminal in the conference is the same as the network identifier of the second terminal in the conference, determining that the network identifier of the second terminal in the conference is successfully matched with the network identifier of the second terminal in the conference.

Optionally, the network identifier of the participating second terminal may include the terminal identifier of the participating second terminal, and may further include:

and when the terminal identification of the second terminal participating in the conference is determined to be different from the telephone number of the second terminal participating in the conference, and the terminal identification of the second terminal participating in the conference and the telephone number of the second terminal participating in the conference do not have an inclusion relationship, storing the network identification of the second terminal participating in the conference.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims

1. A conference flow control method is applied to a first terminal, the first terminal establishes a SIP conference with one or more second terminals, and the method comprises the following steps:

when the network identification of the conference leaving second terminal is successfully matched with the network identification of the conference participating second terminal, prompting the conference participating second terminal to leave the SIP conference;

the matching the network identifier of the second terminal in the conference with the network identifier of the second terminal in the conference includes:

2. The method of claim 1, further comprising:

3. The method of claim 2, further comprising:

4. A method according to any of claims 1-3, wherein the network identities of the participating second terminals comprise terminal identities of the participating second terminals, the method further comprising:

5. A terminal, wherein the terminal is a first terminal, and the first terminal establishes a SIP conference with one or more second terminals, and the terminal comprises:

the prompting unit is used for prompting the participating second terminal to leave the SIP conference when the network identifier of the leaving second terminal is successfully matched with the network identifier of the participating second terminal;

the matching unit includes:

6. The terminal of claim 5, further comprising:

7. The terminal of claim 6, wherein the prompting unit is further configured to:

8. The terminal according to any of claims 5-7, wherein the network identities of the participating second terminals comprise terminal identities of the participating second terminals, the terminal further comprising:

9. A terminal, characterized in that the terminal comprises:

a processor and a memory; the memory stores computer instructions, wherein the processor performs the conference flow control method of any one of claims 1-4 when the computer instructions in the memory are executed.

10. A computer-readable storage medium comprising instructions that, when executed on a first terminal that establishes a SIP conference with one or more second terminals, cause the first terminal to perform the conference flow control method of any of claims 1-4.