Local conference recursive cascading creation method of SIP (Session Initiation Protocol)

Abstract

The invention discloses a local conference recursive cascade creation method of an SIP protocol, and the method comprises the steps: employing an inter-device recursive mode, achieving a distributed sub-conference system, and achieving the connection between a newly-added end device and a last end device through collecting SDP information reserved by the newly-added end device; a host is adopted to record equipment information of newly-added end equipment and reserved SDP information, recursive conference creation and management are achieved, and host invitation, control of mute and transfer by the host, self-exit of an intermediate member, removal of an administrator and host exit events are supported; compatibility of nearest direct connection equipment is adopted, and codec of different call connections is mixed. The method solves the problem that a single device cannot establish too many local calls.

Description

Technical Field

[0001] The invention belongs to the field of SIP communication, in particular to a local conference recursive cascade creation method of the SIP protocol. Background Art

[0002] Currently, the SIP communications industry primarily categorizes multi-device communication into two modes: local conferencing and network conferencing. Local conferencing utilizes the device itself to create mixed audio. Currently, the ALE phone M8 supports up to 12 parties, while other manufacturers generally limit conferencing to 5 parties. Network conferencing primarily relies on server support and phone compatibility. These features enable multiple people in different locations to simultaneously create conferences for efficient communication, realizing virtualized meeting room capabilities.

[0003] Regarding the current SIP market support capabilities, the ALE M8 supports up to 12-party conferencing in local conferencing, while other vendors generally limit conferencing to 3-5 parties. Local conferencing capabilities are primarily determined by the performance of the endpoint and the codec used. Furthermore, differences in the number of supported call control channels often result in different interface configurations for different call counts.

[0004] Although network conferencing is mainly supported by servers and can protect the consistency of the terminal's call interface, current server-based network conferencing requires high-end server support, which increases the cost of the deployment environment. Summary of the Invention

[0005] In order to solve the problem that the number of local conferences created by terminal devices is limited by performance and server conference creation requires additional costs, the present invention provides a local conference recursive cascade creation method of the SIP protocol to improve the resource utilization efficiency of terminal devices.

[0006] To achieve the above object, the present invention adopts the following technical solutions:

[0007] In one embodiment of the present invention, a method for creating a local conference recursively cascaded in a SIP protocol is proposed, the method comprising:

[0008] A distributed sub-conference system is implemented using a recursive method between devices. The newly added terminal device is connected to the previous terminal device by collecting the reserved SDP information of the newly added terminal device. The maximum number of call connections for each device participating in the conference is 2. Each time a newly added terminal device is connected to the previous terminal device, the newly added terminal device sends its own user information and reserved SDP information to the host, which the host can use to subsequently invite devices to establish connections.

[0009] The host records the device information and reserved SDP information of newly added terminal devices to achieve recursive conference creation and management, supporting host invitation, host control of mute and transfer, self-exit of intermediate members and administrator removal, and host exit events;

[0010] Leveraging the compatibility of the nearest directly connected devices, codecs from different call connections are mixed. Each device participating in the conference only needs to maintain uplink and downlink connections, while simultaneously forwarding mixed uplink and downlink audio data, allowing a single device to only encode and decode uplink and downlink audio data. Codec negotiation between distributed sub-conference systems is simplified, requiring only that the devices at both the upper and lower levels support the codec.

[0011] Furthermore, the recursive conference creation process is as follows:

[0012] A1 is the first initiator and establishes a call with B1. A1 mainly collects reserved SDP information and serves as the conference host. B1 sends its own device information and reserved SDP information to A1.

[0013] A1 creates a conference and invites C1 to join. A1 sends B1's reserved SDP information to C1.

[0014] C1 and B1 establish a call, and C1 sends its own device information and reserved SDP information to A1. A1 updates the reserved SDP information of the newly added terminal devices to C1's SDP reserved information.

[0015] B1 forms a connection mode of upper connection A1 and lower connection C1, and does not send reserved SDP information to the outside. At the same time, B1 mixes C1's audio data and sends it to A1, and B1 mixes A1's audio data and sends it to C1;

[0016] A1 invites D1 to join the conference and sends C1's reserved SDP information to D1.

[0017] C1 and D1 establish a call, and D1 sends its device information and reserved SDP information to A1;

[0018] A1 updates the SDP reserved address of D1 to which the newly added terminal devices need to connect;

[0019] C1 establishes a call with B1 in the uplink and with D1 in the downlink. It mixes D1's audio data and sends it to B1. C1 then sends B1's mixed audio data, including A1's, to D1.

[0020] Based on this recursive mode, A1 needs to maintain the latest available terminal device reserved SDP information and display device information.

[0021] Furthermore, the process for the host to control mute and transfer in recursive conference management is as follows:

[0022] A1 needs to mute C1 in the conference. A1 sends a mute request to C1 based on C1's device information.

[0023] C1 stops sending its own audio data to B1, but keeps forwarding the data coming in from D1 to B1, and also keeps forwarding the data coming in from B1 to D1;

[0024] A1 wishes to transfer the conference host role to D1 and downgrade itself to a conference member. Based on the displayed device information, A1 sends a conference host transfer request to D1. The request includes the device information displayed on A1, the reserved SDP information of the terminal device, and A1's downlink interface data. A1 then creates a pre-stored uplink interface.

[0025] After receiving A1's conference host transfer request, D1 responds to A1, including: D1's uplink interface data and downlink interface data;

[0026] A1 sends a call refresh message to inform B1 to forward subsequent data to D1's downlink interface. At the same time, A1 loses conference management privileges and is downgraded to a member.

[0027] D1 sends a call refresh, telling C1 to forward subsequent data to A1's uplink interface, and telling E1 to forward subsequent data to A1's downlink interface;

[0028] D1 displays device information and related host authority buttons, and notifies members to update host information based on the device information provided by A1.

[0029] Furthermore, the process of self-exit of intermediate members and removal of administrators in recursive conference management is as follows:

[0030] If B1 wants to exit the conference but wants to ensure that downlink members continue to participate, B1 needs to send a call refresh to C1, informing C1's uplink interface of B1's uplink interface data;

[0031] After C1 receives the call update, it updates the uplink interface data of C1 to A1;

[0032] B1 sends the exit conference device information to A1, and A1 updates the device information so that the administrator knows that B1 has exited.

[0033] If administrator A1 removes B1, the administrator sends a command to exit the meeting to B1. After receiving it, B1 repeats the first three steps to complete the removal of B1.

[0034] Furthermore, the host exit event process in recursive conference management is as follows:

[0035] A1 wishes to withdraw from the meeting and hand it over to D1 for chairing;

[0036] A1 sends a conference host transfer request to D1. Following the host control mute and transfer process in recursive conference management, D1 is promoted to host and A1 is demoted to member.

[0037] A1 completes the intermediate member self-exit operation according to the intermediate member self-exit and administrator removal process in recursive conference management.

[0038] In one embodiment of the present invention, a computer device is also proposed, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the aforementioned local conference recursive cascade creation method of the SIP protocol is implemented.

[0039] In one embodiment of the present invention, a computer-readable storage medium is further provided. The computer-readable storage medium stores a computer program for executing a local conference recursive cascade creation method of a SIP protocol.

[0040] Beneficial effects:

[0041] 1. The present invention solves the problem of different devices supporting local conference restrictions, breaking through the local conference device restrictions and being limited to 3 or 5 parties, and greatly meeting the local conference multi-person call operation.

[0042] 2. The present invention solves the problem of network conferencing relying on server costs, and achieves recursive addition of members and management functions without user awareness, thus simplifying the cost of deploying multi-person conference rooms and enabling the simplest SIP server to support multiple people online concurrently.

[0043] 3. The present invention utilizes the dual-node support capability of a single device, occupies minimal device resources, and enables low-performance SIP terminals to participate, thereby simultaneously reducing the price cost of the terminal equipment. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Figure 1 This is a flow chart of recursive conference creation according to the present invention;

[0045] Figure 2 This is a flow chart of the host controlling mute and transfer in the recursive conference management of the present invention;

[0046] Figure 3 This is a flow chart of the self-exit of an intermediate member and the removal of an administrator in the recursive conference management of the present invention;

[0047] Figure 4 2 is a schematic diagram of a recursive call networking according to Embodiment 1 of the present invention;

[0048] Figure 5 It is a schematic diagram of the computer device structure of the present invention. DETAILED DESCRIPTION

[0049] The principles and spirit of the present invention will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided solely to enable those skilled in the art to better understand and implement the present invention, and are not intended to limit the scope of the present invention in any way. Rather, these embodiments are provided to make this disclosure more thorough and complete, and to fully convey the scope of the present disclosure to those skilled in the art.

[0050] Those skilled in the art will appreciate that the embodiments of the present invention may be implemented as a system, apparatus, device, method, or computer program product. Therefore, the present disclosure may be implemented in the following forms: entirely in hardware, entirely in software (including firmware, resident software, microcode, etc.), or in a combination of hardware and software.

[0051] The present invention provides a method for recursive cascading local conference creation based on the SIP protocol. To address the problem of a single device being unable to establish too many local calls, inter-device recursion is employed. Specifically, the maximum number of call connections for each participating device is two. Each newly added terminal device connects to the previous terminal device, such as A connecting only to B, B connecting to AC, C connecting to BD, and so on, forming a recursive audio data forwarding system. The newly added terminal device sends its own user information and reserved SDP information to the host, which the host can then use to invite devices to establish connections, thereby implementing a distributed sub-conference system. By collecting the reserved SDP information of the newly added terminal device, the newly added terminal device is connected to the previous terminal device, expanding the local device's member capacity. Decentralized single-device control reduces the performance load of the host device and improves the multi-party communication capabilities of low-performance devices. The host records the device information and reserved SDP information of the newly added terminal device to implement recursive conference creation and management, supporting host invitations, host-controlled muting and transfers, intermediate member self-exit and administrator removal, and host exit events. Leveraging the compatibility of the nearest directly connected device, codecs for different calls are mixed, maintaining high device availability. For example, if a conference connection model is established as A1-B1-C1-D1, then audio data processing between devices actually requires processing a maximum of two connections. For example, B1 only needs to process data from C1 and A1, and does not need to worry about data sent from D1 to C1. In this way, B1 only needs to ensure codec support with A1 and C1, without worrying about D1's codec support. Similarly, D1 does not need to worry about the codec support of A1 and B1. Therefore, devices only need to consider the capabilities of the most directly connected device. In this conference system, the maximum number of connections for all devices is two. Only uplink and downlink connections are maintained, and mixed forwarding of uplink and downlink call data is implemented. This allows a single device to only perform encoding and decoding of uplink and downlink audio data, reducing CPU and other resource consumption. The recursive system's device forwarding configuration simplifies codec negotiation between conference subsystems, ensuring codec support only with devices at the upper and lower levels, without requiring all devices to have the same codec processing capabilities. This makes it suitable for devices with different performance and codec support capabilities.

[0052] The principles and spirit of the present invention are explained in detail below with reference to several representative embodiments of the present invention.

[0053] like Figure 1 As shown, the recursive conference creation process steps are:

[0054] S01: A1 is the first initiator and establishes a call with B1. As A1 is the first initiator, it mainly collects recursive information and serves as the conference host. B1 sends its own device information and reserved SDP information to A1.

[0055] S02: A1 creates a conference and invites C1 to join. Since A1 is the first initiator, A1 sends B1's reserved SDP information to C1.

[0056] S03: C1 and B1 establish a call. C1 sends its own device information and reserved SDP information to A1. A1 updates the reserved SDP information of the newly added terminal devices to C1's SDP reserved information.

[0057] S04: B1 forms a connection mode with upper connection A1 and lower connection C1, and does not send reserved SDP information to the outside. At the same time, B1 needs to mix C1's audio data and send it to A1, and B1 mixes A1's audio data and sends it to C1;

[0058] S05: A1 invites D1 to join the conference and sends C1's reserved SDP information to D1.

[0059] S06: C1 and D1 establish a call, and D1 sends its device information and reserved SDP information to A1;

[0060] S07: A1 updates the SDP reserved address of D1 to which the subsequent terminal device needs to connect;

[0061] S08: C1 establishes an uplink call with B1 and a downlink call with D1. At the same time, C1 needs to mix D1's audio data and send it to B1. C1 needs to send B1's mixed audio data including A1's mixed audio data to D1.

[0062] S09: Based on this recursive mode, the three parties can talk. A1 needs to maintain the latest SDP information reserved by the available terminal devices and display device information.

[0063] Based on the above logic, recursively added endpoints establish a connection with the previous endpoint after joining the conference. They receive mixed audio data from the upstream device, enabling everyone to communicate. This process allows for the addition of EFN devices. Each newly added endpoint needs to update the reserved SDP information of the host device A1 and its own device information. Each device has a maximum of two call data channels.

[0064] like Figure 2 As shown, recursive conference management --- host control of mute and transfer process steps:

[0065] S01: A1 needs to mute C1 in the conference. Because A1 has C1's device information, A1 directly sends a mute request to C1.

[0066] S02: C1 stops sending its own audio data to B1, but still keeps forwarding the data entering the D1 port to B1, and at the same time keeps forwarding the data entering the B1 port to D1;

[0067] S03: A1 wishes to transfer the conference host to D1 and downgrade itself to a conference member. Based on the displayed device information, A1 sends a conference host transfer request to D1. The request includes: the device information displayed on A1 and the reserved SDP information (the reserved SDP information of the end device), A1's downlink interface data (the call connection data with B1), and A1 creates a pre-stored uplink interface.

[0068] S04: After receiving the conference host transfer request from A1, D1 responds to A1, including: D1's uplink interface data (call connection information with C1) and downlink interface data (call interface data with E1).

[0069] S05: A1 sends a call refresh message to inform B1 to forward subsequent data to D1's downlink interface. At the same time, A1 loses the conference control and management authority and is downgraded to a member.

[0070] S06: D1 sends a call refresh, telling C1 to forward subsequent data to A1's uplink interface, and telling E1 to forward subsequent data to A1's downlink interface;

[0071] S07: D1 displays the device information, presses the buttons to display the relevant host authority buttons, and notifies members to update the host information based on the device information provided by A1.

[0072] like Figure 3 As shown in the figure, recursive meeting management --- intermediate members self-exit and administrator removal process steps:

[0073] S01: If B1 wants to exit the conference but wants to ensure that downlink members continue to participate, B1 needs to send a call refresh to C1, informing C1's uplink interface data (A1) of B1;

[0074] S02: After receiving the call update, C1 updates the uplink interface data of C1 to A1;

[0075] S03: B1 sends the exit conference device information to A1. A1 updates the device information so that the administrator knows that B1 has exited.

[0076] S04: If administrator A1 removes B1, the administrator sends a command to exit the meeting to B1. After receiving the command, B1 repeats steps S01-S03 to complete the removal of B1.

[0077] Recursive meeting management---host exit event process steps:

[0078] S01: A1 wishes to withdraw from the meeting and hand it over to D1 to preside over;

[0079] S02: A1 sends a conference host transfer request to D1, completing D1's upgrade to host and A1's downgrade to member (recursive conference management - host control of mute and transfer)

[0080] S03: A1 completes the self-exit operation of the intermediate member (recursive meeting management---intermediate member self-exit and administrator removal)

[0081] It should be noted that although the operations of the method of the present invention are described in a specific order in the above embodiments and drawings, this does not require or imply that these operations must be performed in this specific order, or that all illustrated operations must be performed to achieve the desired results. Additionally or alternatively, certain steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0082] In order to more clearly explain the above-mentioned local conference recursive cascade creation method of the SIP protocol, a specific embodiment is described below. However, it should be noted that this embodiment is only for better illustrating the present invention and does not constitute an improper limitation to the present invention.

[0083] Example 1: User A initiates and controls a conference:

[0084] 1. User A uses device A1 to call user B's device B1.

[0085] 2. User B answers the call and establishes a call. Device B1 sends the reserved SDP information to device A1, which then stores it in the cache.

[0086] 3. User A initiates a local conference and invites user C to join. By doing so, user A calls user C's device C1. (When calling device C1, device A1 sends device B1's reserved SDP information to device C1, and device C1 actually establishes a connection with device B1.)

[0087] 4. Users A, B, and C form a conference and can talk to each other (Device B1 mixes the audio data sent by device A1 with the channel with C1, and mixes the audio data sent by device C1 with the channel with A1). At this time, device A1 updates the cached data to C1.

[0088] 5. User A invites user D to join the conference and calls device D1 (device A1 sends C1's reserved SDP information to D1);

[0089] 6. User D joins the conference (actually establishes a connection with user C1's device. At this time, C1 mixes the audio data of B1's channel and sends it to D1's channel, and C1 mixes the audio data of D1's channel and sends it to B1's channel).

[0090] 7. User A invites user N to join the conference and calls device N1.

[0091] 8. User N joins the meeting (actually establishing a connection with the upper-level user);

[0092] 9. Users A, B, C, D.....N can all communicate in the meeting (refer to Figure 4 , recursive call networking);

[0093] 10. User A makes a presentation in a meeting. To maintain effectiveness, User A mutes everyone.

[0094] 11. After user A finishes his presentation, B and C need to speak and discuss. User A sends instructions to devices B1 and C1.

[0095] 12. Devices B1 and C1 are muted. At this point, users A, B, and C are allowed to speak, while the rest of the group can only listen.

[0096] 13. User A ends the meeting and wants all participants to exit, so he sends a meeting end notification.

[0097] 14. Devices B1 through N1 receive the conference end command, delete their upstream and downstream interfaces, and exit the conference.

[0098] 15. Device A1 exits the meeting.

[0099] Example 2 - Conference Transfer Authorization

[0100] User A is the assistant of User D, and User D is ultimately responsible for and in control of the conference.

[0101] 1. User A uses device A1 to set up a conference and invites users B, C, D, E, F, and G to the conference. The devices used are B1, C1, D1, E1, F1, and G1 respectively.

[0102] 2. After user A confirms that all users have joined the meeting, he needs to transfer the meeting host position to user D;

[0103] 3. User A's device A1 sends a conference transfer request (including: member list, connection information of A1 and B1, and pre-stored SDP information) to user D's device D1.

[0104] 4. User D and user A complete the transfer. User D's device D1 displays the current conference participants and can perform conference control (D1 responds to A1's exchange information and returns the call interface information of the previous channel and the next channel).

[0105] 5. User D mutes all participants and then starts the meeting (D updates the address for sending meeting authorization information to all participants);

[0106] 6. At the same time, user A becomes a common member and loses the ability to control the meeting.

[0107] 7. User D takes control of the meeting and has a discussion with user BCEF.

[0108] 8. If user A wishes to exit the conference while the transfer is being triggered, after completing steps 1-7, device A1 invokes the intermediate member self-exit process.

[0109] Based on the above invention concept, Figure 5 As shown, the present invention also proposes a computer device 100, including a memory 110, a processor 120, and a computer program 130 stored in the memory 110 and executable on the processor 120. When the processor 120 executes the computer program 130, the local conference recursive cascade creation method of the aforementioned SIP protocol is implemented.

[0110] Based on the aforementioned inventive concept, the present invention further proposes a computer-readable storage medium storing a computer program for executing the aforementioned local conference recursive cascade creation method of the SIP protocol.

[0111] The present invention proposes a method for creating a local conference recursively cascading in a SIP protocol, which has the following highlights:

[0112] 1. The bidirectional node mode of the equipment of the present invention ensures that the conference subsystem only needs to maintain the upper and lower level equipment, and adopts a step-by-step recursive approach to achieve conference expansion.

[0113] 2. The present invention needs to complete the exchange capability of device information, adopts a recursive approach, and only needs to ensure that the upper-level device obtains it, thereby reducing the performance overhead of device maintenance information.

[0114] 3. The present invention implements signal transmission in a recursive manner, thereby realizing common conference control capabilities in the conference, supporting the invitation, removal, and transfer of hosts.

[0115] Although the spirit and principles of the present invention have been described with reference to several specific embodiments, it should be understood that the present invention is not limited to the specific embodiments disclosed, and the division into various aspects does not mean that the features of these aspects cannot be combined to benefit. Such division is only for the convenience of expression. The present invention is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.

[0116] Regarding the limitation of the protection scope of the present invention, those skilled in the art should understand that, based on the technical solution of the present invention, various modifications or variations that can be made by those skilled in the art without creative work are still within the protection scope of the present invention.

Claims

1. A method for creating a local conference recursive cascade in a SIP protocol, characterized in that: The method includes: A distributed sub-conference system is implemented using a recursive method between devices. The newly added terminal device is connected to the previous terminal device by collecting the reserved SDP information of the newly added terminal device. The maximum number of call connections for each device participating in the conference is 2. Each time a newly added terminal device is connected to the previous terminal device, the newly added terminal device sends its own user information and reserved SDP information to the host, which the host can use to subsequently invite devices to establish connections. The host records the device information and reserved SDP information of newly added terminal devices to achieve recursive conference creation and management, supporting host invitation, host control of mute and transfer, self-exit of intermediate members and administrator removal, and host exit events; Leveraging the compatibility of the nearest directly connected devices, codecs from different call connections are mixed. Each device participating in the conference only needs to maintain uplink and downlink connections, while simultaneously forwarding mixed uplink and downlink audio data, allowing a single device to only encode and decode uplink and downlink audio data. Codec negotiation between distributed sub-conference systems is simplified, requiring only that the devices at both the upper and lower levels support the codec.

2. The method for creating a local conference recursively cascading in the SIP protocol according to claim 1, characterized in that: The recursive conference creation process is as follows: A1 is the first initiator and establishes a call with B1. A1 mainly collects reserved SDP information and serves as the conference host. B1 sends its own device information and reserved SDP information to A1. A1 creates a conference and invites C1 to join. A1 sends B1's reserved SDP information to C1. C1 and B1 establish a call, and C1 sends its own device information and reserved SDP information to A1. A1 updates the reserved SDP information of the newly added terminal devices to C1's SDP reserved information. B1 forms a connection mode of upper connection A1 and lower connection C1, and does not send reserved SDP information to the outside. At the same time, B1 mixes C1's audio data and sends it to A1, and B1 mixes A1's audio data and sends it to C1; A1 invites D1 to join the conference and sends C1's reserved SDP information to D1. C1 and D1 establish a call, and D1 sends its device information and reserved SDP information to A1; A1 updates the SDP reserved address of D1 to which the newly added terminal devices need to connect; C1 establishes a call with B1 in the uplink and with D1 in the downlink. It mixes D1's audio data and sends it to B1. C1 then sends B1's mixed audio data, including A1's, to D1. Based on this recursive mode, A1 needs to maintain the latest available terminal device reserved SDP information and display device information.

3. The method for creating a local conference recursively cascading in the SIP protocol according to claim 1, characterized in that: The process of the host controlling mute and transfer in the recursive conference management is as follows: A1 needs to mute C1 in the conference. A1 sends a mute request to C1 based on C1's device information. C1 stops sending its own audio data to B1, but keeps forwarding the data coming in from D1 to B1, and also keeps forwarding the data coming in from B1 to D1; A1 wishes to transfer the conference host role to D1 and downgrade itself to a conference member. Based on the displayed device information, A1 sends a conference host transfer request to D1. The request includes the device information displayed on A1, the reserved SDP information of the terminal device, and A1's downlink interface data. A1 then creates a pre-stored uplink interface. After receiving A1's conference host transfer request, D1 responds to A1, including: D1's uplink interface data and downlink interface data; A1 sends a call refresh message to inform B1 to forward subsequent data to D1's downlink interface. At the same time, A1 loses conference management privileges and is downgraded to a member. D1 sends a call refresh, telling C1 to forward subsequent data to A1's uplink interface, and telling E1 to forward subsequent data to A1's downlink interface; D1 displays device information and related host authority buttons, and notifies members to update host information based on the device information provided by A1.

4. The method for creating a local conference recursively cascaded in SIP protocol according to claim 1, characterized in that: The process of self-exit of intermediate members and removal of administrators in the recursive conference management is as follows: If B1 wants to exit the conference but wants to ensure that downlink members continue to participate, B1 needs to send a call refresh to C1, informing C1's uplink interface of B1's uplink interface data; After C1 receives the call update, it updates the uplink interface data of C1 to A1; B1 sends the exit conference device information to A1, and A1 updates the device information so that the administrator knows that B1 has exited. If administrator A1 removes B1, the administrator sends a command to exit the meeting to B1. After receiving it, B1 repeats the first three steps to complete the removal of B1.

5. The method for creating a local conference recursively cascading in the SIP protocol according to claim 1, characterized in that: The process of the host exit event in the recursive conference management is as follows: A1 wishes to withdraw from the meeting and hand it over to D1 for chairing; A1 sends a conference host transfer request to D1. Following the host control mute and transfer process in recursive conference management, D1 is promoted to host and A1 is demoted to member. A1 completes the intermediate member self-exit operation according to the intermediate member self-exit and administrator removal process in recursive conference management.

6. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the method according to any one of claims 1 to 5 is implemented.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program for executing any one of claims 1 to 5.

Images